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.3 Communication 171<br />

(normalCourseOfBehaviour) interrupt channel!temperature(real)<br />

In this construct (normalCourseOfBehaviour) is a collection <strong>of</strong> one or more process statements<br />

that perform some behaviour. This behaviour can be interrupted any time to<br />

finish a rendezvous with the requester <strong>of</strong> a temperature(real) message.<br />

Recall that runk is an example <strong>of</strong> one <strong>of</strong> the unknown objects. These are built-in primitive<br />

objects in POOSL. When a message transports more complex objects, we are ourselves<br />

responsible for the definition <strong>of</strong> unknown values.<br />

Summary<br />

The continuous flow symbol is useful for the modelling <strong>of</strong> a continuous stream <strong>of</strong><br />

messages or values. The meaning <strong>of</strong> the flow is that the producer produces continuously,<br />

and the consumer can consume at any moment. This means that the producer:<br />

sends a message instantly on any initiative for a rendezvous by a consumer <strong>of</strong> the<br />

flow;<br />

refreshes the message instantly after each rendezvous with a consumer;<br />

sends a message containing the instantaneous value <strong>of</strong> the continuous source at<br />

the moment <strong>of</strong> the rendezvous, during the time interval that the flow must be<br />

produced;<br />

sends a message containing an unknown value, during the time interval that the<br />

flow must not be produced.<br />

6.3.6.4 Buffered Message Symbol<br />

The buffered message symbol models asynchronous communication. Asynchronous communication<br />

means that a sender can send without knowing whether the receiver is willing<br />

to receive. This sort <strong>of</strong> communication is modelled by the introduction <strong>of</strong> a buffer.<br />

Therefore the symbol is a flow with a buffer symbol near the arrow head, see Figure 6.7.<br />

A problem with this communication concept is that the receiver may or may not accept<br />

client retrieve(PersonName) dataBaseA<br />

Figure 6.7: A Buffered Message Flow<br />

the message within a given time period. The sender, however, can always accomplish<br />

a rendezvous with the buffer; the buffer always listens. The receiver cannot always<br />

perform a rendezvous. This depends in the first place on the state <strong>of</strong> the receiver, but

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

Saved successfully!

Ooh no, something went wrong!