Papers by Alejandro Oliveros
Software processes and practices have a leading role in software development and in the last few ... more Software processes and practices have a leading role in software development and in the last few decades a wide variety of processes and practices have emerged to face the challenges arising in the software industry. The success of process and practice adoption initiatives depends at least partially on the experience and satisfaction of the people who use them, thus making usability an interesting process quality attribute. This paper describes the inter-rater reliability evaluations performed on the UMP to assess consistency among metric values produced by different evaluators. It presents two inter-rater reliability assessment studies, the Scrum study and the TDD-BDD study. The paper presents four inter-rater reliability statistics for the process and practices under study, a comparative analysis of their strengths and weaknesses, and an analysis of the study results and their interpretation. The results show varying reliability results among the different UMP metrics, which seem ...
Lecture notes in information systems and organisation, 2022
There is currently a trend that highlights the interest in the use of Design Thinking techniques ... more There is currently a trend that highlights the interest in the use of Design Thinking techniques for the elicitation of requirements. The evidence concerning the effectiveness of these techniques is, however, still scarce, which has consequently led us to carry out a quasi-experiment in order to evaluate the effectiveness of one of the most frequently used DT techniques: Empathy Maps. Empathy Maps were employed by students enrolled on a Bachelor's degree in Computer Engineering at the Universitat Politècnica de València in Spain in order to understand their influence on the effectiveness of Brainstorming sessions, which was measured in terms of the quantity of requirements attained. The students perceived a slightly positive influence as regards the use of the Empathy Maps as part of a requirements elicitation, despite not finding statistically positive results in favour of Empathy Maps. We obtained several insights that may be useful for practitioners, researchers and lecturers interested in using this type of techniques to improve the requirements elicitation practices currently employed to develop information systems, although this preliminary result is not conclusive and should be corroborated in further studies.
There is a growing interest in the use of Design Thinking (DT) to enrich requirements elicitation... more There is a growing interest in the use of Design Thinking (DT) to enrich requirements elicitation processes. This fact motivated us to explore the use of user-centered and empathy-oriented techniques taken from the DT process, in combination with the Brainstorming technique, usually used alone, for requirements elicitation. Specifically, we carried out a quasi-experiment to compare the Effectiveness of Brainstorming sessions in terms of the number of ideas of requirements generated, and the Identified Stakeholders, complementing the Brainstorming sessions with two of the most widely used DT techniques: Empathy Maps and Personas. Therefore, we consider three treatments: Personas + Brainstorming, Empathy Maps + Brainstorming, and Brainstorming alone (control group). The quasi-experiment was carried out with 74 students enrolled in the Bachelor of Computer Engineering course at the Universitat Politècnica de València in 2021. The results reveal a statistically significant effect on Identified Stakeholders when using Empathy Maps. Descriptive analysis also shows an increase in Identified Stakeholders when using Personas, and in the Effectiveness of Brainstorming sessions when used together with Empathy Maps or Personas. There is also a variation in the type of ideas, with the number of functional ideas being higher, and that of non-functional ideas being lower when Empathy Maps are used. These results seem to indicate that Brainstorming sessions are improved when complemented with Empathy Maps or personas techniques. However, we still do not have enough evidence to recommend either Personas or Empathy Maps. Therefore, further experimentations will be needed to obtain more conclusive results considering some improvements that are discussed in the paper.
This appendix list the selected papers found in the systematic mapping study
Anais do XXVI Congresso Ibero-Americano em Engenharia de Software (CIbSE 2023)
Los procesos de elicitación de requisitos tienen una serie de desafíos y limitaciones en cuanto a... more Los procesos de elicitación de requisitos tienen una serie de desafíos y limitaciones en cuanto al foco en el proceso del negocio, la transparencia del sistema y el lidiar con la complejidad producto de la interdependencia. El enfoque de Design Thinking, centrado en las personas y en comprender el contexto de los problemas, puede aportar a resolverlos. En este artículo se presenta el estado actual de un proceso de elicitación de requisitos basado en Design Thinking propuesto para resolver algunos de los desafíos de los procesos existentes. Está compuesto por tres actividades: empatizar, sintetizar e idear. También se presentan los resultados de un focus group que se realizó con el objetivo de obtener feedback de expertos sobre el proceso, concretamente sobre el rol de la empatía en el proceso, su dominio de aplicación y actividades. Los resultados confirman vla utilidad del proceso y también generan una serie de enseñanzas que permitirán continuar refinándolo.
Procesos y Prácticas Ágiles en el Desarrollo de Software
Appendix_A systematic mapping study on the application of design thinking in requirement engineering.pdf
Hereafter, in this Appendix some relevant content that cannot be included in the paper due to spa... more Hereafter, in this Appendix some relevant content that cannot be included in the paper due to space constraints is presented. In order not to generate confusion, the tables will be listed in this Appendix with the suffix of the letter A in their titles.
This thesis introduces specifics guidelines to apply Web Requirements Engineering to the treatmen... more This thesis introduces specifics guidelines to apply Web Requirements Engineering to the treatment of Non-Functional Requirements. It introduces the process of Elicitation and Specification for Web Non-Functional Requirements and offers spreadsheets designed to capture and specify Non-Functional Requirements in the defined processes. While at present Requirement Engineering has numerous techniques and tools to identify, describe, validate and manage requirements, these are not frequently applied in the development of Web applications. The maturity of the Requirements Engineering process seems insufficient; this insufficiency demands new approaches or the evolution of current process to the correct treatment of Non-Functional Requirements. Non-Functional Requirements of software systems are not homogenous; there is a lack of consensus to answer the following questions: What are Non-Functional Requirements? How they are classified within the context of software development? and How the Non-Functional Requirements are classified within the development of web software application? This thesis starts with a revision of the state of art of the concept of Non-Functional Requirements in Requirements Engineering literature and establishes as conceptual foundations that Non-Functional Requirements are quality requirements and restrictions. Then, there is a comparative analysis of six different existing approaches in Web application development to study what treatment applies to Non-Functional Requirements, in which methodologies of the Web applications studied: Non-Functional Requirements are considered, but there is no consensus in their meaning. There are neither specifics techniques for elicitation of Non-Functional Requirements nor uniform guidelines for the specification and validation. There are no techniques supporting the treatment of the Non-Functional Requirements along the lifetime cycle. There is a lack of consensus to establish within which phase of development lifetime cycle Non-Functional Requirements are identified. There are Non-Functional Requirements that are not indentified during requirement capture and analysis phases. After this analysis and the give importance of the Non-Functional Requirements, a process for the elicitation and specification of the Web Non-Functional Requirements (quality and restrictions) is proposed, exposed spreadsheets are described to TESIS: Elicitación y Especificación de Requerimientos No Funcionales en Aplicaciones Web Rojo, Silvana iv support processes and finally, validations of the concepts and techniques are introduced applied to a real project.
Proceso de medición de funcionalidad en la Elicitación de Requerimientos
producir una descripción detallada de un problema, con el fin de construir un Sistema de Software... more producir una descripción detallada de un problema, con el fin de construir un Sistema de Software, que satisfaga las "necesidades y objetivos" de la organización donde funcionará dicho sistema. En la comunidad de Ingeniería de Requerimientos, estos objetivos constituyen el fundamento del sistema, y son usualmente definidos como las metas a ser cumplidas por el sistema y su entorno, aunque algunos autores distinguen los objetivos del sistema de los objetivos de la organización. Actualmente existen diferentes enfoques de formulación de los requerimientos del sistema de software a partir de los objetivos, cada uno de ellos con características diferentes pero con un propósito en común: disponer de las Metas u Objetivos que deberá cumplir el sistema. Como todo artefacto a producir en la fase de requerimientos, los objetivos del sistema deben recorrer un proceso de elicitación, modelización y validación [Lou95]. Sin embargo, las diferentes propuestas poseen, aunque en diferente medida, procesos mediante los que modelizan y validan los objetivos, pero no sucede lo mismo en cuanto a las indicaciones para la elicitación de los objetivos. Este trabajo presenta un estudio comparativo de los principales enfoques orientados a objetivos, analizando el proceso de elaboración de objetivos en cada uno de ellos, con especial atención en el proceso de Elicitación de Objetivos. Palabras Clave Metas y Objetivos. Elicitación de Objetivos. Stakeholder (STK) Introducción La complejidad de los problemas del mundo real generan la necesidad de poseer un proceso para su comprensión y entendimiento, mas aún si la solución a los mismos debe ser provista por Sistemas de Software. En este contexto, la Ingeniería de Requerimientos cumple un rol esencial para "elucidar" las cuestiones surgidas de esos problemas [Tho03]. Diferentes técnicas son aplicadas para adquirir conocimiento del dominio del problema. La elección de la técnica depende del tiempo y recursos disponibles por el analista y por supuesto, de la clase de información que necesita ser capturada [Nus00]. Se han clasificado [Nus00] las técnicas de elicitación en Tradicionales, Grupales, Prototipos, Orientadas por Modelos, Cognitivas y Contextuales.
Léxico extendido del lenguaje y escenarios del meeting scheduler
Curso Administración de Proyectos de Software
Construcción de Escenarios a partir del Léxico Extendido del Lenguaje
Baseline mentor, an application that derives CRC cards from lexicon and scenarios
We consider the cosmological constraints on the holographic dark energy model by using the data s... more We consider the cosmological constraints on the holographic dark energy model by using the data set available from the type Ia supernovae (SNIa), CMB and BAO observations. The constrained parameters are critical to determine the quintessence or quintom character the model. The SNIa and joint SNIa+CMB+BAO analysis give the best-fit results for $\beta$ with priors on $\Omega_{m0}$ and $\omega_0$. Using
2014 IEEE 22nd International Requirements Engineering Conference (RE), 2014
Estimating the size of a software system is a critical task due to the implications the estimatio... more Estimating the size of a software system is a critical task due to the implications the estimation has in the management of the development project. There are some widely accepted estimation techniques: Function Points, Use Case Points and Cosmic Points, but these techniques can only be applied after the availability of a requirements specification. In this paper, we propose an approach to estimate the size of an application previous to its requirements specification by using the application language itself, captured by the Language Extended Lexicon (LEL). Our approach is based on Use Case Points and on a technique which derives Use Cases from the LEL. The proposed approach provides a measure of the application's size earlier than the usual techniques, thus reducing the effort needed to apply them. An initial experiment was conducted to evaluate the proposal.
Integración de Escenarios con el Léxico Extendido del Lenguaje en la Elicitación de Requerimientos: aplicación a un caso real
Revista De Informática Teórica E Aplicada, 1999
ABSTRACT En nuestro trabajo nos hemos centrado en la elicitación de los requerimientos, para ello... more ABSTRACT En nuestro trabajo nos hemos centrado en la elicitación de los requerimientos, para ello estudiamos dos herramientas denominadas LEL [Leite 89] y escenarios [Carrol 95] [Rubin 92] [Potts 94] [Jacobson 92], y las aplicamos a un caso de estudio real: Sistema Nacional para la Obtención de Pasaportes. Ambas herramientas utilizan el lenguaje natural lo que permite una fácil validación con el usuario. El LEL (Léxico Extendido del Lenguaje) [Leite 89] tiene como propósito exclusivo conocer la semántica del vocabulario de la aplicación, dejando para una etapa posterior la comprensión del problema [Franco 92]. Utilizamos los escenarios para comprender el problema. En cada escenario se describe un momento específico de la aplicación, lo cual permite refinar el problema y analizarlo parcialmente.
Análisis de Medidas en la Etapa de Elicitación de Requerimientos
Uploads
Papers by Alejandro Oliveros