Architecture Modeling - SPES 2020

Architecture Modeling
Shape that describes its sphere of effect. GeometricInstallations being impacted by
a particular risk are listed as a result of a particular risk analysis.
3.3 Heterogeneous Rich Components
The concepts of Heterogeneous Rich Components (HRC) and contracts both originate from the
European SPEEDS project. Both are key concepts of the architecture meta-model.
3.3.1 Component Model
The component concept of HRC is compatible to many other modeling languages that have a
component concept. For example the meta-model of AUTOSAR defines a set of templates, one
of which is the SoftwareComponentTemplate [8] that establishes the concept of a SoftwareComponent.
The interface concept in terms of ports and their types is more refined in AUTOSAR
than in HRC, but is still compatible. SysML also provides a component concept (referred to as
blocks) [39]. In fact, alignment with SysML was an important goal when defining the component
and interface concept of the architecture meta-model.
Port
+ isConjugated: Boolean
Variable
+port
0..*
0..*
+attribute
+component
Aspect
RichComponent
SystemRequirement +satisfies
Satisfy
1
+component
0..1
1..*
+component 1..*
+aspect
0..1
+component
0..1
+behavior
0..*
Behav iorImplementation
Behavior
Figure 3.23: Meta-model integration of the concept of components
BlockOccurrence
A component is a module with well defined interfaces and is the basic entity of any model.
Resuability of components is an inherent property of the proposed architecture modeling approach.
Note that the concept of components proposed here is not restricted to software components.
It is rather an approach of how architecture modeling should be done, fostering reuse
of models for different developed products as well as enabling computer aided verification of
integration of models. So a component can model a reusable software module, a specific sensor
measuring temperature or a computing device (e. g. an ECU or IMA-module) hosting software
applications.
Figure 3.23 depicts how the component concept is embedded in the architecture meta-model.
A RichComponent optionally encapsulates a realization of a certain aspect, which is aggregated
in the role of behavior. The association to Aspect from Behavior provides means
to categorize the realization in terms of the addressed aspects. Parts of the behavior realizations
can be exposed at the Ports of the component. The set of all ports is considered the syntactic
interface of the RichComponent. The optional realization of an aspect is complemented by
its specification. A specification of an aspect can be expressed by means of contracts.
35/ 156