Agile prototyping strategy for building shared understanding in requirements engineering
Article Sidebar
Main Article Content
Abstract
The strategy proposed in this paper addresses a critical challenge in requirements engineering: building a shared understanding among all stakeholders in software development. Shared understanding refers to the ability of people in a team to have a common and consistent understanding of the requirements that the system will have, which is essential for effective collaboration. The construction of this strategy was done using Situational Method Engineering (SME), which allowed to obtain, at the end of the realization of each of its activities, a set of phases, with their respective activities and tasks, which seek the construction of shared understanding through the realization of agile prototyping. The use of prototypes allows to provide a visual and tangible representation of the system requirements, which facilitates communication and feedback among stakeholders. In this sense, this article shows the use of SME for the final construction of the strategy, which consists of several phases, including planning, requirements identification and analysis, non-functional prototyping, requirements management, functional prototyping, and socialization. These phases are designed to strengthen communication, promote collaboration, and ensure a solid shared understanding throughout the software development process.
Downloads
Article Details
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
All the texts published in this magazine are distributed under a Creative Commons License «Attribution-Non-Commercial-Share the same»
References
N. N. B. Abdullah, S. Honiden, H. Sharp, B. Nuseibeh, y D. Notkin, “Communication patterns of agile requirements engineering,” Proc. 1st Agil. Requir. Eng. Work. AREW’11 - Conjunction with ECOOP’11, pp. 1–4, 2011, doi: 10.1145/2068783.2068784.
E. Bittner y J. Leimeister, “Creating shared understanding in heterogeneous work groups: Why it matters and how to achieve it,” J. Manag. Inf. Syst., vol. 31, no. 1, pp. 111–144, 2014, doi: 10.2753/MIS0742-1222310106.
M. Hummel, C. Rosenkranz, y R. Holten, “The role of shared understanding in distributed scrum development: An empirical analysis,” 24th Eur. Conf. Inf. Syst. ECIS 2016, 2016.
M. Arias Chaves, “La ingeniería de requerimientos y su importancia en el desarrollo de proyectos de software Michael,” Rev. las Sedes Reg., vol. VI, no. 2215–2458, pp. 1–13, 2005, [Online]. Available: https://www.redalyc.org/articulo.oa?id=66612870011
D. Carrizo y J. Rojas, “Methodologies, techniques and tools in requirements engineering: A systematic mapping,” Ingeniare, vol. 26, no. 3, pp. 473–485, 2018, doi: 10.4067/S0718-33052018000300473.
N. Fiquitiva Segura y M. A. López Ruiz, “PROTOTIPO DE APLICATIVO PARA ESPECIFICAR REQUERIMIENTOS DE SOFTWARE,” vol. 13, 2015.
M. Käpyaho y M. Kauppinen, “Agile requirements engineering with prototyping: A case study,” 2015 IEEE 23rd Int. Requir. Eng. Conf. RE 2015 - Proc., pp. 334–343, 2015, doi: 10.1109/RE.2015.7320450.
K. Elghariani y N. Kama, “Review on Agile requirements engineering challenges,” 2016 3rd Int. Conf. Comput. Inf. Sci. ICCOINS 2016 - Proc., pp. 507–512, 2016, doi: 10.1109/ICCOINS.2016.7783267.
L. Zamudio, A. A. B, y C. Tripp, “in Agile Software Development Methods,” Comput. Sci. Its Appl., vol. 2, pp. 683–698, 2017, doi: 10.1007/978-3-319-62404-4.
B. Henderson-Sellers, J. Ralyté, P. J. Ågerfalk, y M. Rossi, Situational method engineering. 2014. doi: 10.1007/978-3-642-41467-1.
N. Devadiga, “Tailoring architecture centric design method with rapid prototyping,” in Proceedings of the 2nd International Conference on Communication and Electronics Systems, ICCES 2017, Mar. 2018, vol. 2018-Janua, pp. 924–930. doi: 10.1109/CESYS.2017.8321218.
R. F. Ciriello, A. Richter, y G. Schwabe, “When prototyping meets storytelling: Practices and malpractices in innovating software firms,” Proc. - 2017 IEEE/ACM 39th Int. Conf. Softw. Eng. Softw. Eng. Pract. Track, ICSE-SEIP 2017, pp. 163–172, 2017, doi: 10.1109/ICSE-SEIP.2017.24.
A. Hoffmann, E. Alice, C. Bittner, y J. M. Leimeister, “Emergence of Mutual and Shared Understanding in the System Development Process . In?: Requirements Engineering?: Foundation for Software Quality , Lecture The Emergence of Mutual and Shared Understanding in the System Development Process,” no. 2013, pp. 174–189.
J. A. J. Builes, H. J. Hernández-Reinoza, y C. Villota-Ibarra, “Metodología lúdica para la enseñanza de la ingeniería de requisitos basada en esquemas preconceptuales,” Rev. EIA, vol. 18, no. 35, 2021, doi: 10.24050/reia.v18i35.1394.
E. Maida y J. Pacienzia, “Metodologías de desarrollo de software,” Bibl. Digit. la Univ. Católica Argentina, p. 117, 2018, [Online]. Available: http://bibliotecadigital.uca.edu.ar/repositorio/tesis/metodologias-desarrollo-software.pdf
J. M. Cadavid, A. N., Martínez, J. D. F., & Vélez, “Revisión de metodologías ágiles para el desarrollo de software.,” Prospectiva, vol. 11, no. 2, pp. 30–39, 2013, [Online]. Available: http://www.redalyc.org/articulo.oa?id=496250736004%0ACómo
E. Pineda Ballesteros, F. R. Tellez Acuña, y J. Medina Cruz, “Requerimientos de software: prototipado, software heredado y análisis de documentos,” Ing. y Desarro., vol. 37, no. 02, pp. 327–345, 2019, doi: 10.14482/inde.37.2.1053.
S. G. Rivadeneira Molina, “Metodologías ágiles enfocadas al modelado de requerimientos,” Inf. Científicos Técnicos - UNPA, vol. 5, no. 1, pp. 1–29, 2014, doi: 10.22305/ict-unpa.v5i1.66.
S. A. Mosquera Moreno, “Requirements Engineering in Agile Development Methods Engenharia de Requisitos , em Métodos Ágeis de Desenvolvimento La Ingeniería de Requisitos en los Métodos de Desarrollo Agiles,” La Ing. Requisitos En Los Métodos Desarro. Agil. Resum., no. October, 2016, doi: 10.13140/RG.2.1.3303.7687.
S. Ghobadi y L. Mathiassen, “Perceived barriers to effective knowledge sharing in agile software teams,” Inf. Syst. J., vol. 26, no. 2, pp. 95–125, 2016, doi: 10.1111/isj.12053.
X. Yu y S. Petter, “Understanding agile software development practices using shared mental models theory,” Inf. Softw. Technol., vol. 56, no. 8, pp. 911–921, 2014, doi: 10.1016/j.infsof.2014.02.010.
M. Corvera Charaf, C. Rosenkranz, y R. Holten, “The emergence of shared understanding: Applying functional pragmatics to study the requirements development process,” Inf. Syst. J., vol. 23, no. 2, pp. 115–135, 2013, doi: 10.1111/j.1365-2575.2012.00408.x.
A. Nakakawa, P. Van Bommel, E. H. A. Proper, y H. J. B. F. Mulder, “A situational method for creating shared understanding on requirements for an enterprise architecture,” Int. J. Coop. Inf. Syst., vol. 27, no. 4, 2018, doi: 10.1142/S0218843018500107.
N. W. Varas Cortés, “Una técnica basada en Prototipado rápido para favorecer el entendimiento compartido entre el cliente y el desarrollador,” 2021, [Online]. Available: https://repositorio.uchile.cl/handle/2250/181671?show=full
B. Kitchenham y P. Brereton, “A systematic review of systematic review process research in software engineering,” Inf. Softw. Technol., vol. 55, no. 12, pp. 2049–2075, 2013, doi: 10.1016/j.infsof.2013.07.010.
M. Glinz y S. A. Fricker, “On shared understanding in software engineering: an essay,” Comput. Sci. - Res. Dev., vol. 30, no. 3–4, pp. 363–376, 2015, doi: 10.1007/s00450-014-0256-x.
J. B. Windeler, L. M. Maruping, L. P. Robert, y C. K. Riemenschneider, “E-profiles, conflict, and shared understanding in distributed teams,” J. Assoc. Inf. Syst., vol. 16, no. 7, pp. 608–645, 2015, doi: 10.17705/1jais.00401.
J. L. Pérez-Medina y J. Vanderdonckt, “Sketching by Cross-Surface Collaboration,” Adv. Intell. Syst. Comput., vol. 918, pp. 386–397, 2019, doi: 10.1007/978-3-030-11890-7_38.
C. Werner, Z. S. Li, N. Ernst, y D. Damian, “The Lack of Shared Understanding of Non-Functional Requirements in Continuous Software Engineering: Accidental or Essential?,” Proc. IEEE Int. Conf. Requir. Eng., vol. 2020-Augus, pp. 90–101, 2020, doi: 10.1109/RE48521.2020.00021.
K. A. Mohamed, M. A. Ellatif, y M. S. Farhan, “Using ontology-based concept maps for requirements engineering: A case study,” ICENCO 2017 - 13th Int. Comput. Eng. Conf. Boundless Smart Soc., vol. 2018-Janua, pp. 366–371, 2018, doi: 10.1109/ICENCO.2017.8289816.
Y. Liu, S. van Nederveen, y M. Hertogh, “Understanding effects of BIM on collaborative design and constructionAn empirical study in China,” Int. J. Proj. Manag., vol. 35, no. 4, pp. 686–698, 2017, doi: 10.1016/j.ijproman.2016.06.007.
N. Kunicina, A. Zabasta, A. Patlins, I. Bilic, y J. Peksa, “Prototyping process in education and science,” 2020 IEEE 61st Annu. Int. Sci. Conf. Power Electr. Eng. Riga Tech. Univ. RTUCON 2020 - Proc., 2020, doi: 10.1109/RTUCON51174.2020.9316550.
Porter Michael E., “¿Qué es la estrategia?,” Harv. Bus. Rev., no. March, pp. 100–117, 2008.
A. López Gil, “Estudio comparativo de metodologías tradicionales y ágiles para proyectos de Desarrollo de Software,” Univ. Valladolid, p. 139, 2018, [Online]. Available: https://uvadoc.uva.es/handle/10324/32875%0Ahttps://uvadoc.uva.es/handle/10324/32875%0Ahttps://agileexperience.es/wp-content/uploads/2020/06/TFG-I-1015.pdf%0Ahttp://uvadoc.uva.es/handle/10324/32875