"A clearly written book that is a useful primer for a very complicated set of topics." --Capers Jones, Chief Scientist Emeritus, Software Productivity Research LLC Practical Software Estimation brings together today's most valuable tips, techniques, and best practices for accurately estimating software project efforts, costs, and schedules. Written by a leading expert in the field, it addresses the full spectrum of real-world challenges faced by those who must develop reliable estimates. M. A. Parthasarathy draws on the immense experience of Infosys, one of the world's largest and most respected providers of IT-enabled business solutions, to bring you the only book with detailed guidance on estimating insourced and outsourced software projects, as well as projects that blend both approaches. He demonstrates how to successfully utilize Function Point (FP) methods, the industry's leading estimation model. Then, using real case studies, he systematically identifies pitfalls that can lead to inaccurate estimates--and offers proven solutions. Coverage includes Practical Software Estimation is the definitive reference for anyone who must estimate software projects project and IT managers, individual developers, system designers, architects, executives, consultants, and outsourcers alike.
List of Figures List of Tables Foreword Preface Acknowledgments Chapter 1: Introduction Chapter 2: Role of Estimation in Software Projects Chapter 3: A Study of Function Point Analysis Chapter 4: Data Functions Chapter 5: Transactional Functions Chapter 6: General System Characteristics Chapter 7: Size, Effort, and Scheduling of Projects Chapter 8: Estimation Flavors Chapter 9: A Sense of Where You Are Chapter 10: Tips, Tricks, and Traps Chapter 11: Insourcing versus Outsourcing Chapter 12: Key Factors in Software Contracts Chapter 13: Project Estimation and Costing Chapter 14: Other Estimation Methods Chapter 15: Estimation Tools Chapter 16: Estimation Case Study Appendix Reference Transaction Function Counts Appendix Reference Data Function Points Bibliography Index
Quite simply, this is an explanation on how to estimate size and effort for software development projects using Function Point Analysis, as recommended by the International Function Point Users Group (IFPUG). [1]
If you are reading this book, you aren't reading it for the plot. Which is a good thing, because it is about as fun to read as it is to watch paint dry.
The writing is clear and understandable for the most part, but I find myself wandering what advantage this book has over the IFPUG's Counting Practices Manual (CPM). If you are going to read a long, dry, boring manual, then it may as well be the Official Manual. [2]
--- [1] Function Point analysis is intended to be a method of estimating software size based on user requirements and independent of programming language, hardware, or other implementation details.
[2] In full disclosure, I haven't read the CPM, so I can't really compare it.