Architecture Modeling - SPES 2020

More documents

Recommendations

Info

Architecture Modeling mapping relation to pins of the BehaviorBlock (for BehaviorBlocks and Pins refer to [50]). A mapping specifies correlations of observable behavior of components by a formal specification of how dynamics of InteractionPoints of one RichComponentProperty are projected on corresponding behavior of InteractionPoints of another RichComponentProperty. As the mapping relates component parts, the context of both RichComponentProperty needs to be described. Therefore the concept of instanceRefs is used, which has been inspired by the AUTOSAR and EAST-ADL meta-models. An InstanceRef defines a particular navigation within future M0 instance trees of M1 classifiers. The reason is that the concept of reusable RichComponents lead to a situation where a flat M1 model of hierarchical components specifies deep, tree-like M0 instances. That means when mapping parts of components on M1 level, one needs to describe navigation paths in order to uniquely identify the parts. The problem when dealing with reusable structural hierarchies and the concept of InstanceRefs is detailled described in [7]. 44/ 156
4 Steps in Component-Based Design The SPES architecture meta-model (SPESMM) intends to support development of complex systems involving a large number of different engineers. In such a process, it is essential to specify the roles and responsibilities of each engineer: who is responsible for ensuring what, and under which conditions. Only if this is ensured, integration problems in later design phases can successfully be identified and fixed. In SPESMM, first class citizens are components and their interfaces. Components may interact with each other and with the environment by means of their interfaces, thus forming a model of the intended system. The SPESMM supports the development process in that it allows to represent roles and responsibilities of engineers by corresponding concepts in the design architecture. For example, engineers are usually responsible for distinct parts of the design. Design artifacts have to be constructed, refined, and implemented in different perspectives and at different abstraction levels. The SPESMM allows to (formally) express responsibilities for components in form of contracts, which are an instance of the assume/guarantee specification style. If different engineers, responsible for certain design artifacts, have to integrate the respective parts of the design, contracts allow to define under which conditions this integration will be successful. The same holds for example, if different engineers are responsible for specification and implementation of certain components. SPESMM provides means to reason about under which conditions an implementation satisfies the corresponding specification. The underlying concepts of the SPESMM particularly allow to define proof obligations that have to be performed in order to ensure whether responsibilities defined for model and component interfaces are satisfied. In an early design step for example, functionality of the system may be identified, together with a set of requirements to be satisfied by those functions. When in a subsequent design phase decomposition of the system into logical components is performed, it should be explicated which logical components are responsible to guarantee which system functionality. If this is done ”the right way”, the SPESMM allows the application of tools that, if not performing proof obligations automatically, explicate which proof obligations have to be performed in order to ensure satisfaction of the identified function requirements. This section intends to provide an overview of those concepts related to establish a continuous design process, and to provide traceability of requirements and the corresponding relations between design artifacts. Typically, a design process along the SPESMM involves many different design steps: • Entry point is the operational perspective, where system boundaries are identified, and the relevant goals, or initial requirements, are defined. • The system is then decomposed into distinct functions provided by the system in order to achieve the goals. Functionality may be further refined into sub-functions in this phase. Furthermore, requirements are identified for the respective functions which are typically related to the initial goals and requirements. • Functionality is partitioned into logical components providing the intended functions, and 45/ 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 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: ComponentC Architecture Modeling pa
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 89 and 90: Architecture Modeling However this
Page 91 and 92: Architecture Modeling The considera
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:
Architecture Modeling Figure 5.24:
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?