Management of test scenarios involves ordering and selecting a set of test scenarios for testing with the objective of fulfilling criteria like maximizing coverage or discovering defects as early as possible. To do this, knowledge about the main activities in the domain and the interactions between them need to be maintained. This knowledge helps in categorizing scenarios as per the approaches used for testing. Current approaches to test management involve generating scenarios related to use cases. However, the use case based approach does not capture knowledge about the dependencies that exist among activities in the domain and therefore cannot provide complete information for scenario management. Ontologies provide a mechanism to represent this knowledge. They also provide a means to share and reason on knowledge that is captured. The objective of this work is to use ontologies to aid test management.


UML use case scenario ontology test scenario management 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Antoniou, G., van Harmelen, F.: A Semantic Web Primer. The MIT Press, Cambridge (2004)Google Scholar
  2. 2.
    Bezerra, D., Costa, A., Okada, K.: swtoI (Software Test Ontology Integrated) and its Application in Linux Test. In: Proceedings of Ontose 2009, pp. 25–36 (2009)Google Scholar
  3. 3.
    Dillon, T.S., Chang, E., Wongthongtham, P.: Ontology-based software engineering-software engineering 2.0. In: Proceedings of the 19th Australian Conference on Software Engineering, pp. 13–23. IEEE, Los Alamitos (2008)Google Scholar
  4. 4.
    DuCharme, B.: XSLT Quickly. Manning PublicationsGoogle Scholar
  5. 5.
    Mendes, O., Abran, A., Montral Qubec, H.K.: Software engineering ontology: A development methodology. In: Metrics NewsGoogle Scholar
  6. 6.
    Juristo, N., Ferndandez, M., Gomez-Perez, A.: METHONTOLOGY: From Ontological Art Towards Ontological Engineering. AAAI Technical Report SS-97-06, 15(2) (1997)Google Scholar
  7. 7.
    Mabotuwana, T., Warren, J.: An ontology based approach to enhance querying capabilities of general practice medicine for better management of hypertension. Artificial Intelligence in Medicine (2009)Google Scholar
  8. 8.
    Noy, N.F., McGuinness, D.L.: Ontology Development 101: A Guide to Creating Your First Ontology. Stanford Knowledge Systems Laboratory Technical Report KSL-01-05 and Stanford Medical Informatics Technical Report SMI-2001- 0880, 15(2) (2001)Google Scholar
  9. 9.
    Nguyen, C.D., Perini, A., Tonella, P.: Ontology-based Test Generation for Multiagent Systems. In: AAMAS 2008: Proceedings of the 7th International Joint Conference on Autonomous Agents and Multiagent Systems. International Foundation for Autonomous Agents and Multiagent Systems, pp. 1315–1320 (2008)Google Scholar
  10. 10.
    Andrea Rodriguez, M., Egenhofer, M.J.: Determining semantic similarity among entity classes from different ontologies. IEEE Transactions on Knowledge and Data Engineering 15(2), 442–456 (2003)CrossRefGoogle Scholar
  11. 11.
    Chang, E., Wongthongtham, P., Cheah, C.: Software Engineering Sub Ontology for Specific Software Development. In: Proceedings of 29th Annual EEE/NASA Software Engineering Workshop (SEW 2005), pp. 27–33. IEEE, Los Alamitos (2005)Google Scholar
  12. 12.
    Wongthongtham, P., Chang, E., Dillon, T.: Towards Ontology-based Software Engineering for Multi-site Software Development. In: 3rd IEEE International Conference on Industrial Informatics (INDIN), pp. 362–365. IEEE, Los Alamitos (2005)Google Scholar
  13. 13.
    Zhu, H., Huo, Q.: Developing software testing ontology in UML for a software growth environment of web-based applications. Software Evolution with UML and XML, 263–295 (2005)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • P. G. Sapna
    • 1
  • Hrushikesha Mohanty
    • 1
  1. 1.University of HyderabadHyderabadIndia

Personalised recommendations