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.4 Essential Model and Extended Model 123<br />

multidisciplinary approach and 6.5 about scenarios). All these views can be used for<br />

refining the specification with details belonging to the specific view, and integrating the<br />

relevant details into the behaviour model.<br />

5.4 Essential Model and Extended Model<br />

5.4.1 Essence and Implementation<br />

The separation <strong>of</strong> essence and implementation reflects the distinction between ’problem’<br />

and ’solution’. SASD methods [WM85, HP88] distinguish between respectively Essential<br />

& Implementation Models and Requirements & Architecture Models. Figure 5.3<br />

shows two approaches towards the modelling process. An essential model describes<br />

Essence<br />

Implementation<br />

Essence Implementation<br />

Sequential Approach Parallel Approach<br />

Figure 5.3: Sequential versus Parallel Modelling<br />

the requirements <strong>of</strong> a system in an implementation independent fashion. In a sequential<br />

approach, an essential model is developed before an implementation model. Such an<br />

approach leads to unnecessary development costs, caused by unnecessary iterations<br />

(see Chapter 2). This is especially true for hardware/s<strong>of</strong>tware systems, because <strong>of</strong> the<br />

important role <strong>of</strong> various forms <strong>of</strong> ’implementation’ structure.<br />

In the parallel approach both models are developed concurrently. Ward and Mellor<br />

give two related heuristics concerning essence and implementation [WM85]. The first is<br />

already mentioned: separate essential model and implementation model. The second is:<br />

minimise the essential model distortion. This distortion can occur when the contents <strong>of</strong><br />

the essential model is mapped into an implementation environment. The implementation<br />

structure in the implementation model will usually be inconsistent with an essential<br />

model, when both models are developed independently. The essential model must be<br />

distorted (by changes) to achieve consistency <strong>of</strong> both models afterwards. The best way<br />

to minimise distortion is to prevent it by developing both essential model and implementation<br />

model simultaneously. This is illustrated in Figure 5.3 as parallel approach.<br />

Both the development <strong>of</strong> the essential end implementation model <strong>of</strong> a complex system<br />

require activities on various levels <strong>of</strong> abstraction. The iterations necessary to keep the

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

Saved successfully!

Ooh no, something went wrong!