Papers by Olga Lucero Vega Márquez
Metodologías ágiles de desarrollo de Software
chie.uniandes.edu.co
2019 IEEE/ACM 41st International Conference on Software Engineering (ICSE), 2019
Software documentation provides developers and users with a description of what a software system... more Software documentation provides developers and users with a description of what a software system does, how it operates, and how it should be used. For example, technical documentation (e.g., an API reference guide) aids developers during evolution/maintenance activities, while a user manual explains how users are to interact with a system. Despite its intrinsic value, the creation and the maintenance of documentation is often neglected, negatively impacting its quality and usefulness, ultimately leading to a generally unfavorable take on documentation. Previous studies investigating documentation issues have been based on surveying developers, which naturally leads to a somewhat biased view of problems affecting documentation. We present a large scale empirical study, where we mined, analyzed, and categorized 878 documentation-related artifacts stemming from four different sources, namely mailing lists, Stack Overflow discussions, issue repositories, and pull requests. The result is a detailed taxonomy of documentation issues from which we infer a series of actionable proposals both for researchers and practitioners.
Mapping Study on Traceability Between BPMN Models and Source Code
International Journal on Advanced Science, Engineering and Information Technology
Understanding businesses and how they work can help software engineers build systems that really ... more Understanding businesses and how they work can help software engineers build systems that really meet the corresponding business goals. For instance, methods such as the Rational Unified Process (RUP) include activities to model a business before eliciting requirements. However, during our software development practice in academic and ”real-life” projects, we found problems using these artefacts with stakeholders. Here we present our experience on integrating BPMN (Business Process Modeling and Notation) diagrams with RUP, aiming to improve the elicitation of software requirements. These diagrams appeared to be easier to understand by stakeholders. The current paper discusses the challenges we faced in using RUP and the way in which we integrate conceptual maps and BPMN into the process. In addition, we illustrate the changes using models that reflect real project implementations realized by using this approach.
Empirical Studies on the Development of Executable Business Processes, 2019
The Business Process Model and Notation (BPMN) has become the de facto standard for process model... more The Business Process Model and Notation (BPMN) has become the de facto standard for process modeling. Currently, BPMN models can be (a) analyzed or simulated using specialized tools, (b) executed using business process management systems (BPMSs), or (c) used for requirements elicitation. Although there are many studies comparing BPMN to other modeling techniques for analyzing and executing processes, there are few showing the suitability of BPMN models as a source for requirements comprehension in projects where process-aware software is built without using BPMSs. This chapter presents a study aimed at comparing the comprehension of software requirements regarding a business process using either BPMN or traditional techniques, such as use cases. In our study, we analyzed responses of 120 undergraduate and graduate students regarding the requirements comprehension achieved when using only BPMN models, only use cases, or both. The results do not show significant impact of the artifact...
Software documentation provides developers and users with a description of what a software system... more Software documentation provides developers and users with a description of what a software system does, how it operates, and how it should be used. For example, technical documentation (e.g., an API reference guide) aids developers during evolution/maintenance activities, while a user manual explains how users are to interact with a system. Despite its intrinsic value, the creation and the maintenance of documentation is often neglected, negatively impacting its quality and usefulness, ultimately leading to a generally unfavorable take on documentation. Previous studies investigating documentation issues have been based on surveying developers, which naturally leads to a somewhat biased view of problems affecting documentation. We present a large scale empirical study, where we mined, analyzed, and categorized 878 documentation-related artifacts stemming from four different sources, namely mailing lists, Stack Overflow discussions, issue repositories, and pull requests. The result is a detailed taxonomy of documentation issues from which we infer a series of actionable proposals both for researchers and practitioners.
Las metodologías ágiles para el desarrollo de software han sido adoptadas cada vez más por las em... more Las metodologías ágiles para el desarrollo de software han sido adoptadas cada vez más por las empresas, debido a que han visto en ellas una manera de desarrollar software de manera rápida y efectiva. El mundo del software actualmente se caracteriza por estar en permanentes cambios, debido a que el mercado así lo demanda, por lo que las metodologías agiles reciben estos cambios de manera rápida sin verse afectado la evolución del proyecto. En esta revisión se podrá encontrar todo lo relacionado con algunas de la metodologías agiles para el desarrollo de software más comunes (Scrum, Xp, DSDM, Crystal Clear, FDD), se dará a breve detalle del ciclo de vida de la metodología, los roles y responsabilidades que se manejan, los principales valores que se tienen, los artefactos que se manejan para el monitoreo en el desarrollo del software, y las reuniones que se llevan a cabo durante la ejecución del proyecto.
Uploads
Papers by Olga Lucero Vega Márquez