Books for you

Example: Train passenger.
uc Actor generalization
Service system
{abstract}
Maintenance
system
Configuration
system
Change soft
drink data
{abstract}
FIGURE 3-33
Example for an actor generalization.
173
3.5.3 Include Relationship
3.6 The Activity Diagram
FIGURE 3-34
Example for an include relationship.
End car usage ?«continuous?»
Show car usage data
?«secondary?»
Determine car
usage data
?«include?»
uc Secondary use cases car usage
?«include?»
Defi nitions
An include relationship describes that a use case is included in another use
case.
This relationship is used to enable writing only once flows that occur in more
than one use case. However, a flow occurring several times is hardly ever a fully
fledged use case. In such a use case, the domain trigger, the result, or the actor do
not exist or correspond to the use case definition of our approach. This is the reason
why this type of use cases is marked with the stereotype ?«secondary?» . This
is an extension of UML introduced by the SYSMOD profile. UML itself does not
know this differentiation.


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