【正文】 Project Plan ForContent Management System Document Revision Date of Issue: 20081013Project Manager: Sweeper22 / 24Approval SignaturesApproved by: Business Project LeaderApproved by: IM/IT Project Leader SweeperPrepared by: Business Project ManagerPrepared by: IM/IT Project ManagerJaneEmmaReviewed by: Quality Assurance ManagerTable of ContentsDocument Change Control 31. Project Overview 4. Purpose, Scope, and Objectives 4. Assumptions, Constraints and Risks 4. Assumptions 4. Constraints 4. Risk Assessment 5. Project Deliverables 5. Schedule and Budget Summary 6. Schedule and Milestone 6. Budget 7. Evolution of the Plan 8. References 8. Definitions and Acronyms 82. Project Organization 9. External Interfaces 9. Internal Structure 9. Roles and Responsibilities 93. Managerial Process Plans 10. Startup Plan 10. Estimates 10. Staffing 10. Resource Acquisition 11. Project Staff Training 11. Work Plan 12. Work Breakdown Structure 12. Schedule Allocation 13. Resource Allocation 13. Budget Allocation 13. Project Tracking Plan 13. Issues Management 13. Schedule Control 14. Budget Control 14. Quality Control 14. Reporting 14. Project Metrics 14. Risk Management Plan 15. Project Closeout Plan 15. Project Review Meeting Plan 154. Technical Process Plans 16. Process Model 16. Infrastructure 16. Product Acceptance 165. Supporting Process Plans 16. Configuration Management 16. Verification and Validation 17. Documentation 17. Quality Assurance 18. Reviews and Audits 18. Problem Resolution 18. Subcontractor Management 18. Process Improvement 186. Additional Plans 19Annex A Biweekly progress report 19Annex B Project Risk Checklist 19Document Change ControlThis section provides control for the development and distribution of revisions to the Project Charter up to the point of approval. The Project Charter does not change throughout the project life cycle, but rather is developed at the beginning of the project (immediately following project initiation approval, and in the earliest stages of project planning). The Project Charter provides an ongoing reference for all project stakeholders. The table below includes the revision number (defined within your Documentation Plan Outline), the date of update/issue, the author responsible for the changes, and a brief description of the context and/or scope of the changes in that revision.Revision NumberDate of IssueAuthor(s)Brief Description of Change20080909SweeperBuild Doc20080919JaneRevision20080920JaneRevision20080923SweeperRevision20080923JaneRevision20080925EmmaLiliJackRevision and Review20080926JaneCheck English20080927Sweeper Revision20080926Project TeamRelease One20081006SweeperAdd Review Meetings Plan20081010JaneRelease Two20081012SweeperUpdate Plan Sync Update11. Project OverviewThe project plan for Content Management System (CMS) of Manufacturing Trade Association (MTA) is written by Final Fantasy Company according to the original requirements of the project. It will provide a definition of the project, including the project’s goals and objectives, etc. Additionally, the Plan will serve as an agreement between the following parties: Project Sponsor, Steering Committee, Project Manager, Project Team, and other personnel associated with and/or affected by the project.. Purpose, Scope, and ObjectivesThe project is developed for a large Manufacturing Trade Association (MTA) with over 2000 members. The purpose for this project is that MTA works closely with enterprises of all sizes to help them unlock the value of their unstructured content.The objective of deploying the CMS is to facilitate the creation and manipulation of content on a website and to enhance collaboration by making it possible to collect information generated within the organization and facilitate its distribution. The preliminary scope of the CMS defined by MTA includes: 216。 Tools for managing users and workflow. The separation of content and the visual display makes it easier to maintain a consistent lookandfeel across the entire website. 216。 Support collaboration tools such as discussion forums and document management. 216。 Support customized information retrieval sophisticated search tools can allow users to locate just the information they are looking for. 216。 Webbased interfaces to selected information in the databases can facilitate data sharing between the organization and its stakeholders. 216。 Make it easier for nontechnical staff to add and edit content, thus streamline the process of maintaining a website. Developing the CMS will be about 4 months. It will plete the requirement research, analysis, design, development, test, deploy and finally deliverable.. Assumptions, Constraints and Risks. AssumptionsThe stakeholders of MTA include: 216。 Executive Council of MTA, consisting of 15 executive members who made decision on running MTA 216。 Office staffs of MTA who carry out the daytoday operation of MTA, under the direction of the Executive Council 216。 MTA Members who receive newsletters and event announcements 216。 Universities which support some of MTA39。s events 216。 Other trade associations which support some of MTA39。s events 216。 Government and IT vendors who sometimes sponsor events organized by MTA 216。 General public who receive announcement on important events of MTA. . ConstraintsMTA has requested that open source software be used whenever possible. In particular, they suggest using Linux operating system。 Apache web server, MySQL database, etc. The CMS must be deployed by Dec. 31 this year, about 4 months fr