This means that your system
is part of another system??”a system of systems ( SoS ).
The elements at the model transitions may play various roles. For example, the
block card reader of our on-board computer system could be an independent system
from the view of another project. In this case, it plays two roles that are both
realized by the same model element??”the block. This means that you can simply
model both roles by using two stereotypes ( ?«block?» and ?«system?» ), which are
shown or hidden, respectively, in the respective context. Things are a bit harder
for the on-board computer control , which is a block in the on-board computer
system and an actor in the card reader system. These are different model elements.
This means that the on-board computer control exists twice in the entire
model. We use the trace relationship to ensure that we won ??™ t lose sight of the difference
of these elements.
FIGURE 2-92
A test environment.
ibd [block] Test on-board computer access system [TC42]
values
sn:IDbc2342
testBC1:[on-board computer]
values
sn:IDkl32X27
reading device:
[card reader]
values
card#:CardID3725
cus#:CustomerID2936
pinCheckCode:String???x4637a???
name???Gabi Goldfish???
card:[customer card]
values
sn:IDctrlOO79
bcCtrl:[on-board computer
control]
135 2.
Pages:
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289