pith. sign in

arxiv: 1711.08894 · v1 · pith:6X5G27Z2new · submitted 2017-11-24 · 💻 cs.SE

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

classification 💻 cs.SE
keywords nfrsdocumentationsoftwareagilechallengescompaniesdevelopmentnon-functional
0
0 comments X
read the original 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. Please refer to the manuscript for the full abstract.

This paper has not been read by Pith yet.

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.