@inproceedings{437f35ee106e4c10a71c1b1f043e125e,
title = "Prioritizing non-functional requirements in agile software engineering",
abstract = "Developing agile software is a method to deliver and develop software products quickly and effectively. Agile methodology tends to favor Functional Requirements (FRs) while disregarding Non-Functional Requirements (NFRs). Disregarding NFRs can have adverse effects on software that can result in lower quality and increased rate to repair software in later stages. This research is a component of the Capture Elicit and Prioritizing (CEP) methodology. The Prioritizing part of the methdology is covered in this paper. The goal of this research focuses on the prioritizing part to improve the prioritization of NFRs. This study provides methods in NFRs prioritization during beginning stages in agile development process. The Capture Elicit Prioritize methodology prioritizes NFRs by using the αβγ- framework similar to p r i o r i t y o f F R s . The αβγ- framework provides unique capabilities to development teams. The interchanging capabilities of the αβγ-framework allows developers to be flexible. Prioritization of NFRs concurs with developing agile software. This accommodates agile developer to plan for budget and time. ",
keywords = "Agile Software Engineering, FRs, Functional Requirements, NFR Priority, NFRs, Non- Functional Requirements",
author = "Richard Maiti and Frank Mitropoulos",
year = "2017",
month = apr,
day = "13",
doi = "10.1145/3077286.3077565",
language = "English",
series = "Proceedings of the SouthEast Conference, ACMSE 2017",
publisher = "Association for Computing Machinery, Inc",
pages = "212--214",
booktitle = "Proceedings of the SouthEast Conference, ACMSE 2017",
note = "2017 ACM SouthEast Regional Conference, ACMSE 2017 ; Conference date: 13-04-2017 Through 15-04-2017",
}