¡@ 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

¡@

                                                             

   Directing Implementation

    GP 2.6  (DI 1)  Manage Configurations

Place designated work products of the requirements management process under appropriate levels of configuration management. 

     Elaboration :

¡@

          Examples of work products of the requirements management process under appropriate

          levels of configuration management.

¡@

      GP 2.7  (DI 2)  Identify and Involve Relevant Stakeholders

Identify and involve the relevant stakeholders of the requirements management process as planned. 

      Elaboration :

      Select relevant stakeholders from customers, end users, developers, producers, testers, suppliers,      

      marketers, maintainers, disposal personnel, and others who may be affected by, or may affect, the

      product as well as the process. 

¡@

¡@

     

            Examples of activities for stakeholder involvement include :

                ¡EResolving issues on the understanding of the requirements

                ¡EAssessing the impact of requirements changes

                ¡ECommunicating the bidirectional traceability

                ¡EIdentifying inconsistencies among project plans, work products and requirements

¡@

     

       GP 2.8  (DI 3)  Monitor and Control the Process

Monitor and control the requirements management process against the plan for performing the process and take appropriate corrective action.

          Elaboration :

        

               Examples of measures used in monitoring and controlling include the following:

                ¡ERequirements volatility (percentage of  requirements changed)

 

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

¡@