Function Point Analysis: Measurement Practices for Successful Software Projects (Addison-Wesley Information Technology Series) [Paperback]

David Garmus (Author), David Herron (Author)

Book Description

ISBN-10: 0201699443 | ISBN-13: 978-0201699449 | Publication Date: December 15, 2000 | Edition: 1

This is the first in-depth software measurement guide focused entirely on the #1 technique for evaluating software productivity and quality: function point analysis. Written for both seasoned practitioners and newcomers, it reflects the latest standards defined by the International Function Point User Group (IFPUG), and presents realistic techniques for analyzing any type of software -- including graphical, object-oriented, Web and client/server applications. It also offers comprehensive preparation for the IFPUG CFPS certification exam. Coverage includes: all rules and guidelines prescribed by IFPUG's Counting Practices Manual 4.1; practical guidance on baselining and estimating; advanced counting techniques for contemporary distributed development environments; and using function point data to manage software development more effectively. The book presents extensive examples, case studies, and scenarios, and reviews repository and estimating tools that can streamline function point analysis. For every IT manager, project manager, software developer and engineer, and for any professional concerned with the measurement of software quality and productivity.

Editorial Reviews

From the Inside Flap

Writing this book has been a process, a journey, and a wonderful learning experience.

We have been immersed in the world of function points and software metrics for more than ten years. We both are proud of our accomplishments and contributions to the advancement and utilization of the function point methodology. We recognize a responsibility, as experts in this field, to communicate our experiences and to express our opinions in such a way that others can gain from what we have observed, learned, and practiced. You could say that we believe and that we are extending the wisdom of the message. We have also found our writings to be an opportunity for continued learning. While writing this book, we had the good fortune to receive comments and constructive criticisms from a significant number of book reviewers and industry experts. Their thoughtful comments and contributions have given us greater insight into the software community views of software measurement and management and, in particular, function points. We thank all of you who participated in the review process.

Our second book was in many ways easier, but in some ways more challenging, than the first. We endeavored to write a book that was significantly better than the first. We achieved success with our first book, but we knew that there was so much more to share. The process of writing becomes easier once you understand that it is a process similar to developing software. Our challenge was to identify the content that would serve a diverse audience while not losing sight of the most important audience, the practitioner. After all, it is the practice, not the theory, of function points that will sustain this valuable software management methodology.

0201699443P04062001

From the Back Cover

Function Point Analysis: Measurement Practices for Successful Software Projects is a comprehensive presentation of the principles of function point analysis (FPA) and a guide to its effective use in managing the development and deployment of software. Written for both information technology (IT) practitioners and managers, it describes how to use this proven-but-underutilized software-sizing metric to achieve successful software projects.

Completely up-to-date, the book introduces the latest rules and guidelines released in the International Function Point Users Group (IFPUG) Counting Practices Manual 4.1.

Function Point Analysis presents fundamental counting techniques for basic-to-advanced technologies. It explains the calculations for determining function point size, an indication of a software application's overall functionality and complexity. Moving beyond mechanics, the book features the most common uses of FPA and reveals experience-based techniques for applying the methodology with success.

The book covers such important topics as:

• An overview of FPA for the IT executive
• A description of software measurement, relating size to other software metrics
• Sizing data and transactional functions
• The application of general system characteristics
• Counting object-oriented, Web-based, client-server, and GUI applications
• Becoming a Certified Function Point Specialist (CFPS), using a practice exam
• The use of FPA for accurate project estimating, development and maintenance outsourcing, and performance productivity baselining
• FPA automation tools, including function point repository tools and function point- based project estimation tools
• The role of FPA in standardizing industry benchmarking data

Numerous detailed examples and case studies demonstrate the FPA methodology in action. As a reference, tutorial, and practical guide, Function Point Analysis: Measurement Practices for Successful Software Projects raises the level of awareness and understanding of FPA and its role in bringing proven quality standards to the software development industry.

0201699443B04062001

See all Editorial Reviews

Product Details

• Paperback: 400 pages
• Publisher: Addison-Wesley Professional; 1 edition (December 15, 2000)
• Language: English
• ISBN-10: 0201699443
• ISBN-13: 978-0201699449
• Product Dimensions: 9.3 x 7.4 x 1 inches
• Shipping Weight: 1.4 pounds (View shipping rates and policies)
• Average Customer Review: 3.8 out of 5 stars  See all reviews (6 customer reviews)
• Amazon Best Sellers Rank: #646,013 in Books (See Top 100 in Books)

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

Most Helpful Customer Reviews

38 of 40 people found the following review helpful:

5.0 out of 5 stars Excellent Description and Great for CFP Candidates, March 29, 2001

By 

Mike Tarrani "www.tarrani.com" (Deltona, FL USA) - See all my reviews
(COMMUNITY FORUM 04)    (REAL NAME)   

This review is from: Function Point Analysis: Measurement Practices for Successful Software Projects (Addison-Wesley Information Technology Series) (Paperback)

This is an authoritative book by two authors who have a published a large number of articles on the subject.

Function point analysis is, in both my experience and opinion, one of the most accurate estimating tools a software engineer has at his or her disposal. I have previously used the constructive cost model (COCOMO) through version 2, Raleigh curves, and hybrids such as Software Estimation Analysis Tool, which computes both COCOMO and function point statistics. Granted, not all of these estimating models are equal - the Raleigh curve approach has a focus on quality and manpower loading that the others lack. But each (and many I have not cited) are estimating tools for software development.

My experience shows function point analysis to be the most accurate - if done correctly. Therein lies the crux of the matter. Function point analysis, in order to yield accurate estimates of effort, needs to be performed by certified counters and the resulting data needs to be properly interpreted. That's where this book comes in.

It starts with an overview that serves as an understandable introduction for someone who is new to software estimation, yet is interesting enough to hold the attention of more experienced professionals. The advice on preparing for IFPUG (International Function Point User Group) certification is a highlight and underscores the fact that FP counting should only be performed by certified counters.

The chapters on software measurement and executive introduction to function points are really extensions of the introduction. I found both the software measurement model in this chapter, and how to establish a world class measurement program interesting and informative.

This segues into three chapters that cover measuring and using function points, and industry benchmarks. Some highlights are the way the authors tie function points to key performance indicators such as productivity, quality, financial and maintenance. I also liked the way that the authors stratify the users of function point data into project managers, IT managers and cross-organizational stakeholders. I was particularly interested in the last group because I am often involved in both service and application delivery projects. The use of function points as a basis for service level metrics and outsourcing is an intriguing idea that I will explore further.

When you arrive at chapter 6 the foundation built in the first five chapters prepare you for a detailed, methodical approach to performing function point analysis. This is straightforward and appears to be completely consistent with IFPUG. All you need to know about function point analysis is, in my opinion, provided in the remainder of the book. The material is augmented by case studies, and also addresses contemporary issues such as applying function point analysis to object-oriented, web, client/server and data warehouse applications. While each of these topics are not given in-depth treatment the fact that they are addressed at all is impressive. The authors end the book with advice on preparing for the certified function point specialist exam, and gives sample exam questions. They also provide sample worksheets in the appendices.

This book merits a solid five stars because it is well written, up-to-date and follows IFPUG recommendations. If you are pursuing CFP certification this book will simplify your life. If you want to learn about an effective software estimating technique this book is a great starting point. To be completely fair, if you are new to software estimation you should also read Estimating Software Costs (Caspers Jones), which gives a complete and unbiased survey of all of the major (and some obscure) software estimating approaches.

16 of 18 people found the following review helpful:

4.0 out of 5 stars An excellent companion through the complete process, March 30, 2001

By A Customer

This review is from: Function Point Analysis: Measurement Practices for Successful Software Projects (Addison-Wesley Information Technology Series) (Paperback)

This is a really useful book. It's a must if you need to look deep into the Function Point Analysis and get a clear understanding of what this is all about. As a professional and local instructor in Function Point Analysis I've got a lot of inspiration from this book for my course. I believe that beginners would gain even more from this book, however. It covers all topics from the current IFPUG Function Point Counting Practices Manual (release 4.1). It guides you all the way through the whole process and presents a lot of examples and additional explanations on the way.

Beside the operational guidelines this book also describe the Function Point Analysis in the perspective of related topics as e.g. estimation and benchmarking. Those topics are covered very thoroughly as well and the book provides a good insight in how Function Points can be used as a management tool.

In the last chapters "hot issues" as applying Function Points to GUI applications and OO-system development are discussed. Some very useful guidelines are presented here, indeed. But it's my personal experience that mapping OO components to the Function Point concept might be quite more challenging that the book indicates.

3 of 3 people found the following review helpful:

5.0 out of 5 stars Excellent Guide to Function Point Analysis, January 26, 2007

By 

Kiwi (Mississauga, Ontario Canada) - See all my reviews
(TOP 500 REVIEWER)   

This review is from: Function Point Analysis: Measurement Practices for Successful Software Projects (Addison-Wesley Information Technology Series) (Paperback)

Published in 2001, this is a very detailed book on Function Points that follows the guidelines in the 4.1 version of the International Function Point Users Group (IFPUG) standard. Function Point metrics originated in IBM back in the 1970's and spread slowly out to the rest of the world in the late 70's and early 80's. As with anything originating from IBM, it's a process that's heavy on detail and requires a lot of work to get it right. Over the years, FPA has got more and more technical, to the extent that you really need to get certified in it these days (when I first took an FPA course in the early 80's, it wasn't nearly as comprehensive as it is these days, 20 years on..). The authors of this book between them have published a number of articles on the subject and have more than a few years of experience under their respective belts.

The book kicks off with an overview that provides a useful introduction for those "new" to software estimation, although it's still pretty heavy going and it assumes a process-heavy background. If you've worked for a large organization with a comprehensive PMBOK-like methodology, it'll all make sense. If not, you're going to have a headache by the time you finish the first chapter. <lol>. There's some good advice on preparing for IFPUG (International Function Point User Group) certification and the authors emphasize the fact that FP counting should only be performed by certified counters. IMPORTANT ENOUGH TO REITERATE - FP counting should only be performed by certified counters!!!! Keep this in your mind at all times. FPA is "Estimating-Heavy", not estimating-light. It don't come cheap in time or education.

The other reviewers have covered the content in enough detail that it's rather pointless to reiterate - suffice it to say I agree with their comments on the content. So, cutting to the chase, if you're looking at books on Function Point Analysis, you've obviously got a serious interest in estimating, and if so, and if FPA is where you want to go, this book is going to be very useful for you as a reference and as a guide. On the other hand, FPA is, while accurate if applied correctly (the nub of the matter.....), both time and expertise intensive - I can't emphasis the expertise factor enough. You need a sizable project with a budget sufficient to fund the additional overhead to make it worthwhile - for your average development project, this is overkill. If you've got a $50-$100 million plus project within the grasp of our sticky little paws and you can get a certified FPA resource on board, using FPA may very well help you stay within your rather sizable budget. And if your're studying towards your FPA certification, by all means delve into this book - it'll help you no end.

But having been there and done that in my past, don't try this at home kids. This book is a great resource, you'll learn all about FPA from it, but reading the book is a completely different kettle of fish to actually doing it. As another reviewer has pointed out, FPA is accurate IF DONE CORRECTLY. To get accurate estimates, you need certified FP counters, and the data needs to be interpreted correctly. Easier said than done. If you want to use FPA yourself, go study and get yourself certified before you try it for real - otherwise, you may well send your career as an estimator down the tubes.

If you've got to come up with estimates and you've got no real estimating experience, DON'T START HERE. Go look at Steve McConnell's book on "Software Estimation: Demystifying the Black Art" to get yourself started. You could also look at Caper Jones' "Estimating Software Costs" although it's a little dated and not up to date with Agile estimating practices (my bias shows through.....). (Subsequent update - apparantly -the second edition (2007) of "Estimating Software Costs" by Capers Jones addresses Agile methods...).

On the third hand, I do give this book 5 stars for what it is. Well-written, understandable, effective - and it follows IFPUG guidelines. If you're after CFP certification, this book won't lead you astray (although it is a version or 2 out of date) and it will prove a useful study aid. I've got it on my bookshelf at work and although I now use Agile Estimating Practices a la Ken Schwaber (Agile Project Management with Scrum) and Mike Cohn (Agile Estimating and Planning), I do take a look at this one every now and then just to see what the FPA guidelines are. Mind you, every time I look thru this book and think of what I might have been doing, I bless Ken Schwaber for coming up with Scrum (OK, OK, I like smaller projects and I like the Agile approach.....).