Non-Functional Requirements Size Measurement Method (NFSM) with COSMIC-FFP

Non-functional requirements (NFRs) of software systems are an important source of uncertainty in effort estimation. Furthermore, quantitatively approaching NFR early in a project is difficult. This paper makes a step towards reducing the impact of uncertainty due to NFRs. It offers a new generic classification of the NFRs, and a NFR size measurement method (NFSM) that incorporates NFRs into the functional size quantification process. We chose the NFR framework as a vehicle to integrate NFRs into the requirements modeling process and to apply quantitative assessment procedures. Our solution proposal also rests on the functional size measurement method, COSMIC-FFP, adopted in 2003 as the ISO/IEC 19761 standard. We discuss the advantages of our approach and the open questions related to its design as well.

[1]  Roel Wieringa,et al.  The declarative problem frame: designing systems that create and use norms , 2000, Tenth International Workshop on Software Specification and Design. IWSSD-10 2000.

[2]  Maya Daneva,et al.  ERP requirements engineering practice: lessons learned , 2004, IEEE Software.

[3]  Martin Glinz,et al.  Rethinking the Notion of Non-Functional Requirements , 2005 .

[4]  Scott A. Whitmire,et al.  Object-Oriented Design Measurement , 1997 .

[5]  Shari Lawrence Pfleeger,et al.  Software Metrics : A Rigorous and Practical Approach , 1998 .

[6]  George R. Ribeiro-Justo,et al.  Process/sup NFL/: a language for describing non-functional properties , 2002, Proceedings of the 35th Annual Hawaii International Conference on System Sciences.

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

[8]  Dae-Sung Park,et al.  Design phase analysis of soft-ware performance using aspect-oriented programming , 2004 .

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

[10]  Haruhiko Kaiya,et al.  Identifying stakeholders and their preferences about NFR by comparing use case diagrams of several existing systems , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[11]  John E. Gaffney,et al.  Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation , 1983, IEEE Transactions on Software Engineering.

[12]  John Mylopoulos,et al.  Goal-Oriented Requirements Engineering, Part II , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).

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

[14]  John Mylopoulos.  Goal-Oriented Requirements Engineering , 2008, CIbSE.

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

[16]  João Araújo,et al.  Crosscutting quality attributes for requirements engineering , 2002, SEKE '02.

[17]  Nancy G. Leveson,et al.  An investigation of the Therac-25 accidents , 1993, Computer.

[18]  I. Alexander,et al.  Misuse cases help to elicit non-functional requirements , 2003 .

[19]  J. M. Singer,et al.  IEEE Recommended Practice for Software Requirements SpeciÞcations , 1993 .

[20]  Stephen J. Andriole.  Microcomputer decision support systems : design, implementation, and evaluation , 1986 .

[21]  Barry W. Boehm,et al.  Quantitative evaluation of software quality , 1976, ICSE '76.

[22]  Gruia-Catalin Roman,et al.  A taxonomy of current issues in requirements engineering , 1985, Computer.

[23]  Shari Lawrence Pfleeger,et al.  Software Cost Estimation and Sizing Methods, Issues, and Guidelines , 2005 .

[24]  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..

[25]  A. Finkelstein,et al.  A comedy of errors: the London Ambulance Service case study , 1996, Proceedings of the 8th International Workshop on Software Specification and Design.

[26]  John Mylopoulos,et al.  Non-Functional Requirements in Software Engineering , 2000, International Series in Software Engineering.