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.

13.4 Related Results 409<br />

The notion <strong>of</strong> behaviour-preservation is based on an equivalence relation, called<br />

transformation equivalence. Transformation equivalence is defined on top <strong>of</strong> the<br />

operational semantics in terms <strong>of</strong> bisimulations.<br />

Each transformation is:<br />

– mathematically proven correct with respect to transformation equivalence;<br />

– applicable to the full range <strong>of</strong> POOSL specifications, even those that are<br />

infinite-state;<br />

– applicable during interactive simulation.<br />

The system <strong>of</strong> transformations is proven to be incomplete. There are always<br />

specifications that are transformation equivalent and that only differ with respect<br />

to their boundaries and channels, but which cannot be transformed into each<br />

other. This incompleteness result is fundamental; it cannot be solved by adding<br />

more transformations. Despite <strong>of</strong> this, case studies have proven the transformation<br />

system to be applicable in many practical situations.<br />

Next to the incompleteness result described above, another incompleteness result<br />

is proven. For each specification there exists an infinite number <strong>of</strong> other<br />

specifications that are transformation equivalent, but for which no sequences <strong>of</strong><br />

transformations exist that transform the former specification into the latter ones.<br />

This incompleteness result leads us to a fundamental limitation <strong>of</strong> transformational<br />

design. The choice <strong>of</strong> an initial specification model determines whether<br />

or not a satisfying implementation model is derivable using transformational design.<br />

Therefore it is important to consider implementation-oriented aspects during<br />

specification. This statement confirms one <strong>of</strong> the basic ideas <strong>of</strong> this whole thesis.<br />

13.4 Related Results<br />

Next to the results described in this thesis, there are a number <strong>of</strong> related results in the<br />

context <strong>of</strong> our project:<br />

In [Lis94] the POOSL language has been successfully applied to specify the presentation<br />

layer <strong>of</strong> the OSI reference model.<br />

In [vF96] it is studied how POOSL specifications can be implemented in the C++<br />

programming language [Str92]. A partial mapping from POOSL to C++ is described<br />

in [vF96].<br />

In [Man96] a prototype partial simulator for POOSL is designed.<br />

In [Gei96] the POOSL language has been extended with primitives that allow<br />

the specification <strong>of</strong> real-time behaviour. A complete formal semantics <strong>of</strong> these<br />

primitives are also given in [Gei96].<br />

In [Kup96] a compiler is developed that is able to perform a partial translation <strong>of</strong><br />

POOSL into PROMELA [Hol93]. PROMELA is the input language for the formal<br />

verification tool SPIN [Hol93].

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

Saved successfully!

Ooh no, something went wrong!