Architecture Modeling - SPES 2020

More documents

Recommendations

Info

Architecture Modeling refined by decomposition of components (see Section 3.3.2.2), but also by means of a different component hierarchy. So refinement subsumes but is not restricted to simple decomposition of components. When switching abstraction levels the component-models must be related to each other. This is done by Realize-trace links (shown in Figure 3.2), that constitute a mapping relation between component instance roles of different abstraction levels. Due to its similarity to Allocate-trace links, the superordinate concept of Mapping has been defined, that is discussed in Section 3.4. +type 1 RichComponent +component 1 «isOfT ype» +part 0..* +m appedT o RichComponentProperty 1 «instanceRef» +m apped 1 «instanceRef» Allocate Mapping Realize Figure 3.2: Meta-model integration of the concept of Realize-trace links While the models on lower abstraction levels usually provide more detail with regard to the design item, the respective models still have to satisfy all functional and non-functional requirements defined for their higher level counterparts with respect to a continuous development process. The Realize-link provided by the meta-model also indicates the proof obligations, that have to be performed to ensure a valid refinement with regard to the specified contracts. The realize relation is discussed detailed in Section 4.4. Since the design processes for different application domains like automotive and avionics are very diverse, a fixed set of predefined abstraction levels has found to be insufficient to support different domains. The EAST-ADL abstraction levels for example are just one possible instantiation of the generic abstraction level concept. In other application domains, e. g. avionics, or even for different companies in the same domain, the set of actually used concrete abstraction levels may be different. The meta-model provides concepts for tailoring models to specific needs. This allows to define so-called model libraries that provide predefined sets of abtraction levels, such as those defined in EAST-ADL. The underlying formal semantics of the Realizelink then allows the verfication of refinements of component-models. 3.2 Perspectives Beside the distinction of different user-defined abstraction levels, a model of a system under development may be associated with certain viewpoints, such as defined in [33]. The architecture meta-model differentiates between viewpoints that establish structurally different views on the system (perspectives), and viewpoints, that are orthogonal to the structure of the system and describe different aspects of functional and/or non-functional properties of model elements. The concept of aspects is discussed in Section 3.3.1.2. So models of a system addressing a certain perspective will specify the structure of the system from that particular perspective. This results in a two-dimensional organization of component 16/ 156
Abstraction-Levels (detail increases) Operational Perspective Architecture Modeling Allocate Functional Perspective Allocate Allocate Logical Perspective Realize Technical Perspective Realize Geometrical Perspective Figure 3.3: Matrix of abstraction levels and perspectives models according to abstraction levels and perspectives like in Figure 3.3. We identified five specific perspectives which are currently supported by the architecture meta-model: The operational perspective, the functional perspective, the logical perspective, the technical perspective, and the geometrical perspective. +subPackage Package SystemModel +owner 0..1 1..* +owner 0..1 0..* +abstractionLevel DeclarationZone 1 +topLevel +declarationZone 0..1 +owner Perspectiv eKind operational functional logical technical geometric +declared ReusableElement AbstractionLev el 0..1 +ownedPerspective Perspectiv e +successor 0..1 0..* +abstractionLevel 0..* 0..* +perspective 0..* SystemArtefact +root 0..1 + kind: PerspectiveKind Figure 3.4: Meta-model integration of the concept of Perspectives The combination of the perspectives at a certain abstraction level provides a specification of the whole architecture at the given level of detail. The entities and their interfaces defined in different perspectives do not need to be compatible to each other. For example, three interacting functions defined at the functional perspective may be modelled as two logical components. Elements of one perspective however can be allocated to elements of another perspective (cf. Section 4.4). Du to its similarity to Realize-trace links, the superordinate concept of Mapping has been defined, that is discussed in Section 3.4. A function for example, that is defined in the functional perspective, may be allocated to a logical component, which itself may be allocated to a hardware resource defined in the technical perspective. The meta-model provides a formal definition of Allocate-links, allowing to define simulation relations between linked elements, and to reason about consistency of the system design among different perspectives. 17/ 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: 3 The Architecture Meta-Model In Se
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?