← Portal CONCEPT 04 Effort Estimation: FPA & COCOMO
01 / 05 • 00:00
4.1 Foundations of Software Estimation (DCAP Unit 6)

Why Estimation is a "Black Art"

3 ESTIMATION PHASESEQF
  • Phase 1 (Initial Estimate): First-cut sizing (SWAG — Scientific Wild-Ass Guess) refined via WBS.
  • Phase 2 (Track EQF): Track Estimate-to-Quantity Factor against actual progress.
  • Phase 3 (Manage Concerns): Use EQF variance early to negotiate scope, schedule, or cost.
HIDDEN OVERHEADGRANULARITY
  • Never estimate coding alone! Also estimate:
  • 1. Project Management Effort
  • 2. Documentation Effort (SRS, User Manuals)
  • 3. Reviews & Inspections
  • 4. Configuration Management & Releases
ESTIMATION FAILURESLAWS
  • Under-Estimating: Infeasible plans, missed deadlines, rushed testing → Weinberg's Zeroth Law (low reliability).
  • Over-Estimating: Wastes budget & stretches timeline via Parkinson's Law.
  • Pricing-to-Win (Sommerville): Bid price is adjusted to win contracts, then scope is trimmed to fit.
4.2 Albrecht Function Point Analysis (FPA)

Function Point Components & Weights

Code Albrecht Component Simple Average Complex What Counts
EI (A) External Inputs 3 4 6 User forms / data screens entering system & updating ILFs
EO (B) External Outputs 4 5 7 Reports, derived data, screens leaving the app boundary
EQ (C) External Inquiries 3 4 6 Interactive input+output retrieval (no derived data, no ILF update)
ILF (D) Internal Logical Files 7 10 15 Logically related permanent data maintained inside app boundary
EIF (E) External Interface Files 5 7 10 Reference data maintained outside app (another app's ILF)

Step 1: Unadjusted Function Count (UFC / UAF)

Multiply each component count by its complexity weight (Simple / Average / Complex) and sum across all 5 categories. Rated via Data Element Types (DETs) and File Types Referenced (FTRs).

FP = UAF × VAF
4.3 Value Adjustment Factor & Mark II FPA

14 System Characteristics & Mark II

14 GENERAL SYSTEM CHARACTERISTICS (0–5)

Each rated 0 (irrelevant) to 5 (essential) to compute the Value Adjustment Factor (VAF):

1. Backup & recovery • 2. Data communications • 3. Distributed functions • 4. High performance • 5. Heavily used config • 6. On-line data entry • 7. End-user efficiency (easy to use)

8. On-line update • 9. Complex UI • 10. Complex processing • 11. Reusability • 12. Ease of installation • 13. Multiple sites • 14. Facilitate change

Rule of Thumb: 1 Function Point ≈ 2 Days Effort
MK II FUNCTION POINT ANALYSIS

Charles Symons (1991) — ISO/IEC 20968

Measures information-processing systems from an end-user functional view; maintained by UK Software Metrics Association (UKSMA).

Albrecht FPA vs. Mark II

Albrecht suits transaction/file boundaries well and is language-independent (unlike LOC), while Mark II focuses on logical transactions (Input + Processing + Output elements).

4.4 Barry Boehm's Constructive Cost Model

The COCOMO Estimation Model

EQUATION & LEVELSBOEHM
Effort = c × (Size)^k
Person-Months via KDSI
  • Basic COCOMO: Static single-variable using estimated KDSI (Delivered Source Instructions).
  • Intermediate: Adds 15 cost-driver multipliers (personnel, hardware, tool maturity).
  • Detailed: Applies cost drivers per phase (Analysis, Design, Code) & hierarchy level.
3 PROJECT MODESCATEGORIES
  • 1. Organic Mode: Small, straightforward projects; experienced team; flexible requirements (e.g., internal data utility).
  • 2. Semi-Detached Mode: Medium size & complexity; mixed experience; mix of rigid & flexible reqs (e.g., transaction DB).
  • 3. Embedded Mode: Tight hardware, software & operational constraints (e.g., avionics, real-time robotics).
APPRAISALPROS & CONS
  • Strengths: Public domain, well-documented, supports development & maintenance effort + schedule estimates.
  • Weaknesses: Early KDSI size is hard to guess; LOC varies wildly by language expressivity & code reuse; subjective cost drivers.
Function Points can be converted into KDSI via language tables before applying COCOMO.
4.5 Trade-Offs & Revision Check

Estimation Trade-Offs

Extending Schedule Can Lower Overall Cost

Lengthening a deadline slightly lets a smaller, core team complete the work with fewer communication channels and lower coordination overhead—remember Brooks' Law!

KEY INSIGHT
REVIEW QUESTIONS
  • Why does sound effort estimation always start with a Work Breakdown Structure (WBS)?
  • Contrast LOC-based estimation (COCOMO) with functional sizing (Albrecht FPA).
  • Distinguish Organic, Semi-Detached, and Embedded projects with real examples.
NEXT MODULE
  • Once effort is estimated per WBS task, we sequence dependencies and calculate start/finish dates and critical paths.
  • Move to Concept 5 for Activity Planning, Network Diagrams, CPM & PERT!

Completed Concept 4: Effort Estimation

Next up: Gantt Charts, Dependencies (FS/SS/FF/SF), ES/EF/LS/LF, CPM, PERT & CCPM Buffers.

Next: Concept 5 (CPM & PERT) →