Formal Inspection Scenes

Slides:



Advertisements
Similar presentations
COMP8130 and 4130Adrian Marshall Verification & Validation INSPECTIONS Adrian Marshall.
Advertisements

Teamwork. Can be in person or virtually. Organizing a Team Project Appoint a group manager Define a clear and definite goal Identify the type of document.
Software Project Management Lecture # 11. Outline Quality Management ( chapter 26 - Pressman )  Software reviews  Formal Inspections & Technical Reviews.
Practical Skills for Leaders Archdiocese of Cape Town Centre for Pastoral Development.
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.
Code Inspections CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 23, 2003.
Code Inspections CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 22, 2007.
SE 555 Software Requirements & Specification Requirements Validation.
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.
OHT 4.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Leaders Manage Meetings
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.
Software Reviews. Introduction/Motivation When creating written documents, it is a good idea to have someone else proof read your work. Oftentimes an.
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.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Product Design Finalization; Inspections.
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.
Code Reviews James Walden Northern Kentucky University.
Facilitate Group Learning
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.
By Godwin Alemoh. What is usability testing Usability testing: is the process of carrying out experiments to find out specific information about a design.
HFT 2220 Chapter 6 Orientation and Training. Orientation Why do we do it? Why do we do it?
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.
Advances In Software Inspection
Peer Review Presented by : Basker George. Peer ( 同等的人 ) Review( 回顾 ) During the development of software, defects are inevitably ( 不可避免 ) injected. Defect.
Inspections - Page P3-L14-1 MEF-TRANSITION-P3-L14-1 Dr. M.E. Fayad Lesson 14: Inspections SoftwareEngineeringII.
IB Language A: Language and Literature Year 2 Individual Oral Commentaries.
C.C.C.P Caribbean Coaching Certification Program.
Software Project Management Lecture # 12. Outline Quality Management ( chapter 26 - Pressman )  SQA  Who does it?  SQA Activities  Software reviews.
Verification vs. Validation Verification: "Are we building the product right?" The software should conform to its specification.The software should conform.
Interview Skills.
Chapter 25 Process Improvement.
CIS 375 Bruce R. Maxim UM-Dearborn
Stakeholder consultations
Facilitator Training Introduction to the Model
Writing your reflection in Stage 1 & 2 Indonesian (continuers)
Communication Skills.
Data Collection Interview
Requirements Analysis Scenes
Adapted from PPT developed by Jhpiego corporation
Putting it all together: Writing research proposals and reports
INTRODUCING THE TOOLKIT L3 & L5
Managing the Captain and the Coach
Tools for Teaching Boy’s Town Skills
Creating a Social Media Policy
Strategies for Preparing for Interviews
Performance Feedback Training
INTRODUCTION TO OSHA Lesson
Continuing Education Module
Evaluating the Quality of Student Achievement Objectives
What documents make up the learning program documentation?
Internal Audit Training
Give 5 facts about having a positive attitude
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.
Customer Focus.
Thesis and Dissertation Proposals
How To Handle The Irate Customer
Communication GAA Award 2 1.
QA Reviews Lecture # 6.
Code Inspection Class Exercise – Inspection Roles
Naming & Code Reviews.
Communication Skills.
Rebounding from Failure
Software Reviews.
Presentation transcript:

Formal Inspection Scenes Video Case Study Video Case Study Module Number: VS02 This course material was developed with NSF – TUES award # 1245036

Formal Inspections Case Study Video: Formal Inspection Scenes Developed by: Robert Morris University What is this ? brief dramatizations demonstrates appropriate and inappropriate conducts during Formal Inspection Process

Inspections Remember Inspections are Characterized by Explicit Entry and Exit Criteria Individual preparation by inspectors Defined roles of Moderator, Reader, Producer and Recorder. Training for Moderators Use of Checklist Limitation of discussion to identification and classification of defects A requirement that successful completion of rework is necessary to complete inspection. Formal data collection, reporting and analysis

Questions Prior to Video Display What is a software review? Why is it important? What is code review? Is code review a formal inspection process? What is the role of inspectors in a code review meeting? Does a manger of a software work product participate in inspection meetings?

SCENE - 1

Video Case Study – SCENE 1 What happened in this Scene? Is this procedure normal? Why? What module is being inspected? Is it important to budget the inspection in the plan? Why? Why did Michael leave with an uncertain face?

SCENE - 2

Video Case Study – SCENE 2 Does Michael look like someone who is serious about getting a task done following a process and timeline? What mistake did Michael make in his thoughts about scheduling the inspection? Michael chose to use a different language than the group normally uses. What problem(s) has this brought on? Was it okay for Michael to test before inspect? Why is it important to talk to Anil?

SCENE - 3

Video Case Study – SCENE 3 In this scene is everyone’s role for the inspection meeting clear? Is it always necessary to explain the process? What required information did Dennis collect from the participants? Why is this important? Did Dennis address all questions professionally and adequately? Do you think Dennis is a good facilitator? Why? Why is Raj upset?

SCENE - 4

Video Case Study – SCENE 4 What’s happening in this scene? Is Dennis handling the meeting appropriately? Was Raj’s comment necessary i.e. the way it was expressed? Why? Why are all looking the Michael in bewilderment?

SCENE - 5

Video Case Study – SCENE 5 Did Dennis handle the situation well? Was it necessary for Sally to apologize. What is happening in this scene? Why is everyone looking at Dennis? What would you do differently?

SCENE - 6

Video Case Study – SCENE 6 What happened in this Scene? How would you do things differently? Was it okay for Dennis to stop Raj? Why?

SCENE - 7

Video Case Study – SCENE 7 What happened in this Scene? Was it okay for Sam to respond like this? Why?

Concluding Remarks

Five Review Traps to Avoid Participants don’t understand the review process. The review process isn’t followed. The right people do not participate. Review meeting drift to problem solving. Reviewers focus on style not substance. Source: Peer Reviews in Software – A Practical Guide, Karl E. Weigers, Addison-Wesley copyright © 2002

Critical Factors for a Successful Review Program Source: Peer Reviews in Software – A Practical Guide, Karl E. Weigers, Addison-Wesley copyright © 2002

Questions