Specification of an Architecture Meta-Model - SPES 2020
Specification of an Architecture Meta-Model - SPES 2020
Specification of an Architecture Meta-Model - SPES 2020
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Specification</strong> <strong>of</strong> <strong>an</strong> <strong>Architecture</strong> <strong>Meta</strong>-<strong>Model</strong><br />
MultiplicityElement<br />
RichComponentProperty Port<br />
+ isConjugated: Boole<strong>an</strong><br />
Figure 2.15: Multiplicities.<br />
+size<br />
1<br />
Expression<br />
Constraints Multiplicity elements are subject to the following constraints:<br />
1. The size expression must be <strong>of</strong> Integer type:<br />
context MultiplicityElement inv sizeIsInteger:<br />
self .size.type().isInteger()<br />
2. The size expression must be statically computable:<br />
context MultiplicityElement inv sizeIsStaticallyComputable:<br />
self .size.isStaticallyComputable()<br />
2.1.12 Rich Components<br />
In this section rich components <strong>an</strong>d their dependencies are presented. As depicted in<br />
Figure 2.16 a component reflects structural modeling but also behavioral aspects which<br />
are shown in Figure 2.17.<br />
Figure 2.17 shows component behavior concepts like component initialization, service<br />
implementations as well as behavior descriptions with behavior links that are<br />
described in Section 2.2.8 <strong>an</strong>d component operation concepts like failure conditions as<br />
described in Section 2.4.<br />
2.1.12.1 RichComponent<br />
A rich component describes a type <strong>of</strong> structural unit (by contrast to <strong>an</strong> HRC block<br />
that denotes a type <strong>of</strong> behavior unit) that share the same characterization <strong>of</strong> features,<br />
constraints, <strong>an</strong>d dynamics.<br />
A rich component is both, a reusable element <strong>an</strong>d a templatable element. A rich<br />
component in the role <strong>of</strong> template realization implicitly specifies the features <strong>an</strong>d dynamics<br />
defined by its template, in which all template parameters are replaced by the<br />
actual ones.<br />
28/135