Concurrent behavioral coverage criteria for sequence diagrams

2021 ◽  
Author(s):  
Mahesh Shirole ◽  
Rajeev Kumar
Keyword(s):  
Sequence Diagrams ◽  
Coverage Criteria

scholarly journals Synthesis of Test Scenarios Using UML Sequence Diagrams

2012 ◽  
Vol 2012 ◽  
pp. 1-22
Author(s):  
Ashalatha Nayak ◽  
Debasis Samanta
Keyword(s):  
Sequence Diagrams ◽  
System Behavior ◽  
Test Scenario ◽  
Coverage Criteria ◽  
Different Types ◽  
Levels Of Automation ◽  
Uml 2.0 ◽  
Test Scenarios ◽  
Arbitrary Flow ◽  
Testable Model

UML 2.0 sequence diagrams are used to synthesize test scenarios. A UML 2.0 sequence diagram usually consists of a large number of different types of fragments and possibly with nesting. As a consequence, arriving at a comprehensive system behavior in the presence of multiple, nested fragment is a complex and challenging task. So far the test scenario synthesis from sequence diagrams is concerned, the major problem is to extract an arbitrary flow of control. In this regard, an approach is presented here to facilitate a simple representation of flow of controls and its subsequent use in the test scenario synthesis. Also, the flow of controls is simplified on the basis of UML 2.0 control primitives and brought to a testable form known as intermediate testable model (ITM). The proposed approach leads to the systematic interpretation of control flows and helps to generate test scenarios satisfying a set of coverage criteria. Moreover, the ability to support UML 2.0 models leads to increased levels of automation than the existing approaches.

scholarly journals Fault Model for UML Behavioral Activity and Sequence Diagrams

2019 ◽  
Vol 9 (1) ◽  
pp. 6926-6929
Keyword(s):  
Fault Detection ◽  
Software Testing ◽  
Fault Model ◽  
Behavioral Activity ◽  
Sequence Diagrams ◽  
Coverage Criteria ◽  
Testing Methodology ◽  
Different Types ◽  
Uml Diagrams ◽  
Types Of Faults

In software testing, the fault detection in any software construct is very important factor to check how efficiently testing process is carried out. While testing software, it is required to take some coverage criteria to check the testing methodology. The paper shows a way for fault detection for UML behavioral diagrams. Different types of faults which can occur in UML diagrams are discussed and a fault model is proposed for combinational diagram made by integrating UML behavioral diagram such as activity and sequence diagrams. The percentage of fault detected in software is calculated using fault model and to prove how efficient is the software testing process.

TESTING ASPECT-ORIENTED PROGRAMS WITH UML DESIGN MODELS

2008 ◽  
Vol 18 (03) ◽  
pp. 413-437 ◽  
Author(s):  
DIANXIANG XU ◽  
WEIFENG XU ◽  
W. ERIC WONG
Keyword(s):  
Sequence Diagram ◽  
Test Case ◽  
Test Cases ◽  
Sequence Diagrams ◽  
Aspect Oriented Programming ◽  
Design Models ◽  
Coverage Criteria ◽  
Model Based Testing ◽  
Class Diagrams ◽  
Testing Approach

The new constructs in aspect-oriented programming bring new types of programming faults with respect to crosscutting concerns, such as incorrect pointcuts and advice. This paper presents a UML-based approach to testing whether or not an aspect-oriented program conforms to its expected crosscutting behavior. We explore aspect-oriented UML design models to derive tests for exercising interactions between aspects and classes. Each aspect-oriented model consists of class diagrams, aspect diagrams, and sequence diagrams. For a method under test, we weave the sequence diagrams of the advice on the method into the method's sequence diagram. Based on the woven sequence diagram and class/aspect diagrams, we then generate an AOF (Aspect-Object Flow) tree by applying coverage criteria such as condition coverage, polymorphic coverage, and loop coverage to woven sequence diagrams. In the AOF tree, each path from the root to a leaf is an abstract message sequence, indicating a template of test cases. A concrete test case is obtained by creating objects that satisfy the collective constraints in the template. Our empirical study shows that the model-based testing approach is capable of revealing several types of aspect-specific faults, including incorrect advice type, incorrect (weaker or stronger) pointcut strengths, and incorrect aspect precedence.

scholarly journals Evaluating the alignment of sequence diagrams with system behavior

2021 ◽  
Vol 180 ◽  
pp. 502-506
Author(s):  
Atif Mashkoor ◽  
Alexander Egyed
Keyword(s):  
Sequence Diagrams ◽  
System Behavior

scholarly journals OESDs in an on-road study of semi-automated vehicle to human driver handovers

2021 ◽  
Author(s):  
Neville A. Stanton ◽  
James W. Brown ◽  
Kirsten M. A. Revell ◽  
Jisun Kim ◽  
Joy Richardson ◽  
...  
Keyword(s):  
Vehicle Control ◽  
Future Research ◽  
Strong Correlations ◽  
Sequence Diagrams ◽  
Driving Simulators ◽  
Human Driver ◽  
Handover Process ◽  
Vehicle Automation ◽  
The Uk ◽  
Road Study

AbstractDesign of appropriate interaction and human–machine interfaces for the handover of control between vehicle automation and human driver is critical to the success of automated vehicles. Problems in this interfacing between the vehicle and driver have led, in some cases, to collisions and fatalities. In this project, Operator Event Sequence Diagrams (OESDs) were used to design the handover activities to and from vehicle automation. Previous work undertaken in driving simulators has shown that the OESDs can be used to anticipate the likely activities of drivers during the handover of vehicle control. Three such studies showed that there was a strong correlation between the activities drivers represented in OESDs and those observed from videos of drivers in the handover process, in driving simulators. For the current study, OESDs were constructed during the design of the interaction and interfaces for the handover of control to and from vehicle automation. Videos of drivers during the handover were taken on motorways in the UK and compared with the predictions from the OESDs. As before, there were strong correlations between those activities anticipated in the OESDs and those observed during the handover of vehicle control from automation to the human driver. This means that OESDs can be used with some confidence as part of the vehicle automation design process, although validity generalisation remains an important goal for future research.

Sign in / Sign up

Export Citation Format

Share Document