Requirements engineering: A systematic mapping study in agile software development

Curcio, Karina; Navarro, T. Gómez; Malucelli, Andreia; Reinehr, Sheila

doi:10.1016/j.jss.2018.01.036

Cited by 131 publications

(130 citation statements)

References 9 publications

Supporting

Mentioning

101

Contrasting

Unclassified

Order By: Relevance

“…Neglect of QRs, which is the third most common challenge in our SMS, was also reported in previous secondary studies [10,11,[16][17][18]21]. We found that ASD teams ignore QRs for different reasons.…”

Section: Related Worksupporting

confidence: 83%

“…Except Alsaqaf et al [10] and Villamizar et al [22], existing secondary studies only superficially discuss QRs, or do not discuss them at all. Some highlight the limitations of agile methods when managing QRs and the risks of neglecting QRs [11,[16][17][18]21], and some identify strategies for managing QRs in ASD, such as the AFFINE framework, NORMAP, and SENoR [11]. Others explicitly include QRs in the user story definition [20] and techniques for managing usability in agile [19,48].…”

Section: Related Secondary Studiesmentioning

confidence: 99%

“…The figure shows that 61 studies lie in the upper right corner and have a research rigor value of ≥ 1.5 and an industrial relevance value of ≥ 2. Among these studies, 16 have the highest research rigor value (3) and the highest industrial relevance value (4). Studies with high research rigor and industrial relevance enable easy transfer of knowledge and offer opportunities for replication.…”

Section: Fig 2(a) Annual Distribution Of Primary Studies Based On Aumentioning

confidence: 99%

“…Despite the need to better understand the management of QRs in ASD and RSD, the body of knowledge on this topic is not well structured. While there are secondary studies [10,11,[16][17][18][19][20][21][22] that examine state-of-the-art of requirements engineering (RE) in the context of ASD, only Alsaqaf et al [10] and Villamizar et al [22] specifically focused on QRs. However, Alsaqaf et al [10] did so only in the context of large-scale ASD, whereas Villamizar et al [22] examined only how security is handled in ASD.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Management of quality requirements in agile and rapid software development: A systematic mapping study

Behutiye

Karhapää

López³

et al. 2020

Information and Software Technology

View full text Add to dashboard Cite

Context: Quality requirements (QRs) describe the desired quality of software, and they play an important role in the success of software projects. In agile software development (ASD), QRs are often ill-defined and not well addressed due to the focus on quickly delivering functionality. Rapid software development (RSD) approaches (e.g., continuous delivery and continuous deployment), which shorten delivery times, are more prone to neglect QRs. Despite the significance of QRs in both ASD and RSD, there is limited synthesized knowledge on their management in those approaches.Objective: This study aims to synthesize state-of-the-art knowledge about QR management in ASD and RSD, focusing on three aspects: bibliometric, strategies, and challenges. Research method: Using a systematic mapping study with a snowballing search strategy, we identified and structured the literature on QR management in ASD and RSD. Results: We found 156 primary studies: 106 are empirical studies, 16 are experience reports, and 34 are theoretical studies. Security and performance were the most commonly reported QR types. We identified various QR management strategies: 74 practices, 43 methods, 13 models, 12 frameworks, 11 advices, 10 tools, and 7 guidelines. Additionally, we identified 18 categories and 4 non-recurring challenges of managing QRs. The limited ability of ASD to handle QRs, time constraints due to short iteration cycles, limitations regarding the testing of QRs and neglect of QRs were the top categories of challenges. Conclusion: Management of QRs is significant in ASD and is becoming important in RSD. This study identified research gaps, such as the need for more tools and guidelines, lightweight QR management strategies that fit short iteration cycles, investigations of the link between QRs challenges and technical debt, and extension of empirical validation of existing strategies to a wider context. It also synthesizes QR management strategies and challenges, which may be useful for practitioners.

show abstract

Section: Related Worksupporting

confidence: 83%

Section: Related Secondary Studiesmentioning

confidence: 99%

Section: Fig 2(a) Annual Distribution Of Primary Studies Based On Aumentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Management of quality requirements in agile and rapid software development: A systematic mapping study

Behutiye

Karhapää

López³

et al. 2020

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…But, no one is based on feature graph model itself; which is a conceptual weakness. Software requirements are becoming a specialized engineering science [21,22]. It is supported by engineering methodologies, methods, techniques, and tools.…”

Section: Introductionmentioning

confidence: 99%

A Feature Based Methodology for Variable Requirements Reverse Engineering

Alhamwieh¹,

Ghoul²

2019

AJSEA

View full text Add to dashboard Cite

In the past years, software reverse engineering dealt with source code understanding. Nowadays, it is levered to software requirements abstract level, supported by feature model notations, language independent, and simpler than the source code reading. The recent relevant approaches face the following insufficiencies: lack of a complete integrated methodology, adapted feature model, feature patterns recognition, and Graph based slicing. This work aims to provide some solutions to the above challenges through an integrated methodology. The following results are unique. Elementary and configuration features are specified in a uniform way by introducing semantics specific attributes. The reverse engineering supports feature pattern recognition and requirements feature model graph-based slicing. The slicing criteria are rich enough to allow answering questions of software requirements maintainers. A comparison of this proposed methodology, based on effective criteria, with the similar works, seems to be valuable and competitive: the enrichment of the feature model and feature pattern recognition were never approached and the proposed slicing technique is more general, effective, and practical.

show abstract

Functional and Non‐Functional Requirements in Agile Software Development

Saroja¹,

Haseena²

2023

Agile Software Development

View full text Add to dashboard Cite

Requirements engineering: A systematic mapping study in agile software development

Cited by 131 publications

References 9 publications

Management of quality requirements in agile and rapid software development: A systematic mapping study

Management of quality requirements in agile and rapid software development: A systematic mapping study

A Feature Based Methodology for Variable Requirements Reverse Engineering

Functional and Non‐Functional Requirements in Agile Software Development

Contact Info

Product

Resources

About