APPLICATION

ENGINEERING
METRICS
HITESHI
801031011
ME(SE)- 2ND SEM
Overview…..
Project-level functions
 Reuse distribution
 Project-level Return on Investment
 Reusable code percentage

Domain engineering metrics

 Reuse means: software library metrics

Organization level metrics

 Reuse impact: Productivity gains
 Project-level functions

Project-level Return Reusable Code

Reuse Distribution
on Investment Percentage

New code

Reused code

Adapted code
• This metrics considers the overall size of the application
produced by the software development project .
• Divided into three categories as:

New Code: %age of code developed specifically for the application.

Reused Code, verbatim: %age of code reused verbatim from a

corporate reuse library.

Adapted Code: %age of code reused from a corporate reuse library,

after adaptation.
Reuse distribution…..
• Definition emphasis on:
 Size percentage..,, measured in lines of code(LOC). But we can use
other measures also, say function points.
 Measure is used in computing the percentages, which must be
interpreted with cautions.
Example: Consider a project having
Reused code = 20%
New code = 80%
So, Even if we neglect the cost of integrating the reused code and the
nonlinear effects of the software costs, we cannot claim that we have
saved 20% of the development effort, because the size of a reused
asset is larger than the size of the written code if the reusable asset
were not available.
•It quantifies the decision by providing the estimates of risks and benefits
and matching them in an ROI equation.
Say, a corporation has a stake that all projects make use of reusable assets
,individual projects have to balance the benefits of reuse against other short-
term considerations ,like changes in the group’s operational procedures ,
risks that project staff be distracted by the introduction of reuse technology
but do not benefit from it and overhead caused by producing reusable asset.
The decision apply to the software reuse in any one project is not
straightforward i.e. there are some cases where from the projects
viewpoint, the potential risks outweight the benefits.
• This metrics reflects the amount of code contributed by the
individual project to the corporate software reuse library, as a
percentage of the size of the application produced by the project.

• It can also used to reward the individual projects;

• Challenge of the project manager is to optimize this metrics without

undue burden on the project team and without derailing the project
goals.
II. Domain engineering metrics..
This metrics reflects to what extent the domain engineering effort
is successful, by quantifying the level of demand experienced by
domain assets, the level of efficiency of the library and the
degree of usefulness of domain assets.

Software library metrics: To justify the creation or the existence of a software

reuse library we consider the level of use of the libraries in the organization day
to day operations. We have three metrics to identified the level of library traffic
as:

No. of accesses to the library

No. of retrieval from the library

Library efficiency
• It reflects the corporation involvement in software reuse, or the
corporate maturity w.r.t software reuse .

 It includes Productivity Gains ; quantifies the impact of

reuse on corporate operation considering the
distribution of reused and original code in the total
quantity of code produced per unit of time. If the unit of
time is the “Year” and the amount of code is measured
in “KLOC” the distribution table is obtained known as
“yearly reuse distribution by size” as :
Category Percentage

New code %

Reuse code ,verbatim %

Internal %

External %

Adapted Code %

Internal %

External %
• Reuse Code and Adapted Code , we have

Internal Code : developed in-house

External Code: code acquired from outside source

These two codes having different cost equations and hence we

considered them separately.
• If we ignore the distinction between the internal and external
sources of reusable (or adaptable ) code and in application we
assume that

Cn: New code

Cr: Reusable code

Ca: Adaptable code

• So, the cost of developing a LOC with reuse averages 0.20 times
the cost of developing a new line from a scratch and the cost of
developing a LOC by adaptation is on average 0.67 times the cost
of developing a new line from scratch.

• We also find that the cost of developing a product with reuse

distribution ( Cn, Cr, Ca ) is a linear function of

Cn +0.2 * Cr +0.67 * Ca

having constraints: Cn + Cr +Ca =1 .

• We can also use “ reuse leverage metrics” as the ratio between the
productivity of the organization ( LOC/ year ) with reuse over its
productivity without reuse.