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.

368 SHE Framework<br />

Object Class Models are extended with new classes that emerge from the extension<br />

<strong>of</strong> the Message Flow Diagrams.<br />

Extended Instance Structure Diagrams are created. Behaviour-Preserving Transformations<br />

can be used to improve structure and map processes to various implementation<br />

resources that are visualised as clusters.<br />

The Unified Model is extended, refined and transformed according to the needs <strong>of</strong><br />

all other extended diagrams.<br />

If decisions for a technology can be made well considered, but also early, this is a<br />

big advantage for the efficiency <strong>of</strong> the modelling. We <strong>of</strong>fer the opportunity to specify<br />

these decisions in the essential phase. However, the separation between essence and<br />

implementation must always be kept in mind. It will be clear that there is such a<br />

wide variety <strong>of</strong> possible systems and possible technologies that a lot <strong>of</strong> decisions can<br />

be made only after the Essential <strong>Specification</strong> is finished. Furthermore the extension <strong>of</strong><br />

the model with new objects with corresponding behaviour can cause iterations in the<br />

design because some newly added functionality can form an unacceptable load on the<br />

specified resources.<br />

Because <strong>of</strong> the wide variety <strong>of</strong> possibilities it is hard to give generic rules for the development<br />

<strong>of</strong> an extended model. A designer that learned to use our method in the<br />

essential phase will be able to create an extended model using his design knowledge<br />

and skills. This second model gives the opportunity to explore a specification in depth,<br />

including implementation modelling. An extended model is in general very specific for<br />

different products or systems. Therefore we only illustrate the sort <strong>of</strong> activities we have<br />

in mind for extended modelling by mentioning examples <strong>of</strong> various aspects.<br />

11.5.2 Implementation Technologies<br />

During the extended modelling phase the models are extended with directives about<br />

implementations in the form <strong>of</strong> boundaries and annotations in diagrams in the form <strong>of</strong><br />

comments. In this subsection we give an impression <strong>of</strong> the sort <strong>of</strong> information we want<br />

to annotate in the models.<br />

On the system level, decisions can be made for one or more:<br />

available hardware platforms;<br />

hardware modules to be developed;<br />

operating systems;<br />

networks based on one or more protocols;<br />

application s<strong>of</strong>tware layers;<br />

user interfaces;

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

Saved successfully!

Ooh no, something went wrong!