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.

9.8 Summary 301<br />

To prepare the development <strong>of</strong> behaviour-preserving transformation in Chapter 10, we<br />

have made the notion <strong>of</strong> ’behaviour-preservation’ precise. To this end we have defined<br />

a binary relation, called transformation equivalence, on POOSL specifications.<br />

Transformation equivalence is (indirectly) defined in terms <strong>of</strong> so-called bisimulations.<br />

Bisimulations, on their turn, are specified in terms <strong>of</strong> the structural operational semantics<br />

<strong>of</strong> POOSL. They provide a simple and elegant technique for proving equivalences<br />

between specifications.<br />

Transformation equivalence is strongly related to observation equivalence defined by<br />

Milner for CCS. Observation equivalence has the advantage <strong>of</strong> being very strong. If two<br />

systems are known to be observation equivalence, then they are also equivalent under<br />

many other equivalence relations. In the context <strong>of</strong> behaviour-preserving transformations,<br />

this is a very pleasant property.<br />

Although observation equivalence is a very strong relation, it is still too weak to support<br />

behaviour-preserving transformations. The problem is that observation equivalence<br />

only refers to future behaviour <strong>of</strong> systems. It does therefore not allow transformations<br />

to be carried out correctly during interactive system simulation. Transformation equivalence<br />

remedies this shortcoming by also taking the past behaviour into account. To<br />

demonstrate the applicability <strong>of</strong> transformation equivalence, we have given a simple<br />

example in which we prove that a simple handshake protocol and a 1-place buffer are<br />

transformation equivalent.<br />

In comparison to semantics found in literature, our semantics may seem rather complex.<br />

In literature, however, semantics are <strong>of</strong>ten based on toy languages or on simple and clean<br />

parts <strong>of</strong> realistic languages. In our case we have given a full semantics <strong>of</strong> a complex and<br />

realistic language. We think that this justifies the additional complexity.

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

Saved successfully!

Ooh no, something went wrong!