Putnam model Wikipedia. The Putnam model is an empirical software effort estimation model. The original paper by Lawrence H. Putnam published in 1. 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. Staffing Level Estimation In Software Engineering' title='Staffing Level Estimation In Software Engineering' />Background It is uncertain whether lower levels of staffing by nurses at hospitals are associated with an increased risk that patients will have complications or die. Project Planning PP A Project Management Process Area at Maturity Level 2 Purpose The purpose of Project Planning PP is to establish and maintain plans that. To perform testing in a planned and systematic manner, software testing strategy is developed. A testing strategy is used to identify the levels of testing which are. Product-oriented_work_breakdown_structure_of_an_aircraft_system.png/800px-Product-oriented_work_breakdown_structure_of_an_aircraft_system.png' alt='Staffing Level Estimation In Software Engineering' title='Staffing Level Estimation In Software Engineering' />Created by Lawrence Putnam, Sr. 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. 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 EquationeditWhile managing 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 B13Size. ProductivityEffort. Time. 43displaystyle frac B13cdot textrm Sizetextrm Productivitytextrm Effort13cdot textrm Time43where 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 personyears. 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 EffortSize. Toshiba Satellite A660 Bluetooth Driver. ProductivityTime. Bdisplaystyle textrm Effortleftfrac textrm Sizetextrm Productivitycdot textrm Time43right3cdot BAn 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 1Process ProductivitySizeEffort. B13Time. 43displaystyle textrm Process Productivityfrac textrm Sizeleftfrac textrm EffortBright13cdot textrm Time43Putnam 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. See alsoeditReferencesedit ab. Putnam, Lawrence H. Ware Myers September 2. Chopper Sound Effects'>Chopper Sound Effects. Five core metrics  the intelligence behind successful software management. Dorset House Publishing. ISBN 0 9. 32. 63. Putnam, Lawrence H. A General Empirical Solution to the Macro Software Sizing and Estimating Problem. IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. SE 4, NO. 4, pp 3. Focus on Lawrence Putnam  A CAI State of the Practice InterviewPDF. Computer Aid, Inc. September 2. 00. 6. US Government August 2. Putnam Special Skills Factor Table. Data Analysis Center for Software. Putnam, Lawrence H. Ware Myers October 1. Measures for Excellence  Reliable Software on Time, Within Budget. Prentice Hall. p. ISBN 9. 78 0 1. US Government August 2. Putnam Productivity Parameter Table. Data Analysis Center for Software. External linksedit.