1 / 7

Cleanroom software development

Cleanroom software development. Spend a lot of effort "up-front" to prevent defects Formal specification Incremental development Statistical methods to ensure reliability. Cleanroom Process. Formal specification using a state transition model

galena
Download Presentation

Cleanroom software development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Cleanroom software development • Spend a lot of effort "up-front" to prevent defects • Formal specification • Incremental development • Statistical methods to ensure reliability Ch. 19 - Cleanroom Development

  2. Cleanroom Process • Formal specification using a state transition model • Structured programming - limited control and abstraction constructs are used • Program resembles state machine • Static verification using rigorous inspections • Mathematical arguments • Statistical testing of the system reliability [Ch. 21]. Ch. 19 - Cleanroom Development

  3. Cleanroom Process Ch. 19 - Cleanroom Development

  4. Cleanroom Process • Incremental development • Allows freezing of requirements, so formal work can proceed • Work on critical functionality in early revisions, so it receives the most testing Ch. 19 - Cleanroom Development

  5. Cleanroom Process • Specification team. Develop and maintain system specification • Development team. Develop and verify (mathematically) the software. The software is not executed or even compiled during this process • Certification team. Develop set of statistical tests to exercise the software after development. Reliability growth models [Ch.21] used to determine when reliability is acceptable Ch. 19 - Cleanroom Development

  6. Test Results • Successful in the field [Cobbs and Mills 1990] • Few errors • Not more expensive than other processes • Generally workable [Selby et. al. 1987] • Higher quality code resulted Ch. 19 - Cleanroom Development

  7. Deployment • Has been successfully used with highly-trained motivated engineers, at IBM, where process was developed • Can it work with less highly-skilled/motivated engineering teams? Ch. 19 - Cleanroom Development

More Related