Automated Requirements Engineering in Agile Development: A Practitioners Survey

Muhammad Aminu Umar*, Kevin Lano

*Corresponding author for this work

Research output: Contribution to conference typesPaperpeer-review

Abstract

Requirements Engineering (RE) in the context of agile development is the process of discovering, analysing, validating, and managing software requirements through engaging with the stakeholders. RE activities are central to software development and its success. Advances in automation have been explored in requirements engineering activities and processes in the industry. However, the application of automated support is still limited in practice. In this study, we examine automated RE support in agile development through a qualitative analysis using industry experts. We have found that the application of automated RE support tools is primarily in the experimental stage, largely due to the limited practical implementation in industry settings. The current focus has been on research experiments, with relatively fewer instances of real-world industry application. Although experts are optimistic about its huge potential to reduce development efforts and costs if automation is harnessed. Therefore, we anticipate that these findings will be beneficial for practitioners responsible for developing RE tools for agile development, as well as for the researchers.

Original languageEnglish
DOIs
Publication statusPublished - 2024
Event2023 International Conference on Electrical, Computer, Communications and Mechatronics Engineering, ICECCME 2023 - Tenerife, Canary Islands, Spain
Duration: 19 Jul 202321 Jul 2023

Conference

Conference2023 International Conference on Electrical, Computer, Communications and Mechatronics Engineering, ICECCME 2023
Country/TerritorySpain
CityTenerife, Canary Islands
Period19/07/202321/07/2023

Keywords

  • Agile Development
  • Automation
  • Empirical study
  • Requirements Engineering
  • Support

Fingerprint

Dive into the research topics of 'Automated Requirements Engineering in Agile Development: A Practitioners Survey'. Together they form a unique fingerprint.

Cite this