- Paperback: 767 pages
- Publisher: Prentice Hall; 1 edition (November 1, 1981)
- Language: English
- ISBN-10: 0138221227
- ISBN-13: 978-0138221225
- Product Dimensions: 6.9 x 1.8 x 9.1 inches
- Shipping Weight: 2.7 pounds (View shipping rates and policies)
- Average Customer Review: 7 customer reviews
Amazon Best Sellers Rank:
#849,537 in Books (See Top 100 in Books)
- #68 in Books > Engineering & Transportation > Engineering > Industrial, Manufacturing & Operational Systems > Economics
- #929 in Books > Textbooks > Computer Science > Software Design & Engineering
- #2024 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Software Development
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Software Engineering Economics 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
All Books, All the Time
Read author interviews, book reviews, editors picks, and more at the Amazon Book Review. Read it now
Frequently bought together
Customers who bought this item also bought
Discover books for all types of engineers, auto enthusiasts, and much more. Learn more
Top customer reviews
Personally I especially likes the Part III and Part IV which were about the factors changing the software estimate and the reasons why. The last chapter of the book is something everyone should read who is working in quality/process management and is trying to improve productivity of a large project.
Still a classic and worth reading!
HOWEVER, it must be kept in mind that the book itself is somewhat outdated - COCOMO 81, as defined by Barry Boehm, has been overtaken by new technologies and in particular by the surge in PCs & the Internet. The basic model is still valid - I still use it myself - provided you are aware what the background in computing was when it was written, and you carefully assign the adjustment factors.
Barry Boehm himself recognizes that COCOMO 81 is no longer valid - hence his collaboration with COCOMO II, which has addressed many of the problems that affected the old COCOMO 81 (e.g., it was mainly thought for development of software on expensive mainframes, and development tools have greatly evolved since that time). Still, I insist, if you are careful when making your estimations, the model and the techniques presented in this book are very useful and could be applied even on more modern projects.
My second HOWEVER is related to use the model presented in this book for Software Maintenance purposes. Though the book has a chapter on this issue, by opinion is a radical NO-No on this particular issue. COCOMO 81 (as presented in this book) and COCOMO II are adequate for software development purposes. I totally disagree that they are adequate for software Maintenance purposes (though COCOMO II is at least not so very bad). Apart from the fact that it ignores things such as regression testing, or the number of releases to be made during such maintenance, it also ignores the fact that software "degrades" during such maintenance - subsequent modifications introduce more and more stress on the original design, until at a certain moment the software requires a great "overhaul" in order to solve a lot of patchwork that has accumulated over the years. Hence the typical case of having to redesign a complete new software system because maintenance of the old system becomes too expensive.
In any case, if aware of such limitations, I can highly recommend it.
The COCOMO model is calibrated by industry data and expert opinion. Given module size estimates in lines of code as input the COCOMO model will predict effort and schedule in man-months. The COCOMO predictions cover the plans, product design, programming, and integration & test portions of the life cycle. The validity of the model is illustrated by charting actual vs. COCOMO prediction and the detailed analysis of the COCOMO cost driver attributes in Chapters 24-26. Product attributes are required software reliability (RELY), data base size (DATA), and product complexity (CPLX). Computer attributes are execution time constraint (TIME), main storage constraint (STOR), virtual machine volatility (VIRT), and computer turnaround time (TURN). Personnel attributes are analyst capability (ACAP), applications experience (AEXP), programmer capability (PCAP), virtual machine experience (VEXP), and programming language experience (LEXP). Project attributes are modern programming practices (MODP), use of software tools (TOOL), and required development schedule (SCED).
Readers should be aware that some aspects of the COCOMO have been replaced by the publication of the "Software Cost Estimation with COCOMO II" book. The "COCOMO II" book contains a preface section titled "Relation to 1981 Software Engineering Book". I recommend keeping a copy of this preface handy while you read "Software Engineering Economics" because it provides a chapter-by-chapter assessment of the relevance of the "Software Engineering Economics" content in the year 2000.