Quality Planning And Defect Estimation Presented by Basker George.

Slides:



Advertisements
Similar presentations
Effort Estimation and Scheduling
Advertisements

Process Database and Process Capability Baseline
Planning at CMM level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements Engineering.
More CMM Part Two : Details.
1 State of Michigan Achieving Software Process Improvement with Capability Maturity Model (CMM)
Metrics for Process and Projects
Project Closure Report Basker George. Project Closure When does a project end? Does it end when the software has been delivered to customer & acceptance-tested?
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
Stepan Potiyenko ISS Sr.SW Developer.
Software Measurement and Process Improvement
Software Project Planning CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 12, 2002.
1 Testing. 2 About Testing  The reason the program is in testing is that it probably doesn’t work!  We test to find bugs before our users and hope that.
Chapter 24 - Quality Management 1Chapter 24 Quality management.
 QUALITY ASSURANCE:  QA is defined as a procedure or set of procedures intended to ensure that a product or service under development (before work is.
Chapter 2- Software Process Lecture 4. Software Engineering We have specified the problem domain – industrial strength software – Besides delivering the.
Software Process and Product Metrics
Using A Defined and Measured Personal Software Process Watts S. Humphrey CS 5391 Article 8.
Project Execution & Termination Life Cycle Execution Presented by: Basker George.
Capability Maturity Model
PROJECT DATABASE(PDB) & PROCESS CAPABILITY BASELINE(PCB) Presented By Basker George.
S T A M © 2000, KPA Ltd. Software Trouble Assessment Matrix Software Trouble Assessment Matrix *This presentation is extracted from SOFTWARE PROCESS QUALITY:
Quality Planning & Defect Estimation
COURSE TITLE: 1 Software Quality Assurance. Course Aims Introduction to software quality assurance. Software testing terminology. Role and responsibility.
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
Chapter 15 Projecting Defects( 缺陷预测 ). 山东大学齐鲁软件学院 2 outline  Analyze and use your defect data to help improve both planning accuracy and product quality.
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
CLEANROOM SOFTWARE ENGINEERING.
N By: Md Rezaul Huda Reza n
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 1 (Ch. 1, 2, & 3)
Software Engineering Software Process and Project Metrics.
1 POP Quiz T/F Defect Removal Effectiveness and Defect Removal Models are not true Predictive Models Define DRE What is a Checklist? What is it for? What.
COMP3001 Technology Management & Professional Issues: Project Management CMMI and Improving Process Quality Lecture 10 Graham Collins, UCL
Lecture 1 Introduction to Software Engineering
Software Engineering - Spring 2003 (C) Vasudeva Varma, IIITHClass of 39 CS3600: Software Engineering: Standards in Process Modeling CMM and PSP.
Project Monitoring ( 监测 ) And Control Presented by Basker George.
Software Project Management Lecture # 7. What are we studying today? Chapter 24 - Project Scheduling  Effort distribution  Defining task set for the.
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 Project Management Lecture # 3. Outline Chapter 22- “Metrics for Process & Projects”  Measurement  Measures  Metrics  Software Metrics Process.
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
Process capability Baseline Presented by Basker George.
Computing and SE II Chapter 15: Software Process Management Er-Yu Ding Software Institute, NJU.
Effort Estimation ( 估计 ) And Scheduling ( 时序安排 ) Presented by Basker George.
Ch-1 Introduction The processes used for executing a software project have major effect on quality of s/w produced and productivity achieved in project…
Chapter 13: Software Quality Project Management Afnan Albahli.
Carnegie Mellon Software Engineering Institute © 2006 by Carnegie Mellon University Software Process Performance Measures James Over Software Engineering.
1 Software Quality Engineering. 2 Quality Management Models –Tools for helping to monitor and manage the quality of software when it is under development.
CS223: Software Engineering Lecture 4: Software Development Models.
CSE SW Metrics and Quality Engineering Copyright © , Dennis J. Frailey, All Rights Reserved CSE8314M13 8/20/2001Slide 1 SMU CSE 8314 /
Copyright , Dennis J. Frailey CSE Software Measurement and Quality Engineering CSE8314 M00 - Version 7.09 SMU CSE 8314 Software Measurement.
Peer Review Presented by : Basker George. Peer ( 同等的人 ) Review( 回顾 ) During the development of software, defects are inevitably ( 不可避免 ) injected. Defect.
Project Management Planning Nikolai Dushkov Sirma AI Ltd.
Chapter 05 Quality Planning SaigonTech – Engineering Division Software Project Management in Practice By Pankaj Jalote © 2003 by Addison Wesley.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
Capability Maturity Model. What is CMM? n CMM: Capability Maturity Model n Developed by the Software Engineering Institute of the Carnegie Mellon University.
Software Quality Control and Quality Assurance: Introduction
Testing More In CS430.
Levels of testing.
Software Quality Engineering
Product reliability Measuring
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Software Engineering Lecture 16.
Software Engineering I
Advancing Defect Containment to Quantitative Defect Management
Capability Maturity Model
Chapter # 1 Overview of Software Quality Assurance
Capability Maturity Model
Requirements Engineering
Introduction to Project Management
Software Design & Production Methodologies
Presentation transcript:

Quality Planning And Defect Estimation Presented by Basker George

Quality Planning Not only Cost & Schedule but QUALITY is also a major factor in determining the success of the project. There are many characteristic which define Quality. But the de facto industry standard definition of Quality is: “ The number of defects per unit size in the delivered software ”

Definition of Defect What is defect? Defect in software is something that causes the software to behave in a manner that is inconsistent with the requirement of the need of the customer.

Cont …. For High Quality software, the final product should have as few defects as possible. Since Software Development is a HUMAN activity, it is not possible to prevent injection of all defects. But it can be reduced by Quality control activity, which is Review & Testing.

Cont … In this chapter we shall study how quality control activities are Planned & Managed The Software Product Engineering KPA of CMM Level 3 includes some key practices that is used to test software for Quality. Software Quality Management KPA at Level 4 focus on Quantitatively Planning & Controlling the quality in a project.

Quality Management The task of quality management is To plan suitable quality control activities Properly execute & control these activities such that most defects are detected during “ In-Process ” & removed before delivery. In process activities include: Requirement Review, Design Review, Code review Unit Testing, Integration Testing, System Testing & Acceptance Testing

Procedural Approach to Quality Management. Defects are detected by performing Review or Testing Review are structured, human oriented process Testing is the process of executing software to identify defects In procedural approach for Quality management, procedures & guidelines for review & testing are established.

Cont … For example, the system testing procedure involves making a test plan that lists all test cases that should be executed during testing, getting the plan reviewed & then executing the plan. The above approach is called procedural approach to defect identification.

Defect Injection & Removal during Development process Requirement Analysis R R R Design CodingUTIT/IST AT R- Defect Removal Defect Injection

Quantitative Approach to Quality Management Quantitative Quality Management is the process of controlling the Quality of the software based on quantitative data. It makes use of software reliability model. These model indicate weather the reliability is acceptable or more testing is needed.

Cont … A good quality management approach should provide warning signs early in the project & not just towards the end. Early warning allow for timely intervention Therefore during project execution some parameter are measured & compared with the estimated values to determine whether the project is going along “ desired ” path.

Cont … Another quality concept is defect removal efficiency. DRE= Defects found by the QC activity Total defects in the product before the QC activity

Quantitative Quality Management through defect prediction This approach makes use of observed defects pattern in previous projects to forecast defect levels. RR HLD DD UT IT ST AT Operation Defects Time Defects during diff. Review phase

Quantitative Quality Management Planning This process involves setting the Quality goals for the project. The quality goal is the expected no of defects during acceptance test. The primary source for setting the quality goals are PDB & PCB

Cont … Estimate for AT defects(P) = AT defects(SP) X efforts estimate(P) Actual efforts(SP)

Estimating Defects for other stage: From the estimate of the total no of defects that will be introduced during the course of the project, the defect level for different testing stage are forecast by using percentage distribution of defects as given in PCB

Cont … Defect distribution at Infosys PCB Process Stage%tage of total defects SRS +HLD +Detail design Reviews 15% - 20% Code review+Unit testing50%-70% Integration testing + System testing 20%-28% Acceptance Testing5%-10%