Evolving Test Patterns for Use Case Maps

  • P. G. Sapna
  • Hrushikesha Mohanty
  • Arunkumar Balakrishnan
Part of the Communications in Computer and Information Science book series (CCIS, volume 204)


An important aspect of software testing today is the ability to seamlessly move from analysis models to generating test scenarios and test cases. Use Case Maps(UCMs) are a scenario-based software engineering technique used at early stages of software development. The notation is most suited to capturing and eliciting use cases as well as high-level architectural design and for test case generation. Test patterns provide established solutions for designing tests or for supporting the testing process. In this work, we define test patterns based on the the primitives of the Use Case Maps to aid the process of test scenario generation.


Test Pattern Test Case Generation Business Process Execution Language Business Process Modeling Notation Parallel Branch1 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Amyot, D.: Specification and Validation of Telecommunications Systems with Use Case Maps and LOTOS, Ph.D. thesis, SITE, University of Ottawa, Canada (September 2001)Google Scholar
  2. 2.
    Amyot, D., Logrippo, L., Weiss, M.: Generation of test purposes from Use Case Maps. Computer Networks (2005)Google Scholar
  3. 3.
    Wang, L., Yuan, J., Yu, X., Hu, J., Li, X., Zheng, G.: Generating Test Cases from UML Activity Diagram based on Gray-Box Method. In: Proceedings of the 11th Asia-Pacific Software Engineering Conference (APSEC). IEEE Computer Society, Los Alamitos (2004)Google Scholar
  4. 4.
    Binder, R.V.: Testing Object-Oriented Systems Models, Patterns, and Tools. Addison Wesley, Reading (1999)Google Scholar
  5. 5.
    Mussbacher, G.: Evolving Use Case Maps as a Scenario and Workflow Description Language. In: 10th Workshop of Requirement Engineering (WER 2007), pp. 56–67 (2007)Google Scholar
  6. 6.
    Larman, C.: Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process, 2nd edn. Prentice Hall, Englewood Cliffs (2001)Google Scholar
  7. 7.
    Amyot, D., Eberlein, A.: An Evaluation of Scenario Notations and Construction Approaches for Telecommunication Systems Development. Telecommunications Systems Journal 24(1), 61–94 (2003)CrossRefGoogle Scholar
  8. 8.
    Amyot, D., He, X., He, Y., Cho, D.Y.: Generating Scenarios from Use Case Map Specifications. In: 3rd International Conference on Quality Software (QSIC), pp. 108–115 (2003)Google Scholar
  9. 9.
    Beizer, B.: Software Testing Techniques. Dreamtech Press (2002)Google Scholar
  10. 10.
    Roy, J.-F., Kealey, J., Amyot, D.: Towards Integrated Tool Support for the User Requirements Notation. In: Gotzhein, R., Reed, R. (eds.) SAM 2006. LNCS, vol. 4320, pp. 198–215. Springer, Heidelberg (2006)CrossRefGoogle Scholar
  11. 11.
    Kealey, J., Amyot, D.: Enhanced Use Case Map Traversal Semantics. In: Gaudin, E., Najm, E., Reed, R. (eds.) SDL 2007. LNCS, vol. 4745, pp. 133–149. Springer, Heidelberg (2007)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • P. G. Sapna
    • 1
  • Hrushikesha Mohanty
    • 2
  • Arunkumar Balakrishnan
    • 1
  1. 1.Coimbatore Institute of TechnologyCoimbatoreIndia
  2. 2.University of HyderabadHyderabadIndia

Personalised recommendations