Tom Gilchrist The Tools and Techniques of SQA SASQAG, February 17, 2000.

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

QuEST Forum 2006 Requirements Handbook 4.0 Overview.
Tom Gilchrist, CQA, CSQE Quality Assurance in ISD and Maintenance Projects How do you do QA when the time it takes is longer that the.
Software Quality Assurance Plan
Damian Gordon.  Static Testing is the testing of a component or system at a specification or implementation level without execution of the software.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #7 Software Engineering.
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”
Stepan Potiyenko ISS Sr.SW Developer.
Quality Management System
Overview Lesson 10,11 - Software Quality Assurance
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.
SOFTWARE PROJECT MANAGEMENT Project Quality Management Dr. Ahmet TÜMAY, PMP.
Software Quality Assurance For Software Engineering && Architecture and Design.
Process Engineering, Documentation, and Evaluation
Software Process Reviews/Audits
ISO 9000 Certification ISO 9001 and ISO
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.
SystematicSystematic process that translates quality policy into measurable objectives and requirements, and lays down a sequence of steps for realizing.
OHT 4.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
S/W Project Management
Introduction to Software Quality Assurance (SQA)
Software Inspections and Walkthroughs By. Adnan khan.
Galin, SQA from theory to implementation © Pearson Education Limited 2004 Review objectives Formal design reviews (FDRs) Participants Preparations The.
S oftware Q uality A ssurance Part One Reviews and Inspections.
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.
Software Quality Assurance
Lecture #9 Project Quality Management Quality Processes- Quality Assurance and Quality Control Ghazala Amin.
Software Quality Assurance Lecture #2 By: Faraz Ahmed.
Thomas L. Gilchrist Testing Basics Set 6: Use Cases, Audits, and Meetings By Thomas L. Gilchrist, CSQE, CSQA 2009.
Software Quality Assurance SE Software Quality Assurance What is “quality”?
CHAPTER 9 INSPECTIONS AS AN UP-FRONT QUALITY TECHNIQUE
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Chapter 19 Verification and Validation.
THE SQA CHARTER Find defects so they can be REMOVED Anticipate defects so they can be PREVENTED.  Software Quality Assurance 
Project quality management. Introduction Project quality management includes the process required to ensure that the project satisfies the needs for which.
Chapter 1: Fundamental of Testing Systems Testing & Evaluation (MNN1063)
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
Thomas L. Gilchrist Testing Basics Set 5: CM & Peer Reviews By Thomas L. Gilchrist CSQE,CSQA 2009.
© Michael Crosby and Charles Sacker, 2001 Systematic Software Reviews Software reviews are a “quality improvement process for written material”.
Advances In Software Inspection
Thomas L. Gilchrist Testing Basics Slide Set 2: Software Processes By Tom Gilchrist 2009-v2.
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
Mahindra Satyam Confidential Quality Management System Software Defect Prevention.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
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.
6/22/2016 Tom Gilchrist Cost and Impact of Errors/Defects Errors are introduced in all activities. The longer errors go undetected and.
SQA project process standards IEEE software engineering standards
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Software Project Configuration Management
Software Quality Control and Quality Assurance: Introduction
CIS 375 Bruce R. Maxim UM-Dearborn
How To Apply Quality Management
Software Configuration Management (SCM)
Software Verification and Validation
SQA project process standards IEEE software engineering standards
Systems Analysis and Design
Engineering Processes
Verification and Validation Unit Testing
QA Reviews Lecture # 6.
Engineering Processes
Software Reviews.
Testing, Inspection, Walkthrough
Presentation transcript:

Tom Gilchrist The Tools and Techniques of SQA SASQAG, February 17, 2000

SASQAG 2/17/00 Disclaimers The views and opinions expressed in this presentation are not necessarily those of my employer. Your results may vary. You are free to use any slide in your work, but if you do, please include my name and .

SASQAG 2/17/00 Goals and Objectives Some Terms Peer Reviews Kickoff Meetings Audits Checklist and Worklists Sharpen Your SQA Skills

SASQAG 2/17/00 Software Quality Assurance Check software products and processes to verify that they comply with the applicable procedures and standards. (Process Checks/Audits) Review and measure the quality of software products and processes throughout development. (Peer Reviews) Provide software project management (and other appropriate parties) with the results of reviews and process checks. Work with the software project during early stages to establish plans, standards, and procedures to keep errors from occurring in the first place.

SASQAG 2/17/00 Validation and Verification Validation -Are we building the right product? Verification -Are we building the product right? Static Verification (of software) -Verification of a program by examination and analysis of its program elements.

SASQAG 2/17/00 Quality In Perspective

SASQAG 2/17/00 Customer vs. End User End User: -The person who uses the software product in the value stream Customer: -Anyone who is affected by the end product or intermediate software engineering deliverables being produced (reviewed).

SASQAG 2/17/00 Healthy Customer/Supplier Relationship Implies product use by customer! Implies choice Communications centers on expectations. -How we identify expectations -How we document and communicate them -How we measure/improve them

SASQAG 2/17/00 Value vs Quality Customers are concerned with value not just quality.

SASQAG 2/17/00 Value vs Quality Customers are concerned with value not just quality. "Value is not overpaying for quality." Value is..."the right combination of product quality, fair price, and good service." * From Business Week, Nov 11, 1991

SASQAG 2/17/00 Low Quality in Software Unneeded ComplexityUnneeded Complexity ReworkRework -Wrong -Unclear -Missing -Extra

SASQAG 2/17/00 The Project Requirements Finished Product SpecsDesignCodeTest Time Project Plan

SASQAG 2/17/00 Where is rework introduced? Requirements Finished Product SpecsDesignCodeTest Time Project Plan

SASQAG 2/17/00 Where is rework found? Requirements Finished Product SpecsDesignCodeTest Time Project Plan

SASQAG 2/17/00 Where is rework fixed? Requirements Finished Product SpecsDesignCodeTest Time Project Plan

SASQAG 2/17/00 The Quality Lever Requirements Design Coding Development Testing Acceptance Testing Improve Product Production X 30-70X 15-40X 10X 3-6X 1X Data from Boehm: Software Engineering Economics, 1981

SASQAG 2/17/00 The Quality Lever Requirements Design Coding Development Testing Acceptance Testing Improve Product Production X 30-70X 15-40X 10X 3-6X 1X Data from Boehm: Software Engineering Economics, 1981 High Visibility/Reward

SASQAG 2/17/00 The Quality Lever Requirements Design Coding Development Testing Acceptance Testing Improve Product Production X 30-70X 15-40X 10X 3-6X 1X Data from Boehm: Software Engineering Economics, 1981 High Visibility/Reward Low Visibility/Reward

SASQAG 2/17/00 Error/Defect Classification Number of Errors MinorMajor"Show Stoppers" Error Severity

SASQAG 2/17/00 Error/Defect Classification Number of Errors MinorMajor"Show Stoppers" Find and remove as many Major and Show Stopper errors as early as possible. Error Severity

SASQAG 2/17/00 Terminology Major ErrorMajor Error -Something that is wrong -High degree of probability that it will cause rework -Rework later will cost much more if left allowed to migrate downstream. Minor ErrorMinor Error An issue or defect that is not major. The costs of fixing later is not significantly higher than fixing now.

SASQAG 2/17/00 Quality Metric…Rework Number of Major Errors / Unit of WorkNumber of Major Errors / Unit of Work -ME/Page -ME/Drawing Zone -ME/KLOC -ME/?

SASQAG 2/17/00 Peer Reviews

SASQAG 2/17/00 Initial Level Informal Checking Do Work Down- stream Customers Input Source Materials Errors Found Process Product Entry Criteria Loosely Defined Exit Criteria For Quality Not Defined Work Process ENTRYENTRY EXITEXIT

SASQAG 2/17/00 Initial Level Informal Checking Do Work Down- stream Customers Re-Work Input Source Materials Errors Found Process Product Entry Criteria Loosely Defined Exit Criteria For Quality Not Defined Work Process ENTRYENTRY EXITEXIT

SASQAG 2/17/00 Measure and Improve Product Quality Do Work Down- stream Customers Re- Work Errors Found Process Product Crossfunctional Checklists SW Inspection Input Source Materials Entry Criteria Loosely Defined Exit Criteria For Quality Defined ENTRYENTRY EXITEXIT Work Process

SASQAG 2/17/00 Improve Product Quality and Reduce Variation Do Work Down- stream Customers Re- Work Errors Found Process Product Crossfunctional Checklists Input Source Materials Entry Criteria Defined Exit Criteria For Quality Defined ENTRYENTRY EXITEXIT Work Process SW Inspection

SASQAG 2/17/00 To Improve Product AND Process (Entry Criteria Met) Do Work Down- stream Customers Re- Work Input Source Materials Errors Found Process Product Crossfunctional Checklists Exit Criteria Met Statistical Data Analysis and Causal Analysis P D C A Deming Cycle (Defect Prevention Process) Repeatable Work Process SW Inspection

SASQAG 2/17/00 SW Inspection Process Flow Planning Collect and Store Data Another Chunk? Verify and Approve AuthorsModeratorInspection Team Members OK Re-Work YES NO Other Inspection and CI Processes Produce Product Rework Product Release Individual Preparation Overview Meeting Error Logging Meeting 7

SASQAG 2/17/00 SDLC ENTRYENTRY EXITEXIT Output... ENTRYENTRY EXITEXIT Output Input Standards, templates, rules and checklists Standards, templates, rules and checklists Program Element Creation Program Element Creation Time

SASQAG 2/17/00 SW Inspections ENTRYENTRY EXITEXIT Output... ENTRYENTRY EXITEXIT Output Input Standards, templates, rules and checklists Standards, templates, rules and checklists Program Element Creation Program Element Creation SW Inspection

SASQAG 2/17/00 Kickoff Meeting ENTRYENTRY EXITEXIT Output... ENTRYENTRY EXITEXIT Output Input Standards, templates, rules and checklists Standards, templates, rules and checklists Program Element Creation Program Element Creation Task Kickoff Meeting Task Kickoff Meeting Task Kickoff Meeting Task Kickoff Meeting SW Inspection

SASQAG 2/17/00 Task Kickoff Meeting Identify people/organizations affected by errors in the activity Identify and document potential major errors (build/modify checklists) Confirm task/process entry conditions Identify resources Forum for learning Reduce the amount of time needed by the author(s) to produce a deliverable by giving technical and resource information to do the job.

SASQAG 2/17/00 Kickoff Meeting ENTRYENTRY EXITEXIT Output... ENTRYENTRY EXITEXIT Output Input Standards, templates, rules and checklists Standards, templates, rules and checklists Task Kickoff Meeting Task Kickoff Meeting Task Kickoff Meeting Task Kickoff Meeting Program Element Creation Program Element Creation SW Inspection

SASQAG 2/17/00 Walkthrough ENTRYENTRY EXITEXIT Output... ENTRYENTRY EXITEXIT Output Input Standards, templates, rules and checklists Standards, templates, rules and checklists Walkthrough Program Element Creation Program Element Creation Walkthrough 21 Task Kickoff Meeting Task Kickoff Meeting Task Kickoff Meeting Task Kickoff Meeting SW Inspection

SASQAG 2/17/00 Walkthrough Process Reduce the amount of time needed for re-work by reviewing work completed to date and address questions and concerns. Led by author Discussion of deliverable style and format Examine technical alternatives Evaluate checklists, standards, and rules. Capture undocumented issues Forum for learning

SASQAG 2/17/00 Peer Review Methods Walkthrough MethodsTypical GoalsTypical Attributes Minimal overhead Developer training Quick turnaround Little/no preparation Informal process Meetings No measurement Led by the author SW Inspection Detect and report all defects efficiently and effectively. Usage of deliverable Formal process Known Coverage Rate Moderator Checklists Customer Reviewers Measurement Desk Check Minimal overhead Quick turnaround Little/no preparation Informal process No measurement No Meetings Done by the author

SASQAG 2/17/00 SQA Interventions Output ENTRYENTRY EXITEXIT Input Program Element Creation StartDuringEnd Kickoff Meeting

SASQAG 2/17/00 SQA Interventions Output ENTRYENTRY EXITEXIT Input Program Element Creation StartDuringEnd Kickoff Meeting Walkthrough Desk Check

SASQAG 2/17/00 SQA Interventions Output ENTRYENTRY EXITEXIT Input Program Element Creation StartDuringEnd Kickoff Meeting Walkthrough Desk Check SW Inspection

SASQAG 2/17/00 SQA Interventions Output ENTRYENTRY EXITEXIT Input Program Element Creation StartDuringEnd Kickoff Meeting Walkthrough Desk Check SW Inspection Formal Walkthrough Formal Desk Check

SASQAG 2/17/00 Peer Reviews ENTRYENTRY EXITEXIT Output... ENTRYENTRY EXITEXIT Output Input Standards, templates, rules and checklists Standards, templates, rules and checklists Task Kickoff Meeting Task Kickoff Meeting Task Kickoff Meeting Task Kickoff Meeting Walkthrough Desk Check Walkthrough Desk Check Program Element Creation Program Element Creation SW Inspection Formal Walkthrough Formal Desk Check SW Inspection Formal Walkthrough Formal Desk Check SW Inspection Formal Walkthrough Formal Desk Check SW Inspection Formal Walkthrough Formal Desk Check Walkthrough Desk Check Walkthrough Desk Check

SASQAG 2/17/00 Audits

SASQAG 2/17/00 Audit Process Software Quality Assurance is to provide management with appropriate visibility into the process being used by the software developers and of the products being built. Determine: Conformance to policies, procedures, and standards Adequacy of policies, procedures, and standards Effectiveness and efficiency of policies, procedures, and standards Assess personnel familiarity to requirements and documentation Assure availability, use and adherence to software standards

SASQAG 2/17/00 Audit Process Un- satisfactory Report? OK NO YES Produce Product Corrective Actions Audit Kickoff Meeting Develop Audit Checklist Conduct Audit DevelopersAuditor & Project Manager Write-up Report & Findings Auditor Identify Requirements Follow-up Audit Re-Work Close Audit & File END Start Review with Manager

SASQAG 2/17/00 Checklists & Worklists

SASQAG 2/17/00 Checklists Used to identify Major Errors Usually in the form of questions When used…. -By the authors to keep from inserting rework into the work stream -By reviewers to find and report as many Major Errors as possible -By future authors and reviewers

SASQAG 2/17/00 Generic Document Checklist PurposeHas the document satisfied the stated purpose? RedundantIs the same information presented elsewhere within the document? AcronymsHave all acronyms been defined prior to use? AccuracyIs the information wrong? ExtraneousIs there information outside the stated scope of the document? CompletenessIs necessary information missing? StandardDoes the document follow the xyz documentation standard?

SASQAG 2/17/00 Generic Document Worklist Before creating the deliverable... -Hold Kickoff Meeting Invite the right participants Plan for a successful document Build/Refine Checklists While working on the deliverable… -Use the checklists -Use Walkthroughs and Desk Checks as needed to reduce rework (major errors). When finished with the deliverable… -As per SQA plan, perform the appropriate Peer review -Send peer review data summary to SQA focal

SASQAG 2/17/00 For More Information

SASQAG 2/17/00 Resources... SASQAG WEB Site (sasqag.org) -Past Meetings -Links UW Certificate Course Commercial Courses SASQAG Training Courses

SASQAG 2/17/00 Goals and Objectives Some Terms Peer Reviews Kickoff Meetings Audits Checklist and Worklists Sharpen Your SQA Skills

SASQAG 2/17/00