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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

11.5 Extended <strong>Specification</strong> Modelling 373<br />

purchased real-time operating system for the chosen processor. There is a wide variety<br />

available. Some are rather standard products others are intended as a framework that<br />

allows user defined configuration. Van Felius [vF96] explored the mapping from POOSL<br />

to pseudo concurrent implementations in C++, using the IEEE standard 1003.1 (POSIX)<br />

as interface to a thread library.<br />

<strong>Hardware</strong> implementation technology decisions can lead to the exploration <strong>of</strong> various<br />

specific functions. For instance a power-up reset may require a specific order in which<br />

various processes or modules are activated. Programmable logic requires configuration.<br />

Programmable logic modules can realise system parts that can be used in a flexible way.<br />

This requires programming control that can be even remote. Saving power can require<br />

a considered control <strong>of</strong> the activation <strong>of</strong> subsystems.<br />

The choice <strong>of</strong> a communication technology has in general a big impact on a model.<br />

Therefore selections should be made on the system level and as early as possible. The<br />

world <strong>of</strong> communication technology and protocols is a rapidly growing. Depending on<br />

the sort <strong>of</strong> system to be developed we have to cope with design according to various<br />

standards. There is a huge amount <strong>of</strong> knowledge in the area <strong>of</strong> standards. A wide variety<br />

<strong>of</strong> communication processors that implement particular protocols for networks or busses<br />

is available in hardware and/or s<strong>of</strong>tware. In depth specific knowledge is necessary when<br />

the implementation <strong>of</strong> one or more protocols is needed. Further description is beyond<br />

the scope <strong>of</strong> this thesis.<br />

Selection <strong>of</strong> interface technology on the system boundary is in general postponed to<br />

the extended modelling phase. Therefore the modelling <strong>of</strong> objects around the system<br />

boundary needs special attention. Dedicated objects can be added to model the concrete<br />

communication between actors and sensors that are chosen to implementation terminators.<br />

Another example <strong>of</strong> a modelling activity in this phase is the detailed design <strong>of</strong> user<br />

interfaces. The essential model will specify a rather abstract user interface. A command<br />

by a user can be modelled as one single message. In reality many interactions can be<br />

needed accompanied by checking <strong>of</strong> the interactions to give such a command. Extended<br />

modelling refines such a user interface. User interface and interface technology affect<br />

also an environment model developed for simulation. So refinement <strong>of</strong> this model is<br />

also part <strong>of</strong> the activities.<br />

11.5.5 Extended Instance Structure Diagrams<br />

The activities in the Instance Structure Models in the extended phase are <strong>of</strong> the same<br />

sort. Formalisation <strong>of</strong> properties by boundaries is further extended and refined based in<br />

implementation and design decisions. Abstraction boundaries, implementation boundaries,<br />

concurrency boundaries, and distribution boundaries annotated on a hierarchy<br />

<strong>of</strong> clusters structure the model. Behaviour preserving transformations can be used to<br />

improve the structure <strong>of</strong> the model and to map various processes on various implementation<br />

modules.

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

Saved successfully!

Ooh no, something went wrong!