Error Tracking Defect removal efficiency DRE = E / (E+D)

Slides:



Advertisements
Similar presentations
PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.
Advertisements

These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 6/e (McGraw-Hill 2005). Slides copyright 2005 by Roger Pressman.1.
Overview Lesson 10,11 - Software Quality Assurance
Soft. Eng. II, Spr. 02Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter 6 Title : The Software Quality Reading: I. Sommerville, Chap: 24.
Chapter 16 Software Quality Assurance
Managing Software Quality
Software Quality Assurance Activities
Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.
Software Quality Applied throughout SW Engineering Process Encompasses ▫ Analysis, design, coding, testing, tools ▫ Formal tech reviews ▫ Multi-tiered.
SE513 Software Quality Control Lecture01: Introduction to Software Quality Assurance Galin, SQA from Theory to Education Limited.
S Q A.
Software Measurement & Metrics
Software Project Management Lecture # 10. Outline Quality Management (chapter 26)  What is quality?  Meaning of Quality in Various Context  Some quality.
This chapter is extracted from Sommerville’s slides. Text book chapter
Software Project Management Lecture # 3. Outline Chapter 22- “Metrics for Process & Projects”  Measurement  Measures  Metrics  Software Metrics Process.
Lecture 4 Software Metrics
CHAPTER 9 INSPECTIONS AS AN UP-FRONT QUALITY TECHNIQUE
Quality Management Managing the quality of the software process and products.
Computing and SE II Chapter 15: Software Process Management Er-Yu Ding Software Institute, NJU.
SOFTWARE PROCESS AND PROJECT METRICS. Topic Covered  Metrics in the process and project domains  Process, project and measurement  Process Metrics.
Empirical Estimation Models Based upon historic data Basic Structure E = A + B * (ev) C where A, B, c are empirical constants ‘ev’ is the effort in terms.
Hussein Alhashimi. “If you can’t measure it, you can’t manage it” Tom DeMarco,
1 Lecture 12: Chapter 16 Software Quality Assurance Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman Slides.
Software Project Management Lecture # 12. Outline Quality Management ( chapter 26 - Pressman )  SQA  Who does it?  SQA Activities  Software reviews.
TOTAL QUALITY MANAGEMENT
Software Reviews Software reviews are the filter for the software engineering process Applied at various different points and serve to uncover errors that.
Software Quality Control and Quality Assurance: Introduction
Metrics for Specification Quality
CIS 375 Bruce R. Maxim UM-Dearborn
Software Quality Assurance
Software Verification and Validation
RET Rules One of the following rules applies when counting RETs:
Quality Management chapter 27.
Software Engineering Lecture #41
Source & Courtesy: Doc. S. Dapkūnas
Software Engineering B.Tech Ii csE Sem-II
McCall’s Quality Factors
Chapter 21 Software Quality Assurance
Software Quality Engineering CS- 449
Why Do We Measure? assess the status of an ongoing project
Software Engineering Lecture #2
Chapter 21 Software Quality Assurance
Software Engineering Lecture #39
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
A simple database Project Size (FP) Effort (Pm) Cost Rs. (000) Pp. doc
What is software quality?
Software Engineering Lecture #45
Chapter 13 Quality Management
Software Engineering Lecture #25
Software Engineering Lecture # 17
Software Engineering Lecture #26
Program Restructuring
Chapter 25 Process and Project Metrics
Baseline – IEEE definition
KEY PROCESS AREAS (KPAs)
Quality Measurable characteristic Cyclomatic complexity Cohesion
The Project Reel’s five step approach for successful projects
Software Engineering Lecture #35
Software metrics.
What is software quality?
Software Engineering Lecture #40
Why Do We Measure? assess the status of an ongoing project
Metrics for process and Projects
Software Quality Assurance 2015
Chapter 32 Process and Project Metrics
Legacy system components
Software Engineering Lecture #29
Metrics for Process and Projects
Software Engineering II
Software Engineering Lecture #28
Presentation transcript:

Error Tracking Defect removal efficiency DRE = E / (E+D) E – errors found before shipment D – errors found during operation Provides strong indication of the effectiveness of the quality assurance activities Track errors in work products (requirement specifications, design documents, source code etc) to assess the status of a project Collect error related metrics over many projects

Recap

Software Engineering II Lecture 26 Fakhar Lodhi

Using Error Tracking to assess progress Let us assume that we have collected errors and defect data over the last 24 months Errors per requirement specification page – Ereq Error per component – design level – Edesign Errors per component – code level – Ecode DRE – requirement analysis DRE – architectural design DRE – coding

Using Error Tracking to assess progress Record the number of errors found during each SE step Calculate current values for Ereq, Edesign, and Ecode Compare to averages of past projects If the current results vary more than 20% from average, there may be cause for concern and there is certainly cause for investigation

Example Ereq for the current project = 2.1 Organizational average = 3.6

Can also be used to better target review and/or testing resources 120 components 32 exhibit Edesign > 1.2 average Adjust code review resources accordingly

Software Quality Software quality is defined as: Conformance to explicitly stated functional and non-functional requirements, explicitly documented development standards, and implicit characteristics that are expected of all professionally developed software.

Software Quality 3 important points Software requirements are the foundation from which quality is measured. Lack of conformance is lack of quality Specified standards define a set of development criteria that guide the manner in which software is engineered. If the criteria are not followed, lack of quality will almost surely result. A set of implicit requirements often goes unmentioned (ease of use, good maintainability etc.)

Quality Assurance Goal is to provide the management with the necessary data to be informed about product quality Consists of auditing and reporting functions of management If data provided through QA identifies problems, the management deploys the necessary resources to fix it