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.

13.2 P.H.A. van der Putten’s Contributions 407<br />

Objects, clusters and channels support formalisation <strong>of</strong> architecture and implementation<br />

structure. Representations are defined consistently with formal structure<br />

description in POOSL.<br />

Hierarchy, hiding, functionally decomposed scenarios and multidisciplinary scenarios<br />

enable coping with complexity.<br />

Graphical notations are complemented by textual descriptions, such as decision<br />

statements, scenario narratives and system dictionaries.<br />

Method framework<br />

An activity framework has been developed that:<br />

guides the designer from idea to formal model by giving orientation as well as<br />

guidelines and heuristics;<br />

separates a specification in an essential specification and an extended specification;<br />

<strong>of</strong>fers system modelling in different views as well as in a unified model that<br />

formalises a part <strong>of</strong> the information in the other views;<br />

four different types <strong>of</strong> views are represented in graphical diagrams:<br />

– object collaboration in scenarios (Message Flow Diagrams and Scenario Narratives);<br />

– classes and relations (Object Class Diagrams);<br />

– physical or logical system structure (Architecture Structure Diagrams);<br />

– formal system structure (Instance Structure Diagrams);<br />

uses textual representations, combined in a Requirements Catalogue, for the description<br />

<strong>of</strong> design decisions, environmental requirements and entities <strong>of</strong> the problem<br />

domain;<br />

invites to create a well-designed system structure based on physical and logical<br />

constraints, on possible prescribed implementations and according to the structure<br />

<strong>of</strong> the problem domain; structure does not emerge from coincidental functional<br />

decomposition;<br />

<strong>of</strong>fers a balanced approach for finding objects by looking both at classes and<br />

instances;<br />

uses scenarios for focusing on various forms <strong>of</strong> functionality as well as on various<br />

multidisciplinary views on functionality; scenario narratives are used for the description<br />

<strong>of</strong> dynamic behaviour, ordering and causality; they prepare the formal<br />

description <strong>of</strong> behaviour in POOSL.

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

Saved successfully!

Ooh no, something went wrong!