Use case

Written by

·

1. Actor – Role(s) external parties that interact with the system
2. Use Case – A sequence of actions that the system performs that yields an observable result of value to an actor.
3. Use Case Model – Bag that contains
–Actors list, packages, diagrams, use cases, views

Relationships

  • Organize use cases by grouping them in packages as in the organization of classes
  • Generalization: The child use case exhibits a more specific variation in behavior than as specified for its parent
  • Include: Common behaviour of more than one use case is
    referenced as a separate instance to avoid repetition
  • Extend: Implicit integration of the behavior of another use
    case by declaring the extension points / events in the base

The <<include>> relationship means that the flow of that use case is always included.
But a <<extend>> relationship means that the flow of the extending use case is only
included under specific conditions, which must be specified as the extension point of the
use case being extended.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.