© Mahindra Satyam 2009 Inspections and Reviews QMS Training.

Slides:



Advertisements
Similar presentations
Damian Gordon.  Static Testing is the testing of a component or system at a specification or implementation level without execution of the software.
Advertisements

Software Project Management Lecture # 11. Outline Quality Management ( chapter 26 - Pressman )  Software reviews  Formal Inspections & Technical Reviews.
Testing Without Executing the Code Pavlina Koleva Junior QA Engineer WinCore Telerik QA Academy Telerik QA Academy.
Code Inspections CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 23, 2003.
OHT 8.1 Galin, SQA from theory to implementation © Pearson Education Limited Review objectives Formal design reviews (FDRs) Participants Preparations.
OHT 8.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Review objectives Formal design reviews (FDRs) Participants Preparations.
SE 555 Software Requirements & Specification Requirements Validation.
Validating and Improving Test-Case Effectiveness Author: Yuri Chernak Presenter: Lam, Man Tat.
SystematicSystematic process that translates quality policy into measurable objectives and requirements, and lays down a sequence of steps for realizing.
Overview Software Quality Software Quality and Quality Assurance
© Mahindra Satyam 2009 Project Metrics QMS Training.
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.
SoITSSpecifications of IT systems? 1 Specifications of IT systems checking and validating Jens Bennedsen and Peter Gorm Larsen
Applying the Inspection Process. What Software Artifacts Are Candidates for Inspection? Software Requirements Software Designs Code Test Plans.
S oftware Q uality A ssurance Part One Reviews and Inspections.
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.
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.
© 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.
Lecture #9 Project Quality Management Quality Processes- Quality Assurance and Quality Control Ghazala Amin.
Project Planning QMS Training.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Product Design Finalization; Inspections.
Project Tracking and Monitoring QMS Training. 2 Objective To track and monitor the progress of the project and take appropriate corrective actions to.
Formal Technical Reviews Matt Graham 18 November 2004 EECS 814 University of Kansas.
Mahindra Satyam Confidential1 BASE TM Methodology Guide Quality Management System BASE TM Methodology - 17 Slides Continue Back.
© Mahindra Satyam 2009 Project Initiation QMS Training.
© Mahindra Satyam 2009 QMS Training Conducting Contract Review.
CHAPTER 9 INSPECTIONS AS AN UP-FRONT QUALITY TECHNIQUE
© Mahindra Satyam 2009 Configuration Management QMS Training.
Processing Project Proposals
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Chapter 12: Software Inspection Omar Meqdadi SE 3860 Lecture 12 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Project quality management. Introduction Project quality management includes the process required to ensure that the project satisfies the needs for which.
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.
Estimation QMS Training. Objective To arrive at accurate estimates for the project Mahindra Satyam Confidential2.
PRODUCT IMPLEMENTATION Chapter 8 Tawatchai Iempairote September 23, 2041.
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”.
TOTAL QUALITY MANAGEMENT
© Mahindra Satyam 2009 PM/PL/ML Module QMS Training Mahindra Satyam Confidential.
Advances In Software Inspection
QMS Training TM Module.
Capgemini India. 2 Project Execution Process  Onsite team will gather the requirements from client and put them in Business Requirements specification.
Mahindra Satyam Confidential Quality Management System Software Defect Prevention.
Reviews Chapter 5 Applied Software Project Management, Stellman & Greene See also:
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.
Software Project Management Lecture # 12. Outline Quality Management ( chapter 26 - Pressman )  SQA  Who does it?  SQA Activities  Software reviews.
1 Software Testing and Quality Assurance Motivation and Review of Software Verification & Validation (2)
Software Reviews Ashima Wadhwa.
Software Configuration Management (SCM)
Overview of the FEPAC Accreditation Process
Version 0.1Assessment Method Overview - 1 Process Assessment Method An objective model-independent method to assess the capability of an organization to.
Engineering Processes
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.
Informal document GRVA nd GRVA, 28 Jan Feb. 2019
Applied Software Project Management
QA Reviews Lecture # 6.
The Software Testing Life Cycle
WALKTHROUGH and INSPECTION
Configuration Management
Code Reviews Assignment Each team should perform a code review
Software Reviews.
Review & Inspection Process
Presentation transcript:

© Mahindra Satyam 2009 Inspections and Reviews QMS Training

2 © Mahindra Satyam 2009 Objective To examine work products to identify defects and to ensure that the uncovered defects are fixed Mahindra Satyam Confidential

3 © Mahindra Satyam 2009 Preparation for Inspection /Review PL  Plans for Inspections and Reviews in all phases of the project – The Inspection / Review Plan forms a part of the Project Plan  Ensures that the draft Work Products are ready for Inspection/ Review as per the Inspection/Review Plan  Schedules the Inspection / Review when the draft work product is ready  Identifies the Inspection / Review Team Mahindra Satyam Confidential

4 © Mahindra Satyam 2009 Inspection /Review Team  The Inspection Team consists of – Moderator – Author – Interpreter – Recorder – Inspectors  All the members in the Inspection Team are also Inspectors in addition to their respective roles  The Review Team consists of one or more reviewers  In case of more than one reviewer in the team, one of them will play a role of the team leader Mahindra Satyam Confidential

5 © Mahindra Satyam 2009 Process Reviews Process Inspections Process Mahindra Satyam Confidential

6 © Mahindra Satyam 2009 Inspections Process Plan for the Inspection Conduct Overview Meeting Prepare for the Inspection Conduct Inspection Meeting Conduct Follow-up Action Verify Follow-up Action Mahindra Satyam Confidential

7 © Mahindra Satyam 2009 Plan for the Inspection The moderator  Dispatches the Inspection item and relevant supporting documents to all the members in the Inspection team  Plans for the Overview meeting  Plans for the Inspection meeting  Identifies the Interpreter  Intimates the Inspection team members regarding the meetings Mahindra Satyam Confidential

8 © Mahindra Satyam 2009 Conduct Overview Meeting The author gives an overview of  The work product  The working environment  Any other dependencies to the Inspection team Mahindra Satyam Confidential

9 © Mahindra Satyam 2009 Conduct Overview Meeting The members of the Inspection team ensure that  they have a broad overview of the inspection item, and  the relevant documentation is available to them Mahindra Satyam Confidential

10 © Mahindra Satyam 2009 Prepare for the Inspection Each of the members in the inspection team will  Go through the work product  Refer the associated documents  Use relevant review checklists  Log the defects in the Inspector/Reviewer Form Mahindra Satyam Confidential

11 © Mahindra Satyam 2009 Conduct Inspection Meeting The moderator will  Arrange for the Inspection meeting  Intimate all the members of the Inspection team Mahindra Satyam Confidential

12 © Mahindra Satyam 2009 Conduct Inspection Meeting  Enough time will be given to the team members to prepare for the Inspection meeting  The time gap between the Overview meeting and the Inspection meeting will be at least one full working day  At the beginning of the Inspection meeting, the moderator ensures that each of the members in the Inspection team had spent sufficient time in preparation  Inspection Meeting may be postponed if the moderator feels that sufficient preparation has not been done Mahindra Satyam Confidential

13 © Mahindra Satyam 2009 Conduct Inspection Meeting Moderator identifies the recorder who logs the defects found in the Inspection  Recorder can be any one of the Inspection team members except the interpreter Mahindra Satyam Confidential

14 © Mahindra Satyam 2009 Conduct Inspection Meeting Interpreter paraphrases the work product and narrates each logical section of the work product  If any defect is found in that particular section, the interpreter pauses and the team will discuss the validity of the defect  Moderator ensures that the team reaches consensus on these  Recorder logs the defect details in Quantify and updates the corresponding review checklist Interpreter then resumes the paraphrasing Moderator manages the time of the Inspection Meeting taking care to see that the team does not digress or go into the details of the defect fixing Mahindra Satyam Confidential

15 © Mahindra Satyam 2009 Conduct Inspection Meeting At the end of the Inspection meeting, the work product can be  Accepted unconditionally – the Inspection is closed  Accepted conditionally – the author reworks the Work Product and gets it verified  Rejected – the work product has to be reworked and the Inspection has to be repeated either with the same Inspection team or a different Inspection team Mahindra Satyam Confidential

16 © Mahindra Satyam 2009 Conduct Follow-up Action The author of the Review item  Clarifies any ambiguous issues recorded in the inspection/review report  Close the identified defects Mahindra Satyam Confidential

17 © Mahindra Satyam 2009 Verify Follow-up Action The moderator verifies the adequacy of the follow-up action  If inadequate, further follow-up action has to be taken by the author  If adequate, the inspection is considered to be complete – the moderator signs-off the follow-up action section of the Inspection report Mahindra Satyam Confidential

18 © Mahindra Satyam 2009 Verify Follow-up Action In case there is a conflict on the Inspection report or the follow-up action between the inspection team and the author,  PL has to mediate and resolve the conflict, if the inspection team is from within the project  PM and Head(TQA) have to mediate and resolve the conflict, if the inspection team is external to the project Mahindra Satyam Confidential

19 © Mahindra Satyam 2009 Reviews Process Gather Inputs for the Review Perform the Review Conduct Follow-up Action Verify Follow-up Action Mahindra Satyam Confidential

20 © Mahindra Satyam 2009 Gather Inputs for the Review The review team gathers the inputs required for the review:  Review objective(s), which may be a part of the project plan or as identified by author  Related Documents  Review Checklists Mahindra Satyam Confidential

21 © Mahindra Satyam 2009 Perform the Review The review team performs the review, using all the inputs In case of single reviewer  Documents the review findings in the inspection/review report and corresponding checklist  Hands-over the inspection/review report to the author In case of multiple reviewers  The team documents the review findings in the individual inspector/reviewer forms  The review team leader consolidates all the comments in the inspector/reviewer forms into the inspection/ review report and corresponding checklists into a final checklist  Hands-over the inspection/review report to the author Mahindra Satyam Confidential

22 © Mahindra Satyam 2009 Conduct Follow-up Action  The author of the Review item – Clarifies any ambiguous issues recorded in the inspection/review report – Closes the identified defects Mahindra Satyam Confidential

23 © Mahindra Satyam 2009 Verify Follow-up Action The reviewer/ review team leader verifies the adequacy of the follow-up action  If inadequate, further follow-up action has to be taken by the author  If adequate, the review is considered to be complete – the reviewer/ review team leader signs-off the follow-up action section of the Inspection/ Review report Mahindra Satyam Confidential

24 © Mahindra Satyam 2009 Verify Follow-up Action In case there is a conflict on the Inspection/Review report or the follow-up action between the reviewer/ review team leader and the author,  PL has to mediate and resolve the conflict, if the review team is from within the project  PM and Head(TQA) have to mediate and resolve the conflict, if the review team is external to the project Mahindra Satyam Confidential

25 © Mahindra Satyam 2009 Objective Met The work products are examined to identify defects and the uncovered defects are fixed Mahindra Satyam Confidential