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.

384 Case Study<br />

Feeding Unit Image. On the reception <strong>of</strong> a feed message, the Feeding Unit adds a new<br />

item to the mailing product. The unit can detect the occurrence <strong>of</strong> an incorrectly fed<br />

item (misFed) as well as the erroneous situation that more than one copy <strong>of</strong> the item was<br />

fed (doubleFed). It is further possible to detect whether the Feeding Unit is mounted to<br />

the station or not by a continuous status message (mounted,notMounted).<br />

Before any item is actually being fed, the Service Scheduler investigates the services<br />

<strong>of</strong>fered by the feeder station. For this purpose it requests the status <strong>of</strong> the<br />

Feeding Unit Image. The image answers whether a Feeding Unit is mounted, and if<br />

so what Service it <strong>of</strong>fers 8 .<br />

Upon reception <strong>of</strong> the schedule message, the Service Scheduler asks the appropriate<br />

Product Info Keeper for each <strong>of</strong>fered service 9 whether this service is required. In case the<br />

feeding service is required, the Service Scheduler commands the Feeding Unit Image to<br />

perform the feed action for the appropriate mailing product. Based on the Initial Position,<br />

the Feeding Unit Image can calculate at what position the feed action actually has to take<br />

place. Subsequently the Feeding Unit Image requests the Transporter Image to get woken<br />

at this position. If it receives the wakeUp message, the Feeding Unit Image triggers the<br />

Feeding Unit and monitors if the feed action is carried out properly. After successful<br />

completion <strong>of</strong> the feed action, the Service Administrator is informed and this administrator<br />

updates the appropriate product Info Keeper. The situation that the feed action is not<br />

completed successfully is not covered in this scenario.<br />

12.3.5 Other Scenarios and Other Stations<br />

The Product Flow Scenario and Feeding Scenario only address a (simplified) part <strong>of</strong><br />

the necessary behaviour. Together the scenarios describe a number <strong>of</strong> essential objects<br />

and flows to perform the normal course <strong>of</strong> behaviour <strong>of</strong> a production line. But even<br />

for this purpose the scenarios are not complete. To achieve completeness and to study<br />

and specify other forms <strong>of</strong> behaviour, other scenarios had to be elaborated. Examples<br />

<strong>of</strong> important scenarios are:<br />

Batch job preparation scenario.<br />

Initialisation and configuration scenario.<br />

Error handling scenario.<br />

Maintenance, repair and test scenario.<br />

Product information distribution scenario.<br />

Failure effect analysis scenario.<br />

8 The service can for instance be the feeding <strong>of</strong> a floppy disk or <strong>of</strong> a certain magazine.<br />

9 In case <strong>of</strong> the feeder station, at most one service can be <strong>of</strong>fered. In general, a station can perform<br />

many services.

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

Saved successfully!

Ooh no, something went wrong!