0% found this document useful (0 votes)
123 views

Chapter 2 Goal Based Framework For Software Measurement

Uploaded by

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

Chapter 2 Goal Based Framework For Software Measurement

Uploaded by

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

Chapter Two

Goal-Based Framework for


Software Measurement

1
Classifying Software Measures
In software there are three such classes

▪ Processes: Collection of software-related activities.

▪ Products: Artifacts, deliverables or documents that


result from a process activity.

▪ Resources: Entities required by a process activity.

2
Internal and External Attributes
• An internal attribute can be measured by examining the
product, process, or resource on its own, separate from its
behavior. (Program size, complexity, dependencies).

• External attributes are those that can be measured only


with respect to how the product, process or resource
relates to the environment.

(Ease of Navigation, Number of failures)

3
Internal and External Attributes

Internal External
▪ Size, Effort, Cost ▪ Usability
▪ Code Complexity ▪ Integrity
▪ Functionality ▪ Efficiency
▪ Modularity ▪ Testability
▪ Redundancy ▪ Reusability
▪ Syntactic Correctness ▪ Portability
▪ Reuse ▪ Interoperability

4
Importance of Internal Attributes
• Many software engineering methods proposed and
developed in the last 25 years provide rules, tools, and
any heuristics for providing software products. It is
claimed that this structure makes them easier to
understand, and tests.

• It is assumed that good internal structure leads to a


good external quality. This connection has rarely been
established.
5
Processes
• We often have questions about our software-development activities and
processes that measurement can help us to answer.

• We want to know how long it takes for a process to complete, how much it will
cost, whether it is effective or efficient, and how it compares with other processes
that we could’ve chosen.

Example: AT&T developers wanted to know the effectiveness of their software


inspections. In particular, managers needed to evacuate the cost of inspections
against benefits received. To do this, they measured the average amount of effort
expended per thousand lines of code reviewed. This information combined with
measures of the number of faults discovered during the inspections, allowed
managers to perform a cost-benefit analysis.
6
Products
• Products are not restricted to the items that management is committed to deliver to the
customer.
• Any artifact or document produced during the software life cycle can be measured and
assessed.
• For example developers often build prototypes for examination only, so that they can
understand requirements or evaluate possible designs; these prototypes may be
measured in some way.
• External product attributes depend on both product behavior and environment, each
attribute measure should take these characteristics into account.
• Internal product attributes are sometimes easy to measure.
• We can determine the size of a product by measuring the number of pages it fills or the
number of words it contains.
• Other internal product attributes are more difficult to measure, because opinions differ as
to what they mean and how to measured them.
• For example the complexity of codes.
7
Resources
• The resources that we are likely to measure include any input for software
production.

• Resources include personnel, materials, tools and methods. Resources are


measured to determine their magnitude, cost and quality.

• Cost is often measured across all types of resources, so that managers can
see how the cost of inputs affects the cost of the outputs.

• Resource measure combines a process measure (input) with a product


measure (output).

8
Determining what to measure
• A particular measurement is useful only if it helps you to
understand the underlying process or one of its resultant
products.

• In turn, recognizing improvement of the process and


product can occur only when the project has clearly
defined goals for process and products.

9
Goal-Question-Metric
• The GQM approach to process and metrics has proven
to be a particular effective approach to selecting and
implementing the metrics.

• To use GQM,
✓You express the overall goals of your organization
✓Ask relevant questions
✓Measure.

10
Examples of AT&T Goals, Questions
and Metrics

11
Measurement and Process
Improvement
• The Software Engineering Institute has suggested
that there are five levels of process maturity.
• These levels of are: ad hoc, repeatable, defined,
managed and optimized.
• The SEI distinguishes one level from another in
terms of key process activity going on at each
level.
12
Overview Of Process Maturity
And Measurement
I. Ad hoc: Initial, Baseline

II. Repeatable: Process dependent on individual.

III. Defined: Process defined and institutionalized.

IV. Managed: Measured process.

V. Optimizing: Improvement fed back to the process.

13
Software Measurement Validation
• Even when you know which entity and attribute you want to
assess, there are many measures from which to choose.

• Measures or measurement systems are used to assess an


existing entity by numerically characterizing one of more of
its attribute.

• Prediction systems are used to predict some attribute of a


future entity, involving a mathematical model with associated
prediction procedures.
14
Software Measurement Validation(2)
• The formal requirement for a validating measure involves
demonstrating that it characterizes the stated attribute
in the sense of measurement Theory.

• To validate the prediction system formally you must first


decide how stochastic it is, and then compare
performance of the prediction system with known data
points.

15
Questions….

16

You might also like