Synthesis of test scenarios using UML activity diagrams

Ashalatha Nayak, Debasis Samanta

Research output: Contribution to journalArticle

25 Citations (Scopus)

Abstract

Often system developers follow Unified Modeling Language (UML) activity diagrams to depict all possible flows of controls commonly known as scenarios of use cases. Hence, an activity diagram is treated as a useful design artifact to identify all possible scenarios and then check faults in scenarios of a use case. However, identification of all possible scenarios and then testing with activity diagrams is a challenging task because several control flow constructs and their nested combinations make path identification difficult. In this paper, we address this problem and propose an approach to identify all scenarios from activity diagrams and use them to test use cases. The proposed approach is based on the classification of control constructs followed by a transformation approach which takes into account any combination of nested structures and transforms an activity diagram into a model called Intermediate Testable Model (ITM). We use ITM to generate test scenarios. With our approach it is possible to generate more scenarios than the existing work. Further, the proposed approach can be directly carried out using design models without any addition of testability information unlike the existing approaches.

Original languageEnglish
Pages (from-to)63-89
Number of pages27
JournalSoftware and Systems Modeling
Volume10
Issue number1
DOIs
Publication statusPublished - 01-01-2011

Fingerprint

Unified Modeling Language
Diagram
Synthesis
Scenarios
Use Case
Flow control
Flow Control
Model
Testing
Fault
Transform
Path

All Science Journal Classification (ASJC) codes

  • Software
  • Modelling and Simulation

Cite this

@article{dc621bb4e4854f3ba3ec09cadf0c1fe9,
title = "Synthesis of test scenarios using UML activity diagrams",
abstract = "Often system developers follow Unified Modeling Language (UML) activity diagrams to depict all possible flows of controls commonly known as scenarios of use cases. Hence, an activity diagram is treated as a useful design artifact to identify all possible scenarios and then check faults in scenarios of a use case. However, identification of all possible scenarios and then testing with activity diagrams is a challenging task because several control flow constructs and their nested combinations make path identification difficult. In this paper, we address this problem and propose an approach to identify all scenarios from activity diagrams and use them to test use cases. The proposed approach is based on the classification of control constructs followed by a transformation approach which takes into account any combination of nested structures and transforms an activity diagram into a model called Intermediate Testable Model (ITM). We use ITM to generate test scenarios. With our approach it is possible to generate more scenarios than the existing work. Further, the proposed approach can be directly carried out using design models without any addition of testability information unlike the existing approaches.",
author = "Ashalatha Nayak and Debasis Samanta",
year = "2011",
month = "1",
day = "1",
doi = "10.1007/s10270-009-0133-4",
language = "English",
volume = "10",
pages = "63--89",
journal = "Software and Systems Modeling",
issn = "1619-1366",
publisher = "Springer Verlag",
number = "1",

}

Synthesis of test scenarios using UML activity diagrams. / Nayak, Ashalatha; Samanta, Debasis.

In: Software and Systems Modeling, Vol. 10, No. 1, 01.01.2011, p. 63-89.

Research output: Contribution to journalArticle

TY - JOUR

T1 - Synthesis of test scenarios using UML activity diagrams

AU - Nayak, Ashalatha

AU - Samanta, Debasis

PY - 2011/1/1

Y1 - 2011/1/1

N2 - Often system developers follow Unified Modeling Language (UML) activity diagrams to depict all possible flows of controls commonly known as scenarios of use cases. Hence, an activity diagram is treated as a useful design artifact to identify all possible scenarios and then check faults in scenarios of a use case. However, identification of all possible scenarios and then testing with activity diagrams is a challenging task because several control flow constructs and their nested combinations make path identification difficult. In this paper, we address this problem and propose an approach to identify all scenarios from activity diagrams and use them to test use cases. The proposed approach is based on the classification of control constructs followed by a transformation approach which takes into account any combination of nested structures and transforms an activity diagram into a model called Intermediate Testable Model (ITM). We use ITM to generate test scenarios. With our approach it is possible to generate more scenarios than the existing work. Further, the proposed approach can be directly carried out using design models without any addition of testability information unlike the existing approaches.

AB - Often system developers follow Unified Modeling Language (UML) activity diagrams to depict all possible flows of controls commonly known as scenarios of use cases. Hence, an activity diagram is treated as a useful design artifact to identify all possible scenarios and then check faults in scenarios of a use case. However, identification of all possible scenarios and then testing with activity diagrams is a challenging task because several control flow constructs and their nested combinations make path identification difficult. In this paper, we address this problem and propose an approach to identify all scenarios from activity diagrams and use them to test use cases. The proposed approach is based on the classification of control constructs followed by a transformation approach which takes into account any combination of nested structures and transforms an activity diagram into a model called Intermediate Testable Model (ITM). We use ITM to generate test scenarios. With our approach it is possible to generate more scenarios than the existing work. Further, the proposed approach can be directly carried out using design models without any addition of testability information unlike the existing approaches.

UR - http://www.scopus.com/inward/record.url?scp=79251600511&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=79251600511&partnerID=8YFLogxK

U2 - 10.1007/s10270-009-0133-4

DO - 10.1007/s10270-009-0133-4

M3 - Article

VL - 10

SP - 63

EP - 89

JO - Software and Systems Modeling

JF - Software and Systems Modeling

SN - 1619-1366

IS - 1

ER -