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.

5.9 Transformations 141<br />

The modification <strong>of</strong> the clustering over various abstraction levels appears to be an<br />

important type <strong>of</strong> transformation. In comparison to modifications <strong>of</strong> process objects,<br />

modifications <strong>of</strong> clusters have a weak influence on the system behaviour. This observation<br />

enabled the definition <strong>of</strong> a set <strong>of</strong> behaviour-preserving transformations on clusters.<br />

They are described in Chapter 10. In general, the word transformation means behaviourpreserving<br />

transformation in this thesis.<br />

5.9.2 Purpose <strong>of</strong> Transformations<br />

Transformations enable addition and removal <strong>of</strong> clusters as well as channels, while preserving<br />

behaviour. They indirectly enable the formalisation <strong>of</strong> boundaries into a model,<br />

because they can modify clusters. Transformations help to make an Object Instance<br />

Model consistent with an Architecture or Implementation Structure Model. Especially<br />

the modification <strong>of</strong> channels is important. Initially, channels are defined more or less<br />

’automatically’. If two process objects exchange a message, they need at least one channel.<br />

If process objects exchange several types <strong>of</strong> messages they are in principle mapped<br />

onto one channel. Adding a second channel, or sharing a channel must be designed<br />

explicitly. It is a deviation <strong>of</strong> the ’automatic channel approach’. Shared channel structures<br />

such as backbones, star or ring topologies are typically designed in architecture<br />

and implementation structures. Figure 5.13 shows an Architecture Structure Diagram<br />

A<br />

DISTR DISTR<br />

B<br />

Architecture Structure Model<br />

( Distibuted topology)<br />

DISTR DISTR DISTR<br />

DISTR<br />

Figure 5.13: Distribution Transformation<br />

C

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

Saved successfully!

Ooh no, something went wrong!