Supporting quantitative reasoning of non-functional requirements: A process-oriented approach

A long standing problem in software engineering is inadequate requirements elicitation, analysis, specification, validation and management. The lack of well defined requirements is one of the major causes of project failure. Several well-known techniques and frameworks have been developed to deal with the functional aspect of requirements engineering. Recent years have also seen the emergence of frameworks that incorporate non-functional requirements. The Non-Functional Requirements (NFR) Framework models non-functional requirements and associated implementation methods. This paper presents a process-orientated, lightweight, quantitative extension to the NFR Framework; focusing on providing quantitative support to the decision process and how decisions affect the system.

[1]  Pamela Zave.  Classification of research efforts in requirements engineering , 1997, ACM Comput. Surv..

[2]  Martin S. Feather,et al.  Quantitative risk-based requirements reasoning , 2003, Requirements Engineering.

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

[4]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[5]  Axel van Lamsweerde,et al.  Reasoning About Alternative Requirements Options , 2009, Conceptual Modeling: Foundations and Applications.

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

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