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...") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Requirement lifecycle]] is the cycle through which [[requirement]]s tend to go through from their [[Requirements collection|collection]] to [[Requirements implementation|implementation]].<blockquote><table class="wikitable" width=100% style="text-align:center;"><tr><td>[[Requirement life-cycle phase|Phase]]</td><th>[[Phase gate]]</th><th>Description</th></tr><tr><th>[[Requirements collection|Collection]]</th><td>[[Stated requirement]]</td><td>Idea of a [[business need]] is identified.</td></tr><tr><th>[[Requirements confirmation|Confirmation]]</th><td>[[Confirmed requirement]]</td><td>[[Business need]] is confirmed.</td></tr><tr><th>[[Requirements prioritization|Prioritization]]</th><td>[[Prioritized requirement]]</td><td>Importance of a [[requirement]] to the [[enterprise outcome]] is assessed and prioritized.</td></tr><tr><th>[[Requirements organization|Organization]]</th><td>[[Organized requirement]]</td><td>Understandable view of a [[requirement]] is developed.</td></tr><tr><th>[[Requirements model|Model]]</th><td>[[ | + | [[Requirement lifecycle]] is the cycle through which [[requirement]]s tend to go through from their [[Requirements collection|collection]] to [[Requirements implementation|implementation]].<blockquote><table class="wikitable" width=100% style="text-align:center;"><tr><td>[[Requirement life-cycle phase|Phase]]</td><th>[[Phase gate]]</th><th>Description</th></tr><tr><th>[[Requirements collection|Collection]]</th><td>[[Stated requirement]]</td><td>Idea of a [[business need]] is identified.</td></tr><tr><th>[[Requirements confirmation|Confirmation]]</th><td>[[Confirmed requirement]]</td><td>[[Business need]] is confirmed.</td></tr><tr><th>[[Requirements prioritization|Prioritization]]</th><td>[[Prioritized requirement]]</td><td>Importance of a [[requirement]] to the [[enterprise outcome]] is assessed and prioritized.</td></tr><tr><th>[[Requirements organization|Organization]]</th><td>[[Organized requirement]]</td><td>Understandable view of a [[requirement]] is developed.</td></tr><tr><th>[[Requirements model|Model]]</th><td>[[Modeled requirement]]</td><td>[[Requirement]] is located on a [[requirements model]] confirming its role in satisfying of the [[business need]].</td></tr><tr><th>[[Requirements verification|Verification]]</th><td>[[Verified requirement]]</td><td>The quality of a [[requirement]] is confirmed.</td></tr><tr><th>[[Requirements validation|Validation]]</th><td>[[Validated requirement]]</td><td>[[Business value]] of a [[requirement]] is confirmed.</td></tr><tr><th>[[Requirements review|Review]]</th><td>[[Reviewed requirement]]</td><td>A [[requirement]] is reviewed formally prior to its approval.</td></tr><tr><th>[[Requirements approval|Approval]]</th><td>[[Approved requirement]]</td><td>A [[requirement]] is confirmed to be ready for implementation and/or to be included into the [[requirements baseline]].</td></tr><tr><th>[[Requirements implementation|Implementation]]</th><td>[[Implemented requirement]]</td><td>A [[requirement]] is stored and/or communicated and/or included into the [[requirements baseline]].</td></tr></table></blockquote>[[File:Requirement-lifecycle.png|400px|thumb|right|[[Requirement lifecycle]]]] |
*[[Requirements signoff]]. Formal approval of a set of requirements by a sponsor or other decision maker. | *[[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. | *[[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. | ||
| − | ==Related | + | ==Related lectures== |
*[[Business Analysis Quarter]]. | *[[Business Analysis Quarter]]. | ||
[[Category: Septem Artes Administrativi]][[Category: Articles]] | [[Category: Septem Artes Administrativi]][[Category: Articles]] | ||
Latest revision as of 20:42, 1 April 2020
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 Modeled 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.
