Towards an Artifact-Oriented Requirements Engineering Model for Developing Successful Products, Services, and Systems: Identification of Model Requirements

Despite extensive research in the domain of requirements engineering (RE), companies still struggle with this discipline. Moreover, practitioners are challenged with developing successful products, services, and systems which address the true needs of their customers. This gives rise to a new research field in the domain of RE, namely artifact orientation. According to the literature, this artifact orientation should increase the success of RE significantly. By conducting a literature review and 7 expert interviews, we identified 7 model requirements (MRs) for an artifact-oriented RE model. Furthermore, the results of this paper suggest that existing artifact-oriented RE models do not sufficiently address all identified MRs. In particular, these models lack the combination of traditional RE practices, such as goal orientation, documentation, and traceability with novel agile approaches. Furthermore, there is a need for a more holistic RE which merges the domains of product, service, and software engineering.

[1]  Richard T. Watson,et al.  Analyzing the Past to Prepare for the Future: Writing a Literature Review , 2002, MIS Q..

[2]  Stuart J. Barnes,et al.  An empirical exploration of requirements engineering for hybrid products , 2009 .

[3]  Birgit Penzenstadler,et al.  Artefact-based requirements engineering: the AMDiRE approach , 2014, Requirements Engineering.

[4]  Jacob Cohen,et al.  Weighted kappa: Nominal scale agreement provision for scaled disagreement or partial credit. , 1968 .

[5]  Colin J. Neill,et al.  State of practice in requirements engineering: contemporary data , 2014, Innovations in Systems and Software Engineering.

[6]  Jeffrey O. Grady.  System requirements analysis , 1993 .

[7]  Jukka Kääriäinen,et al.  Requirements engineering Inventory of technologies , 2003 .

[8]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[9]  Stefan Wagner,et al.  Naming the pain in requirements engineering: design of a global family of surveys and first results from Germany , 2013, EASE '13.

[10]  Jo Hanisch,et al.  Impediments to requirements engineering during global software development , 2007, Eur. J. Inf. Syst..

[11]  Austen Rainer,et al.  Using an expert panel to validate a requirements process improvement model , 2005, J. Syst. Softw..

[12]  Manfred Broy,et al.  Challenges in automotive software engineering , 2006, ICSE.

[13]  Fausto Giunchiglia,et al.  Tropos: An Agent-Oriented Software Development Methodology , 2004, Autonomous Agents and Multi-Agent Systems.

[14]  Jaejoon Lee,et al.  A holistic approach to feature modeling for product line requirements engineering , 2013, Requirements Engineering.

[15]  Rainer Grau.  Requirements Engineering in Agile Software Development , 2012 .

[16]  Jeff Sutherland,et al.  Manifesto for Agile Software Development , 2013 .

[17]  Klaus Pohl.  Requirements Engineering - Grundlagen, Prinzipien, Techniken (2. Aufl.) , 2008 .

[18]  Pericles Loucopoulos,et al.  Enterprise Modelling and the Teleological Approach to Requirements Engineering , 1995, Int. J. Cooperative Inf. Syst..

[19]  Karl Cox,et al.  Empirical study of Sommerville and Sawyer's requirements engineering practices , 2009, IET Softw..

[20]  Björn Niehaves,et al.  Reconstructing the giant: On the importance of rigour in documenting the literature search process , 2009, ECIS.

[21]  Manfred Broy,et al.  Ein Requirements-Engineering-Referenzmodell , 2007, Informatik-Spektrum.

[22]  M. Dewey,et al.  Coefficients of Agreement , 1983, British Journal of Psychiatry.

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

[24]  Jan Marco Leimeister,et al.  A requirements data model for product service systems , 2012, Requirements Engineering.

[25]  B. Everitt,et al.  Statistical methods for rates and proportions , 1973 .

[26]  Klaus Pohl,et al.  COSMOD-RE: Supporting the Co-Design of Requirements and Architectural Artifacts , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[27]  Austen Rainer,et al.  Requirements problems in twelve software companies: an empirical analysis , 2002, IEE Proc. Softw..

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

[29]  H. Hoffmann.  Streamlining the development of complex systems through model-based systems engineering , 2012, 2012 IEEE/AIAA 31st Digital Avionics Systems Conference (DASC).

[30]  Alan M. Davis,et al.  A Unified Model of Requirements Elicitation , 2004, J. Manag. Inf. Syst..

[31]  Lia Patrício,et al.  Requirements engineering for multi-channel services: the SEB method and its application to a multi-channel bank , 2009, Requirements Engineering.

[32]  Tony Gorschek,et al.  Requirements Abstraction Model , 2005, Requirements Engineering.

[33]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[34]  Birgit Penzenstadler,et al.  Understanding the Impact of Artefact-Based RE -- Design of a Replication Study , 2013, 2013 ACM / IEEE International Symposium on Empirical Software Engineering and Measurement.

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

[36]  Manfred Broy,et al.  Requirements Engineering as a Key to Holistic Software Quality , 2006, ISCIS.

[37]  Jan Marco Leimeister,et al.  Towards a competency model for requirements analysts , 2012, Inf. Syst. J..

[38]  Richard Baskerville,et al.  Agile requirements engineering practices and challenges: an empirical study , 2007, Inf. Syst. J..

[39]  Amy L. Spawr.  Drive: the surprising truth about what motivates us, Pink, D.H. (2009). New York, NY (pp. 1–242) , 2012 .

[40]  Saonee Sarker,et al.  Exploring Agility in Distributed Information Systems Development Teams: An Interpretive Study in an Offshoring Context , 2009, Inf. Syst. Res..

[41]  Behrouz Homayoun Far,et al.  A methodology for the selection of requirements engineering techniques , 2008, Software & Systems Modeling.