Dr. William C. Hetzel is an expert in the field of software testing. He compiled the papers from the 1972 Computer Program Test Methods Symposium, also known as the Chapel Hill Symposium, into the book Program Test Methods.[1] The book, published in 1973, details the problems of software validation and testing.[2]

The International Conference and Exposition on Testing Computer Software, which is the first conference with a focus on software testing, is convened in 1984 by the US Professional Development Institute (USPDI) in Washington, D.C.[3] Hetzel and Dr. David Gelperin are the joint program chairs.[2]

Hetzel and Dave Gelperin co-found the Software Quality Engineering consultancy firm in 1986. Their motto was, "Test, then code." Together they worked to establish software testing as a stand-alone computer discipline. In 1988 they classified the phases and goals of software testing into the following stages:[4]

  • Until 1956 – Debugging Oriented – Until 1956 it was the debugging oriented period, when testing was often associated to debugging: there was no clear difference between testing and debugging.
  • 1957–1978 – Demonstration Oriented – From 1957–1978 there was the demonstration oriented period where debugging and testing was distinguished now – in this period it was shown, that software satisfies the requirements.
  • 1979–1982 – Destruction Oriented – The time between 1979–1982 is announced as the destruction oriented period, where the goal was to find errors.
  • 1983–1987 – Evaluation Oriented – The years 1983–1987 are classified as the evaluation oriented period: intention here is that during the software lifecycle a product evaluation is provided and measuring quality.
  • 1988–____ – Prevention Oriented – From 1988 on it was seen as prevention oriented period where tests were to demonstrate that software satisfies its specification, to detect faults and to prevent faults.

In 1988 Gelperin and Heztel write the article The Growth of Software Testing. In it they discuss four major models for software testing. The first two are Phase Models, and the second two are Life Cycle Models.[4]

  • Demonstration – To make sure that software satisfies its specification
  • Destruction – To detect implementation faults
  • Evaluation – To detect requirements, design, and implementation faults
  • Prevention – To prevent requirements, design, and implementation faults

Hetzel's book The Complete Guide to Software Testing which provides methodologies, testing techniques, and the principles of software testing, is released in 1988. The book is released in a 2nd edition later the same year, and several other printings are made through 1994.[5]

In 1992 Gelperin and Hetzel firm organized the first "Software Testing, Analysis & Review," the "STAR" conference, in Las Vegas, Nevada and in 1993 introduced a European equivalent, the EuroSTAR Conference.[6][7][8][2] The US-based conferences are now produced by TechWell Corporation which is the new name for their Software Quality Engineering company.

Gelperin and Hetzel developed the STEP methodology for implementing the original IEEE-829-1998 Standard for Software and System Test Documentation.[9] Their firm was instrumental in gaining recognition for testing as a separate discipline within the software industry.[2]

References

  1. ↑ Hetzel, William C., ed. (1973). Program Test Methods. Prentice-Hall. ISBN 9780137296248.
  2. 1 2 3 4 Meerts, Joris. "The History of Software Testing". Testing References. Retrieved 20 November 2016.
  3. ↑ Yourdon, Edward (1992). Decline & Fall of the American Programmer. Yourdon Press. p. 333. ISBN 9780132036702.
  4. 1 2 Gelperin, David; Hetzel, Bill (June 1988). "The Growth of Software Testing". Communications of the ACM. 31 (6): 687–695. doi:10.1145/62959.62965. S2CID 14731341. Retrieved 18 December 2017.
  5. ↑ Hetzel, Bill (June 1988). The Complete Guide to Software Testing (2nd ed.). Wiley. ISBN 978-0471565673.
  6. ↑ Hetzel, Bill (10 May 2017). "Guest Editorial: Bill Hetzel & Cindy Morelli". Software Testing, Verification & Reliability. 5 (3): 141–142. doi:10.1002/stvr.4370050302. S2CID 34030778.
  7. ↑ MacKenzie, Donald (2004). Mechanizing Proof: Computing, Risk, and Trust. MIT Press. p. 42. ISBN 978-0-262-63295-9.
  8. ↑ "Testen Chronologie". Computerwoche. IDG. 9 December 1998. Retrieved 6 January 2010.
  9. ↑ Rick D. Craig; Stefan P. Jaskiel (2002). Systematic Software Testing. Artech House. p. 4. ISBN 978-1-58053-792-6.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.