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.

186 Modelling <strong>of</strong> Concurrent <strong>Reactive</strong> Behaviour<br />

We defined a collection <strong>of</strong> message flow symbols. They can graphically represent communication<br />

between process objects and clusters in so-called Message Flow Diagrams.<br />

These symbols are designed to be understood intuitively.<br />

We showed that all forms <strong>of</strong> process communication can be formalised by mapping<br />

them on the one way synchronous message passing primitive <strong>of</strong> POOSL. We described<br />

various alternatives to specify the destination <strong>of</strong> messages between process objects, and<br />

multiples. We described how channel names and identifiers <strong>of</strong> process object can be<br />

used to create static and dynamic links between process objects.<br />

We described the communication between data objects. They always use a double<br />

rendezvous to realise synchronous communication with reply and waiting.<br />

6.4 Distribution<br />

6.4.1 Introduction<br />

Distribution is a key issue in present-day research for complex system design. Production<br />

systems, industrial control systems and automated teller networks, for instance, are very<br />

<strong>of</strong>ten distributed systems. Even many consumer products are distributed systems internally.<br />

A distributed computer system has its resources dispersed across independent<br />

computers (subsystems) connected through a communication network. These resources<br />

may be programs, pieces <strong>of</strong> hardware, data resources, peripherals or specific interfaces<br />

to the environment. Distribution may be logical, physical or both, it may be weak or<br />

strong, and the subsystems may be statically or dynamically linked. In this section we<br />

describe the concepts for distributed modelling.<br />

6.4.2 Distribution and System Design<br />

The architecture model <strong>of</strong> a system can define a distribution structure. Physical distribution<br />

is <strong>of</strong>ten simply prescribed by a real physical topology, e.g. topology <strong>of</strong> an<br />

existing infrastructure, or by the physical (geographical) embedding <strong>of</strong> the system to<br />

be designed. In these cases structure is a strong requirement that should influence<br />

the development process as early as possible. This is an important reason to integrate<br />

system specification with system design. During analysis <strong>of</strong> a complex system we use<br />

abstract entities such as objects as the vehicles that enable a dispersion (distribution) <strong>of</strong><br />

the overwhelming amount <strong>of</strong> details in the problem domain. A method must be able<br />

to match the two completely different forms <strong>of</strong> distribution: the conceptual (logical)<br />

distribution and the implementation-oriented physical distribution.<br />

A distributed architecture requires a specific sort <strong>of</strong> decomposition <strong>of</strong> a system into<br />

subsystems. This can be specified by defining subsystems with distribution boundaries.<br />

Any object that is found during continuing analysis must find its place in one <strong>of</strong> the subsystems.<br />

We must prevent that objects appear to be cut by a distribution boundary. We

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

Saved successfully!

Ooh no, something went wrong!