HyperMSCs and Sequence Diagrams for Use Case Modelling and Testing

Graubmann, Peter; Rudolph, Ekkart

doi:10.1007/3-540-40011-7_3

Cited by 4 publications

(2 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Some relevant proposals for scenario-based testing include: the approach of Graubmann and Rudolph [12], in which the Message Sequence Chart (MSC) inline expressions and High Level MSC (hMSC) are included into Sequence Diagrams for the specification of test cases; the methodology of Harel and Marelly [13], which is specifically designed for scenario-based specification of reactive systems; TOTEM (Testing Object-orienTEd systems with the unified Modelling language) [8], which uses sequence or collaboration diagrams associated to each use case for deriving test cases, test oracles and test drivers, and SCENTOR [25], which uses JUnit as a basis for test case derivation. SeDiTeC [11] automatically generates test stubs for the classes and methods whose behaviour is specified in the sequence diagrams.…”

Section: Related Workmentioning

confidence: 99%

TeStor: Deriving Test Sequences from Model-Based Specifications

Muccini

Bucchiarone

Facchini

2005

Component-Based Software Engineering

View full text Add to dashboard Cite

Abstract. The dependability analysis of a component-based system may be driven by the components/system implementation or by the model-based specification provided prior to or together with the implementation. In particular, model-based specifications of a componentbased system allows to explicitly model the structure and behavior of components and their integration, while model-based testing allows to derive test sequences which can be successively refined into test cases and then run onto the system implementation. Several techniques have been proposed so far to allow model-based testing. However, very few of them show certain characteristics which are peculiar for use in industrial contexts. We here describe TeStor, a TEst Sequence generaTOR algorithm which allows to extract test sequences from both state machine and scenario diagrams. We detail the algorithm, we apply it to a system study and we provide a link to its implementation.

show abstract

Section: Related Workmentioning

confidence: 99%

TeStor: Deriving Test Sequences from Model-Based Specifications

Muccini

Bucchiarone

Facchini

2005

Component-Based Software Engineering

View full text Add to dashboard Cite

show abstract

“…However, an Alloy model does not support significant UML and OCL features like attributes and its data types. Approaches concentrating on testing of UML models have been considered for special applications like smart cards [19], and with emphasis on special UML language features like sequence diagrams [20] or collaboration [21] diagrams. The approach in [22] adapts state-based specification test data generation criteria to generate test cases from UML statecharts obeying classical test coverage criteria.…”

Section: Introductionmentioning

confidence: 99%

Validating UML and OCL models in USE by automatic snapshot generation

2005

View full text Add to dashboard Cite

We study the testing and certification of UML and OCL models as supported by the validation tool USE. We extend the available USE features by introducing a language for defining properties of desired snapshots and by showing how such snapshots are generated. Within the approach, it is possible to treat test cases and validation cases. Test cases show that snapshots having desired properties can be constructed. Validation cases show that given properties are consequences of the original UML and OCL model.

show abstract