Module4-1RD_REQM(2h)需求开发与需求管理.pptVIP

Obtain understanding(需求理解) 2013-5-16 S115 Inputs 1 Software requirements Steps 1 PM and stakeholders establish acceptance criteria for defining requirements with appropriate requirement’s providers 2 PM and designated personnel review and analyze the requirements, ensuring that the requirements acceptance criteria is met. 3 PM and all stakeholders hold a meeting to reach sufficient understanding on requirements Exit Criteria 1 The stakeholders understand and commit to the requirements. Control changes（变更流程控制） Inputs 1 The new requirement or requirement change request Steps 1 PM defines which products of this process are to be maintained under configuration control. 2 PM and relevant stakeholders evaluate and document impact of the proposed changes against existing commitments, project plans, current requirements, project activities, and other work products 3 PM, relevant stakeholders and high level management review the changes and make their decisions (approve or disapprove) 4 If changes are approved, relevant stakeholders execute the changes for the impacted work products. 5 CM makes requirements and change data available to the project’s relevant stakeholders Outputs 1 Modified SRS Modified related CI items Change request Form Maintain traceability Entry Criteria 1 Requirements have been understood, Design spec has been reviewed, test plan and test case have been reviewed Steps 1 The requirements have been understood and the commitment to requirements has been obtained, PM establishes the requirement traceability matrix form and fills in the function ID and relevant requirement ID 2 Designers fill in the relevant Design spec ID 3 QA manager fills in the relevant test plan and test case ID 4 Developers fill in the relevant code ID 5 PM maintains the Requirement Traceability Matrix Exit Criteria 1 The Requirement Traceability Matrix Form is established and maintained Identify inconsistencies Entry Criteria 1 Requirements are documented and understood or re