Cleanroom software engineering

<h2 id="history">History</h2>
<p>The cleanroom process was originally developed by <a href="/facts/Harlan_Mills/vwoXQcgB">Harlan Mills</a> and several of his colleagues including Alan Hevner at <a href="/facts/IBM/QszA7nwd">IBM</a>.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a>
</p><p>The cleanroom process first saw use in the mid to late 1980s. Demonstration projects within the military began in the early 1990s.<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> Recent work on the cleanroom process has examined fusing cleanroom with the automated verification capabilities provided by specifications expressed in <a href="/facts/Communicating_sequential_processes/bzKGnJ50">CSP</a>.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a>
</p>
<h2 id="philosophy">Philosophy</h2>
<p>The focus of the cleanroom process is on defect prevention rather than defect removal. The name "cleanroom" was chosen to evoke the <a href="/facts/Cleanroom/qa97Ff9p">cleanrooms</a> used in the <a href="/facts/Electronics_industry/YX8VCvKC">electronics industry</a> to prevent the introduction of defects during the fabrication of <a href="/facts/Semiconductor/zFf3mGTE">semiconductors</a>.
</p>
<h2 id="central-principles">Central principles</h2>
<p>The basic principles of the cleanroom process are
</p>
Software development based on <a href="/facts/Formal_methods/tw4FCWIb">formal methods</a>
Software tool support based on some mathematical formalism includes <a href="/facts/Model_checking/FwvKMlw9">model checking</a>, <a href="/facts/Process_algebras/RmAEJ2tN">process algebras</a>, and <a href="/facts/Petri_nets/BK7eTHNm">Petri nets</a>. The Box Structure Method might be one such means of specifying and designing a software product.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a> Verification that the design correctly implements the specification is performed through team review, often with software tool support.
Incremental implementation under <a href="/facts/Statistical_quality_control/Qwkqg5d4">statistical quality control</a>
Cleanroom development uses an <a href="/facts/Iterative_and_incremental_development/wqT31VIC">iterative</a> approach, in which the product is developed in increments that gradually increase the implemented functionality. The quality of each increment is measured against pre-established standards to verify that the development process is proceeding acceptably. A failure to meet quality standards results in the cessation of testing for the current increment and a return to the design phase.
Statistically sound <a href="/facts/Software_testing/VoXzG9Tb">testing</a>
Software testing in the cleanroom process is carried out as a statistical experiment. Based on the formal specification, a representative subset of software input/output trajectories is selected and tested. This sample is then statistically analyzed to produce an estimate of the reliability of the software and a level of confidence in that estimate.

<h2 id="further-reading">Further reading</h2>
<ul><li>Stavely, Allan (1999). <i>Toward Zero-Defect Programming</i>. Addison-Wesley.</li>
<li>Stacy J. Prowell and Carmen J. Trammell and Richard C. Linger and Jesse H. Poore (1999). <i>Cleanroom Software Engineering: Technology and Process</i>. Addison-Wesley.</li>
<li>Jesse H. Poore and Carmen J. Trammell (1996). <i>Cleanroom Software Engineering: A Reader</i>. NCC Blackwell.</li></ul>
<h2 id="external-links">External links</h2>
<ul><li><a href="http://www.uta.edu/cse/levine/fall99/cse5324/cr/clean/page1.html">An introduction</a></li></ul>

<h2 id="references">References</h2>

<ol>
<li id="fn:1"><p>Mills, H.; M. Dyer; R. Linger (September 1987). "Cleanroom Software Engineering" (PDF). IEEE Software. 4 (5): 19–25. doi:10.1109/MS.1987.231413. S2CID 383170. <a href="/wiki/Harlan_Mills" target="_blank">/wiki/Harlan_Mills</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li>
<li id="fn:2"><p>Foreman, John (2005). "Cleanroom Software Engineering Reference". Software Technology Roadmap. Software Engineering Institute (SEI). Retrieved 2006-04-27. <a href="http://www.sei.cmu.edu/library/abstracts/reports/96tr022.cfm" target="_blank">http://www.sei.cmu.edu/library/abstracts/reports/96tr022.cfm</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li>
<li id="fn:3"><p>Guy H. Broadfoot and P. J. Hopcroft (2005). "Introducing formal methods into industry using Cleanroom and CSP". Dedicated Systems e-Magazine. S2CID 14066854. {{cite journal}}: Cite journal requires |journal= (help) <a href="/wiki/S2CID_(identifier)" target="_blank">/wiki/S2CID_(identifier)</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li>
<li id="fn:4"><p>Linger, R. (April 1994). "Cleanroom Process Model". IEEE Software. 11 (2): 50–58. CiteSeerX 10.1.1.130.8642. doi:10.1109/52.268956. S2CID 206447346. <a href="/wiki/CiteSeerX_(identifier)" target="_blank">/wiki/CiteSeerX_(identifier)</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li>
</ol>

Cleanroom software engineering open-in-new

Cleanroom software engineering