Use-Case Model Survey
This report describes the use-case model comprehensively, in terms of how the
model is structured into packages and what use cases and actors there are in the
model. If you are using packages, the document shows the model structure
hierarchically. The report can be used to describe the entire use-case model at
- During inception, such as when you have defined the scope of the system.
- During elaboration, such as when the use-case model is more stable.
- During construction, when requirements is complete.
This report is used by various people interested in the use-case model, such
as the customer, users, software architects, use-case authors, designers, use-case
designers, testers, managers, reviewers, and writers.
Introduction to the use-case model.
2. Survey Description
Survey Description of the use-case model.
3. The Use-Case-Model Hierarchy
This section presents the use-case packages hierarchically, explains
the dependencies among them, and shows the content of each package recursively.
If the model has several levels of packages, those at the top-level are
presented first. The packages within these are presented next, and so on, all
the way down to the packages at the bottom of the hierarchy. For each package
- Its Name.
- A Brief Description explaining the package's function and role in the
system. The description must be understandable to any developer who wants to
use the package.
- A list of the use cases owned by the package, including the name and brief
description of each use case.
- A list of actors owned by the package, including the name and brief
description of each actor.
- A list of relationships owned by the package, including the name and brief
description of each relationship.
- A list of the packages directly owned by the package, with each package
presented in the same hierarchical manner as above.
4. Diagrams of the Use-Case Model
Diagrams, primarily use-case diagrams, of the entire use-case model are
included here. Note: These diagrams are not related to the use cases or the
architectural views of the model.
© 1987 - 2001 Rational Software Corporation