80 ). Figure 2.80 shows the relationships between several blocks. In contrast,
Figure 4.29 (p. 244), e.g., shows the detailed defi nition of a single block, card
reader .
FIGURE 2-79
Specifying the identifi ed ports.
bdd [package] On-board computer [port specifications]
readCardData():Card data
?«interface?»
ICustomerCard
?«signal?»
SigLED(f:color,blinking:Boolean)
?«interface?»
IStatusDisplay
send(chipId:String,data:String)
?«interface?»
ICardData
zv(cmd:String)
ws(cmd:String)
getSpeedoStatus():String
?«interface?»
ICar
srvSendMessages(data:String)
?«interface?»
IBC_ServerData
srvReceiveMessages(data:String)
?«interface?»
IBC_ServerCtrl
123 2.7 Realizing Use Cases
By way of example, we have added the navigation subsystem in Figure 2.80 , which
we would normally fi nd only later when looking at the pertaining use cases. We
have described the domain fl ows in activity diagrams. We have now identifi ed the
system structures and modeled them in block diagrams. The allocate relationship
brings the two models together and answers this question: Which action of an
activity is executed on which block?
There are several possibilities to visualize this relation.
Pages:
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270