Richard R. Maiti
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 priority of FRs. 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.
- Quyen L. Nguyen. 2009. Non-functional requirements analysis modeling for software product lines. In Proceedings of the 2009 ICSE Workshop on Modeling in Software Engineering (MISE '09). IEEE Computer Society, Washington, DC, USA, 56--61. Google Scholar
Digital Library
- Danylenko, A. and Lowe, W. 2012. Context-aware recommender systems for non- functional requirement. In Proceeding of the 3rd International Workshop on Recommendation Systems for Software Engineering (RSSE '12), Zurich, Switzerland, 80--84. Google ScholarDigital Library
- Slankas, J and Williams, L. 2013. Automated extraction of non-functional requirement in available documents. In Proceeding of the 1st International Workshop on Natural Language Analysis in Software Engineering (NaturaLise '13), San Francisco, CA, 9--16.Google Scholar
- Saadatmand, M., Cicchetti, A., and Sjodin, M. 2012. Toward model-based trade-off analysis of non-functional requirements (SEAA'12). In proceedings of the 38th Conference on EUROMICROS (SEAA '12), Cesme. Google ScholarDigital Library
- Bajapi, V. and Gorthi, R. P. 2012. On non-functional requirements: A Survey. In Proceeding of the International Conference on Computer Networks and Information Technology (ICCNIT'12), Abbottabad, Pakistan, 333--340.Google Scholar
- Farid, W. M. and Mitropoulos, F. J. 2012. Novel lightweight engineering artifacts for modeling non-functional requirements in agile processes. In proceedings of IEEE, (Southeastcon '12), Orlando, FL, 1--7.Google Scholar
- Aasem, M., Ramazan, M. & Jaffar, A. 2010. Analysis and optimization of software requirements prioritization techniques, In proceedings of the International Conference On Emerging Technologies (ICIET '10), Karachi, Pakistan, 14--16.Google ScholarCross Ref
- Veerappa, V. and Letier, E. 2011. Clustering stakeholders for requirement decision making. Requirements Engineering: Foundation for Software Quality Lecture Notes in Computer Science, 6606, 202--208. Google ScholarDigital Library
- European Dynamics S.A. 2005. Functional Requirements for Conducting Electronic Public Procurement Under the EU Framework (Volume 1). Internet: http://ec.europa.eu/internal_market/publicprocurement/docs/eprocurement/functional-reguirements-vol1_en.pdf European Dynamics S.A. (May 30, 2015).Google Scholar
- Functional Requirements for Conducting Electronic Public Procurement Under the EU Framework (Volume 2). Internet: http://ec.europa.eu/internal_market/publicprocurement/docs/eprocurement/functional-reguirements-vol2_en.pdfGoogle Scholar
- Maiti, R. R. and Mitropoulos, F. J. 2015. Capturing, eliciting, predicting and prioritizing (CEPP) non-functional requirements metadata during the early stages of agile software development. In proceedings of IEEE, (Southeastcon '15), Fort Lauderdale, FL, 1--8.Google Scholar
- Domah, D. 2013. The NERV methodology: Nonfunctional requirements elicitation, reasoning and validation in agile processes (Doctoral Dissertation) ProQuest Dissertation and Thesis database (UMI No. 3594275)Google Scholar
- Faird, W. M. 2011. The NORMAP methodology: Non functional requirements modeling for agile processes (Doctoral Dissertation) ProQuest Dissertation and Thesis database. (UMI No. 3460458)Google Scholar
- Maiti, R. R. 2016. Capturing, Eliciting, and Prioritizing (CEP) Non-Functional Requirements Metadata during the Early Stages of Agile Software Development ProQuest Dissertation and Thesis database. (UMI No. 10128003)Google Scholar
- Prioritizing Non-Functional Requirements in Agile Software Engineering
Recommendations
Non-functional Requirement Patterns for Agile Software Development
ICSEB '19: Proceedings of the 2019 3rd International Conference on Software and e-BusinessFollowing the agile principles, agile software development is popular among software developing organizations. The attractive characteristics of agile development are that it embraces frequent changes and that it gives high priority to users. Due to ...
Are "non-functional" requirements really non-functional?: an investigation of non-functional requirements in practice
ICSE '16: Proceedings of the 38th International Conference on Software EngineeringNon-functional requirements (NFRs) are commonly distinguished from functional requirements by differentiating how the system shall do something in contrast to what the system shall do. This distinction is not only prevalent in research, but also ...
Predicting NFRs in Agile Software Engineering
SIGITE '18: Proceedings of the 19th Annual SIG Conference on Information Technology EducationNon-Functional requirements (NFRs) are overlooked where as Functional Requirements (FRs) take the center stage in developing agile software. Research has shown that ignoring NFRs can have negative impact on the software and could potentially cost more ...
Comments