Cleanroom software engineering – a description Kaur Gurvinder*, Lecturer, Jain Bhawna**, Lecturer *Guru Nanak Khalsa Institute of Technology and Management Studies, Yamuna Nagar **Tecnia Institute of Advanced Studies, New Delhi Online published on 19 October, 2011. Abstract With Cleanroom Software Engineering software quality could be verified with the completion of a project. The philosophy behind cleanroom software engineering is to develop code increments and verify their correctness before testing, rather than relying on costly defect removal processes. This cleanroom method ensures high quality software with certified reliability, which is an important aspect of every software product. Through this paper it is highlighted that cleanroom software engineering uses some techniques like the integrated use of software engineering modeling, program verification, and statistical software quality assurance. It also throws light when cleanroom combines mathematically-based methods of software specification, design, and correctness verification with statistical, usage-based testing to certify software fitness for use. Cleanroom projects reported substantial gains in quality and productivity are also encouraged. This paper gives a brief description of some principles where the user becomes aware how the development of software exhibits zero failures. It emphasizes on the important strategies related to a user which he should keep in his mind while applying Cleanroom software engineering. This paper helps to define the different technologies of clean room software engineering like incremental development, precise specification and design, correctness verification, Statistical quality certification. This paper describes about the process known as fourteen phases of the iterative process which is designed to identify and correct bugs from occurring before the very first run of the software so that the software contains zero or near zero errors. The testing of the software done by a team that is independent of the coding team with mathematical specifications to verify the correctness of the system is also quoted. It is also suggested that the more powerful process of team correctness verification replaces unit testing and debugging, and software enters system testing directly, with no execution by development teams. Top Keywords cleanroom, design, specification, verification. Top |