Putnam software cost estimation

Putnam estimation model Next Previous. B is a scaling factor and is a function of the project size. 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.

Your rating has been saved. Post your comment. Edit Show Details. Two of the well known software cost estimation methods are dis- cussed below:. The Putnam model is very sensitive to the development time: decreasing the development time can greatly increase the per- son-months needed for development. One significant problem with the PUTNAM model is that it is based on knowing, or being able to estimate accurately, the size in lines of code of the software to be developed.

There is often great uncertainty in the software size. It may result in the inaccuracy of cost estimation. For all the scale factors and effort multipliers we have taken average for all the parameters.

By calculating the final values which we got are. Both the Post-Architecture and Early Design models use the same functional from to estimate the amount of effort and ca- lendar time it will take to develop a software project. The amount of effort in person-months, PM, is estimated by the formula:. As a case study we have taken a project in consideration which was developed for an very US based client.

The project takes care calls and SMS details for a client. Please mail your requirement at [email protected] Duration: 1 week to 2 week.

Software Engineering. Coding Programming Style Structured Programming. Next Topic Risk Management. Reinforcement Learning. R Programming. React Native. Python Design Patterns. Python Pillow. Python Turtle. Verbal Ability. Interview Questions. Company Questions. Artificial Intelligence. Cloud Computing. Data Science.

Angular 7.