A Formalism for Extending the NFR Framework to Support the Composition of the Goal Trees

Non-functional requirements are considered as vital factors for producing software of better quality. As a widely adopted non-functional requirements analysis framework, the NFR Framework provides a graphical treatment for goal refinement and evaluation. This paper propose a logical representation for the NFR Framework. In addition, an NFR extension operator and an accompanying extension function for composing multiple viewpoints of NFR are proposed. Compared with the graphical NFR Framework, the logical approach further enhances the reasoning capabilities of the NFR framework. A real-world example has been used to illustrate the formal approach.

[1]  Dov M. Gabbay,et al.  Making Inconsistency Respectable: Part 2 - Meta-level handling of inconsistency , 1993, ECSQARU.

[2]  Axel van Lamsweerde.  Engineering Requirements for System Reliability and Security , 2007 .

[3]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

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

[5]  John Mylopoulos,et al.  Towards requirements-driven information systems engineering: the Tropos project , 2002, Inf. Syst..

[6]  Axel van Lamsweerde,et al.  Reasoning about partial goal satisfaction for requirements and design engineering , 2004, SIGSOFT '04/FSE-12.

[7]  Andrew Ryan.  An Approach To Qunantitative Non-Functional Requirements In Software Development , 2000 .

[8]  Pierre-Yves Schobbens,et al.  A More Expressive Softgoal Conceptualization for Quality Requirements Analysis , 2006, ER.

[9]  Dov M. Gabbay,et al.  Making inconsistency respectable: a logical framework for inconsistency in reasoning , 1991, FAIR.

[10]  Bashar Nuseibeh,et al.  Leveraging Inconsistency in Software Development , 2000, Computer.

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

[12]  Axel van Lamsweerde,et al.  Managing Conflicts in Goal-Driven Requirements Engineering , 1998, IEEE Trans. Software Eng..

[13]  Herbert A. Simon,et al.  The Science of Design: Creating the Artificial , 1988 .

[14]  Paolo Donzelli,et al.  A goal-driven and agent-based requirements engineering framework* , 2004, Requirements Engineering.

[15]  Lawrence Chung,et al.  Dealing with Non-Functional Requirements: Three Experimental Studies of a Process-Oriented Approach , 1995, 1995 17th International Conference on Software Engineering.

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

[17]  John Mylopoulos,et al.  Reasoning with Goal Models , 2002, ER.

[18]  Robert Balzer,et al.  Tolerating Inconsistency , 1991, [1989] Proceedings of the 5th International Software Process Workshop.

[19]  Carlos José Pereira de Lucena,et al.  Integrating scenarios, i*, and AspectT in the context of multi-agent systems , 2006, CASCON.

[20]  John Mylopoulos,et al.  Enterprise modelling for business redesign: the i* framework , 1997, SIGG.

[21]  Lin Liu,et al.  Designing information systems in social context: a goal and scenario modelling approach , 2004, Inf. Syst..

[22]  John Mylopoulos,et al.  Specifying and analyzing early requirements in Tropos , 2004, Requirements Engineering.