10 ;;Quote: developed COBOL/SF (for structuring programs) with Cleanroom techniques; 80K lines; field test found 10 simple errors

10+;;Quote: Cleanroom development with statistical quality control, mathematical verification, no unit debugging, incremental development, change control

11 ;;Quote: COBOL/SF used a Cleanroom software team of 8 people plus 3 summer students; first software development project for all but two people

11 ;;Quote: COBOL/SF development by Cleanroom methods meet all schedules and budgets; all committed functions were delivered

12 ;;Quote: Cleanroom places programs under engineering change control before first execution; for reliable statistics

12+;;Quote: Cleanroom uses successive times between execution failure to estimate reliability

13 ;;Quote: Cleanroom uses box structures for specification; before design starts, everyone must agree that the specification is correct

13 ;;Quote: Cleanroom designs are constructed by decomposing a specified function into control structures and subspecifications; never bottom-up

14 ;;Quote: a Cleanroom objective was simplifying designs; sometimes achieved a five-fold reduction in size

14 ;;Quote: in Cleanroom, used intensive team reviews to verify two formal grammars of 1500 productions each; no grammar errors found in field testing

14 ;;Quote: traditional design inspection uses mental program execution; needs long term memory, non-local reasoning, virtually infinite number of paths

15 ;;Quote: function-theoretic design verification for verifying successive function decompositions into control structures and subfunctions

15 ;;Quote: using function-theoretic design verification, a team review checked 1200 correctness questions in a few days; astonishing savings during test

15 ;;Quote: Cleanroom designs are mapped statement-to-statement into PL/1; automated

15+;;Quote: coding a Cleanroom design must follow the design exactly

16 ;;Quote: under Cleanroom, high quality code rapidly becomes error free; expect defect free within a day or two of first execution

16+;;Quote: Cleanroom estimates the user input distribution to generate test cases

16 ;;Quote: in Cleanroom, the primary function of testing is to certify code, not debug it; reject if 7-8 errors/KLOC

16 ;;Quote: in Cleanroom, the team's goal was error-free code for an increment; occurred many times; high satisfaction and motivation