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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

11.4 Essential <strong>Specification</strong> Modelling 361<br />

Object<br />

Class<br />

Diagrams<br />

Initial Requirements Description<br />

Message Flow Diagrams<br />

Unified Model<br />

(POOSL)<br />

Requirements Catalogue<br />

Instance<br />

Structure<br />

Diagrams<br />

Arch/<br />

Impl.<br />

Structure<br />

Diagrams<br />

Figure 11.17: Development <strong>of</strong> Models in the Course <strong>of</strong> Time<br />

11.4.7.1 Design <strong>of</strong> a Channel Structure<br />

An ISD is a rather abstract representation <strong>of</strong> a system. Figure 11.18 shows an ISD.<br />

An ISD shows clusters, objects, terminators, channels and channel names. During the<br />

development <strong>of</strong> a system model a designer usually designs Message Flow Diagrams<br />

without immediately considering channel structures. This is necessary to get an initial<br />

model. Subsequently however it is necessary to relate flows to channels. A part <strong>of</strong><br />

a channel structure can usually be derived almost automatically from message flows.<br />

Another part must be designed carefully.<br />

Every message flow between process objects, clusters or terminators needs to be mapped<br />

onto a channel. A number <strong>of</strong> flows between a pair <strong>of</strong> instances (<strong>of</strong> process objects,clusters<br />

or terminators) can be mapped in principle on one channel between that pair. Therefore<br />

an automatic approach can be followed to assign channels between pairs <strong>of</strong> instances<br />

such that all flows can be mapped. An automatic approach results in channels that<br />

connect pairs <strong>of</strong> instances.<br />

This basic approach <strong>of</strong> pair-wise channels is only the simple part <strong>of</strong> the ISD modelling.<br />

ISDs are used to perform considered channel design, and to verify previous modelling<br />

activities. We already stated that the structure that has been designed in the Architecture<br />

Structure Diagrams must be consistently incorporated into Message Flow Diagrams.<br />

ISDs let us verify this because both types <strong>of</strong> diagrams should be used as input. The<br />

structure <strong>of</strong> ISDs is in general based on the basic structure <strong>of</strong> the Message Flow Diagrams<br />

<strong>of</strong> a system. It must be verified whether this structure is consistent with the Architecture<br />

Structure Diagrams <strong>of</strong> the system. Structures such as backbones or other shared channel<br />

time <strong>of</strong> the development proces

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

Saved successfully!

Ooh no, something went wrong!