Map
Index
Random
Help
th

QuoteRef: lingRC10_1988

topics > all references > ThesaHelp: references i-l



ThesaHelp:
references i-l
Topic:
Cleanroom software development
Topic:
quality assurance
Topic:
software change management
Topic:
statistical testing based on a usage profile
Topic:
requirement specification by diagrams
Group:
program design
Topic:
handling complexity
Group:
program proving
Topic:
software review
Topic:
program proof via assertions
Topic:
executable code from specifications and designs
Topic:
programming without errors
Topic:
automated testing

Reference

Linger, R.C., Mills, H.D., "A case study in Cleanroom software engineering: The IBM COBOL structuring facility ", COMPSAC 88. The 12th Annual International Computer Software and Applications Conference , IEEE Computer Society, October 1988. Google

Quotations
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


Related Topics up

ThesaHelp: references i-l (342 items)
Topic: Cleanroom software development (38 items)
Topic: quality assurance (20 items)
Topic: software change management (48 items)
Topic: statistical testing based on a usage profile (27 items)
Topic: requirement specification by diagrams (27 items)
Group: program design   (13 topics, 453 quotes)
Topic: handling complexity (59 items)
Group: program proving   (10 topics, 310 quotes)
Topic: software review (80 items)
Topic: program proof via assertions (61 items)
Topic: executable code from specifications and designs (18 items)
Topic: programming without errors (28 items)
Topic: automated testing (24 items)

Collected barberCB 7/90
Copyright © 2002-2008 by C. Bradford Barber. All rights reserved.
Thesa is a trademark of C. Bradford Barber.