Concept · entity · registered
Use case
A description of how an actor reaches a goal by interacting with a system, including the main sequence and the alternatives. The actor may be a person, an organization, or another system. A use case is not a user story. The story is one backlog increment, while the use case is the interaction and can span more than one increment. It is not one of the requirement classes, though it may be written to show how requirements are met. It is not a business process. A business process is how the organization does a piece of work, whether or not that work is one session with a system.
Definition
What Use case means
Used in data
In OVDB databases
Databases, recordsets and fields whose meaning is this concept, a kind of it, or whose values are instances of it. Rows open the OVDB Directory.
No OVDB database carries this concept yet.
Properties
What we can say about Use case
These properties describe meanings and reference targets. Storage types, required fields, and cardinality belong to the consuming data model.
| Property | Meaning | Values and units |
|---|---|---|
| Use case actor | The name of an actor in the use case. The actor may be a person, an organization, or another system, so this attribute is the name in the narrative rather than a reference to one kind of party. An actor need not be a stakeholder, because another system can be an actor, and need not be the only stakeholder of the requirements the use case touches. | Scalar meaning |
| Use case requirement | A requirement this use case shows being met. The use case can touch several requirements, and a requirement can be met without a use case being written. | Values reference Requirement |