0% found this document useful (0 votes)
35 views18 pages

Software Process Measurement

1. Software metrics are used to measure processes, products, and projects to manage quality and improve the software development lifecycle. 2. Process metrics measure attributes of the development process, product metrics measure attributes of the software product, and project metrics track attributes like cost, schedule and staffing. 3. Good metrics provide quantitative indicators to determine quality, identify problems, and guide process, product and project improvements.

Uploaded by

samar haider
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
35 views18 pages

Software Process Measurement

1. Software metrics are used to measure processes, products, and projects to manage quality and improve the software development lifecycle. 2. Process metrics measure attributes of the development process, product metrics measure attributes of the software product, and project metrics track attributes like cost, schedule and staffing. 3. Good metrics provide quantitative indicators to determine quality, identify problems, and guide process, product and project improvements.

Uploaded by

samar haider
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 18

Lecture : 04

Software Process
Measurement
Why do we measure?
IF YOU CAN’T MEASURE IT, YOU CAN’T MANAGE IT (Tom DeMarco, 1982)

1. Determine quality of piece of software or documentation


2. Determine the quality work of people such software engineers, programmers, database admin, and most
importantly MANAGERS
3. Improve quality of a product/project/ process
4. To uncover problem areas before they go critical
5. To close the gap of any problems (E.g training)
6. To help justify requests for new tools or additional training
7. Track potential risks
8. To adjust workflow or tasks
Definitions
MEASUREMENT: is the act of obtaining a measure.

MEASURE: provides a quantitative indication of the size of some product or process


attribute e.g. number of errors

METRIC: is a quantitative measure of the degree to which a system, component or


process possesses a given attribute e.g. number of errors found per person hours
expected.
What to Measure
Process: Measure the efficacy of processes. What works.. what doesn’t

Project: Assess the status of the project. Track risks Identify problem areas. Adjust
workflows

Product: Measure predefined product attributes


A Good Manager Measures
What to measure (Process)
Code quality
Programmer productivity
Software engineer productivity
Requirements,
design,
testing
and all other tasks done by software engineers
Software
Maintainability
Usability
And all other quality factors
Management
Cost estimation
Schedule estimation, Duration, time
Staffing
Process Metrics Vs Project Metrics
Process metrics are measures of the Project Metrics are the measures of Software
software development process, such Project and are used to monitor and control the
as project.
Overall development time They usually show how project manager can
Type of methodology used estimate schedule and cost
Process metrics are collected across They enable a software project manager to:
all projects and over long periods of
time.  Minimize the development time by making
Their intent is to provide indicators the adjustments necessary to avoid delays and
that lead to long-term software potential problems and risks.
process improvement.
 Assess product cost on an ongoing basis &
modify the technical approach to improve cost
estimation.
Process Metrics Vs Product Metrics
Process metrics are measures of the Product metrics are measures of the software
software development process, such product at any stage of its development, from
as requirements to installed system. Product
Overall development time metrics may measure:
Type of methodology used How easy is the software to use
How easy is the user to maintain
Process metrics are collected across
all projects and over long periods of The quality of software documentation
time. And more ..
Their intent is to provide indicators .
that lead to long-term software
process improvement.
Integrating Metrics within the Software Process
Process Measurement
We measure the efficacy of the software process indirectly
That is we drive a set of metrics based on the outcomes that can be derived from the
process

Outcomes include
measures of errors uncovered before release of the software
defects delivered to and reported by the end users
work products delivered (productivity)
human effort expended
calendar time expended
schedule conformance

We also derive process metrics by measuring the characteristics of specific software


engineering tasks.
Process Metrics
Quality-Related:
Focus on quality of work products and deliverables
Productivity-Related:
Production of work-products related to effort expended
Statistical SQA data:
Error categorization & analysis
Defect Removal Efficiency
Propagation of errors from process activity to activity
Reuse Data
The number of components produced and their degree of reusability
Software Metrics etiquettes
 Do not use metrics to appraise people
 Provide regular feedback to the individuals and teams who collect measure and
metrics
Use common sense and organizational sensitivity when analyzing and interpreting
software metrics data.
 Don’t obsess on a single metric to the exclusion of other important metrics
 Metrics area that indicate a problem area should not be considered negative. These
data are merely an indicator for process improvement.
 Never use metrics to threaten individuals or teams
 Work with practitioners and teams to set clear goals and metrics that will be used to
achieve them
Statistical Software Process Improvement
ERROR
Some flaw in the software engineering work product that is uncovered before the
s/w is delivered to the end-user

DEFECT:
A flaw that is uncovered after the delivery to the end user
TASK:
Identify the metrics parameters in a Web Engineering project
TASK:
Identify the metrics parameters in a Web Engineering project
Core Measurement Process
Who Cares about what?
Managers – Project Measures

Developers – Product Measures

Both should care about the Process measures.


What should we measure?

Process Measure Product Measure Project Measure


- how effective is the process? -performance and quality - used to monitor the state
- how well are we following - How well is the product of the project
the process? meeting its requirements
- how are we doing relative to
- risk monitoring cost, schedule and staffing)

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy