Specification of an Architecture Meta-Model - SPES 2020

More documents

Recommendations

Info

Specification of an Architecture Meta-Model The subclasses of ReusableElement are BehaviorBlock, VVTarget, Interconnection- Specification, PortSpecification, ValueFunction, FailureScope, Dimension, Unit, SystemArtefact, DataType, Constant, MappingBlock, Aspect, VVCategory, Entail, Mapping, Stakeholder, .Decompose, InformalAssertion, OperationalBlock, Derive, Satisfy and Refine. Generalizations: NamedElement Associations • declarationZone : DeclarationZone [0..1] The declaration zone that owns the reusable element. 2.1.4 System Design An embedded system is modeled along the development process. Such a development process has several steps. As depicted in Figure 2.5 a system model covering such a process therefore has several abstraction levels. In one abstraction level different kinds of model compositions can be created or regarded coming from other abstraction levels. Such model compositions belong to different perspectives such as operational, functional, logical, technical and geometrical. Models are created based on system artifacts such as requirements, rich components and VVCases. In one perspective there is one root system artifact denoting the entry element of the model of the perspective. For the model in one perspective several aspects can be regarded which refer to specific system artifacts. +subPackage Package SystemModel +owner 0..1 1..* +owner 0..1 0..* +abstractionLevel DeclarationZone 1 +topLevel AbstractionLev el +successor 0..1 +declarationZone 0..1 +owner 0..1 0..* +ownedPerspective +abstractionLevel 0..* 0..* +perspective SystemArtefact +root 0..1 Perspectiv e + kind: PerspectiveKind +declared ReusableElement +aspect 0..* Aspect Perspectiv eKind operational functional logical technical geometric Figure 2.5: System design elements. 0..* AbstractionLev elCategory +category 0..1 The evolution of an embedded system development process and related models is illustrated in Figure 2.6. The real system with the system under design is projected to 12/135
Specification of an Architecture Meta-Model a model world. In this model world different kinds of models are created and refined until finally the system can be built in the real world. These models evolve along three axes covering the abstraction levels of the process steps and the viewpoints. As a first axis there is an ordered set of abstraction levels. These abstraction levels generally start with the definition of very coarse models and end with very low level and detailed models. A transition from one abstraction level to another level is always a refinement of models. Models defined on a lower level of abstraction realize models of the next higher abstraction level. Several kinds of composed models can be regarded on one abstraction level which cover different perpectives of the system as a second axis of the model evolution. The models of the different perspectives are related to each other via allocation links. Furthermore, within the models several non-functional aspects are regarded which are covered by different artifacts of the models. The coverage of aspects in the models therefore provides a third axis of model evolution. 3. Dimension Viewpoints (Partial) Generation Model World Real World 1. Dimension Abstraction Levels Safety Interfaces S’ Projection S Viewpoint X Real- Time Figure 2.6: Embedded system design model evolution. 2. Dimension Perspectives The models that are created during such a development process can be covered by a SPESMM system model. The presence of requirements and VV cases is considered the whole time. They can be introduced in any step of the process and therefore be related 13/135
Page 1 and 2: Specification of an Architecture Me
Page 3 and 4: Contents 1 Introduction 1 1.1 Overv
Page 5 and 6: 1 Introduction This document specif
Page 11 and 12: 2 Specification of the SPES Meta-Mo
Page 13 and 14: Associations Specification of an Ar
Page 15: 2.1.3.1 DeclarationZone {abstract}
Page 23 and 24: 2.1.6 Constants Specification of an
Page 25 and 26: 2.1.8.1 Expression {abstract} Speci
Page 29 and 30: 2.1.10.2 Parameter Specification of
Page 33 and 34: Port Specification of an Architectu
Page 39 and 40: Generalizations: NavigableFeature A
Page 41 and 42: RichComponentProperty 0..1 Connecto
Page 43 and 44: Assosiations Specification of an Ar
Page 45 and 46: Flow + direction: FlowDirection + k
Page 47 and 48: Generalizations: NavigableFeature A
Page 51 and 52: Generalizations: Interconnection Ag
Page 53 and 54: EndSubstitution Port + isConjugated
Page 55 and 56: 2.1.19.2 ExtensionAttribute Specifi
Page 57 and 58: 2.2.1.1 FunctionCall Specification
Page 59 and 60: 2.2.2.1 Initializer Specification o
Page 61 and 62: RichComponent Specification of an A
Page 63 and 64: «isOfType» +type Specification of
Page 65 and 66: Generalizations: BehaviorBlock Aggr
Page 67 and 68:
Specification of an Architecture Me
Page 69 and 70:
Page 71 and 72:
2.2.7.3 ServicePin Specification of
Page 73 and 74:
Associations Specification of an Ar
Page 75 and 76:
Page 77 and 78:
2.2.9 Component Mapping Specificati
Page 79 and 80:
Page 81 and 82:
2.2.9.6 MappingBlock Specification
Page 83 and 84:
Page 85 and 86:
MappingLink «instanceRef» +flowPi
Page 87 and 88:
2.2.9.17 PortMapping Port Specifica
Page 89 and 90:
Page 91 and 92:
2.3.1.5 ProcessRequirement Specific
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
EnumerationLiterals Specification o
Page 101 and 102:
2.4.1.6 VVTarget Specification of a
Page 103 and 104:
Page 105 and 106:
Generalizations: VVProcedure Attrib
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Operations Specification of an Arch
Page 113 and 114:
Page 115 and 116:
2.6.1.4 Bus Specification of an Arc
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
EnumerationLiterals Specification o
Page 123 and 124:
2.6.2.5 CommunicationResource Speci
Page 125 and 126:
Attributes Specification of an Arch
Page 127 and 128:
Page 129 and 130:
2.6.2.19 SchedulerPortSpec Specific
Page 131 and 132:
Aggregations Specification of an Ar
Page 133 and 134:
Attributes Specification of an Arch
Page 135 and 136:
3 Conclusion In this document a met
Page 137 and 138:
Page 139:
show all

Specification of an Architecture Meta-Model - SPES 2020

Create successful ePaper yourself

Delete template?

Save as template?