Knowledge meaning and management in requirements engineering

What is the meaning of knowledge in requirements engineering?What approaches are proposed to manage knowledge in requirements engineering?Can the efficiency and the efficacy of knowledge management models be evidenced in requirements engineering?The knowledge management used to construct the requirements specification should be performed in a structured manner to discover, analyze and understand the datainformationknowledge chain. It is traditionally assumed that requirements specification, as a product of requirements engineering, has a high impact on the ensuing software development stages. Therefore, the knowledge management used to construct the requirements specification should be performed in a structured manner to discover, analyze and understand the datainformationknowledge chain, both tacit and explicit, that the interested parties possess. In this article, the results of a literature review are presented, seeking to answer the following questions: (1) What is the meaning of knowledge in requirements engineering? (2) What approaches are proposed to manage knowledge in requirements engineering? (3) Can the efficiency and the efficacy of knowledge management models be evidenced in requirements engineering? Thirty-six works were chosen for analysis out of a total 83 found in our search. The analysis showed that (1) knowledge has a central significance at this stage, but the authors have yet to agree on the best methods to impart and apply that knowledge; (2) no general framework has emerged as a validated approach to manage knowledge for requirements engineering; and (3) the evaluation marks for model efficiency and efficacy are low, consisting mostly of personal interpretations.

[1]  M. Bunge,et al.  Filosofía de la psicología , 1988 .

[2]  Stephen Gourlay,et al.  The SECI model of knowledge creation: some empirical shortcomings , 2003 .

[3]  Pearl Brereton,et al.  Lessons from applying the systematic literature review process within the software engineering domain , 2007, J. Syst. Softw..

[4]  Javier Andrade Garda,et al.  A Reference Model for Knowledge Management in Software Engineering , 2006, Eng. Lett..

[5]  Pearl Brereton,et al.  Systematic literature reviews in software engineering - A systematic literature review , 2009, Inf. Softw. Technol..

[6]  S. Alshawi,et al.  Knowledge management: Using a knowledge requirements framework to enhance UK health sector supply chains , 2008 .

[7]  Paolo Donzelli,et al.  Requirements Engineering for Knowledge Management in eGovernment , 2003, KMGov.

[8]  Stephanie M. White,et al.  Application of cognitive theories and knowledge management to requirements engineering , 2010, 2010 IEEE International Systems Conference.

[9]  Chi Fai Cheung,et al.  Self-associated concept mapping for representation, elicitation and inference of knowledge , 2008, Knowl. Based Syst..

[10]  Miguel Mira da Silva,et al.  Gamifying requirement elicitation: Practical implications and outcomes in improving stakeholders collaboration , 2014, Entertain. Comput..

[11]  Dominik Schmitz,et al.  Managing dynamic requirements knowledge : an agent-based approach , 2010 .

[12]  Andreas Breiter,et al.  Requirements development in loosely coupled systems: building a knowledge management system with schools , 2004, 37th Annual Hawaii International Conference on System Sciences, 2004. Proceedings of the.

[13]  I. Nonaka.  A Dynamic Theory of Organizational Knowledge Creation , 1994 .

[14]  Azeddine Chikh,et al.  A Knowledge Management Framework in Software Requirements Engineering Based on the SECI Model , 2011 .

[15]  John Mylopoulos,et al.  Ontologies for Knowledge Management: An Information Systems Perspective , 2004, Knowledge and Information Systems.

[16]  Jouni Similä,et al.  Utilizing online serious games to facilitate distributed requirements elicitation , 2015, J. Syst. Softw..

[17]  Jonathan Low.  The value creation index , 2000 .

[18]  Thomas H. Davenport,et al.  Book review:Working knowledge: How organizations manage what they know. Thomas H. Davenport and Laurence Prusak. Harvard Business School Press, 1998. $29.95US. ISBN 0‐87584‐655‐6 , 1998 .

[19]  Tore Dybå,et al.  Empirical studies of agile software development: A systematic review , 2008, Inf. Softw. Technol..

[20]  Kimiz Dalkir,et al.  Knowledge Management in Theory and Practice , 2005 .

[21]  J. Biggs,et al.  Teaching For Quality Learning At University , 1999 .

[22]  Retha Snyman,et al.  Coping with Continuous Change in the Business Environment: Knowledge Management and Knowledge Management Technology , 2008 .

[23]  G. McLean,et al.  Linking organizational culture, structure, strategy, and organizational effectiveness: Mediating role of knowledge management , 2010 .

[24]  Dorota Buchnowska,et al.  Customer Knowledge Management Models: Assessment and Proposal , 2011, SIGSAND.

[25]  Mamoona Humayoun,et al.  Towards Knowledge Management in RE Practices to Support Software Development , 2015 .

[26]  Maria Isabel Sánchez Segura,et al.  Knowledge management acquisition improvement by using software engineering elicitation techniques , 2014, Comput. Hum. Behav..

[28]  Pedro R. Falcone Sampaio,et al.  Applying collaborative process design to user requirements elicitation: A case study , 2013, Comput. Ind..

[29]  Alexander Felfernig,et al.  An Overview of Recommender Systems in Requirements Engineering , 2013, Managing Requirements Knowledge.

[30]  F. Hegazy,et al.  The Influence of Knowledge Management on Organizational Business Processes' and Employees' Benefits , 2014 .

[31]  Efraim Turban,et al.  Decision Support and Business Intelligence Systems (8th Edition) , 2006 .

[32]  Shuib Basri,et al.  Knowledge management in software process improvement: A case study of very small entities , 2011 .

[33]  Dirk Basten,et al.  Knowledge Creation in Requirements Engineering - A Systematic Literature Review , 2013, Wirtschaftsinformatik.

[34]  Sjaak Brinkkemper,et al.  REfine: A gamified platform for participatory requirements engineering , 2015, 2015 IEEE 1st International Workshop on Crowd-Based Requirements Engineering (CrowdRE).

[35]  Stefanos Mouzas,et al.  Efficiency versus effectiveness in business networks , 2006 .

[36]  E. Laurier,et al.  Towards an interactional approach to reflective practice in social work , 2016, Private Troubles or Public Issues?.

[37]  Abdulmajid Mohamed,et al.  Facilitating tacit-knowledge acquisition within requirements engineering , 2010 .

[38]  Stephen Denning,et al.  The Springboard: How Storytelling Ignites Action in Knowledge-Era Organizations , 2000 .

[39]  Daniel Pérez,et al.  Tecnologías de la información para la gestión del conocimiento , 2007 .

[40]  A. Hafez,et al.  Integrated Knowledge Management System (IKMS) , 2008, 2008 IEEE Conference on Technologies for Homeland Security.

[41]  Rusli Abdullah,et al.  Identifying knowledge components in software requirement elicitation , 2014, 2014 IEEE International Conference on Industrial Engineering and Engineering Management.

[42]  Stéphane Faulkner,et al.  What stakeholders will or will not say: A theoretical and empirical study of topic importance in Requirements Engineering elicitation interviews , 2014, Inf. Syst..

[43]  Jiangping Wan,et al.  Research on Explicit and Tacit Knowledge Interaction in Software Process Improvement Project , 2011, J. Softw. Eng. Appl..