Review on formalizing use cases and scenarios: Scenario based testing

Hussain, Altaf; Nadeem, Aamer; Ikram, Muhammad Touseef

doi:10.1109/icet.2015.7389203

Cited by 8 publications

(6 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Many other proposals are related to the steps that are implicitly linked to every requirement (for example (Hussain et al, 2015)). This is the essence of our approach but some distinctions should be made.…”

Section: Related Workmentioning

confidence: 99%

User acceptance test for software development in the agricultural domain using natural language processing

Antonelli

Camilleri

Torres

et al. 2023

Journal of Decision Systems

View full text Add to dashboard Cite

Software test case design is one of the most challenging activities since many actors with different backgrounds must cover most of the user's needs and expectations. In the agricultural domain tasks can be done in very different ways since practices vary worldwide. Thus, in this context, it is very hard to design test cases to validate requested functionality that automatizes some farm tasks. This paper proposes an approach to make the testing step easier, designing User Acceptance Tests (UATs) from requirements captured through scenarios. The scenarios capture the knowledge of different stakeholders (farmers) and using natural language processing tools, the approach proposed to consolidate the set of scenarios in a consistent and coherent base of knowledge organised in a tree, from where the design of test cases is extracted using the Task/Method model, a tool from the Artificial Intelligence.

show abstract

Section: Related Workmentioning

confidence: 99%

User acceptance test for software development in the agricultural domain using natural language processing

Antonelli

Camilleri

Torres

et al. 2023

Journal of Decision Systems

View full text Add to dashboard Cite

show abstract

“…Biswal et al [4] generate scenarios from UML diagrams to obtain Test Cases. Hussain et al [11] propose a similar approach. We believe that if scenarios begin to be used from the early stages of software development, their description and the test cases will be richer.…”

Section: Related Workmentioning

confidence: 99%

Anais do Workshop em Engenharia de Requisitos

2022

View full text Add to dashboard Cite

Requirements engineering is one of the most important stages in software development. Errors committed at this stage require a lot of effort to fix in further stages. There are two main strategies to deal with software development: classic and agile. Classic software development relies on an extensive and very detailed specification, while agile development minimizes the effort on requirements specifications, relying on brief descriptions and a running prototype as a means of communication. Before the specification of requirements, there are some preliminary meetings held between the stakeholders and the IT team with the objective of discovering the goal and scope of the application to be developed. The knowledge transferred during these meetings is crucial to provide a context to requirements, no matters whether the approach is classic or agile. We argue that scenarios written in natural language are adequate artifacts to capture this knowledge. This paper proposes an iterative and collaborative approach to describe scenarios. The approach has two main activities: one of them is concerned with the description that stakeholders should perform, while the other provides guidelines to verify and possible improve the scenarios. This paper also presents a prototype tool that helps enforcing these guidelines automatically. This prototype relies on natural language processing. Finally, the paper shows the result of a preliminary evaluation of the proposed approach that indicates its results are promising

show abstract

“…Takagi and Noda (2016) describe a strategy to develop a graph about the sequence of test case execution related to hardware testing, that is, very detail and specific situations in contrast with the essence of the scenarios. Hussain et al (2015) also provide an approach to design test considering dependencies between scenarios. Nomura et al (2014) model the business context in a matrix representing the dependency between business process, and then from the perspective of profiles is design the tests to cover the different situations.…”

Section: User Acceptance Tests Automationmentioning

confidence: 99%

“…There are many other proposals that are related to the steps that are implicitly linked to every requirement, for example, as in Hussain et al (2015). That is the essence of our approach.…”

Section: Related Workmentioning

confidence: 99%

AGUTER a platform for automated generation of user acceptance tests from requirements specifications

Antonelli

Camilleri

Torres

et al. 2021

View full text Add to dashboard Cite

PurposeThis article proposes a strategy to make the testing step easier, generating user acceptance tests (UATs) in an automatic way from requirements artifacts.Design/methodology/approachThis strategy is based on two modeling frameworks: scenarios and task/method paradigm. Scenarios are a requirement artifact used to describe business processes and requirements, and task/method paradigm is a modeling paradigm coming from the artificial intelligence field. The proposed strategy is composed of four steps. In the first step, scenarios are described through a semantic wiki website. Then scenarios are automatically translated into a task/method model (step two). In the third step, the task/method model obtained in step two is executed in order to produce and store all possible achievements of tasks and thus scenarios. The stored achievements are saved in a data structure called execution tree (ET). Finally, from this ET (step four), the UATs are generated.FindingsThe feasibility of this strategy is shown through a case study coming from the agriculture production systems field.Originality/valueGenerally, test design approaches deal with a small number of variables describing one specific situation where a decision table or workflow is used to design tests. The proposed approach can deal with many variables because the authors rely on scenarios that can be composed in order to obtain a tree with all the testing paths that can arise from their description.

show abstract

Review on formalizing use cases and scenarios: Scenario based testing

Cited by 8 publications

References 4 publications

User acceptance test for software development in the agricultural domain using natural language processing

User acceptance test for software development in the agricultural domain using natural language processing

Anais do Workshop em Engenharia de Requisitos

AGUTER a platform for automated generation of user acceptance tests from requirements specifications

Contact Info

Product

Resources

About