Software Economics Phase Yield

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

Testing and Quality Assurance
Test Execution and Defect management. 2 Module Objectives Introduction to Test Execution Checklist of Test Execution Defect management Defect Classification.
The Personal Software Process (PSP) Lecture #1 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
Software Testing By Marcin Starzomski :P. What is Testing ? Testing is a process used to help identify the correctness, completeness and quality of developed.
Chapter 4 Quality Assurance in Context
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #7 Software Engineering.
Empirical Results Copyright © Software Carpentry 2011 This work is licensed under the Creative Commons Attribution License See
SE382 Software Engineering Lecture 21b
Reliability and Software metrics Done by: Tayeb El Alaoui Software Engineering II Course.
The Software Process Strategy The Software Process Strategy Part III.
Lecturer: Dr. AJ Bieszczad Chapter Predictive accuracy Predictions are biased when they are consistently different from the actual value. Predictions.
CS 325: Software Engineering March 26, 2015 Software Quality Assurance Software Metrics Defect Injection Software Quality Lifecycle Measuring Progress.
EXAMPLES OF METRICS PROGRAMS
1 Software Quality Metrics Ch 4 in Kan Steve Chenoweth, RHIT What do you measure?
Planning and Tracking Software Quality Yordan Dimitrov Telerik Corporation
Fundamental of Software Project Management Team Assignment 1 – K15T2 – Team 07.
Verification and Validation
Software Testing Verification and validation planning Software inspections Software Inspection vs. Testing Automated static analysis Cleanroom software.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Software Quality Chapter Software Quality  How can you tell if software has high quality?  How can we measure the quality of software?  How.
Ch.4: QA in Context  QA and the overall development context Defect handling/resolution How alternative QA activities fit in process Alternative perspectives:
Planning and Tracking Software Quality.  What Is Software Quality?  Causes of Software Defects  What is Quality Assurance?  Improving the Software.
Applying the Inspection Process. What Software Artifacts Are Candidates for Inspection? Software Requirements Software Designs Code Test Plans.
Validation Metrics. Metrics are Needed to Answer the Following Questions How much time is required to find bugs, fix them, and verify that they are fixed?
INFO 637Lecture #41 Software Engineering Process II Development Plan INFO 637 Glenn Booker.
Dr. Tom WayCSC Code Reviews & Inspections CSC 4700 Software Engineering.
Software testing basic. Main contents  Why is testing necessary?  What is testing?  Test Design techniques  Test level  Test type  How to write.
CS 350, slide set 6 M. Overstreet Old Dominion University Spring 2005.
Software Test Metrics When you can measure what you are speaking about and express it in numbers, you know something about it; but when you cannot measure,
Disciplined Software Engineering Lecture #7 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
1 Pop Quiz What is an Orthogonal Defect? Which is more precise: predictive models or management models? Why? Essay: Why are metrics and models an important.
Software Engineering Modern Approaches Eric Braude and Michael Bernstein 1.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
From Quality Control to Quality Assurance…and Beyond Alan Page Microsoft.
Jump to first page (C) 1998, Arun Lakhotia 1 Quality Assurance: Reviews and Walkthroughs Arun Lakhotia University of Southwestern Louisiana Po Box
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Software Verification, Validation and Testing.
INFO 636 Software Engineering Process I Prof. Glenn Booker Week 9 – Quality Management 1INFO636 Week 9.
PSP Quality Strategy [SE-280 Dr. Mark L. Hornick 1.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 7 1 Design and Code Reviews - Overview What are design and code.
SE-280 Dr. Mark L. Hornick 1 Design and Code Reviews Review Checklists.
Chapter 12: Software Inspection Omar Meqdadi SE 3860 Lecture 12 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Defect resolution  Defect logging  Defect tracking  Consistent defect interpretation and tracking  Timely defect reporting.
Implementation Phase CS4311 – Spring 2008 References: Shach, Object Oriented and Classical Software Engineering E. Braude, Software Engineering, an Object-Oriented.
Can we calculate the profit of testing? Jurian van de Laar Philips TASS 10th Dutch Testing Day October 8th, Leiden Version 2.0.
Ensure that the right functions are performed Ensure that the these functions are performed right and are reliable.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Defect Classes and the defect repository
1 Software Engineering. 2 Software Engineering is the study of activities related to the development of a software product.
1 Software Quality Engineering. 2 Quality Management Models –Tools for helping to monitor and manage the quality of software when it is under development.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.1.
CAT Executive Review Team 3: Lions. Cycle 2 Key Lessons: Quality.
6/22/2016 Tom Gilchrist Cost and Impact of Errors/Defects Errors are introduced in all activities. The longer errors go undetected and.
Planning 2: Estimation Mechanics Emerson Murphy-Hill Creative Commons Attribution 4.0 License. Material Produced by NCSU Software Engineering Faculty.
Software Reviews Software reviews are the filter for the software engineering process Applied at various different points and serve to uncover errors that.
CIS 375 Bruce R. Maxim UM-Dearborn
Maintenance Issues in Software Engineering
Testing More In CS430.
Personal Software Process Team Software Process
Quality Quality is “a characteristic or attribute of something.”
Software Quality Engineering
Software Quality Engineering
SQA for Individuals based on
KEY PROCESS AREAS (KPAs)
Quality Measurable characteristic Cyclomatic complexity Cohesion
Estimating the number of components with defects post-release that showed no defects in testing C. Stringfellow A. Andrews C. Wohlin H. Peterson Jeremy.
Software Engineering Lecture #40
Integrating quality activities in
Presentation transcript:

Software Economics Phase Yield Emerson Murphy-Hill Creative Commons Attribution 4.0 License. Material Created by NCSU Software Engineering Faculty.

Fault removal yield Phase yield = removed in phase removed in phase + escapes from phase Phases: design review, code, code review, compile, test Phase escapes: defects injected before or during the phase, not found before or during the phase, and found later The “escapes from phase” measure cannot be precisely calculated until after the program has been used in the field (need post-development defects) – need 20/20 hindsight even then some failures can surface for years

Fault Removal Yield Example Phase Injected Removed Cumulative Injected Cumulative Removed Requirements 1 Design 5 6 Design Review 3 Code 15 21 4 Code Review 8 12 Static Analysis 18 Test Field Total 26 Note: the faults show up in the “injected” column if they were analyzed and removed prior to release. Design Review Yield = 3/(0+6) = 50% Code Review Yield= 8/(8+9) = 47% Process Yield = 21/26 = 81%

Quality Assurance Filters - Examples 100 errors Inspection (50%) 50 errors Testing (50%) 25 errors To customer Solo programming with inspection Testing To customer Testing (50%) Solo programming without inspection or pair programming Pair Programming Paired team without inspection See course pack page 23