Architecture Modeling - SPES 2020

RichComponent
Architecture Modeling
Satisfy Refine
1..* +component
+refinedBy 1..* 1 +refinedReq
Requirement
+ rationale: String [0..*]
+satisfies
1..*
SystemRequirement
+entailed
1
+entailing
Figure 3.28: Meta-model integration of the tracing of requirements and contracts
ments have been derived from initial product requirements. The meta-model supports tracability
by different trace-links between Requirements and RichComponents (see Figure 3.28).
The Satisfy concept links SystemRequirements to RichComponents, indicating
the components that have to satisfy the aspect specifications defined by the
SystemRequirements. The satisfaction relation is discussed detailed in Section 4.3. Note
that RichComponents are linked to SystemRequirements and do not own them. This
allows both of them to exist independently from each other, i. e. from the meta-model point of
view it is not necessary to first create a RichComponent along with its syntactical interface
in order to specify a SystemRequirement (contract). Indeed this loose coupling makes it
possible to first specify a contract and to define a RichComponent at a later time and link it
to that contract.
The Refine concept links Requirements to other Requirements. The motivation is
to express that a requirement referenced in the role refinedReq has been refined by a set of
more detailed requirements referenced in the role refinedBy. One use-case for this trace-link
is to document requirement formalizations. How requirements can be formalized is discussed
in Section 4.1.
The Entail concept links SystemRequirements to other SystemRequirements.
The composition of the contracts referenced in the role entailing establish a refinement
of the contract referenced in the role entailed. The role of Entail-trace link in design
steps carried out during the development process is discussed in Section 4.2. In this document
we consider a formal interpretation of contracts linked by the Entail concept and call it a
refinement or entailment of contracts (see Section 6.3.2).
3.3.1.4 Requirement Specification Language
In order to ease the specification of contracts we provide a pattern-based requirement specification
language (RSL) (see Section 6.1), that can be used to specify the aspects of a
RichComponent or specializations thereof.
The RSL is basically a set of textual patterns, that can be instatiated in order to specify an
Assertion. For example the syntax of the pattern F1 is defined as:
1..*
Entail
39/ 156