IIM Rohtak

If you are not measuring, then how are you managing?

Effort Resources Schedule

SOFTWARE PROJECT
MANAGEMENT
……
Outsourcing Modelling Structure

Indian Institute of Management (IIM),Rohtak

 Software Project Planning

Cocomo Model
 Software Project Planning

The Norden / Rayleigh Curve

The curve is modeled by differential equation

dy − at 2
m(t ) = = 2kate --------- (1)
dt
dy
dt
= manpower utilization rate per unit time
a = parameter that affects the shape of the curve
K = area under curve in the interval [0, ∞ ]
t = elapsed time
 Software Project Planning
dy − at 2
m(t ) = = 2kate --------- (1)
dt
On Integration on interval [o, t]

y(t) = K [1-e-at2] -------------(2)

Where y(t): cumulative manpower used upto time t.

y(0) = 0
y(∞) = k

The cumulative manpower is null at the start of the project, and

grows monotonically towards the total effort K (area under the
curve).
 Software Project Planning
d2y − at 2
2
= 2 kae [1 − 2 at 2
]=0
dt
1
td =
2

2a
“td”: time where maximum effort rate occurs
Replace “td” for t in equation (2)
 t d2 

E = y (t ) = k 1 − e 2 t d2  = K (1 − e −0.5 )
 
 
E = y (t ) = 0.3935k
1
a= 2
5
2t d
 Software Project Planning

1
Replace “a” with 2
in the Norden/Rayleigh model(eq1)
2t d
. By making this substitution in equation we have

t2
− t2
2K 2t d2 − 2
m(t ) = te K
2t d2 = 2 te 2t d

td

m0 = K e
td
6
 Software Project Planning
At time t=td, peak manning m (td) is obtained and denoted by mo.

k
mo =
td e
k = Total project cost/effort in person-years.
td = Delivery time in years
m0 = No. of persons employed at the peak
e = 2.71828

7
 Software Project Planning

Example

A software development project is planned to cost 95 PY in a period

of 1 year and 9 months. Calculate the peak manning and average rate
of software team build up.
 Software Project Planning
Solution
Software development cost k=95 MY
Peak development time td = 1 Y 9 M =1+9/12=1.75 years
k
Peak manning mo=
td e

95
= 32.94 = 33 persons
1.75 1.648
Average rate of software team build up

m0 33
= = = 18.8 persons / year or 1.56 person / month
td 1.75
9
 Software Project Planning

Example:

Consider a large-scale project for which the manpower requirement is

K=600 PY and the development time is 3 years 6 months.

(a)Calculate the peak manning and AVERAGE team buildup rate.

(b)What is the manpower cost after 1 year and 2 months?
 Software Project Planning

Solution

(a) We know td=3 years and 6 months = 3.5 years

K
NOW m0 =
td e

 m0 = 600/(3.5x1.648)  104 persons

104/3.5=29p/y

11
 Software Project Planning

 
(b) We know
− at 2
y (t ) = K 1 − e
t = 1 year and 2 months
= 1.17 years
1 1
a= = = 0.041
2t d 2  (3.5)
2 2

y (1.17) = 600 1 − e  − 0.041(1.17 ) 2


= 32.6 P

12
 IIM Rohtak

Additional Information:
•The cost per person per year is $50,000.
•A 5% annual inflation rate increases manpower costs after each
year.

(c) If the project experiences a delay and is completed in 4 years instead of 3 years 6
months, estimate the additional cost incurred due to the delay, given the inflation continues
at 5% annually.
Indian Institute of Management (IIM),Rohtak
 IIM Rohtak

Average Team Buildup Rate:

•The average team buildup rate is calculated as:

=K/Td =600/3.5=171.42 PY

Mo =K/Td*squart(e) =600/3.5*1.648=104 p

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Total Manpower Cost Considering 5% Annual Inflation

To account for inflation, the cost per person-year increases by 5%
annually. Let's calculate the total cost year by year.
•Year 1:
• Cost per PY = $50,000 (no inflation yet)
• Manpower requirement: 171.43 PY (since this is the average
buildup for 1 year)
Cost for Year 1: Cost for Year 1=171.43 PY×50,000 $=8,571,500 $
Year 2:
•Inflation-adjusted cost per PY = $50,000 \times 1.05 = $52,500
Cost for Year 2: Cost for Year 2=171.43 PY×52,500 $=8,997,075 $
Year 3:
•Inflation-adjusted cost per PY = $52,500 \times 1.05 = $55,125
Cost for Year 3=171.43PY×55,125$=9,446,929$.
Year 4 (6 months): Inflation-adjusted cost per PY = $55,125 \times
1.05 = $57,881.25 Cost for Year 4 (6 months):
Cost for Year 4=85.72 PY×57,881.25 $=4,961,400
Indian Institute of Management (IIM),Rohtak
 IIM Rohtak

•Total Project Cost with Inflation:

•Total Cost=8,571,500 $+8,997,075 $+9,446,929 $+4,961,400 $=31,9
76,904
Thus, the total manpower cost for the project, accounting for
inflation, is approximately $31,976,904.

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

What is the manpower cost after 1 year and 2 months (14

months), assuming 60% of the team is built by this time and that
the cost per PY remains constant in the first year?

Manpower Cost after 1 Year and 2 Months (14 months)

After 14 months, 60% of the total team is built, meaning the
manpower requirement fulfilled is:
Manpower built=0.60×600=360 PY
The cost associated with this manpower is calculated using the
constant manpower cost of $50,000 per PY (since inflation starts
after the first year):
Cost after 14 months=360 PY×50,000 $ per PY=18,000,000 $
So, the manpower cost after 1 year and 2 months is $18,000,000.

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Cocomo II screens

http://csse.usc.edu/csse/research/COCOMO_suite/index.html

http://sunset.usc.edu/csse/research/COCOMOII/cocomo_main.html

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Cocomo screens

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Cocomo screens

Indian Institute of Management (IIM),Rohtak

What the Cocomo II screen looks like upon starting a new Project.
Let start with Post Architecture model.
Enter a Project Name
Can’t really do much unless we add a Module, so
choose Edit → Add Module. A new line shows
up in the screen with a default module name.
1. Change the 2. Now double click on the
module name yellow rectangle under
to whatever Module Size…
you want.
This screen will pop up allowing us to choose
between Source Lines Of Code (SLOC),
Function Points, or Adaptation and Re-Use. Let’s
stick with SLOC for this module.
I have indicated my program language is C++
(this is really important to know for Function
Points), there is an estimated 10,000 lines of
code, and 20% of the code will be discarded due
to requirements evolution and volatility.
Hit OK…
The main screen is updated with the SLOC and programming
language as well as some calculated values.
Now add another module and choose Function Points.
This is the
default screen
for Function
Points.

Let’s look
deeper at the
Function Type
descriptions…
External Input Count each unique user data or user control input type that (i)
(Inputs) enters the external boundary of the software system being
measured and (ii) adds or changes data in a logical internal
file.
External Output Count each unique user data or control output type that leaves
(Outputs) the external boundary of the software system being measured.

Internal Logical File Count each major logical group of user data or control
(Files) information in the software system as a logical internal file
type. Include each logical file (e.g., each logical group of data)
that is generated, used, or maintained by the software system.

External Interface Files passed or shared between software systems should be

Files (Interfaces) counted as external interface file types within each system.

External Inquiry Count each unique input-output combination, where an input

(Queries) causes and generates an immediate output, as an external
inquiry type.

From Cocomo II User Manual via software

So let’s go back
into this screen
and add some
entries in the
grid.

Notice, there are

some kind of
subtotals per
line, but the
Equivalent
SLOC = 0.

Let’s change the

Language and
see what
happens.
By changing the
language to
C++, we now
have an
Equivalent Total
in SLOC.

Also, we can
see a value next
to the Change
Multiplier
button.

Let’s change the

language to
Machine Code!
☺
Quite a
difference
jumping from
10,653 SLOC to
128,640 SLOC.

Note the
multiplier
changed from
53 to 640.

Change the
language once
more to 5’th
Generation.
So using a 5’th
generation level
language would cut
our code base by a
factor of 285 times
according to
Cocomo II’s default
estimation (not
calibrated for your
environment, not
taking into account
other factors).

Change the
language to C++
and change REVL
to 20%…
So now Module2 has F:12783 or, in other words, it’s
based on Function points (the F:) and it has an
equivalent 12,783 lines of code (10,653 + 20% for
volatility).
So how did the 12,783 (or even the 10,653) get calc’d?
Part 1 of the answer is to click on Parameters→
Function Points. You will see the following screen…
So let’s see what part of the calculation we just affected…
So now let’s add a module and use Adaptation and Reuse…
What % of the adapted
software’s design will
change?

… % of code that will

change?

% of effort required to
integrate the adapted
software into an
overall product and to
test the resulting
product as compared to
the normal amount of
integration and test
effort for software of
comparable size.
Software Understanding
(SU): Use the table
below to help you come
up with a weighted
average based on three
key areas…
Assessment &
Assimilation (AA): 0 to 8.
Effort to determine
whether
a fully-reused software
module is appropriate to
the application, and to
integrate its description
into the overall product
description
These last two areas have
to deal with automatically
translating code.
Double click on the yellow rectangle under EAF for Module1
This screen will pop-
up. As you click on
any given button top
row button, the
button’s title will
change (Nom,
High,Very High,
Very Low, Low, etc)
AND you will see
the EAF at the
bottom of the screen
change.
I have changed ONLY
the button for RELY to
VHI and by doing so,
the EAF has changed
to 1.26.

So we just increased
the Effort equation by
26%!!!

Click OK to see the

result.
So the EAF for Module1 has changed. We also see changes on
the results to the right… NOM DEV has stayed the same; EST
DEV has gone from 48.6 to 61.6; PROD from 245.6 to 194.9;
Staff from 3 to 3.7; and risk from 0.0 to 1.7. What does this all
mean?
•INST COST: calculated most likely cost per instruction. This
number is calculated from Cost/SLOC in each module.
•Staff: most likely estimate for the number of full-time
developers that would be needed to complete a module in the
estimated development time.
•RISK: total_risk = schedule_risk + product_risk +
personnel_risk + process_risk + platform_risk + reuse_risk.
To answer that question we need to click on the above menu
choices Parameters→Post Architecture→Product.

Note: There are other parameter menus just like the Post-Arch /
Product choices. You can see a list of those above. You can
adjust Function Point weights, EAF factors for Early
Architecture, Scale Factors, the number of hours in a Person
Month, etc.
This is where you set the quantitative measures associated with
your qualitative choices. This is how you calibrate Cocomo II to
fit your environment. You can also save your calibrations as a
separate loadable module.
•If we go back to the main screen and click on Scale Factor, we
see the above Popup screen.

•Important Note: Scale Factor and Schedule are Project-wide,

not module specific!!!
Change Precedentedness to VHI. Notice that the number to the
right of the button changes to 1.24. Click OK.
Notice that some of the costs have changed. In particular, they
have gone down. By decreasing the exponent in the effort
equation, we have decreased the effort expenditure required.

Let’s see what area of the calculation we are talking about…

Again, what does “VHI” mean quantitatively for
“Precedentedness”, and what are the details?

From Parameters→Scale Factors, we can find the quantitative

measures shown above in the pop-up…
It should be noted we have been dealing with the Post
Architecture model. An Early Design model is available as well
with only 7 Effort Adjustment Factors, no RISK assessment (that
I know of), and the same project-wide Scale Factors and
Schedule. BUT… in Cocomo II there is a separate Schedule
weight adjustment in each model.
What other information can be obtained from the calculations?
Well, for one, we know the total lines of code estimated…
We are also given a range of estimates, + / - one standard deviation
from the mean.
We can also see some reports with effort distribution, either as a
Waterfall lifecycle or “MBASE” (a spiral model), and across all
phases or for a specific phase.

So, from the above choices, let’s choose “Overall Phase”

Notice the percentages for Elaboration and Construction add
up to 100%!!! Inception and Transition are statically
configured as a percent of Elaboration and Construction, in
this case at 6% and 12% respectively.
Let’s take a look at the Inception phase in MBASE…
Totals up to 100%…
File menu options. The intriguing ones are the
ability to change the weighting factors for Effort
Adjustment Factors, Scale Factors, Person Man-
Months, and Function Points… and then save
those as your own Model for future projects.

Also, if you choose the Export option, you can

then load up additional reports via an Excel
interface (you can find the Excel file by
navigating via the Start→Programs→USC
Cocomo II).
 Parting thoughts…
1. There are limited online calculator versions of Cocomo 81 and Cocomo II:
http://sunset.usc.edu/research/COCOMOII/cocomo81_pgm/cocomo81.html
http://sunset.usc.edu/research/COCOMOII/expert_cocomo/expert_cocomo2000
.html
2. SoftStarSystems.com sells CoStar, a Cocomo II on steroids. A trial version limited to
5,000 lines of code is available. Single user license starts at $2,000!!!
3. It’s really hard getting a good handle on all the current algorithms for Cocomo II. It
varies over time, administered by fluctuating grad students, etc.
4. Home website for Cocomo:
http://sunset.usc.edu/csse/research/COCOMOII/cocomo_main.html
5. Email from USC student: There is no source code available for COCOMO II.
This would be an interesting open source/thesis project if you could get their
data!
Software Cost Model
 IIM Rohtak

Use Case point Method

UAW UUCW TCF ECF

UUCP

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Use Case Modeling

Help of

Use Case
Relationship

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Online Shopping Example

Use case: A use case describes a
sequence of actions that provide
something of measurable value System
to an actor and is drawn as a oval boundary

System boundary:
Actor indicates the scope of your
system. Anything within the
box represents functionality
that is in scope and anything
Use case outside the box is not
Actor: An actor is a person,
organization, or external
system that plays a role in
one or more interactions
with your system
Indian Institute of Management (IIM),Rohtak
 IIM Rohtak

system name
system boundary
ATM
System
primary actor 1
Withdraw secondary actor
Money

2
Bank Deposit
Customer Money
Customer
Accounts
role 3 Database
Transfer
Money
association

4
Check
use case Balance

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Sub-use Case Diagram

1a
Withdraw from
<<extend>> Check

1
Withdraw
Money
Bank
Customer
<<extend>>
1b
Withdraw from
Customer
Savings
Accounts
Database

This is an extend dependency.

It indicates that use case 1b is part of use
case 1, but it may or may not be invoked.
The same is true of use case 1a.
Indian Institute of Management (IIM),Rohtak
 IIM Rohtak

Sub-use Case Diagram

1a
Withdraw from
Checking

1
Withdraw
Money
Bank
Customer
1b
Withdraw from
Customer
Savings
Accounts
Database
generalization

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Sub-use Case Diagram

3a
Select
<<include>> Accounts

3
Transfer
Money
Bank
Customer
<<include>>
3b
Update Account
Customer
Balances
Accounts
Database

This is an include dependency.

It indicates that use case 3b is “included”
in use case 3 and will be invoked.
The same is true of use case 3a.
Indian Institute of Management (IIM),Rohtak
 IIM Rohtak

Medical Clinic Example

Both Make Appointment
and Request Medication
include Check Patient
Record as a subtask.

An extend
relationship indicates
that one use case is a
variation of another.

A use case generalization shows that

one use case is simply a special kind
of another.
Indian Institute of Management (IIM),Rohtak
 IIM Rohtak

Case: Consider an online reservation system for a bus

company.. Seats can be reserved by customers on the web
site of the bus company. The customer has the option to
directly pay for the seat through the website. In that case, the
seat cannot be cancelled (neither by the customer nor by the
bus company). If the customer has not paid for the seat, the
bus company can cancel the seat if the customer does not
show up one hour before the trip. When the reservation is
cancelled, the seat will become free and can be sold to
another customer. Both the customer and the company staff
must authenticate themselves for performing operations with
the system. Draw a simple use case diagram for
describing the basic functional requirements(reservation)
of the above system
Indian Institute of Management (IIM),Rohtak
 IIM Rohtak

Case :sol

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Use Case Point Estimation – Process

Use Case Point Estimation 79

11/9/2024 Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Use Case point Method

Use-Case Points Counting Process

The Use-Case Points counting process
has the following steps −
Calculate unadjusted UCPs
Adjust for technical complexity
Adjust for environmental complexity
Calculate adjusted UCPs

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Use Case point Method

Step 1.1 − Determine Unadjusted Use-Case Weight.
Step 1.1.1 − Find the number of transactions in each
Use-Case.
Step 1.1.2 − Classify each Use-Case as Simple,
Average or Complex based on the number of
transactions in the Use-Case. Also, assign Use-Case
Weight as shown in the following table −

Use-Case Number of Use-Case Weight

Complexity Transactions
Simple ≤3 5
Average 4 to 7 10
Complex >7 15

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Use Case point Method

Step 1.1.3 − Repeat for each Use-Case and get all the Use-Case
Weights. Unadjusted Use-Case Weight (UUCW) is the sum of all
the Use-Case Weights.
Step 1.1.4 − Find Unadjusted Use-Case Weight (UUCW) using
the following table −
Use-Case Use-Case Number of Product
Complexity Weight Use-Cases

Simple 5 NSUC 5 × NSUC

Average 10 NAUC 10 × NAUC

Complex 15 NCUC 15 × NCUC

Unadjusted Use-Case Weight (UUCW) 5 × NSUC + 10 × NAUC + 15 ×

NCUC
Where,
NSUC is the no. of Simple Use-Cases.
NAUC is the no. of Average Use-Cases.
NCUC is the no. of Complex Use-Cases.
Indian Institute of Management (IIM),Rohtak
 IIM Rohtak

Use Case point Method

Step 1.2 − Determine Unadjusted Actor Weight.
Step 1.2.1 − Classify Actors as Simple, Average and Complex and
assign Actor Weights as shown in the following table −
Actor Complexity Example Actor Weight
Simple A System with defined API 1
Average A System interacting 2
through a Protocol
Complex A User interacting through 3
GUI

Step 1.2.2 − Repeat for each Actor and get all the Actor Weights.
Unadjusted Actor Weight (UAW) is the sum of all the Actor Weights.

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Use Case point Method

Step 1.2.3 − Find Unadjusted Actor Weight (UAW)
using the following table −
Actor Actor Weight Number of Product
Complexity Actors
Simple 1 NSA 1 × NSA
Average 2 NAA 2 × NAA
Complex 3 NCA 3 × NCA
Unadjusted Actor Weight (UAW) 1 × NSA + 2 × NAA + 3 × NC

Where,
NSA is the no. of Simple Actors.
NAA is the no. of Average Actors.
NCA is the no. of Complex Actors.

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Use Case point Method

Step 1.3 − Calculate Unadjusted Use-Case Points.

The Unadjusted Use-Case Weight (UUCW) and the Unadjusted

Actor Weight (UAW) together give the unadjusted size of the
system, referred to as Unadjusted Use-Case Points.

Unadjusted Use-Case Points (UUCP) = UUCW + UAW

The next steps are to adjust the Unadjusted Use-Case Points (UUCP)
for Technical Complexity and Environmental Complexity.

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Use Case point Method

Step 2: Adjust For Technical Complexity
Step 2.1 − Consider the 13 Factors that contribute to the impact of the
Technical Complexity of a project on Use-Case Points and their
corresponding Weights as given in the following table −
Technical Factor Description Weight
T1 Distributed System 2
T2 Performance 1
T3 End User Efficiency 1
T4 Complex Internal
Processing 1
T5 Reusability 1
T6 Installability 0.5
T7 Usability 0.5
T8 Portability 2
T9 Modifiability 1
T10 Concurrency 1
T11 Includes special security
requirements 1
T12 Provides direct access by
third parties 1
T13 Special User training
facilities are required 1
Indian Institute of Management (IIM),Rohtak
 IIM Rohtak

Technical Complexity Factor

Rate each factor on a scale of 0 to 5.
0 1 2 3 4 5

No Incidental Moderate Average Significant Essential

Influence

Step 2.2 − For each of the 13 Factors, assess the project and rate
from 0 (irrelevant) to 5 (very important).

Step 2.3 − Calculate the Impact of the Factor from Impact Weight of
the Factor and the Rated Value for the project as

Impact of the Factor = Impact Weight × Rated Value

Step (2.4) − Calculate the sum of Impact of all the Factors. This
gives the Total Technical Factor (TFactor) as given in table below
− next slide
Indian Institute of Management (IIM),Rohtak
 IIM Rohtak

Use Case point Method

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Use Case point Method

Step 3: Adjust For Environmental Complexity
Step 3.1 − Consider the 8 Environmental Factors that could affect the
project execution and their corresponding Weights as given in the
following table −
actor Description Weight
F1 Familiar with the project 1.5
model that is used
F2 Application experience .5
F3 Object-oriented 1.0
experience
F4 Lead analyst capability .5
F5 Motivation 1.0
F6 Stable requirements 2.0
F7 Part-time staff -1.0
F8 Difficult programming -1.0
language
Indian Institute of Management (IIM),Rohtak
 IIM Rohtak

Use Case point Method

Step 3.2 − For each of the 8 Factors, assess the project and rate
from 0 (irrelevant) to 5 (very important).

Step 3.3 − Calculate the Impact of the Factor from Impact Weight
of the Factor and the Rated Value for the project as

Impact of the Factor = Impact Weight × Rated Value

Step 3.4 − Calculate the sum of Impact of all the Factors. This gives
the Total Environment Factor (EFactor) as given in the following
table −

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Use Case point Method

Factor Description Weight (W) Rated Value (0 Impact (I = W ×
to 5) (RV) RV)
F1 Familiar with 1.5
the project
model that is
used
F2 Application .5
experience
F3 Object-oriented 1.0
experience
F4 Lead analyst .5
capability
F5 Motivation 1.0
F6 Stable 2.0
requirements
F7 Part-time staff -1.0
F8 Difficult -1.0
programming
language
Total Environment Factor (EFactor)
Indian Institute of Management (IIM),Rohtak
 IIM Rohtak

Use Case point Method

Step 3.5 − Calculate the Environmental Factor (EF) as −
1.4 + (-0.03 × EFactor)

Step 4: Calculate Adjusted Use-Case Points (UCP)

Calculate Adjusted Use-Case Points (UCP) as −

UCP = UUCP × TCF × EF
Effort =UCP *NO OF HOURS

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Use Case point Method

Advantages of Use-Case Points

• UCPs are based on use cases and can be measured very early in
the project life cycle.
• UCP (size estimate) will be independent of the size, skill, and
experience of the team that implements the project.
• UCP based estimates are found to be close to actuals when
estimation is performed by experienced people.
• UCP is easy to use and does not call for additional analysis.
• Use cases are being used vastly as a method of choice to describe
requirements. In such cases, UCP is the best suitable estimation
technique.

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Use Case point Method

Disadvantages of Use-Case Points
• UCP can be used only when requirements are written in
the form of use cases.
• Dependent on goal-oriented, well-written use cases. If
the use cases are not well or uniformly structured, the
resulting UCP may not be accurate.
• Technical and environmental factors have a high impact
on UCP. Care needs to be taken while assigning values
to the technical and environmental factors.
• UCP is useful for initial estimate of overall project size
but they are much less useful in driving the iteration-to-
iteration work of a team.

Indian Institute of Management (IIM),Rohtak

 IIM Rohtak

Thank you !!!

Indian Institute of Management (IIM),Rohtak