Architecture Modeling - SPES 2020

Architecture Modeling
Technical Perspective The technical perspective describes the electrical and electronical architecture,
the software architecture and the mechanical structure of the system under
development(↑). Modeling elements are for example electronic control units, bus
systems, tasks, and hydraulic systems. By allocating components(↑) of the logical
perspective(↑) to the technical perspective a software-hardware partitioning is realized.
Geometrical Perspective On this perspective the physical layout of the system under
development(↑) is modeled. This includes (amongst others) models describing the location
of control units, and the cable layout.
Refinement Refinement defines the derivation of a concrete desciption of the design item from
an abstract description. The derivation thereby conserves the characteristics of the abstract
description. In the case of a contract specification(↑), the derived component(↑)
has to fulfill all contracts of the more abstract component.
Dominance Dominance is a necessary but not sufficient condition to check a refinement(↑), in
that dominance implies refinement.
Mapping A mapping is a concept of the SPESMM which relates a set of component parts(↑)
to each other. In particular, it descibes the projection of interfaces of a set of component
parts to component parts of different perspectives(↑) or abstraction layers(↑). There are
two types of mappings: realization(↑) and allocation(↑).
Realization An realization describes a mapping(↑) between component parts(↑) of different
abstraction layers(↑).
Allocation (Allokation) An allocation describes a mapping(↑) between component parts(↑) of
different perspectives(↑).
Satisfaction Satisfaction is the proof obligation stating that an implementation of a desing
item must adhere to its specification. In context of SPES, this means that an aspect
realization(↑) of a component(↑) has to fulfill its contracts(↑), i.e., if its behavior does
not violate its specified one. That way, the behavior of a component defined by its aspect
realization can be seen as a refinement(↑).
Compatibility Compatibility reflects the distinction of responsibilities: The strong
assumptions(↑) about the environment of a component must not be violated by another
component that is connected to this component.
Virtual Integration Test (VIT) A virtual integration test verifies the correctness of a design
item, which is composed by a set of interconnected sub-design items. In particular, to
perform a virtual integration test in the context of SPES, one has to show on the one hand
the compatibility(↑) of the interconnected sub-components. On the other hand, one has to
check, whether the contract specifications of the composition of all sub-conponents refine
the contract specification of the composed component.
152/ 156