Analysis of Uml to Gather Non Functional Requirements
(
Analysis of UML to Gather Non Functional Requirements
Batool, A. Malik, Z. and Shabbir, S.
Abstract— During the process of software development, gathering requirement is the very imperative task. Both functional as well as non functional requirements play an important role in building the quality software. Little work has been done in the field of gathering the non functional requirements. To reflect the FRs and NFR’s properly, a solid architectural foundation is needed. Modeling is the best way to achieve such a goal, and Using UML tools can help to achieve the goal of eliciting functional as well as non functional requirements. We use UML models to represent FRs and NFRs of the system because UML has emerged as the industry standard for software modeling notations. This work provides the thorough and comprehensive work done in the field of eliciting non functional requirements. A new technique has been presented that helps in getting the non functional requirements right. This technique covers all the phases of requirement engineering and produces very valid results, as the goal of requirement engineering i.e.. Fulfilling the demands of stakeholder is completely satisfied.
Index Terms-- Aspect oriented approach, Goal oriented approach, Non Functional requirements, UML.
INTRODUCTION
During the process of software development gathering requirement is the very important task, we can say that it is the “brain” of the system being developed. If this is done right, the whole system is going to perform efficiently or according to the needs of the stakeholder. There are two main types of requirements: Functional and Non-Functional. Functional requirements specify specific behavior or functions whereas Non-functional requirements specify all the remaining requirements not covered by the functional requirements. They specify criteria that judge the operation of a system, rather than specific behaviors.
For the past ten years, the Requirements
Analysis of UML to Gather Non Functional Requirements
Batool, A. Malik, Z. and Shabbir, S.
Abstract— During the process of software development, gathering requirement is the very imperative task. Both functional as well as non functional requirements play an important role in building the quality software. Little work has been done in the field of gathering the non functional requirements. To reflect the FRs and NFR’s properly, a solid architectural foundation is needed. Modeling is the best way to achieve such a goal, and Using UML tools can help to achieve the goal of eliciting functional as well as non functional requirements. We use UML models to represent FRs and NFRs of the system because UML has emerged as the industry standard for software modeling notations. This work provides the thorough and comprehensive work done in the field of eliciting non functional requirements. A new technique has been presented that helps in getting the non functional requirements right. This technique covers all the phases of requirement engineering and produces very valid results, as the goal of requirement engineering i.e.. Fulfilling the demands of stakeholder is completely satisfied.
Index Terms-- Aspect oriented approach, Goal oriented approach, Non Functional requirements, UML.
INTRODUCTION
During the process of software development gathering requirement is the very important task, we can say that it is the “brain” of the system being developed. If this is done right, the whole system is going to perform efficiently or according to the needs of the stakeholder. There are two main types of requirements: Functional and Non-Functional. Functional requirements specify specific behavior or functions whereas Non-functional requirements specify all the remaining requirements not covered by the functional requirements. They specify criteria that judge the operation of a system, rather than specific behaviors.
For the past ten years, the Requirements
References: 1] LUIZ MARCIO CYSNEIROS AND ERIC YU DEPARTMENT OF MATHEMATICS AND STATISTICS YORK UNIVERSITY FACULTY OF INFORMATION STUDIES; “NON-FUNCTIONAL REQUIREMENTS: A COMPREHENSIVE APPROACH”; ACM ORGANIZATION; 2001 2] Gerd Wagner Eindhoven Univ. of Technology, Faculty of Technology Management,“A UML Profile for Agent-Oriented Modeling”; 2002 3] Bresciani P., Giorgini P., Giunchiglia F., Mylopoulos J., Perini A. ; “Tropos: An Agent−Oriented Software Development Methodology”; December 2002 4] Phillip A. Laplante ; “What Every Engineer Should Know about Software Engineering”; 2004 Page 44. 5] Amund Tveit amund.tveit@idi.ntnu.no Norwegian University of Science and Technology; “A survey of Agent-Oriented Software Engineering”; May 8, 2001 6] Raquel Hill, Jun Wang Department of Computer Science/ NCSA University of Illinois Urbana-Champaign; “Quantifying Non-Functional Requirements: A Process Oriented Approach” ; IEEE Computer Society; 2004 7] João Araújo and Ana Moreira Dept. Informática, FCT Universidade Nova Lisboa, Caparica, Portugal, Isabel Brito Dept. de Engenharia Instituto Politécnico de Beja, Portugal, Awais Rashid Computing Department Lancaster University Lancaster; “Aspect-Oriented Requirements with UML”; 2002 8] Muhammad Rizwan Abid, Daniel Amyot and Stéphane Sotèg Som University of Ottawa; “A Uml Profile For Goal-Oriented Modelling” Telelogic Americas User Group Conference Centro Per La Ricerca Scientifica E Tecnologica 38050 Povo (Trento), Italy; 2008 9] Chung, L., Nixon, B., Yu, E. and Mylopoulos, J; “Non-Functional Requirements in Software Engineering”; Kluwer Academic Publishers2000