| Work Product (Artifact): Use Case Document |
| |
 |
| The Use Case Document will describe how a users will perform tasks. |
|
Relationships
| Input To | Mandatory:
| Optional:
| External:
|
Main Description
| The use case document contains a sequence of actions that describes a way in which an actor (user) interacts with a system
with the objective of achieving a particular goal. The use case document focuses on the users of the system thus the real
system needs are brought to light early on. Since a use case consists mainly of narrative text, it is easily understandable
by all stakeholders, including customers, users and executives, not just developers and testers. It provides basic
groundwork for the requirements document, user manual and test cases. Use cases also encourage designers to envision
outcomes before attempting to specify outcomes. |
Properties
| Optional |  |
| Planned | |
Illustrations
Tailoring
| Impact of not having | Without a use case, It is difficult to establish a common understanding of how an actor interacts with a system. Because
the desired outcome may not be clearly defined in the Functional requirements but rather in a Use case, it may be difficult
to establish a test criterion. |
| Reasons for not needing | The Use Case is not used for systems design, User Interface design, feature lists, or testing (they are not test plans or
test cases). |
Version and Release
Unified Life Cycle (ULC): 5.1, November 3, 2014
Phase Gates: 1.1, May 27, 2014
Process Engineering Process (PEP): 1.1, May 27, 2014
|
|
