【正文】 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: ? 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 ponent 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. Work Product Type Suggested Reviewers Architecture or HighLevel 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, managementlevel 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 Peer Review Process Description anization Page 3 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 documentation writer, requirements analyst, user or marketing representative, system test engineer, maintainer, designer, instructional designer, trainer, technical support representative Peer Review Process Description anization Page 4 5. Inspection Procedure Participants The roles and responsibilities shown below pertain to the inspection process. All participants are inspectors, in addition to any specialized role they might have. At least three participants, including the author, are required for an inspection. If only three people participate in an inspection, the moderator shall also serve as recorder or reader. The author may not serve as reader, moderator, or recorder. Role Responsibilities Author ? Creator or maintainer of the work product to be inspected. Initiates the inspection process by asking the peer review coordinator to assign a moderator. ? States his or objectives for the inspection. ? Delivers work product and its specification or predecessor document to moderator. ? Works with moderator to select inspectors and assign roles. ? Addresses items on the Issue Log and Typo Lists. ? Reports rework time and defect counts to moderator. Moderator ? Uses Inspection Moderator’s Checklist as a work aid. ? Plans, schedules, and leads the inspection events. ? Works with author to select inspectors and assign roles. ? Assembles inspection package and delivers it to inspectors at least 3 days prior to the inspection meeting. ? Determines whether preparation is sufficient to hold the meeting. If not, reschedules the meeting. ? Facilitates inspection meeting. Corrects any inappropriate behavior. Solicits input from inspectors as reader presents each section of the work product. Records any action items or side issues that arise during the inspection. ? Leads inspection team in determining the work product appraisal. ? Serves as verifier or delegates this responsibility to someone else. ? Delivers pleted Inspection Summary Report to the anization’s peer review coordinator. Reader Presents portions of the work product to the inspection team to elicit ments, issues, or questions from inspectors. Recorder Records and classifies issues raised during inspection meeting. Inspector Examines work product prior to the inspection meeting to find defects and prepare for contributing to the meeting. Records preparation time. Participates during the meeting to identify defects, raise issues, and suggest improvements. Verifier Performs followup to determine whether rework has been performed appropriately and correctly. Peer Review Coordinator Custodian of the project’s inspection metrics database. Maintains records of inspections conducted and data from the Inspection Peer Review Process Descripti