Apply the software engineering and testing terminology from this chapter to the following terms used in Feynman’s article mentioned in the introduction:

What will be an ideal response?

• What is a “crack”? [error]
• What is “crack initiation”? [error introduction]
• What is “high engine reliability”? [high component reliability]
• What is a “design aim”? [design goal or a nonfunctional requirement]
• What is a “mission equivalent”? [the operation of the engine for 500 continuous seconds, either during a
mission or during a test; this term has no equivalent in the testing chapter]
• What does “10 percent of the original specification” mean? [the achieved lifetime of the engine is a tenth
of the original goal, that is, instead of having a lifetime of 55 mission equivalents, it has a life time of 5.5
mission equivalents]
• How is Feynman using the term “verification,” when he says that “As deficiencies and design errors are
noted they are corrected and verified with further testing”? [In this context, verification means the
accumulation of sufficient experimental evidence to convince the designers that an error has been
corrected; in software engineering, verification is the development of a proof using formal methods to
achieve the same goal]