Specification of an Architecture Meta-Model - SPES 2020

More documents

Recommendations

Info

2.1.5.2 DataType {abstract} Specification of an Architecture Meta-Model Type DataType ExtensionType Figure 2.7: Types. A data type denotes a set of data values. DataType is an abstract meta-class and has four subclasses: Array, Record, PrimitiveType, and Enumeration. See Section 2.5 for details on data types. Generalizations: Type Operations • isBoolean(): Boolean Overridden in subclasses. context PrimitiveType::isBoolean(): Boolean post: result = (self .kind = PrimitiveTypeKind::boolean) • isReal(): Boolean Overridden in subclasses. Specified as for isBoolean() above. • isInteger(): Boolean Overridden in subclasses. Specified as for isBoolean() above. • isString(): Boolean Overridden in subclasses. Specified as for isBoolean() above. • isVoid(): Boolean Overridden in subclasses. Specified as for isBoolean() above. • isNumber(): Boolean Returns true if the type in question is intended to be used with arithmetic operators. context DataType::isNumber(): Boolean post: result = (self .isInteger() or self .isReal()) • conformsTo(DataType): Boolean Specifies whether the types denoted by self and other are compatible. 18/135
2.1.6 Constants Specification of an Architecture Meta-Model As depicted in Figure 2.8 Constant values such as a natural number are reusable elements, which can be referenced by Expressions. These entities, also known as rigid variables, could be shared across multiple HRC models by packaging them into libraries. 2.1.6.1 Constant DataType +type 1 +value Constant Expression Figure 2.8: Constants. A Constant inherits from NavigableFeature and ReusableElement. A Constant is associated to exactly one DataType by its type and owns exactly one value, which is a statically computable Expression. Generalizations: NavigableFeature, ReusableElement Aggregations • value : Expression [1] The value of the constant. Associations • type : DataType [1] The type of the constant. Constraints Constants are subject to the following constraints: 1. The value of a Constant must be statically computable. 2.1.7 Textual Elements Some elements contain textual descriptions. Such a textual description can be optional but there are special opaque elements which are only represented by their contained text. Figure 2.9 gives an overview over all textually representable elements. 19/135 1
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 21: Specification of an Architecture Me
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 71 and 72: 2.2.7.3 ServicePin Specification of
Page 73 and 74:
Associations Specification of an Ar
Page 75 and 76:
Specification of an Architecture Me
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?