In a peer review, co-workers of a person who created a software work product examine that product to identify defects and correct shortcomings. A review:
在同行評審中，由軟件工作產品創建者的同行們檢查該工作產品，識別產品的缺陷，改進產品的不足。評審：
· verifies whether the work product correctly satisfies the specifications found in any predecessor work product, such as requirements or design documents
· 檢驗工作產品是否正確的滿足了以往的工作產品中建立的規範，如需求或設計文檔
· identifies any deviation from standards, including issues that may affect maintainability of the software
· 識別工作產品相對於標準的偏差，包括可能影響軟件可維護性的問題
· suggests improvement opportunities to the author
· 向創建者提出改進建議
· promotes the exchange of techniques and education of the participants.
· 促進參與者之間的技術交流和學習
All interim and final development work products are candidates for review, including:
所有中間和最終的開發工作產品都可以進行評審，包括：
· requirements specifications
· 需求規格說明書
· user interface specifications and designs
· 用戶界面規範及設計
· architecture, high-level design, and detailed designs and models
· 架構，概要設計，詳細設計及模型
· source code
· 源代碼
· test plans, designs, cases, and procedures
· 測試計劃，設計，用例及步驟
· software development plans, including project management plan, configuration management plan, and quality assurance plan
· 軟件開發計劃，包括項目管理計劃，配置管理計劃和質量保證計劃
This document defines an overall peer review process. It includes procedures for conducting inspections and two types of informal peer review, a walkthrough and a passaround, as well as guidance for selecting the appropriate approach for each review.
該文檔定義了一個全面的同行評審過程。包括了執行評審的步驟和兩種非正式的同行評審，走查和輪查，以及對每個評審選擇適當方法的指南。
2. Work Aids（工作輔助項）
The following peer review work aids are available from :
<場所>中，需要有如下的同行評審工作輔助項：
· Inspection Summary Report
· 評審總結報告
· Issue Log
· 問題日誌
· Typo List
· 微錯清單
· Inspection Moderator’s Checklist
· 評審負責人的檢查表
· Inspection Lessons Learned Questionnaire
· 評審經驗教訓問卷
· defect checklists for several types of software work products
· 各種軟件工作產品的缺陷檢查表
3. Risk Assessment Guidance（風險評估指南）
To judge which software components (or portions of components) to review and what type of review method to use, consider the following risk criteria:
在判斷哪些軟件組件（或組件的部分）需要評審及使用哪種評審方法的時候，需要考慮如下的風險條件：
· components that use new technology, techniques, or tools
· 使用了新技術，方法，工具的組件
· key architectural components
· 關鍵的架構性的組件
· complex logic or algorithms that are difficult to understand but must be accurate and optimized
· 難以理解，卻又必須準確和優化的複雜邏輯或算法
· mission-, security-, or safety-critical components with dangerous failure modes
· 具有危險失敗模式的組件，而且是任務、可靠性、安全性關鍵的
· components having many exception conditions or failure modes
· 具有多個異常條件或失敗模式的組件
· exception handling code that cannot easily be tested
· 不易測試的異常處理代碼
· components that are intended to be reused
· 打算複用的組件
· components that will serve as models or templates for other components
· 將作爲其他組件的模型或模板的組件
· components that affect multiple portions of the product
· 影響產品多個部分的組件
· complex user interfaces
· 複雜的用戶界面
· components created by less experienced developers
· 由缺乏經驗的開發者創建的組件
· code modules having high cyclomatic complexity
· 具有高度圈複雜性的代碼模塊
· modules having a history of many defects or changes
· 以往具有很多缺陷或變更的模塊
Work products that fit in one or more of these categories are considered high risk. A product is considered low risk if an undetected error will not significant affect the project’s ability to meet its schedule, quality, cost, and feature objectives. Use inspections for high-risk work products, or the high-risk portions of large products, and for major work products that are about to be baselined. Less formal reviews are acceptable for other work products
符合這些條件中一種或幾種的工作產品被認爲是高風險的。如果未發現的缺陷對項目達成進度，質量，成本及特徵目標的能力沒有重大影響，則該工作產品被認爲是低風險的。評審只用於高風險的工作產品或大產品的高風險部分或將要被基線化的主要工作產品。對其他的工作產品可以進行不太正式的評審。
4. Participants（參與者）
Table 1 suggests project roles who might review different work products. Not all of these perspectives need to be represented. In general, a work product should be reviewed by:
表1列出了評審不同工作產品的項目角色。不是所有這些角度都必須表現出來。通常，一項工作產品的評審需要有：
· the author of any predecessor document or specification
· 以往的文檔或規範的創建者
· someone who must base their subsequent work on the work product
· 以該工作產品爲基礎進行後續工作的人。
· peers of the author
· 創建者的同行們
· anyone responsible for a component to which the work product interfaces
· 使用該工作產品接口的組件的負責人
Attendance by anyone with supervisory authority over the author is by invitation of the author only.
對工作產品創建者具有監督權力的人只能在創建者的邀請下參加評審。
Table 1. Review Participants for Different Types of Work Products.
表1. 各類工作產品的參評人
| Work Product Type工作產品類型 | Work Product Type工作產品類型 |
| Architecture or High-Level Design架構或概要設計 | architect, requirements analyst, designer, project manager, integration test engineer架構師，需求分析師，設計師，項目經理，集成測試工程師 |
| Detail Design詳細設計 | designer, architect, programmer, integration test engineer設計師，架構師，程序員，集成測試工程師 |
| Process Documentation過程文檔 | process improvement group leader, process improvement working group members, management-level process owner, practitioner representatives who will use the process過程改進組負責人，過程改進工作組成員，管理級的過程擁有者，使用過程的實踐者的代表 |
| Project Plans項目計劃 | project manager, program manager, business sponsor, marketing or sales representative, technical lead, quality assurance manager項目經理，產品經理，需求提出者，市場或銷售代表，技術負責人，質量保證工程師 |
| Requirements Specification需求規格說明書 | requirements analyst, project manager, architect, designer, system test engineer, quality assurance manager, user or marketing representative, documentation writer, subject matter expert, technical support representative需求分析師，項目經理，架構師，設計師，系統測試工程師，質量保證經理，用戶或市場代表，文檔編寫者，業務專家，技術支持代表 |
| Source Code源代碼 | programmer, designer, unit test engineer, maintainer, requirements analyst, coding standards expert程序員，設計師，單元測試工程師，維護者，需求分析師，編碼標準專家 |
| System Technical Documentation系統技術文檔 | author, project manager, maintainer, programmer創建者，項目經理，維護者，程序員 |
| Test Documentation測試文檔 | test engineer, programmer (unit testing) or architect (integration testing) or requirements analyst (system testing), quality assurance representative測試工程師，程序員（單元測試）或架構師（集成測試）或需求分析師（系統測試），質量保證代表 |
| User Interface Design用戶界面設計 | user interface designer, requirements analyst, user, application domain expert, usability or human factors expert, system test engineer用戶界面設計師，需求分析師，用戶，應用領域專家，可用性或人體專家，系統測試工程師 |
| User Manual用戶手冊 | ocumentation writer, requirements analyst, user or marketing representative, system test engineer, maintainer, designer, instructional designer, trainer, technical support representative文檔編寫者，需求分析師，用戶或市場代表，系統測試工程師，維護人員，設計師，用戶教育設計師，培訓師，技術支持代表 |