Cleanroom: A Superior Software Development Process Jim Stambaugh 11/29/2006

Cleanroom Principles Software development based on formal methods Software development based on formal methods formal methods are mathematically-based techniques for the specification, development and verification of software formal methods are mathematically-based techniques for the specification, development and verification of software Uses team review Uses team review Incremental implementation under statistical quality control Incremental implementation under statistical quality control Uses an iterative approach Uses an iterative approach Measured against pre-established standards Measured against pre-established standards Statistically sound testing Statistically sound testing A representative subset is tested and statistically analyzed A representative subset is tested and statistically analyzed

Cleanroom: Ethical Benefits A software development process effects: Project cost Project cost Time Time Deadlines Deadlines Overtime Overtime Profit Profit Quality Quality Choices that may occur: Profit vs Bug Fixes Profit vs Bug Fixes Money vs Safety Money vs Safety Time vs Testing Time vs Testing Deadline vs Quality Deadline vs Quality

Cleanroom: Ethical Benefits Using the Cleanroom software development processes creates quality software from the beginning. Cleanroom assures that the project will likely be: on budget on budget on time on time of high quality of high quality This prevents management from having to make any of the common ethical decisions that occurs when using another software development process.

Conclusion The higher upfront cost greatly outweigh the longer term benefits of: Quality software Quality software Near bug free code Near bug free code Flexibility Flexibility Dependability Dependability Predictability of: Predictability of: Deadlines Deadlines Costs Costs Lack of ethical decisions Lack of ethical decisions Happy Customers! Happy Customers!