Architecture Modeling - SPES 2020

More documents

Recommendations

Info

Architecture Modeling ServiceBinding and compatibility of Services There are two case distinctions for binding Services by means of ServiceBinding. If services of different ports shall be bound establishing an assembly connection like illustrated in Figure 3.30a, then the directions of both services need to be complementary (required for provided and vice versa). In the case of delegation connections like depicted in Figure 3.30b, the directions must be the same. Further the services must be compatible. Two services are compatible if their signatures are the same. That means they associate the same DataType as returnType and have identical Parameters with regard to their name and types. Connector and compatibility of Ports When defining assembly connections or delegation connections between Ports by means of the concept Connector, all InteractionPoints of the Ports defined by their corresponding PortSpecification are bound. Which pairs of InteractionPoints are bound is determined by name. All pairs of InteractionPoints (Flows or Services) must be compatible as described above. FlowDirection in out bidirectional FlowKind discrete continuous event Serv iceDirection provided required Parameter +part 0..* RichComponentProperty PortSpecification 1 +component +type 1 +portSpecification +formalParameter +service 0..* 0..1 1 «isOfType» +type 1 «isOfType» +interactionPoint RichComponent Port + isConjugated: Boolean 0..* Serv ice InteractionPoint + direction: ServiceDirection +service 1..* «isOfType» +component +port «isOfType» 1 0..* +port 1..* +component 1 Connector «instanceRef» +interconnection Flow + direction: FlowDirection + kind: FlowKind +returnType 1 «isOfType» +type 1 DataType +type 1 0..* Interconnection FlowBinding Serv iceBinding «instanceRef» Figure 3.31: Meta-model integration of the composition concepts +flow 1..* «instanceRef» Composition of Contracts: If a composition of components is specified by means of the described concepts, that composition is correct with regard to the syntactical interfaces of the parts and the composition. However it must also be ensured, that the contracts specified for the components typing the parts are compatible and are a valid refinement of the contracts of the composition. Figure 3.32 illustrates that relation. The components ComponentA and ComponentB have contracts C1 resp. C2. They are used as parts in the context of the composition ComponentC, which in turn has a contract C12. The contracts are linked to the components by means of the Satisfy-trace link described in 3.3.1.3. When constructing a composition, the relationship of the contracts associated with the concerned components is specified by means of the Entail-trace link. 42/ 156
ComponentC Architecture Modeling part1:ComponentA part2:ComponentB ComponentB C2 «Entail» C12 «Entail» ComponentA Figure 3.32: Composition of components and contracts Note that this link only declares the proof obligations which have to carried out in order to ensure a sound (de-)composition. Actually one needs to verify, that the entailing contracts are compatible, meaning the strong assumption of a contract must not be violated by another component, which is connected to it. If the entailing contracts are compatible, it must be checked if the entailing contracts are indeed a refinement of the entailed contract. Related to the example sketched in Figure 3.32, Compatibility of C1 and C2 needs to be verified and the pair {C1,C2} must be a refinement of C12. We call such proof obligations Virtual Integration Testing, which is discussed in Section 4.2. 3.4 Mapping Component Parts In Section 3.1 the Realize-trace link has been introduced, which allows to trace component realizations when switching abstraction levels. In Section 3.2 the Allocate-trace link has been introduced, which allows to trace component allocations between different perspectives. Both concepts are similar and therefore the superordinate concept of Mapping has been defined. +type 1 RichComponent +component 1 «isOfType» +part 0..* +mappedTo RichComponentProperty 1 «instanceRef» +mapped 1 «instanceRef» TextuallyRepresentedElement + textualRepresentation: String Allocate Mapping 0..1 Realize +mapping +formal 1 MappingBlock +mappingBlock 0..1 +behavior 1 BlockOccurrence 1 Serv ice C1 + direction: ServiceDirection +mappingBlock +mappingLink «isOfType» +service 0..1 «instanceRef» 0..* +type 1 Flow + direction: FlowDirection + kind: FlowKind MappingLink BehaviorBlock Figure 3.33: Meta-model integration of the mapping concepts +flow 0..1 «instanceRef» Figure 3.33 shows how a Mapping relates two parts of components (RichComponentProperty) to each other. Further a mapping is formalized by means of a MappingBlock, that has a BlockOccurrence, which is typed by a BehaviorBlock. The concept of MappingLinks link flows or services of a component taking part in the 43/ 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: MultiplicityElement +part 0..* Rich
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 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?