KENDA ALBERTSON Formal Peer Review Processes for Software and Documents.

Slides:

Advertisements

Similar presentations

Configuration Management

Advertisements

Validating and Improving Test- Case Effectiveness Yuri Chernak Presented by Michelle Straughan.

1.Quality-“a characteristic or attribute of something.” As an attribute of an item, quality refers to measurable characteristics— things we are able to.

MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.

More CMM Part Two : Details.

ITIL: Service Transition

Static Technique. Static Technique - Review  A way of testing software work products  Program code, requirement spec., design spec.  Test plan, test.

© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.

Testing Without Executing the Code Pavlina Koleva Junior QA Engineer WinCore Telerik QA Academy Telerik QA Academy.

Code Inspections CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 22, 2007.

SE 555 Software Requirements & Specification Requirements Validation.

 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.

1 Software Inspections and Walkthroughs Author: A. Frank Ackerman Presented by Cynthia Johnson EEL6883.

Degree and Graduation Seminar Project Management Processes

Software Inspections and Walkthroughs By. Adnan khan.

N By: Md Rezaul Huda Reza n

Callis ApS, Copyright © Reviewer Training Material Callis Reviewer version 1.1.

Page 1 MODEL TEST in the small GENERALIZE PROGRAM PROCESS allocated maintenance changes management documents initial requirement project infrastructure.

Article: Source Code Review Systems Author: Jason Remillard Presenter: Joe Borosky Class: Principles and Applications of Software Design Date: 11/2/2005.

S oftware Q uality A ssurance Part One Reviews and Inspections.

Software Quality Assurance Activities

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.

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.

程建群博士 (Dr. Jason Cheng) 年 03 月 Software Engineering Part 06.

CPSC 873 John D. McGregor Session 4 Requirements V & V - continued.

Software Quality Assurance SE Software Quality Assurance What is “quality”?

What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Product Design Finalization; Inspections.

Fun, fun, fun. But first … the code review Preparation Process.

Quality Activity Matrix Presented by Sandra Toalston President, SanSeek 1.

Formal Technical Reviews Matt Graham 18 November 2004 EECS 814 University of Kansas.

Monitoring and Evaluation Management of a Training Program.

Georgia Institute of Technology CS 4320 Fall 2003.

INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.

CHAPTER 9 INSPECTIONS AS AN UP-FRONT QUALITY TECHNIQUE

© 2012 IBM Corporation Rational Insight | Back to Basis Series Chao Zhang Code Review.

Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?

Code review. informal formal ad hoc reviewpair programmingwalk throughinspection/review.

Code Reviews James Walden Northern Kentucky University.

Documentation Workflows D. Olson 13 Mar 2006 DRAFT.

Software Engineering Lecture # 1.

Project Management Basics

© Michael Crosby and Charles Sacker, 2001 Systematic Software Reviews Software reviews are a “quality improvement process for written material”.

Quality Assurance at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.

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

Peer Review Overview Meeting [Date] [Product name]

Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.

JRA1 Meeting – 09/02/ Software Configuration Management and Integration EGEE is proposed as a project funded by the European Union under contract.

Software Project Management Lecture # 12. Outline Quality Management ( chapter 26 - Pressman )  SQA  Who does it?  SQA Activities  Software reviews.

by: Er. Manu Bansal Deptt of IT Software Quality Assurance.

Agenda  Purpose  Processes  Deliverables  Executing Activities 4.3.

ITIL: Service Transition

Configuration Management

Software Quality Control and Quality Assurance: Introduction

Software Configuration Management (SCM)

Configuration Management

TechStambha PMP Certification Training

Engineering Processes

Air Traffic Quality Assurance Program

QA Reviews Lecture # 6.

Engineering Processes

Testing and Inspection Present and Future

Software Reviews.

Testing, Inspection, Walkthrough

Verification and Validation

Presentation transcript:

KENDA ALBERTSON Formal Peer Review Processes for Software and Documents

What is a peer review? Definition according to Merriam-Webster: a process by which something proposed (as for research or publication) is evaluated by a group of experts in the appropriate field

Purpose of Peer Reviews Find and record defects before a document is released or code is integrated Receive input from many product experts and stakeholders

Who is Involved? Author Moderator Product Experts / Stakeholders / Reviewers Recorder (Meetings) Quality Assurance

Process Prepare the Review Send Review Notice Hold a Meeting to Discuss Findings (optional) Change Product Based on Recommendations Release Product

Prepare the Review Author  Prepares the material for the review package Moderator  Reviews material for readiness  Identifies product experts and stakeholders to invite as reviewers  Send review notice to reviewers  Ensures reviewers have enough time to review Reviewers  Review the product  Record time spent

Hold a Meeting Moderator  Conducts the meeting Author  Answers questions about the product Reviewers  Present defects in the material Recorder  Records defects  Records review time for each reviewer

Fix Product Author  Fixes product based on recommendations Moderator  Verifies fixes to product

Role of Quality Assurance Supervises process Reviews the document Collects review metrics to track effectiveness

Useful Metrics Review Time Meeting Length Number of Defects Found Types of Defects (Minor, Major, etc.)

Tools for Reviews Defect Tracking System (Bugzilla) Excel Spreadsheet Checklists Tools Built in to Editors or IDE  Microsoft Word - tracked changes  IBM Rational - CodeCollaborator

CodeCollaborator

Conclusion Peer Reviews are very useful for finding defects earlier in the process Peer Reviews are more effective when:  Correct stakeholders are included  Reviewers are given adequate time Important to collect metrics to evaluate effectiveness

Questions?

References 11 proven practices for more effective, efficient peer code review. Cohen, Jason. ry/11-proven-practices-for-peer-review/ ry/11-proven-practices-for-peer-review/ Merriam-Webster Online. webster.com/dictionary/peer%20reviewhttp:// webster.com/dictionary/peer%20review