Knowledge Acquisition and Dissemination Strategies to Support Software Development with RUP

• Rodrigo Fernandes de Oliveira UFRJ
• Ana Regina C. da Rocha UFRJ
• Guilherme Horta Travassos UFRJ

DOI: https://doi.org/10.5753/sbqs.2003.15691

Abstract

Enterprises have demonstrated along the years their interest in object-oriented based development. As a consequence, some of them have adopted the RUP as the basis for their software development process. RUP represents a process framework. Therefore, several variables can affect its adaptation, execution and management when applied to a project. At this context, to have knowledge about these variables value and be able to identify their impact on the project is basic for continuous process improvement. By defining a strategy to acquire process knowledge, such as project’s strong and weak points, we intend to deal more objectively with most deficient processes (weak points) and stimulate strong points continue to be applied in future projects. A case study applying such knowledge acquisition strategy on a RUP based project is discussed. Moreover, a strategy for knowledge dissemination is also described. This dissemination strategy is based on the construction of action plans elaborated according the team needs.

Keywords: Knowledge Acquisition and Dissemination, Process Improvement, RUP

References

Kroll, P., 2001, “The RUP: An Industry-wide Platform for Best Practices”, Online: http://www.therationaledge.com/content/dec_01/f_TheRUP_pk.html.

Jacobson, I., Booch, G., Rumbaugh, J., 1998, The Unified Software Development Process, Reading, Massachusetts, Addison-Wesley.

Davenport, T.H. e Prusak, L., 1998, Working Knowledge: How Organizations Manage What They Know, Harvard College Business School Press, Boston.

Nonaka, I., Takeuchi, H., 1995, The Knowledge Creation Company: How Japanese Companies Create the Dynamics of Innovation, Oxford University Press, New York.

ISO/IEC 12207, 2001, Information Technology - Amendment to ISO/IEC 12207, Montreal: ISO/IEC JTC1 SC7.

Rus, I., Lindvall, M., 2002, “Knowledge Management in Software Engineering”, IEEE Software, Maio/Junho, pp. 26-38.

Basili, V.R., Caldieira, G., Rombach, D., 1994, “The Experience Factory”, Encyclopedia of Software Engineering, Volume 1, pp. 469-476.

Birk, A., Dingsøyr, T. Stalhane, T., 2002, “Postmortem: Never Leave a Project without It”, IEEE Software, Maio/Junho, pp. 43-45.

Collier, B., DeMarco, T., Fearey, P., “A Defined Process For Project Post Mortem Review”, IEEE Software, Júlio/Agosto, pp. 65-72.

Nolan, A. J., 1999,“Learning from Success”, IEEE Software, Janeiro/Fevereiro, pp. 97-105.

Senge, P. M., The Fifth Discipline: The Art and Practice of the Learning Organization, New York: Doubleday.

Holz, H., Könnecker, A., Maurer, F., 2001, “Task-Specific Knowledge Management in a Process-Centred SEE”, LSO 2001, LNCS 2176, pp. 163-177.

Apostolou, D., Mentzas, G., 1998, “Managing Corporate Knowledge: A Comparative Analysis of Experiences in Consulting Firms”, Second International Conference on Practical Aspects of Knowledge Management, Basel, Suíça.

Dingsøyr, T., Moe, N. B., Nytrø, Ø., 2001, “Augmenting Experience Reports with Lightweight Postmortem Reviews”, 3rd International Conference Product Focused Software

Process Improvement (Profes 01), Lecture Notes in Computer Science, vol. 2188, Springer- Verlag, Berlin, pp. 167-181.

Beck, K., 2000, Extreme Programming Explained, Addison-Wesley.