SOFTWARE MEASUREMENT

AND METRICS
MEASUREMENT
• Software measurement is a quantified attribute of a characteristic of a software product or the
software process.
• A measurement is a manifestation of the size, quantity, amount or dimension of a particular
attribute of a product or process.
• Software measurement is a titrate impute of a characteristic of a software product or the software
process. It is an authority within software engineering.
• The software measurement process is defined and governed by ISO Standard .
METHODS OF MEASUREMENT
• There are three basic methods for measuring software size:
1. SLOC (Source Line-Of-Code): Source Line-Of- Code is the primary measure for the software
size. However especially during the early development stages, it is difficult to relate software
functional requirements to Source Line-Of-Code

2. Function Points: Function point method is used as an alternative method of Source Line-Of-
Code, and it should be used for the software size estimate. For the management information
systems (MISS) function points are used primarily.

3. Feature points: Feature points method is similar to function points method and used for the
embedded systems or real-time systems
NEED OF SOFTWARE MEASUREMENT
Measurement are a key element for controlling software engineering processes. By controlling it
meant that one access the status of the process, observe the trends to what is likely to happen and take
corrective action for modifying our practices

Software is measured to:

• Create the quality of the current product or process.
• Anticipate future qualities of the product or process.
• Enhance the quality of a product or process.
• Regulate the state of the project in relation to budget and schedule.
TYPES
There are 2 types of software measurement:

1. Direct Measurement :
In direct measurement the product, process or thing is measured directly using standard scale.

2. Indirect Measurement :
In indirect measurement the quantity or quality to be measured is measured using related parameter
i.e., by use of reference.
METRICS
A software metric is a measure of software characteristics which are measurable or countable.
A metric is a measurement of the level that any impute belongs to a system product or process.
Software metrics are valuable for many reasons, including measuring software performance, planning work items, measuring
productivity, and many other uses.
Software engineering metrics cover a wide range of activities, including the following:
• Estimation of costs and time.
• Productivity metrics and model.
• Gathering data
• Models and measures of quantity.
• Models of dependability
• Models for performance and evaluation.
• Metrics of structural and complexity
• Assessment of capability and maturity.
• Metrics-based management.
• Evaluation of tools and methods.
CHARACTERISTICS OF SOFTWARE METRICS
Following are the characteristics of software metrics:

1. Quantitative :Metrics must possess quantitative nature. It means metrics can be expressed in values.
2.Understandable :Metric computation should be easily understood, the method of computing metric
should be clearly defined.
3.Applicability:Metrics should be applicable in the initial phases of development of the software
4.Repeatable :The metric values should be same when measured repeatedly and consistent in nature.
5.Economical:Computation of metrics should be economical.
6.Language Independent :Metrics should not depend on any programming language
CLASSIFICATION OF SOFTWARE METRICS
1.Product Metrics:
Product metrics are used to evaluate the state of the product, tracing risks and undercovering
prospective problem areas. The ability of team to control quality is evaluated. Size, complexity, design
features, performance, and quality level of the product are all factors to consider.
2.Process Metrics:
To optimize software development and maintenance, process metrics can be used.. Process metrics pay
particular attention on enhancing the long term process of the team or organization.
3.Project Metrics:
The characteristics and execution of a project are described by project metrics. The project matrix
describes the project characteristic and execution process.
• Number of software developer.
• Staffing pattern over the life cycle of software.
• Cost and schedule.
• Productivity
CLASSIFICATION OF SOFTWARE METRICS
1.Product Metrics:
Product metrics are used to evaluate the state of the product, tracing risks and undercovering
prospective problem areas. The ability of team to control quality is evaluated. Size, complexity, design
features, performance, and quality level of the product are all factors to consider.
2.Process Metrics:
To optimize software development and maintenance, process metrics can be used.. Process metrics pay
particular attention on enhancing the long term process of the team or organization.
3.Project Metrics:
The characteristics and execution of a project are described by project metrics. The project matrix
describes the project characteristic and execution process.
• Number of software developer.
• Staffing pattern over the life cycle of software.
• Cost and schedule.
• Productivity