Dealing with Concurrent Regions during Scenario Generation from Activity Diagrams

Chandler, Robert C.; Lam, Chiou Peng; Li, Huaizhong

doi:10.1007/978-1-4020-6268-1_74

Cited by 3 publications

(4 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…First, the existing approaches make it difficult to generate tests for complex models because the work assume simplified models [4,8,13,16,[19][20][21]29] or make use of a subset of the constructs in the models [7,9]. Second, the reported researches are not able to capture the essential structure of the model prior to test case generation.…”

Section: Related Workmentioning

confidence: 99%

“…To be able to uniquely distinguish these constructs, we identify every basic (non-nested) construct and define it as the smallest region known as a minimal region. This allows us to express nested constructs in terms of basic types without introducing any more new types unlike the existing approaches [7,9]. We define a minimal region as given below.…”

Section: Control Constructs In An Activity Diagrammentioning

confidence: 99%

“…From an input XML file, they describe how to extract and process diagram elements so as to generate usage scenarios. In [7], an approach extending the work in [8] is presented, focusing on concurrent regions. It allows inclusion of loops, branches and nested concurrent regions.…”

Section: Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Synthesis of test scenarios using UML activity diagrams

Nayak

Samanta

2009

Softw Syst Model

View full text Add to dashboard Cite

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.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Control Constructs In An Activity Diagrammentioning

confidence: 99%

See 1 more Smart Citation

Synthesis of test scenarios using UML activity diagrams

Nayak

Samanta

2009

Softw Syst Model

View full text Add to dashboard Cite

show abstract

“…Li and Lam proposed the traversal to be a composite activity and not pre-processing it. Chandler [14] suggested the generation of usage scenario from the activity diagram. They employed the XML file to extract the model attributes and define usage scenarios from each iteration.…”

Section: Cmentioning

confidence: 99%

SR-UML: Quality Visualization in Software Design

Chourey¹,

Sharma²

2019

IJITEE

View full text Add to dashboard Cite

The current requirements of software are intensively based on load sharing, on-demand services, cascading requirements, redundancy for reliability and executing on heterogeneous environments. It needs precise architectural details for development of such software systems. These are large scale software systems with complex interactions amongst the constituent components. Testing for performance and conformance to quality requires perspective modeling fordesigning critical systems. The analysis of these systems is focused on dynamic or execution time behavior for achieving quality. In the same context, this paper redefines Functional Flow Specification for dynamic analysis of critical and collaborating systems. Functional Flow based modeling is a mature concept in the domain of system engineering but is rarely applicable to software systems. Functional Flow Block Reliability Diagram (FFBRD) is a notation for abstract view of the system evolution and interactions. This adopts the specification format of UML and system modeling conventions of SysML specially Enhanced Functional Flow Block Diagram (EFFBD). The flow of data and control are so designed that it best suits the approaches for quality analysis like system reliability. The method proposed is System Reliability with UML or SR-UML for generating test through FFBRD. It also caters to the need of designing software in a familiar formalization for extending, translating and simulating with existing algorithms. From the results collected through various scenarios, we can conclude that SR-UML is instrumental in process improvement of current software development methods

show abstract

Scenario Based Test Case Generation Using Activity Diagram and Action Semantics

Hashmani

Zaffar

Ejaz

2019

Human Factors in Global Software Engineering

View full text Add to dashboard Cite

Scenario is an account of description of user interaction with the system, presented in a sequence. They can be represented using unified modeling language (UML) diagrams such as use case diagram, state charts, activity diagrams etc. Scenario-based testing can be performed at higher abstraction level using the design diagrams. In this work activity diagrams are used which are annotated with action semantics to test scenario dependencies. The action semantics make activity diagram executable and the dependencies between multiple scenarios can be seen at execution level. The authors intend to propose an approach for scenario dependency testing. Dependency graphs will be then generated against all the dependencies present on activity diagram under test. The test paths extracted from these dependency graphs help in testing.

show abstract

Dealing with Concurrent Regions during Scenario Generation from Activity Diagrams

Cited by 3 publications

References 16 publications

Synthesis of test scenarios using UML activity diagrams

Synthesis of test scenarios using UML activity diagrams

SR-UML: Quality Visualization in Software Design

Scenario Based Test Case Generation Using Activity Diagram and Action Semantics

Contact Info

Product

Resources

About