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.

2.3 <strong>Specification</strong>s, Models and Views 17<br />

The duration <strong>of</strong> communications, the duration between communications and the<br />

duration <strong>of</strong> data transformations are captured in timing views. Current methods<br />

that <strong>of</strong>fer timing views, be it in a very restricted way, are HOOD [Rob92], HRT-<br />

HOOD [BW95], OOSE [J<br />

92], OOD [Boo91] and the method <strong>of</strong> Hatley and Pirbhai<br />

[HP88]. The Statemate method does not support timing views directly. However,<br />

time is expressible in an adequate way within the state-transition view <strong>of</strong> Statemate.<br />

The same holds for the SDL-based methods [Tur93, BH93] and for ROOM [SGW94].<br />

A conceptual view focuses on classes <strong>of</strong> system components (called objects) together<br />

with the conceptual relations that exist between those classes. These static views<br />

are typically supported by most object-oriented methods nowadays [R 91, C 94,<br />

CY91a, CY91b, J 92, Boo91, Mor94, SM88].<br />

In architectural views the physical system structure is described. Examples <strong>of</strong> physical<br />

structures are s<strong>of</strong>tware layering, physical topologies, distributed architectures<br />

and hardware/s<strong>of</strong>tware partitionings. Most current specification methods aim<br />

at the development <strong>of</strong> s<strong>of</strong>tware and do not <strong>of</strong>fer architectural views that are adequate<br />

for hardware too. Methods that do <strong>of</strong>fer architectural views are the Statemate<br />

method [H 90] and the method <strong>of</strong> Hatley and Pirbhai [HP88]. The formal descrip-<br />

tion techniques based on LOTOS, SDL and Estelle [Tur93, BH93, Pir92, D<br />

89] as<br />

well as the ROOM method [SGW94] do not <strong>of</strong>fer separate architectural views,<br />

but can adequately describe architecture within their unified model. Architecture<br />

plays a crucial role within reactive hardware/s<strong>of</strong>tware systems and requires<br />

adequate modelling concepts. These are studied in Section 2.5 and in Chapter 5.<br />

The unified model combines the five views, by describing as many system aspects as<br />

possible simultaneously in an integrated way. Only few specification methods aim at<br />

the development <strong>of</strong> such an explicit unified model. These are the formal description<br />

techniques based on LOTOS, SDL and Estelle [Tur93, BH93, Pir92, D<br />

89], the ROOM<br />

method [SGW94] and the ROOA method [Mor94]. The formal description techniques<br />

and ROOM, however, do not create separate views. The ROOA method, on the other<br />

hand, produces a unified model as well as separate views.<br />

This thesis focuses on the higher levels <strong>of</strong> specification and design (see Section 2.6).<br />

Although each <strong>of</strong> the elements shown in Figure 2.1 are addressed in this thesis, the focus<br />

will be on those elements that we consider most important and difficult for these higher<br />

levels <strong>of</strong> specification and design. These elements are behavioural views, architectural<br />

views and the unified system model. The modelling concepts that are required to support<br />

these views are described in more detail in Section 2.5.<br />

Behavioural views and architectural views are indispensable for<br />

reactive hardware/s<strong>of</strong>tware systems. Other important views are<br />

timing views, requirements views and conceptual views.

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

Saved successfully!

Ooh no, something went wrong!