一网打尽网路书城专案执行计画

1、一網打盡網路書城專案執行計畫Project Execution Plan of Online Bookstore SystemVersion 1.0MemberCommitment signature沈文祥林慶全朱鵬化郭嘉竣林君蔚楊智幃吳孟蓉2005/04/21目錄Revision History (林慶全)2Table PEP001 Revision check list (Version 0.8) (林慶全)31.1 Introduction (林慶全)51.2 Project Scope (Work Breakdown Structure) (郭嘉竣)51.3 Project Life

2、Cycle (郭嘉竣)61.4 Project Schedule (林慶全)61.4.1 Milestone Review71.5 Work Descriptions (楊智幃)71.6 Resources (林君蔚)141.6.1 Budget141.6.2 Personnel141.7 Risk Management (吳孟蓉)161.7.1 Define Risk Levels161.8 Data Management Plan (吳孟蓉)161.8.1 Management Data Table171.8.2 Security and Privacy Issues (林慶全)192.1

3、 Requirement Management Plan (林慶全)202.1.1 Requirement Management Process202.1.2 Resources202.2 Measurement and Analysis Plan (郭嘉竣)242.3 Configuration Management Plan (楊智幃)282.3.1目的282.3.2管理項目282.3.3 建構管理系統282.4 Process and Product Quality Assurance Plan (吳孟蓉)342.5 Project Monitor and Control Plan (林

4、君蔚)372.5.1 Monitor Project372.5.2 PMC Process Diagram392.5.3 PMC Table Template402.5.4 Responsibility assignment41Revision History (林慶全)DateVersionDescription2005/04/07DraftInitiation 2005/04/140.5Add §2.1 Requirement Management Plan, §2.2 Measurement and Analysis Plan, §2.3 Configura

5、tion Management Plan, §2.4 Process and Product Quality Assurance Plan, §2.5 Project Monitor and Control Plan2005/04/210.8Add§Revision History§Revision Check List (Version 0.8)§Security and Privacy IssuesTable PEP001 Revision check list (Version 0.8) (林慶全)Problem descriptionC

6、orrective actionsCheckProcess Area: PPPP GP2.6: no version #Version numbered (0.8)üPP GP 2.6: no revision history in PEPAdd revision history, p.3üno released dateAdd release date on the cover (2005/04/21)üPP SP2.3: should concern the security/privacy issueAdd §Security and Privac

7、y IssuesüProcess Area: PMCPMC SP1.1: should define what is your "significant" deviationAdded in PM001üPMC GP2.2: should provide a more detailed process. Use diagram to describe the processPMC diagram has been addedüPMC GP2.3: create tables/templates for monitoring and contro

8、lAdd general meeting table and problem record table templateüPMC GP2.4: Assign ResponsibilityProcess Area: MAMA SP1.3: too fuzzyDescribed in §2.2.4üMA SP1.4: should define what the indicator in your measurement is. The indicator is measured from base measuresDescribed in §2.2.5&#

9、252;MA GP2.3: should provide form/templateMA GP2.4: Assign ResponsibilityDescribed in §2.2.6üProcess Area: CMCM SP1.2: for a CM system, the process and related template/form should be defined. Only the CVS is not enough.CM BPM Wincvs使用權限對照§分一般文件與程式碼二部分CM控管üCM SP3.1

10、: Establish and maintain records describing configuration items§定義每個星期maintain一次, 記錄並納入CM管理üCM GP2.2: describe it by graph (ex: BPM)Refer to §üCM GP2.3: define template/formRefer to Table 2.3.1üCM GP2.4:Assign ResponsibilityRefer to üProcess Area: P

11、PQAPPQA SP1.1: see subpractice 2. You should define what to evaluate? When and how often a process should be evaluated?Follow it in process, after plan changed, we will check the process again.üPPQA SP1.1: see subpractice 2.PPQA GP2.2: plan the processDesign a processüPPQA GP2.3: the provi

12、ded checklist should be defined based on SP1.1 and SP1.2Follow it in processüPPQA GP2.4:Assign ResponsibilityProcess Area: REQMREQM GP2.2: Plan the ProcessProcess plannedüREQM GP2.3:Provide ResourceProvide budget and personnelüREQM GP2.4:Assign ResponsibilityResponsibility assigned

13、52;1.1 Introduction (林慶全)The OBS system is an online book store system. It consists of four subsystems - inquiring subsystem, book purchasing subsystem, member management subsystem, and reader service subsystem. It will take four months from project planning to project support. The major jobs are or

14、ganized by project management, system engineering, software development, integration and testing, and project support. To finish the project on time, the schedule as shown below must be under controlled. 1.2 Project Scope (Work Breakdown Structure) (郭嘉竣)我們使用Work Breakdown Structure描述整個專案的範圍，如下圖：Figu

15、re PEP1.2.1 OBS的WBS1.3 Project Life Cycle (郭嘉竣)本專案生命週期主要階段有架構設計、需求發展、專案規劃、子系統發展、子系統整合及系統整合等階段，如下圖所示：Figure PEP1.3.1 OBS的Life Cycle1.4 Project Schedule (林慶全)整個專案工作排程如下所示：Figure PEP1.4.1 OBS的工作排程1.4.1 Milestone Review2005/03/25 Requirement DevelopmentChairman:楊智幃Objective: Development user requirement

16、Report: System Requirement Specification2005/04/14 Project Execution Plan ReviewChairman:林慶全Objective: Review project planReport: Project execution plan checklist2005/05/06 Subsystem implementationChairman:郭嘉竣Objective: Review source codeReport: source code which need to be modified2005/05/27 System

17、 Integration TestChairman:林君蔚Objective: Review source codeReport: Integration test report (system valid and invalid item)1.5 Work Descriptions (楊智幃)Table PEP 1.5.1工作項目編號名稱1.1.1Project Planning工作內容說明1.定義專案範圍、所需資源2.建立專案工作評估方法以及工作排程3.進行專案風險分析工作產品格式專案執行規劃書文件與其他工作項目的相依性1.9.1 建構管理、1.9.2 度量分析需求技能與知識專案管理工作時

18、程0.5月需求資源人力2 人月硬體設備軟體工具Microsoft Office、Visio其他工作排程限制這是專案全程活動備註依照訂定的專案規劃書進行工作項目編號名稱1.1.2Project Monitoring and Control工作內容說明執行專案監控工作產品格式專案監控記錄文件與其他工作項目的相依性1.9.2 度量分析需求技能與知識專案管理工作時程3.5月需求資源人力2人月硬體設備軟體工具Microsoft Office其他工作排程限制這是專案全程活動備註依專案監控規劃書執行工作項目編號名稱1.1.3Milestone Checking工作內容說明指導教授負責於查核點進行計畫監督工作

19、工作產品格式與其他工作項目的相依性需求技能與知識專案管理工作時程4月需求資源人力1人月硬體設備軟體工具其他工作排程備註依專案規劃書預定的時程進行工作項目編號名稱1.2.1Requirement Analysis工作內容說明1.收集、瞭解、分析系統需求2.Use case development工作產品格式系統需求規格書草稿文件與其他工作項目的相依性需求技能與知識需求發展與管理、Java 及JSP 知識、系統分析工作時程0.25月需求資源人力4人月硬體設備軟體工具Microsoft Office、Together、XDE其他工作排程備註工作項目編號名稱1.2.2System Design工作內容

20、說明進行系統架構設計。工作產品格式系統設計規格書草稿文件與其他工作項目的相依性需求技能與知識Java 及JSP 知識、物件導向分析與設計工作時程0.5月需求資源人力4人月硬體設備軟體工具Microsoft Office、XDE、Together其他工作排程備註依系統需求規格書設計工作項目編號名稱1.3.0IS Subsystem Development工作內容說明負責IS 子系統程式：1.設計；2.開發；3.內部整合測試工作產品格式IS 子系統程式碼測試報告文件規模估計500 LOC與其他工作項目的相依性1.4.0購書子系統需求技能與知識Java、JSP、.NET、Web service、My

21、SQL 知識、微軟作業系統、應用程式設計、測試規劃能力工作時程1月需求資源人力1人月硬體設備軟體工具Java、JDK、TOMCAT、Microsoft Office、.NET其他工作排程備註工作項目編號名稱1.4.0BPS Subsystem Development工作內容說明負責BPS 子系統程式：1.設計；2.開發；3.內部整合測試工作產品格式BPS 子系統程式碼測試報告文件規模估計800 LOC與其他工作項目的相依性1.3.0查詢子系統需求技能與知識Java、JSP、.NET、Web service、MySQL 知識、微軟作業系統、應用程式設計、測試規劃能力工作時程1月需求資源人力1人月

22、硬體設備軟體工具Java、JDK、TOMCAT、Microsoft Office、.NET其他工作排程備註工作項目編號名稱1.5.0MMS Subsystem Development工作內容說明負責MMS 子系統程式：1.設計；2.開發；3.內部整合測試工作產品格式MMS 子系統程式碼測試報告文件規模估計1000 LOC與其他工作項目的相依性需求技能與知識Java、JSP、.NET、Web service、MySQL 知識、微軟作業系統、應用程式設計、測試規劃能力工作時程1月需求資源人力1人月硬體設備軟體工具Java、JDK、TOMCAT、Microsoft Office、.NET其他工作排程

23、備註工作項目編號名稱1.6.0RSS Subsystem Development工作內容說明負責RSS 子系統程式：1.設計；2.開發；3.內部整合測試工作產品格式RSS 子系統程式碼測試報告文件規模估計800 LOC與其他工作項目的相依性需求技能與知識Java、JSP、.NET、Web service、MySQL 知識、微軟作業系統、應用程式設計、測試規劃能力工作時程1月需求資源人力1人月硬體設備軟體工具Java、JDK、TOMCAT、Microsoft Office、.NET其他工作排程備註工作項目編號名稱1.7.1Integration Testing工作內容說明負責整合並測試子系統工作

24、產品格式測試報告文件與其他工作項目的相依性需求技能與知識系統驗證、測試能力工作時程0.5月需求資源人力4人月硬體設備軟體工具Microsoft Office、JDK、TOMCAT、.NET其他工作排程須安排在IS、BPS、MMS、RSS 子系統完成之後備註工作項目編號名稱1.7.2System Testing工作內容說明1.Validate use cases2.Verify system requirements3.對整個系統進行相關系統測試：Recovery、Security、Performance、Stress Testing工作產品格式測試報告文件與其他工作項目的相依性需求技能與知識系

25、統驗證、測試能力工作時程0.5月需求資源人力2人月硬體設備軟體工具Microsoft Office、JDK、TOMCAT、.NET其他工作排程1.7.1 Integration Testing備註工作項目編號名稱1.7.3System Delivery工作內容說明負責將完成的系統交付客戶工作產品格式OBS 系統程式碼與其他工作項目的相依性需求技能與知識系統包裝移植及製作工作時程0.5月需求資源人力4人月硬體設備軟體工具Microsoft Office、JDK、TOMCAT、.NET其他工作排程1.7.1 系統整合測試備註工作項目編號名稱1.8.1Project Report (includin

26、g Software User Manual)工作內容說明為所完成的系統撰寫使用手冊和計劃報告書工作產品格式使用手冊文件與其他工作項目的相依性需求技能與知識工作時程0.5月需求資源人力4人月硬體設備軟體工具Microsoft Office、JDK、TOMCAT、.NET其他工作排程1.7.1 系統整合測試備註工作項目編號名稱1.9.1Configuration Management工作內容說明執行建構管理流程。工作產品格式建構管理計畫文件與其他工作項目的相依性需求技能與知識建構管理工作時程4月需求資源人力1人月硬體設備軟體工具Microsoft Office、WinCVS其他工作排程這是專案全

27、程活動備註工作項目編號名稱1.9.2Measurement and Analysis工作內容說明執行度量分析流程工作產品格式專案度量計畫文件度量分析報告文件與其他工作項目的相依性需求技能與知識專案管理工作時程4月需求資源人力4人月硬體設備軟體工具Microsoft Office其他工作排程這是專案全程活動備註工作項目編號名稱1.9.3Training工作內容說明準備需教授的知識內容，撰寫訓練教材。工作產品格式訓練教材文件與其他工作項目的相依性需求技能與知識CMMI、Java 、.NET及JSP 知識工作時程1月需求資源人力4人月硬體設備軟體工具Microsoft Office其他工作排程備註1

28、.6 Resources (林君蔚)1.6.1 Budget Hardware NT$40000 (PC)CPU Intel P4-2.4GRAM 768MB DDRHD IDE 200GB 7200RPMDVD R/W 32X21”LCD DisplayVideo CardOther accessories (Mouse, Keyboard, Spearker, Printer.) Personnel ExpenseNT$ 2000 Per Unit1 Person * 3 Unit = NT$6,000 Per Month7 Person * 4 Month = NT$168,000 Ot

29、herPrinter toner: NT$3500 * 10 = NT$35000A4 paper: NT$100 * 50 = NT$5000DVD R-W: NT$600 * 5 = NT$30001.6.2 PersonnelTable PEP 1.6.1專案人員需求規格表WBS編號活動與交付項目負責人員所需的知識與技能需加強之知識與技能1.1.1Project Planning沈文祥林慶全朱鵬化Project Analysis1.1.2Project Monitoring and Control林慶全朱鵬化Project Management1.1.3Milestone Checkin

30、g沈文祥林慶全朱鵬化Project Management、Project Monitoring and Control1.2.1Requirement Analysis楊智幃Project Analysis、Requirement collection1.2.2System Design林君蔚Project AnalysisOO Design1.3.0IS Subsystem Development郭嘉竣ASP、Unit TestingASP1.4.0BPS Subsystem Development林君蔚ASP、Unit TestingASP1.5.0MMS Subsystem Develo

31、pment楊智幃ASP、Unit TestingASP1.6.0RSS Subsystem Development吳孟蓉ASP、Unit Testing1.7.1Integration Testing郭嘉竣林君蔚楊智幃吳孟蓉System Integration、Testing1.7.2System Testing林慶全郭嘉竣林君蔚楊智幃吳孟蓉Testing、Verification、Validation1.7.3System Delivery林慶全楊智幃1.8.1Software User Manual郭嘉竣林君蔚楊智幃吳孟蓉Software Engineering knowledge1.9.

32、1Configuration Management郭嘉竣Configuration Management1.9.2Measurement Analysis林君蔚Measurement AnalysisMeasurement Analysis1.9.3Training林慶全楊智幃.NetCMMI1.7 Risk Management (吳孟蓉)Table PEP 1.7.1序號風險因素影響嚴重性發生機率風險性內部或外部風險技術時程1人員訓練不足MM90.32.7內部2資料庫變動M80.43.2內部3資料庫損毀M60.10.6外部4硬體維護LM40.83.2內部5版本控管H80.86.4內部描述：

33、人員訓練不足：由於每一位參與者並非專業人員所以會有訓練不足之風險。資料庫變動：系統人員內部的資料庫更動維護。資料庫損毀：預防外界破壞系統資料之風險。硬體維護：除了軟體，硬體亦需維護，用以促使系統運作正常。版本控管：使系統維持在最新版本之上。1.7.1 Define Risk LevelsTable PEP 1.7.2影響專案目標項目低(L)中(M)高(H)技術<5%技術變更5-10%技術變更10-20%技術變更時程<5%時程差距5-10%時程差距10-20%時程差距 嚴重性介於 0-10，0：最不嚴重，10：最為嚴重 發生機率介於 0-1 之間 風險性 = 嚴重性 * 發生機率1.

34、8 Data Management Plan (吳孟蓉)在 Data Management Plan 中記載著開發 Project 過程中所需要管理的資料，其中記載資料內容主要包括下面幾項：1. Data Content Work Product Product Specification2. Data Type Document Database Source Code3. Store Medium File Paper1.8.1 Management Data TableTable PEP 1.8.1ClassificationProcess AreaDataDeliver or notD

35、ata TypeMediumProject ManagementProject PlanProject Execution PlanYesDocumentFile(Project Execution Plan of Online Bookstore System Version 0.8)Engineering Process AreaRequirement DevelopmentRequirement SpecificationYesDocumentFile(Project Execution Plan of Online Bookstore System Version 0. )Techni

36、cal SolutionDesign SpecificationYesDocumentFile(Project Execution Plan of Online Bookstore System Version 0. )Engineering Process AreaRequirement DevelopmentUser ManualYesDocumentFileTechnical SolutionProgram Design Plan、Source CodeYesSource CodeFileProduct Integration、Verification、ValidationTest Pl

37、anYesDocumentFile(Project Execution Plan of Online Bookstore System Version 0. )Product Integration、Verification、ValidationTest Design SpecificationYesDocumentFile(Project Execution Plan of Online Bookstore System Version 0. )Product Integration、Verification、ValidationTest CaseYesDocumentFile(Projec

38、t Execution Plan of Online Bookstore System Version 0. )Configuration ManagementConfiguration ManagementConfiguration Management PlanNoDocumentFileProject ManagementMeasure and AnalysisMeasure and Analysis PlanNoDocument1.8.2 Security and Privacy Issues (林慶全)We take careful precautions to protect ou

39、r project information. Only project members can get documents, testing report, minutes, reports, etc. Set access password for every document, e.g. password is 123 for this document, Project Execution Plan. People, who do not know the access password, can not open this document. Appropriate security

40、and privacy policies are listed below:1. All documents are copied to CDs for back up.2. Source code as well as technical documents are stored in the safe deposit box which is fireproofing. Additionally, tape label on the cover to direct if box was opened by unauthorized people.3. Evaluate and measur

41、e the security and privacy facility regually and record it in the following table. Table PEP1.9.1 Evaluation of security and privacy facilityDateWas taped label broken?Inspector Remark4. Any team member who wants to refer to the technical document should apply the permission of Project Manager.The s

42、ecurity is as secure as can reasonably be provided.2.1 Requirement Management Plan (林慶全)2.1.1 Requirement Management ProcessEndApply Changing RequirementReview Changing RequirementEvaluateChange RequirementNegotiate with customerFailed/OthersPassConfiguration ManagementBeginFigure PEP 2.1.1 Requirem

43、ent management flow chart Process Plan2.1.2 Resources Budget Personnel Expense5 Persons * 4 Month = NT$20,000 OtherPrinter toner: NT$3500 * 1 = NT$3,500A4 paper: NT$100 * 5 reams = NT$500Total budget for configuration management : NT$24,00.2 PersonnelTable PEP 2.1.1Responsibility assig

44、nmentWork ID*ActivitiesResponsibilityBackground and skillsKnowledge and trainingAnalyze requirements林慶全郭嘉竣林君蔚楊智幃吳孟蓉Java, Internet, UMLHold a meeting楊智幃Requirements version control林慶全楊智幃Project management,WordTrace requirements林慶全郭嘉竣林君蔚楊智幃吳孟蓉Corrective actions林慶全郭嘉竣

45、林君蔚楊智幃吳孟蓉Web service*Work ID maps to the planning description in Requirement Management Plan. Forms and templatesTo change requirement, the following table, Table PEP2.1.2, should be submitted.Table PEP2.1.2 Requirement change requestProject name:Name:Date:Original requirement IDPriority:Req

46、uirement updateEvaluationPass Fail OthersProject Manager commitmentTable PEP 2.1.2Requirements ManagementPracticeDescriptionPossible Direct and Indirect implementation evidences Yes NoNot ApplicableNoteSP 1.1Develop an understanding with the requirements providers on the meaning of requirements與需求的提

47、供者共同開發需求，瞭解需求1. List of Requirement providers2. Criteria for evaluation and acceptance3. Results of analysis4. Agreed set of requirementsSP 1.2Obtain commitment to requirements from the project participants從專案的參與者獲得對需求的承諾1. Requirement impact assessments2. Commitment to requirements and requirement

48、changes3. Project Initiation / Kickoff meeting minutesSP 1.3Manage changes to the requirements as they evolve during the project管理對需求的修改1. Requirement status2. Requirements database3. Requirements decision databaseSP 1.4Maintain Bidirectional traceability among the requirements and the project plans

49、 and work products維護 需求與 project plan 與 work product 的雙向追蹤性1. Requirements traceability matrix2. Requirements tracking systemSP 1.5Identify inconsistencies between the project plans and work products and the requirements指出 需求，project plan 與 work product 之間的不一致1. Documentation of inconsistencies2. Corrective Actions2.2 Measurement and Analysis Plan (郭嘉竣)1. 目的收集資訊、提供度量能力來支援支援管理的資訊需求。2. 收集目的與資訊需求 目的資訊需求時程與進度里程碑完成狀況、工作進度3. 度量基礎 項目度量基礎里程碑完成狀況、工作進度里程碑完成的時間進度=(已完成的工作項目/預期完成項目)*100%4. 收集項目與程序 工作進度表資料來源本組所有成員及組長資料內容內容必須說明本次會期前，完成了哪些工作項目、發生問題原因、進度落後原因、完成的百分比，