NORPLAN: Non-functional Requirements Planning for agile processes

Farid, Weam M.; Mitropoulos, Frank J.

doi:10.1109/secon.2013.6567463

Cited by 14 publications

(10 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The findings from the scientific literature acknowledge the significance of handling NFRs in ASD [3,8,15]. The challenges of NFRs documentation in ASD, the limitations of ASD for handling NFRs, solution proposals for handling NFRs in ASD and the need for further investigation of the topic are reported frequently.…”

Section: Introductionmentioning

confidence: 95%

See 1 more Smart Citation

Non-functional Requirements Documentation in Agile Software Development: Challenges and Solution Proposal

Behutiye

Karhapää

Costal

et al. 2017

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Non-functional requirements (NFRs) are determinant for the success of software projects. However, they are characterized as hard to define, and in agile software development (ASD), are often given less priority and usually not documented. In this paper, we present the findings of the documentation practices and challenges of NFRs in companies utilizing ASD and propose guidelines for enhancing NFRs documentation in ASD. We interviewed practitioners from four companies and identified that epics, features, user stories, acceptance criteria, Definition of Done (DoD), product and sprint backlogs are used for documenting NFRs. Wikis, word documents, mockups and spreadsheets are also used for documenting NFRs. In smaller companies, NFRs are communicated through white board and flip chart discussions and developers' tacit knowledge is prioritized over documentation. However, loss of traceability of NFRs, the difficulty in comprehending NFRs by new developers joining the team and limitations of documentation practices for NFRs are challenges in ASD. In this regard, we propose guidelines for documenting NFRs in ASD. The proposed guidelines consider the diversity of the NFRs to document and suggest different representation artefacts depending on the NFRs scope and level of detail. The representation artefacts suggested are among those currently used in ASD in order not to introduce new specific ones that might hamper actual adoption by practitioners.

show abstract

Section: Introductionmentioning

confidence: 95%

“…AFFINE framework, NORMAP, NORPLAN, security backlog for Scrum etc.) [3,8,15]. Lightweight practices and systematic solutions that integrate NFRs in ASD without compromising quality of software and agility of the development process are of high importance.…”

Section: Non-functional Requirements Documentation Challenges and Pramentioning

confidence: 99%

Non-functional Requirements Documentation in Agile Software Development: Challenges and Solution Proposal

Behutiye

Karhapää

Costal

et al. 2017

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…In our SMS, we also identified some solution proposals focusing not on a specific QR but instead on a wider range of QRs. Farid and Mitropoulos (2013) proposed the Non-functional Requirements Planning for Agile Processes (NORPLAN) to improve the planning and prioritization of NFRs. Cannizzo et al (2008) explained that the implementation of continuous integration (CI) can address QRs, particularly robustness and performance.…”

Section: Related Workmentioning

confidence: 99%

Strategies to manage quality requirements in agile software development: a multiple case study

et al. 2021

View full text Add to dashboard Cite

Agile methods can deliver software that fulfills customer needs rapidly and continuously. Quality requirements (QRs) are important in this regard; however, detailed studies on how companies applying agile methods to manage QRs are limited, as are studies on the rationale for choosing specific QR management practices and related challenges. The aim of this study was to address why practitioners manage QRs as they do and what challenges they face. We also analyzed how existing practices mitigate some of the found challenges. Lastly, we connect the contextual elements of the companies with their practices and challenges. We conducted 36 interviews with practitioners from four companies of varying sizes. Since each company operates in different domains, comparing QR management strategies and related challenges in different contexts was possible. We found that the companies apply proactive, reactive, and interactive strategies to manage QRs. Additionally, our study revealed 40 challenges in six categories that companies applying agile methods may face in QR management. We also identified nine contextual elements that affect QR management practice choices and which, importantly, can explain many related challenges. Based on these findings, we constructed a theoretical model about the connection between context, QR management practices, and challenges. Practitioners in similar contexts can learn from the practices identified in this study. Our preliminary theoretical model can help other practitioners identify what challenges they can expect to face in QR management in different developmental contexts as well as which practices to apply to mitigate these challenges.

show abstract

“…Sources User stories [25], [57], [66], [74], [78] User stories with acceptance tests [79], [80] Constraints within user stories [25], [ [19], [20], [70], [72] Textual quantified descriptions [74] Traceability matrices (quality attributes vs. FRs) [76], [83] Agile Loose Cases [75] Wiki pages [57] Instances of requirements templates dedicated to particular categories of NFRs [16], [17] NFR Framework (Goal Oriented Requirements Engineering notation) models [20], [75] stemming from such a consideration is that, despite using the agile approach to software development, this approach is hardly the only method followed by the team, department or organization as a whole. Some interviewees explicitly stated that they use a hybrid approach (integrating agile and plan-driven practices), others claimed that they use a specific agile method (most often Scrum), but at the same time, at the management level, some other method is applied (e.g.…”

Section: Documentation Techniquementioning

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

NORPLAN: Non-functional Requirements Planning for agile processes

Cited by 14 publications

References 8 publications

Non-functional Requirements Documentation in Agile Software Development: Challenges and Solution Proposal

Non-functional Requirements Documentation in Agile Software Development: Challenges and Solution Proposal

Strategies to manage quality requirements in agile software development: a multiple case study

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

Contact Info

Product

Resources

About