Requirements Engineering in Agile and Traditional Environments: A Comprehensive Approach to User-Centered Software Development
DOI:
https://doi.org/10.70577/ASCE/944.969/2025Keywords:
Requirements engineering, software development, elicitation, validation, requirements management, ISO standards, agility.Abstract
In the context of accelerated digital transformation, organizations face challenges in developing software that effectively responds to user needs. Requirements engineering, while critical to the success of software projects, often presents issues such as ambiguities, contradictions, and lack of traceability in requirements, which can lead to critical errors during the development cycle. This article aims to analyze requirements engineering in agile and traditional environments, with a focus on improving the quality, traceability and usefulness of systems through proper requirements management. To this end, a mixed methodology was used, combining documentary research and the analysis of practical cases in educational and health institutions in Ecuador. The methods used include semi-structured interviews, direct observation, questionnaires and prototypes, following the international standards ISO/IEC/IEEE 29148:2018 and BABOK v3. The results obtained show that the rigorous application of elicitation and validation techniques, together with the combination of agile and traditional approaches, improves the accuracy and relevance of requirements. In addition, it was found that the active participation of stakeholders and the use of digital tools favor a better alignment of projects with the real needs of users. Finally, it is concluded that requirements engineering should be integrated as a transversal competence in the training of software engineers, prioritizing an approach that combines technical, methodologicaland ethical aspects to guarantee the success of digital transformation.
Downloads
References
Administración de Requerimientos. (2014, agosto 26). Clasificación y tipos de requerimientos. WordPress. https://administracionderequerimientos.wordpress.com/2014/08/26/clasificacion-y-tipos-de-requerimientos/
Arangurí, M., & Bravo, J. (2021). Metodología integral de casos de prueba sustentado en un modelo de verificación de requisitos. eLibro. https://elibro.net/es/lc/espoch/titulos/228963
Bejarano, M., & Baquero, L. (2020). Ciclo de vida de desarrollo ágil de software seguro. eLibro. https://elibro.net/es/lc/espoch/titulos/197008 DOI: https://doi.org/10.2307/j.ctv1vbd1rf
Echeverri, J., Aristizábal, M., & González, L. (2013). Reflexiones sobre ingeniería de requisitos y pruebas de software. eLibro. https://elibro.net/es/lc/espoch/titulos/68913
Jiménez, C. (2021). UML: Arquitectura de aplicaciones en Java, C++ y Python. eLibro. https://elibro.net/es/lc/espoch/titulos/2227203
IEEE. (1998). IEEE Recommended Practice for Software Requirements Specifications (Std 830-1998). Institute of Electrical and Electronics Engineers.
ISO/IEC/IEEE. (2018). Systems and software engineering — Life cycle processes — Requirements engineering (ISO/IEC/IEEE 29148:2018). International Organization for Standardization.
International Institute of Business Analysis. (2015). A guide to the business analysis body of knowledge (BABOK guide) (Version 3). IIBA.
ISO/IEC. (2011). ISO/IEC 25010:2011. Systems and software engineering — Systems and software quality requirements and evaluation (SQuaRE) — System and software quality models. International Organization for Standardization.
PMI Levante. (s.f.). Gestión de los interesados. https://pmi-levante.org/gestion-interesados/
Downloads
Published
How to Cite
Issue
Section
License
Copyright (c) 2025 Cristian Geovanny Merino Sánchez

This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.