Books for you

We, therefore, use continuous use cases to describe
these types of services.
Activities that describe the fl ow of a continuous use case are also defi ned with
the ?«continuous?» stereotype. Actions that invoke continuous use case activities
( CallBehaviorAction ) show stereotypes in their notation.
You can optionally use the stereotype symbol for continuous use cases. It is an
ellipse with arrows ( Figure 5.12 ).
In our approach, we use continuous use cases in Section 2.4.1 (Figure 2.37),
for example.
A secondary use case characterizes a use case fragment. This is a ??? piece ??? of use
case that has no trigger, no result, or none of the other use case criteria. It is modeled
only if its fl ow is part of several (primary) use cases. This allows us to avoid
redundant descriptions. Include creates a relationship between primary and secondary
use cases.
Activities that describe the fl ow of a secondary use case are also defi ned with
the ?«secondary?» stereotype, as are actions that invoke secondary use case activities
( CallBehaviorAction ).


Pages:
479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503