Publicado
ADKT: a support tool for reducing architectural knowledge evaporation in software projects
ADKT: una herramienta para la reducción de la evaporación del conocimiento arquitectónico en proyectos software
DOI:
https://doi.org/10.15446/dyna.v92n239.119675Palabras clave:
architectural design decisions, software architecture, documentation and traceability, software maintenance, architectural knowledge evaporation (en)decisiones de diseño arquitectónico, arquitectura de software, documentación y trazabilidad, mantenimiento de software, evaporación del conocimiento arquitectónico. (es)
Descargas
Defining software architecture is a complex task that demands technical expertise and business knowledge. Design decisions drive architectural structures throughout development and maintenance. However, this knowledge often dissipates over time, a phenomenon known as architectural knowledge evaporation, leading to increased costs and maintenance difficulties. This paper presents ADKT, a support tool designed to mitigate architectural knowledge evaporation by enabling the documentation and traceability of design decisions. ADKT was evaluated through a case study involving software engineers of different expertise levels. The evaluation assessed the tool’s ease of use, perceived usefulness, and effectiveness in reducing knowledge evaporation. Results indicate that participants found ADKT easy to use and valuable for preserving architectural knowledge. Nonetheless, challenges remain regarding engineers’ commitment to consistently documenting decisions and the need for a designated person to oversee this process. These findings highlight the importance of developing advanced tools and fostering a culture of documentation within development teams.
Definir la arquitectura de software es una tarea compleja que exige experiencia técnica y conocimiento del negocio. Las decisiones de diseño impulsan las estructuras arquitectónicas durante el desarrollo y mantenimiento. Sin embargo, este conocimiento a menudo se disipa con el tiempo, un fenómeno conocido como evaporación del conocimiento arquitectónico, lo que genera mayores costos y dificultades de mantenimiento. Este artículo presenta ADKT, una herramienta de apoyo diseñada para mitigar la evaporación del conocimiento arquitectónico al permitir la documentación y trazabilidad de decisiones de diseño. ADKT fue evaluado mediante un estudio de caso con ingenieros de software de distintos niveles de experiencia. La evaluación analizó la facilidad de uso, utilidad percibida y efectividad de la herramienta para reducir la evaporación del conocimiento. Los resultados indican que los participantes encontraron ADKT fácil de usar y valioso para preservar el conocimiento arquitectónico. No obstante, persisten desafíos en el compromiso de los ingenieros para documentar decisiones de manera constante y la necesidad de una persona encargada de supervisar este proceso. Estos hallazgos destacan la importancia de desarrollar herramientas avanzadas y fomentar una cultura de documentación en los equipos de desarrollo.
Referencias
[1] Bass, L., Clements, P., Kazman, R., Software Architecture in Practice. Second. Addison Wesley; 2003.
[2] Harrison, N., and Avgeriou, P., How do architecture patterns and tactics interact? a model and annotation. Journal of Systems and Software, 83(10), pp. 1735-1758, 2010. DOI: https://doi.org/10.1016/j.jss.2010.04.067
[3] Jansen, A., and Bosch, J., Software architecture as a set of architectural design decisions. 5th Working IEEE/IFIP Conference on Software Architecture (WICSA’05), 2005, pp. 109-120. DOI: https://doi.org/10.1109/WICSA.2005.61
[4] van-der-Ven, J.S., Jansen, A.G.J, and Bosch, J., Design decisions: the bridge between rationale and architecture. In: Dutoit, A.H., McCall, R., Mistrík, I., and Paech, B., eds. Rationale Management in Software Engineering. Springer Berlin Heidelberg, 2006, pp. 329-348. DOI: https://doi.org/10.1007/978-3-540-30998-7_16
[5] Borrego, G., Morán, A., Palacio, R., Vizcaíno, A., and García, F., Towards a reduction in architectural knowledge vaporization during agile global software development. Inf. Softw Technol, 112(6), pp. 68-82, 2019. DOI: https://doi.org/10.1016/j.infsof.2019.04.008
[6] Capilla, R., Jansen, A., Tang, A., Avgeriou, P., and Babar, M., 10 years of software architecture knowledge management: practice and future. Journal of Systems and Software. (116), pp. 191-205, 2016. DOI: https://doi.org/10.1016/j.jss.2015.08.054
[7] Hadar, I., Sherman, S., Hadar, E., and Harrison, J., Less is more: architecture documentation for agile development, in: 6th International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE, Proceedings, 2013, pp. 121-124.
[8] Hyun, S., and Hurtado, J., Traceability of architectural design decisions and software artifacts: a Systematic Mapping Study. Foundations of Computing and Decision Sciences, 48(4), pp. 401-423, 2023. DOI: https://doi.org/10.2478/fcds-2023-0018
[9] Tofan, D., Understanding and supporting software architectural decisions: for reducing architectural knowledge vaporization. University of Groningen, 2015.
[10] Dutoit, A.H, McCall, R., Mistrík, I., and Paech, B., Rationale management in software engineering: concepts and techniques. In: Dutoit, A.H., McCall, R., Mistrík, I., Paech, B., eds., Rationale Management in Software Engineering. Springer Berlin Heidelberg, 2006, pp. 1-48. DOI: https://doi.org/10.1007/978-3-540-30998-7_1
[11] Bass, L., Clements, P., Nord, R., and Stafford, J., Capturing and using rationale for a software architecture. In: Dutoit, A.H., McCall, R., Mistrík, I., Paech, B., eds., Rationale Management in Software Engineering. Springer Berlin Heidelberg, 2006, pp. 255-272. DOI: https://doi.org/10.1007/978-3-540-30998-7_12
[12] Kamalabalan, et al., Tool support for traceability of software artefacts. In: Moratuwa Engineering Research Conference (MERCon), 2015, pp. 318-323. DOI: https://doi.org/10.1109/MERCon.2015.7112366
[13] Petersen, K., Vakkalanka, S., and Kuzniarz, L., Guidelines for conducting systematic mapping studies in software engineering: An update. Inf Softw Technol, 64, pp. 1-18, 2015. DOI: https://doi.org/10.1016/j.infsof.2015.03.007
[14] Gilson, F., Annand, S., and Steel, J., Recording software design decisions on the fly. CEUR Workshop Proc., (2799), 2020, pp. 53-66.
[15] Meza-Soria, A., and Van-Der-Hoek, A., Collecting design knowledge through voice notes. Proceedings IEEE/ACM 12th International Workshop on Cooperative and Human Aspects of Software Engineering, CHASE, 2019, pp. 33-36. DOI: https://doi.org/10.1109/CHASE.2019.00015
[16] Soria, A., KNOCAP: capturing and delivering important design bits in Whiteboard design meetings. Proceedings ACM/IEEE 42nd International Conference on Software Engineering: Companion, ICSE-Companion, 2020, pp. 194-197. DOI: https://doi.org/10.1145/3377812.3381397
[17] Souali, K., Rahmaoui, O., and Ouzzif, M., An overview of traceability: definitions and techniques. Colloquium in Information Science and Technology, CIST., 2016, pp. 789-793. DOI: https://doi.org/10.1109/CIST.2016.7804995
[18] Hyun, S., ADKT Documentation web site. Preprint posted [online], 2025. Available at: https://zahydo.github.io/adkt-docs
[19] ISO/IEC. ISO/IEC 25010, Systems and Software Engineering-Systems and Software quality requirements and evaluation (SQuaRE)-System and Software Quality Models. ISO/IEC; 2010.
[20] Runeson, P., and Höst, M., Guidelines for conducting and reporting case study research in software engineering. Empir Softw Eng., 14, pp. 131-164, 2009. DOI: https://doi.org/10.1007/s10664-008-9102-8
[21] Quercus Software Engineering Group research group. Preprint posted [online], 2025. Available at: https://quercusseg.unex.es/
[22] Hyun-Dorado S., Materiales para la evaluación de ADKT a través de un estudio de caso. Zenodo. Preprint posted, Art. 9845, 2024. DOI: https://doi.org/10.5281/zenodo.13209845
[23] Davis, F., Bagozzi R., and Warshaw P., User acceptance of computer technology: a comparison of two theoretical models. Management Science, 35(8), pp. 982-1003, 1989.
[24] Wang, C., Ahmad SF, Bani Ahmad Ayassrah AYA, et al. An empirical evaluation of technology acceptance model for Artificial Intelligence in E-commerce. Heliyon, 9(8), e.18349, 2023. DOI: https://doi.org/10.1016/j.heliyon.2023.e18349
Cómo citar
IEEE
ACM
ACS
APA
ABNT
Chicago
Harvard
MLA
Turabian
Vancouver
Descargar cita
Licencia
Derechos de autor 2025 DYNA

Esta obra está bajo una licencia internacional Creative Commons Atribución-NoComercial-SinDerivadas 4.0.
El autor o autores de un artículo aceptado para publicación en cualquiera de las revistas editadas por la facultad de Minas cederán la totalidad de los derechos patrimoniales a la Universidad Nacional de Colombia de manera gratuita, dentro de los cuáles se incluyen: el derecho a editar, publicar, reproducir y distribuir tanto en medios impresos como digitales, además de incluir en artículo en índices internacionales y/o bases de datos, de igual manera, se faculta a la editorial para utilizar las imágenes, tablas y/o cualquier material gráfico presentado en el artículo para el diseño de carátulas o posters de la misma revista.




