A Requirements Engineering Techniques Review in Agile Software Development Methods

Zamudio, Lizbeth; Aguilar, José Alfonso; Tripp, Carolina; Misra, Sanjay

doi:10.1007/978-3-319-62404-4_50

Cited by 23 publications

(13 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In most cases, it is not possible to directly compare our findings to results reported by others, as they do not explicitly focus on NFRs and thus it is not possible to tell which reported practices/techniques were applicable to NFRs (e.g. [27], [28], [31]). Also, some sources mention practices related to software project organization like division into teams or a customer-supplier cooperation model (e.g.…”

Section: A Theoretical Implicationsmentioning

confidence: 87%

“…An article by Zamudio et al [27] reports a SLR study on requirements engineering techniques in ASD. The authors focus on elicitation techniques reported as used in particular agile methodologies.…”

Section: Related Workmentioning

confidence: 99%

“…The quoted literature points out the issues that provide a rationale for our research though. A general research gap on NFRs in ARE is identified [31] [27]. Moreover, several ARE challenges related to engineering NFRs are reported [7], [8], [11], [28].…”

Section: Summary Of Previous Studies' Findingsmentioning

confidence: 99%

“…Despite the fact that the challenges and solutions related to NFRs in Agile are mentioned in several sources (see Section II for details), a summary of practices and techniques dedicated to NFR identification, elicitation and documentation in Agile projects is still not provided in comprehensive manner by the existing literature. We identified several secondary studies covering research topics like: requirements engineering techniques used in Agile projects [10], [27], [28], ARE practices and challenges [29], requirements engineering challenges and mitigating practices [8], quality of agile requirements specifications [30] and main research areas in ARE [7], [31]. None of them however focused on NFRs and, as a result, they report only individual cases of findings (challenges, practices, techniques) related to NFRs.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

A Qualitative Study on Non-Functional Requirements in Agile Software Development

Jarzębowicz

Weichbroth

2021

IEEE Access

View full text Add to dashboard Cite

Widespread use of agile software development (ASD) methods can be observed nowadays. Non-functional requirements (NFRs) are often reported to be a problematic issue for agile projects, since ASD methods tend to neglect NFRs while focusing on incremental delivery of functional features. Despite that, only very few studies have explored the requirements engineering practices used in ASD and dedicated particularly to NFRs. Objective: We aimed to identify and investigate the practices used in industrial ASD projects to identify, elicit and document NFRs. Method: We conducted a systematic literature review (SLR) and used its findings to prepare an interview guide. We then conducted a series of semi-structured interviews with 10 experienced practitioners. Results: The SLR revealed a number of strategies related to the timing of NFR identification as well as 13 elicitation practices and 20 documentation techniques. At least some of these findings show discrepancies between ASD theory and practice. The interviews provided a more in-depth understanding of the practices used, and their context. The main findings from the interviews include: practitioners' attempts to start identifying NFRs early in the project, a lack of elicitation techniques aimed at NFRs only, and different choices about documentation techniques, including the additional techniques introduced to cope specifically with NFRs. Conclusions: It was not confirmed that requirements engineering activities related to NFRs are perceived by ASD practitioners as a problem, as they developed effective practices to deal with this issue. Moreover, our findings show that different approaches to NFRs can be used and give satisfactory results.

show abstract

Section: A Theoretical Implicationsmentioning

confidence: 87%

Section: Related Workmentioning

confidence: 99%

Section: Summary Of Previous Studies' Findingsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A Qualitative Study on Non-Functional Requirements in Agile Software Development

Jarzębowicz

Weichbroth

2021

IEEE Access

View full text Add to dashboard Cite

show abstract

“…More recently, Matyokurehwa, Mavetera and Jokonya (2010) considered a time window from 2000 to 2016 for a literature review, evidencing a great variety of methods and techniques, however, none of the these consider the whole RE process systemically and holistically, leaving for the practitioner the task to choose tools for RE implementation from a wide and dynamic variety in the software market. It should be noted that, given the recent but dynamic, rapid and complex growth of RE, researchers have focused their studies in certain aspects, such as the use of techniques in agile development methodologies (Zamudio, Aguilar, Tripp, & Misra, 2017) or the use of empirical RE techniques (Ambreen, Ikram, Usman, & Niazi, 2018) either by their importance or urgency, or as a herd effect of what is being published in academic journals.…”

Section: Related Workmentioning

confidence: 99%

The Knowledge Body of Requirement Engineering in IST Innovations: An Ontological Analysis

Vásquez

Paz

2019

Journal of Technology Management & Innovation

View full text Add to dashboard Cite

Requirement Engineering is considered a key factor for Information Systems and Technology (IST) success in innovation. After roughly 40 years, important questions about the impact of RE in innovations remains. Literature review and bibliometric reports are well-known techniques for describing the state of the art; however, both can cover what has been done, but fail to identify the less developed areas. An alternative method is used to describe the whole knowledge body of RE (KBoRE) for IST innovations, and then systematically identify the most, less and uncovered areas. This paper proposes an Ontological framework of the KBoRE for IST innovations, by decomposing it through the identification of taxonomies and concepts that represent the field. Then, we apply the ontology to map articles from SCOPUS and WoS databases. Results reveal emphases that help to design research agendas and feed the KBoRE for IST Innovations to fill the gaps between the academic curiosity and the industry progress.

show abstract

Scaled agile framework. Dealing with software process‐related challenges of a financial group with the action research approach

Kowalczyk

Marcinkowski

Przybyłek

2022

J Software Evolu Process

View full text Add to dashboard Cite

This article reports on a domain-specific software development venture at Nordea. We explore organizational constraints, challenges, and corrective actions undertaken when scaling the agile development approach of their Core Banking Platform program. The fit and required customizations of the rather complex and rigid SAFe framework in a policy-heavy financial institution are audited against the organic growth of the program. In a qualitative study with three cycles using the Action Research method, both organizational and technical restrictions were tackled jointly with the company employees. Thirty-four potential solutions were developed-some of which turned out to be dead-ends. Ultimately, the effectiveness of prior recommendations was tested in a highly challenging implementation environment, and the list of guidelines was extended. We discovered several meeting and collaboration schemes that are not fully aligned with previous reports.

show abstract

A Requirements Engineering Techniques Review in Agile Software Development Methods

Cited by 23 publications

References 11 publications

A Qualitative Study on Non-Functional Requirements in Agile Software Development

A Qualitative Study on Non-Functional Requirements in Agile Software Development

The Knowledge Body of Requirement Engineering in IST Innovations: An Ontological Analysis

Scaled agile framework. Dealing with software process‐related challenges of a financial group with the action research approach

Contact Info

Product

Resources

About