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.

344 SHE Framework<br />

Object Models<br />

Object Class<br />

Model<br />

Object<br />

Class<br />

Diagrams<br />

Message<br />

Flow<br />

Diagrams<br />

Listed Requirements<br />

System Dictionary<br />

Object Instance Model<br />

Instance<br />

Structure<br />

Diagrams<br />

Unified Model:<br />

POOSL Description<br />

Requirements catalogue<br />

Graphical models<br />

Structure models<br />

Architecture Structure<br />

Diagrams<br />

Implementation<br />

Structure Diagrams<br />

Architecture Decisions Statement<br />

Textual models<br />

Implementation Decisions Statement<br />

Figure 11.8: Simplified Overview <strong>of</strong> Textual and Graphical Representations<br />

that visualises relations between classes and the Object Instance Model that visualises<br />

instances which are objects and/or clusters. Message Flow Diagrams show message<br />

flows and Instance Structure Diagrams show channels. Notice that Instance Structure<br />

Diagrams are both part <strong>of</strong> the Object Model as well as part <strong>of</strong> the Structure model.<br />

Instance Structure Diagrams serve to formalise the informal architecture structure (or<br />

implementation structure) as a structure <strong>of</strong> clusters, processes and channels.<br />

11.4.2.2 Unified Model<br />

The block ’Textual models’ in Figure 11.8 shows the Unified Model and the Requirements<br />

Catalogue. A Unified Model is a formal description <strong>of</strong> a system in the language POOSL.<br />

This model is called unified because it encompasses both behaviour and structure <strong>of</strong> the<br />

system to be designed.<br />

11.4.2.3 Requirements Catalogue<br />

A Requirements Catalogue contains all items that must be specified but cannot be<br />

formalised in the Unified Model. A minimum catalogue contains four items:<br />

Listed Requirements. This is an extension <strong>of</strong> the Requirements List in the Initial<br />

Requirements Description.

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

Saved successfully!

Ooh no, something went wrong!