Executable acceptance tests for communicating business requirements: Customer perspective

Proceedings - AGILE Conference, 2006

Volumn 2006, Issue , 2006, Pages 35-46

  Melnik, Grigori ^a   Maurer, Frank ^a   Chiasson, Mike ^b  

^a UNIVERSITY OF CALGARY   (Canada)

^b LANCASTER UNIVERSITY   (United Kingdom)

Author keywords

[No Author keywords available]

Indexed keywords

ADMINISTRATIVE DATA PROCESSING; CUSTOMER SATISFACTION; INFORMATION TECHNOLOGY; SOFTWARE ENGINEERING;

ACCEPTANCE TESTS; BUSINESS REQUIREMENTS; USAGE OBSERVATIONS;

INDUSTRIAL MANAGEMENT;

EID: 34247561407     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/AGILE.2006.26     Document Type: Conference Paper

References (31)

1. Acceptance Test. Online: http://c2.com/cgi/wiki?AcceptanceTest
2. Alexander, I. "Initial industrial experience of misuse cases in trade-off analysis", Proc. IEEE Int. Conf. on Requirements Engineering (RE'02), IEEE Press: 61-68, 2002.
3. Alexander, I. "Positive Results from Negative Scenarios". Pres. for IDEX Project Challenge, May 2002. Online: http://easyweb. easynet.co.uk/~iany/consultancy/negative_scenarios.ppt
4. Bache, G. "What is Acceptance Testing?" Online: http://texttest.carmen.se/AcceptanceTesting/
5. Basili, V.R. "The Role of Experimentation in Software Engineering: Past, Current, and Future"; Proc. 18th Int. Conf. on Software Engineering, IEEE Press: 442-449, 1996.
6. Beck, K. Extreme Programming Explained: Embrace Change, 1/e. Addison-Wesley, Boston, MA, 1999.
7. th Annual Workshop of the Psychology of Programming Interest Group (PPIG-11): 24-35, 1999.
8. Buwalda, H. "Soap Opera Testing". Better Software, 6(2): 30-37, 2004.
9. Chaos Report. The Standish Group, West Yarmouth, MA, 1995, 1997, 1999, 2001, 2003.
10. Cohn, M. "Do-It-Yourself, Better Software, 7(9): 18-22, 2005.
11. Department of Defense. Military Standard Defense System Software Development DOD-STD-2167, section.5.3.3. Online: http://www2.umassd.edu/ SWPI/DOD/MIL-STD-2167A/DOD2167A.html.
12. FIT: The Framework for Integrated Testing Documentation. Online: http://fit.c2.com/wiki.cgi?FitDocumentation
13. FitNesse Documentation. Online: http://www.fitnesse.org/FitNesse. UserGuide
14. Fowler, M. "Specification by Example". Online: http://www.martinfowler.com/bliki/SpecificationByExample.html
15. Green, T.R.G. Cognitive dimensions of notations. In A. Sutcliffe & L. Macaulay (Eds.), People and Computers V. Cambridge University Press: 1989.
16. Institute of Electrical and Electronics Engineers. IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries. New York, NY: 1990.
17. Jeffries, R. "What is XP?" Online: http://www.XProgramming.com/ xpmag/whatisXP.htm
18. Kaner, C. "Cem Kaner on Scenario Testing: The Power of 'What-If...' and Nine Ways to Fuel Your Imagination", Better Software, 5(5):16-22, 2003.
19. Kaner, C. "What is a Good Test Case?" STAR East Conf. 2003, May 2003. Online: http://www.testingeducation.org/a/testcase.pdf
20. Kerievsky, J. "Storytesting". Online: http://industrialxp.org/ storytesting.html
21. Marick, B. "Example-Driven Development". Online: http://www.exampler.com, and http://www.testing.com/cgi-bin/blog/2003/09/ 05#agile-testing-project-4
22. Marick, B. Agile Acceptance Testing Workshop Report, XP/Agile Universe 2002 Conf. Online: http://www.pettichord.com/XP_Agile_Universe_trip_report. txt
23. Melnik, G., Read, K., and Maurer, F. "Suitability of FIT User Acceptance Tests for Specifying Functional Requirements: Developer Perspective". Proc. XP/Agile Universe 2004, LNCS, Vol. 3134, Springer Verlag: 60-72, 2004.
24. Meyer, B. "On Formalism in Specifications". IEEE Software, 2(1): 6-26, 1985.
25. Mugridge, R., and Cunningham, W. FIT for Developing Software: Framework for Integrated Tests, Prentice Hall, Upper Saddle River, NJ: 2005.
26. Perry, W. Effective Methods for Software Testing, 2/e, John Wiley & Sons: New York, NY, 2000.
27. Raha, S. Comment in [29], p. 19.
28. Read, K., Melnik, G., and Maurer, F. "Examining Usage Patters of the FIT Acceptance Testing Framework". Proc. XP2005, LNCS, Vol. 3556, Springer Verlag: 127-136, 2005.
29. Reppert, T. "Don't Just Break Software, Make Software: How Story-Test-Driven-Development is Changing the Way QA, Customers, and Developers Work". Better Software, 6(6): 18-23, 2004.
30. Sepulveda, C. "XP and Customer Tests: Is It Fair?" Online: http://christiansepulveda.com/blog/archives/cat_software_development.html
31. Shadish, W.R., Cook, T.D., and Campbell, D.T. Experimental and Quasi-Experimental Designs for Generalized Causal Inference. Houghton Mifflin, 2002.