【正文】 ect Manager will document the issue.Step 2: The Project Manager will review the change and determine the associated impact to the project and will forward the issue, along with a remendation, to the Steering Committee for review and decision. Step 3: Upon receipt, the Steering Committee should reach a consensus opinion on whether to approve, reject or modify the request based upon the information contained within the project website, the Project Manager’s remendation and their own judgment. Should the Steering Committee be unable to reach consensus on the approval or denial of a change, the issue will be forwarded to the Project Sponsor, with a written summation of the issue, for ultimate resolution.Step 4: If required under the decision matrix or due to a lack of consensus, the Project Sponsor shall review the issue(s) and render a final decision on the approval or denial of a change.Step 5: Following an approval or denial (by the Steering Committee or Project Sponsor), the Project Manager will notify the original requestor of the action taken. There is no appeal process. *Tags: In this project, team members will act as the Steering Committer role. And the teacher will act as the Project Sponsor.. Schedule ControlThe weekly schedule will be shown intuitively in the CMS Gantt chart, and then be shared to team members. And the PM will release “Biweekly Report Week” half month. So for the delay tasks, PM will try to adjust resources to bring down influence. *Tags: refer to the document “”.. Budget ControlThis project doesn’t need to control the budget, and only need to control the plan. . Quality ControlThere is a professional SQA role to control quality in this project. SQA staff will provide a SQA plan and test plan for quality control. PM and SQA staff will follow the plans to control quality.See “SQA Plan”, please.. ReportingA Bi weekly report will deliver to teacher by PM. It will report current status and issues for this project.*Tags: the template of Bi weekly report refers to the Annex A.. Project MetricsSome project status will be tracked and collected, including workload process status, work deviation case, defects, etc. The workload process status and work deviation case will be collected semimonthly. The defects status will be collected in the process of testing. The checklist will be used in the document check and the efficiency of process executed. . Risk Management PlanPM will manage the risk on a weekly basis, including identifying risk, tracking and analyze the identified risk. When the risk happened, PM will use the required measures. The checklist of risk refers to the Annex B.. Project Closeout PlanIt is necessary to project closeout process to ensure orderly closeout of the project.216。 Project Manager will provide a Skeleton Closeout Report. The closeout Report would have information regarding the project scope, risk and the original plan’s schedule.216。 PM will have a closeout meeting with customers. In the meeting, they will review the following agenda.178。 Executive Summary of the project plan 178。 Project result 178。 Analysis of project objectives achieved178。 Real deliverables to those described in the plan216。 It is necessary to a post mortem meeting in the team. Project personnel will write postmortem debriefings and discuss lessons learned. . Project Review Meeting PlanIt is necessary to project review meetings in order to ensure work objective and quality.In the project process, we will hold the review meetings in each phase. The following is the step.216。 Meeting Time:178。 At 9:00 every weekend. 178。 two days before the end of each milestone216。 Venue: The meeting will be held on the internet through Group.216。 Team leader will give members the for the meeting. At the same time, the deliverables will be sent in the . 216。 Members will review the deliverables, and then send ments back to team leader.216。 Team leader will sort out the information from members. An informal list of discussion topics will be formed.216。 According to the informal list of discussion topics, team will discuss them and draw conclusions one by one.216。 Finally, team leader will record the conclusions in the transaction track system (Google Code). Corresponding member will be in charge of the tasks according to the conclusions. Team leader will follow up the process of the tasks.4. Technical Process Plans. Process ModelThe iteration process of RUP will be used in the CMS project. The following step:216。 Analyze Requirement216。 Condense Requirement 216。 Design CMS 216。 Condense Designs216。 Coding216。 Integration Testing216。 Deployment.. InfrastructureThe free system for JAVA and MySQL will be used in this project. It is cross platform, so foreseeingly this project will be deployed in many platforms.. Product AcceptanceThe teacher will act as the customer role. In other words, product acceptance will depend on the teacher’ review. If the teacher has any suggestions and opinions, the team will perfect the plan at the right moment.5. Supporting Process Plans. Configuration ManagementGoogle Code Tool will be used in issues management in the project. When there is an issue, it will be placed in the following link:Then PM will track this issue and assign tasks to the person responsible. The status of issue also will be tracked until to be pleted. When the sponsor approves the issue, the issue will be closeout.The documents and programs in the project process will be carried out the configuration management, and adopt the unique identification. After the review passed, they will be placed under the configuration management. When the change happened, the change control process will be adopted.. Verification and ValidationAll the team members will review all the documents for this project. The program will be tested prehensively by testers. Finally, the teacher will verify the product –