Practical Software Measurement: Objective Information for Decision Makers / Edition 1by John McGarry, David Card, Cheryl Jones, Beth Layman
Pub. Date: 08/17/2001
PSM provides you with a way to realize the significant benefits of a software measurement program, while understanding and avoiding the risks involved with a “blind jump.” You’ll find this book a worthwhile starting point for your future software measurement initiatives, as well as a source of continuing guidance as you chart your way through
PSM provides you with a way to realize the significant benefits of a software measurement program, while understanding and avoiding the risks involved with a “blind jump.” You’ll find this book a worthwhile starting point for your future software measurement initiatives, as well as a source of continuing guidance as you chart your way through the sea of complex opportunities ahead.
—Barry Boehm, from the Foreword
Objective, meaningful, and quantifiable measurement is critical to the successful development of today’s complex software systems. Supported by the U.S. Department of Defense and a rapidly increasing number of commercial practitioners, Practical Software Measurement (PSM) is a process for designing and implementing a project-based software measurement program. PSM provides essential information on scheduling, resource allocation, and technological performance. It enables software managers and developers to make decisions that will affect the project’s outcome positively.
This book is the official, definitive guide to PSM written by the leaders of the PSM development initiative. It describes the principles and practices for developing, operating, and continuously improving your organization’s measurement program. It uses real-world examples to illustrate practical solutions and specific measurement techniques. This book examines the foundations of a software measurement program in depth, defining and prioritizing information needs, developing a project-specific information model, tailoring a process model to integrate measurement activities, and analyzing and understanding the results.
Specific topics include:
In addition, this book includes numerous detailed examples of measurement constructs typically applied to software projects, as well as two comprehensive case studies that illustrate the implementation of a measurement program in different types of projects. With this book you will have the understanding and information you need to realize the significant benefits of PSM as well as a guide for a long-term, organization-wide measurement program.
PSM is founded on the contributions and collaboration of key practitioners in the software measurement field. The initiative was established in 1994 by John McGarry and is currently managed by Cheryl Jones. Both are civilians employed by the U.S. Army. David Card is an internationally known software measurement expert, and is with the Software Productivity Consortium. Beth Layman, Elizabeth Clark, Joseph Dean, and Fred Hall have been primary contributors to PSM since its inception.
- Publication date:
- Edition description:
- New Edition
- Product dimensions:
- 6.44(w) x 9.62(h) x 0.84(d)
Table of Contents
1. Measurement: Key Concepts and Practices.
Motivation for Measurement.
Measurement as an Organizational Discriminator.
The Foundation—Project Measurement.
What Makes Measurement Work.
Measurement Information Model.
Measurement Process Model 10.
2. Measurement Information Model.
Measurement Construct Examples.
3. Plan Measurement.
Identify and Prioritize Information Needs.
Select and Specify Measures.
Integrate the Measurement Approach into Project Processes.
4. Perform Measurement.
Collect and Process Data.
5. Analysis Techniques.
6. Evaluate Measurement.
Evaluate the Measures.
Evaluate the Measurement Process.
Update the Experience Base.
Identify and Implement Improvements.
7. Establish and Sustain Commitment.
Obtain Organizational Commitment.
Define Measurement Responsibilities.
Review the Measurement Program.
8. Measure For Success.
Appendix A: Measurement Construct Examples.
Work Unit Progress: Software Design Progress.
Financial Performance: Earned Value.
Appendix B. Information System Case Study.
Getting the Project Under Control.
Evaluating Readiness for Test.
Installation and Software Support.
Appendix C. Xerox Case Study.
Product and Project Overview.
Estimation and Feasibility Analysis.
Redesign and Replanning.
and post it to your social network
Most Helpful Customer Reviews
See all customer reviews >