A classic reference on estimating the cost of software projects, economic analysis techniques, and applying economic principals to upper-level management of software projects. The intimidating appearance of the text on initial inspection is overcome by the author's excellent organization of the content into small chapters and his lucid writing style. The definition of a software cost model called the constructive cost model (COCOMO) is a major centerpiece. Another centerpiece is the chapters on cost-effectiveness analysis, multiple goal decision analysis, dealing with uncertainties and the value of information, software project planning and control, and improving software productivity. Alternatives to cost models such as experts, analogy, Parkinson, price-to-win, top-down, and bottom-up are discussed in Chapter 22. Uses several case studies for example a transaction processing system. Contains an excellent set of questions and exercises at the end of each chapter.
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.
Flip to back
Flip to front
Follow the Author
Something went wrong. Please try your request again later.
OK
Software Engineering Economics Hardcover – Oct. 22 1981
by
Barry W. Boehm
(Author)
|
Barry W. Boehm
(Author)
Find all the books, read about the author and more.
See search results for this author
|
|
Amazon Price
|
New from | Used from |
-
ISBN-100138221227
-
ISBN-13978-0138221225
-
Edition1st
-
PublisherPrentice Hall
-
Publication dateOct. 22 1981
-
LanguageEnglish
-
Dimensions19.05 x 3.81 x 24.77 cm
-
Print length800 pages
Customers who bought this item also bought
Page 1 of 1 Start overPage 1 of 1
No Kindle device required. Download one of the Free Kindle apps to start reading Kindle books on your smartphone, tablet, and computer.
-
Apple
-
Android
-
Windows Phone
-
Android
Tell the Publisher!
I'd like to read this book on Kindle
Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.
I'd like to read this book on Kindle
Don't have a Kindle? Get your Kindle here, or download a FREE Kindle Reading App.
Product details
- Publisher : Prentice Hall; 1st edition (Oct. 22 1981)
- Language : English
- Hardcover : 800 pages
- ISBN-10 : 0138221227
- ISBN-13 : 978-0138221225
- Item weight : 1.31 kg
- Dimensions : 19.05 x 3.81 x 24.77 cm
-
Best Sellers Rank:
#1,255,655 in Books (See Top 100 in Books)
- #648 in Questions & Answers
- #917 in Software Information Systems
- #1,029 in PMP Exam
- Customer Reviews:
Customer reviews
4.3 out of 5 stars
4.3 out of 5
13 global ratings
How are ratings calculated?
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzes reviews to verify trustworthiness.
Top reviews
Top reviews from Canada
There was a problem filtering reviews right now. Please try again later.
Reviewed in Canada on June 27, 2001
Report abuse
Helpful
Reviewed in Canada on January 26, 2004
Software Engineering Economics is one of the biggest classics in software engineering books. Still today (2004) much of the content is valid and the discussions are very useful. When reading this book you should realize that it's from 1981 and that much has changed since then.
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!
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!
One person found this helpful
Report abuse
Reviewed in Canada on September 10, 2002
"Software Engineering Economics" is *the* book to be considered for anybody wishing to seriously enter the world of software cost estimation - only if it were because of the extremely great influence this book has had on this very peculiar aspect of software engineering. In this aspect, Barry Boehm is undoubtly the master.
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.
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.
Reviewed in Canada on May 11, 1998
This is a great book and should be required reading for anyone who schedules software projects. Some of the data is out of date and readers should look to the website for updates. If this book contained current information it would easily be a 10.
Reviewed in Canada on April 6, 2000
For those engaged in Software Project Management this book is an excellent reference. Free software available from University of Southern California references this book.
Top reviews from other countries
N. Bain
4.0 out of 5 stars
Needs must.
Reviewed in the United Kingdom on May 15, 2013Verified Purchase
I bought this book to help with a project at work. It's a dry read and not for the faint-hearted, but full of useful stuff.
Jon
5.0 out of 5 stars
Excellent condition for a used item
Reviewed in the United Kingdom on May 24, 2014Verified Purchase
Book arrived on schedule. It's in excellent condition for a used item. This is a software engineering classic and regularly used reference, many years after publication
Bas Vodde
4.0 out of 5 stars
Still a classic
Reviewed in the United States on January 26, 2004Verified Purchase
Software Engineering Economics is one of the biggest classics in software engineering books. Still today (2004) much of the content is valid and the discussions are very useful. When reading this book you should realize that it's from 1981 and that much has changed since then.
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!
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!
4 people found this helpful
Report abuse
Joel R.
3.0 out of 5 stars
One of the original pioneering works on software engineering.
Reviewed in the United States on December 15, 2014Verified Purchase
This is one of the original books on software engineering estimation. In this book, Boehm publishes the theory behind COCOMO (Constructive Cost Model). It has since been updated by COCOMO II, making this book obsolete.
3 people found this helpful
Report abuse



