Data-driven and tool-supported elicitation of quality requirements in agile companies
- PDF / 2,040,331 Bytes
- 33 Pages / 439.37 x 666.142 pts Page_size
- 63 Downloads / 174 Views
Data-driven and tool-supported elicitation of quality requirements in agile companies Marc Oriol 1 & Silverio Martínez-Fernández 1,2 & Woubshet Behutiye 3 & Carles Farré 1 & Rafał Kozik 5,6 & Pertti Seppänen 3 & Anna Maria Vollmer 2 & Pilar Rodríguez 3,4 & Xavier Franch 1 & Sanja Aaramaa 7 & Antonin Abhervé 6,8 & Michał Choraś 5,6 & Jari Partanen 9
# Springer Science+Business Media, LLC, part of Springer Nature 2020
Abstract
Quality requirements (QRs) are a key artifact needed to ensure the quality and success of a software system. Despite their importance, QRs rarely get the same degree of attention as their functional counterpart in agile software development (ASD) projects. Moreover, crucial information that can be obtained from software development repositories (e.g., JIRA, GitHub) is not fully exploited, or is even neglected, in QR elicitation activities. In this work, we present a data-driven tooled approach for the semi-automatic generation and documentation of QRs in the context of ASD. The approach is based on the declaration of thresholds over quality-related issues, whose violation triggers user-defined alerts. These alerts are used to browse a catalog of QR patterns that are presented to the ASD team by means of a dashboard that implements several analysis techniques. Once selected, the patterns generate the QRs, which are documented and stored in the product backlog. The full approach is implemented via a configurable platform. Over the course of 1 year, four companies differing in size and profile followed this approach and deployed the platform in their premises to semi-automatically generate QRs in several projects. We used standardized measurement instruments to elicit the perception of 22 practitioners regarding their use of the tool. The quantitative and qualitative analyses yielded positive results; i.e., the practitioners’ perception with regard to the tool’s understandability, reliability, usefulness, and relevance was positive. We conclude that the results show potential for future adoption of data-driven elicitation of QRs in agile companies and encourage other practitioners to use the presented tool and adopt it in their companies. Keywords Requirements engineering . Data-driven software engineering . Software quality . Quality requirements . Non-functional requirements . Quality attributes . Agile software development * Marc Oriol [email protected] Extended author information available on the last page of the article
Software Quality Journal
1 Introduction Quality management is known to be one of the critical success factors for software projects (Abbas et al. 2010). There are many examples of software with poor quality (e.g., software with critical bugs, security vulnerabilities, technical debt, low quality of service, poor code quality) that have caused millions of euros of losses (Krasner 2018). A report conducted by the software testing company Tricentis revealed that software failures caused more than $1.7 trillion in financial losses in 2017 (Tricentis 2018). Therefore, to be
Data Loading...
