Select Page

Effort and Cost Estimation Techniques

Effort and cost estimation techniques are essential in software project management to predict the amount of effort and financial resources required to complete a project. Accurate estimates help in planning, budgeting, and resource allocation.

Common Estimation Techniques:

  1. Expert Judgment:
    • Involves consulting with experienced individuals or teams who provide estimates based on their knowledge and past experiences.
    • Pros: Quick and leverages expertise.
    • Cons: Can be subjective and vary between experts.
  2. Analogous Estimation:
    • Uses data from similar past projects to estimate the current project.
    • Pros: Relatively simple and leverages historical data.
    • Cons: Relies on the similarity of past projects, which may not always be accurate.
  3. Parametric Estimation:
    • Utilizes mathematical models to estimate effort and cost based on project parameters, such as size, complexity, and team experience.
    • Pros: Can be highly accurate if the model is well-calibrated.
    • Cons: Requires detailed data and understanding of the model.
  4. Bottom-Up Estimation:
    • Breaks the project into smaller tasks, estimates each task individually, and sums these estimates.
    • Pros: Detailed and can be very accurate.
    • Cons: Time-consuming and requires detailed task breakdown.
  5. Top-Down Estimation:
    • Estimates the overall project effort and cost, then breaks it down into smaller components.
    • Pros: Quick and useful in the early stages of project planning.
    • Cons: Less detailed and can be less accurate.
  6. Three-Point Estimation:
    • Uses three estimates (optimistic, pessimistic, and most likely) to calculate an average estimate.
    • Pros: Considers uncertainty and variability.
    • Cons: Requires more effort to derive three estimates.
  7. Wideband Delphi:
    • A group estimation technique where experts anonymously provide estimates, discuss discrepancies, and converge on a final estimate.
    • Pros: Combines multiple expert opinions and reduces bias.
    • Cons: Can be time-consuming.

COSMIC Full Function Points

COSMIC (Common Software Measurement International Consortium) Full Function Points is a method for measuring a software application’s functional size. It focuses on the functional user requirements that define what the software must do.

Key Features of COSMIC Full Function Points:

  1. Measurement Concepts:
    • Functional Processes: The smallest unit of functionality meaningful to the user.
    • Data Movements: Includes four types:
      • Entry (E): Data entering the system.
      • Exit (X): Data leaving the system.
      • Read (R): Data read from persistent storage.
      • Write (W): Data written to persistent storage.
  2. Measurement Process:
    • Identify Functional Processes: Determine the functional processes in the software.
    • Identify Data Movements: Identify and classify each data movement within functional processes.
    • Measurement: Assign COSMIC function points to each data movement.
  3. Applications:
    • Suitable for different types of software, including business applications, real-time systems, and embedded systems.
    • Used for effort estimation, benchmarking, and performance measurement.
  4. Advantages:
    • Provides a standardized, objective measure of software size.
    • Applicable across various types of software and development methodologies.
    • Supports early project estimation and scope management.

COCOMO II (Constructive Cost Model II)

COCOMO II is a parametric cost estimation model developed by Barry Boehm. It provides estimates of effort, time, and cost based on the size of the software and various project factors.

Key Features of COCOMO II:

  1. Estimation Formulas:
    • Effort: Measured in Person-Months (PM).

      Effort (PM)=𝐴×Size𝐵×𝑖=1𝑛EM𝑖


      • 𝐴


        = Constant scale factor.

      • 𝐵


        = Exponent derived from project attributes.

      • Size


        = Size of the software in KSLOC (thousands of source lines of code).

      • EM𝑖


        = Effort multipliers for various cost drivers.

  2. Cost Drivers:
    • Product Attributes: Complexity, reliability requirements, etc.
    • Hardware Attributes: Constraints imposed by the hardware.
    • Personnel Attributes: Experience, capabilities, etc.
    • Project Attributes: Development environment, tools, etc.
  3. Models within COCOMO II:
    • Application Composition Model: Used for projects using rapid application development (RAD) tools.
    • Early Design Model: Used in the early stages of design, when not much is known about the project.
    • Post-Architecture Model: Used after the system architecture has been defined.
  4. Advantages:
    • Provides detailed and flexible estimation based on a variety of factors.
    • Can be adjusted for different types of projects and environments.
    • Incorporates both size and productivity factors, offering a comprehensive estimation.

Parametric Productivity Model

A parametric productivity model uses statistical techniques to predict project effort and cost based on known parameters and historical data. These models establish relationships between variables to make estimations more objective and reliable.

Key Features of Parametric Productivity Models:

  1. Inputs:
    • Project size (e.g., function points, lines of code).
    • Complexity and technical attributes.
    • Team experience and productivity.
  2. Estimation Process:
    • Define relevant parameters for the project.
    • Collect historical data to understand how these parameters affect effort and cost.
    • Develop mathematical relationships (regression models) to predict effort and cost.
  3. Examples:
    • COCOMO II: A well-known parametric model.
    • SLIM (Software Life Cycle Management): Uses system dynamics modeling.
    • SEER-SEM (System Evaluation and Estimation of Resources – Software Estimation Model): Offers parametric-based estimation.
  4. Advantages:
    • Provides a systematic approach to estimation.
    • Can handle complex relationships between different project factors.
    • Reduces reliance on subjective judgment.

Effort and cost estimation techniques are vital for successful software project management. Techniques like COSMIC Full Function Points provide a standardized way to measure software size, while models like COCOMO II and parametric productivity models offer sophisticated methods to estimate effort and cost based on project-specific parameters. These tools and techniques enable project managers to plan, budget, and allocate resources effectively, ensuring project success and minimizing risks.