Specification of an Architecture Meta-Model - SPES 2020

More documents

Recommendations

Info

Generalizations: RichComponent 2.1.12.3 Function Specification of an Architecture Meta-Model A function is a rich component that denotes a function in the functional perspective that shall be fulfilled by the system. Generalizations: RichComponent 2.1.12.4 LogicalComponent A logical component is a rich component that denotes a logical system component in the logical perspective. Generalizations: RichComponent 2.1.12.5 System A system is a rich component that denotes a system under design in the logical perspective. A system may be decomposed by instances of logical components. Generalizations: RichComponent 2.1.12.6 EnvironmentComponent An environment component is a rich component that denotes a component of the environment, such as an actor, that interacts with the system(s) under design in the logical perspective. Generalizations: RichComponent 2.1.12.7 TechnicalComponent A logical component is a rich component that denotes a technical system component in the technical perspective. The TechnicalComponent is used to describe functional hardware. The TechnicalComponent is a structural entity that is part of an electrical architecture. Through its ports it can be connected to other electrical hardware components. Its sub-meta-classes add more information about which hardware component is represented. The TechnicalComponent is only to be used in case the designer does not know more specific details about the hardware to represent (the sub-meta-classes should be the primarily used hardware modeling artifacts). Generalizations: RichComponent 32/135
Specification of an Architecture Meta-Model 2.1.13 RichComponents and Parts The definition of component parts provides a means for arbitrary hierarchies of component composition. As depicted in Figure 2.18 RichComponentProperties are parts of RichComponents and as well typed by respective RichComponents. Thus composed components can be reused in another component context by being assigned to a component part as a type. Furthermore, a RichComponentProperty can be assigned a size which denotes its multiplicity and expresses that a component owns a RichComponentProperty typed by one RichComponent several times. RichComponent +type +component 2.1.13.1 RichComponentProperty 1 1 «isOfType» +part 0..* RichComponentProperty Figure 2.18: Rich Component Property. A rich component property specifies a part/sub-component of a rich component. A rich component property is both a navigable feature, and a multiplicity element. Generalizations: NavigableFeature, MultiplicityElement Associations • type : RichComponent [1] The type of the rich component property. • component : RichComponent [1] The rich component that owns the rich component property as a part. 2.1.14 Componenets and Ports The concept of ports provides a means of interface specification for components. As depicted in Figure 2.19 a ports type can be specified. A port can be referenced from expressions as well. Furthermore a port can have asize which denotes its multiplicity and expresses that a component owns a port of one type several times. 2.1.14.1 Port A port is owned by a rich component. It aggregates a set of interaction points of the owning rich component. A port is typed by a port specification, which specifies the set of interaction points in terms of flows or services. A port is both a navigable feature, and a multiplicity element. 33/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 and 16: 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 35: Specification of an Architecture Me
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 71 and 72: 2.2.7.3 ServicePin Specification of
Page 73 and 74: Associations Specification of an Ar
Page 77 and 78: 2.2.9 Component Mapping Specificati
Page 81 and 82: 2.2.9.6 MappingBlock Specification
Page 85 and 86: MappingLink «instanceRef» +flowPi
Page 87 and 88:
2.2.9.17 PortMapping Port Specifica
Page 89 and 90:
Specification of an Architecture Me
Page 91 and 92:
2.3.1.5 ProcessRequirement Specific
Page 93 and 94:
Page 95 and 96:
Associations Specification of an Ar
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?