THE FAMU-CIS ALUMNI SYSTEM

THE FAMU-CIS ALUMNI SYSTEMTHE FAMU-CIS ALUMNI SYSTEM

CEN5055 Project Management

Feb 23rd 2009

Jamin Bao

Martin Brown

Sherene Campbell

Saidi Mchumo

Xian Long

EstimatioEstimationn

EstimatioEstimationn

TEAM ORANGETEAM ORANGE

INTRODUCTIONINTRODUCTION Tools used for estimation

Function Points Units of measure based on functionality

DVC 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)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 8530 10850

Xian Long 9850 12020

Average 6830

7934

9647

10410

9640

FUNCTION POINTSFUNCTION POINTS:::OVERVIEW 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.

Calculate unadjusted Function Count (FC)

Determine the Value Adjustment Factor (VAF)

Calculate Function Points

CALCULATING FUNCTION POINTSCALCULATING 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 FUNCTION POINTS FOR ALUMNI SYSTEM RESULTSRESULTS

LINES OF CODE (SLOC) ESTIMATE LINES OF CODE (SLOC) ESTIMATE FROM FUNCTION POINTSFROM FUNCTION POINTS

Past date indicate that one FP translate into 25 times of code

LOCs = 25 * 256 =6400 (approximately)

Factor SLOC25 640045 1152060 15360

DATA VOLUME COUNTERDATA VOLUME COUNTER:::DATA DATA DICTIONARYDICTIONARY

DATA VOLUME COUNTERDATA VOLUME COUNTER:::DATA DATA DICTIONARYDICTIONARY

DATA VOLUME COUNTERDATA VOLUME COUNTER:::DATA DATA DICTIONARYDICTIONARY

DATA VOLUME COUNTERDATA VOLUME COUNTER:::OVERVIEW OVERVIEW

Needs Data Dictionary

Purpose To calculate the input data volume

DATA VOLUME COUNTERDATA VOLUME COUNTER:::RESULTS RESULTS (FROM XIAN LONG)(FROM XIAN LONG)

DVC = 146 vs. function point 256

DATA VOLUME COUNTERDATA VOLUME COUNTER:::RESULTS RESULTS (FROM MARTIN)(FROM MARTIN)

DVC = 161 vs. function point 256

COCOMO IICOCOMO II ::: OVERVIEW 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 IICOCOMO II:::MODELSMODELS 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 IICOCOMO II:::EARLY DESIGN MODELEARLY 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 COCOMO II ::: SCALE FACTORS (B)SCALE FACTORS (B)

COCOMO II COCOMO II ::: EFFORT ADJUSTMENT EFFORT ADJUSTMENT FACTOR(M)FACTOR(M)

EM NameRCPX Product Reliability and ComplexityRUSE Developed for ReusabilityPDIF Platform DifficultyPERS Personnel Capability and Mapping ExamplePREX Personnel ExperienceFCIL Facilites

COCOMO II COCOMO II ::: RESULTSRESULTS

results

CONCLUSIONCONCLUSION

Function Points Team DVC

Value: 256SLOC: 11520

SLOC: 7934 (average)

Martin: 161Xian: 145

Cocomo I Cocomo II

Effort: 21 (Likely) Effort: 28.7 (Likely)

Cost: Student: $50,399OutSource: $210,000

Cost:Student: $68,885OutSource:$287,022.62

QUESTIONSQUESTIONS

?