This blog focuses on explaining the Function Point calculations.
- Software Sizing Background
- Function Point
- Rules for Counting FP
- Deep Dive - Function Point Analysis
- Case Study
- General Software Characteristics Details
History - Measurement Methodologies
- Lines of Code (Oldest)
- Use case based Software Sizing
- IPFUG Function Point Analysis (ISO)
Need for Software Sizing.
- Estimation and Budgeting
- Phasing Development Work
- Prioritization of Work
- Monitoring the Progress
- Bidding for Projects
- Allocating Testing Resources
- To measure and Manage Productivity
- Risk Assessment
- Software Asset Valuation
- CMMi Level 2 and 3 require that a valid sizing method be used.
Software Sizing - Lines of Code
The easiest and historically the most common method in Sizing Software project has been counting the number of lines of code and / or the number of screens.
Automation of the counting process can be done
Intuitive as the measurements are easily understood
Lines of Code is language and the skill set of the developer
The coding phase is only around 30-35% of the actual software development.
Lack of counting standards (What about comments, notes etc.?)