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.

398 Case Study<br />

Feeder<br />

Sensors/<br />

Actuators<br />

Merger<br />

Sensors/<br />

Actuators<br />

Feeder<br />

Sensors/<br />

Actuators<br />

Feeder<br />

Sensors/<br />

Actuators<br />

Feeder<br />

Sensors/<br />

Actuators<br />

CAN<br />

Packer<br />

Sensors/<br />

Actuators<br />

Central Control<br />

Station<br />

Separator/<br />

Printer<br />

Sensors/<br />

Actuators<br />

Stacker<br />

Sensors/<br />

Actuators<br />

Figure 12.10: Implementation Structure Diagram <strong>of</strong> Centralised Control System<br />

The step from the current centralised mailing machines to the fully distributed ones<br />

is quite large and therefore risky. To reduce the risk it would be attractive to start<br />

<strong>of</strong>f with the implementation <strong>of</strong> an ’in-between’ solution. Instead <strong>of</strong> distributing the<br />

intelligence in a physical way, one could distribute the same intelligence in a logical<br />

way. The resulting logically distributed control system could then be implemented in<br />

s<strong>of</strong>tware in a centralised sequential manner. Another implementation decision could<br />

be to use a ’remote IO’ solution (in stead <strong>of</strong> large bundles <strong>of</strong> point-to-point wires)<br />

for the communication with sensors and actuators. The ’remote IO’ solution could<br />

for instance be implemented using a Controller Area Network (CAN) [CAN95]. A<br />

graphical representation <strong>of</strong> the topology that results from the implementation decisions<br />

is presented in the Implementation Structure Diagram <strong>of</strong> Figure 12.10. To conform to the<br />

implementation decisions, the structure <strong>of</strong> the essential model, which was formalised as<br />

shown in Figure 12.11, will have to be transformed. The idea is to map each terminator<br />

instance <strong>of</strong> the Instance Structure Diagram (Figure 12.11) on a corresponding sensor<br />

and actuator module in the Implementation Structure Diagram (Figure 12.10). The<br />

controllers and the information server are mapped on the central control station. Using<br />

the behaviour-preserving transformations <strong>of</strong> Chapter 10, the model <strong>of</strong> Figure 12.11 can<br />

be transformed into a behaviour-equivalent model presented in Figure 12.12. Notice that<br />

the Central Control Station contains a complete logical image <strong>of</strong> the physical production<br />

line. In this way, the modularity <strong>of</strong> the physically distributed control system is preserved<br />

in the s<strong>of</strong>tware <strong>of</strong> the control station. Notice further that the Central Control Station<br />

represents a distribution boundary as well as a concurrency boundary. The concurrency<br />

boundary formalises the constraint <strong>of</strong> sequential implementation. To make the mapping<br />

<strong>of</strong> the behaviour <strong>of</strong> the Central Control Station onto a sequential s<strong>of</strong>tware implementation<br />

feasible, it could be necessary to eliminate concurrency by modifying the behaviour style<br />

<strong>of</strong> the Central Control Station.<br />

A formal precondition for the previously described transformation to be carried out is<br />

that the controllers (<strong>of</strong> Figure 12.11) communicate with their terminators in a weakly

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

Saved successfully!

Ooh no, something went wrong!