Requirement lifecycle

From CNM Wiki
Jump to: navigation, search

Requirement lifecycle is the cycle through which requirements tend to go through from their collection to implementation.

PhasePhase gateDescription
CollectionStated requirementIdea of a business need is identified.
ConfirmationConfirmed requirementBusiness need is confirmed.
PrioritizationPrioritized requirementImportance of a requirement to the enterprise outcome is assessed and prioritized.
OrganizationOrganized requirementUnderstandable view of a requirement is developed.
ModelModeled requirementRequirement is located on a requirements model confirming its role in satisfying of the business need.
VerificationVerified requirementThe quality of a requirement is confirmed.
ValidationValidated requirementBusiness value of a requirement is confirmed.
ReviewReviewed requirementA requirement is reviewed formally prior to its approval.
ApprovalApproved requirementA requirement is confirmed to be ready for implementation and/or to be included into the requirements baseline.
ImplementationImplemented requirementA 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.

Related lectures