Estimation
THE FAMU-CIS ALUMNI SYSTEM
CEN5055
Project Management
Feb 23rd 2009
TEAM ORANGE
Jamin Bao
Martin Brown
Sherene Campbell
Saidi Mchumo
Xian Long
INTRODUCTION

Tools used for estimation

Function Points


DVC


Units of measure based on functionality
The amount of data going through the system
Cocomo “COnstructive COst MOdel”
model for estimating effort, cost, and schedule for software projects
 Developed 1981


Cocomo II
Same as Cocomo but for newer/more modern practices
 Developed 1997 – published in 2001

PROPOSED SSS MATRIX
21 Data Tables
 11 Forms
 7 Reports
 Proposed Matrix

LINES OF CODE (SLOC)
Team Member
Lower Bound
Expected
Upper Bound
Jiamin Bao
7900
8600
9100
Martin Brown
4340
6507
10143
Sherene Campbell
3530
4515
6125
Saidi Mchumo
9640
10850
Xian Long
8530
9850
10410
12020
Average
6830
7934
9647
FUNCTION POINTS:::OVERVIEW
What is a Function Point?
 A standard unit of measure that represent the
functional size of a software application.
 An application can be measured by the number of
function points it delivers to the users of the
application.
A SIMPLE SIX STEP COUNTING
PROCESS
Identify all instances of each function type in the
system.
 Assign a complexity weight to each instance of a
function type.
 Calculate a weighted sum for each function type.
 Determine the unadjusted function count (FC).
 Determine the Value Adjustment Factor (VAF).
 Calculate FP Count.

CALCULATING FUNCTION POINTS

Calculate unadjusted Function Count (FC)

Determine the Value Adjustment Factor (VAF)

Calculate Function Points
IDENTIFY FIVE STANDARD “FUNCTION
TYPES” AND COMPLEXITY WEIGHT

Data Functions:
Internal logical files (ILFs)
 External interface files (EIFs)


Transactional Functions:
External Inputs (EIs)
 External Outputs (EOs)
 External Inquiries (EIs)

CALCULATE UNADJUSTED FUNCTION
COUNT (FC)
FUNCTION POINTS FOR ALUMNI SYSTEM
RESULTS
LINES OF CODE (SLOC) ESTIMATE
FROM FUNCTION POINTS
Past date indicate that one FP translate into 25
times of code
LOCs = 25 * 256
=6400 (approximately)
Factor
25
45
60
SLOC
6400
11520
15360
DATA VOLUME COUNTER:::DATA DICTIONARY
DATA VOLUME COUNTER:::DATA
DICTIONARY
DATA VOLUME COUNTER:::DATA
DICTIONARY
DATA VOLUME
COUNTER:::OVERVIEW

Needs


Data Dictionary
Purpose

To calculate the input data volume
DATA VOLUME COUNTER:::RESULTS
(FROM XIAN LONG)
DVC = 146 vs. function point 256
DATA VOLUME COUNTER:::RESULTS
(FROM MARTIN)
DVC = 161 vs. function point 256
COCOMO II ::: OVERVIEW
To develop a software cost and schedule
estimation model tuned to the life cycle practices
of the 1990's and 2000's.
 To develop software cost database and tool
support
 To provide a set of tools and techniques for
evaluating the effects of software technology
improvements on software life cycle costs and
schedules.

COCOMO II:::MODELS
The Post-Architecture Model
 Most detailed COCOMO 2 model.
 Used after you've developed your project's overall architecture.
 It has new cost drivers, new line counting rules & new equations.

The Early Design Model
 Get rough estimates of a project's cost and duration before you've
determined it's entire architecture.
 It uses a small set of new Cost Drivers, and new estimating
equations. Based on Unadjusted Function Points or KSLOC.


Application composition model
• Used when software is composed from existing parts.

Reuse model
• Used to compute the effort of integrating reusable components.
COCOMO II:::EARLY DESIGN MODEL
Estimates can be made after the requirements have
been done
 Based on a standard formula for algorithmic models


Effort (person-months) = A  SizeB  M where
M = PERS  RCPX  RUSE  PDIF  PREX  FCIL 
SCED;
 A = 2.94 in initial calibration
 Size in KLOC
 B varies from 1.1 to 1.24 depending on novelty of the
project, development flexibility, risk management
approaches and the process maturity.

COCOMO II ::: SCALE FACTORS (B)
COCOMO II ::: EFFORT ADJUSTMENT FACTOR(M)
EM
RCPX
RUSE
PDIF
PERS
PREX
FCIL
Name
Product Reliability and Complexity
Developed for Reusability
Platform Difficulty
Personnel Capability and Mapping Example
Personnel Experience
Facilites
COCOMO II ::: RESULTS

results
CONCLUSION
Function Points
Team
DVC
Value: 256
SLOC: 11520
SLOC: 7934
(average)
Martin: 161
Xian: 145
Cocomo I
Cocomo II
Effort: 21 (Likely)
Effort: 28.7 (Likely)
Cost:
Student: $50,399
OutSource: $210,000
Cost:
Student: $68,885
OutSource:$287,022.62
QUESTIONS