Architecture Modeling - SPES 2020

More documents

Recommendations

Info

Architecture Modeling Figure 5.13: Realize Links for BSCU (Iteration from System Level to Device Level) Such a reaction is observed by the output of the metervalve actuator i. e. when the signal meterValveStatus has been updated (upd). On the right hand side of the figure the same snapshot at the same abstraction level is shown for the technical perspective. In this perspective we differentiate between the driver unit for the actuator (MeterValveControl) and the actuator itself (MeterValveActuator) as well as the communication channel (Channel) between them. Furthermore, technical issues are considered as the environmental temperatures TEMP1 and TEMP2 of the actuator and the channel where the respective components are specified to work correctly. The temperatures might be provided by some sensor components that are not shown here. The logical meter-valve component is allocated to the three depicted technical components while the allocate-link is defined by a mapping block that maps the ports of one perspective to ports of the other perspective. The mapping links are depicted in red dotted lines. In this case, 82/ 156
Architecture Modeling Figure 5.14: Example for proving Allocation by Virtual Integration Test the ports meterControl and meterValveStatus of the logical perspective are mapped to the ports meterValve and valveStatus of the technical perspective. The components of the technical perspective have a satisfy-link to the contracts C2.1-T1, C2.1-T2, C2.1-T3 and C2.1.2-T3 where C2.1-T1 is relevant for MeterValveControl, C2.1-T2 for Channel and both C2.1-T3 and C2.1.2-T3 for MeterValveActuator. The composition of these four contracts has an entailment link to the contract C2.1 of the logical perspective that has to be ensured. To prove an allocation-link a virtual integration test may be performed as introduced in Section 4.2 consisting of the two steps of assuring compatibility and refinement. Compatibility For the scenario from Figure 5.14, we start with the validation of the compatibility of the three neighbouring components in the technical perspective or, to be more precise, the compatibility of their annotated contracts. For this, we have to analyze their strong assumptions and guarantees. Note, that the weak asspumptions do not constrain the compatibility of systems. In this example, the second part of the guarantee of C2.1-T1 is compatible to the second part of the strong assumption of C2.1-T2. The same holds for C2.1-T2 and C2.1-T3. Further, in this example the assumption parts about the temperature do not influence the validity of the composition of these three components because they are parts of interfaces to other components. Refinement As a further step, the entailment-link between the contract on the logical perspective and the composition of the four contracts on the technical perspective has to be proven to be a valid refinement. Checking the refinement for this example results in a falsification, as the strong assumptions of the contracts C2.1-T2 and C2.1-T3 are stronger than the parent contract C2.1. To be more precise, the assumptions about the temperature cannot be assured by C2.1. To solve this situation there are at least two possible scenarios. One solution would 83/ 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 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: Architecture Modeling Figure 5.12:
Page 89 and 90: Architecture Modeling However this
Page 91 and 92: Architecture Modeling The considera
Page 93 and 94: Architecture Modeling Figure 5.18:
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 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?