Information System

Management

A report on

Library Management
System
Software Cost
Estimation
Using COCOMO II Model

Submitted to
Dr. Abu Turab Alam
Course Instructor

Submitted by
M. Kamran Zubairy
Roll No.: 2005-3-21-4930
Library Management System
Software Cost Estimation using COCOMO II

MBA (Executive), IoBM

Date: 16 December, 2007

College of Business Management

Letter of Authorization
16 Dec 2007

Dear Reader

As a students of IoBM, I have been authorized by Dr. Abu Turab Alam to prepare a term report on
“Library Management System Software Cost Estimation using COCOMO II Model”. This report is an
integral part of our course ‘Information System Management’ to be submitted by 16 Dec, 07.

The report required an in-depth research to be conducted before compiling a detailed account of the
underlying knowledge. All attempts have been made to provide you with an informational report
detailing credible data and results to educate you on this subject.

Sincerely

M. Kamran Zubairy
Roll No: 2005-3-21-4930
Phone: 0333-214-3970

Information Management System (Fall Semester) Page 2 of 12

Institute of Business Management
Library Management System
Software Cost Estimation using COCOMO II

Letter of Transmittal
16 Dec 2007

Dr. Abu Turab Alam

Course Instructor
Institute of Business Management

Dear Dr. Alam

Please find enclosed a report on “Library Management System Software Cost Estimation using
COCOMO II Model” that you authorized me to prepare.

This report provides an understanding of estimating software cost using COCOMO II model.
Application composition model of COCOMO II has been used for this purpose. IEEE 830 SRS for the
same software was provided by you to extract object points from.

If there be any clarification demanded, I would appreciate a call on the contact number given below.

Sincerely

M. Kamran Zubairy
Roll No: 2005-3-21-4930
Phone: 0333-214-3970

Information Management System (Fall Semester) Page 3 of 12

Institute of Business Management
Library Management System
Software Cost Estimation using COCOMO II

Contents
Letter of Authorization........................................................................................................................2

Letter of Transmittal............................................................................................................................3

Contents...............................................................................................................................................4

Introduction.........................................................................................................................................5

Introduction to COCOMO II Model.....................................................................................................5

COCOMO II Sub-models...................................................................................................................6

Object Points in Application Composition Model................................................................................6

Steps to calculate Efforts using Application Composition Model........................................................6

Screens..............................................................................................................................................7

Reports..............................................................................................................................................7

Modules.............................................................................................................................................8

Total Weighted Object Points............................................................................................................8

Productivity Level...............................................................................................................................9

Reuse................................................................................................................................................9

Effort..................................................................................................................................................9

Total Software Cost Calculation......................................................................................................10

Cost Drivers.....................................................................................................................................10

Software Cost..................................................................................................................................10

Total Cost Grid.................................................................................................................................10

Project Duration and Staffing...........................................................................................................12

Exponential Value (B)......................................................................................................................12

Sources............................................................................................................................................12

Information Management System (Fall Semester) Page 4 of 12

Institute of Business Management
Library Management System
Software Cost Estimation using COCOMO II

Introduction
This report is part of the course of Information System Management, which shows the usage and
importance of SRS to the management and its team and moreover explains how to estimate the cost
of such products. As future managers it is very important for us to learn how to estimate the cost of
software products.

 The main objective of this report is to estimate the cost of the software with the help of cost
estimation modules.

 A library management system software requirement specification is taken in order to estimate

the cost of system

 To understand the art and science of software cost estimation techniques, which as a future
manager would be helpful for us in making educated decisions

Introduction to COCOMO II Model

 COCOMO II allow for spiral development model instead of waterfall model only

 Use Function Points, Object Points and LOC for Sizing

 COCOMO II includes same activities as COCOMO 81

o development activities are included: documentation, planning & control, software

configuration management (CM)

o excluded: database management, general CM, Management

 COCOMO II has add-on effort for back-end Transition Phase (conversion, installation,
training)

Information Management System (Fall Semester) Page 5 of 12

Institute of Business Management
Library Management System
Software Cost Estimation using COCOMO II

COCOMO II Sub-models
There are following three sub-models in COCOMO II:

 Application Composition Mode : prototyping, use of existing components, based on

“Object Points”

 Early Design Model : architectural design stage, closest to original COCOMO, uses
Function Points as Size estimation

 Post-Architecture Model :For actual development stage & Maintenance; Uses FPs or
SLOC as size measure; Most detailed COCOMO II model

Object Points in Application Composition Model

Object Point estimation is a relatively new software sizing approach, but it is well-matched to the
practices in the Applications Composition sector. It is also a good match to associated prototyping
efforts, based on the use of a rapid-composition Integrated Computer Aided Software Environment
(ICASE) providing graphic user interface builders, software development tools, and large, composable
infrastructure and applications components. In these areas, it has compared well to Function Point
estimation on a nontrivial (but still limited) set of applications.

Following are some of the highlights of objection point model:

 Object points are alternative measure to function points when similar languages are used for
development.

 Object points are easier to estimate from a specification rather than function points, as they
are simply concerned with screens, reports, and programming language modules.

 They can therefore be estimated at a fairly early point in the development process.

 The number of object points in a program is weighted estimate of:

o The number of separate screens that are displayed.

o The number of reports that are produced by the system

o The number of program modules that must be developed to supplement the database
code.

Steps to calculate Efforts using Application Composition Model

1. Assess Application Counts: estimate the number of screens, reports and 3GL components

2. Classify each element instance to simple, medium and difficult complexity levels

3. Weigh the number in each cell. The weights reflect the relative effort required to implement
an instance of that complexity level

Information Management System (Fall Semester) Page 6 of 12

Institute of Business Management
Library Management System
Software Cost Estimation using COCOMO II

4. Determine Application Points = add all the weights to get 1 number, the Application Point
Count

5. Estimate the percentage of reuse & compute the New Application Points (NAP) to be
developed

6. Determine a productivity rate

7. Compute the estimated person-months

Screens
The complexity of the screens can be judged by the following:

 Simple Screen counts as 1 Object Point.

 Moderately Complex Screen counts as 2 Object Points.
 Highly Complex Screens counts as 3 Object Points.

The number of separate screens that are displayed in the system are as follows:

Object Section Simple Medium Complex

Count Wt Total Count Wt Total Count Wt Total
. . .
Library user account manage system 2 1 2
Book borrowing system 2 1 2 1 2 2 1 3 3
Book recall system 1 2 2 1 3 3
Search book record 2 2 4
Subtotal 4 8 6
Total 18

Reports
The complexity of the report generation can be judged by the following:

 Simple Report counts as 2 Object Point.

 Moderately Complex Reports counts as 5 Object Points.
 Highly Complex Reports counts as 8 Object Points.

The number of separate reports that are generated by the system are as follows:

Object Section Simple Medium Complex

Count Wt Total Count Wt Total Count Wt Total
. . .
Sign out books report 1 8 8
Overdue books and penalty report 1 5 5
Patron report 1 5 5
Book purchase report 1 8 8
Report printing and export 1 8 8
Subtotal 10 24
Total 34

Information Management System (Fall Semester) Page 7 of 12

Institute of Business Management
Library Management System
Software Cost Estimation using COCOMO II

Modules
Modules are imperative programming language code that must be developed to supplement the
database access and decision logic blocks.

The number of separate modules that are required by the system are as follows:

Object Section Simple Medium Difficult

Count Wt Total Count Wt Total Count Wt Total
. . .
Data Entry 2 2 4 1 5 5 1 10 10
Library user account manage system 1 2 2 1 5 5 1 10 10
Book borrowing system 4 2 8 3 5 15 1 10 10
Book recall system 1 2 2 1 5 5 1 10 10
Search book record 1 2 2 1 5 5 1 10 10
Update book database 2 5 10
Subtotal 18 45 50
Total 113

Total Weighted Object Points

Screens Reports Modules Total
Simple 4 18 22
Medium 8 10 45 63
Difficult 6 24 50 80
Total 18 34 113 165

Total Number of Screens + Total Number of Reports Generated + Total Modules Used by the
System

=> 18 + 34 + 113
=> 165 –> Total Weighted Object Points (NAP)

Information Management System (Fall Semester) Page 8 of 12

Institute of Business Management
Library Management System
Software Cost Estimation using COCOMO II

Productivity Level
The table has been generated to show the levels of object point productivity.

OBJECT POINT PRODUCTIVITY

Developer's Experience and Capability Very Low Low Nominal High Very High
CASE Maturity and Capability Very Low Low Nominal High Very High
PROD (NOP/Month) 4 7 13 25 50

Reuse
- User account management module – 5% of the code
- Date entry via calendar – 2% of the code
- Total Reuse of code = 7%

Effort
PM = [NAP * (1 - % reuse/100)] / PROD

Where:

NAP = 165
Reuse% = 7%

Therefore:

=> [165 * (1 – 0.07)] / 25

=> 6.138 ~ 6 Person-Months

Information Management System (Fall Semester) Page 9 of 12

Institute of Business Management
Library Management System
Software Cost Estimation using COCOMO II

Total Software Cost Calculation

There are three components taken into account for calculating the Total Software Cost of the project,
which are as follows:

 The cost of the hardware for executing the system.

 The cost of the platform (computer plus software) to develop the system.
 The cost of the effort required to develop the system.

Cost Drivers
Cost Type Description Rating
Driver Very Low Normal High Very Extra
Low High High
RELY Product Required system reliability 0.75 0.88 1 1.15 1.39
CPLX Product Complexity of system modules 0.75 0.88 1 1.15 1.3 1.66
DOCU Product Extent of documentation required 0.89 0.95 1 1.06 1.13
TIME Computer Execution time constraint 1 1.11 1.31 1.67
ACAP Personnel Capability of project analysts 1.5 1.22 1 0.83 0.67
PCAP Personnel Programmer capability 1.37 1.16 1 0.87 0.74
PCON Personnel Personnel continuity 1.24 1.1 1 0.92 0.84
LTEX Personnel Language and tool experience 1.22 1.1 1 0.91 0.84
TOOL Project Use of software tools 1.24 1.12 1 0.86 0.72
SITE Project Extent of multi-site working 1.25 1.1 1 0.92 0.84 0.78

Software Cost
SC = Effort Estimate x RELY x CPLX x DOCU x TIME x ACAP x PCAP x PCON x LTEX x TOOL x
SITE x Rs. 100,000

=> 6.138 PM x 1.15 x 0.88 x 1.06 x 1.11 x 0.83 x 0.87 x 0.84 x 0.84 x 0.86 x 0.84 x Rs. 100,000
=> Rs. 269,010.9

* Estimated Average Cost of One Person-Month is Rs 100,000, which covers salaries and operational expenses
per person.

Total Cost Grid

Total Cost
Factor Description Value
RELY Required system reliability 1.15
CPLX Complexity of system modules 0.88
DOCU Extent of documentation required 1.06
TIME Execution time constraint 1.11
ACAP Capability of project analysts 0.83
PCAP Programmer capability 0.87
PCON Personnel continuity 0.84

Information Management System (Fall Semester) Page 10 of 12

Institute of Business Management
Library Management System
Software Cost Estimation using COCOMO II

LTEX Language and tool experience 0.84

TOOL Use of software tools 0.86
SITE Extent of multi-site working 0.84
Total Effort 6.14 PM
Software Cost Rs. 269,010
Hardware Cost Rs. 300,000
Total Cost Rs. 569,010

* Estimated Hardware Cost is Rs. 300,000 (assuming purchase of 10 PCs at the cost of Rs. 30,000 per PC.)

Information Management System (Fall Semester) Page 11 of 12

Institute of Business Management
Library Management System
Software Cost Estimation using COCOMO II

Project Duration and Staffing

The project managers also estimate how long the software will take to develop and when staff will be
needed to work on the project.

Through the COCOMO Model, the following formula is used to estimate the Calendar Time (TDEV)
that is required to complete the project:

TDEV = 3 x [PM ^ {0.33 + 0.2 * (B – 1.01)}]

* PM is the effort computation.

* B is the exponent.
* This computation predicts the nominal schedule for the project.

Exponential Value (B)

In COCOMO II, a continuous range of values is possible for exponent B. This exponent is based on
five scale factors (rated on a six-point scale from Very low (5) to Extra high (0)). The rating is then
added and divided by 100 and then added to 1.01 to get the exponent. Following are the scale factors
and their ratings as per the project of Library Management System:

Exponent Calculation
Exponent Factor Description Value
Precedentedness Required system reliability 3
Development
flexibility Complexity of system modules 1
Architecture/risk
resolution Extent of documentation required 5
Team cohesion Execution time constraint 2
Process maturity Use of software tools 2
Total Rating 13
Divide by 100 and Add to 1.01 1.14

Therefore, the Exponential Value would be:

Therefore:

TDEV = 3 x [6 ^ {0.33 + 0.2 * (1.14 – 1.01)}]

=> 5.68 ~ 6 Months

Thus, the project will take an estimated time of 6 months to be completed.

Sources
 http://yunus.hun.edu.tr/~sencer/objectp.html
 http://sern.ucalgary.ca/courses/seng/621/W98/johnsonk/cost.htm

Information Management System (Fall Semester) Page 12 of 12

Institute of Business Management