2019
DOI: 10.1007/978-3-030-29238-6_4
|View full text |Cite
|
Sign up to set email alerts
|

Data-Driven Elicitation of Quality Requirements in Agile Companies

Abstract: Quality Requirements (QRs) are a key artifact to ensure the quality and success of a software system. Despite its importance, QRs have not reached the same degree of attention as its functional counterparts, especially in the context of trending software development methodologies like Agile Software Development (ASD). Moreover, crucial information that can be obtained from data sources of a project under development (e.g. JIRA, github,…) are not fully exploited, or even neglected, in QR elicitation activities.… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Year Published

2019
2019
2021
2021

Publication Types

Select...
4
2
1

Relationship

4
3

Authors

Journals

citations
Cited by 9 publications
(6 citation statements)
references
References 20 publications
0
6
0
Order By: Relevance
“…The framework provides a structure to organize the comprehensive representation of information technology architecture data. The project historical data is used to predict the new NFR [13], [40], [41]. The proposed NFRElicit methodology includes the role of the experts and the previous data of organization for NFR elicitation.…”
Section: Proposed Nfr Elicitation Methodologymentioning
confidence: 99%
“…The framework provides a structure to organize the comprehensive representation of information technology architecture data. The project historical data is used to predict the new NFR [13], [40], [41]. The proposed NFRElicit methodology includes the role of the experts and the previous data of organization for NFR elicitation.…”
Section: Proposed Nfr Elicitation Methodologymentioning
confidence: 99%
“…The process performance SI measures the performance of an organization's software development process. Among the Solution features, the 'quality alert' feature [22] carries significance in this study, as we discuss in Section 4.1. Here, once a metric crosses a user-defined threshold, indicating violation of quality goals defined by the use-case Quality Engineers, this feature triggers a quality alert.…”
Section: Q-rapids Projectmentioning
confidence: 99%
“…CC4 is a proponent of low-level metrics, and that has proven beneficial for them. In contrast, most of the metrics used to generate quality alert [14] in CC1 are aggregated metrics. This is also the case with CC2's use of the metric to improve their practice of maintaining the DoD field in Jira.…”
Section: Rq22: What Is the Utilitarian Perspective Of An Actionable mentioning
confidence: 99%