An Industrial Case Study on Test Cases as Requirements

1. Sommerville, I.: Integrated requirements engineering: a tutorial. IEEE Softw. 22, 16–23 (2005)

   Article  Google Scholar 

2. Layman, L., Williams, L., Cunningham, L.: Motivations and measurements in an agile case study. J. Syst. Archit. 52, 654–667 (2006)

   Article  Google Scholar 

3. Beck, K.: Manifesto for Agile Software Development. http://agilemanifesto.org/

4. Ramesh, B., Cao, L., Baskerville, R.: Agile requirements engineering practices and challenges: an empirical study. Inf. Syst. J. 20, 449–480 (2010)

   Article  Google Scholar 

5. Bjarnason, E., Runeson, P., Borg, M., et al.: Challenges and practices in aligning requirements with verification and validation: a case study of six companies. Empir. Softw. Eng. 19, 1809–1855 (2014)

   Article  Google Scholar 

6. Davis, A.M.: Just Enough Requirements Management: Where Software Development Meets Marketing. Dorset House, New York (2005)

   Google Scholar 

7. van Lamsweerde, A.: Formal specification: a roadmap. In: Conf. on The Future of Software Engineering, pp. 147–159. ACM, Limerick (2000)

   Google Scholar 

8. Pohl, K.: Requirements Engineering - Fundamentals, Principles, and Techniques. Springer, Heidelberg (2010)

   Google Scholar 

9. Mavin, A., Wilkinson, P.: Big ears (the return of “easy approach to requirements engineering”). In: 18^th Int. Reqts. Engineering Conf., pp. 277–282. IEEE, Sydney (2010)

   Google Scholar 

10. Cohn, M.: User Stories Applied: For Agile Software Development. Addison-Wesley Professional, Boston (2004)

    Google Scholar 

11. Heitmeyer, C.L., Jeffords, R.D., Labaw, B.G.: Automated Consistency Checking of Requirements Specifications. ACM Trans. Softw. Eng. Methodol. 5, 231–261 (1996)

    Article  Google Scholar 

12. Dromey, R.G.: From requirements to design: formalizing the key steps. In: 1st Int’l Conf. on Software Engineering and Formal Methods, pp. 2–11. IEEE, Brisbane (2003)

    Google Scholar 

13. Miller, T., Strooper, P.: A case study in model-based testing of specifications and implementations. Softw. Test. Verification Reliab. 22, 33–63 (2012)

    Article  Google Scholar 

14. Davis, A., Overmyer, S., Jordan, K., et al.: Identifying and measuring quality in a software requirements specification. In: 1^st Int. Softw. Metrics Symp., Baltimore, USA, pp. 141–152 (1993)

    Google Scholar 

15. Martin, R.C., Melnik, G.: Tests and Requirements, Requirements and Tests: A Möbius Strip. IEEE Softw. 25, 54–59 (2008)

    Article  Google Scholar 

16. Whittaker, J.A.: What is software testing? And why is it so hard? IEEE Softw. 17, 70–79 (2000)

    Article  Google Scholar 

17. Runeson, P.: A survey of unit testing practices. IEEE Softw. 23, 22–29 (2006)

    Article  Google Scholar 

18. Hsia, P., Kung, D., Sell, C.: Software requirements and acceptance testing. Ann. Softw. Eng. 3, 291–317 (1997)

    Article  Google Scholar 

19. Lethbridge, T.C., Singer, J., Forward, A.: How software engineers use documentation: the state of the practice. IEEE Softw. 20, 35–39 (2003)

    Article  Google Scholar 

20. Haugset, B., Hanssen, G.K.: Automated acceptance testing: a literature review and an industrial case study. In: Agile Conf., pp. 27–38. IEEE, Toronto (2008)

    Google Scholar 

21. Park, S., Maurer, F.: A literature review on story test driven development. In: 11^th Int. Conf. on Agile Processes in Softw. Engin. and Extreme Progr., pp. 208–213 (2010)

    Google Scholar 

22. Melnik, G., Maurer, F., Chiasson, M.: Executable acceptance tests for communicating business requirements: customer perspective. In: IEEE Agile Conf., USA, pp. 35–46 (2006)

    Google Scholar 

23. Causevic, A., Sundmark, D., Punnekkat, S.: Factors limiting industrial adoption of test driven development: a systematic review. In: 4th Int’l Conf. on Software Testing, Verification and Validation, pp. 337–346. IEEE, Berlin (2011)

    Google Scholar 

24. George, B., Williams, L.: A structured experiment of test-driven development. Inf. Softw. Technol. 46, 337–342 (2004)

    Article  Google Scholar 

25. Janzen, D.S., Saiedian, H.: A leveled examination of test-driven development acceptance. In: 29th Int’l Conf. on Software Engineering, pp. 719–722. IEEE, Minneapolis (2007)

    Google Scholar 

26. North, D.: Behavior Modification: The evolution of behavior-driven development (2006)

    Google Scholar 

27. Runeson, P., Höst, M., Rainer, A., Regnell, B.: Case Study Research in Software Engineering: Guidelines and Examples. Wiley, Hoboken (2012)

    Book  Google Scholar 

28. Lauesen, S.: Software Requirements: Styles & Techniques. Addison-Wesley Professional, Harlow (2002)

    Google Scholar 

29. Melnik, G., Maurer, F.: Multiple perspectives on executable acceptance test-driven development. In: Concas, G., Damiani, E., Scotto, M., Succi, G. (eds.) XP 2007. LNCS, vol. 4536, pp. 245–249. Springer, Heidelberg (2007)

    Chapter  Google Scholar 

30. Park, S., Maurer, F.: Communicating domain knowledge in executable acceptance test driven development. In: Abrahamsson, P., Marchesi, M., Maurer, F. (eds.) Agile Processes in Software Engineering and Extreme Programming. LNBIP, vol. 31, pp. 23–32. Springer, Heidelberg (2009)

    Chapter  Google Scholar 

31. Latorre, R.: A successful application of a Test-Driven Development strategy in the industrial environment. Empir. Softw. Eng. 19, 753–773 (2014)

    Article  Google Scholar 

32. Kongsli, V.: Towards agile security in web applications. In: 21^st ACM SIGPLAN Symp. on Object-oriented Progr. Systems, Languages, & Appl., Portland, USA, pp. 805–808 (2006)

    Google Scholar 

33. Mugridge, R.: Managing Agile Project Requirements with Storytest-Driven Development. IEEE Softw. 25, 68–75 (2008)

    Article  Google Scholar 

34. Uusitalo, E.J., Komssi, M., Kauppinen, M., Davis, A.M.: Linking requirements and testing in practice. In: 16^th Int. Conf. Reqts. Engineering, pp. 265–270. IEEE, Catalunya (2008)

    Google Scholar 

Download references