Skip to main content

Requirement-Based Testing - Extracting Logical Test Cases from Requirement Documents

  • Conference paper
  • First Online:
Software Quality: Methods and Tools for Better Software and Systems (SWQD 2018)

Part of the book series: Lecture Notes in Business Information Processing ((LNBIP,volume 302))

Included in the following conference series:

Abstract

Much has been written on the subject of model-based testing, i.e. taking the test cases from the system model. The prerequisite to that is that the testers have access to a design model, preferably in UML. Less has been published on the subject of requirement-based testing, i.e. taking the test cases directly from the requirement document, which is usually some structured text. Model-based testing has, to a certain extent, already been automated. Tools process the model XMI schema to extract logical test cases or test conditions as they are referred to in the ISO Standard-29119. There has yet to be any tools to extract test cases from requirement documents since this entails natural language processing and presupposes the marking up of the documents. The author began his research in this field already in 2003 while working as tester in a large scale financial services project in Vienna. There he was able to generate several thousand logical test cases and store them in the project test case database. His first internationally published paper on the subject was at the QSIC Conference in 2007. Since then he has published another five papers on the subject, alone and with others. At the heart of this approach is a text analysis tool named TestSpec which processes both English and German language requirement texts. The tool has been used in several projects to set up a logical test case database and to determine the extent of the planned system test. By counting the number of test conditions contained in the requirements text, it is possible to better estimate test effort. In all cases it proves to be helpful to testers in recognizing and defining test cases. It saves the effort involved in manually scanning through large text documents often containing several hundred pages in search of features to be tested. What used to take many days can now be done within a few minutes with the help of the tool. Not only that, but the tool also generates a test plan and a test specification in accordance with the ISO/IEEE standard. In this paper the automated approach to extracting test conditions from natural language text is explained and how it is implemented by the tool. In this praxis-oriented paper four test projects are cited which deal with very different types of requirement documents.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

References

  1. Sneed, H.: Testing against natural language requirements. In: 7th IEEE International Conference on Software Quality, QSIC 2007, Portland, p. 380, October 2007

    Google Scholar 

  2. Badni, M., Badni, L., Flageol, W.: On the relationship between use cases and test suite size. ACM SIGSOFT Softw. Eng. Notes 38(4), 1 (2013)

    Google Scholar 

  3. Roßner, T., Brandes, C., Götz, H., Winter, M.: Basiswissen – Modellbasierter Test. Dpunkt verlag, Heidelberg (2010)

    Google Scholar 

  4. Davis, A.: Software Requirements – Analysis and Specification. Prentice-Hall, Englewood Cliffs (1990)

    Google Scholar 

  5. Miriyala, K., Harandi, M.: Automatic derivation of formal software specifications from informal descriptions. IEEE Trans. S.E. 17(10), 1126 (1991)

    Article  Google Scholar 

  6. Poston, R.: “Action-Driven Test Case Design” in Tutorial: Automating Specification – Based Software Testing. IEEE Press, Los Alamitos (1996). p. 47

    Google Scholar 

  7. Daigl, M., Glunz, R.: ISO-29119 – Softwaretest Normen verstehen und anwenden. Dpunkt verlag, Heidelberg (2016)

    Google Scholar 

  8. Potts, C., Takahashi, K., Anton, A.: Inquiry-based requirements analysis. IEEE Softw. 12(2), 21 (1994)

    Article  Google Scholar 

  9. Bach, J.: Reframing requirements analysis. IEEE Comput. 32(6), 113 (2000)

    MathSciNet  Google Scholar 

  10. Miller, T.W.: Data and Text Mining – A Business Application Approach. Prentice-Hall, Upper Saddle River (2005)

    Google Scholar 

  11. Haumer, P., Pohl, K., Weidenhaupt, K.: Requirement elicitation and validation with real world scenarios. IEEE Trans. S.E. 24(12), 1089 (1998)

    Article  Google Scholar 

  12. Swartow, W., Balzer, R.: On the inevitable intertwining of specification and implementation. Comm. ACM 25(7), 438 (1982)

    Article  Google Scholar 

  13. Davis, A.: System phenotypes. IEEE Softw. 21(4), 54 (2003)

    Article  Google Scholar 

  14. Manning, C., Schütze, H.: Foundations of Statistical Natural Language Processing. MIT Press, Cambridge (1999)

    MATH  Google Scholar 

  15. Beizer, B.: Software Testing Techniques, p. 107. van Nostrand Reinhold, New York (1983)

    Google Scholar 

  16. Sneed, H., Seidl, R., Baumgartner, M.: Der Systemtest. Hanser Verlag, München-Wien (2008)

    Google Scholar 

  17. Fraser, M., Kumar, K., Vaisnavi, V.: Informal and fomal requirement specification languages – bridging the gap. IEEE Trans. S.E. 17(5), 454 (1991)

    Article  Google Scholar 

  18. Sneed, H.: Bridging the concept to implementation gap in software system testing. In: Proceedings of IEEE QSIC Conference, Oxford, G.B., p. 56, August 2008

    Google Scholar 

  19. Sneed, H.: Testing an eGovernment website. In: Proceedings of the WSE 2005, Budapest, p. 3. IEEE Computer Society Press, September 2005

    Google Scholar 

  20. Peters, R., Parnas, D.: Using test oracles generated from program documentation. IEEE Trans S.E. 28(2), 146 (2002)

    Article  Google Scholar 

  21. Friske, M.: Testfallerzeugung aus Use-Case Beschreibungen. GI Softwaretechnik Trends 24(3), 20 (2004)

    Google Scholar 

  22. Friske, M., Pirk, H.: Werkzeuggestützte interactive Formalisierung textueller Anwendungsbeschreibungen für den Systemtest. GI Softwaretechnik Trends 35(1), 27 (2015)

    Google Scholar 

  23. Felderer, M., Beer, A.: Eine industriell erprobte Methode für den Review und Test von Anforderungen mit Hilfe von Fehlertaxonomien. GI Softwaretechnik Trends 34(1), 5 (2014)

    Article  Google Scholar 

  24. Ramamoorthy, C.V., Ho, S.F.: Testing large software systems with automated software evaluation systems. IEEE Trans. S.E. 1(1), 51 (1975)

    Google Scholar 

  25. https://www.tutorialpoint.com/software_testing_dictionary/requirements_based_testing.htm

  26. Magorodi, G.: What is requirements-based testing? Bloodworth Integrated Technologies, March 2003

    Google Scholar 

  27. Offutt, J., Xiong, Y., Liu, S.: Criteria for generating specification-based tests. In: Proceedings of the of 5th IEEE International Conference on Engineering of Complex Computer Systems, p. 72, October 1999

    Google Scholar 

  28. Wilson, W., et al.: Automated quality analysis of natural language requirement specifications. In: 19th International Conference on Software Engineering, ICSE 2007, Montreal, May 2007, p. 158 (1997)

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Harry M. Sneed .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2018 Springer International Publishing AG

About this paper

Check for updates. Verify currency and authenticity via CrossMark

Cite this paper

Sneed, H.M. (2018). Requirement-Based Testing - Extracting Logical Test Cases from Requirement Documents. In: Winkler, D., Biffl, S., Bergsmann, J. (eds) Software Quality: Methods and Tools for Better Software and Systems. SWQD 2018. Lecture Notes in Business Information Processing, vol 302. Springer, Cham. https://doi.org/10.1007/978-3-319-71440-0_4

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-71440-0_4

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-71439-4

  • Online ISBN: 978-3-319-71440-0

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics