Architecture Modeling - SPES 2020

More documents

Recommendations

Info

Architecture Modeling structed for every combination of abstraction level and perspective, representing a view of the system under development. 2.3.2.2 Composition The ports of HRCs used as parts in the context of another HRC are interconnected forming a composition of HRCs. In a component-based design there are two use-cases for the composition concept. A component can be decomposed(↑) into smaller subcomponents in a top-down approach. So, a large design is split into smaller components, that can be implemented or further decomposed. Following a bottom-up approach one can also specify components and integrate them in a composition to realize its specification. ComponentC delegation connector part2:ComponentB part1:ComponentA ComponentB C2 C12 assembly connector ComponentA C1 Figure 2.10: Compositions of components To decide whether an HRC can be used in a given context and connected with other HRCs, the ports that are connected must be compatible. Compatibility of ports is discussed in Section 3.3.2.2. Figure 2.10 shows the distinction between delegation connectors and assembly connectors. The former connect the outer ports of an HRC to ports of its constituting parts. So in order to connect the ports they must have the same direction. Assembly connectors link the parts of a composition to each other. Additionally with regard to the contracts a Virtual Integration Test(↑) must be carried out (cf. Section 4.2). Related to the example from Figure 2.10 it must be checked, that the contracts C1 and C2 are compatible and that together with the interconnection they are a valid refinement of C12. p1 p2 14/ 156
3 The Architecture Meta-Model In Section 2 we briefly introduced the fundamental concepts of the architecture modeling approach. In this section these concepts are described in more detail. In addition it is shown how they are expressed in the architecture meta-model and how concepts relate to each other. However it is not in the scope of this document to give a complete specification of the architecture meta-model. That specification is delivered seperately in [50]. Note, that we sometime use the abbreviation SPESMM denoting the architecture meta-model. 3.1 Abstraction levels The SPESMM introduces a generic concept of abstraction levels. An abstraction level represents the system under development at a certain level of detail. A car for example may be modelled at the top-level as a single component where only the interface of the car to the environment is visible. At a lower level, certain components of the car may be visible (chassis, engine, ...), and so on. +subPackage Package SystemModel +owner 0..1 1..* +owner 0..1 0..* +abstractionLevel DeclarationZone 1 +topLevel +declarationZone 0..1 +owner AbstractionLev el 0..1 +ownedPerspective Perspectiv e +successor 0..1 0..* +abstractionLevel 0..* 0..* +perspective +declared ReusableElement 0..* + kind: PerspectiveKind AbstractionLev elCategory +category 0..1 Figure 3.1: Meta-model integration of the concept of abstraction levels A design item (e. g. the system under development or a component) may be modeled on different levels of abstraction. An ordering relation on the abstraction levels within a model is defined by means of the successor-association between AbstractionLevels (see Figure 3.1). The highest abstraction level associated by the SystemModel in the role of topLevel is intended to contain the most abstract description. Each AbstractionLevel owns a set of Perspectives, that in turn contain models and requirements. An abstraction level may be further categorized by AbstractionLevelCategory, which allows to adapt the concept to development processes of a company. So for an abstraction level of a certain category one can e. g. specify the set of considered perspectives. The component hierarchy modelled within a certain abstraction level may be re-arranged within the next lower abstraction level. Thus, a component-based architecture can not only be 15/ 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: Architecture Modeling can usually o
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 and 32: 3.2.5 Geometrical Perspective Archi
Page 33 and 34: ShapeCompositionOperator intersecti
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?