Software Measurement and Estimation: A Practical Approach (Quantitative Software Engineering Series) (Hardcover)

~ (Author), M. Carol Brennan (Author) "Suppose you are a software manager responsible for building a new system..." (more)
Key Phrases: John Wiley, New York, Carol Brennan Copyright (more...)

Editorial Reviews

Review

"It is a good and welcome addition to any technical library…and for anyone…who needs to manage software, either development or acquisition." (ACM Software Engineering Notes, January 2007)

"…an excellent book on this important area of software development." (CHOICE, December 2006)

"The authors offer software engineers and project managers a new, tested approach that provides the quantitative tools, data, and knowledge needed to make sound estimations." (IEEE Computer Magazine, August 2006)

"Corporations should advise both their project managers and their software teams to study methods introduced in this worthy text." (Kybernetes, Vol.36 Issue 1)

Product Description

An effective, quantitative approach for estimating and managing software projects


How many people do I need? When will the quality be good enough for commercial sale? Can this really be done in two weeks? Rather than relying on instinct, the authors of Software Measurement and Estimation offer a new, tested approach that includes the quantitative tools, data, and knowledge needed to make sound estimations.

The text begins with the foundations of measurement, identifies the appropriate metrics, and then focuses on techniques and tools for estimating the effort needed to reach a given level of quality and performance for a software project. All the factors that impact estimations are thoroughly examined, giving you the tools needed to regularly adjust and improve your estimations to complete a project on time, within budget, and at an expected level of quality.

This text includes several features that have proven to be successful in making the material accessible and easy to master:
* Simple, straightforward style and logical presentation and organization enables you to build a solid foundation of theory and techniques to tackle complex estimations
* Examples, provided throughout the text, illustrate how to use theory to solve real-world problems
* Projects, included in each chapter, enable you to apply your newfound knowledge and skills
* Techniques for effective communication of quantitative data help you convey your findings and recommendations to peers and management

Software Measurement and Estimation: A Practical Approach allows practicing software engineers and managers to better estimate, manage, and effectively communicate the plans and progress of their software projects. With its classroom-tested features, this is an excellent textbook for advanced undergraduate-level and graduate students in computer science and software engineering.

An Instructor Support FTP site is available from the Wiley editorial department.

See all Editorial Reviews

Product Details

• Hardcover: 280 pages
• Publisher: Wiley-IEEE Computer Society Pr (June 5, 2006)
• Language: English
• ISBN-10: 0471676225
• ISBN-13: 978-0471676225
• Product Dimensions: 9.3 x 6.1 x 0.7 inches
• Shipping Weight: 1.1 pounds (View shipping rates and policies)
• Average Customer Review: 4.5 out of 5 stars  See all reviews (4 customer reviews)
• Amazon.com Sales Rank: #483,652 in Books (See Bestsellers in Books)

Customer Reviews

Most Helpful Customer Reviews

4 of 4 people found the following review helpful:

4.0 out of 5 stars Very Good Book , December 22, 2006

By	MAURICIO AGUIAR (Rio de Janeiro, RJ, Brazil) - See all my reviews (REAL NAME)

It is amazing how much information could be packed into a book of only 250 pages (approximately). This is probably the best book one can currently buy for a good introduction to software measurement and estimation. It is both a guide for students as well as a reference for software measurement practitioners. The book contains small imperfections that can be fixed and by no means reduce its value. They will certainly be corrected in a future edition. Comments below:

- Chapter 1 / Section 1.4 about the CMMI mentions the Project Planning and Project Monitoring and Control process areas (PAs) but fails to mention the Measurement and Analysis process area - that has everything to do with the book's theme.

- Chapter 2 provides a short (and good) description of the GQM (Goal/Question/Metric) approach but fails to mention the PSM (Practical Software & Systems Measurement) methodology, even though the PSM book is listed as reference [3] at the end of the chapter. Also, Section 2.3 is titled "Method 3: Standards Driven Metrics" but does not mention the ISO/IEC 15939 standard (Software Engineering - Software Measurement Process), which is related to the CMMI Measurement and Analysis PA and also to the Practical Software & Systems Measurement initiative. Any book on Software Measurement should cover the ISO/IEC 15939 standard.

- Chapter 3 contains a very good explanation of measurement scales, measures of central tendency, measures of variability, measurement errors, accuracy, and precision.

- Chapter 4 is about software sizing. Even though the coverage is very good, the chapter fails to inform the reader that 3 of the FSM methods - IFPUG, NESMA (Netherlands Software Metrics Users Association, not even mentioned), and COSMIC have become ISO standards. It should also be said that IFPUG considers the Value Adjustment Factor optional since 2003. The main IFPUG Function Point reference, the Counting Practices Manual, is not listed as a reference at the end of the chapter.

- Chapter 5 features a good introduction to complexity measures, including McCabe's cyclomatic complexity, Halstead's measure, and the Agresti-Card-Glass system complexity metric. Object-oriented design metrics are also covered in this chapter. The author explains those measures very clearly including examples.

- Chapter 6 is about effort estimation. Again the author provides excellent and comprehensive explanations of several estimation models, such as expert opinion (including Delphi), benchmark data, analogy, proxy points, custom models, and algorithmic models. On page 96 the author directs the reader to reference [10] for the IFPUG website. As it turns out, reference [10] on page 116 points to the website of a consulting company. It would be nice to have this fixed in the next edition of the book. On page 104 COCOMO II is mentioned but the example on page 105 uses COCOMO 81. The reader should be aware that COCOMO 81 has been replaced by COCOMO II. On page 106 some estimation tools are listed, namely COCOMO, SPR, and Checkpoint. COCOMO itself is not a tool so it would have been better to use the USC COCOMO II free tool as an example, as well as commercial tools such as COSTAR and Cost Xpert. SPR is listed as a tool when it is actually a company that used to sell the Checkpoint tool that has been replaced by KnowledgePlan.

- Chapter 7 provides the reader with a very good introductory treatment of defects. Figure 7.6 on page 122 depicts a size-defect relationship that has been "linearized" through the use of a log-log scale. That should be clearly explained (the text refers to the relationship as linear). Overall this is an excellent chapter.

- Chapter 8, 9, and 10 are, respectively, about reliability, response time and availability, and measuring progress. They are all very good and I can only recommend them. Excellent explanations and references.

- Chapters 11 and 12 - Outsourcing and Financial Measures - seem a little displaced in this book, even though they can still be useful for students.

- Chapter 13 on Benchmarking is perhaps too short to give the theme a fair treatment.

- Chapter 14 on Presenting Metrics to Management is very interesting and potentially useful to measurement analysts. The author teaches the reader how to create a dashboard for all metrics to be viewed as a whole.

What I like about this book is that it deals with the most important topics of software measurement and estimation without being bulky or tedious. The language is simple and keeps the reader interested throughout the 250 pages. Recommended.

I hope this review helps potential readers as well as the author of this very good book.

1 of 1 people found the following review helpful:

4.0 out of 5 stars Excellent book., July 9, 2006

By	Nitram (Edison, NJ USA) - See all my reviews

I bought this book after going through the Table of Contents. After reading some chapters, I am convinced that it is a good buy. The book is written in a simple language and is well structured with good examples thrown in. I found the chapters 'Measuring Size' and 'Estimating Effort' especially well presented. The References listed at the end of the chapters is extremely useful and allows one to explore certain topics in greater detail.

One drawback is that the problems listed at the end of the chapters do not have solution key and the FTP site is not available despite the claim on the front cover. The good news is that one of the authors (Linda) emailed me to state that creating the FTP site was her next project !!!

Overall, an excellent book on a yet to be fully understood software engineering topic.

1 of 1 people found the following review helpful:

5.0 out of 5 stars Outstanding book!, July 7, 2006

By	H. Nguyen (NY, USA) - See all my reviews (REAL NAME)

I've been working on a web application project. I needed to analyze and estimate the reliability of my project. Using the techniques presented in this book (especially chapter 7 - Defects and Defect Metrics), I was able to predict the reliability of my project. Starting at the beginning of the project, I used my history data from other projects for calculations. As I progressed to the test phase (I used incremental model), I was able to estimate the reliability based on the defects collected during the testing phase. I highly recommend this book especially if you are software engineering major.