Capturing, eliciting, and prioritizing (CEP) NFRs in agile software engineering

Maiti, Richard R.; Mitropoulos, Frank J.

doi:10.1109/secon.2017.7925365

Cited by 14 publications

(8 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Content may change prior to final publication. On the basis of a training provided to the customer in each iteration [68] On the basis of business process models [59], [60] By automated OCR and text processing of project documents and images [77] shops, brainstorming) seem to be most popular. Document circulation (that seems not to be in line with direct communication practices) is also proposed.…”

Section: A Systematic Literature Reviewmentioning

confidence: 99%

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 Systematic Literature Reviewmentioning

confidence: 99%

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

“…There are several studies regarding the management of NFRs on ASD [3], [5], [6], [7], [8], [10], [11], [13], [14], [15].…”

Section: Related Workmentioning

confidence: 99%

“…In the study [10], the authors proposed to use NFRs metadata from software requirements artifacts -documents and images -as an extension of previous works [6] and [5]. Finally, in [12], authors investigated the prioritization of requirements based on the framework proposed in [11].…”

Section: Related Workmentioning

confidence: 99%

A Non-Functional Requirements Recommendation System for Scrum-based Projects

Ramos¹,

Costa²,

Perkusich³

et al. 2018

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Agile software development focuses on quick delivery and flexibility to change. Despite being effective in delivering quality functional requirements, agile practices tend to neglect non-functional requirements until the later stages of software development. This work focuses on Scrum, the most popular agile method, and presents a non-functional requirements recommendation system to support Scrum practitioners on their early identification. The solution is based on instrumenting the Scrum process to extract useful data and the use of collaborative filtering and item recommendation. To evaluate the recommendations, we conducted off-line experiments with data collected from 12 Scrum practitioners through a survey. The data was analyzed using 10fold cross-validation. As a result, our proposed solution showed a recall rate of up to 81%, which indicates that it is a promising approach to recommend non-functional requirements given a set of functional requirements identified by project stakeholders.

show abstract

Section: Introductionmentioning

confidence: 99%

“…By addressing this problem, some studies proposed techniques to support the NFR elicitation in the agile context [10], [11], [12], [13]. Maiti and Mitropoulos [12], [13] presented a methodology to collect NFRs metadata from software requirements artifacts such as documents and images available in the initial stages of projects. Farid et al [10], [11] proposed a solution based on decision trees to predict NFRs from future iterations of agile projects based on the metadata collected with the methodology proposed in Maiti and Mitropoulos [12], [13].…”

Section: Introductionmentioning

confidence: 99%

Evaluating Software Developers’ Acceptance of a Tool for Supporting Agile Non-Functional Requirement Elicitation

Ramos¹,

Pedro²,

Cesar³

et al. 2019

International Conferences on Software Engineering and Knowledge Engineering

View full text Add to dashboard Cite

Due to the need for flexibility to requirements changes, agile software development methods have been attracting the attention of academic and industrial domains. Unlike traditional approaches, agile methods focus on the rapid delivery of business value to customers through empirical and incremental development processes. Despite being effective in delivering quality functional requirements, agile practices generally neglect non-functional requirements until the later stages of software development. However, neglecting non-functional requirements during requirements analysis can lead to project failures. In this paper, we present the NFRec tool, which aims to support software developers in the elicitation of non-functional requirements in the context of agile software development. Additionally, we report the results from a case study to evaluate the acceptance of the NFRec tool from the point of view of software developers of four projects from a Brazilian software company. To gather information about the tool acceptance, we applied a questionnaire based on the indicators from the Technology Acceptance Model. Overall, the four teams considered the NFRec tool useful and easy to use for supporting the management of non-functional requirements in agile projects.

show abstract

Capturing, eliciting, and prioritizing (CEP) NFRs in agile software engineering

Cited by 14 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

A Non-Functional Requirements Recommendation System for Scrum-based Projects

Evaluating Software Developers’ Acceptance of a Tool for Supporting Agile Non-Functional Requirement Elicitation

Contact Info

Product

Resources

About