An extension to iStar framework as alternative to support design decisions in the task analysis performed in the Human Computer Interaction Area (HCI)

Abstract The goal of this work is to present i* framework as alternative to support design decisions in the Human Computer Interaction Area (HCI), mainly, in the process of task analysis. We show i* framework a modeling language suitable for an early phase of software system modeling to understand the problem domain, also, that provides methods to represent tasks, as well as support design decisions the development that satisfies the process requirements from the beginning until the end. To achieve our goal, approaches addressed to analyze notations aimed at task analysis and their representation. Finally, we present suggestions for improvement in the i* framework through a proposed extension for refining task model, instantiating examples and justifying our proposal through peer review.Abstract The goal of this work is to present i* framework as alternative to support design decisions in the Human Computer Interaction Area (HCI), mainly, in the process of task analysis. We show i* framework a modeling language suitable for an early phase of software system modeling to understand the problem domain, also, that provides methods to represent tasks, as well as support design decisions the development that satisfies the process requirements from the beginning until the end. To achieve our goal, approaches addressed to analyze notations aimed at task analysis and their representation. Finally, we present suggestions for improvement in the i* framework through a proposed extension for refining task model, instantiating examples and justifying our proposal through peer review

Agile Functional Requirements Modeling from Goal-Oriented Requirements Engineering: A Systematic Mapping Study

During the last two decades, the application of Goal-Oriented Requirements Engineering has increased in software projects, mainly because this approach is useful during the requirements analysis process and supports the realization of tasks such as requirements elaboration, validation, and planning, and can be used as part of the system life cycle, e.g. architecture and design of behavioral processes, coding, testing, monitoring, adaptation and evolution. Several approaches addressing goal-oriented requirements have already been proposed. Currently, there are several concerns about how to correctly adopt and implement it in current industrial contexts, such as agile approaches and, more specifically, its integration with user stories and acceptance criteria. This study presents a compilation of the current knowledge on adopting GORE in agile requirements specification through user stories and their acceptance criteria. A systematic mapping study guided by ten research questions was conducted, and nine primary studies were selected considering the selection criteria. The results obtained show some initiatives as goal-oriented modelling languages in different proposals for transforming goal-oriented models into user stories, among them: i* (i-star), Tropos, KAOS, GRL, AOM, and Goal Net. This study provides a solid basis for classifying existing and future approaches in the application of GORE. Researchers and practitioners can use this mapping to identify existing technical/research gaps to better address and assess their own contributions or understand existing ones

Semi-Automatic Mapping Technique Using Snowballing to Support Massive Literature Searches in Software Engineering

Systematic literature reviews represent an important methodology in Evidence-Based Software Engineering. To define the methodological route in these type of studies, in which a review of quantitative and qualitative aspects of primary studies is carried out to summarize the existing information regarding a particular topic, researchers use protocols that guide the construction of knowledge from research questions. This article presents a process that uses forward Snowballing, which identifies the articles cited in the paper under study and the number of citations as inclusion criteria to complement systematic literature reviews. A process that relies on software tools was designed to apply the Snowballing strategy and to identify the most cited works and those who cite them. To validate the process, a review identified in the literature was used. After comparing the results, new works that were not taken into account but made contributions to the subject of study emerged. The citation index represents the number of times a publication has been referenced in other documents and is used as a mechanism to analyze, measure, or quantitatively assess the impact of said publication on the scientific community. The present study showed how applying Snowballing along with other strategies enables the emergence of works that may be relevant for an investigation given the citations rate. That is, implementing this proposal will allow updating or expanding systematic literature studies through the new works evidenced

APLICACIÓN Y AJUSTE EN LA PRÁCTICA DEL NUEVO PROCESO DE MEJORA PARA PROCESOS DE SOFTWARE AGILE SPI PROCESS: CASO DE ESTUDIO REAL EN UNA PYME

RESUMENEl trabajar en el sector de las PyMES (Pequeñas y Medianas Empresas) con un programa SPI (Software Process Improvement - Mejora de Procesos de Software) es un interés que se ha vuelto muy importante en todo el mundo. Algunos estudios han demostrado que la dificultad de aplicación de grandes modelos en un SPI es un problema en PyMEs, fundamentalmente por los grandes costes asociados a su aplicación (tiempo y recursos), especialmente en el seguimiento de los planes de acción e implantación [6]. Otro problema añadido para las PyMEs, es el largo plazo de espera necesario para la obtención de resultados [2], nuevamente demasiado para una PyME. Éste artículo propone un proceso para la Mejora de Procesos de Software para apoyar la gestión y administración de un programa de mejora pero adaptado a las características de las PyMEs, fue desarrollado en el proyecto SIMEP-SW y aplicado a dos PyMES de Software. Este artículo presenta el modelo y la experiencia de su aplicación en unaPyME. La experiencia permitió probar el modelo y evaluar su impacto en el contexto de las PyMES. Algunas lecciones aprendidas fueron recopiladas para refinar y ajustar el modelo. En definitiva, el tamaño de una empresa no limita el éxito de los programas de mejora sino que se ve afectado fundamentalmente por los problemas mencionados anteriormente; el proceso expuesto en este trabajo pretende que sea utilizado en empresas de cualquier tamaño, especialmente las PyMES. PALABRAS CLAVEMejora de Procesos de Software (SPI)CalidadCMMIPequeñas y Medianas Empresas (PyMEs)PyMEÁgilProceso ABSTRACTWorking in the SMEs (Small and Medium Enterprises) sector with an SPI (Software Process Improvement) program is an interest that has become very important anywhere in the world. Some studies have demonstrated that the difficulty of application of large international models in a SPI is a problem in SMEs, basically by the great costs associated to its application (time and resources), specially in the tracking of the action and implantation plans [6]. Another problem for the SMEs is the long waiting time for obtaining results [2], again too much for a SME. This article proposes a process for the Software Process Improvement to support the managementand administration of an improvement program but adapted to the features of the SMEs, it was developed in the SIMEP-SW project and applied to two software SMEs. This article presents the model and the experience of its application in a SME. The experience has allowed to prove the model and to evaluate their impact in the context of the SMEs. Some learned lessons were compiled to refine and to fit the model. After all, the size of an enterprise doesn't limit the success of the improvement programs but it is affected fundamentally by the problems mentioned previously; the process exposed in this work pretends to be used in enterprises of any size, especially the SMEs. KEYWORDS: Software Process Improvement (SPI)QualityCMMISmall and Medium Enterprises (SME's)SMEAgileProces

APLICACIÓN Y AJUSTE EN LA PRÁCTICA DEL NUEVO PROCESO DE MEJORA PARA PROCESOS DE SOFTWARE AGILE SPI PROCESS: CASO DE ESTUDIO REAL EN UNA PYME

RESUMENEl trabajar en el sector de las PyMES (Pequeñas y Medianas Empresas) con un programa SPI (Software Process Improvement - Mejora de Procesos de Software) es un interés que se ha vuelto muy importante en todo el mundo. Algunos estudios han demostrado que la dificultad de aplicación de grandes modelos en un SPI es un problema en PyMEs, fundamentalmente por los grandes costes asociados a su aplicación (tiempo y recursos), especialmente en el seguimiento de los planes de acción e implantación [6]. Otro problema añadido para las PyMEs, es el largo plazo de espera necesario para la obtención de resultados [2], nuevamente demasiado para una PyME. Éste artículo propone un proceso para la Mejora de Procesos de Software para apoyar la gestión y administración de un programa de mejora pero adaptado a las características de las PyMEs, fue desarrollado en el proyecto SIMEP-SW y aplicado a dos PyMES de Software. Este artículo presenta el modelo y la experiencia de su aplicación en unaPyME. La experiencia permitió probar el modelo y evaluar su impacto en el contexto de las PyMES. Algunas lecciones aprendidas fueron recopiladas para refinar y ajustar el modelo. En definitiva, el tamaño de una empresa no limita el éxito de los programas de mejora sino que se ve afectado fundamentalmente por los problemas mencionados anteriormente; el proceso expuesto en este trabajo pretende que sea utilizado en empresas de cualquier tamaño, especialmente las PyMES. PALABRAS CLAVEMejora de Procesos de Software (SPI)CalidadCMMIPequeñas y Medianas Empresas (PyMEs)PyMEÁgilProceso ABSTRACTWorking in the SMEs (Small and Medium Enterprises) sector with an SPI (Software Process Improvement) program is an interest that has become very important anywhere in the world. Some studies have demonstrated that the difficulty of application of large international models in a SPI is a problem in SMEs, basically by the great costs associated to its application (time and resources), specially in the tracking of the action and implantation plans [6]. Another problem for the SMEs is the long waiting time for obtaining results [2], again too much for a SME. This article proposes a process for the Software Process Improvement to support the managementand administration of an improvement program but adapted to the features of the SMEs, it was developed in the SIMEP-SW project and applied to two software SMEs. This article presents the model and the experience of its application in a SME. The experience has allowed to prove the model and to evaluate their impact in the context of the SMEs. Some learned lessons were compiled to refine and to fit the model. After all, the size of an enterprise doesn't limit the success of the improvement programs but it is affected fundamentally by the problems mentioned previously; the process exposed in this work pretends to be used in enterprises of any size, especially the SMEs. KEYWORDS: Software Process Improvement (SPI)QualityCMMISmall and Medium Enterprises (SME's)SMEAgileProces