CMMI-DEV V1.3 项目管理过程域.pptVIP

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * State the purpose of Requirements Management. Emphasize the two elements: Manage requirements Identify inconsistencies Point out that a good project will align requirements, plans, and work products, but that occasionally inconsistencies will materialize. Explain that according to the introductory notes, the scope of Requirements Management covers the management of requirements for products and services. The term “requirements” refers to product or product component requirements that are received by or generated by the project. Reminder - Throughout the process areas, where we use the terms product and product component, they are intended to include service and service component and should be interpreted in that way. All requirements should be objective and verifiable. After mutual agreement between the project and its relevant stakeholders, which is part of the Requirements Development PA, the requirements are used to plan the project’s activities and develop work products. The term “requirements” refers to product and product component requirements that are received by or generated by the project, including those requirements levied on the project by the organization. The requirements are both technical and non-technical. This process area does not address the development of requirements; but their management only. 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. Point out the last paragraph under Introductory Notes that describes how requirements changes would appear in a maintenance activity. Explain the distinction between the management of requirements, and requirements elicitation or requirements analysis. * Discuss what can happen when Requirements Management is not implemented well. Ask participants about their experiences. Ask participants what the benefits of good Requireme