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

November 24, 2017 Β· Declared Dead Β· πŸ› International Conference on Product Focused Software Process Improvement

πŸ‘» CAUSE OF DEATH: Ghosted
No code link whatsoever

"No code URL or promise found in abstract"

Evidence collected by the PWNC Scanner

Authors Woubshet Behutiye, Pertti KarhapÀÀ, Dolors Costal, Markku Oivo, Xavier Franch arXiv ID 1711.08894 Category cs.SE: Software Engineering Citations 64 Venue International Conference on Product Focused Software Process Improvement Last Checked 3 months ago
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.
Community shame:
Not yet rated
Community Contributions

Found the code? Know the venue? Think something is wrong? Let us know!

πŸ“œ Similar Papers

In the same crypt β€” Software Engineering

Died the same way β€” πŸ‘» Ghosted