Software Engineering Economics is an invaluable guide to determining software costs, applying the fundamental concepts of microeconomics to software engineering, and utilizing economic analysis in software engineering decision making.
| ||||||||||||
 Trade In this Item for up to £0.50
Trade in Software Engineering Economics (Prentice-Hall advances in computing science & technology series) for an Amazon.co.uk gift card of up to £0.50, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Learn more
|
Book Description
Product details
Would you like to update product info or give feedback on images?
|
More About the Author
Discover books, learn about writers, and more.
Inside This Book
(Learn More)
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
Customer Reviews
Most Helpful Customer Reviews
By N. Bain
Format:Paperback|Amazon Verified 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.
By A Customer
Format:Paperback
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.
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
3.8 out of 5 stars
6 reviews
14 of 15 people found the following review helpful
4.0 out of 5 stars
A great classic. Needs to be updated for modern practices.
12 May 1998
By Ted Carroll (revonrat@nwlink.com)
- Published on Amazon.com
Format:Paperback
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.
13 of 14 people found the following review helpful
4.0 out of 5 stars
A classic "must read" - but be aware of its limitations
10 Sep 2002
By Ramon Somoza Garcia
- Published on Amazon.com
Format:Paperback
"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.
19 of 25 people found the following review helpful
2.0 out of 5 stars
Outdated classic
5 Oct 1999
By A Customer
- Published on Amazon.com
Format:Paperback
I own a copy and have referenced it numerous times. Perhaps I'm too veteran, but I don't look too often anymore. You may still find this book useful, and it certainly is cited very often, but be warned - it was written in 1981. How much has the software industry changed since then?
›
Go to Amazon.com to see all 6 reviews
3.8 out of 5 stars
Were these reviews helpful?
Let us know
Customer Discussions
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|
Listmania!
Look for similar items by category
- Books > Computing & Internet > Digital Lifestyle > Online Shopping > Amazon
- Books > Computing & Internet > Software & Graphics
- Books > Reference
- Books > Science & Nature > Engineering & Technology > Production, Manufacturing & Operational > Engineering Economics
- Books > Society, Politics & Philosophy > Philosophy
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
