¡@ RM
PurposeIntroductory NoyesRelated Process AreasSpecific and Generic GoalsPractice-to-Goal Relationship TableSpecific Practices by Goal

Commitment to PerformAbility to PerformDirecting ImplementationVerifying Implementation

­º­¶
Level 1
Level 2
Level 3
Level 4
Level 5

¡@

¡@

   Introductory Notes

        Requirements management processes manage all requirements received or generated by the       

   project, including both technical and nontechnical requirements as well as those requirements levied on

   the project by the organization. In particular, if the Requirements Development process area is

   implemented, its processes will generate product and product-component requirements that will also be

   managed by the requirements management processes. When the Requirements Management,

   Requirements Development, and Technical Solution process areas are all implemented, their associated

   processes may be closely tied and be performed concurrently. 

        The project takes appropriate steps to ensure that the agreed-upon set of requirements is managed

   to support the planning and execution needs of the project. When a project receives requirements from

   an approved requirements provider, the requirements are reviewed with the requirements provider to

   resolve issues and prevent misunderstanding before the requirements are incorporated into the project¡¦s

   plans. Once the requirements provider and the requirements receiver reach an agreement, commitment 

   to the requirements is obtained from the project participants. The project manages changes to the

   requirements as they evolve and identifies any inconsistencies that occur among the plans, work 

   products, and requirements. 

        Part of the management of requirements is to document requirements changes and rationale and

   maintain bidirectional traceability between source requirements and all product and product-component

   requirements. 

¡@

­º­¶ | RM | PP | PM&C | SAM | M&A | P&PQA | Configuration

¡@