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.

5.10 Formalisation 143<br />

Level<br />

1<br />

Level<br />

2<br />

Level<br />

3<br />

Figure 5.15: Hierarchical Levels 2<br />

to level 3. Addition <strong>of</strong> a cluster on level 1, can be considered a horizontal refinement.<br />

This transformation causes also changes on level 3. There appear to be entanglements<br />

<strong>of</strong> the various forms <strong>of</strong> refinement. Both removal and addition affects the next lower<br />

level. This is only a simple example. In a hierarchy with more levels, more levels will<br />

be affected. The complete hierarchical tree <strong>of</strong> clusters and objects in the cluster to be<br />

removed or added will move. All these transformations are supported as behaviour<br />

preserving transformations, that are proven correct.<br />

5.10 Formalisation<br />

This chapter paid a lot <strong>of</strong> attention to hierarchical structuring, and structure transformations.<br />

However, the properties, that are prescribed by the definition <strong>of</strong> boundaries,<br />

must also affect the behaviour description <strong>of</strong> process objects. Figure 5.16 visualises the<br />

effort that must be done. After a thorough analysis, using mainly graphical representations,<br />

a POOSL description <strong>of</strong> all classes must be written. This description integrates<br />

many properties <strong>of</strong> the overall model into a formal Unified Model. On the one hand the<br />

derivation <strong>of</strong> this model must be postponed until the graphical models become stable<br />

and mature, on the other hand POOSL exercises give a lot <strong>of</strong> insight. Postponement<br />

can prevent costly iterations <strong>of</strong> POOSL descriptions. However missing the insight that<br />

comes with modelling attempts may cause iterations. Adequate guidelines must be<br />

derived from future specification projects. In practice, it appears that there are many

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

Saved successfully!

Ooh no, something went wrong!