Difference between revisions of "Requirement lifecycle"
(Created page with "Requirement lifecycle is the cycle through which requirements tend to go through from their collection to Requirements implementation|imp...") |
(No difference)
|
Revision as of 21:09, 21 November 2018
Requirement lifecycle is the cycle through which requirements tend to go through from their collection to implementation.
Phase Phase gate Description Collection Stated requirement Idea of a business need is identified. Confirmation Confirmed requirement Business need is confirmed. Prioritization Prioritized requirement Importance of a requirement to the enterprise outcome is assessed and prioritized. Organization Organized requirement Understandable view of a requirement is developed. Model Modelled requirement Requirement is located on a requirements model confirming its role in satisfying of the business need. Verification Verified requirement The quality of a requirement is confirmed. Validation Validated requirement Business value of a requirement is confirmed. Review Reviewed requirement A requirement is reviewed formally prior to its approval. Approval Approved requirement A requirement is confirmed to be ready for implementation and/or to be included into the requirements baseline. Implementation Implemented requirement A requirement is stored and/or communicated and/or included into the requirements baseline.
- Requirements signoff. Formal approval of a set of requirements by a sponsor or other decision maker.
- Requirements iteration. An iteration that defines requirements for a subset of the solution scope. For example, an iteration of requirements would include identifying a part of the overall product scope to focus upon, identifying requirements sources for that portion of the product, analyzing stakeholders and planning how to elicit requirements from them, conducting elicitation techniques, documenting the requirements, and validating the requirements.
