Using non-functional requirements templates for elicitation: A case study

It is still an open question how to achieve a proper balance between the cost and value of requirements elicitation. When deciding to assign time and other resources to elicitation, one needs to know what its effectives would be. In the paper we investigate the Structured Elicitation of Non-functional Require-ments(SENoR) method. The method is composed of a sequence of short brainstorming sessions driven by ISO25010 quality characteristics. It uses Non-functional Requirements Templates (NoRTs) to support the elicitation process. Our exploratory case study on cost and effectiveness of SENoR and NoRTs included 7 projects that developed tailor-made web applications. The findings show that two 1.5-hour elicitation workshops can result in non-functional requirements of stability at the level of 80%.

[1]  Gil Taran,et al.  Proposal Based Studio Projects:  How to Avoid Producing "Cookie Cutter" Software Engineers , 2008, 2008 21st Conference on Software Engineering Education and Training.

[2]  Ursula Faber,et al.  Requirements Engineering A Good Practice Guide , 2016 .

[3]  James Robertson,et al.  Mastering the Requirements Process: Getting Requirements Right , 2012 .

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

[5]  Kent Beck,et al.  Extreme Programming Explained: Embrace Change (2nd Edition) , 2004 .

[6]  Miroslaw Ochodek,et al.  Software development studio — Bringing industrial environment to a classroom , 2012, 2012 First International Workshop on Software Engineering Education Based on Real-World Experiences (EduRex).

[7]  Jerzy Nawrocki,et al.  Structured meetings for non-functional requirements elicitation , 2011 .

[8]  Markus Strohmaier,et al.  Can Patterns Improve i* Modeling? Two Exploratory Studies , 2008, REFSQ.

[9]  J. Hart.  [Qualitative methods]. , 2000, Recherche en soins infirmiers.

[10]  Alan M. Davis,et al.  Requirements elicitation and elicitation technique selection: model for two knowledge-intensive software development processes , 2003, 36th Annual Hawaii International Conference on System Sciences, 2003. Proceedings of the.

[11]  John A. McDermid,et al.  Ten steps towards systematic requirements reuse , 2008, Requirements Engineering.

[12]  Stephen Withall.  Software Requirement Patterns , 2007 .

[13]  Jane Cleland-Huang.  Quality Requirements and their Role in Successful Products , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[14]  Kanad K. Biswas,et al.  Using Grammatical Knowledge Patterns for structuring requirements specifications , 2013, 2013 3rd International Workshop on Requirements Patterns (RePa).

[15]  Sabrina Hirsch,et al.  Requirements By Collaboration Workshops For Defining Needs , 2016 .

[16]  A. Sutcliffe,et al.  A technique combination approach to requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

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

[18]  Klaus Pohl,et al.  The Three Dimensions of Requirements Engineering , 1993, CAiSE.

[19]  Julio Cesar Sampaio do Prado Leite,et al.  An NFR Pattern Approach to Dealing with NFRs , 2010, 2010 18th IEEE International Requirements Engineering Conference.

[20]  Barbara Paech,et al.  MOQARE: misuse-oriented quality requirements engineering , 2008, Requirements Engineering.

[21]  Ken Schwaber,et al.  SCRUM Development Process , 1997 .

[22]  Wu Yue,et al.  Towards a Multiple Ontology Framework for Requirements Elicitation and Reuse , 2007, COMPSAC.

[23]  Jane Cleland-Huang,et al.  A Persona-Based Approach for Exploring Architecturally Significant Requirements in Agile Projects , 2013, REFSQ.

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

[25]  Liping Zhao,et al.  Towards a generalised framework for classifying and retrieving requirements patterns , 2011, 2011 First International Workshop On Requirements Patterns.

[26]  Tore Dyba,et al.  Process research in requirements elicitation , 2013, 2013 3rd International Workshop on Empirical Requirements Engineering (EmpiRE).

[27]  Paul Grünbacher.  Collaborative requirements negotiation with EasyWinWin , 2000, Proceedings 11th International Workshop on Database and Expert Systems Applications.

[28]  Jerzy R. Nawrocki,et al.  Balancing Agility and Discipline with XPrince , 2005, RISE.

[29]  Venkataraman Ramesh,et al.  Improving information requirements determination: a cognitive perspective , 2002, Inf. Manag..

[30]  Carme Quer,et al.  A pattern-based method for building requirements documents in call-for-tender processes , 2009, Int. J. Comput. Sci. Appl..

[31]  Andrea Herrmann,et al.  Exploring the Characteristics of NFR Methods - A Dialogue About Two Approaches , 2007, REFSQ.

[32]  Franz Lehner,et al.  Requirements Engineering as a Success Factor in Software Projects , 2001, IEEE Softw..

[33]  Bashar Nuseibeh.  Ariane 5: Who Dunnit? , 1997, IEEE Software.

[34]  Laurie A. Williams,et al.  Security requirements patterns: understanding the science behind the art of pattern writing , 2012, 2012 Second IEEE International Workshop on Requirements Patterns (RePa).