The Cleanroom Approach to Quality Software Development


Book Description

Describes the first practical attempt to place software development under statistical quality control and to deliver software with a known and certified meantime to failure. Shows how to improve productivity during software development using statistical design methods, and gives guidelines for writing more precise specifications, building simpler designs and avoiding error rework.




Cleanroom Software Engineering


Book Description

Cleanroom software engineering is a process for developing and certifying high-reliability software. Combining theory-based engineering technologies in project management, incremental development, software specification and design, correctness verification, and statistical quality certification, the Cleanroom process answers today's call for more reliable software and provides methods for more cost-effective software development. Cleanroom originated with Harlan D. Mills, an IBM Fellow and a visionary in software engineering. Written by colleagues of Mills and some of the most experienced developers and practitioners of Cleanroom, Cleanroom Software Engineering provides a roadmap for software management, development, and testing as disciplined engineering practices. This book serves both as an introduction for those new to Cleanroom and as a reference guide for the growing practitioner community. Readers will discover a proven way to raise both quality and productivity in their software-intensive products, while reducing costs. Highlights Explains basic Cleanroom theory Introduces the sequence-based specification method Elaborates the full management, development, and certification process in a Cleanroom Reference Model (CRM) Shows how the Cleanroom process dovetails with the SEI's Capability Maturity Model for Software (CMM) Includes a large case study to illustrate how Cleanroom methods scale up to large projects.




Cleanroom Software Engineering Practices


Book Description

Cleanroom Software Engineering is a set of techniques and practices for the development of software-intensive systems. This book brings together concepts, lessons learned and best practices resulting from Cleanroom projects surveyed in the past several years.




Software Engineering Quality Practices


Book Description

Learn how to attract and keep successful software professionals Software Engineering Quality Practices describes how software engineers and the managers that supervise them can develop quality software in an effective, efficient, and professional manner. This volume conveys practical advice quickly and clearly while avoiding the dogma that surr




Mathematical Approaches to Software Quality


Book Description

This book provides a comprehensive introduction to various mathematical approaches to achieving high-quality software. An introduction to mathematics that is essential for sound software engineering is provided as well as a discussion of various mathematical methods that are used both in academia and industry. The mathematical approaches considered include: Z specification language Vienna Development Methods (VDM) Irish school of VDM (VDM) approach of Dijkstra and Hoare classical engineering approach of Parnas Cleanroom approach developed at IBM software reliability, and unified modelling language (UML). Additionally, technology transfer of the mathematical methods to industry is considered. The book explains the main features of these approaches and applies mathematical methods to solve practical problems. Written with both student and professional in mind, this book assists the reader in applying mathematical methods to solve practical problems that are relevant to software engineers.




Software Engineering


Book Description

For more than 20 years, this has been the best selling guide to software engineering for students and industry professionals alike. This edition has been completely updated and contains hundreds of new references to software tools.




Foundations of Empirical Software Engineering


Book Description

Although software engineering can trace its beginnings to a NATO conf- ence in 1968, it cannot be said to have become an empirical science until the 1970s with the advent of the work of Prof. Victor Robert Basili of the University of Maryland. In addition to the need to engineer software was the need to understand software. Much like other sciences, such as physics, chemistry, and biology, software engineering needed a discipline of obs- vation, theory formation, experimentation, and feedback. By applying the scientific method to the software engineering domain, Basili developed concepts like the Goal-Question-Metric method, the Quality-Improvement- Paradigm, and the Experience Factory to help bring a sense of order to the ad hoc developments so prevalent in the software engineering field. On the occasion of Basili’s 65th birthday, we present this book c- taining reprints of 20 papers that defined much of his work. We divided the 20 papers into 6 sections, each describing a different facet of his work, and asked several individuals to write an introduction to each section. Instead of describing the scope of this book in this preface, we decided to let one of his papers, the keynote paper he gave at the International C- ference on Software Engineering in 1996 in Berlin, Germany to lead off this book. He, better than we, can best describe his views on what is - perimental software engineering.




Metrics and Models in Software Quality Engineering


Book Description

""This is the single best book on software quality engineering and metrics that I've encountered."" --Capers Jones, from the Foreword"Metrics and Models in Software Quality Engineering, Second Edition," is the definitive book on this essential topic of software development. Comprehensive in scope with extensive industry examples, it shows how to measure software quality and use measurements to improve the software development process. Four major categories of quality metrics and models are addressed: quality management, software reliability and projection, complexity, and customer view. In addition, the book discusses the fundamentals of measurement theory, specific quality metrics and tools, and methods for applying metrics to the software development process.New chapters bring coverage of critical topics, including: In-process metrics for software testingMetrics for object-oriented software developmentAvailability metricsMethods for conducting in-process quality assessments and software project assessmentsDos and Don'ts of Software Process Improvement, by Patrick O'TooleUsing Function Point Metrics to Measure Software Process Improvement, by Capers Jones In addition to the excellent balance of theory, techniques, and examples, this book is highly instructive and practical, covering one of the most important topics in software development--quality engineering. 0201729156B08282002




Quality Software Project Management


Book Description

The book is based on the "best practices" of the UT Software Quality Institute Software Project Management certificates program. Quality Software Project Management identifies and teaches 34 essential project management competencies project managers can use to minimize cost, risk, and time-to-market. Covers the entire project lifecycle: planning. initiation, monitoring/control, and closing. Illuminates its techniques with real-world software management case studies. Authors (leading practitioners) address the pillars of any successful software venture: process, project, and people. Endorsed by the Software Quality Institute.




Toward Zero-defect Programming


Book Description

Toward Zero-Defect Programming describes current methods for writing (nearly) bug-free programs. These methods are based on practices developed at IBM and elsewhere under the name Cleanroom Software Engineering. The successful application of these methods in commercial projects over the past fifteen years has produced defect rates that are, at least, an order of magnitude lower than industry averages. Remarkably, this reduction in defects comes at no net cost; on the contrary, it is often accompanied by increased productivity and shorter overall development time. In a concise and well-illustrated presentation, Stavely shows how these methods can be applied in three key areas of software development: 1. specification, 2. verification, and 3. testing.