TEST METRICS AND MEASUREMENTS

Similar documents
Project Scorecard Template

An Introduction to. Metrics. used during. Software Development

TEST METRICS AND KPI S

Testing Metrics. Introduction

Quantitative Quality Management through Defect Prediction and Statistical Process Control Τ

Fundamentals of Measurements

1. Introduction. Annex 7 Software Project Audit Process

A Framework for Project Metrics

Software Project Audit Process

B2B Software Technologies Ltd. Service Level Agreement (SLA)

5.1 Project Control Overview

BODY OF KNOWLEDGE CERTIFIED SIX SIGMA YELLOW BELT

Orthogonal Defect Classification in Agile Development

Use of Metrics in High Maturity Organizations

QUANTIFIED THE IMPACT OF AGILE. Double your productivity. Improve Quality by 250% Balance your team performance. Cut Time to Market in half

CSSE 372 Software Project Management: Managing Software Projects with Measures

Personal Software Process (PSP)

Chap 1. Software Quality Management

Software Metrics. Er. Monika Verma*, Er. Amardeep Singh **, Er. Pooja Rani***, Er. Sanjeev Rao****

Project Cost Management

Applied Software Project Management

Project Control System Manual. Jefferson Science Associates, LLC. 600 Progress Status. Project Control System Manual Revision

Case Study I: A Database Service

Commonwealth of Massachusetts CommonWay Schedule Management Guidelines. Common Values - Common Goals Common Way. Schedule Management.

Certified Six Sigma Yellow Belt

Relationships Among Software Metrics in Benchmarking

Software Project Management Matrics. Complied by Heng Sovannarith

AGILE Burndown Chart deviation - Predictive Analysis to Improve Iteration Planning

Lean Six Sigma Analyze Phase Introduction. TECH QUALITY and PRODUCTIVITY in INDUSTRY and TECHNOLOGY

White Paper from Global Process Innovation. Fourteen Metrics for a BPM Program

Understand the role that hypothesis testing plays in an improvement project. Know how to perform a two sample hypothesis test.

The Thinking Approach LEAN CONCEPTS , IL Holdings, LLC All rights reserved 1

Process Improvement Program Project Process

SOFTWARE REQUIREMENTS

Description of Services for A Quality Assurance Engineer for SQA Assignment for eservices Development Projects ICTA/CON/IC/P5/411B

Integrated methodology for testing and quality management.

Essential Metrics for Agile Project Management

Project Quality Planning

Estimating Cost at Completion - Judgment & EV Information

ESTABLISHING A MEASUREMENT PROGRAM

Characteristics of Binomial Distributions

FUNCTION POINT ANALYSIS: Sizing The Software Deliverable. BEYOND FUNCTION POINTS So you ve got the count, Now what?

PLANNING FOR YOUR PROJECT

MCQ: Unit -2: Operation processes

Comprehensive Job Analysis. With MPG s Performance Navigator

Fuzzy Logic Based Revised Defect Rating for Software Lifecycle Performance. Prediction Using GMR

3-Step Competency Prioritization Sequence

Learning Objectives. Understand how to select the correct control chart for an application. Know how to fill out and maintain a control chart.

TenStep Project Management Process Summary

SCHEDULE AND BUDGETING

Reduce QA Cost by Improving Productivity & Test Optimization

PERFORMANCE AND QUALITY IN PROJECTS Project Management and Leadership 2016D, PhD, PMP

Body of Knowledge for Six Sigma Green Belt

The Next Generation of Inventory Optimization has Arrived

Input, Output and Tools of all Processes

Business Process Optimization w/ Innovative Results

An Example of Using Key Performance Indicators for Software Development Process Efficiency Evaluation

ITRM Guideline CPM Date: January 23, 2006 SECTION 4 - PROJECT EXECUTION AND CONTROL PHASE

Schedule analytics tool

Measurement Information Model

Agile Metrics - What You Need to, Want to, and Can Measure. June 9, 2014

Useful Automated Software Testing Metrics

Reaching CMM Levels 2 and 3 with the Rational Unified Process

Sizing Application Maintenance and Support activities

Measurement and Metrics Fundamentals. SE 350 Software Process & Product Quality

Introduction to CONTINUOUS QUALITY IMPROVEMENT TECHNIQUES. for Healthcare Process Improvement

CSTE Mock Test - Part I - Questions Along with Answers

PMO Metrics Recommendations

Schedule Analysis Using Earned Value Concepts ABSTRACT

SEI Level 2, 3, 4, & 5 1 Work Breakdown Structure (WBS)

IMPORTANCE OF SOFTWARE TESTING IN SOFTWARE DEVELOPMENT LIFE CYCLE

Lean Six Sigma Black Belt Body of Knowledge

The Personal Software Process (PSP) Tutorial

Level 1 Articulated Plan: The plan has established the mission, vision, goals, actions, and key

Introduction to Cost Accounting

225 Bush St, Ste West, San Francisco, CA Follow us on

Measuring Return on Investment of Model-Based Design

A Comparison of Software Cost, Duration, and Quality for Waterfall vs. Iterative and Incremental Development: A Systematic Review

Statistics I for QBIC. Contents and Objectives. Chapters 1 7. Revised: August 2013

1.3 Developing Performance Metrics University of California Approach

Making Improvement Work in Pharmaceutical Manufacturing Some Case Studies. Ronald D. Snee

Productivity Measurement and Analysis

Transcription:

TEST METRICS AND MEASUREMENTS OVERVIEW: Derive information from raw data to help in decision making Metrics derived from measurements using formulae/calculations Metrics program to decide what measurements are important and collect data Metrics and analysis helps in preventing the defects Metrics used in resource management To make right analysis on data measured To metrics related to testing and product To plan the metric for taking necessary action To describe metrics for combining the data points The metrics can be divided as 4 major units, Project metric Progress metric Productivity metric Release metric

1. PROJECT METRICS Starts with requirement gathering and end with product release Project scope get translated into size estimates Project metric can be dived as, a) Effort variance(planned VS Actual): Good idea to plot effort numbers phase-wise Calculating effort variance for each phases given Indicates effort stability b) Schedule variance(planned VS Actual): Deviation of actual schedule from estimated schedule Calculated at the end of every milestone Indicates schedule stability c) Effort distribution across phases: The various phases are captured and analysed Effort percentage for testing depends on, Type of release Amount of change to existing code base Functionality To specifies the quantum work To differentiate the baselined and revised effort in effort variance To project the causes and outcomes To estimating the total effort of testing To produce good quality product

PROBLEM: If the actual effort for effort variance is 110 and estimated effort is 100 means then, the effort variance can be calculated as, = [(110-100/100) *100 = 10% 2. PROGRESS METRICS Reflects the defects of the product Testing progress is estimated by test execution status and outcome Progress metrics can be categorized as, a) Test defect metrics: Helps to understand how defects found and assign defect priority To find defects early in test cycle using defect find rate Development to fix defects as soon as they arrive Provide a combined perspective of defects b) Development defect metrics: Helps to improving development activities Map defects to different components of product Unit of defects can be calculate using KLOC defects have been waiting to fix for a long time age analysis To reduce the defects rate To estimate the priority for defects To identifies the problem in software development model To compute the complexity and time in testing defect

PROBLEMS: If the no. of defects identified is 30 means and the size of requirement is 5,then defect density can be calculated as, DEFECT DESITY=No. of defects identified/size. = (30/5) = 6 3. PRODUCTIVITY METRICS Combines several measurements and parameters with effort on product Find out the capability of terms and purposes Describe the reason for variation in result a) Defects per 100 hours of testing: Normalize the defects Conclude that there is no end for testing b) Test case executed per 100 hours of testing: Track the productivity Judge the product quality c) Test case developed per 100 hours of testing: Modify the test cases Address new functionality and features for testing d) Defect per 100 test case: Measure the uncover defects Improve the quality e) Defect per 100 failed test case: Shows the product readiness Improve the productivity f) Test phase effectiveness: Defect found in early phases Used for planning activities

g) Close defect distribution: Judge whether all defects are fixed Analyze the closeness of defect To find some of the defects To discover the release date To estimate the quality of product PROBLEMS: If total test case executed for a period is 65and toatal hours spent in test execution is 100,then to find test cases executed per 100 hrs can be, Test cases executed per 100hrs of testing = (total test cases executed for a period/total hrs spent in test execution)*100 = (65/100)*100= 65% 4. RELEASE METRICS Determine whether the product is ready for release Decision to release product need to consider several perspective Building the credibility of metric program To increase effectiveness of metric To analyze the metric result To make decisions