FREE Delivery in the UK.
Only 1 left in stock (more on the way).
Dispatched from and sold by Amazon.
Gift-wrap available.
Quantity:1
Software Engineering Econ... has been added to your Basket
+ £2.80 UK delivery
Used: Good | Details
Condition: Used: Good
Comment: Dispatched from the US -- Expect delivery in 2-3 weeks. Shows some signs of wear, and may have some markings on the inside. 100% Money Back Guarantee. Shipped to over one million happy customers. Your purchase benefits world literacy!
Trade in your item
Get a £0.83
Gift Card.
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See all 2 images

Software Engineering Economics (Prentice-Hall advances in computing science & technology series) Paperback – 22 Oct 1981


See all formats and editions Hide other formats and editions
Amazon Price New from Used from
Paperback
"Please retry"
£62.99
£36.29 £4.44
£62.99 FREE Delivery in the UK. Only 1 left in stock (more on the way). Dispatched from and sold by Amazon. Gift-wrap available.


Trade In this Item for up to £0.83
Trade in Software Engineering Economics (Prentice-Hall advances in computing science & technology series) for an Amazon Gift Card of up to £0.83, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Learn more

Product details

  • Paperback: 1317 pages
  • Publisher: Prentice Hall; 1 edition (22 Oct. 1981)
  • Language: English
  • ISBN-10: 0138221227
  • ISBN-13: 978-0138221225
  • Product Dimensions: 17.5 x 4.6 x 23.1 cm
  • Average Customer Review: 4.3 out of 5 stars  See all reviews (3 customer reviews)
  • Amazon Bestsellers Rank: 317,972 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, and more.

Inside This Book (Learn More)
Browse Sample Pages
Front Cover | Copyright | Table of Contents | Excerpt | Index | Back Cover
Search inside this book:

Customer Reviews

4.3 out of 5 stars
5 star
1
4 star
2
3 star
0
2 star
0
1 star
0
See all 3 customer reviews
Share your thoughts with other customers

Most Helpful Customer Reviews

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.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
Format: Paperback Verified 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
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
By N. Bain on 15 May 2013
Format: Paperback 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.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Most Helpful Customer Reviews on Amazon.com (beta)

Amazon.com: 0 reviews
13 of 14 people found the following review helpful
A classic "must read" - but be aware of its limitations 10 Sept. 2002
By Ramon - 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.
14 of 15 people found the following review helpful
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.
9 of 12 people found the following review helpful
Economic analysis of software decisions making 27 Jun. 2001
By Daniel Mall - Published on Amazon.com
Format: Paperback
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.
19 of 26 people found the following review helpful
Outdated classic 4 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?
4 of 5 people found the following review helpful
Classic Required Reading 6 April 2000
By Denis Snyder - Published on Amazon.com
Format: Paperback
For those engaged in Software Project Management this book is an excellent reference. Free software available from University of Southern California references this book.
Were these reviews helpful? Let us know


Feedback