項(xiàng)目管理計(jì)劃書(shū)模板

1、Co. Lt有限公司Product version 產(chǎn)品版本Confidentiality level密級(jí)Project ID 工程IDTotal pages：共26頁(yè)XX Project PlanXX工程計(jì)劃Prepared by 擬制Date日期yyyy-mm-ddReviewed by 審核Date日期yyyy-mm-ddApproved by批準(zhǔn)Date日期yyyy-mm-ddRevision record 修訂記錄Date日期Revision version修訂版本修訂記錄的修訂版本請(qǐng)按1.00、1.01、1.02.進(jìn)行填寫(xiě) Revised release should be log

2、ged as 1.00, 1.01, 1.02Description描述每次修訂的詳細(xì)內(nèi)容，例如在哪個(gè)地方有過(guò)修訂，都要有明確說(shuō)明。Describe detailed contents of each modification, e.g. Where was revised. 描述Author作者2001-06-081.00initial 初稿完成name 作者名yyyy-mm-dd1.01revised xxx 修改XXXname 作者名yyyy-mm-dd1.02revised xxx 修改XXXname 作者名yyyy-mm-dd2.00revised xxx 修改XXXname 作者名

3、Distribution LIST 分發(fā)記錄Copy No.Holder's Name & Role 持有者和角色I(xiàn)ssue Date 分發(fā)日期1< RDPDT >yyyy-mm-dd2<Project Manager>yyyy-mm-dd3<Team members>yyyy-mm-dd4<Customer Representative>yyyy-mm-dd5<Others>yyyy-mm-ddCatalog目錄1 1 Introduction 簡(jiǎn)介7.1 1.1Purpose 目的7.2 1.2Scope 范圍7.

4、3 1.3References 參考資料72 2Resource Summary資源概述73 3Project specific software Processes 工程特定的軟件過(guò)程84 4 Project Scope工程范圍85 5 Deliverables交付件8.4 5.1 Customer Deliverables給客戶的交付件8.5 5.2 Internal Deliverables內(nèi)部交付件86 6 Organization and Responsibilities組織和職責(zé)87 7 Estimated Size /Effort/schedule規(guī)模/工作量/進(jìn)度的估計(jì)10.6

5、 7.1Estimated size估計(jì)的規(guī)模10.7 7.2Estimated effort估計(jì)的工作量10.8 7.3Estimated schedule估計(jì)的進(jìn)度118 8 Project resource required 工程所需資源11.9 8.1Equipment Requirement 設(shè)備需求11.10 8.2Software tools 軟件工具11.11 8.3Documents 文檔資料12.12 8.4Customer Supplied Products 需要客戶提供的產(chǎn)品12.13 8.5Staffing 人員需求12.14 8.6Travel 差旅129 9 Pr

6、oject Schedule 工程進(jìn)度1310 10 Work Products工作產(chǎn)品1311 11 Outsourced Task外包任務(wù)14.15 11.1 Subcontractor Profile子承包商資料14.16 11.2 Scope of the Outsourced task 外包任務(wù)的范圍14.17 11.3 Milestone, Receivables & Deliverables 里程碑、交付件1412 12 Acceptance Criteria驗(yàn)收標(biāo)準(zhǔn)1413 13 Quality Plan 質(zhì)量計(jì)劃15.18 13.1 Process Deviation

7、 過(guò)程偏差15.19 13.2 Quality Goal質(zhì)量目標(biāo)15.20 13.3 Plan to achieve the Quality Targets & Contingency達(dá)到質(zhì)量目標(biāo)的計(jì)劃及應(yīng)急措施16.1 13.3.1 Plan to achieve the Quality Targets達(dá)成質(zhì)量目標(biāo)的計(jì)劃16.2 13.3.2Contingency Plan應(yīng)急計(jì)劃17.21 13.4 Quality Assurance Activities 質(zhì)量保證活動(dòng)17.22 13.5 Quality Control Activities 質(zhì)量控制活動(dòng)1814 14 Defec

8、t Prevention 缺陷預(yù)防18.23 14.1 Defect Prevention Plan 缺陷預(yù)防計(jì)劃1815 15 Project Control 工程控制19.24 15.1 Project Reports 工程報(bào)告19.25 15.2 Project Team Meeting 工程組會(huì)議1916 16 Reuse Component Management 重用構(gòu)件管理20.26 16.1 Existing components 現(xiàn)有構(gòu)件20.27 16.2 New components 新增構(gòu)件2017 17 Configuration Management 配置管理2018

9、 18 Criteria for updating Project plan 工程計(jì)劃的修訂2019 19 Assumptions 假定2120 20Dependencies 依賴關(guān)系2121 21 Issues問(wèn)題2222 22 Customer involvement客戶的參與2223 23 Risk Management風(fēng)險(xiǎn)管理2224 24 Training 培訓(xùn)22Table of contents for the table表目錄Table 1 XX 表1 XX6Table of contents for the figure圖目錄Figure 1 XX 圖 1 XX7XX Pro

10、ject PlanXX工程計(jì)劃Keywords 關(guān)鍵詞：Abstract 摘要：List of abbreviations 縮略語(yǔ)清單：Acronym術(shù)語(yǔ)Definition定義SOWStatement Of Work 工作任務(wù)書(shū)QAQuality Assurance Engineer QARATRisk Analysis Tool風(fēng)險(xiǎn)分析工具1 Introduction 簡(jiǎn)介1.1 Purpose 目的This section should state the purpose of the document. It could also specify the intended audien

11、ce. 矚慫潤(rùn)厲釤瘞睞櫪廡賴。這部分要描述文檔的目的，應(yīng)該指明讀者。1.2 Scope 范圍< Describe the scope of the this Project Plan . Identify the various items this document addresses. >聞創(chuàng)溝燴鐺險(xiǎn)愛(ài)氌譴凈。<描述工程計(jì)劃的范圍，明確文檔涉及的各項(xiàng)內(nèi)容>< This document addresses本文檔解決以下問(wèn)題：The project planning activities to be done and its objective殘騖樓諍錈瀨濟(jì)溆塹

12、籟。工程的計(jì)劃完成的活動(dòng)及其目標(biāo)The quality plan adopted for the project工程采用的質(zhì)量計(jì)劃Deliverables of the project工程的交付件Roles and responsibilities of people involved所有相關(guān)的角色和職責(zé)Schedule of the project工程進(jìn)度Configuration Management for the project工程的配置管理Risk Management for the project工程的風(fēng)險(xiǎn)管理>1.3 References 參考資料Doc ID參考資料編號(hào)

13、Name of the referred document參考資料名稱1 Resource Summary資源概述Total Estimated Effort (in person days)估計(jì)的總工作量Proposal Cost (if available)建議成本(如果可以提出)Proposed Project Start Date建議工程起始時(shí)間Development Completion Date開(kāi)發(fā)結(jié)束時(shí)間Support Completion Date (if applicable)支持結(jié)束時(shí)間(如果有)Remarks, if any.說(shuō)明2 Project specific so

14、ftware Processes 工程特定的軟件過(guò)程The project shall conform to the Life Cycle Model and the Processes defined in the Process Handbook, < Provide the document ID and link to the Process Handbook. >釅錒極額閉鎮(zhèn)檜豬訣錐。工程應(yīng)該與生命周期模型和過(guò)程手冊(cè)中定義的過(guò)程保持一致<提供文檔ID并通過(guò)鏈接方式指向過(guò)程手冊(cè)>。3 Project Scope工程范圍< The project's

15、 purpose, scope, goals, and objectives. >彈貿(mào)攝爾霽斃攬磚鹵廡。<工程的目的、范圍、目標(biāo)。>4 Deliverables交付件1.1 Customer Deliverables給客戶的交付件< List down all the external deliverables i.e. deliverables to the customer as per the SOW/Allocated Requirements. > 謀蕎摶篋飆鐸懟類(lèi)蔣薔。<羅列所有對(duì)外的交付件，如在工作任務(wù)書(shū)或分配需求中要求的交付件>>

16、1.2 Internal Deliverables內(nèi)部交付件< List down all the Internal Deliverables, i.e. deliverables which are not necessary a delivered to the customer, but produced during the project life cycle >廈礴懇蹣駢時(shí)盡繼價(jià)騷。<羅列所有的內(nèi)部交付件，如不必要給客戶，但是在生命周期內(nèi)產(chǎn)生的。>2 Organization and Responsibilities組織和職責(zé)The table below

17、identifies the roles and the name involved in the project. 煢楨廣鰳鯡選塊網(wǎng)羈淚。下表定義了工程組涉及到的角色和名稱。The Project Manager before the start of the review will identify reviewers for all documents and code. 鵝婭盡損鵪慘歷蘢鴛賴。在review之前PM需指定所有文檔和代碼的reviewers。For the responsibility of these roles, please refer to the Org. Ma

18、nual of Huawei.籟叢媽羥為贍僨蟶練淨(jìng)。這些角色的職責(zé)，請(qǐng)參考華為的組織手冊(cè)The below table shall be revisited at least at the end of every Phase/Stage.預(yù)頌圣鉉儐歲齦訝驊糴。在每個(gè)階段結(jié)束時(shí)要檢查下表的內(nèi)容。The changes to the team organization in-between the phase will be communicated to all concerned by the Project Manager through mail and later updated in

19、 the Project Plan at every phase.滲釤嗆儼勻諤鱉調(diào)硯錦。在階段之間如果對(duì)工程組的結(jié)構(gòu)進(jìn)行了改變，由PM通過(guò)mail通知所有相關(guān)人員，并在以后每個(gè)階段的工程計(jì)劃中更新。鐃誅臥瀉噦圣騁貺頂廡。Sl. No.Role Including additional roles, if any. 如果有其他角色，請(qǐng)包括進(jìn)角色Name姓名Reporting To來(lái) Mention the abbreviated Role only (e.g. PM etc.) 以角色縮寫(xiě)名填寫(xiě)（如PM等向誰(shuí)報(bào)告Backup resource備份資源1Customer Representativ

20、e客戶代表NA2PDT R&D RepresentativePDT開(kāi)發(fā)代表3Project ManagerPM4QA5Metrics Coordinator 度量協(xié)調(diào)員6Test Coordinator 測(cè)試協(xié)調(diào)員7Risk Officer 風(fēng)險(xiǎn)管理員8Project Consultant(s)工程顧問(wèn)9Configuration Librarian配置管理員10Team Members工程組成員11Change Control Board變更控制委員會(huì)（CCB）<PDT R&D Representative><PDT開(kāi)發(fā)代表>NANA<PM>

21、;<PM><QA>.12Technical Reviewers, if available技術(shù)reviewers13Affected groups相關(guān)小組1 Estimated Size /Effort/schedule規(guī)模/工作量/進(jìn)度的估計(jì)1.1 Estimated size估計(jì)的規(guī)模No. of estimationEstimated size in KLOC(NBNC)Initial estimationRe-estimation1Re-estimation2Re-estimation31.1 Estimated effort估計(jì)的工作量 TaskDistrib

22、ution(%)Initial estimationRe-estimation1Re-estimation2Re-estimation3PPL工程計(jì)劃SRS需求規(guī)格STP系統(tǒng)測(cè)試計(jì)劃UM用戶手冊(cè)HLD概要設(shè)計(jì)ITP集成測(cè)試計(jì)劃LLD詳細(xì)設(shè)計(jì)UTP單元測(cè)試計(jì)劃CODE編碼UT單元測(cè)試IT集成測(cè)試ST系統(tǒng)測(cè)試TRG培訓(xùn)PM工程管理QA質(zhì)量保證CM配置管理IGC組間協(xié)調(diào)TOTAL合計(jì)1.1 Estimated schedule估計(jì)的進(jìn)度 PhaseInitial estimationRe-estimation1Re-estimation2Re-estimation3Start DateEnd Dat

23、eStart DateEnd DateStart DateEnd DateStart DateEnd DatePLANSRSHLDLLDCODINGUTITST1 Project resource required 工程所需資源1.1 Equipment Requirement 設(shè)備需求< List down the hardware requirements for the project e.g. specific hardware platform, test equipment, which is considered as "critical computer res

24、ource" etc., 羅列工程開(kāi)發(fā)需要的硬件資源，如特殊的硬件平臺(tái)、測(cè)試設(shè)備等。標(biāo)準(zhǔn)的辦公硬件不必在這里列。>擁締鳳襪備訊顎輪爛薔。Sl.No.Description描述Qty.數(shù)量Start Date起始日期End Date結(jié)束日期Remarks說(shuō)明123451.1 Software tools 軟件工具< List down the software required for the project e.g. Linux, Clearcase license, etc., 列出工程需要的軟件或軟件license，例如Linux、Clearcase license等

25、。標(biāo)準(zhǔn)的辦公軟件不必在這里列。>贓熱俁閫歲匱閶鄴鎵騷。Sl. No.Description描述Qty.數(shù)量Start Date起始日期End Date結(jié)束日期Remarks說(shuō)明1< Mention the software details, including versions etc., 軟件描述，包括版本等>23451.1 Documents 文檔資料< List down the documents, books, and papers to be purchased for the project羅列工程需要的文檔資料、書(shū)籍、論文等>壇摶鄉(xiāng)囂懺蔞鍥鈴氈淚。

26、Sl. No.Description描述Qty.數(shù)量Start date起始日期Est. Cost估計(jì)成本Remarks說(shuō)明12341.1 Customer Supplied Products 需要客戶提供的產(chǎn)品< List down any existing customer supplied products required for the development, integration or testing of the project羅列開(kāi)發(fā)、集成、測(cè)試中需要用戶提供的產(chǎn)品> 蠟變黲癟報(bào)倀鉉錨鈰贅。Sl. No.Description描述Qty.數(shù)量Start date

27、起始日期End date結(jié)束日期Remarks說(shuō)明12341.1 Staffing 人員需求< List down the human resource requirement with required skills for the project 羅列工程需要的人力資源及技能要求>買(mǎi)鯛鴯譖曇膚遙閆擷凄。Sl. No.Designation資源名稱Number人數(shù)Start date起始日期End date結(jié)束日期Required skill技能要求Remark說(shuō)明12341.1 Travel 差旅Sl.No.Travel Description差旅描述Number次數(shù)Expec

28、ted Date預(yù)計(jì)時(shí)間Remarks說(shuō)明1234< List down the software hardware requirements for the project e.g. computer etc. ><羅列工程開(kāi)發(fā)需要的軟硬件資源，如計(jì)算機(jī)等>綾鏑鯛駕櫬鶘蹤韋轔糴。Sl.No.Description描述Qty.數(shù)量Start Date起始日期End Date結(jié)束日期Remarks說(shuō)明123451 Project Schedule 工程進(jìn)度Major milestones of the project is listed below:將工程的主要里程碑列在

29、下表中：驅(qū)躓髏彥浹綏譎飴憂錦。Phase階段Estimate Start date 估計(jì)開(kāi)始日期Estimate finish date估計(jì)結(jié)束日期Responsibility責(zé)任人 SRS Phase軟件需求階段yyyy-mm-ddyyyy-mm-ddProject ManagerPMHLD Phase概要設(shè)計(jì)階段yyyy-mm-ddyyyy-mm-dd<Team Member><工程組成員>LLD Phase詳細(xì)設(shè)計(jì)階段yyyy-mm-ddyyyy-mm-dd<Team member><工程組成員>Coding Phase編碼階段yyyy-m

30、m-ddyyyy-mm-dd<Team member><工程組成員>Unit Testing Phase單元測(cè)試階段yyyy-mm-ddyyyy-mm-dd<Team member><工程組成員>Integration Testing Phase集成測(cè)試階段yyyy-mm-ddyyyy-mm-dd<Team member><工程組成員>System Testing Phase系統(tǒng)測(cè)試階段yyyy-mm-ddyyyy-mm-dd<Team member><工程組成員>Release and Accep

31、tance發(fā)布和驗(yàn)收yyyy-mm-ddyyyy-mm-ddProject ManagerPMOther, if any其它yyyy-mm-ddyyyy-mm-ddProject ManagerPMRefer to the Gantt chart for detailed schedule. < Give reference to WBS (Microsoft Project Plan) here. > Project manager will update the Gantt chart every week, and the activities will be tracked

32、 through Gantt chart. 貓蠆驢繪燈鮒誅髏貺廡。進(jìn)度細(xì)節(jié)請(qǐng)參考Gantt圖。<給出WBS的參考位置（Microsoft Project Plan）>。PM應(yīng)該每周更新Gantt圖，通過(guò)它來(lái)跟蹤活動(dòng)。鍬籟饗逕瑣筆襖鷗婭薔。1 Work Products工作產(chǎn)品< List down the Approver and Authorizer for each work product. Note that only planning documents and management documents need to be authorized. >構(gòu)氽頑黌

33、碩飩薺齦話騖。<列出每個(gè)工作產(chǎn)品的批準(zhǔn)人和簽發(fā)人，注意只有計(jì)劃文檔和管理文檔需要簽發(fā)。>Work Product工作產(chǎn)品Approver (Name & Role)批準(zhǔn)者（名字和角色）Authorizer (Name & Role)簽發(fā)者（名字和角色）1 Outsourced Task外包任務(wù)< This is applicable if any part of the project is outsourced to subcontractor >輒嶧陽(yáng)檉籪癤網(wǎng)儂號(hào)澩。<本部分僅當(dāng)工程中有外包時(shí)適用>1.1 Subcontractor Pr

34、ofile子承包商資料Subcontractor's Name子承包商名Contact Person聯(lián)系人Address for communication通訊地址<Others><其它>1.1 Scope of the Outsourced task 外包任務(wù)的范圍< Specify the scope of the work from the project outsourced to subcontractor. This could be specified as Features, requirements, modules etc. >堯

35、側(cè)閆繭絳闕絢勵(lì)蜆贅。<指明工程外包給子承擔(dān)商的工作內(nèi)容，可以采用特性、需求、模塊等來(lái)說(shuō)明>1.2 Milestone, Receivables & Deliverables 里程碑、交付件< Specify the agreed Milestones, Receivables & Deliverables by the subcontractor >識(shí)饒鎂錕縊灩筧嚌儼淒。<指明協(xié)商后確定的子承包商的里程碑、交付件>Milestone里程碑Work Product issued to subcontractor分配給子承包商的工作產(chǎn)品Plann

36、ed Start date計(jì)劃開(kāi)始日期Planned finish date計(jì)劃完成日期Deliverables to Huawei Technologies給華為的交付件1 Acceptance Criteria驗(yàn)收標(biāo)準(zhǔn)The acceptance criteria for the customer are that the software meets the requirements stated in the requirement specification document. The system test and the acceptance test will demonstr

37、ate the software's conformance to the requirement specification.凍鈹鋨勞臘鍇癇婦脛糴?？蛻舻尿?yàn)收標(biāo)準(zhǔn)就是軟件應(yīng)滿足在需求規(guī)格文檔中描述的需求。系統(tǒng)測(cè)試和驗(yàn)收測(cè)試將證實(shí)軟件與需求規(guī)格保持了一致。恥諤銪滅縈歡煬鞏鶩錦。< Please mention here any specific acceptance criteria from the customer. The acceptance criteria are based on the need of the customer and so shall be de

38、fined by the customer with the assistance of the project wherever required. Examples could be Nature of deliveries, Quality Objectives, Testing criteria, Post acceptance fault handling, Documentation etc., >鯊腎鑰詘褳鉀溈懼統(tǒng)庫(kù)。<請(qǐng)?jiān)谶@里注明客戶特殊的驗(yàn)收標(biāo)準(zhǔn)。驗(yàn)收標(biāo)準(zhǔn)是基于客戶的需要，所以應(yīng)由客戶來(lái)制定，在需要的時(shí)候由工程組協(xié)助。交付件的屬性如：質(zhì)量目標(biāo)，測(cè)試標(biāo)準(zhǔn)，驗(yàn)收結(jié)束后

39、發(fā)現(xiàn)故障的處理方式，文檔等。>碩癘鄴頏謅攆檸攜驤蘞。2 Quality Plan 質(zhì)量計(jì)劃2.1 Process Deviation 過(guò)程偏差< Provide the link of the Deviation Request Form ><提供到PJM03F10-偏差申請(qǐng)表的鏈接>。2.2 Quality Goal質(zhì)量目標(biāo)Following metrics will be collected as per the Metrics Procedure. These metrics will be tracked at least once per phase o

40、f the project.閿擻輳嬪諫遷擇楨秘騖。按照度量過(guò)程收集以下度量數(shù)據(jù)。這些度量數(shù)據(jù)將會(huì)在工程的各個(gè)階段進(jìn)行跟蹤。Sl. No.序號(hào)Metric度量Quality Targets質(zhì)量目標(biāo)Remarks說(shuō)明Project） These quality goals are also indicative of the priorities of the project. Lesser the variance more the priority. 這些質(zhì)量目標(biāo)也表明了工程的優(yōu)先級(jí)別，變化率較小者具有較高的優(yōu)先工程O(píng)rg.組織Goal目標(biāo)LCL 下限UCL上限Goal目標(biāo)LCL下限UCL上限

41、1Software Requirements Stability Index 軟件需求穩(wěn)定指數(shù) (%)2Duration Variance持續(xù)時(shí)間偏差 (%)3Schedule Slippage進(jìn)度偏移 (%)4Effort Variance工作量偏差 (%)5Size Variance規(guī)模偏差 (%)6Defect Detected Density發(fā)布前缺陷發(fā)現(xiàn)密度 (個(gè)/KLOC)7Residual Defect Density遺留缺陷密度 (個(gè)/KLOC)8Productivity 生產(chǎn)率 (LOC /人天)Activity Wise Defect Detection Density 活

42、動(dòng)缺陷發(fā)現(xiàn)密度9SRS Review需求規(guī)格review缺陷發(fā)現(xiàn)密度 (個(gè)/頁(yè))10STP Review系統(tǒng)測(cè)試計(jì)劃review缺陷發(fā)現(xiàn)密度 (個(gè)/用例)11UM Review用戶文檔review缺陷發(fā)現(xiàn)密度 (個(gè)/頁(yè))12HLD Review 概要設(shè)計(jì)review缺陷發(fā)現(xiàn)密度 (個(gè)/頁(yè))13ITP Review集成測(cè)試計(jì)劃review缺陷發(fā)現(xiàn)密度 (個(gè)/用例)14LLD Review 詳細(xì)設(shè)計(jì)review缺陷發(fā)現(xiàn)密度 (個(gè)/頁(yè))15UTP Review單元測(cè)試計(jì)劃review缺陷發(fā)現(xiàn)密度 (個(gè)/用例)16CODE Review代碼review缺陷發(fā)現(xiàn)密度 (個(gè)/KLOC)17UT單元測(cè)試缺陷

43、發(fā)現(xiàn)密度 (個(gè)/KLOC)18IT集成測(cè)試缺陷發(fā)現(xiàn)密度 (個(gè)/KLOC)19ST系統(tǒng)測(cè)試缺陷發(fā)現(xiàn)密度 (個(gè)/KLOC)1.1 Plan to achieve the Quality Targets & Contingency達(dá)到質(zhì)量目標(biāo)的計(jì)劃及應(yīng)急措施氬嚕躑竄貿(mào)懇彈瀘頷澩。1.1.1 Plan to achieve the Quality Targets達(dá)成質(zhì)量目標(biāo)的計(jì)劃< Please refer to the following two examples when plan to achieve the quality targets. >釷鵒資贏車(chē)贖孫滅獅贅。<

44、制定達(dá)成質(zhì)量目標(biāo)的計(jì)劃請(qǐng)參考下述兩例：>< Static Code Analysis tools would be utilized during the coding phase. These would be configured to ensure that all programming issues are identified even before the code reaches the code review. The entry criteria for code review would be a no-error and no-warning source

45、code from those tools. This would help improve the code quality and help reviewers focus on design defects in the code rather than on the coding defects (which would take more time )>慫闡譜鯪逕導(dǎo)嘯畫(huà)長(zhǎng)涼。<在編碼階段使用靜態(tài)的代碼分析工具，配置工具以確保甚至在進(jìn)行代碼review之前就能識(shí)別所有的編程問(wèn)題。代碼review的入口條件是使用工具分析時(shí)無(wú)錯(cuò)及無(wú)警告信息，如此將能改進(jìn)代碼的質(zhì)量，并幫助rev

46、iewers關(guān)注代碼中的設(shè)計(jì)問(wèn)題而不是關(guān)注簡(jiǎn)單的編碼缺陷（這樣將會(huì)花去更多的時(shí)間）。>諺辭調(diào)擔(dān)鈧諂動(dòng)禪瀉類(lèi)。< Test Coverage tools have been identified to ensure that desired code coverage levels are monitored throughout the coding unit testing and subsequent phases. >嘰覲詿縲鐋囁偽純鉿錈。<指明應(yīng)使用的測(cè)試覆蓋率工具，以確保在整個(gè)編碼及單元測(cè)試階段及后續(xù)階段中，期望達(dá)到的代碼覆蓋率得到了監(jiān)控。>熒紿譏鉦鏌觶

47、鷹緇機(jī)庫(kù)。1.1.2 Contingency Plan應(yīng)急計(jì)劃< Please take the following statements as example when make contingency plan. If the said quality goals are not met, then we do the root cause analysis for the same. If the quality goal is related schedule variance then project manager will ask team members to work

48、extra time to complete the activities on time. >鶼漬螻偉閱劍鯫腎邏蘞。<制定應(yīng)急計(jì)劃時(shí)請(qǐng)參考下例：如果列出的質(zhì)量目標(biāo)沒(méi)有達(dá)到，我們將進(jìn)行針對(duì)性的根本原因分析，如果質(zhì)量目標(biāo)引起進(jìn)度偏差，PM將要求工程組成員加班以及時(shí)完成各項(xiàng)任務(wù)。>紂憂蔣氳頑薟驅(qū)藥憫騖。1.2 Quality Assurance Activities級(jí) For the schedule of these quality assurance activities, refer to the Gantt (WBS)質(zhì)量保證活動(dòng)的進(jìn)度安排參考甘特圖（WBS質(zhì)量保證活動(dòng)穎

49、芻莖蛺餑億頓裊賠瀧。Following Quality Assurance activities will be performed:濫驂膽閉驟羥闈詔寢賻。應(yīng)該執(zhí)行以下的質(zhì)量保證活動(dòng)：Activity 活動(dòng)Responsibility 責(zé)任人Software Requirement Specifications review軟件需求規(guī)格reviewPerson designated by Project Manager由PM指定的人員High Level Design Review概要設(shè)計(jì)reviewPerson designated by Project Manager由PM指定的人員Low

50、 Level Design Review詳細(xì)設(shè)計(jì)reviewPerson designated by Project Manager由PM指定的人員Code review代碼reviewPerson designated by Project Manager由PM指定的人員Unit test plan and test cases review單元測(cè)試計(jì)劃和測(cè)試用例reviewPerson designated by Project Manager由PM指定的人員Integration test plan and test cases review集成測(cè)試計(jì)劃和測(cè)試用例reviewPerson

51、 designated by Project Manager由PM指定的人員System test plan and test cases review系統(tǒng)測(cè)試計(jì)劃和測(cè)試用例reviewPerson designated by Project Manager由PM指定的人員(Unit/Integration/System) Test results review（單元/集成/系統(tǒng)）測(cè)試結(jié)果reviewPerson designated by Project Manager由PM指定的人員Backup and restoration Verification備份與恢復(fù)驗(yàn)證QADeliverables audit交付件審計(jì)QABaseline audit基線審計(jì)QA2.1 Quality Control Activities）1.1Quality Control Activities For the schedule of these quality control activities, refer to the Gantt (WBS)關(guān)于質(zhì)量活動(dòng)的進(jìn)度，請(qǐng)參看甘特圖（WBS質(zhì)量控制活動(dòng)銚銻縵嚌鰻鴻鋟謎諏涼。Following Quality Control activities will be