1 / 25

THE FAMU-CIS ALUMNI SYSTEM

Estimation. THE FAMU-CIS ALUMNI SYSTEM. TEAM ORANGE. CEN5055 Project Management Feb 23 rd 2009 Jamin Bao Martin Brown Sherene Campbell Saidi Mchumo Xian Long. Introduction. Tools used for estimation Function Points Units of measure based on functionality DVC

cianna
Download Presentation

THE FAMU-CIS ALUMNI SYSTEM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Estimation THE FAMU-CIS ALUMNI SYSTEM TEAM ORANGE CEN5055 Project Management Feb 23rd 2009 Jamin Bao Martin Brown Sherene Campbell Saidi Mchumo Xian Long

  2. Introduction • 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

  3. Proposed SSS Matrix • 21 Data Tables • 11 Forms • 7 Reports • Proposed Matrix

  4. LINES OF CODE (SLOC) 9640 10410

  5. 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.

  6. 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.

  7. Calculating Function Points • Calculate unadjusted Function Count (FC) • Determine the Value Adjustment Factor (VAF) • Calculate Function Points

  8. 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)

  9. Calculate unadjusted function count (FC)

  10. Function Points for Alumni system Results

  11. 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)

  12. Data Volume Counter:::Data Dictionary

  13. DATA VOLUME COUNTER:::DATA DICTIONARY

  14. DATA VOLUME COUNTER:::DATA DICTIONARY

  15. DATA VOLUME COUNTER:::OVERVIEW • Needs • Data Dictionary • Purpose • To calculate the input data volume

  16. DATA VOLUME COUNTER:::RESULTS (FROM XIAN LONG) DVC = 146 vs. function point 256

  17. DATA VOLUME COUNTER:::RESULTS (FROM MARTIN) DVC = 161 vs. function point 256

  18. 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.

  19. 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.

  20. 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.

  21. Cocomo II ::: Scale Factors (B)

  22. Cocomo II ::: Effort Adjustment Factor(M)

  23. Cocomo II ::: Results • results

  24. Conclusion

  25. Questions ?

More Related