Review & Inspection Process

Slides:



Advertisements
Similar presentations
Collaborative Code Construction: Code Reviews and Pair Programming CPSC 315 – Programming Studio Spring 2009.
Advertisements

Systematic Software Reviews Software reviews are a “quality improvement processes for written material”.
Software Project Management Lecture # 11. Outline Quality Management ( chapter 26 - Pressman )  Software reviews  Formal Inspections & Technical Reviews.
Formal Technical Reviews
Static Technique. Static Technique - Review  A way of testing software work products  Program code, requirement spec., design spec.  Test plan, test.
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”
Chesapeake Chapter Webinar Go Virtual or Go Home June 19, 2014 Kelson Forsgren and Jack Fagan.
Code Inspections CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 22, 2007.
CSC 395 – Software Engineering Lecture 9: Testing -or- How I Stopped Worrying and Learned to Love the Bug.
Verification and Validation
University of Southern California Center for Software Engineering CSE USC Sep. 24, 2009 v01 ©USC-CSE CS 577a Software Engineering I Peer Review.
Design Reviews Peer Reviews. Agenda Peer Reviews Participants of Peer Review Preparation for a Peer Review Session The Peer Review Session Post-peer Review.
1 Software Reviews - FTR SWENET Module QUA2. Formal Technical Review u Features – Formal v Scheduled event v Defined procedure v Reported result – Technical.
Software Inspections and Walkthroughs By. Adnan khan.
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.
SoITSSpecifications of IT systems? 1 Specifications of IT systems checking and validating Jens Bennedsen and Peter Gorm Larsen
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 10: Testing and Inspecting to Ensure High Quality Part 4:
Software Inspections. Defect Removal Efficiency The number of defects found prior to releasing a product divided by The number of defects found prior.
Lecture 16 Formal Technical Reviews (FTRs) (also know as inspections) FOR0383 Software Quality Assurance 9/19/20151Dr Andy Brooks Don´t review in your.
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.
Formal and Informal Peer Reviews
© 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.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Product Design Finalization; Inspections.
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.
... there is no particular reason why your friend and colleague cannot also be your sternest critic. --Jerry Weinberg --Jerry Weinberg.
CHAPTER 9 INSPECTIONS AS AN UP-FRONT QUALITY TECHNIQUE
Software Testing and Maintenance 1 Code Review  Introduction  How to Conduct Code Review  Practical Tips  Tool Support  Summary.
(1) Introduction to Software Review Philip Johnson Collaborative Software Development Laboratory Information and Computer Sciences University of Hawaii.
Chapter 12: Software Inspection Omar Meqdadi SE 3860 Lecture 12 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
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.
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.
© Michael Crosby and Charles Sacker, 2001 Systematic Software Reviews Software reviews are a “quality improvement process for written material”.
Management of Software Project CSM Review By:Nafas.
Peer Review Presented by : Basker George. Peer ( 同等的人 ) Review( 回顾 ) During the development of software, defects are inevitably ( 不可避免 ) injected. Defect.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Software inspections l Involve people examining the source representation with.
Software Project Management Lecture # 12. Outline Quality Management ( chapter 26 - Pressman )  SQA  Who does it?  SQA Activities  Software reviews.
© Mahindra Satyam 2009 Inspections and Reviews QMS Training.
CIS 375 Bruce R. Maxim UM-Dearborn
Software Configuration Management (SCM)
Verification and Validation
Verification and Validation
CMMI – Staged Representation
Software Inspections and Testing
Peer Reviews 11/21/2018.
Conducting Effective Meetings
Software Engineering: Principles and Practices (Second Edition)
Systematic Software Reviews
G&W Chapter 20: Technical Reviews Software Specification Lecture 27
Collaborative Code Construction: Code Reviews and Pair Programming
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.
Before During After Follow-up Resolve Review Pre-review Familiarize
COLLABORATIVE CODE CONSTRUCTION: CODE REVIEWS AND PAIR PROGRAMMING
CMPT 371 Software Management
Applied Software Project Management
Collaborative Code Construction: Code Reviews and Pair Programming
QA Reviews Lecture # 6.
WALKTHROUGH and INSPECTION
Collaborative Code Construction: Code Reviews and Pair Programming
Software Reviews.
Testing, Inspection, Walkthrough
Collaborative Code Construction: Code Reviews and Pair Programming
Role Based Peer Reviews A. Winsor Brown Oct. 2, 2009
3. Software Quality Management
Collaborative Code Construction: Code Reviews and Pair Programming
Presentation transcript:

Review & Inspection Process

Review Materials Source Document Checklist Supporting Documents Invitation Master Plan Issue/Defect Log Data Summary

Review Methods Synchronous Asynchronous Traditional Approach Meeting-based Asynchronous Relatively new area Meeting replaced with email (or other electronic) communication

Synchronous Review Review is separated into 5/6 phases (Planning) Overview Preparation Inspection Rework Follow-up

Planning/Overview Reviewers are selected Roles are assigned Documents are distributed General review task is discussed

Review Roles .

Roles: Leader Manages inspection Acts as moderator Determines document worthiness Identifies/invites reviewers Assigns roles Distributes documents Schedules meeting times/locations

Roles: Author . Creates the document for review Assists with answering questions Typically not directly involved in review Makes corrections to document if necessary .

Roles: Inspector/Reviewer Complete familiarization of document on time Review document(s) for defects Look for assigned defects (if appropriate) Make use of checklists or other supporting documents Contact leader early if problems arise or if the review might be a waste of time

Roles: Scribe/Recorder Records issues as they are raised Ideally not the moderator or reviewer Record information legibly

Inspection/Review Meeting Review team attempts to locate defects Defects are not fixed at this point Meeting < 2 hours long!

Inspection/Review (cont.) Round-robin approach or Reader approach Scribe records all issues Where defect was located Why is it a defect (cite requirement or checklist) Suggested severity level (Major, minor) Do Not record names of reviewers with defect Try to make visible to all participants (avoid duplication) .

Rework Author receives defect log Identifies true defects vs. “false positives” Fixes defects, provides justification for false positive

Follow-Up Leader verifies all defects have been addressed Decides if document passes review or if another review is necessary

Review Pitfalls Insufficient Preparation Moderator Domination Incorrect Review Rate Ego-involvement and Personality Conflict Issue Resolution and Meeting Digression Recording Difficulties and Clerical Overhead