 |
| This artifact specifies conditions or capabilities to which an information technology solution must conform. |
|
|
Purpose
Requirements are documented to gain agreement on:
-
Capabilities needed by a user or organization to solve a problem or to achieve an objective.
-
Constraints that must be satisfied to conform to a contract, standard, or specification
Requirements are used to derive designs, implementations, and tests for these capabilities and constraints.
|
Relationships
| Container Artifact |
|
| Contained Artifacts |
|
Key Considerations
-
A good quality requirement will allow the identification of specific actions, drive clear design and will be one
for which it is possible to measure or design a test or verification procedure for a solution.
-
The understanding of requirements changes over time, and so requirements should be revisited and refined as needed.
-
Customers often need guidance in developing requirements that suit their needs. This guidance may consist of
both what needs capturing and how it should be represented.
-
Requirements typically affect many different downstream artifacts. Some requirements may have an easily
identifiable and relatively localized impact whereas others have a far reaching affect.
|
Tailoring
| Impact of not having |
If this artifact is not used, there is a risk that stakeholders and the development
team will have different expectations of what is being developed. Additionally, without this artifact it is
difficult to determine when the project has been successfully completed. Projects without well defined requirements can
experience ‘scope creep’ causing them to run over schedule without being able to determine the cause of the
overrun.
|
| Representation Options | Requirements can be captured in models, requirements management tools, documents, or combinations of these. |
|
