1 reviews8 Software Reviews, Walkthroughs, and Inspections The standard technique to ensure quality in software development.

Slides:



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

Formal Process of QA and quality related certifications Formal Process of QA and quality related certifications MIM 3 rd year – Sem V Abhishek Mishra –
Damian Gordon.  Static Testing is the testing of a component or system at a specification or implementation level without execution of the software.
Software Project Management Lecture # 11. Outline Quality Management ( chapter 26 - Pressman )  Software reviews  Formal Inspections & Technical Reviews.
Formal Technical Reviews
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 6/e (McGraw-Hill 2005). Slides copyright 2005 by Roger Pressman.1.
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”
SOFTWARE QUALITY ASSURANCE Maltepe University Faculty of Engineering SE 410.
Stepan Potiyenko ISS Sr.SW Developer.
1 Software Testing and Quality Assurance Lecture 2 Software Verification & Validation.
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.
Week 7: Requirements validation Structured walkthroughs Why have walkthroughs When to have walkthroughs Who participates What procedures are helpful Thoughtless.
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.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
SE 555 Software Requirements & Specification Requirements Validation.
University of Sunderland CIFM03Lecture 1 1 Quality Management of IT CIFM03 Introduction.
Software Quality Assurance
1 Software Inspections and Walkthroughs Author: A. Frank Ackerman Presented by Cynthia Johnson EEL6883.
Even More SQA: Work Procedures
ARC 807: Professional Practice and Procedure Department of Architecture, Federal University of Technology, Akure, Nigeria ARC 807: Professional Practice.
Introduction to Engineering and Urban Planning How to be a Successful Engineer.
Software Quality Chapter Software Quality  How can you tell if software has high quality?  How can we measure the quality of software?  How.
Overview of the research process. Purpose of research  Research with us since early days (why?)  Main reasons: Explain why things are the way they are.
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.
S OFTWARE Q UALITY QA: Quality Assurance By: MSMZ.
1 Chapter 3 Defining The Problem: Project and People Skills.
Galin, SQA from theory to implementation © Pearson Education Limited 2004 Review objectives Formal design reviews (FDRs) Participants Preparations The.
Software Quality Assurance Activities
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.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Formal and Informal Peer Reviews
Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.
Soft Tech Development Inc. 1 Software Project Tracking A CMM Level 2 Key Process Area Soft Tech Development Inc.
Thomas L. Gilchrist Testing Basics Set 6: Use Cases, Audits, and Meetings By Thomas L. Gilchrist, CSQE, CSQA 2009.
S Q A.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Product Design Finalization; Inspections.
CHAPTER 9 INSPECTIONS AS AN UP-FRONT QUALITY TECHNIQUE
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.
University of Palestine software engineering department Testing of Software Systems Program Inspections, Walkthroughs, and Reviews instructor: Tasneem.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.1.
1 Phase Implementation. Janice Regan, Overview of Implementation phase Create Class Skeletons Define Implementation Plan (+ determine subphases)
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.
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”.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.1.
1 540f07reviews9sep25 Pert and Reviews Reviews S&G Chapter 5.
Advances In Software Inspection
Strategies for Collaboration CHAPTER 5. Consultation and Collaboration: Models and Skills What are the six problem-solving stages of the collaborative.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Software Project Management Lecture # 12. Outline Quality Management ( chapter 26 - Pressman )  SQA  Who does it?  SQA Activities  Software reviews.
SQA COMPONENTS IN THE PROJECT LIFE CYCLE C HAPTER 8 Dr. Ahmad F. Shubita.
Verification vs. Validation Verification: "Are we building the product right?" The software should conform to its specification.The software should conform.
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 Ashima Wadhwa.
Review Techniques SEII-Lecture 16
Software Quality Control and Quality Assurance: Introduction
Software Configuration Management (SCM)
Software Quality Assurance
Lecture 12: Chapter 15 Review Techniques
Peer Reviews 11/21/2018.
Reviews & Inspections ... there is no particular reason
Review Techniques copyright © 1996, 2001, 2005 R. S
QA Reviews Lecture # 6.
Software Reviews.
3. Software Quality Management
Presentation transcript:

1 reviews8 Software Reviews, Walkthroughs, and Inspections The standard technique to ensure quality in software development

2 reviews8 Question u What is the title of the chapter in which the material about software reviews is found? –A. SQA –B. Testing –C. Software Design

3 reviews8 Question u What do software reviews do to software? –A. correct –B. purify –C. disinfect –D. clarify

4 reviews8 Review – two definitions u A formal, scheduled activity where a designer presents material about a design and a selected group of peers evaluates the technical aspects of the design. u The inclusive name for reviews, walkthroughs, and inspections

5 reviews8 Types of Reviews u Reviews – Requirement (SRR) – Design (PDR,CDR) u Walkthroughs u Inspections – Code – Document

6 reviews8 Walkthrough u A formal, scheduled activity where a designer presents a design and traces the values of sample data through the design and a selected group of peers evaluates the technical aspects of the design.

7 reviews8 Inspection u A formal, scheduled activity where a specialist checks a document for conformity with established standards (often corporate standards)

8 reviews REVIEWS u Professionalism – be prepared – be organized – present good image u Materials in advance u TA and Instructor serve as evaluators u Team is graded on quality of effort, professionalism, and following standards u Points will be taken off for not correcting problems u Usually 50 minutes

9 reviews8 Procedures for Reviews u The evaluators prepare for the review by studying the prepared documents. u A formal report on the review is often required by management.

10 reviews8 Conduct of Reviews 1 schedule review 2 distribute materials 3 prepare 4 present 5 discuss 6 report

11 reviews8 Rules for Reviews – proper constructive attitude – proper preparation – proper environment – no management – participants should be participants – producers should determine time – distribute reports fast – record all issues in public

12 reviews8 Rules for Reviewers – prepare – be friendly – watch comments – one positive comment, one negative – raise issues, don't solve them – avoid style issues – stick to standards – stick to technical issues – make certain that everybody understands – do not evaluate producers

13 reviews8 An Example Presentation 1

14 reviews8 Purpose of Reviews u ensure quality through peer review u provide management visibility u encourage preparation

15 reviews8 Defect Amplification u Undetected defect “amplify” during subsequent phases u Figure

16 reviews8 Peer Review u the primary function is to use the skill of a group of people to: – 1) identify needed improvements – 2) certify correctness – 3) encourage uniformity – 4) enforce subjective rules

17 reviews8 Management u secondary functions include: » 1) communication » 2) milestone » 3) visibility to management

18 reviews8 Progress u additional function (and not the least) is to force preparation of materials and specification (both meanings) of ideas.

19 reviews8 Next Tuesday, 9/24/02 u Read about derived classes in C++ book u Stroustrup, ch 12