Peer Review Presented by : Basker George. Peer ( 同等的人 ) Review( 回顾 ) During the development of software, defects are inevitably ( 不可避免 ) injected. Defect.

Slides:



Advertisements
Similar presentations
UNIT-V DEFECT PREVENTION Defect prevention (Arun).
Advertisements

Damian Gordon.  Static Testing is the testing of a component or system at a specification or implementation level without execution of the software.
More CMM Part Two : Details.
Software Project Management Lecture # 11. Outline Quality Management ( chapter 26 - Pressman )  Software reviews  Formal Inspections & Technical Reviews.
Formal Technical Reviews
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #7 Software Engineering.
Static Technique. Static Technique - Review  A way of testing software work products  Program code, requirement spec., design spec.  Test plan, test.
Project Closure Report Basker George. Project Closure When does a project end? Does it end when the software has been delivered to customer & acceptance-tested?
Testing Without Executing the Code Pavlina Koleva Junior QA Engineer WinCore Telerik QA Academy Telerik QA Academy.
 Every stage from phase DESIGN in Software Development Process will have “design document” especially in analysis and design phases.  “Design document”
SOFTWARE QUALITY ASSURANCE Maltepe University Faculty of Engineering SE 410.
Code Inspections CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 22, 2007.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
Project Management Plan
SE 555 Software Requirements & Specification Requirements Validation.
Project Closure CHAPTER FOURTEEN Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Project Execution & Termination Life Cycle Execution Presented by: Basker George.
1 Software Inspections and Walkthroughs Author: A. Frank Ackerman Presented by Cynthia Johnson EEL6883.
Design Reviews Peer Reviews. Agenda Peer Reviews Participants of Peer Review Preparation for a Peer Review Session The Peer Review Session Post-peer Review.
KENDA ALBERTSON Formal Peer Review Processes for Software and Documents.
Extreme Programming Software Development Written by Sanjay Kumar.
Software Inspections and Walkthroughs By. Adnan khan.
Slide 6.1 CHAPTER 6 TESTING. Slide 6.2 Overview l Quality issues l Nonexecution-based testing l Execution-based testing l What should be tested? l Testing.
CLEANROOM SOFTWARE ENGINEERING.
Software Inspections. Defect Removal Efficiency The number of defects found prior to releasing a product divided by The number of defects found prior.
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
Software Quality Assurance
Formal and Informal Peer Reviews
Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.
© Mahindra Satyam 2009 Defect Management and Prevention QMS Training.
Phil Cronin Anne Hill Allen Schones CIS841 Summer on Campus 1998 IN-PROCESS INSPECTIONS FOR OBJECT ORIENTED DESIGNS.
Project Monitoring ( 监测 ) And Control Presented by Basker George.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Product Design Finalization; Inspections.
Quality Planning And Defect Estimation Presented by Basker George.
Formal Technical Reviews Matt Graham 18 November 2004 EECS 814 University of Kansas.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
CHAPTER 9 INSPECTIONS AS AN UP-FRONT QUALITY TECHNIQUE
1-2 Training of Process Facilitators 3-1. Training of Process Facilitators 1- Provide an overview of the role and skills of a Communities That Care Process.
Software Testing and Maintenance 1 Code Review  Introduction  How to Conduct Code Review  Practical Tips  Tool Support  Summary.
Ch-1 Introduction The processes used for executing a software project have major effect on quality of s/w produced and productivity achieved in project…
Inspection and Review The main objective of an Inspection or a Review is to Detect Defects. (Today -there may be some other goals or broader definition.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
Inspection and Review The main objective of an Inspection or a Review is to detect defects. This activity and procedure was first formalized by Mike Fagan.
Project management Topic 8 Quality Review. Overview of processes Prepare for Quality Review Questions list Meeting Agenda Review Meeting Sign-off Product.
© Michael Crosby and Charles Sacker, 2001 Systematic Software Reviews Software reviews are a “quality improvement process for written material”.
Advances In Software Inspection
QMS Training TM Module.
Mahindra Satyam Confidential Quality Management System Software Defect Prevention.
Management of Software Project CSM Review By:Nafas.
Peer Review Overview Meeting [Date] [Product name]
Chapter 05 Quality Planning SaigonTech – Engineering Division Software Project Management in Practice By Pankaj Jalote © 2003 by Addison Wesley.
Project Management Methodology Project Closing. Project closing stage Must be performed for all projects, successfully completed or shut off by management.
Software Project Management Lecture # 12. Outline Quality Management ( chapter 26 - Pressman )  SQA  Who does it?  SQA Activities  Software reviews.
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
Software Reviews Ashima Wadhwa.
Software Quality Control and Quality Assurance: Introduction
CIS 375 Bruce R. Maxim UM-Dearborn
Software Configuration Management (SCM)
Peer Reviews 11/21/2018.
Inspection and Review The main objective of an Inspection or a Review is to detect defects. (Not for Giving Alternative Solutions) This activity and procedure.
QA Reviews Lecture # 6.
Software Reviews.
Testing, Inspection, Walkthrough
Review & Inspection Process
Role Based Peer Reviews A. Winsor Brown Oct. 2, 2009
3. Software Quality Management
Presentation transcript:

Peer Review Presented by : Basker George

Peer ( 同等的人 ) Review( 回顾 ) During the development of software, defects are inevitably ( 不可避免 ) injected. Defect can be injected at any stage. The main goal of the project is to develop software that has no defects or has few defects as possible. Therefore defects removal is a very important activity.

Cont… Two approach used to identify defects Review Testing Testing can be done only on executable system, where as Review is general can be done on documents or any system that cannot be executed.

Cont… There are many ways of doing Review A formal group review, also called ( 检查 ) inspection, is the best way of identifying defects. Software inspection are recognized Industry best practice. That is why Peer review is a separate KPA of CMM.

Cont… Group review is a review of software work product by group of peers following a clearly defined process. The goal is to improve Quality & productivity by finding defects in a cost- effective ( 有成本效益的 ) manner.

Characteristics of Group review Conducted by technical people for technical people It is a structured process with defined roles for participants ( 参与者 ). Before the review begins, they prepare in advance ( 提前 ) the questions & concerns ( 关心 )

Cont… The focus is on Identifying problem, not solving the problem The review data are recorded & used for monitoring the effectiveness ( 效力 ) of the group review process.

Advantage of Group Review Best talent from the organization can be utilized for a project. They provide people with a sense of achievement ( 成就 ), participation ( 分享 ) & recognition( 赞誉 ). By reviewing the output of other people, participants develop their skills. It build team spirit It helps defect prevention.

Review Process Planning Rework & follow-up Group review meeting Preparation & overview Work product For review Schedule, review team, invitation Self preparation logs Defect log, recommendation Reviewed work product, summary report

Planning Objective prepare for group review by selecting the group team Schedule the review Activities Verify entry criteria Select the group review team Prepare the group review package for distribution

Cont… Check the entry criteria are satisfied by the work product Review team is formed, no superior is included, but project leader may take part The package is distributed for review work The package includes Work product to be reviewed Specifications, checklist & Standards

Overview & Preparation The purpose of the overview & preparation phase is to deliver the package for review to the reviewers Explain the work product, so that reviewers prepare for the group review meeting Entry criteria: is that group review package is ready for distribution & group review team is ready. Exit criteria: reviewer submit the log of errors detected during their individual review to the moderator ( 仲裁人 ).

Cont… Measurements: Efforts for preparation Number of defects Number of issues Severity ( 严肃 ) of defects

Major Activities Call an opening meeting to describe the group review objectives Provide a overview ( 总的看法 ) of the work product & review process Review the group review work individually Record defects & issues & submit them to moderator Record the time spent on preparation & submit it to the moderator

Group Review Meeting The basic purpose of Group Review is to come out with the Final DEFECT LIST Entry criteria: moderator is satisfied that all reviewers are ready for the meeting. Output: defect log Measurement: Effort spent on group meeting Number of defects detected Type of defect detected Origin of defect

Major activities of Group Review Check the preparedness of the reviewers Conduct the group review meeting Record the defects Decide weather re-review is required Summarize the issues & action items Make review recommendation for the next stage Close the meeting

Rework & Follow-up The author has to perform rework to correct all defects raised during the group review meeting. Perform investigation ( 调查 ) on open issues & provide results to the author Prepare a summary report & send it to SEPG

Roles & Responsibilities The group review is a structured process Different people have different responsibility The key roles Moderator Scribe( 抄写员 ) Reviewer Reader and Author

Cont… A person can have many roles Author cannot be Moderator or Reader Moderator cannot be reader Therefore for a group review three person are required Author Moderator Reader

Responsibilities of Moderator Assist the author in selecting the reviewers and arranging for their participation Schedule the group review meeting Conduct a pre-review session and ensure that the reviewers understand both the responsibilities & the group review process. Ensure that the entry criteria for the meeting are met

Responsibilities of Moderator Ensure that all participants are prepared & have submitted self preparation logs Conduct the group in an orderly & efficient manner Ensure group review starts & ends on time Ensure that the meeting stays focused on the main task of defect identification

Responsibilities of Moderator Ensure that all identified problems are recorded & resolution ( 决议 ) responsibility are assigned. Track each problem to resolution or ensure that it is tracked by some one else. Ensure that group review summary form ( 表格 ) is completed. Communicate ( 通信 ) the group review result to the SEPG & others.

Duties of reviewer Be prepared for group review Be objective; focus on issues rather than on people Offer suggestion or problem solution before or after group review Address major issues & submit minor issues separately during preparation If something is not clear, do not hesitate ( 不愿 ) to stop When proved wrong, move on.

Responsibilities of the author Ensure work is ready for review Identify the review team in consultation with the project leader & the moderator. Provide copies of group review package that is distributed to reviewers Promptly resolve all identified issues Remain objective & avoid being defensive ( 自卫的 ).

One person review Although group review is a highly effective way of identifying defect, but Cost & resource is high Therefore for a Medium Critical ( 评论的 ) products, One person performs the review. The reviewer generates Issues log & defects logs, & the project leader is responsible to track defects to closure.

Guidelines for selecting work product for review. All product of a project may not undergo group review. It may be decided by project leader Since early part of project life cycle are very critical, it is recommended that the following work product be group reviewed.

Cont… Project Management Plan Requirement Specification System test plan High level design Integration test plan