Scribd
Upload
26 views5 pages

Unit 1

The document outlines the principles and importance of software measurement and metrics in software engineering, emphasizing the need for accurate measurement to enhance product quality and facilitate data-driven decision-making. It classifies software measurements into direct and indirect types, and software metrics into product, process, and project metrics, each serving distinct purposes. Additionally, it discusses the advantages and disadvantages of software metrics, as well as the key activities involved in software processes.

Uploaded by

mousam26ca003
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
26 views5 pages

Unit 1

The document outlines the principles and importance of software measurement and metrics in software engineering, emphasizing the need for accurate measurement to enhance product quality and facilitate data-driven decision-making. It classifies software measurements into direct and indirect types, and software metrics into product, process, and project metrics, each serving distinct purposes. Additionally, it discusses the advantages and disadvantages of software metrics, as well as the key activities involved in software processes.

Uploaded by

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

Unit 1

So

Software Measurement and Metrics


Software Measurement: 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.
Software Measurement Principles:
The software measurement process can be characterized by five activities-

1. Formulation: The derivation of software measures and metrics


appropriate for the representation of the software that is being
considered.
2. Collection: The mechanism used to accumulate data required to
derive the formulated metrics.
3. Analysis: The computation of metrics and the application of
mathematical tools.
4. Interpretation: The evaluation of metrics resulting in insight into the
quality of the representation.
5. Feedback: Recommendation derived from the interpretation of
product metrics transmitted to the software team.

Need for Software Measurement:


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.
 Enable data-driven decision-making in project planning and control.
 Identify bottlenecks and areas for improvement to drive process
improvement activities.
 Ensure that industry standards and regulations are followed.
 Give software products and processes a quantitative basis for
evaluation.
 Enable the ongoing improvement of software development practices.
Classification of Software Measurement:
There are 2 types of software measurement:

1. Direct Measurement: In direct measurement, the product, process,


or thing is measured directly using a standard scale.
2. Indirect Measurement: In indirect measurement, the quantity or
quality to be measured is measured using related parameters i.e. by
use of reference.

Software Metrics:
A metric is a measurement of the level at which any impute belongs to a
system product or process.

Software metrics will be useful only if they are characterized effectively and
validated so that their worth is proven. There are 4 functions related to
software metrics:

1. Planning
2. Organizing
3. Controlling
4. Improving

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,
and the method of computing metrics should be clearly defined.
3. Applicability: Metrics should be applicable in the initial phases of the
development of the software.
4. Repeatable: The metric values should be the same when measured
repeatedly and consistent in nature.
5. Economical: The computation of metrics should be economical.
6. Language Independent: Metrics should not depend on any
programming language.

Classification of Software Metrics:


There are 3 types of software metrics:

1. Product Metrics: Product metrics are used to evaluate the state of


the product, tracing risks and undercover prospective problem areas.
The ability of the team to control quality is evaluated. Examples
include lines of code, cyclomatic complexity, code coverage, defect
density, and code maintainability index.
2. Process Metrics: Process metrics pay particular attention to
enhancing the long-term process of the team or organization.
Examples include effort variance, schedule variance, defect injection
rate, and lead time.
3. Project Metrics: The project matrix describes the project
characteristic and execution process. Examples include effort
estimation accuracy, schedule deviation, cost variance, and
productivity.
o Number of software developer
o Staffing patterns over the life cycle of software
o Cost and schedule
o Productivity.

Types of Software Metrics

 Internal metrics: Internal metrics are used to measure properties that are deemed more
important to a software developer than the users. Lines of Code (LOC) is one example.
 External metrics: External metrics are used to measure features that are deemed more
important to the user than the software developers, such
as portability, reliability, functionality, usability, and so on.
 Hybrid Metrics: Metrics that mix product, process, and resource metrics are known as hybrid
metrics. Cost per FP is an example, where FP stands for Function Point Metric.

Advantages of Software Metrics :

1. Reduction in cost or budget.


2. It helps to identify the particular area for improvising.
3. It helps to increase the product quality.
4. Managing the workloads and teams.
5. Reduction in overall time to produce the product,.
6. It helps to determine the complexity of the code and to test the code
with resources.
7. It helps in providing effective planning, controlling and managing of
the entire product.

Disadvantages of Software Metrics :

1. It is expensive and difficult to implement the metrics in some cases.


2. Performance of the entire team or an individual from the team can’t be
determined. Only the performance of the product is determined.
3. Sometimes the quality of the product is not met with the expectation.
4. It leads to measure the unwanted data which is wastage of time.
5. Measuring the incorrect data leads to make wrong decision making.

Software Processes
The term software specifies to the set of computer programs, procedures
and associated documents (Flowcharts, manuals, etc.) that describe the
program and how they are to be used.

A software process is the set of activities and associated outcome that


produce a software product. Software engineers mostly carry out these
activities. These are four key process activities, which are common to all
software processes. These activities are:

1. Software specifications: The functionality of the software and constraints


on its operation must be defined.
2. Software development: The software to meet the requirement must be
produced.

3. Software validation: The software must be validated to ensure that it does


what the customer wants.

4. Software evolution: The software must evolve to meet changing client


needs.

You might also like