Terms and Conditions:
Michael R. Lyu wrote:The book content here is free for use or link. Please cite the book properly in resulted publications.
Excerpts from the Preface:
This is a handbook on software reliability engineering
. The theme underlying the book is the formulation, application, and evaluation of software reliability engineering techniques in practice. Reliability is obviously related to many characteristics of the software product and development process. This Handbook
intends to address all its aspects in a quantitative way.
The book is designed for practitioners or researchers at all levels of competency, from novice to expert. It is targeted for several large, general groups of people who need information on software reliability engineering. They include:
1. People who need a general understanding of software reliability. These are high-level managers, professional engineers who use soft ware or whose designs interface with software, and people who acquire, purchase, lease, or use software.
2. Software developers, testers, and quality assurance personnel who use and apply software reliability engineering techniques. This also includes practitioners in related disciplines such as system engineering, reliability management, risk analysis, management-decision sciences, and software maintenance.
3. Researchers and students in software engineering, reliability analysis, applied statistics, operations research, and related disciplines, and anyone who wants a deeper understanding of software reliability and its engineering techniques.
Each of the book's individual topics (i.e., chapters) could be considered as a compact, self-contained minibook. However, these topics are presented in relation to the basic principles and practices of software reliability engineering. The approach is to provide a framework and a set of techniques for evaluating and improving the engineering of software reliability. It presents specific solutions, obtained mostly from real-world projects and experimental studies, for routine applications. It further hi ghlights promising emerging techniques for research and exploration opportunities.
:) "If you're trying to answer questions like "based on historical data, when is the next expected failure," or "what model best predicts my software's reliability," or "when will the software be stable" then you need this book."
:) "This is an essential work for anyone compiling metrics for gauging how well a S/W development effort is progressing."