Project size is easily the most significant determinant of effort. From lines of code, to function points, to similar projects, to industry estimates. Home page for steve mcconnell, author of code complete, rapid development, software estimation, and several other best selling software books. Steve mcconnell on software estimation ryan kienstra. Often referred to as the black art because of its complexity and uncertainty, software estimation is not as difficult or puzzling as people think. If you havent read it, pick up a copy and work your way through it. Software estimation by steve mcconnell provides a very broad overview of. Software estimation in depth construx software youtube. Software estimation by steve mcconnell and agile estimating and planning by mike cohn. Demystifying the black art by steve mcconnell get software estimation. Like all of mr mcconnells books, he provides crystal clear writing with tons of techniques that are ready for application in the real world. Agilier is an experienced it change management consultancy, providing.
The mythical book, mythical man month quoted that no matter the programming language chosen, a professional developer will write in average 10 lines of code loc day. Software estimation by steve mcconnell provides a very broad overview of many ways to reduce the software estimation errors for your development cycle. Mcconnell published his first book, code complete, in 1993. Demystifying the black art, steve mcconnell explains. Steve mcconnell, construx instructor, teaching estimation in depth seminar. Mcconnell, steve, rapid development,microsoft press,1996 presents all the factor to. Gauging software readiness with defect tracking steve. Estimate the size of the product number of lines of code or function points. Software estimation introduction kariera future processing.
Because different programming languages produce such different bangs for a given number of lines of code, much of the software. Software estimation in this highly anticipated book, acclaimed author steve mcconnell unravels the mystery to successful. Effort per line of code is more a function of project size and kind of software. Techniques for more accurate and transparent estimates, from steve mcconnells book software estimation. Software development every programmer should read this outstanding. As a practitioner of the agile arts i must say in reading it now this book seems like the last great attempt to. He is chief software engineer of construx software and was the lead developer of construx estimate. Steve mcconnell is chief software engineer at construx soft. Estimation by analogy compute a size estimate based on a piecebypiece count of analogous elements, and the past sizes of those elements. Software estimation quotes by steve mcconnell goodreads. Find, read and cite all the research you need on researchgate. For majority of people its all black magic and a shot from nowhere.
Diseconomies of scale and lines of code coding horror. Software estimation is difficult, and what some people try to do with software estimation isnt even theoretically possible. When executives ask for an estimate, theyre often asking for a commitment or for a plan to meet a target. Picture 1 model the cone of uncertainty from steve mcconnells software estimation. Published over 6 years ago software estimation by steve mcconnell is a great read. At boeing, he worked on a strategic defense initiative project. Steve mcconnell shares some common software estimation mistakes. Adapted from charles simons, software sizing and estimating. Steve mcconnell on diseconomies of scale in software development.
Steve mcconnell is recognized as one of the premier authors and voices in the development community. Steve mcconnell in rapid development microsoft press, 1996. Estimation often doesnt work very well, therefore software professionals should not develop estimation skill this is a common line of. Software estimation is one of those skills that programmers usually avoid and dont really care for. Contrary to intuition, the number of errors per lines of does seem to be relatively constant, reguardless of the specific language involved. Software estimation demystifying the black art by steve mcconnell. Demystifying the black art how inaccurate is a ballpark estimate. In fact, generating accurate estimates is straightforwardonce you understand the art of creating them.
In fact, generating accurate estimates is straightforwardonce. Demystifying the black art is a fabulous resource for software projects. Learn many useful rules of thumb and procedures for creating software estimates. Flow of software estimates on a wellestimated project. Putman and myers 1992 to convert a lines of code estimate into an effort. One of the many great things about software estimation is the sheer number of methods he gives. The software therefore had a lifetime defect count of 700 defects, and a defect density of 7 defects per thousand lines of code kloc. Gauging software readiness with defect tracking in the competitive commercial software market, software companies feel compelled to release software the moment it is ready. In his highly anticipated book, acclaimed author steve mcconnell unravels the mystery. Demystifying the black art now with oreilly online learning. The only way to reduce the variability in the estimate is to reduce the variability in th.
The primary purpose of software estimation is not to predict a projects outcome. I always enjoy books by steve mcconnell, and his software estimation. Steve mcconnell, 10900 ne 8th st, ste 50, bellevue, wa. Programmers working with highlevel languages achieve better productivity and quality than those working with lowerlevel languages. Software estimation with steve mcconnell ryan ripley. Before using loc as silver bullet i suggest you to come back to the. In his highly anticipated book, acclaimed author steve mcconnell unravels the mystery to successful software estimationdistilling academic information and. Demystifying the black art is as readable as all of his other works. The basic software estimation story is a process of gradual refinement. From lines of code, to function points, to similar projects, to industry estimates broken.
256 135 1145 1294 1029 1121 629 1277 846 666 63 854 1150 868 332 98 1261 88 652 68 712 237 236 981 1418 150 82