Architecture Modeling - SPES 2020

More documents

Recommendations

Info

Architecture Modeling zones such as cargo bay or engine bay. In order to describe the external structure of a geometric component there can be a shape. Geometric component installations are specialized rich component properties. Having the role of rich component parts they are instances of geometrical components and therefore typed by them. Instantiated technical components can be allocated to these installations. I.e. a technical ECU of a car is allocated to an installation of a representing geometrical component. Geometric installations can be location installations or routed installations. A location installation refers to a defined location of the containing geometric component. The location installation specifies that a geometric component of its type is installed to that location and therefore to the position which is specified by the translation releative to the reference system of the containg geometric component. I.e. an acceleration sensor is installed to a location x = 0m, y=-20cm and z=1,2m relative to the middle of the car. Routed installations declare a route for a geometric component along several component links. They are used for layable components like cables or pipes. I.e. in the car the mentioned acceleration sensor is connected to an ECU in the cargo bay by a cable component that is layed via several locations with a total length of 3 m. Geometric failures are specialized failure conditions. They describe failure conditions which have effects on geometric structures. Therefore, a geometric failure can have a shape property which describes the sphere of effect that a geometric failure has. I.e. the battery of a car can explode and damage other components inside a sphere with a radius of 20 cm. Geometric Coordinates Figure 3.19 provides an overview on concepts to describe geometric coordinates. GeometricScaling +length 0..1 +width 0..1 +height 0..1 +x 0..1 GeometricTranslation +y 0..1 Expression +z 0..1+roll 0..1 GeometricRotation +pitch 0..1 +yaw 0..1 Figure 3.19: Concepts of the geometrical perspective to cover coordinates. Geometric coordinates are relative to the respective reference system. They are given by geometric scaling, geometric, translation and geometric rotation. Geometric Shapes Figure 3.20 provides an overview on concepts to describe geometric shapes. Geometric shapes describe the shape of a geometric component or the sphere of effect of a geometric failure. They can be primitive shapes such as spheres, cylinders or cuboids. A sphere is defined by its radius, a cylinder is defined by its radius and its length and a cuboid is defined by its length, its width and by its height. A shape can be a mesh. A mesh is a user defined shape which consists of vertices and edges. The position of a vertex is given by a translation relativ to its reference system. Edges connect vertices. A complex shape is defined by a composite shape. A composite shape consists of shape properties as operands respectively typed by shapes. A shape composition operator defines how the operands together provide a shape. The shape operators are defined as follows: 28/ 156
ShapeCompositionOperator intersection union difference Shape Sphere Cylinder Cuboid +radius 1 +radius 1 +length 1 +length 1 +width 1 +height 1 Expression Architecture Modeling +type 1 Mesh +edge 0..* Edge «isOfType» CompositeShape Vertex ShapeProperty + operator: ShapeCompositionOperator +compositeShape +vertex 1..* +vertex 2 +operand 2..* +scaling 0..1 +rotation 0..1 +translation Figure 3.20: Concepts of the geometrical perspective to cover shapes. intersection The composed shape is given by the intersection of the operands. intersection The composed shape is given by the union of the operands. 0..1 0..1 GeometricScaling GeometricRotation GeometricTranslation +position 1 difference The composed shape is given by the difference between the first and the second operand. For this operator ony two operands may be given. 3.2.5.1 Optimizing Cable lengths based on function allocation constraints The different perspectives have already been introduced in this document. Now a use case shall demonstrate how the perspectives get used in a real life example from the automotive domain and how transformations between them are performed. The use case arises from the idea to split the airbag system up on to existing general purpose ECUs. To avoid having very high safety integrity levels for the ECUs the functions of the airbag system have to be deployed redundantly. To allow an ASIL (Automotive Safety Integrity Level) reduction, the independence of the functions have to be ensured. This especially means that the redundant function must not be deployed on the same ECU. The Airbag system consists out of 4 ECUs, in this simplified example, that are distributed across the ego vehicle and a set of pressure and acceleration sensors. Each logical airbag system part requires a known set of sensors at known locations. If a function gets mapped to an ECU also the corresponding sensors need to be connected to the same ECU. The use case consists of the creation of the allocation of logical airbag systems to the ECUs by fulfilling the independence constraints on the one hand side and resource availability on the other side. The resources are given by the available interfaces on one ECU that limits the number and type of connectable sensors. Furthermore the length of the cable from the ECUs to the sensors shall be minimized to reduce the costs of the system. The use case is an excerpt from an automotive design process that deals only with the optimization problem of reducing the length of the cable that connect sensors and ECUs that are distributed across the vehicle and the different constraints that limit the abilities of solving the problem. The independence constraints are typically a result from different safety analyzes but are considered as given in this use case. The problem basically consists of combining three perspectives: • The logical perspective, where safety constraints for the elements are expressed 29/ 156
Page 1 and 2: Architecture Modeling ∗ Andreas B
Page 3 and 4: Contents 1 Introduction 1 2 Quick-T
Page 5 and 6: 1 Introduction This document propos
Page 7 and 8: Architecture Modeling allowing to m
Page 9 and 10: Architecture Modeling creating a vi
Page 11 and 12: Architecture Modeling the design it
Page 13 and 14: Architecture Modeling of the logica
Page 15 and 16: Architecture Modeling realization o
Page 17 and 18: Architecture Modeling can usually o
Page 19 and 20: 3 The Architecture Meta-Model In Se
Page 21 and 22: Abstraction-Levels (detail increase
Page 23 and 24: 3.2.2 Functional Perspective Archit
Page 25 and 26: Architecture Modeling The semantics
Page 27 and 28: Architecture Modeling expressed by
Page 29 and 30: Architecture Modeling computing cap
Page 31: 3.2.5 Geometrical Perspective Archi
Page 35 and 36: Architecture Modeling The constrain
Page 37 and 38: Architecture Modeling of particular
Page 39 and 40: Architecture Modeling Shape that de
Page 41 and 42: Architecture Modeling Conjugation o
Page 43 and 44: RichComponent Architecture Modeling
Page 45 and 46: MultiplicityElement +part 0..* Rich
Page 47 and 48: ComponentC Architecture Modeling pa
Page 49 and 50: 4 Steps in Component-Based Design T
Page 51 and 52: Architecture Modeling Assume/guaran
Page 53 and 54: Architecture Modeling When specifyi
Page 55 and 56: Architecture Modeling next selectio
Page 57 and 58: Architecture Modeling ports must ha
Page 59 and 60: established if (and only if): Archi
Page 61 and 62: 12°C < tempSelect < 35°C actTemp
Page 63 and 64: Architecture Modeling The component
Page 65 and 66: Architecture Modeling 4.3.2 Establi
Page 67 and 68: Architecture Modeling a mapping is
Page 69 and 70: Architecture Modeling Another impor
Page 71 and 72: 5 Using the Architecture Meta-Model
Page 73 and 74: Architecture Modeling Design proces
Page 75 and 76: Architecture Modeling abstraction l
Page 77 and 78: Pwr1 Pedal_Pos1 Pwr2 Pedal_Pos2 CMD
Page 79 and 80: Architecture Modeling Figure 5.4: O
Page 81 and 82: Architecture Modeling Figure 5.7: L
Page 83 and 84:
Architecture Modeling Figure 5.9: T
Page 85 and 86:
Architecture Modeling Figure 5.12:
Page 87 and 88:
Page 89 and 90:
Architecture Modeling However this
Page 91 and 92:
Architecture Modeling The considera
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Architecture Modeling tasks Command
Page 99 and 100:
Architecture Modeling of the V, suc
Page 101 and 102:
Architecture Modeling thus decorate
Page 103 and 104:
Architecture Modeling In summary, P
Page 105 and 106:
Architecture Modeling OEMs are incr
Page 107 and 108:
Architecture Modeling provide effec
Page 109 and 110:
Page 111 and 112:
Architecture Modeling patterns, cap
Page 113 and 114:
Architecture Modeling 6.1 Syntax an
Page 115 and 116:
6.1.1.1.1 Attribuute Definit tion a
Page 117 and 118:
Constrrain Eventts with Co ondition
Page 119 and 120:
These events used in the “and the
Page 121 and 122:
Formalization: whenever StartButton
Page 123 and 124:
Architecture Modeling Basic bloock
Page 125 and 126:
6.1.1.1.1.3 Conditions Conditions c
Page 127 and 128:
6.1.1.1.2.2 Seammless Con ncatenati
Page 129 and 130:
e3 && (clk==0) e1 idle pre e1 idle
Page 131 and 132:
Pattern whenever event occurs condi
Page 133 and 134:
If the brake force is above 80% for
Page 135 and 136:
Pattern S3: Failure shall not be ca
Page 137 and 138:
Pattern S9: failureCondition failur
Page 139 and 140:
Pattern R2: Event occurs each perio
Page 141 and 142:
idle e1 |clk:=0 e2 && (l
Page 143 and 144:
The function : allocates a singl
Page 145 and 146:
Examplees of clocks: • Run: {c=0@
Page 147 and 148:
Architecture Modeling 1. For σ ∈
Page 149 and 150:
Architecture Modeling Traces accord
Page 151 and 152:
Architecture Modeling Definition 6.
Page 153 and 154:
Architecture Modeling the one given
Page 155 and 156:
Architecture Modeling Decomposition
Page 157 and 158:
Bibliography [1] ARINC 653 - Avioni
Page 159 and 160:
Architecture Modeling [26] Holger G
show all

Architecture Modeling - SPES 2020

Create successful ePaper yourself

Delete template?

Save as template?