Architecture Modeling - SPES 2020

More documents

Recommendations

Info

Architecture Modeling or their implementation, in terms of an executable model or even code, is deliberately left open in the meta model, in order to provide flexibility in using aspect-specific modelling formalisms. The formal foundation assumes, that – whatever modelling method is used – the capability to associate with such models a what is often called trace-based semantics, which, for each interface object, defines for each point in time the value of such interface objects. Implementations are allowed to be non-deterministic, hence yielding sets of such traces as their formal representation, but would typically be input-deterministic and responsive, i. e. yield for each valuation of an interface object under control of the components environment a uniquely determined valuation of interface objects under control of the component. Note that in particular modelling approaches such as AutoFocus, which come with a formal semantics, meet this requirement. When using commercial-off-the-shelf (COTS) tools for modelling the realization of a component, a strictly formal development process requires the ability to verify compliance of such models against contracts, requiring a formal definition of their semantics. Such formal semantics have been given for a plurality of COTS tools [17, 19, 3]. Less formalized development processes can use test cases automatically derivable from contract specifications to demonstrate compliance of component realizations and specifications. Within the generic landscape characterized by perspectives and abstraction layers, the emphasis is on supporting the major phases of system development, from product requirements to a specification of the technical architecture of the system. In particular, the transition to the geometric perspective, which is served by tools like CATIA 1 or the Siemens PLM suite 2 , is not elaborated in the current version of this document. In other project contexts, the role of contracts as an interface between the geometric and the technical perspective has been demonstrated, such as the impact of physical allocation decisions and routing of cables on the safety case [4] has already been demonstrated. This document is organized as follows. A quick tour in Section 2 elaborates on an informal level the key concepts of perspectives, abstraction layers and Heteregenous Rich Components, by way of example, providing first indications as to their possible role in design processes. This is complemented by a detailed specification on the conceptual level of the architecture meta-model. The ensuing section adds more detail on the syntax of the meta-model and how design artifacts are to be represented. It is thus technical in nature and could be skipped on first reading. Section 4 presents primitive steps in component-based design. It introduces on an informal level the main concepts underlying contract-based design — contract syntax and semantics, properties, their usage in specification, verification and virtual integration testing — and how they are applied to perform the design task from requirement definition to deployment. While this section provides a bottom-up view of design, Section 5 on using the architecture meta-model adds the top-down perspective, painting the broad picture of applying contract-based design in the industrial context. In fact, readers with an industrial background may prefer to read this section after the quick tour before delving into the more detailed sections 3 and 4. The annex, finally, provides the formal underpinning of this approach. In particular, it provides a reference manual for the proposed requirement specification language, a formal semantics of contracts, a formal semantics of HRC components, and the formal foundations for primitive design steps in component based design. This document thus provides guidance in using the release of the architecture meta-model, 1 http://www.3ds.com/de/products/catia 2 http://www.plm.automation.siemens.com/en us/products/teamcenter/ , http://www.3ds.com/plm 2/ 156
Architecture Modeling allowing to model applications using the concepts of the meta-model, as well as building component specifications with contracts. OFFIS is offering end users to support such modelling activities. 3/ 156
Page 1 and 2: Architecture Modeling ∗ Andreas B
Page 3 and 4: Contents 1 Introduction 1 2 Quick-T
Page 5: 1 Introduction This document propos
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 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?