Procedure（程序）
  Entry Criteria（開始條件）
  Change control board is established for the project.
  Baselined work products exist.
  The Originator has bbbbbbted a valid issue or change request with all necessary inbbbbation to the CCB Chair.
  The change control tool sets the issue’s initial status to bbbbbbted.
  已建立項目變更控制委員會。
  存在已基線化的工件。
  發(fā)起人提交正確的變更請求或?qū)⒆兏埱蠛退斜匾男畔⑻峤唤o變更控制委員會主席。
  變更控制工具將變更請求的初始狀態(tài)設(shè)置為已提交。
  Tasks（任務(wù)）
  1. The CCB Chair assigns an bbbbuator.
  1. 變更控制委員會主席指定一個評估人 。
  2. The bbbbuator assesses the issue as to feasibility, whether it really pertains to the indicated project, whether a reported problem can be reproduced, an estimate of the labor hours needed to implement the change, and so on. For a requirement change, use the Impact Analysis Checklist for Requirements Changes, the Effort Estimation Worksheet for a Requirement Change, and the Impact Analysis Report Template. Change status to bbbbuated.
  2. 評估人對變更請求進行可行性評估，判斷其是否真正符合項目特征，被報告的問題是否能被重復(fù)產(chǎn)生，估計實施變更所需工作量等等。對一個需求變更，用影響分析檢查表，工作量估計表，以及影響分析報告模板進行評估。改變狀態(tài)為已評估。
  3. The CCB decides whether the requested change should be made (or the reported problem fixed) at this time, at some point in the future, or not at all. bbbbb should be solicited from others potentially affected by the change before making the decision.
  3. 變更控制委員會決定此次提出的變更是否應(yīng)實施（或已報告的問題是否應(yīng)解決），或部分變更在將來解決，或根本不解決。 決定前必須從其他被變更影響的潛在方獲取必要的意見。
  4. If the change was accepted, the CCB Chair assigns a Modifier, sets the status to Approved, enters any explanation in the Response attribute, and schedules the work. The Project Manager negotiates any necessary changes in project commitments with affected stakeholders. Tool sends e-mail to the assigned Modifier and the Originator.
  4. 如果接受變更請求，變更控制委員會主席會指定一個修改人，同時設(shè)置變更請求狀態(tài)為已批準(zhǔn)，并在回應(yīng)屬性中填入相應(yīng)解釋。項目經(jīng)理在項目會議中同涉眾協(xié)商任何必需的變更。變更控制工具發(fā)電子郵件給已指定的修改人和發(fā)起人。
  5. If the change was rejected, the CCB Chair sets the status to Rejected and enters an explanation of why in the Response attribute. Tool sends e-mail to the Originator and CCB Chair.
  5. 如果變更被拒絕，變更控制委員會主席設(shè)置變更狀態(tài)為已拒絕并在回應(yīng)屬性中解釋拒絕的原因。變更控制工具發(fā)電子郵件給發(fā)起人和變更控制委員會主席。
  6. The CCB Chair and the Originator determine whether bbbbal verification of the change will be required, following the procedure in the Verification section. If so, they select the verification bbbbbb to be used and the CCB Chair assigns a Verifier.
  6. 變更控制委員會主席和發(fā)起人決定是否需要對變更進行正式的驗證，具體的步驟在下面的驗證部分中描述。如果是，他們選擇使用的驗證方法并由變更控制委員會主席指定驗證人。
  7. The Modifier makes the necessary changes in the affected work products and notifies any other affected parties if corresponding changes need to be made, such as user documentation, help screens, and tests.
  7. 修改人在受影響的工件中實施必要的變更，如果在其他方也需要實施相應(yīng)變更則應(yīng)通知所有其他受影響方，如用戶文檔、幫助屏幕、測試文檔等。
  8. The Project Manager updates the project plans, task lists, and schedules to reflect the impact of the change on project work remaining to be done. The Project Manager revises any task dependencies as necessary.
  8. 項目經(jīng)理更新項目計劃，任務(wù)清單，和時間表，以反映變更對已做或在做工作的影響。如果需要，項目經(jīng)理修訂任務(wù)的依賴性。
  9. If it becomes apparent during the work that the requested change is not feasible after all, the Modifier notifies the CCB Chair, who may then set the status to Canceled. The Modifier backs out of any modifications made, restoring the work products to their previous baseline. Tool sends e-mail to the Originator, CCB Chair, Modifier, and Project Manager.
  9. 最后如果在工作期間發(fā)現(xiàn)需求變更是不可行的，修改人應(yīng)通知變更控制委員會主席，由他作出取消決定并設(shè)置狀態(tài)為已取消。修改人返回未做修改狀態(tài)，恢復(fù)以前已基線化的工件。變更控制工具發(fā)電子郵件給發(fā)起人，變更控制委員會主席，修改人和項目經(jīng)理。
  10. When the change is completed, the Modifier sets the status to Change Made, updates the issue in the database with appropriate notes in the Response attribute, and enters the hours of effort that were required to make the change in the Actual Hours attribute. Tool sends e-mail to the Originator and CCB Chair.
  10. 當(dāng)變更完成時，修改人設(shè)置變更狀態(tài)為實施變更，在回應(yīng)屬性中對更新的變更請求加入適當(dāng)?shù)淖⑨?，并在實際時間屬性中輸入實施變更所花的實際工作量。變更控制工具發(fā)電子郵件給發(fā)起人和變更控制委員會主席。
  Verification（驗證）
  1. The Modifier notifies the Originator and Verifier (if one was assigned) that the change has been made and makes all modified work products available to the people responsible for verification.
  1. 修改人通知發(fā)起人和驗證人（如果已經(jīng)有指定的驗證人）變更已經(jīng)被實施，并且所有已修改的工件已經(jīng)可以進行驗證。
  2. The Verifier perbbbbs the agreed-upon verification steps.
  2. 驗證人執(zhí)行驗證過程。
  3. If verification is successful, the Verifier sets the status to Verified.   Tool sends e-mail to the Originator and Modifier.
  3. 如果驗證通過，驗證人設(shè)置變更狀態(tài)為已驗證。變更控制工具發(fā)電子郵件給修改人和發(fā)起人。
  4. If verification is not successful, the Verifier sets the status back to Approved and describes the problem in the Response attribute. Tool sends e-mail to the Originator and Modifier. The process resumes with Task #7.
  4. 如果驗證未通過，驗證人設(shè)置變更狀態(tài)為已批準(zhǔn)并在回應(yīng)屬性中描述具體的問題。變更控制工具發(fā)電子郵件給修改人和發(fā)起人。此過程會從任務(wù)#7重新開始進行。
  5. For a problem report issue or an enhancement request issue, the Modifier installs the modified work product as appropriate and updates the product baseline. For requirements changes, the Modifier updates version numbers on all modified work products per the project’s version control procedure, checks them back into the version control system, updates requirements traceability inbbbbation and requirements status attributes as necessary, and updates the requirements baseline.
  5. 對于一個問題報告或增加需求的發(fā)布，修改人安裝已修改后的工件并更新產(chǎn)品基線。對于需求變更，修改人按照每個項目的版本控制程序更新所有已修改工件的版本號，如果需要應(yīng)更新需求追溯信息和需求狀態(tài)屬性，并更新需求基線。
  6. The Modifier sets the status to Closed. Tool sends e-mail to the Originator and CCB Chair.
  6. 修改人設(shè)置變更狀態(tài)為已結(jié)束。變更控制工具發(fā)電子郵件給發(fā)起人和變更控制主席。
  Change Control Status Reporting（變更控制狀態(tài)報告） The CCB Chair generates a report at the end of each month summarizing the status of the contents of the change control database. These reports identify all status changes made in the previous month, list the status of all change requests that currently have a status other than Rejected or Closed, and indicate the level of change activity. The project leadership team reviews these reports to determine whether any corrective bbbbbbs are necessary.
  變更控制委員會主席根據(jù)變更控制數(shù)據(jù)庫的內(nèi)容在月末匯總出變更控制數(shù)據(jù)的報告。這些報告表現(xiàn)出上一個月所有發(fā)生的變更的狀態(tài)，列出當(dāng)前所有需求變更的狀態(tài)但已拒絕和已完成的除外，并指出變更活躍程度。項目管理組查看這些報告以確定每個活動的正確性。
  Exit Criteria（退出條件）
  o The status of the request is either Rejected or Closed.
  o The modified work products have been correctly installed into the appropriate bbbbbbbbs.
  o The Originator, CCB Chair, and Project Manager have been notified of the current status.
  o Pertinent requirements traceability inbbbbation has been updated.
  o 變更請求的狀態(tài)為已拒絕或已結(jié)束。
  o 所有修改后的工件被正確安裝到適當(dāng)?shù)奈恢谩?BR>  o 發(fā)起人、變更控制主席、和項目經(jīng)理已被告知當(dāng)前的狀態(tài)。
  o 相關(guān)的需求追溯信息已被更新。