References

** Exploratory Testing, Cem Kaner, Florida Institute of Technology, Quality Assurance Institute Worldwide Annual Software Testing Conference, Orlando, FL, November 2006

** Software errors cost U.S. economy $59.5 billion annually, NIST report

** ^a b c Kaner, Cem; Falk, Jack and Nguyen, Hung Quoc (1999). Testing Computer Software, 2nd Ed.. New York, et al: John Wiley and Sons, Inc., 480 pages. ISBN 0-471-35846-0.

** ^a b Section 1.1.2, Certified Tester Foundation Level Syllabus, International Software Testing Qualifications Board

** 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. Gelperin, D.; B. Hetzel (1988). "The Growth of Software Testing". CACM 31 (6). ISSN 0001-0782.

** Principle 2, Section 1.3, Certified Tester Foundation Level Syllabus, International Software Testing Qualifications Board

** Tran, Eushiuan (1999). "Verification/Validation/Certification", in Koopman, P.: Topics in Dependable Embedded Systems. USA: Carnegie Mellon University. Retrieved on 2008-01-13.

** see D. Gelperin and W.C. Hetzel

** Myers, Glenford J. (1979). The Art of Software Testing. John Wiley and Sons. ISBN 0-471-04328-1.

** Gelperin, D.; B. Hetzel (1988). "The Growth of Software Testing". CACM 31 (6). ISSN 0001-0782.

** until 1956 it was the debugging oriented period, when testing was often associated to debugging: there was no clear difference between testing and debugging.Gelperin, D.; B. Hetzel (1988). "The Growth of Software Testing". CACM 31 (6). ISSN 0001-0782.

** 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. Gelperin, D.; B. Hetzel (1988). "The Growth of Software Testing". CACM 31 (6). ISSN 0001-0782.

** The time between 1979-1982 is announced as the destruction oriented period, where the goal was to find errors. Gelperin, D.; B. Hetzel (1988). "The Growth of Software Testing". CACM 31 (6). ISSN 0001-0782.

** 1983-1987 is classified as the evaluation oriented period: intention here is that during the software lifecycle a product evaluation is provided and measuring quality. Gelperin, D.; B. Hetzel (1988). "The Growth of Software Testing". CACM 31 (6). ISSN 0001-0782.

** 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. Gelperin, D.; B. Hetzel (1988). "The Growth of Software Testing". CACM 31 (6). ISSN 0001-0782.

** Laycock, G. T. (1993). "The Theory and Practice of Specification Based Software Testing" (PostScript). Dept of Computer Science, Sheffield University, UK.Retrieved on 2008-02-13.

** Bach, James (June 1999). "Risk and Requirements-Based Testing". Computer 32 (6): pp. 113-114. Retrieved on 2008-08-19.

** Introduction, Code Coverage Analysis, Steve Cornett

** e)Testing Phase in Software Testing:-

** Myers, Glenford J. (1979). The Art of Software Testing. John Wiley and Sons, 145-146. ISBN 0-471-04328-1.

** Dustin, Elfriede (2002). Effective Software Testing. Addison Wesley, 3. ISBN 0-20179-429-2.

** Binder, Robert V. (1999). Testing Object-Oriented Systems: Objects, Patterns, and Tools. Addison-Wesley Professional, 45. ISBN 0-201-80938-9.

** Beizer, Boris (1990). Software Testing Techniques, Second Edition, pp.21,430. ISBN 0-442-20672-0.

** IEEE (1990). IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries. New York: IEEE. ISBN 1559370793.

** Kaner, Cem; James Bach, Bret Pettichord (2001). Lessons Learned in Software Testing: A Context-Driven Approach. Wiley, 4. ISBN 0-471-08112-4.

** McConnell, Steve (2004). Code Complete, 2nd edition, Microsoft Press, 960. ISBN 0-7356-1967-0.

** IEEE (1998). IEEE standard for software test documentation. New York: IEEE. ISBN 0-7381-1443-X.

** Pan, Jiantao (Spring 1999), "Software Testing (18-849b Dependable Embedded Systems)", Topics in Dependable Embedded Systems, Electrical and Computer Engineering Department, Carnegie Mellon University

** context-driven-testing.com

** [http://www.technicat.com/writing/process.html Article on taking agile traits without the agile method.

** IEEE article about differences in adoption of agile trends between experienced managers vs. young students of the Project Management Institute. See alsoAgile adoption study from 2007

** Agile software development practices slowly entering the military

** IEEE article on Exploratory vs. Non Exploratory testing

** An example is Mark Fewster, Dorothy Graham: Software Test Automation. Addison Wesley, 1999, ISBN 0-201-33140-3. See also Studies on automatic vs. manual testing

** Article referring to other links questioning the necessity of unit testing

** Microsoft Development Network Discussion on exactly this topic

** Kaner, Cem (2001). "NSF grant proposal to "lay a foundation for significant improvements in the quality of academic and commercial courses in software testing"" (pdf).

** Kaner, Cem (2003). "Measuring the Effectiveness of Software Testers" (pdf).

** Quality Assurance Institute

** International Institute for Software Testing

** K. J. Ross & Associates

** International Institute for Software Testing

** ^a b "ISTQB".

** ^a b "ISTQB in the U.S.".

** ALATS

** American Society for Quality

** Quality Assurance Institute

** American Society for Quality