Architecture Modeling - SPES 2020

Architecture Modeling
patterns, capitalize on sequence charts. Within the project SPES, we advocate the use of the
pattern based requirement specification language RSL, see Section 6.1. The additional effort in
providing a degree of formalization is typically well invested due to the additional benefits we
have outlined above, such as testing consistency of requirements, identifying complex integration
errors early through virtual integration testing, boosting re-use though component based
design, and allowing cross layer design optimizations based on performing platform based design.
The key point we raise, is that this formalization can be done incrementally and on a
case by case basis. Thus, there is a clear migration strategy from using contracts informally,
to incorporating domain ontologies, to gradually enriching the number of covered viewpoints,
and to gradually increase the degree of formalization. No matter in which order such steps are
taken, each of these comes with significant potentials for process improvements.
In spite of, or rather: due to their simplicity, the range of applicability of contracts in embedded
systems design is overwhelming. There is almost no phase in V-based development
processes, where today´s engineering practices would not benefit from the boost of process
improvements offered through contract-based design: the already extensive compilation of design
methods discussed in this section is by no means complete. Additional use-cases relate to
the usage of contracts in model-based testing, in automatic code-generation, in registering new
players in system-of-system designs, etc. This combination of simplicity and extremely high
methodological value are in our view a strong indicator for the identification of a fundamental
design principle, already implicitly underlying many of today´s engineering practices, but so
far a treasure hidden.
107/ 156