Prev | Current Page 333 | Next

Tim Weilkiens

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


Bingo!
A use case describes only that a service is present. The service itself is
described by an activity, for example. The relation between use case and activity
cannot be represented in a diagram. However, the relationship exists in the model.
It is up to the modeling tool you use to visualize the relation.
You do not necessarily have to represent the concept of use cases in UML. You
can alternatively work with text documents ( Table 3.2 ). The most important things
are the concept and a standardized fi ling of information, and not the notation.
3.5.2 Actor
uc Generalization
Change soft
drink data
{abstract}
Service system
Delete soft
drink data
Modify soft
drink data
FIGURE 3-31
Use case generalization.
Defi nition
An actor is a role that interacts with the system. The role can be assumed by
an individual or by an external system. An actor is outside the system.
Actors represent users of the system as well as users outside the system which
are, in turn, used by the system.
The UML notation uses the stick man for an actor.


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