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

¡@

                                                             

   Specific Practices by Goal

    SG 1    Manage Requirements 

     The project maintains a current and approved set of requirements over the life of the project by doing the following : 

         ¡EManaging all changes to the requirements

         ¡EMaintaining the relationships between the requirements, the project plans, and the work products

         ¡EIdentifying inconsistencies between the requirements, the project plans, and the work products

         ¡ETaking corrective action

¡@

    Refer to the Technical Solution process area for more information about determining the feasibility of the requirements.  

    Refer to the Requirements Development process area for more information about ensuring that the requirements reflect

    the needs and expectations of the customer. Refer to the Project Monitoring and Control process area for more

    information about taking corrective action.

   

      For Software Engineering

      The requirements may be a subset of the overall product requirements, or they may constitute the entire product

      requirements. 

      For Systems Engineering

      Each level of product-component design (e.g., segment, subsystem) receives the requirements from the higher level. 

¡@

¡@


¡@

¡@

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

¡@