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

Slides:



Advertisements
Similar presentations
Chapter 24 Quality Management.
Advertisements

Verification and Validation
MODELING THE TESTING PROCESS Formal Testing (1.0) Requirements Software Design Risk Data Approved, Debugged, Eng. Tested Code Automated Test Tools Tested.
MIS 325 PSCJ. 2  Business processes can be quite complex  Process model: any abstract representation of a process  Process-modeling tools provide a.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #7 Software Engineering.
Inspection (c) 2007 Mauro Pezzè & Michal Young Ch 18, slide 1 Photo credit jurvetson on Flickr.com; creative commons attribution license.
Software Quality Assurance Inspection by Ross Simmerman Software developers follow a method of software quality assurance and try to eliminate bugs prior.
Testing Without Executing the Code Pavlina Koleva Junior QA Engineer WinCore Telerik QA Academy Telerik QA Academy.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
SE 555 Software Requirements & Specification Requirements Validation.
1 Copyright © 2014 Tata Consultancy Services Limited Source Code Management using Rational Team Concert IBM Rational, Alliance & Technology Unit 2 July.
1 Software Inspections and Walkthroughs Author: A. Frank Ackerman Presented by Cynthia Johnson EEL6883.
KENDA ALBERTSON Formal Peer Review Processes for Software and Documents.
1CMSC 345, Version 4/04 Verification and Validation Reference: Software Engineering, Ian Sommerville, 6th edition, Chapter 19.
OHT 4.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Software Inspections and Walkthroughs By. Adnan khan.
© 2012 IBM Corporation Rational Insight | Back to Basis Series SCM introduction Chu Shu June 2012.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Verification and Validation.
© 2012 IBM Corporation Rational Insight | Back to Basis Series Translation Verification Testing Rational Insight - Jiang Xuan
SoITSSpecifications of IT systems? 1 Specifications of IT systems checking and validating Jens Bennedsen and Peter Gorm Larsen
© 2012 IBM Corporation Rational Insight | Back to Basis Series Chao Zhang Unit Testing.
S oftware Q uality A ssurance Part One Reviews and Inspections.
© 2012 IBM Corporation Rational Insight | Back to Basis Series Work on a Defect from QA Liu Xue Ning.
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
Software Process Guidelines VIETTEL Corporation. CONTENTS I.Standard folder structure II.Review Process III.Data Repository IV.Naming Convention 2.
Phil Cronin Anne Hill Allen Schones CIS841 Summer on Campus 1998 IN-PROCESS INSPECTIONS FOR OBJECT ORIENTED DESIGNS.
Disciplined Software Engineering Lecture #7 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
Formal Technical Reviews Matt Graham 18 November 2004 EECS 814 University of Kansas.
CHAPTER 9 INSPECTIONS AS AN UP-FRONT QUALITY TECHNIQUE
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 7 1 Design and Code Reviews - Overview What are design and code.
Managing Change 1. Why Do Requirements Change?  External Factors – those change agents over which the project team has little or no control.  Internal.
Ch 22 Verification and Validation
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Code review. informal formal ad hoc reviewpair programmingwalk throughinspection/review.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Reviews mae, fall 11. Review What: – Have skilled people assess your work –Requires that you have work product that is reviewable Why: – Find problems.
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”.
Reviews Chapter 5 Applied Software Project Management, Stellman & Greene See also:
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Software inspections l Involve people examining the source representation with.
Peer Review Overview Meeting [Date] [Product name]
© 2012 IBM Corporation Rational Insight | Back to Basis Series Insight Post-Release Delivery Chu Shu July 2012.
More SQA Reviews and Inspections. Types of Evaluations  Verification Unit Test, Integration Test, Usability Test, etc  Formal Reviews  aka "formal.
COMM 3050 – Online Project Update. Project Roles  Organizer Responsible for creating Zoom account technical aspects and posting recorded meeting to S:
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
SQA COMPONENTS IN THE PROJECT LIFE CYCLE C HAPTER 8 Dr. Ahmad F. Shubita.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.
© 2012 IBM Corporation Rational Insight | Back to Basis Series Working on Enhancement/Defect Nick Hu Shuai 2012/05/17.
Software Reviews Ashima Wadhwa.
Software Project Configuration Management
Software Quality Control and Quality Assurance: Introduction
Software Configuration Management (SCM)
Software Verification and Validation
CSC 480 Software Engineering
Verification and Validation
Verification and Validation
Verification and Validation
Verification and Validation
Reliance Supplier Corrective Action Process
Applied Software Project Management
Facility Asset Data Exchange (FADE) Design Phase
QA Reviews Lecture # 6.
Managing Multi-source Feedback
Software Reviews.
Testing, Inspection, Walkthrough
Presentation transcript:

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

© 2012 IBM Corporation Rational Insight | Back to Basis Series 2 06/19/12 Agenda Overview Purpose Process – Roles & Responsibility – Review flow – Online Review – Offline Review Example in RTC

© 2012 IBM Corporation Rational Insight | Back to Basis Series 3 06/19/12 Overview Code review provide a strict method of examining work products for early detection and elimination of errors. By error, it is meant product defect as potentially left for the next phases of the Life Cycle Model but also any design issues or imprecision that can lead to a product quality issue. Source code review has been shown to be a most effective measure for reducing cost and time to market during the software development process

© 2012 IBM Corporation Rational Insight | Back to Basis Series 4 06/19/12 Purpose Verify that work products satisfy design requirements and assess the correctness of the algorithms. Remove structural and low-level semantic coding errors, coding standards violations, and architectural violations from work products.

© 2012 IBM Corporation Rational Insight | Back to Basis Series 5 06/19/12 Process Roles & Responsibilities Author – The author is the designer who produced the work product to be inspected. Moderator – The moderator facilitates the meeting, ensures that inspectors are prepared and that the right expertise is present. Recorder – The recorder ensures all defects have been captured in review tools, updates the inspection record, and records the meeting disposition. Reviewer – The reviewer are design team members who inspect the code to find defects and record the defects found in review tools. Design Manager – is the manager or prime who is responsible for the quality of the code being reviewed.

© 2012 IBM Corporation Rational Insight | Back to Basis Series 6 06/19/12 Process Review Flow Planning & Overview Code Review Defects found ? Code review again? ReworkVerification Enter Exit Yes No Yes No

© 2012 IBM Corporation Rational Insight | Back to Basis Series 7 06/19/12 Process Online Review Author prepare code review, e.g: codes, review tools, attendee list. Author send the review invitation to attendees. Reviewer prepare code review before meeting, e.g: read codes first, prepare related knowledge. In review meeting: – Author introduces the reviewed codes – Reviewer provides comments – Recorder record comments Author correct codes against the review comments. And then: – Launch a new round review meeting if need. – Send codes to attendees to ask for offline review.

© 2012 IBM Corporation Rational Insight | Back to Basis Series 8 06/19/12 Process Offline Review Author prepare code review, e.g: codes, review tools, reviewer list. Author send the review notification to reviewers. Reviewer should review codes and fill comments in review tools. Author should reminder silent reviewer and check with them if they finish reviewing without any comments Author correct codes against the review comments and send a new review notification to reviewers.

© 2012 IBM Corporation Rational Insight | Back to Basis Series 9 06/19/12 Example in RTC Prepare codes, check in your public workspace and associate the changes set with work item. In 'Approvals' of work item, add the reviewer and approvals. RTC will automatically send a notification mail to them. Reviewer should review the codes and write the comments in work item or change the state to 'Approved' if no comment. Author need check comments and correct codes if need. When all reviewers approve the codes, the approval can change the state to 'Approved'. Author can deliver the codes to stream after get all approvals.

© 2012 IBM Corporation Rational Insight | Back to Basis Series 10 06/19/12

© 2012 IBM Corporation Rational Insight | Back to Basis Series 11 06/19/12 Revision History AuthorDateVersionComment Chao Zhang Initial Draft