Autres vendeurs sur Amazon
+ EUR 0,01 (livraison)
+ EUR 0,01 (livraison)
+ EUR 0,01 (livraison)
Estimating Software Costs: Bringing Realism to Estimating (Anglais) Relié – 10 mai 2007
- Choisissez parmi 17 000 points de collecte en France
- Les membres du programme Amazon Prime bénéficient de livraison gratuites illimitées
- Trouvez votre point de collecte et ajoutez-le à votre carnet d’adresses
- Sélectionnez cette adresse lors de votre commande
Les clients ayant acheté cet article ont également acheté
Description du produit
Présentation de l'éditeur
Deliver bug-free software projects on schedule and within budget
Get a clear, complete understanding of how to estimate software costs, schedules, and quality using the real-world information contained in this comprehensive volume. Find out how to choose the correct hardware and software tools, develop an appraisal strategy, deploy tests and prototypes, and produce accurate software cost estimates. Plus, you'll get full coverage of cutting-edge estimating approaches using Java, object-oriented methods, and reusable components.
- Plan for and execute project-, phase-, and activity-level cost estimations
- Estimate regression, component, integration, and stress tests
- Compensate for inaccuracies in data collection, calculation, and analysis
- Assess software deliverables and data complexity
- Test design principles and operational characteristics using software prototyping
- Handle configuration change, research, quality control, and documentation costs
"Capers Jones' work offers a unique contribution to the understanding of the economics of software production. It provides deep insights into why our advances in computing are not matched with corresponding improvements in the software that drives it. This book is absolutely required reading for an understanding of the limitations of our technological advances." --Paul A. Strassmann, former CIO of Xerox, the Department of Defense, and NASA
Biographie de l'auteur
Capers Jones is a leading authority in the world of software estimating. He was the founder and chairman of Software Productivity Research, where he currently serves as chief scientist emeritus.
Aucun appareil Kindle n'est requis. Téléchargez l'une des applis Kindle gratuites et commencez à lire les livres Kindle sur votre smartphone, tablette ou ordinateur.
Pour obtenir l'appli gratuite, saisissez votre numéro de téléphone mobile.
Détails sur le produit
Si vous vendez ce produit, souhaitez-vous suggérer des mises à jour par l'intermédiaire du support vendeur ?
|5 étoiles (0%)|
|4 étoiles (0%)|
|3 étoiles (0%)|
|2 étoiles (0%)|
|1 étoile (0%)|
Commentaires client les plus utiles sur Amazon.com
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.
The book is divided into six sections. Section 1 presents a basic introduction to software estimation, including a brief history, capability and value of commercial estimation tools. There is also a very nice discussion on the potential sources of estimation error.
Section 2 provides methods for generating early estimates and the danger that these will become accepted as THE estimate for the remainder of the project. Jones provides many simple rules of thumb for both classic size measures (Function Points and LOC) and emerging methods.
Section 3 talks about methods of measuring size of various software work products. Again, the predominate method discussed is IFPUG Function Points; however, Jones does address the more abstract and "experimental" size measure in use today.
Section 4 deals with the seven classes of influencing factors that drive project outcomes and how commercial estimation tools compensate for them. Jones concludes that industry averages for these factors should be discarded in favor of specific values from the performing organization. This reduces uncertainty and the political impacts.
Section 5 defines ten activities that are common to many projects for the purpose of accurately deriving a bottom-up estimate. The implication of each of these activities with respect to software estimation is explored in detail.
Section 6 examines the difficulty of maintenance estimation based on the notion of "software entropy," which is analogous to the Thermodynamics property of isolated systems. Entropy is a measure of disorder in an isolated system and increases with time. As a product ages, its level of disorder increases due to the number of maintenance patches and enhancements applied. This reduces the maintainability of the product and increases the difficultly in maintenance estimation.
Again, Capers Jones proves to be a master at collecting, interpreting and presenting useful data. While some of the material (notably the rules of thumb) may be slightly over-approximated to be useful, Jones does present many ways to develop the initial early estimate and start the open dialogue that will ultimately lead to a successful project.