Requirements engineering based on knowledge: a comparative case study of the KMoS-RE strategy and the DMS process
DOI:
https://doi.org/10.17533/udea.redin.n77a11Keywords:
knowledge management, tacit knowledge, empirical software engineering, requirements engineeringAbstract
Nowadays, a difficult problem that software development companies are facing in the elicitation and discovering requirement process is the management of tacit knowledge, which is valuable information that for some reason remains hidden to the developers. The Knowledge Management on a Strategy for Requirements Engineering (KMoS-RE) is especially designed to face that problem and obtain a set of requirements that fulfi ll the clients’ needs and expectations. This paper presents the design and preliminary results of an empirical study that compares the KMoS-RE strategy with the requirements elicitation process proposed by MoProSoft; a Mexican software process model oriented to the specifi c needs of the software industry in Mexico. Preliminary results show that KMoS-RE seems to be more suitable than the before mentioned process proposed by MoProSoft.
Downloads
References
L. McLeod and S. MacDonell, “Factors that affect software systems development project outcomes: A survey of research”, ACM Computing Surveys (CSUR), vol. 43, no. 4, pp. 24-56, 2011.
S. Hansen, N. Berente and K. Lyytinen, “Requirements in the 21st century: Current practice and emerging trends”, in Design requirements engineering: A tenyear perspective, 1st ed., K. Lyytinen, P. Loucopoulos, J. Mylopoulos and W. Robinson (eds). Cleveland, USA: Springer, 2009, pp. 44-87.
L. Pilat and H. Kaindl, “A Knowledge Management Perspective of Requirements Engineering”, in 5th International Conference on Research Challenges in Information Science (RCIS), Guadeloupe, France, 2011, pp. 1-12.
A. Distanont, H. Haapasalo, M. Vaananen and J. Lehto, “The engagement between knowledge transfer and requirements engineering”, International Journal of Management, Knowledge and Learning, vol. 1, no. 2, pp. 131-156, 2012.
M. Polanyi, The tacit dimension, 1st ed. Garden City, USA: Doubleday, 1966.
R. Gacitua et al., “Making Tacit Requirements Explicit”, in 2nd International Workshop on Managing Requirements Knowledge (MARK), Atlanta, USA, 2009, pp. 40-44.
K. Olmos and J. Rodas, “KMoS-RE: knowledge management on a strategy to requirements engineering”, Requirements Engineering Journal, vol. 19, no. 4, pp. 421-440, 2014.
P. Bresciani, A. Perini, P. Giorgini, F. Giunchiglia and J. Mylopoulos, “Tropos: An Agent-Oriented Software Development Methodology”, Autonomous Agents and Multi-Agent Systems, vol. 8, no. 3, pp. 203-236, 2004.
R. Darimont and A. Lamsweerde, “Formal Refinement Patterns for Goal-Driven Requirements Elaboration”, ACM SIGSOFT Software Engineering Notes, vol. 21, no. 6, pp. 179-190, 1996.
I. Jureta, A. Borgida, N. Ernst and J. Mylopoulos, “Towards a New Generation of Requirements Modeling Languages with Goals, Preferences, and Inconsistency Handling”, in 18th IEEE International on Requirements Engineering Conference, Sydney, Australia, 2010, pp. 115-124.
H. Oktaba, “MoProSoft®: A Software Process Model for Small Enterprises”, in 1st International Research Workshop for Process Improvement in Small Settings, Pittsburgh, USA, 2006, pp. 93-101.
Dines Bjørner, “Rôle of domain engineering in software development. Why current requirements engineering is flawed!”, in 7th International Andrei Ershov Memorial Conference on Perspectives of Systems Informatics (PSI), Novosibirsk, Russia, 2009, pp. 2-34.
G. Hadad, “Uso de escenarios en la derivación de software”, Ph.D. dissertation, National University of La Plata, La Plata, Argentina, 2008.
L. Ma, B. Nuseibeh, P. Piwek, A. Roeck and A. Willis, “On presuppositions in requirements”, in 2nd International Workshop on Managing Requirements Knowledge (MARK), Atlanta, USA, 2009, pp. 27-31.
M. Mitri, “Applying tacit knowledge management techniques for performance assessment”, Computers & Education, vol. 41, no. 2, pp. 173-189, 2003.
I. Nonaka and H. Takeuchi, “The knowledge-creating company: how japanese companies create the dynamics of innovation”, Hardvard Business Review, vol. 69, no. 6, pp. 96-104, 1995.
P. Runeson and M. Höst, “Guidelines for conducting and reporting case study research in software engineering”, Empirical Software Engineering, vol. 14, no. 2, pp. 131-164, 2009.
Downloads
Published
How to Cite
Issue
Section
License
Copyright (c) 2015 Revista Facultad de Ingeniería Universidad de Antioquia
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Revista Facultad de Ingeniería, Universidad de Antioquia is licensed under the Creative Commons Attribution BY-NC-SA 4.0 license. https://creativecommons.org/licenses/by-nc-sa/4.0/deed.en
You are free to:
Share — copy and redistribute the material in any medium or format
Adapt — remix, transform, and build upon the material
Under the following terms:
Attribution — You must give appropriate credit, provide a link to the license, and indicate if changes were made. You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
NonCommercial — You may not use the material for commercial purposes.
ShareAlike — If you remix, transform, or build upon the material, you must distribute your contributions under the same license as the original.
The material published in the journal can be distributed, copied and exhibited by third parties if the respective credits are given to the journal. No commercial benefit can be obtained and derivative works must be under the same license terms as the original work.
Twitter