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.

50 Concepts for Analysis, <strong>Specification</strong> and Design<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 3.12: Simplified Overview <strong>of</strong> Textual and Graphical Representations<br />

Figure 3.13 shows the phases and milestones <strong>of</strong> the SHE method in a system specification<br />

and design project. SHE has two phases, marked by a milestone in between. These<br />

phases are the realisation <strong>of</strong> an Essential <strong>Specification</strong> and an Extended <strong>Specification</strong>. Before<br />

starting the application <strong>of</strong> the method an Initial Requirements Description must be realised.<br />

Milestone 3 indicates the start <strong>of</strong> the actual implementation and realisation <strong>of</strong> a system.<br />

The goal <strong>of</strong> the Essential <strong>Specification</strong> phase is an analysis <strong>of</strong> essential system requirements<br />

and the creation <strong>of</strong> both an abstract behaviour model and the highest level system<br />

structure model (architecture). Both models are developed in a strong interaction. Behaviour<br />

and structure are formalised into a Unified formal description in the language<br />

POOSL. This description enables examination <strong>of</strong> various system properties via simulation<br />

and formal verification. The result <strong>of</strong> these activities must be a correct abstract<br />

system model. The goal <strong>of</strong> the Extended <strong>Specification</strong> phase is the incorporation <strong>of</strong> implementation<br />

decisions in the essential system requirements. This leads to the creation<br />

<strong>of</strong> both an extended behaviour model and the concrete system structure model (implementation<br />

structure). Both models are developed in a strong interaction. Extended Behaviour<br />

and Implementation Structure are formalised into an Extended Unified Model.<br />

This is a formal description in the language POOSL. This description enables further detailed<br />

examination <strong>of</strong> various system properties via simulation and formal verification.

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

Saved successfully!

Ooh no, something went wrong!