Scribd Logo
Upload

Welcome to Scribd!

    • 887 views

    Putnam Model

    Uploaded by

    Nitin Dalvi
    The Putnam model is an empirical software effort estimation model created by Lawrence Putnam Sr. It describes the time and effort required to complete a software project of a specified size. As an empirical model, it collects data on past software projects, including size, effort, and time to fit an equation to estimate future project effort based on size. A key feature is that total effort decreases as time to complete the project is extended. Process productivity is a scaling factor that represents an organization's ability to produce software at a given defect rate.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd

    Putnam Model

    Uploaded by

    Nitin Dalvi
    887 views2 pages
    The Putnam model is an empirical software effort estimation model created by Lawrence Putnam Sr. It describes the time and effort required to complete a software project of a specified size. As an empirical model, it collects data on past software projects, including size, effort, and time to fit an equation to estimate future project effort based on size. A key feature is that total effort decreases as time to complete the project is extended. Process productivity is a scaling factor that represents an organization's ability to produce software at a given defect rate.

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The Putnam model is an empirical software effort estimation model created by Lawrence Putnam Sr. It describes the time and effort required to complete a software project of a specified size. As an empirical model, it collects data on past software projects, including size, effort, and time to fit an equation to estimate future project effort based on size. A key feature is that total effort decreases as time to complete the project is extended. Process productivity is a scaling factor that represents an organization's ability to produce software at a given defect rate.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    887 views2 pages

    Putnam Model

    Uploaded by

    Nitin Dalvi
    The Putnam model is an empirical software effort estimation model created by Lawrence Putnam Sr. It describes the time and effort required to complete a software project of a specified size. As an empirical model, it collects data on past software projects, including size, effort, and time to fit an equation to estimate future project effort based on size. A key feature is that total effort decreases as time to complete the project is extended. Process productivity is a scaling factor that represents an organization's ability to produce software at a given defect rate.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    of 2

    Putnam model

    (Consider as a additional material for Putnam’s model)

    The Putnam model is an empirical software effort estimation model The original paper
    by Lawrence H. Putnam published in 1978 is seen as pioneering work in the field
    software process modeling. As a group, empirical models work by collecting software
    project data (for example, effort and size) and fitting a curve to the data. Future effort
    estimates are made by providing size and calculating the associated effort using the
    equation which fit the original data (usually with some error).

    Created by Lawrence Putnam, Sr. the Putnam model describes the time and effort
    required to finish a software project of specified size. SLIM (Software Lifecycle
    Management) is the name given by Putnam to the proprietary suite of tools his company
    QSM, Inc. has developed based on his model. It is one of the earliest of these types of
    models developed, and is among the most widely used. Closely related software
    parametric models are Constructive Cost Model (COCOMO), Parametric Review of
    Information for Costing and Evaluation – Software (PRICE-S), and Software Evaluation
    and Estimation of Resources – Software Estimating Model (SEER-SEM).

    The Software Equation


    While R&D projects for the Army and later at GE, Putnam noticed software staffing
    profiles followed the well-known Rayleigh distribution.

    Putnam used his observations about productivity levels to derive the software equation:

    where:

    • Size is the product size (whatever size estimate is used by your organization is
    appropriate). Putnam uses ESLOC (Effective Source Lines of Code) throughout
    his books.
    • B is a scaling factor and is a function of the project size.
    • Productivity is the Process Productivity, the ability of a particular software
    organization to produce software of a given size at a particular defect rate.
    • Effort is the total effort applied to the project in person-years.
    • Time is the total schedule of the project in years.

    In practical use, when making an estimate for a software task the software equation is
    solved for effort:

    An estimated software size at project completion and organizational process productivity


    is used. Plotting effort as a function of time yields the Time-Effort Curve. The points
    along the curve represent the estimated total effort to complete the project at some time.
    One of the distinguishing features of the Putnam model is that total effort decreases as the
    time to complete the project is extended. This is normally represented in other parametric
    models with a schedule relaxation parameter.

    This estimating method is fairly sensitive to uncertainty in both size and process
    productivity. Putnam advocates obtaining process productivity by calibration:

    Putnam makes a sharp distinction between 'conventional productivity’: size / effort and
    process productivity.

    One of the key advantages to this model is the simplicity with which it is calibrated. Most
    software organizations, regardless of maturity level can easily collect size, effort and
    duration (time) for past projects. Process Productivity, being exponential in nature is
    typically converted to a linear productivity index an organization can use to track their
    own changes in productivity and apply in future effort estimates.

    You might also like