23.08.2013 Views

Specification of Reactive Hardware/Software Systems - Electronic ...

Specification of Reactive Hardware/Software Systems - Electronic ...

Specification of Reactive Hardware/Software Systems - Electronic ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

120 Concepts for the Integration <strong>of</strong> <strong>Specification</strong> and Design<br />

Module G<br />

Module A Module B Module C Module D<br />

Figure 5.1: Architecture with Bus Structure<br />

Module G<br />

Module A Module B Module C Module D<br />

Figure 5.2: Architecture with Star Structure<br />

Considerations about the ’distribution <strong>of</strong> intelligence’ (centralised / decentralised) may<br />

have a major influence on the communication between the collaborating processes. An<br />

Architecture Structure Diagram such as Figure 5.1 can be used to open a discussion<br />

about the distribution issue. A distribution <strong>of</strong> intelligence means that relatively simple<br />

messages from a central module can cause complex actions <strong>of</strong> decentralised modules.<br />

An elegant solution for such a model is defining a dedicated command language for the<br />

communication on the channel. Another solution is the selection <strong>of</strong> an (standardised)<br />

industrial network solution. Both solutions imply that some conceptual solution is chosen.<br />

This shows that architecture design is related to conceptual solution selection. It will be<br />

clear that such choices have a strong influence on the modelling <strong>of</strong> the communication<br />

between collaborating objects and clusters. This example shows again that functional<br />

behaviour and architecture are intertwined, and must be performed concurrently to<br />

prevent costly iterations. This is confirmed by [SB82].<br />

5.2.5 Mapping<br />

One <strong>of</strong> the key issues in SHE is the mapping <strong>of</strong> architecture design upon objects, clusters<br />

and channels. Architecture must be formalised into a behaviour specification. We <strong>of</strong>fer<br />

the concept <strong>of</strong> boundaries (to be introduced in Section 5.8) as an intermediate to perform

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!