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.

32 On <strong>Specification</strong> <strong>of</strong> <strong>Reactive</strong> <strong>Hardware</strong>/S<strong>of</strong>tware <strong>Systems</strong><br />

To make a specification understandable and readable, the formal specification<br />

language should have an imperative nature.<br />

The method must allow the development <strong>of</strong> advanced s<strong>of</strong>tware tools.<br />

The method as well as the formal language must support dedicated modelling<br />

concepts and modelling primitives.<br />

– Behaviour models should be built from process objects. Process objects are<br />

concurrent, self-contained, autonomous, relatively independent and weakly<br />

coupled entities. Process objects have to be grouped into classes.<br />

– Process objects should be connected by channels. It must be possible to group<br />

them into clusters. Clusters have to be organised into classes.<br />

– Information exchange between process objects and clusters must be based on<br />

message passing.<br />

– Process objects must be able to perform various forms <strong>of</strong> complex communication<br />

behaviour.<br />

– Private data <strong>of</strong> process objects must be represented by data objects. Data<br />

objects must be grouped into classes.<br />

The method requires an activity framework that guides the development <strong>of</strong> specifications.<br />

– This framework must be supported by a rich set <strong>of</strong> guidelines and heuristics.<br />

– The activity framework must allow the different modelling views as well as<br />

the unified model to be developed in a simultaneous, evolutionary fashion. To<br />

avoid confusion between different views, they must be explicitly represented.<br />

– The activity framework must allow the determination <strong>of</strong> observable behaviour<br />

by considering the internals <strong>of</strong> a system.<br />

– The activity framework must support the simultaneous development <strong>of</strong> object<br />

structure and object behaviour. Objects are found by considering conceptual<br />

solutions, by studying the real world, and by outside-in modelling.<br />

– The search for objects and behaviour should be guided by scenarios. Next to<br />

looking for object classes the framework should focus on the search for object<br />

instances.<br />

The activity framework must be supported by behaviour-preserving transformations<br />

that allow a consistent integration <strong>of</strong> logical and physical structures.<br />

Behaviour-preserving transformations must be expressed in the formal language<br />

and they have to be mathematically proven correct.

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

Saved successfully!

Ooh no, something went wrong!