- STAFF PICKS
- GIFTS + GIFT CARDS
- SELL BOOKS
- FIND A STORE
Currently out of stock.
available for shipping or prepaid pickup only
Other titles in the SEI Series in Software Engineering series:
Cleanroom Software Engineering: Technology and Process (SEI Series in Software Engineering)by Stacy Prowell
Synopses & Reviews
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.
Book News Annotation:
Cleanroom is a theory-based, team-oriented process for the production of high-quality software in an economical manner. Written by four experienced developers and practitioners of Cleanroom, the book provides an overview of the methods for application to software engineering projects, and a road map for software management, development, and testing as disciplined engineering practices. A case study of a satellite control system project illustrates the methods.
Annotation c. Book News, Inc., Portland, OR (booknews.com)
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. 0201854805B04062001
About the Author
Stacy J. Prowell is a member of the technical staff at Q-Labs, and is the principal inventor of the sequence-based specification method.
Carmen J. Trammell is Manager of Software Quality at CTI-PET Systems, a leading medical imaging company that is integrating Cleanroom technology into product development.
Richard C. Linger is a Visiting Scientist at Carnegie Mellon University's Software Engineering Institute. During his career at IBM he worked with Harlan D. Mills to develop the foundations of Cleanroom, and managed IBM's first Cleanroom project.
Jesse H. Poore is a Professor of Computer Science at the University of Tennessee and holds the Ericsson-Harlan D. Mills Chair in Software Engineering.
Table of Contents
I. CLEANROOM SOFTWARE ENGINEERING FUNDAMENTALS.
1. Cleanroom Overview.
Economic Production of High-Quality Software.
The Cleanroom Process.
Relationship of Cleanroom to Other Practices.
Cleanroom Project Experience.
2. Cleanroom Management by Incremental Development.
Benefits of Incremental Development.
Theoretical Foundations of Incremental Development.
Increment Planning in Practice.
Incremental Development in Practice.
3. Cleanroom Software Specification.
Box Structures for Cleanroom Specification and Design.
The Sequence-Based Specification Process.
Example: Specification of a Security Alarm.
4. Cleanroom Software Development.
Box Structure Development.
Clear Box Development.
Clear Box Verification.
Example: The Security Alarm Clear Box.
5. Cleanroom Software Certification.
Benefits of Statistical Testing Based on a Usage Model.
Theoretical Foundations of Statistical Testing.
Statistical Usage Testing in Practice.
Example: Security Alarm.
II. THE CLEANROOM SOFTWARE ENGINEERING REFERENCE MODEL.
6. The Cleanroom Reference Model.
An Introduction to the CRM.
Cleanroom Process Definition Format.
Common Cleanroom Process Elements.
7. Cleanroom Management Processes.
Project Planning Process.
Project Management Process.
Performance Improvement Process.
Engineering Change Process.
8. Cleanroom Specification Processes.
Requirements Analysis Process.
Function Specification Process.
Usage Specification Process.
Architecture Specification Process.
Increment Planning Process.
9. Cleanroom Development Processes.
Software Reengineering Process.
Increment Design Process.
Correctness Verification Process.
10. Cleanroom Certification Processes.
Usage Modeling and Test Planning Process.
Statistical Testing and Certification Process.
11. Cleanroom and the Capability Maturity Model for Software.
The CMM for Software.
Cleanroom Process Mappings to CMM KPAs.
Integrating CRM Technology and CMM Management.
III. A CASE STUDY IN CLEANROOM SOFTWARE ENGINEERING.
12. Satellite Control System Requirements.
The Satellite Control System Case Study.
Satellite Operations Software Requirements.
13. Satellite Control System Black Box Specification.
Black Box Sequence-Based Specification.
Step 1: Define the System Boundary.
Step 2: Enumerate Stimulus Sequences.
Step 3: Analyze Canonical Sequences.
Step 4: Define Specification Functions.
Step 5: Construct the Black Box Tables.
Common Sequence Abstraction Techniques.
14. Satellite Control System State Box Specification.
State Box Specification.
Step 1: Invent the State Data.
Step 2: Construct the State Box Tables.
15. Satellite Control System Clear Box Design.
Clear Box Implementation.
Step 1: Select a High-Level Software Architecture.
Step 2: Select an Implementation for Stimulus Gathering.
Step 3: Select an Implementation for Response Generation.
Step 4: Select an Implementation for the State Data Items.
Step 5: Select an Implementation for Each Entry in the State Box Table.
Step 6: Reorganize the Implementations into Executable Code.
16. Satellite Control System Testing and Certification.
Step 1: Define Certification Plan.
Step 2: Build Model Structure.
Step 3: Determine State Transition Probabilities.
Step 4: Validate the Usage Model.
Step 5: Generate Test Cases, and Execute and Evaluate Results.
What Our Readers Are Saying
Other books you might like