| | ||
| | | |
| |||
| |
|
| |
![]() | ![]() |
|
| | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
![]() Accounting & Finance Architecture Arts & Photography Business & Investing Business Management Computer Science Apple Education Business & Culture Certification Central Databases Digital Music Digital Photography & Video Games & Strategy Guides Graphic Design Hardware Home Computing Microsoft Mobile & Wireless Computing Networking Operating Systems Programming Project Management Security & Encryption Software Web Development Engineering History Humanities Law Medicine Professional Science Reference Science Social Sciences Summaries and Customer Reviews are supplied by Amazon.com
Customer Reviews:Average Customer Rating: A Comprehensive State of the Art This second edition of the groundbreaking Estimating Software Costs is a must-have desk reference for every PM, program manager and estimation practitioner. It has been updated to include treatment of Agile methods (and other variants such as XP), OO development, UML, and CMMI. While IFPUG Function Points and Lines of Code are the still the leading measures of software size, Jones does provide data with respect to many of the emerging measures (story points, use case points, web object points, etc.) Still valid and applicable, with some gaps This is one of the most comprehensive books on software estimation techniques and supporting statistics in print. True, this book is deficient in object-oriented estimation, but that gap is filled by the definitive text on that subject, "Object-Oriented Design Measurement" ISBN 0471134171. One thing the author is noted for is backing up assertions with statistics and data. This book is no exception. The full spectrum of estimation techniques is covered in great detail, and the scope of this book starts with background material on estimating, and then addresses all of the major techniques. It is the scope of this book that makes it so valuable six years after publication. Techniques drawn from software project management, methods using coefficients and adjustment factors (i.e., COCOMO and Rayleigh Curve), and function points are covered in detail, as are other methods. In addition to software development estimating, the coverage extends to documentation estimating, and maintenance estimating - two areas not commonly addressed in the same detail and depth into which this book goes. Weighing in at 700 plus pages this book is still applicable to most project and development environments, with the only outdated material related to tools and information resources. Most of the techniques cited are tried and true and will work in most contemporary environments and settings. Despite some of the shortcomings noted above this book is an essential resource for project managers and SQA professionals who are involved in either the estimating process or tracking key performance metrics throughout application and system lifecycles. Lots of Data for the Price of a Book This book contains lots of useful data on the software development process -- including productivity -- using both LOC and IFPUG Function Points. It includes basic rules of thumb for estimating schedules and effort. It is a good starting point for organizations that do not have their own historical data to base their estimates on. An excellent reference to have within reach if you work with software measurement. Lacks object-oriented statistics Other people (in old-fashioned waterfall projects) may find this comprehensive and thick book helpful; I did not. I need a book like this, but covering OO and Java in depth. Java has been around for 4 years now: studies exist and one wishes that Jones had gethered them together and analyzed them for us. (Sigh!) Book is excellent otherwise. A must for any IT project Manager This is an excelent textbook about software projects estimation. The only problem with the book is the lack of more examples to learn the techniques discussed by Jones. | | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ![]() | |
| |