University of Southern California Center for Systems and Software Engineering Metrics Organizational Guidelines [1] ©USC-CSSE1 [1] Robert Grady, Practical.

Slides:



Advertisements
Similar presentations
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Advertisements

1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Metrics for Process and Projects
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Low Defect Potentials (< 1 per function point)
SENG 530: Software Verification and Validation
1 SIM5102 Software Evaluation Framework for software measurement.
Stepan Potiyenko ISS Sr.SW Developer.
Software Quality Engineering Roadmap
Software Quality Metrics
University of Southern California Center for Software Engineering CSE USC 12/6/01©USC-CSE CeBASE: Opportunities to Collaborate Barry Boehm, USC-CSE Annual.
A GOAL-BASED FRAMEWORK FOR SOFTWARE MEASUREMENT
1 Maintenance Metrics and Measures (M 12) Steve Chenoweth CSSE 375, Rose-Hulman Based on Don Bagert’s 2006 Lecture.
University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 Ray Madachy, Barry Boehm USC Center for Systems and Software Engineering.
SE 450 Software Processes & Product Metrics 1 Defect Removal.
CMPUT 401- Software EngineerintfSoftware Measurement - 1c Paul SorensonMETRICS WHY DO WE NEED METRICS? HOW DO WE COLLECT (GET, GATHER) METRICS? to measure.
Capability Maturity Model – Integrated (CMMI)
SOFTWARE PROJECT MANAGEMENT Project Quality Management Dr. Ahmet TÜMAY, PMP.
Software Process and Product Metrics
12 Steps to Useful Software Metrics
Software Quality: An Overview From the Perspective of Total Quality Management By Kan, Basili and Shapiro.
What is Business Analysis Planning & Monitoring?
High Impact Global Product Engineering Solutions ® ©2007 Symphony Service Corp. All Rights Reserved. Symphony Services is a registered trademark of Symphony.
Quality Planning & Defect Estimation
University of Southern California Center for Systems and Software Engineering GQM, GQM+ Supannika Koolmanojwong CSCI577 Spring 2013 (C) USC-CSSE1.
N By: Md Rezaul Huda Reza n
Software Engineering Experimentation An Experimental Framework Jeff Offutt
Unit 8 Syllabus Quality Management : Quality concepts, Software quality assurance, Software Reviews, Formal technical reviews, Statistical Software quality.
Software Engineering Software Process and Project Metrics.
Software Project Management With Usage of Metrics Candaş BOZKURT - Tekin MENTEŞ Delta Aerospace May 21, 2004.
Thomas L. Gilchrist Testing Basics Set 4: Strategies & Metrics By Thomas L. Gilchrist, 2009.
CHAPTER 9 INSPECTIONS AS AN UP-FRONT QUALITY TECHNIQUE
Company LOGO Team assignment 03 Team 04 K15T02. Members… 1.Hoàng Thị Kim Dâng 2.Thái Thanh Nhã 3.Trần Thị Mộng Hà 4.Trần Tiễn Hưng 5.Chu Thị Thu Hương.
University of Southern California Center for Systems and Software Engineering Vu Nguyen, Barry Boehm USC-CSSE ARR, May 1, 2014 COCOMO II Cost Driver Trends.
Computing and SE II Chapter 15: Software Process Management Er-Yu Ding Software Institute, NJU.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
University of Southern California Center for Systems and Software Engineering Software Metrics and Measurements Supannika Koolmanojwong CS577 1.
SOFTWARE PROCESS AND PROJECT METRICS. Topic Covered  Metrics in the process and project domains  Process, project and measurement  Process Metrics.
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…
A Metrics Program. Advantages of Collecting Software Quality Metrics Objective assessments as to whether quality requirements are being met can be made.
Advanced Software Engineering Lecture 4: Process & Project Metrics.
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Most Airlines Are Not Operating at Previous 737NG Maintenance Planning Data (MPD) Document
Class-oriented metrics – Weighted methods per class, depth of the inheritance tree, number of children, coupling, response for class, lack of cohesion.
 Aim of any product development is the Marginal benefit  Marginal benefit = Return on investment  Product needs to be acceptable by the end user i.e.
Emilia Mendes Professora Visitante CAPES/ Associate Professor Univ. Auckland, NZ. Introdução a Métricas, Qualidade e Medição de Software.
Rick Selby Software Products, Northrop Grumman & Adjunct Faculty, University of Southern California Los Angeles, CA Candidate member Main empirical research.
Chapter 4 Software Process and Project Metrics
12 Steps to Useful Software Metrics
Software Project Sizing and Cost Estimation
Software Quality Engineering
Goal, Question, and Metrics
Software Engineering Experimentation
For University Use Only
Chapter 25 Process and Project Metrics
Process and Project Metrics
Software Engineering I
Capability Maturity Model
Software metrics.
Goal-Driven Continuous Risk Management
Chapter 32 Process and Project Metrics
Goal-Driven Software Measurement
Capability Maturity Model
Metrics Organizational Guidelines [1]
Presentation transcript:

University of Southern California Center for Systems and Software Engineering Metrics Organizational Guidelines [1] ©USC-CSSE1 [1] Robert Grady, Practical Software Metrics for Project Management and Process Improvement, Prentice-Hall, 1992

University of Southern California Center for Systems and Software Engineering Goal-Question-Metric Paradigm GQM is a framework for developing a metrics program [1] Steps: –Generate a set of organizational goals What do you want to improve? –Derive a set of questions relating to the goals Answers provide visibility into meeting the goals –Develop a set of metrics needed to answer the questions ©USC-CSSE2 [1] Victor Basili, Software Modeling and Measurement: The Goal/Question/Metric Paradigm, CS-TR-2956, University of Maryland, 1992

University of Southern California Center for Systems and Software Engineering GQM Goal Definition Template Purpose: To (characterize, evaluate, predict, motivate, etc.) the (process, product, model, metric, etc.) in order to (understand, assess, manage, engineer, learn, improve, etc.) it. Perspective: Examine the (cost, effectiveness, correctness, defects, changes, product metrics, reliability, etc.) from the point of view of the (developer, manager, customer, corporate perspective, etc.) Environment: The environment consists of the following: process factors, people factors, problem factors, methods, tools, constraints, etc. ©USC-CSSE3

University of Southern California Center for Systems and Software Engineering Sample Goal Trees (1/2) ©USC-CSSE4 Improve software process predictability Improve effort predictability Improve schedule predictability Improve defect predictability Deliver a quality product within cost and schedule constraints Achieve business value Execute successful project Project planning goal area: Predict the process in order to manage it Project tracking goal area: Evaluate the project in order to manage it

University of Southern California Center for Systems and Software Engineering Sample Goal Trees (2/2) ©USC-CSSE5 Improve the software process Improve productivity Maximize reuse Improve quality Minimize schedule Characterize the process to understand it Prevent defects (minimize defect fixing costs, improve product quality) Defect prevention goal area: Characterize defects in order to prevent them Process change management goal area: Evaluate the process in order to improve it

University of Southern California Center for Systems and Software Engineering ©USC-CSSE6 Sample GQM Map for Inspections defect removal effectiveness Increase quality inspection efficiency Is defect density being reduced over time? Increase productivity Goal Question Metric effectiveness vs. # of inspectors inspection rate control chart Is the inspection process under control? defect finding rate control chart How effective have process changes been? defect density trends How well are inspections performing? Efficiently use inspections to improve process What is the return of inspections? productivity trends Organizational Process ImprovementInspection Process What are optimal inspection parameters? effectiveness vs. preparation/inspection time Is productivity increasing over time? effectiveness vs. inspection rate defect categorization What are high-leverage opportunities for defect prevention? inspection ROI