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.4 Essential <strong>Specification</strong> Modelling 343<br />

Unified Model and Requirements Catalogue (textual form).<br />

Figure 11.7 depicts a purpose overview <strong>of</strong> the elements <strong>of</strong> the framework.<br />

Static Modelling:<br />

Finding object classes,<br />

relations, attributes,<br />

messages<br />

Essential Behaviour Model Architecture Structure Model<br />

Essential<br />

Object<br />

Class<br />

Diagrams<br />

Scenario Modelling:<br />

Finding objects and their<br />

message interaction<br />

Formal description <strong>of</strong> system:<br />

Description <strong>of</strong> process<br />

interconnect structure and<br />

behaviour <strong>of</strong> all object<br />

classes.<br />

Essential<br />

Message<br />

Flow<br />

Diagrams<br />

Design <strong>of</strong> process<br />

channel structure:<br />

Structure<br />

transformations<br />

Essential <strong>Specification</strong><br />

Essential<br />

Instance<br />

Structure<br />

Diagrams<br />

Essential<br />

Unified<br />

Model<br />

(POOSL)<br />

and<br />

Essential Requirements Catalogue<br />

System Architecture<br />

design: Topology <strong>of</strong><br />

interconnected Modules<br />

Architecture<br />

Structure<br />

Diagrams<br />

Adding timing<br />

requirements on<br />

architecture<br />

modules level<br />

Architecture<br />

Response<br />

Time<br />

Requirements<br />

Description <strong>of</strong> all items in the<br />

models: meaning, purpose;<br />

Description <strong>of</strong> all requirements that<br />

are not formalised in POOSL;<br />

Description <strong>of</strong> design decisions.<br />

Figure 11.7: Purpose <strong>of</strong> SHE Framework Blocks<br />

11.4.2 Graphical and Textual Representations<br />

A specification consists <strong>of</strong> various kinds <strong>of</strong> models. They are graphical representations,<br />

text in the form <strong>of</strong> a natural or formal language, or lists <strong>of</strong> textual items. Figure 11.8<br />

gives an overview <strong>of</strong> the kinds <strong>of</strong> representations that are used in the framework. Notice<br />

that this figure should not be interpreted as the framework <strong>of</strong> the method.<br />

11.4.2.1 Graphical Representations<br />

The graphical models in Figure 11.8 are divided into Object Models and Structure<br />

Models, see the overlapping dotted blocks. The Object Models are the Object Class Model

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

Saved successfully!

Ooh no, something went wrong!