Modeling Nonfunctional Requirements – A Case Study

A key to successful software development is a clear understanding of the requirements. Requirement analysis is to be carried out at the earlier stage of software development life cycle to avoid requirement related problem at a later stage. Both functional (FR) and non-functional requirement (NFR) play crucial role in software development. A common industrial practice is not to consider NFR at the earlier stage of software development, hence NFR may not be reflected in the design stage and it may lead to a failed product. Addressing these issues, this work-in progress paper extends the traditional feature diagram to model NFR of a system along with its functional features. Such model facilitates a clear view of both NFR and FR at the early stage of system development. An extension of UML use case diagram is demonstrated that enables the elicitation and modeling of NFR in a convenient manner. A case study of Point of Sale (POS) system is presented illustrating the NFR modeling steps. Keywords— NFR, feature diagram, point of sale, UML

[1]  David R. Lindstrom.  Five Ways to Destroy a Development Project , 1993, IEEE Softw..

[2]  Ivar Jacobson,et al.  The unified modeling language reference manual , 2010 .

[3]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[4]  Julio Cesar Sampaio do Prado Leite,et al.  Nonfunctional requirements: from elicitation to conceptual models , 2004, IEEE Transactions on Software Engineering.

[5]  Julio Cesar Sampaio do Prado Leite,et al.  The world?s a stage: a survey on requirements engineering using a real-life case study , 1999, J. Braz. Comput. Soc..

[6]  Krzysztof Czarnecki,et al.  Generative programming - methods, tools and applications , 2000 .

[7]  Julio Cesar Sampaio do Prado Leite,et al.  Integrating non-functional requirements into data modeling , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[8]  Shailey Minocha,et al.  Scenario-based Analysis of Non-Functional Requirements , 1998, REFSQ.

[9]  Shamim Ripon,et al.  Modeling and analysis of product-line variants , 2012, SPLC '12.

[10]  Julio Cesar Sampaio do Prado Leite,et al.  A Framework for Integrating Non-Functional Requirements into Conceptual Models , 2001, Requirements Engineering.

[11]  Kyo Chul Kang,et al.  Feature-Oriented Domain Analysis (FODA) Feasibility Study , 1990 .

[12]  John Mylopoulos,et al.  Representing and Using Nonfunctional Requirements: A Process-Oriented Approach , 1992, IEEE Trans. Software Eng..

[13]  Jr. Brooks F.P..  No Silver Bullet Essence and Accidents of Software Engineering , 1987 .

[14]  Julio Cesar Sampaio do Prado Leite,et al.  On Non-Functional Requirements in Software Engineering , 2009, Conceptual Modeling: Foundations and Applications.