Automated acceptance testing as an agile requirements engineering practice

Proceedings of the Annual Hawaii International Conference on System Sciences

Volumn , Issue , 2012, Pages 5289-5298

  Haugset, Børge ^a   Stålhane, Tor ^a  

^a NORWEGIAN UNIVERSITY OF SCIENCE AND TECHNOLOGY   (Norway)

Author keywords

[No Author keywords available]

Indexed keywords

AGILE MANUFACTURING SYSTEMS; ITERATIVE METHODS; REQUIREMENTS ENGINEERING; SOFTWARE DESIGN; SOFTWARE TESTING;

AUTOMATED ACCEPTANCE TESTING; DEVELOPMENT METHOD; INHERENT RISK; TEST DRIVEN DEVELOPMENT;

ACCEPTANCE TESTS;

EID: 84857938104     PISSN: 15301605     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/HICSS.2012.127     Document Type: Conference Paper

References (26)

1. R. Mugridge and W. Cunningham, Fit for Developing Software: Framework for Integrated Tests, 1st ed. Prentice Hall, 2005.
2. F. Ricca, M. Di Penta, and M. Torchiano, "Guidelines on the use of Fit tables in software maintenance tasks: Lessons learned from 8 experiments," in Software Maintenance, 2008. ICSM 2008. IEEE International Conference on, 2008, pp. 317-326.
3. B. Haugset and G. K. Hanssen, "The Home Ground of Automated Acceptance Testing: Mature Use of FitNesse," in AGILE Conference (AGILE), 2011, pp. 97-106.
4. B. Ramesh, L. Cao, and R. Baskerville, "Agile requirements engineering practices and challenges: an empirical study," Information Systems Journal, vol. 20, no. 5, pp. 449-480, 2010.
5. Lan Cao and B. Ramesh, "Agile Requirements Engineering Practices: An Empirical Study," Software, IEEE, vol. 25, no. 1, pp. 60-67, 2008.
6. G. K. Hanssen and B. Haugset, "Automated Acceptance Testing Using Fit," presented at the HICSS 2009
7. B. Haugset and G. K. Hanssen, "Automated Acceptance Testing: A Literature Review and an Industrial Case Study," in Agile, 2008 Conference, pp. 27-38.
8. P. Saripalli, "Decision support material for incorporating QR technologies," Masters thesis, NTNU, Trondheim, Norway, 2010.
9. B. Nuseibeh and S. Easterbrook, "Requirements engineering: a roadmap," in Proceedings of the Conference on the Future of Software Engineering, 2000, pp. 35-46.
10. I. Jacobson, M. Christerson, P. Jonsson, and G. Overgaard, Object-oriented software engineering: a use case driven approach. Addison-Wesley, 1992.
11. J. Vanhanen, M. V. Mäntylä, and J. Itkonen, "Lightweight Elicitation and Analysis of Software Product Quality Goals: A Multiple Industrial Case Study," in Proceedings of the 2009 Third International Workshop on Software Product Management, 2009, pp. 42-52.
12. G. Kotonya and I. Sommerville, Requirements engineering. 1998.
13. D. Ang, L. H. Lim, and H. C. Chan, "Collaborative requirements engineering: an overview and a proposed integrated model," in HICSS, 1998, p. 355.
14. F. Paetsch, A. Eberlein, and F. Maurer, "Requirements engineering and agile software development," in Enabling Technologies: Infrastructure for Collaborative Enterprises. WET ICE 2003. Proceedings. Twelfth IEEE International Workshops on, 2003, pp. 308-313.
15. G. I. Melnik, "Empirical analyses of executable acceptance test driven development," University of Calgary, 2007.
16. S. Ambler, "Beyond functional requirements on agile projects," Dr. Dobb's Journal, vol. 33, no. 10, pp. 64-66, 2008.
17. G. Melnik, K. Read, and F. Maurer, Suitability of FIT User Acceptance Tests for Specifying Functional Requirements: Developer Perspective, vol. 3134. Springer, 2004.
18. G. Melnik and F. Maurer, The practice of specifying requirements using executable acceptance tests in computer science courses. ACM Press, 2005.
19. P. Gandhi, N. C. Haugen, M. Hill, and R. Watt, "Creating a living specification using FIT documents," in Agile Conference, 2005. Proceedings, 2005, pp. 253-258.
20. G. Melnik and F. Maurer, Multiple Perspectives on Executable Acceptance Test-Driven Development, vol. 4536. SPRINGER-VERLAG, 2007.
21. F. Ricca, M. Torchiano, M. Di Penta, M. Ceccato, and P. Tonella, "Using acceptance tests as a support for clarifying requirements: A series of experiments," Information and Software Technology, vol. 51, no. 2, pp. 270-283, Feb. 2009.
22. S. Park and F. Maurer, "Communicating Domain Knowledge in Executable Acceptance Test Driven Development," in Agile Processes in Software Engineering and Extreme Programming, 2009, pp. 23-32.
23. R. Mugridge and E. Tempero, "Retrofitting an Acceptance Test Framework for Clarity," in Proceedings of the Conference on Agile Development, 2003, p. 92.
24. G. Melnik, F. Maurer, and M. Chiasson, "Executable acceptance tests for communicating business requirements: customer perspective," in Agile Conference, 2006, 2006, p. 12 pp.
25. S. L. Star and J. R. Griesemer, "Institutional ecology, 'translations' and boundary objects: Amateurs and professionals in Berkeley's Museum of Vertebrate Zoology, 1907-39," Social studies of science, vol. 19, no. 3, pp. 387-420, 1989.
26. P. R. Carlile, "A pragmatic view of knowledge and boundaries: Boundary objects in new product development," Organization science, pp. 442-455, 2002.