Concept · entity · registered
Requirement
A usable representation of a need. The classes are a business requirement, which states why a change has been initiated, a stakeholder requirement, which states what a stakeholder needs so that can be achieved, a solution requirement, which states a capability or quality of the solution as a functional or non-functional requirement, and a transition requirement, which is needed only while moving to the new state. A user story is a delivery work item whose text often represents a stakeholder need. The story and this requirement are linked when both are recorded, and they are not the same record. A use case narrates an interaction and is not one of these classes. An acceptance criterion is a condition for accepting a story, a requirement, or a service. Work that delivers the requirement is a work item, linked from the requirement.
Definition
What Requirement 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 Requirement
These properties describe meanings and reference targets. Storage types, required fields, and cardinality belong to the consuming data model.
| Property | Meaning | Values and units |
|---|---|---|
| Requirement business rule | A business rule this requirement is meant to uphold. The rule can outlive the requirement, and the requirement is not the rule. | Values reference Business rule |
| Requirement priority | How important this requirement is relative to others. One scheme is MoSCoW, which sorts requirements into must, should, could and won't. That is a priority classification. It does not grade the severity of a running failure or of a defect. A rank or another local scheme uses this same attribute. The scheme is not fixed here, and priority is not status. | Scalar meaning |
| Requirement source | A stakeholder who raised or owns this requirement. The source is not the user in every user story written from it. | Values reference Stakeholder |
| Requirement status | Where this requirement sits between being proposed and being satisfied or dropped. The state names belong to the practice. Status is not priority. | Scalar meaning |
| Requirement work item | A work item that delivers or checks this requirement. The link connects the recorded need to the delivery work. The work item does not replace the requirement, and a requirement can be met by more than one work item. | Values reference Work item |
In the graph
Related concepts
Kinds of this concept
A requirement that states the goals, objectives, and outcomes for why a change has been initiated. It can apply to the whole organization, a business area, or one initiative. It…
A requirement that states a capability or a quality the solution must have to meet the stakeholder requirements, in enough detail to build and implement the solution. A functional…
A requirement that states what a stakeholder needs so the business requirements can be achieved. It bridges business requirements and solution requirements. It is not a business…
A requirement that states a capability or condition needed only to move from the current state to the future state, such as converting data, training people, or keeping work going…
Concepts whose values are instances of it
A requirement this condition is a check for, when it is attached to a requirement rather than only to a story.
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.