Metrics

Metrics and Models in Software Quality Engineering by Stephen H. Kan, Addison-Wesley, 2002. Measurement plays a critical role in effective and efficient software development, as well as provides the scientific basis for software engineering that makes it a true engineering discipline. This book describes the software quality engineering metrics and models: quality planning, process improvement and quality control, in-process quality management, product engineering (design and code complexity), reliability estimation and projection, object-oriented metrics, availability metrics, and analysis of customer satisfaction data.

Object-Oriented Software Metrics by Mark Lorenz and Jeff Kidd, Prentice Hall, 1994. Thus book provides a number of specific metrics that apply to object-oriented software projects. The metrics are based on measurements and derived advice drawn from a number of actual projects that have successfully used object technology to deliver products.

Object-Oriented Metrics: Measures of Complexity by Brian Henderson-Sellers, Prentice Hall, 1995. Object-oriented (OO) metrics are an integral part of object technology — at the research level and in commercial software development projects. This book offers theoretical and empirical tips and facts for creating an OO complexity metrics (measurement) program, based on a review of existing research from the last several years. Covers moving through object-oriented concepts as they related to managing the project lifecycle; the framework in which metrics exist; structural complexity metrics for traditional systems; OO product metrics; and current industrial applications.

A Framework of Software Measurement by Horst Zuse, Walter de Gruyter, 1997. Zuse's textbook on software measurement provides basic principles as well as theoretical and practical guidelines for the use of numerous kinds of software measures.

Software Complexity: Measures and Methods by Horst Zuse, Walter de Gruyter, 1990. This is a serious, exhaustive treatment of software measurement.

Object-Oriented Design Measurement by Scott A. Whitmire, John Wiley, 1997. Based on a thorough study of measurement theory, category theory, and a strong mathematic foundation, the author presents his own formal model of objects. Using this or any other formal model you can create a custom metric for any design characteristics.

Elements of Software Science by Maurice H Halstead, Elsevier, 1977. Some of the earliest software metrics were developed by Halstead.

Software Metrics edited by Alan Perlis, Frederick Sayward, and Mary Shaw, MIT Press, 1981. A collection of articles which shows the state of software metrics research in the early 1980's.

Metrics and Productivity

A Discipline for Software Engineering by Watts S. Humphrey, Addison-Wesley, 1994. Methods for managing an organization's software process now commonly practiced in industry, provide to programmers and managers specific steps they can take to evaluate and to improve their software development and software maintenance capabilities. In Humphrey's book, he scales those methods down to a more personal level, helping software engineers working on relatively small-scale programs to develop the skills and the habits they will need later in their professional life to plan, track, and analyze large and complex software projects more carefully and more successfully.

Applied Software Measurement: Assuring Productivity and Quality by Capers Jones, McGraw Hill, 1996. The use of metrics has come to play an increasingly pivotal role in the progress of the software industry over the last several years, and this definitive work helped to make software measurement a science. Function points and related variations are now regarded as indispensable tools for software engineers and developers, IS managers, and anyone else charged with performance improvement and quality control. Here is authoritative information on software metrics in relation to many of today's most intriguing and fastest growing areas, including: Object technology; client/server architecture; Multimedia; Software reusability; Reengineering and outsourcing.

Software Metrics: Establishing a Company-Wide Program by Robert B. Grady and Deborah L. Caswell, Prentice Hall, 1987. This book is a diary of the trials and tribulations of implementing a metrics program at Hewlett-Packard that is packed with practical advice that came from lesson's learned and a great roadmap to implementing a program of process improvement. The book addresses the difficulties and rewards of establishing an effective, viable metrics program. The authors clearly show the business and technical value that rewards the daunting effort.

Software Reliability: Measurement, Prediction, Application by John D. Musa, Anthony Iannino, and Kazuhira Okumoto, McGraw Hill, 1989. This book is classified as a seminal work in that it was the first mainstream book to address software reliability. The author is considered to be one of the founders of the discipline. Although the body of knowledge has grown significantly since this book was first published it remains a valid text because unlike technology, the underlying math and modeling are nearly timeless. The book serves as an introduction to software reliability as a discipline, and gives a solid foundation of the basics. Be aware that this is a math-intensive text and requires both statistics and probability skills.

Metrics and Projects

Software Metrics: A Rigorous and Practical Approach by Norman E. Fenton and Shari Lawrence Pfleeger, Course Techhlogy, 1998. Software Metrics is not just a thorough, readable survey of the various proposals that have been made over the years for measuring the characteristics of programs; it is also a detailed critique of the sloppy way in which people have tried to use such measurements to predict how much effort would be required to develop and maintain software, and how reliable that software would be. The first part of Software Metrics introduces the fundamentals of measurement theory. The second part of the book looks at software measurement in particular. Popular measures (COCOMO, function points, cyclometric complexity, and the like) are all described, and their weaknesses pointed out. Part Three looks at implementing software measurement in the workplace.

Practical Software Metrics for Project Management and Process Improvement by Robert B. Grady, Prentice Hall, 1992. This application-oriented book shows how to apply proven software metrics and methods to efficiently manage software development and maintenance--to help boost productivity, efficiency, and quality of software projects at every stage of the process.

Software Engineering Economics and Software Cost Estimation with Cocomo II by Barry W.Boehm, Prentice Hall, 2000. Don't become a statistic take control of your software projects and plan for success! Success in all types of organization depends increasingly on the development of customized software solutions, yet more than half of software projects now in the works will exceed both their schedules and their budgets by more than 50%. While some types of overruns remain unpredictable, most can be avoided by sound modeling. COCOMO II provides you with a thorough rework of the classic COCOMO model to address modern software processes and construction techniques along with representative examples of applying the models to key software decision situations. It was calibrated and validated using innovative statistical techniques to fit both expert judgment and 161 carefully collected project data points.

Software Engineering: A Practitioner's Approach by Roger S Pressman, McGraw Hill, 2004. For over 20 years, Software Engineering: A Practitioner's Approach has been the best selling guide to software engineering for students and industry professionals alike.

Controlling Software Projects: Management, Measurement and Estimation By Tom DeMarco, Prentice Hall, 1986. "You can't control what you can't measure", is how DeMarco opens this seminal work in software project management, and the primary focus of this book is how to develop an effective strategy for measuring software development costs and thus build a reliable means of estimating the cost of future projects.