Specification of Reactive Hardware/Software Systems - Electronic ...

388 Case Study
P:Product_Info_Keeper
Attributes:
Messages:
store
retrieve
servicePerformed
serviceOffered
D: PI
Attributes:
idNumber
Messages:
requires(Service)
markPending(Service)
markPerformed(Service)
D: Destination
Attributes:
name
address
zipcode
city
state
country
Messages:
P: Feeding_Unit_Image
Attributes:
Messages:
giveStatus
mounted
notMounted
feed
misFed
doubleFed
D: Service
Attributes:
type
name
Messages:
D: RequiredService
Attributes:
serviceState
Messages:
markUnserviced
markPending
markPerformed
provides
P: Transporter_Image
Attributes:
Messages:
wakeAt
encoderPuls
keeps
track of
D: Position
Attributes:
Messages:
setToZero
increment
+(PositionDelta)
-(Position)
=(Position)
asInitialPosition
D: InitialPosition
Attributes:
Messages:
P: Transporter
Attributes:
Messages:
move
models runs at
controls
D: Speed
Attributes:
Messages:
setToZero
setToMaximum
differ
D: PositionDelta
Attributes:
Messages:
Figure 12.9: Object Class Diagram of the Mailing Machine
Through the requires(Service) message, a PI instance can be asked whether it contains
a RequiredService that matches the offered Service contained in the message. A RequiredService
matches a Service if they have the same types and names. Through the
markPending(Service) and markPerformed(Service) messages, a PI instance can change state
of its matching RequiredService.
Next to aggregation and generalisation relations Figure 12.9 shows a number of conceptual
relations 15 . For instance, a Transporter Image models a Transporter. A Transporter runs
at a certain Speed. The Speed is controlled by the Transporter Image. The Transporter Image
keeps track of the Position of the Transporter.
A Position can differ from another Position. This is a relation between objects of the
same class. The difference between two Positions is modelled by an object of class
15 Conceptual relations are indicated by named connection between classes.
has