Prev | Current Page 335 | Next

Tim Weilkiens

"Systems Engineering with SysML/UML: Modeling, Analysis, Design"


Actors can have only few relationships among them. Since they are outside the
system, which means that they are not within the modeling focus, there is little
need to examine the relations between actors in detail.
Table 3.2 The use case ???buy soft drink???.
Description of use case
Name: Buy soft drink.
Trigger: A customer selects a soft drink at a
vending machine.
Result: The vending machine dispensed
the selected drink and booked the
corresponding amount of money.
Actors: Customer, card reader, communication
unit.
Short description: A selected drink is dispensed.
Payment is effected by a chip card
that is read and rewritten by a card
reader. Headquarters may be informed
about the fi lling status of the vending
machine via SMS.
Essence: Select soft drink.
Pay for soft drink.
Remove soft drink.
Transmit vending machine status.
uc Multiplicity
Manager
Open safe
2
FIGURE 3-32
Example for multiplicity.
3.5 The Use Case Diagram
172 CHAPTER 3 UML??”Unifi ed Modeling Language
A relationship that is permitted between actors is a generalization (a ??? is a kind
of ??? relationship).


Pages:
323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347