An approach for supporting system-level test scenarios generation from textual use cases

Somé, Stéphane S.; Cheng, Xu

doi:10.1145/1363686.1363857

Cited by 14 publications

(16 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…A restricted form of natural language is used for descriptions of the use cases in [10]. From them, a controlflow-based state machine is created for each use case.…”

Section: B Natural-language-based Scenarios Generationmentioning

confidence: 99%

See 1 more Smart Citation

Interface-based Semi-automated Testing of Software Components

Potužák

Lipka

Brada

2017

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-The component-based software development enables to construct applications from reusable components providing particular functionalities and simplifies application evolution. To ensure the correct functioning of a given component-based application and its preservation across evolution steps, it is necessary to test not only the functional properties of the individual components but also the correctness of their mutual interactions and cooperation. This is complicated by the fact that third-party components often come without source code and/or documentation of functional and interaction properties. In this paper, we describe an approach for performing rigorous semi-automated testing of software components with unavailable source code. Utilizing an automated analysis of the component interfaces, scenarios invoking methods with generated parameter values are created. When they are performed on a stable application version and their runtime effects (component interactions) are recorded, the resulting scenarios with recorded effects can be used for accurate regression testing of newly installed versions of selected components. Our experiences with a prototype implementation show that the approach has acceptable demands on manual work and computational resources.

show abstract

“…A restricted form of natural language is used for descriptions of the use cases in [10]. From them, a controlflow-based state machine is created for each use case.…”

Section: B Natural-language-based Scenarios Generationmentioning

confidence: 99%

“…These state machines are then combined into a single global system level state machine. The testing scenarios are then created by this state machine exploration [10].…”

Section: B Natural-language-based Scenarios Generationmentioning

confidence: 99%

Interface-based Semi-automated Testing of Software Components

Potužák

Lipka

Brada

2017

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

show abstract

“…Recent advancements in the field of use case modeling prompted the necessity of a structured storage and representation mechanism for constraints. Two main research proposals that make use of the use case constraint structure are (1) inferring use case sequencing relations from preconditions and post-conditions for requirements verification [57], use case synchronization [58], and test scenario generation [59], (2) enhancing software effort estimation process by assigning weights to preconditions, post-conditions, and constraints [60].…”

Section: Use Case Constraintsmentioning

confidence: 99%

Extending the UML use case metamodel with behavioral information to facilitate model analysis and interchange

Misbhauddin

Alshayeb

2013

Softw Syst Model

View full text Add to dashboard Cite

Use case diagrams are primary artifacts used for modeling functional requirements. Use case diagrams are part of the Unified Modeling Language (UML) suite of models that has become a de facto standard for modeling object oriented languages. Each model in this suite is described by a metamodel that dictates its syntax and semantics. The use case diagram is considered the most controversial diagram in UML. Practitioners claim that the use case diagram cannot be used as a valuable artifact for requirement analysis. The main reason behind this concern is the lack of behavioral description of a use case depicted within the model. Quite a few extensions to the use case metamodel have been proposed in literature to incorporate behavioral aspect of a use case within the metamodel. All these extensions omit a few important features like generalization and most of them can only be used for model representation and cannot be used for model analysis and evaluation. In this paper, we propose an extension to the UML use case metamodel with use case behavior specification elements. The main objective of the proposed extension is to provide a complete metamodel for use case diagrams which includes representation for all its elements and relationships in a conflict-free manner and one that includes information for model analysis, evaluation, and interchange among modeling tools. In order to include all valuable information related to a use case, a number of use Communicated by Dr. case representation templates were considered for the proposed extension. Simultaneously, to enable the use case models generated based on the proposed metamodel to be used for analysis, pertinent information related to model usage in analysis such as effort estimation, use case scheduling, and use case metrics evaluation were considered from published studies, tools, and paradigms and included within the proposed metamodel.

show abstract

“…A user may perform multiple actions with the system. Since it is not possible to analyze the system execution for all user actions, some representative test scenarios can be used [7]. The selected scenarios should cover all concerns of a viewpoint.…”

Section: Execution Metamodelmentioning

confidence: 99%

“…An important task of an OS is to allocate computer resources among competing execution entities [7]. CPU time is one of the critical resources a computer system has and that needs to be allocated in an appropriate manner.…”

Section: Time Distributionmentioning

confidence: 99%