Checklist: Use-Case Model |
This checklist provides questions to verify that the Use-Case Model is described in a consistent and complete manner.
Relationships
Related Elements | Use Case Model
Check Items
Is the introduction clear, concise and complete
The Introduction section provides a clear, concise and complete overview of the purpose and functionality of the system.
Is it easy to understand what the system does by reviewing the model
There are no long chains of include and extend relationships, such as when an included use case is extended, or when an extended use case includes other use cases. These can obscure comprehensibility. There are minimal cross-dependencies where an included, extending, or specialized use case must know about the structure and content of other included, extending or specialized use cases.
Have all use cases have been identified
The use cases identified collectively account for all required behavior of the system. All features identified in the Vision document for this iteration have been addressed by at least one use case. All non-functional requirements that must be satisfied by a specific use cases have been captured in those use cases The use-case model contains no superfluous behavior (gold-platting).
Are all relationships between use cases required
There is a justification for all include-, extend- and generalization relationships
Are use case packages used appropriately
Cross-package dependencies have been reduced or eliminated to prevent model ownership conflicts Packaging is intuitive and makes the model easier to read
Do all model elements have appropriate names
Each use case should have a name that indicates what is achieved by its interaction with the actor(s). No two use cases can have the same name. Each actor has a name that effectively describes the role.
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. View copyright information here: OpenUP Copyright