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.

6.8 Summary 227<br />

They can graphically represent communication between process objects and clusters<br />

in so-called Message Flow Diagrams. These symbols are designed to be understood<br />

intuitively. All forms <strong>of</strong> communication can be formalised by mapping them on the one<br />

way synchronous message passing primitive <strong>of</strong> POOSL. Channel names and identifiers<br />

<strong>of</strong> process objects can be used to create static and dynamic links between process objects.<br />

The concepts <strong>of</strong> physical and logical distribution support system structure design. Physical<br />

distribution is specified by distribution boundaries on clusters. The specification<br />

<strong>of</strong> distribution is related to communication, more specific to name spaces <strong>of</strong> process<br />

object identifiers, and to the use <strong>of</strong> channels. Weakly distributed modules communicate<br />

using object identifiers to determine the receiver <strong>of</strong> a message. In contrast, strongly distributed<br />

modules communicate autistically via static links. Channels, message names<br />

and process object identifiers are used to specify either static or dynamic links between<br />

collaborating entities. Considered use <strong>of</strong> these concepts is necessary to specify a distribution<br />

structure.<br />

Scenarios are used to conquer complexity and to integrate a multidisciplinary approach<br />

into our method. Scenarios are an approach that extend the interpretations incorporated<br />

in other methods. The use <strong>of</strong> scenarios shortens system development time. A considered<br />

set <strong>of</strong> scenarios <strong>of</strong>fers adequate abstractions that greatly improve the efficiency <strong>of</strong> the<br />

communication with various experts.<br />

Various concepts to reason about state on various levels <strong>of</strong> abstraction have been defined.<br />

Named states represent behaviour that produces responses on messages representing<br />

events. This approach integrates aspects <strong>of</strong> event-orientation found in Structured Analysis<br />

with the object-oriented paradigm.<br />

An introduction to the expressions and statements that POOSL <strong>of</strong>fers for the definition<br />

<strong>of</strong> data classes, process classes, cluster classes and systems completed the description<br />

<strong>of</strong> the modelling <strong>of</strong> dynamic behaviour. Instances <strong>of</strong> process classes can perform concurrent<br />

and/or infinite behaviour. Behaviour is defined as a collection <strong>of</strong> methods.<br />

Interrupt, abort and choice statements are constructs that give our method the properties<br />

to describe systems adequately on a high level <strong>of</strong> abstraction. Clusters and systems<br />

are described as the parallel composition <strong>of</strong> instances <strong>of</strong> process classes and cluster<br />

classes using channel hiding and renaming. Data objects enable the description <strong>of</strong> dynamic<br />

data structures. Data is stored in instance variables and local variables. On the<br />

reception <strong>of</strong> messages, corresponding methods are activated. Interaction <strong>of</strong> data objects<br />

is sequential. Various statements such as assignment statements, ’if’ statements and ’do’<br />

statements have been presented.<br />

Real-time requirements can be specified on system architecture level. The incorporation<br />

<strong>of</strong> time primitives and the development <strong>of</strong> tools will be covered in a separate Ph.D.<br />

project.<br />

The material <strong>of</strong> this chapter, together with Chapters 4 and 5 forms the basis for the<br />

method framework that is described in Chapter 11. All concepts have been defined and

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

Saved successfully!

Ooh no, something went wrong!