54 ;;Quote: real-time program of 27 KLOCs with two customer-reported failures in first full year of continuous operation

54 ;;Quote: near zero software failures by testable requirements, testable software, designing tests before coding, design and code reviews

57 ;;Quote: requirements necessary for good design and tests

57 ;;Quote: good requirements are testable, unambiguous, unique, and use visible inputs and outputs

57 ;;Quote: a good design is made of building blocks which are separately testable

57 ;;Quote: tests should exercise all requirements for input values which are likely to cause failure; e.g., boundary conditions

58 ;;Quote: requirements: standard format, checklist, models, avoid paragraphs, user's vocabulary from a data and function dictionary

58+ ;;Quote: probable errors by testing boundaries + - one, normal, abnormal, and troublesome

58 ;;Quote: create tests before coding so that programmers will design out the most-probable errors

59 ;;Quote: 1509 pages of program design for 700 pages of test plans, 25k of FORTRAN and assembly code, 25k of comments

60 ;;Quote: independent testing found a bug only after severely straining the system

61 ;;Quote: after continuous operation of software at nine additional sites, 11 failures were reported