greatworks

4.2 Project Schedule and Staffing. The staffing level is not changed continuously in a project. Planning process in Software engineering. Reply Delete. Estimation is the process of finding an estimate, or approximation, which is a value that can be used for some purpose even if input data may be incomplete, uncertain, or unstable. Estimation determines how much money, effort, resources, and time it will take to build a specific system or product.

1. What Is Project Estimation In Software Engineering

The Putnam model is an empirical software effort estimation model.^[1]The original paper by Lawrence H. Putnam published in 1978 is seen as pioneering work in the field of software process modelling.^[2]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 areConstructive Cost Model (COCOMO), Parametric Review of Information for Costing and Evaluation – Software (PRICE-S), andSoftware Evaluation and Estimation of Resources – Software Estimating Model (SEER-SEM).

The software equation[edit]

While managing R&D projects for the Army and later at GE, Putnam noticed software staffing profiles followedthe well-known Rayleigh distribution.^[3]

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

${\displaystyle \frac{B^{1/3}\cdot \text{Size}}{\text{Productivity}}={\text{Effort}}^{1/3}\cdot {\text{Time}}^{4/3}}$

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.^[4][5]
• 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:

${\displaystyle \text{Effort}={\left[\frac{\text{Size}}{\text{Productivity}\cdot {\text{Time}}^{4/3}}\right]}^3\cdot B}$

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:^[1]

${\displaystyle \text{Process Productivity}=\frac{\text{Size}}{{\left[\frac{\text{Effort}}{B}\right]}^{1/3}\cdot {\text{Time}}^{4/3}}}$

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.^[6]

What Is Project Estimation In Software Engineering

See also[edit]

References[edit]

1. ^ ^abPutnam, Lawrence H.; Ware Myers (September 2003). Five core metrics : the intelligence behind successful software management. Dorset House Publishing. ISBN0-932633-55-2.
2. ^Putnam, Lawrence H. (1978). 'A General Empirical Solution to the Macro Software Sizing and Estimating Problem'. IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. SE-4, NO. 4, pp 345-361.Missing or empty url= (help)
3. ^'Focus on Lawrence Putnam : A CAI State of the Practice Interview'(PDF). Computer Aid, Inc. September 2006.
4. ^US Government (August 20, 1997). 'Putnam Special Skills Factor Table'. Data & Analysis Center for Software.Missing or empty url= (help)
5. ^Putnam, Lawrence H.; Ware Myers (October 1991). Measures for Excellence : Reliable Software on Time, Within Budget. Prentice Hall. p. 234. ISBN978-0-13-567694-3.
6. ^US Government (August 20, 1997). 'Putnam Productivity Parameter Table'. Data & Analysis Center for Software.Missing or empty url= (help)

External links[edit]

• Putnam, Lawrence H.; Ware Myers (October 1991). Measures for excellence : reliable software On time, within budget. Yourdon Press. ISBN0-13-567694-0.
• Jensen, Dr. Randall W.; Putnam, Lawrence H., Sr.; Roetzheim, William (February 2006). 'Software Estimating Models: Three Viewpoints'(PDF). Software Technology Support Center.
• Jones, Capers (October 2004). 'Software Project Management Practices: Failure Versus Success'(PDF). Software Technology Support Center.
• US Government (October 2005). 'FAA Pricing Handbook'. Federal Aviation Administration.

• Kemerer, Chris F. (May 1987). 'An Empirical Validation of Software Cost Estimation Models'(PDF). Communications of the ACM.