Architecture Modeling - SPES 2020
Architecture Modeling - SPES 2020
Architecture Modeling - SPES 2020
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Architecture</strong> <strong>Modeling</strong><br />
Figure 5.8: Logical Perspective – System Level<br />
provides control signals to the respective actuators. For a valid decomposition, all input and<br />
output ports of the parent component (which is the BSCU here) have to be linked to their<br />
respective ports of the internal components.<br />
In this decomposition example, the subcomponent Command is annotated with a contract<br />
C1.1 which is here (not in general) the same as the contract C1 of its parent component. The<br />
proof obligation for decomposition is a virtual integration test as shown in Section 5.1.3.3 for<br />
allocation.<br />
Allocation To complete the modeling of one abstraction level, the components of one perspective<br />
have to be associated with components of another perspective. This link was introduced<br />
in Section 4.4.2 as the primitive design step named allocation. This concept is exemplified<br />
in Figure 5.11 for the logical perspective of the System Level, where the logical component<br />
MeterValveActuator is allocated to two components of the technical perspective namely<br />
the computing resource MeterValveControl and the actuator MeterValveActuator.<br />
For a valid allocate-link all ports of the source component have to be mapped to ports of<br />
the target component. In this example, meterControl is mapped to meterValve and<br />
meterValveStatus to valveStatus. In Figure 5.11 again contracts are annotated that<br />
already have been introduced in preceding figures and therefore are only referenced by their<br />
78/ 156