Revista GTI

Vol. 4 No. 10 (2005): Revista GTI
Articles

FACILITANDO EL ACCESO A LAS FUENTES DE INFORMACIÓN DE UN GRUPO DE MANTENIMIENTO DE SOFTWARE POR MEDIO DE UN MAPA DE CONOCIMIENTO

PDF (Español (España))
  • Oscar M. Rodríguez Elias,
  • Ana I. Martínez García,
  • Jesús Favela Vara,
  • Aurora Vizcaíno Barceló,
  • Mario Piattini Velthuis
Oscar M. Rodríguez Elias
Universidad de Sonora
Bio
Ana I. Martínez García
CICESE
Bio
Jesús Favela Vara
CICESE
Bio
Aurora Vizcaíno Barceló
Universidad Castilla La Mancha
Bio
Mario Piattini Velthuis
Universidad Castilla La Mancha
Bio

Published 2011-04-14

How to Cite

Rodríguez Elias, O. M., Martínez García, A. I., Favela Vara, J., Vizcaíno Barceló, A., & Piattini Velthuis, M. (2011). FACILITANDO EL ACCESO A LAS FUENTES DE INFORMACIÓN DE UN GRUPO DE MANTENIMIENTO DE SOFTWARE POR MEDIO DE UN MAPA DE CONOCIMIENTO. Revista GTI, 4(10), 31–42. Retrieved from https://revistas.uis.edu.co/index.php/revistagti/article/view/1542

Abstract

RESUMEN

Entre los problemas que enfrentan las organizaciones de desarrollo de software, y en particular los grupos encargados del mantenimiento de software, se encuentran la pérdida o desaprovechamiento del conocimiento que existe en las distintas fuentes disponibles dentro de estos grupos. Esto se produce debido a que con frecuencia esas fuentes son desconocidas o difíciles de localizar. Los Mapas de Conocimiento (MC) son una técnica que puede ser de utilidad para abordar este problema, dado que pueden ser usados para describir las fuentes de conocimiento disponibles, el conocimiento que puede ser obtenido de las mismas, y cómo éstas pueden ser localizadas. Un aspecto importante para la creación de un MC, es definir qué conocimiento y qué fuentes deberán ser tomadas en cuenta. Con este fin, la identificación del flujo del conocimiento dentro de una organización puede ayudar a identificar qué conocimiento es el requerido en las actividades que sus miembros deben llevar a cabo, así como las fuentes donde ese conocimiento puede ser obtenido, con el fin de centrar nuestro interés en aquellas que realmente puedan ser de ayuda para los usuarios del MC. En este trabajo describimos el proceso que se llevó a cabo para la creación de unMCen el ámbito del mantenimiento de software, por medio de una metodología para identificar flujos de conocimiento con base en técnicas de modelado de procesos. El objetivo es plantear nuestra experiencia en la realización de este esfuerzo, con la finalidad de que algunas de estas ideas puedan ayudar a otras organizaciones de desarrollo de software en trabajos similares.

 

PALABRAS CLAVES

Mapa de conocimiento

Gestión de conocimiento

Identificación de flujos de conocimiento

Ingeniería de software

Mantenimiento de software

Mejoramiento de proceso software

 

ABSTRACT

Some of the problems in software development organizations, particularly in the groups in charge of software maintenance, are the scarce use of the knowledge that can be obtained from the sources available in the organization. This is because those sources are often unknown or difficult to locate. Knowledge maps can help to address this problem since these maps can be used to describe the knowledge sources available in the organization, the knowledge that can be obtained from them, and how or where those sources can be accessed. To create a knowledge map, an important factor is to define what knowledge and which sources should be considered. The identification of how knowledge flow through the organization can help to accomplish this, since it can help to identify the knowledge required by the members of the organization to carry on their activities, as well as the sources in which that knowledge can be obtained, in order to focus on those sources that may be really useful to the users of the knowledge map. This paper describes the process followed to create a knowledge map for a software maintenance group following a methodology to identify knowledge flows based on process modelling techniques. The main goal of this paper is to present our experience in the development of the map, expecting that some of these ideas could be useful to other software organizations that could engage similar works in the future.

 

KEYWORDS

Knowledge map

Knowledge management

Knowledge flows identification

Software engineering

Software maintenance

Software process improvement1

PDF (Español (España))

Downloads

Download data is not yet available.

References

  1. Abdullah, M. S., Benest, I., Evans, A., Kimble, C., "Knowledge Modelling Techniques for Developing Knowledge Management Systems", Proc. of the European Conference on Knowledge Management, Dublin, Ireland, 2002, pp. 15-25.
  2. Abran, A., Moore, J. W., Bourque, P., Dupuis, R., Tripp, L. L., "SWEBOK: Guide to the Software Engineering Body of Knowledge: 2004 Version". IEEE Computer Society, Los Alamitos, California, 2004.
  3. Alavi, M., Leidner, D. E., "Knowledge Management and Knowledge Management Systems: Conceptual Foundations and Research Issues", MIS Quarterly, vol. 25, 2001, pp. 107-136.
  4. Basili, V. R., Seaman, C. B., "The Experience Factory Organization", IEEE Software, vol. 19, 2002, pp. 30-31.
  5. Borghoff, U. M., Pareschi, R., "Information Technology for Knowledge Management", Journal of Universal Computer Science, vol. 3, 1997, pp. 835-842.
  6. Carroll, J. M., Rosson, M. B., "Getting Around the Task-Artifact Cycle: How to Make Claims and Design by Scenario", ACM Transactions on Information Systems, vol. 10, 1992, pp. 181-212.
  7. Curtis, B., Kellner, M. I., Over, J., "Process Modeling", Communications of the ACM, vol. 35, 1992, pp. 75-90.
  8. Davenport, T. H., Prusak, L., Working Knowledge: How Organizations Manage What they Know. Harvard Business School Press, Boston, Massachusetts, USA, 2000.
  9. Dias, M. G. B., Anquetil, N., Oliveira, K. M. d., "Organizing the Knowledge Used in Software Maintenance", Journal of Universal Computer Science, vol. 9, 2003, pp. 641- 658.
  10. Dingsøyr, T., Conradi, R., "A survey of case studies of the use of knowledge management in software engineering", International Journal of Software Engineering and Knowledge Engineering, vol. 12, 2002, pp. 391-414.
  11. Hansen, B. H., Kautz, K., "Knowledge Mapping: A Technique for Identifying Knowledge Flows in Software Organizations", Proc. of the European Conference on Software Process Improvement (EuroSPI 2004), Trondheim, Norway, 2004, pp. 126-137.
  12. ISO/IEC, "ISO/IEC FDIS 14764:1999, Software Engineering - Software Maintenance", Secretariat: Standard Council of Canada, Standard 1999.
  13. Kitchenham, B. A., Travassos, G. H., Mayrhauser, A., Niessink, F., Schneidewind, N. F., Singer, J., Takada, S., Vehvilainen, R., Yang, H., "Towards an Ontology of Software Maintenance", Journal of Software Maintenance: Research and Practice, vol. 11, 1999, pp. 365-389.
  14. Koskinen, J., Salminen, A., Paakki, J., "Hypertext support for the information needs of software maintainers", Journal of Software Maintenance and Evolution: Research and Practice, vol. 16, 2004, pp. 187-215.
  15. Lethbridge, T. C., Singer, J., Forward, A., "How Software Engineers Use Documentation: The State of the Practice", IEEE Software, vol. 20, 2003, pp. 35- 39.
  16. Lin, F.-r., Hsueh, C.-m., "Knowledge map creation and maintenance for virtual communities of practice", Information Processing & Management, vol. 42, 2006, pp. 551-568.
  17. Lindvall, M., Rus, I., "Knowledge Management for Software Organizations", In Managing Software Engineering Knowledge, Aurum, A., Jeffery, R., Wohlin, C., and Handzic, M., Eds. Springer, Berlin, 2003, pp. 73-94.
  18. Monk, A., Howard, S., "The Rich Picture: A Tool for Reasoning about Work Context", Interactions, vol. 5, 1998, pp. 21-30.
  19. Nonaka, I., Takeuchi, H., The Knowledge-Creation Company: How Japanese Companies Create the Dynamics of Innovation. Oxford University Press, 1995.
  20. Oliveira, K. M., Anquetil, N., M.G, D., Ramal, M., Meneses, R., "Knowledge for Software Maintenance." Proc. of the Fifteenth International Conference on Software Engineering and Knowledge Engineering (SEKE'03), San Francisco, CA, 2003, pp. 61-68.
  21. Polo, M., Piattini, M., Ruiz, F., Calero, C., "MANTEMA: A Complete Rigorous Methodology for Supporting Maintenance based on the ISO/IEC 12207 Standard", Proc. of the Third Euromicro Conference on Software Maintenance and Reengineering (CSMR'99), Amsterdam (The Netherlands), 1999, pp. 178-181.
  22. Polo, M., Piattini, M., Ruiz, F., Calero, C., "Roles in the Maintenance Process", Software Engineering Notes, Special Interest Group on Software Engineering, ACM, vol. 24, Nº4, 1999, pp. 84-86.
  23. Robillard, P. N., "The Role of Knowledge in Software Development", Communications of the ACM, vol. 42, 1999, pp. 87-92.
  24. Rodríguez, O. M., Martínez, A. I., Favela, J., Vizcaíno, A., Piattini, M., "Understanding and Supporting Knowledge Flows in a Community of Software Developers", Proc. of the 10th International Workshop on Groupware (CRIWG'2004), San Carlos, Costa Rica, 2004, pp. 52-66.
  25. Rodríguez-Elias, O. M., Martínez-García, A. I., Vizcaíno, A., Favela, J., Piattini, M., "Identifying Knowledge Flows in Communities of Practice", In Encyclopedia of Communities of Practice in Information and Knowledge Management, Coakes, E. and Clarke, S. A., Eds. Idea Group Inc., Hershey, PA, USA, 2005, pp. 210-217.
  26. Ruiz, F., Vizcaíno, A., Piattini, M., García, F., "An Ontology for the Management of Software Maintenance Projects", International Journal of Software Engineering and Knowledge Engineering, vol. 14, 2004, pp. 323-349.
  27. Rus, I., Lindvall, M., Sinha, S. S., "Knowledge Management in Software Engineering: A State of the Art Report", Data & Analysis Center for Software: ITT Industries, Rome, NY 29 November 2001.
  28. Seaman, C., "The Information Gathering Strategies of Software Maintainers", Proc. of the International Conference on Software Maintenance (ICSM'2002), 2002, pp. 141-149.
  29. Uschold, M., Gruninger, M., "Ontologies: Principles, methods, and applications", The Knowledge Engineering Review, vol. 11, 1996, pp. 93-136.
  30. Valente, A., Housel, T., "A Framework to Analyze and Compare Knowledge Management Tools", Proc. of the Knowledge-Based Intelligent Information Engineering and Allied Technologies (KES'2002), Crema, Italy, 2002, pp. 291- 295.
  31. Walz, D. B., Elam, J. J., Curtis, B., "Inside a Software Design Team: Knowledge Acquisition, Sharing, and Integration", Communications of the ACM, vol. 36, 1993, pp. 63-77.
  32. Especificación del Metamodelo para ingeniería de procesos de software: tomado de Internet: SPEM (http://www.omg.org).

Most read articles by the same author(s)