Volume- 9
Issue- 1
Year- 2021
DOI: 10.21276/ijircst.2021.9.1.3 | DOI URL: https://doi.org/10.21276/ijircst.2021.9.1.3 Crossref
This is an Open Access article distributed under the terms of the Creative Commons Attribution License (CC BY 4.0) (http://creativecommons.org/licenses/by/4.0)
Article Tools: Print the Abstract | Indexing metadata | How to cite item | Email this article | Post a Comment
Sameer S Paradkar
Proper definition and implementation of NFRs is critical. In case they are Over-specify, then the solution may be too costly to be viable; in case they are underspecified or underachieve them, the system will be inadequate for its intended use. An adaptive and incremental approach to exploring, defining, and implementing NFRs is vital for the successful delivering of NFRs. NFRs are not product backlog items. The constraints on development that limit degree of design freedom while building system. These constraints are articulated in the acceptance criteria for multiple product backlog items. For e.g., SAML-based Single Sign-on - SSO is a requirement for the product. SSO is a functional requirement, while SAML is the constraint. In that sense, any backlog item building sign-on functionality would reference the SAML constraint in its acceptance criteria. The sections that follow describe the phases of NFR journey from discovery to deployment for a large complex business critical systems including the NFR modelling framework.
[1] Rajesh Radhakrishnan, “Non-Functional Requirements (NFR) Framework”, Open Group, 2009
[2] Md. Mijanur Rahman, Shamim Ripon, “Elicitation and Modeling Non-Functional Requirements – A POS Case Study”, International Journal of Future Computer and Communication, Vol.2, Issue.5, 2013
[3] Mehrdad Saadatmand, Antonio Cicchetti, Mikael Sj¨odin,“UML-Based Modeling of Non-Functional Requirements in Telecommunication Systems”, The Sixth International Conference on Software Engineering Advances, 2011
[4] Michael Dinkel, Uwe Baumgarten, “Modeling Nonfunctional Requirements: A Basis for dynamic Systems Management”, ACM SIGSOFT Software Engineering Notes. Vol.30. pp.1-8, 2005.
[5] Christopher J. Pavlovski, Joe Zou, “Non-Functional Requirements in Business Process Modeling” , Fifth Asia-Pacific Conference on Conceptual Modelling, 2008
[6] Lirong Dai, Kendra Cooper, “Modeling and Analysis of Non-functional Requirements as Aspects in a UML Based Architecture Design”, International Conference on Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing, 2005
[7] Ethan K. Jackson, Dirk Seifert and Markus Dahlweid, Thomas Santen, Nikolaj Bjrner, Wolfram Schulte, “Specifying and Composing Non-Functional Requirements in Model-based Development”, International Conference, Software Composition, 2009
[8] Pavan Kumar Nanduru, “Non-Functional Requirement Modeling in the Early-Phase Software Product Life Cycle”, Thesis for: Master's Degree in Software Engineering, 2017
[9] Pere Botella, Xavier Burgués, Xavier Franch, Mario Huerta, Guadalupe Salazar, “Modeling Non-Functional Requirements”, 2001
[10]Christopher J. Pavlovski, Joe Zou, “Modeling Architectural Non Functional Requirements: From Use Case to Control Case”, IEEE International Conference on e-Business Engineering (ICEBE'06), 2006
Enterprise Architect, ATOS, Architecture Group, Business & Platform Solutions, Mumbai, India (sameer.paradkar@atos.net)
No. of Downloads: 56 | No. of Views: 1474
Prof. Balwante S S, Rameshwar Kolhe, Nikhil K Pingale, Dipendra Singh Chandel.
March 2024 - Vol 12, Issue 2
Yufeng Li, Weimin Wang, Xu Yan, Min Gao, MingXuan Xiao.
March 2024 - Vol 12, Issue 2
Abhijit Pathak, Arnab Chakraborty, Minhajur Rahaman, Taiyaba Shadaka Rafa, Ummay Nayema.
March 2024 - Vol 12, Issue 2