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.

4.11 Composites and Hierarchies 99<br />

x<br />

w w<br />

x Object A<br />

y z<br />

Object C<br />

a b<br />

c<br />

Cluster<br />

Object B<br />

Figure 4.26: Cluster with Hidden Channels<br />

for the communication with the sensor and hides in fact the sensor for the rest <strong>of</strong> the<br />

system. The aggregate in Figure 4.27 is thought to encompass Sensor 1 and Actor 1.<br />

However the system boundary intersects the (virtual) cluster. Terminators Sensor 1 and<br />

Actor 1 are considered as belonging to the aggregate, although the cluster boundary<br />

cannot encompass them. By doing this, Object B, for example, can still be considered<br />

to be a separate part <strong>of</strong> a clustered aggregate. Parts B and C are not visible for other<br />

objects, that are outside the cluster but are internal to the system. Object B and C are<br />

however visible to the terminators, which are external objects. So in this case external<br />

objects require a different treatment than internal (system) objects. External objects do not<br />

respect the rules for inward and outward visibility for clustered aggregates. For reasons<br />

<strong>of</strong> clarity they must be referred to as terminators and not as objects. They also have a<br />

different graphical symbol distinguishing them from the process objects. The advantage<br />

<strong>of</strong> a different symbol is that it is always clear that a terminator is an external object. So<br />

it is no problem to draw terminators at various places inside the system boundary. This<br />

is convenient because it prevents diagrams from being cluttered by long connections<br />

to terminators on the edge <strong>of</strong> a scheme. If needed, the diagrams can be transformed<br />

such that the terminators move outside that system boundary, when system analysis is<br />

finished.<br />

4.11 Composites and Hierarchies<br />

In the previous sections, various forms <strong>of</strong> hierarchy passed by, such as:<br />

1. whole-part class hierarchy;<br />

2. subtype/supertype class hierarchy;<br />

3. hierarchy <strong>of</strong> subsystems, cluster hierarchy.<br />

There may be some confusion about the place <strong>of</strong> composites for modelling hierarchy in<br />

our method. Object-oriented analysis methods use Object Class Diagrams to visualise<br />

Whole-part class hierarchies and Subtype/supertype class hierarchies simultaneously.

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

Saved successfully!

Ooh no, something went wrong!