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.

406 Conclusions and Future Work<br />

– integrates analysis and system design with the goal <strong>of</strong> minimising iterations<br />

in the system development process;<br />

– uses appropriate graphical models for easy communication with various persons<br />

involved in a modelling process;<br />

– enables the specification <strong>of</strong> a well-considered system structure <strong>of</strong> generic and<br />

reusable system parts;<br />

– produces adequate abstractions for efficient communication with various experts;<br />

– records design decisions for the purpose <strong>of</strong> efficient future improvements.<br />

The method gradually composes a consistent system model by simultaneous analysis<br />

and modelling <strong>of</strong> various system properties, with emphasis on system structure<br />

and functionality.<br />

The method <strong>of</strong>fers a framework for various modelling activities that yield distinct<br />

views, all having a specific expressiveness. These views are partially integrated<br />

into a unified formal and executable model.<br />

Method elements<br />

Concepts have been defined for the modelling <strong>of</strong> a system in terms <strong>of</strong> weaklycoupled<br />

collaborating entities. Examples <strong>of</strong> concepts are objects, clusters, channels,<br />

message flows, identifiers, and various forms <strong>of</strong> composites.<br />

Process objects as well as data objects are incorporated in the method consistently<br />

with their meaning in POOSL. Process objects are defined to model concurrent<br />

autonomous entities connected by channels. Data objects are defined to model<br />

data in process objects.<br />

Classes are used to group objects and to group clusters. They abstract and generalise<br />

properties <strong>of</strong> objects and clusters and they form the grain <strong>of</strong> behaviour<br />

description.<br />

Various forms <strong>of</strong> communication can be modelled by various graphical symbols.<br />

All forms can be formalised in terms <strong>of</strong> the pair-wise synchronous message passing<br />

primitive used in POOSL.<br />

Channels are used for passing messages between process objects. They enable<br />

static structuring <strong>of</strong> a system.<br />

Boundaries are mapped on clusters. They support the modelling <strong>of</strong> various system<br />

module properties such as internal concurrency, implementation technology and<br />

physical distribution.<br />

Classical object modelling, with the use <strong>of</strong> generally accepted symbols, is incorporated<br />

in the method.

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

Saved successfully!

Ooh no, something went wrong!