SOFTWARE METRICS Presentation Transcript:
1.SOFTWARE METRICS FOR PROCESS AND PROJECTS
2.SOFTWARE METRICS FOR PROCESS AND PROJECTS
Software Process Metrics and Project Metrics are Quantitative Measures that enable Software Professionals to gain insight into the efficacy of Software Process and the Project that are conducted using the Process as a Framework.
Quality and Productivity data are collected, analysed and compared against past averages to :-
- Assess Productivity improvements.
- Pinpoint Problem areas
3.WHO DOES IT ?
Software Measures are often collected by Software Engineers/ Software Practitioner.
Software Metrics are analyzed and assesses by Software Managers.
WHY METRICS IS IMPORTANT?
If you do not measure, your judgment can be based only on subjective evaluations. With Measurement:-
- Trends can be spotted,
- Better estimates can be made,
- True improvement can be accomplished
4.WHAT ARE THE STEPS?
1. Defining a limited set of Process and Project that are easy to collect.
2. The result is analyzed and compared to ‘’Past Average’’ for similar Project performed within the organization. 3. Trends are assessed and conclusions are generated.
WORK PRODUCT?
A set of Software Metrics that provide insight into the Process and understanding of the Project.
- Productivity Metrics
- Quality Metrics
5.
REASONS FOR MEASURING
To Characterize
To Evaluate
To Predict
To Improve
Measurement is a Management Tool.
Measurement provides a Project Manager with insight. It assists Manager and Project team in making sound decision.
6.Project Metrics are collected across all Projects and over long periods of time. Their intent is to provide a set of Process Indicators that lead to long term Software Process improvement.
Project Metrics enable Project Managers to:
Assess the status of an ongoing Project
Track potential Risks
Uncover Problem areas before they “Go critical”
Adjust work flow or Tasks
Evaluate the Project Team’s ability to Control Quality of Software Work Product.
Measures that are collected by a Project team and converted into Metrics for use during a Project can also be transmitted to those with responsibility for Software Process improvement.
For this reason, many of the same Metrics are used in both the Process and Project domain.
7.The only Rational way to improve any Process is to:
a) Measure Specific attributes of the Process
b) Develop a set of meaningful Metrics based on these attributes
c) Use Metrics to provide Indicator that will lead to strategy for improvement
However it is important to note that Process is only one of a number
of ‘’Controllable Factors’’ in improving Software Quality and
Organizational performance.
8.SOFTWARE METRICS FOR PROCESS AND PROJECTS
9.The Figure shows the Process in the centre of a triangle connecting three
Factors that have profound influence on Software Quality and Organizational
Performance.
The Skills and the Motivation of people has been shown to be the single influential factor in Quality and Performance.
The Complexity of Product can have a substantial impact on Quality and Project Team Performance.
The Technology (Methods and Tools) that populates the Process has an impact.
The Process Triangle exists within a circle of Environmental Conditions that
include the Development Environment (CASE TOOLS, Business Conditions
(Deadlines, Business rules), and Customer Characteristics (ease of
communication and collaboration etc)
10.We measuring the efficacy of Software Process “indirectly”.
We derive a Set of Metrics based on the Outcomes that can be derived from Process.
Outcomes include Measures of:-
- Errors uncovered before release of Software,
- Defects delivered to and reported by end-users, - Work Products delivered (Productivity),
- Human effort expanded,
- Calendar time expanded,
- Schedule conformance
- Other measures.
We also derive Process Metrics by measuring the Characteristics of specific Software Engineering Task.
(E.g. we might measure the Effort and Time spent performing the Generic Software Engineering Activities.)
Source: Power Point Presentations
1.SOFTWARE METRICS FOR PROCESS AND PROJECTS
2.SOFTWARE METRICS FOR PROCESS AND PROJECTS
Software Process Metrics and Project Metrics are Quantitative Measures that enable Software Professionals to gain insight into the efficacy of Software Process and the Project that are conducted using the Process as a Framework.
Quality and Productivity data are collected, analysed and compared against past averages to :-
- Assess Productivity improvements.
- Pinpoint Problem areas
3.WHO DOES IT ?
Software Measures are often collected by Software Engineers/ Software Practitioner.
Software Metrics are analyzed and assesses by Software Managers.
WHY METRICS IS IMPORTANT?
If you do not measure, your judgment can be based only on subjective evaluations. With Measurement:-
- Trends can be spotted,
- Better estimates can be made,
- True improvement can be accomplished
4.WHAT ARE THE STEPS?
1. Defining a limited set of Process and Project that are easy to collect.
2. The result is analyzed and compared to ‘’Past Average’’ for similar Project performed within the organization. 3. Trends are assessed and conclusions are generated.
WORK PRODUCT?
A set of Software Metrics that provide insight into the Process and understanding of the Project.
- Productivity Metrics
- Quality Metrics
5.
REASONS FOR MEASURING
To Characterize
To Evaluate
To Predict
To Improve
Measurement is a Management Tool.
Measurement provides a Project Manager with insight. It assists Manager and Project team in making sound decision.
6.Project Metrics are collected across all Projects and over long periods of time. Their intent is to provide a set of Process Indicators that lead to long term Software Process improvement.
Project Metrics enable Project Managers to:
Assess the status of an ongoing Project
Track potential Risks
Uncover Problem areas before they “Go critical”
Adjust work flow or Tasks
Evaluate the Project Team’s ability to Control Quality of Software Work Product.
Measures that are collected by a Project team and converted into Metrics for use during a Project can also be transmitted to those with responsibility for Software Process improvement.
For this reason, many of the same Metrics are used in both the Process and Project domain.
7.The only Rational way to improve any Process is to:
a) Measure Specific attributes of the Process
b) Develop a set of meaningful Metrics based on these attributes
c) Use Metrics to provide Indicator that will lead to strategy for improvement
However it is important to note that Process is only one of a number
of ‘’Controllable Factors’’ in improving Software Quality and
Organizational performance.
8.SOFTWARE METRICS FOR PROCESS AND PROJECTS
9.The Figure shows the Process in the centre of a triangle connecting three
Factors that have profound influence on Software Quality and Organizational
Performance.
The Skills and the Motivation of people has been shown to be the single influential factor in Quality and Performance.
The Complexity of Product can have a substantial impact on Quality and Project Team Performance.
The Technology (Methods and Tools) that populates the Process has an impact.
The Process Triangle exists within a circle of Environmental Conditions that
include the Development Environment (CASE TOOLS, Business Conditions
(Deadlines, Business rules), and Customer Characteristics (ease of
communication and collaboration etc)
10.We measuring the efficacy of Software Process “indirectly”.
We derive a Set of Metrics based on the Outcomes that can be derived from Process.
Outcomes include Measures of:-
- Errors uncovered before release of Software,
- Defects delivered to and reported by end-users, - Work Products delivered (Productivity),
- Human effort expanded,
- Calendar time expanded,
- Schedule conformance
- Other measures.
We also derive Process Metrics by measuring the Characteristics of specific Software Engineering Task.
(E.g. we might measure the Effort and Time spent performing the Generic Software Engineering Activities.)
Source: Power Point Presentations
Posts
0 comments