南台科技大学.ppt

第三章Maturity Level 2:Managed Process Areas 南台科技大學 資管系陳炳文、吳敏南 編 Table of Contents 需求管理(REQM) 專案規劃(PP) 專案監控(PMC) 供應商協議管理(SAM) 度量與分析(MA) 流程與產品品質保證(PPQA) 建構管理(CM) QA Maturity Level 2 PAs 需求管理Requirement Management 需求管理(REQM) 目的 需求管理的目的，在於管理專案產品及產品元件的需求，並界定(identify)這些需求與專案計畫及工作產品間的差異(inconsistencies)。 Requirements Must be Documented Simple as a memo Elaborate as multi-volume specifications All changes must be documented, tracked, and verified throughout the life cycle of the system. Barriers to REQM Requirements constantly change. Requirements are changed without appropriate coordination approval. Customers do not always recognize the need to document the requirements. Responsibility for Requirements Management is not clearly established. Where Does REQM Stand? Why Is REQM Important? Requirements management processes manage the requirements of a project to ensure that The correct requirements are identified and the inconsistencies between the requirements and the project plans and work product are resolved. Bidirectional traceability between the requirements and the product/product component are maintained. Any changes to the requirements are documented and the impact to the project are assessed. What Are the Benefits of REQM? Agreement reached from requirements provider and receiver to ensure that the correct requirements are incorporated into the project plan. Requirement changes are effectively managed thru defined process. Traceability maintained between the requirements and the product facilitate the impact evaluation of changes as well as the verification of work-product. Requirements baseline are established as the basis for further product component requirements development. SG 1 管理需求 管理需求，並界定需求與專案計畫及工作產品間之差異 藉由進行下列活動，使專案能全程維護一組必威体育精装版及已核定的需求： 管理所有的需求變更。 維護需求、專案計畫及工作產品間的關係。 界定需求、專案計畫及工作產品間的差異。 採取矯正措施。 SG 1 管理需求 (2) 特定執行方法(specific practice, SP) SP 1.1 瞭解需求 SP 1.2 取得需求承諾 SP 1.3 管理需求變更 SP 1.4 維護需求的雙向追溯性 SP 1.5 界定專案工作與需求間的差異 REQM Context SP 1.1 瞭解需求 瞭解需求 與需求提供者一起瞭