A multi-case study of agile requirements engineering and the use of test cases as requirements

• URL: http://arxiv.org/abs/2308.11747v1
• Date: Tue, 22 Aug 2023 19:13:45 GMT
• Title: A multi-case study of agile requirements engineering and the use of test cases as requirements
• Authors: Elizabeth Bjarnason, Michael Unterkalmsteiner, Markus Borg, Emelie Engstr\"om
• Abstract summary: Test cases are commonly viewed as requirements and detailed requirements are documented as test cases. The use of test cases as requirements poses both benefits and challenges when eliciting, validating, verifying, and managing requirements. The identified variants of the practice of using test cases as requirements can be used to perform in-depth investigations into agile requirements engineering.
• Score: 5.71126361766062
• License: http://creativecommons.org/licenses/by-nc-sa/4.0/
• Abstract: Context: It is an enigma that agile projects can succeed 'without requirements' when weak requirements engineering is a known cause for project failures. While agile development projects often manage well without extensive requirements test cases are commonly viewed as requirements and detailed requirements are documented as test cases. Objective: We have investigated this agile practice of using test cases as requirements to understand how test cases can support the main requirements activities, and how this practice varies. Method: We performed an iterative case study at three companies and collected data through 14 interviews and two focus groups. Results: The use of test cases as requirements poses both benefits and challenges when eliciting, validating, verifying, and managing requirements, and when used as a documented agreement. We have identified five variants of the test-cases-as-requirements practice, namely de facto, behaviour-driven, story-test driven, stand-alone strict and stand-alone manual for which the application of the practice varies concerning the time frame of requirements documentation, the requirements format, the extent to which the test cases are a machine executable specification and the use of tools which provide specific support for the practice of using test cases as requirements. Conclusions: The findings provide empirical insight into how agile development projects manage and communicate requirements. The identified variants of the practice of using test cases as requirements can be used to perform in-depth investigations into agile requirements engineering. Practitioners can use the provided recommendations as a guide in designing and improving their agile requirements practices based on project characteristics such as number of stakeholders and rate of change.

Related papers

• OLMES: A Standard for Language Model Evaluations [64.85905119836818]
  We propose OLMES, a practical, open standard for reproducible language model evaluations. We identify and review the varying factors in evaluation practices adopted by the community. OLMES supports meaningful comparisons between smaller base models that require the unnatural "cloze" formulation of multiple-choice questions.
  arXiv  Detail & Related papers  (2024-06-12T17:37:09Z)
• A Tool for Test Case Scenarios Generation Using Large Language Models [3.9422957660677476]
  This article centers on generating user requirements as epics and high-level user stories. It introduces a web-based software tool that employs an LLM-based agent and prompt engineering to automate the generation of test case scenarios.
  arXiv  Detail & Related papers  (2024-06-11T07:26:13Z)
• DOLOMITES: Domain-Specific Long-Form Methodical Tasks [81.63464319950664]
  We develop a typology of methodical tasks structured in the form of a task objective, procedure, input, and output. We introduce DoLoMiTes, a novel benchmark with specifications for 519 such tasks elicited from hundreds of experts from across 25 fields. Our benchmark further contains specific instantiations of methodical tasks with concrete input and output examples.
  arXiv  Detail & Related papers  (2024-05-09T17:25:31Z)
• Generating Test Scenarios from NL Requirements using Retrieval-Augmented LLMs: An Industrial Study [5.179738379203527]
  This paper presents an automated approach (RAGTAG) for test scenario generation using Retrieval-Augmented Generation (RAG) with Large Language Models (LLMs) We evaluate RAGTAG on two industrial projects from Austrian Post with bilingual requirements in German and English.
  arXiv  Detail & Related papers  (2024-04-19T10:27:40Z)
• Requirements' Characteristics: How do they Impact on Project Budget in a Systems Engineering Context? [3.2872885101161318]
  Controlling and assuring the quality of natural language requirements (NLRs) is challenging. We investigated with the Swedish Transportation Agency (STA) to what extent the characteristics of requirements had an influence on change requests and budget changes in the project.
  arXiv  Detail & Related papers  (2023-10-02T17:53:54Z)
• An Industrial Case Study on Test Cases as Requirements [5.71126361766062]
  It is a conundrum that agile projects can succeed 'without requirements' when weak requirements engineering is a known cause for project failures. We have investigated this agile practice at three companies in order to understand how test cases can fill the role of requirements. The findings provide insights into how the role of requirements may be met in agile development including challenges to consider.
  arXiv  Detail & Related papers  (2023-08-12T09:06:22Z)
• Challenges in aligning requirements engineering and verification in a large-scale industrial context [7.92131557859946]
  This paper presents preliminary findings of interviews that identify key challenges in aligning requirements and verification processes. The findings of this study can be used by practitioners as a basis for investigating alignment in their organizations.
  arXiv  Detail & Related papers  (2023-07-23T20:08:49Z)
• A Requirements-Driven Platform for Validating Field Operations of Small Uncrewed Aerial Vehicles [48.67061953896227]
  DroneReqValidator (DRV) allows sUAS developers to define the operating context, configure multi-sUAS mission requirements, specify safety properties, and deploy their own custom sUAS applications in a high-fidelity 3D environment. The DRV Monitoring system collects runtime data from sUAS and the environment, analyzes compliance with safety properties, and captures violations.
  arXiv  Detail & Related papers  (2023-07-01T02:03:49Z)
• Socratic Pretraining: Question-Driven Pretraining for Controllable Summarization [89.04537372465612]
  Socratic pretraining is a question-driven, unsupervised pretraining objective designed to improve controllability in summarization tasks. Our results show that Socratic pretraining cuts task-specific labeled data requirements in half.
  arXiv  Detail & Related papers  (2022-12-20T17:27:10Z)
• ADAPQUEST: A Software for Web-Based Adaptive Questionnaires based on Bayesian Networks [70.79136608657296]
  ADAPQUEST is a software tool written in Java for the development of adaptive questionnaires based on Bayesian networks. It embeds dedicated elicitation strategies to simplify the elicitation of the questionnaire parameters. An application of this tool for the diagnosis of mental disorders is also discussed.
  arXiv  Detail & Related papers  (2021-12-29T09:50:44Z)
• Quality meets Diversity: A Model-Agnostic Framework for Computerized Adaptive Testing [60.38182654847399]
  Computerized Adaptive Testing (CAT) is emerging as a promising testing application in many scenarios. We propose a novel framework, namely Model-Agnostic Adaptive Testing (MAAT) for CAT solution.
  arXiv  Detail & Related papers  (2021-01-15T06:48:50Z)

This list is automatically generated from the titles and abstracts of the papers in this site.

This site does not guarantee the quality of this site (including all information) and is not responsible for any consequences.