Navegación

Búsqueda

Búsqueda avanzada

El autor Agustín Yagüe ha publicado 7 artículo(s):

1 - Change-Impact driven Agile Architecting

his summary presents a solution based on the use of change-impact knowledge as the main driver for agile architecting. The solution consists of a Change Impact Analysis technique and a set of models to assist agile architects in the change (decision-making) process by retrieving the change-impact architectural knowledge resulting from adding or changing features iteration after iteration.

Autores: Jessica Díaz / Jennifer Pérez / Juan Garbajosa / Agustín Yagüe / 
Palabras Clave: agile architecting - Agile software development - change-impact analysis

2 - Usability mechanisms extension to ScrumTime

This contribution presents the extension of the existing ScrumTime tool to support usability mechanisms that has been done. The presented tool is used to manage agile projects. The extension increases the features of ScrumTime to define user stories through usability mechanisms selection, acceptance criteria definition and recommendation about usability tasks, acceptance criteria and usability stories. The tool is available to be tested.

Autores: Ana M. Moreno / Agustin Yagüe / Diego Yucra / 
Palabras Clave: Agile development - HCI - usability patterns - user stories

3 - Tailoring user stories to deal with usability

Agile teams have to address usability to properly catch their users experience. But like in traditional software development, this task is not easy to achieve; there exists an interesting debate in the agile and usability communities about how to deal with this integration. In this paper we try to contribute to this debate by discussing the incorporation of particular usability recommendations into one of the most popular artifacts for communicating agile requirements, user stories. We discuss about the changes the incorporation of particular usability issues may introduce in a user story, and describe a tool that helps the agile team to deal with such usability issues during the specification of user stories. Some encouraging results about preliminary validation are also presented in the paper.

Autores: Ana M. Moreno / Agustin Yagüe / Diego Yucra / 
Palabras Clave: Agile development - HCI - usability patterns - user stories

4 - An exploratory study in communication in Agile Global Software Development

Global software development (GSD) is gaining ever more relevance. Although communication is key in the exchange of information between team members, multi-site software development has introduced additional obstacles (different time-zones and cultures, IT infrastructure, etc.) and delays into the act of communication, which is already problematic. Communication is even more critical in the case of Agile Global Software Development (AGSD) in which communication plays a primary role. This paper reports an exploratory study of the effects of tools supporting communication in AGSD. More precisely, this paper analyses the perception of team members about communication infrastructures in AGSD. The research question to which this study responds concerns how development teams perceive the communication infrastructure while developing products using agile methodologies. Most previous studies have dealt with communication support from a highly technological media tool perspective. In this research work, instead, observations were obtained from three perspectives: communication among team members, communication of the status of the development process, and communication of the status of the progress of the product under development. It has been possible to show that team members perceive advantages to using media tools that make them feel in practice that teams are co-located, such as smartboards supported by efficient video-tools, and combining media tools with centralized repository tools, with information from the process development and product characteristics, that allow distributed teams to effectively share information about the status of the project/process/product during the development process in order to overcome some of the still existing problems in communication in AGSD. COMPUTER STANDARDS & INTERFACES Volumen: 48 Páginas: 184-197 Número especial: SI DOI: 10.1016/j.csi.2016.06.002 Impacto de la revista 2015 Computer Science: 171/393 Q2 2015 Computer Svience/Software Engineering 35/106 Q2

Autores: Agustin Yague / Juan Garbajosa / Jessica Díaz / Eloy Gonzalez Ortega / 
Palabras Clave: Agile - Development project - Exploratory research - Global Distributed Software Development - Infrastructure - Mangement - Teams - Tools and technologies

5 - Visual CPS: Sistemas Ciber-Físicos en la Nube con Soporte a la Variabilidad y Multitenencia

En los últimos años, nuestra sociedad está cambiando a gran velocidad. Cada vez son más los dispositivos que interactúan con nosotros y el entorno para ofrecernos servicios ampliados respecto a los servicios de información tradicionales. Esta nueva era de Internet de las Cosas (Internet of Things – IoT) y de servicios al ciudadano a través de internet, con la nueva concepción de los sistemas inteligentes (smart buildings, grids, cities y spaces), necesitan cada vez de más recursos computacionales y software. En este sentido, Cloud Computing ofrece una serie de características en cuanto escalabilidad y flexibilidad, acceso a recursos a través de Internet (off-premises) sin necesidad de ser instalados y gestionados localmente (on-premises) [1] que son fundamentales para soportar tales sistemas. Los servicios proporcionados por la nube son infraestructura (IaaS), plataforma de desarrollo (PaaS) y software (SaaS). Una de las características más significativas de SaaS (Software as a Service) es la multitenencia, la cual promueve las economías de escala mediante la compartición de una serie de recursos entre múltiples usuarios o grupos de usuarios denominados tenants. Cada tenant podría personalizar ciertas partes del software para satisfacer requisitos individuales. Este concepto no es nuevo, y ha sido abordado ampliamente por la ingeniería de líneas de producto [8] y la gestión de la variabilidad. La variabilidad de un producto software se puede definir como la capacidad de este para cambiar y ser utilizado en múltiples contextos. Resulta de gran importancia el dotar al software de mecanismos para soportar distintos grados de variabilidad para poder ofrecer una personalización ajustada a las necesidades específicas de los usuarios. En este artículo se presenta una herramienta para la creación y gestión de sistemas ciber-físicos en la nube con soporte a múltiples tenants y variabilidad entre los tenants llamada Visual CPS. Un sistema ciber-físico es aquel sistema en el que se embebe o integra capacidad de cómputo con el objetivo de interactuar el software con el mundo físico, obteniendo una comunicación bidireccional entre estos dos. Para soportar dichas características la herramienta se basa en el concepto de multitenencia de la plataforma de nube GPaaS [7] y en el diseño arquitectónico basado en el estilo de microservicios [2] que se define como una aplicación compuesta por componentes independientes, ligeros y muy especializados orquestados para proporcionar la funcionalidad de la aplicación global.

Autores: Héctor Humanes / Jessica Díaz / Carlos Fernández / Agustín Yagüe / 
Palabras Clave: Ciber physical system - Cloud Computing - microservices - Multitenancy - Variability

6 - Identification and analysis of the elements required to manage technical debt by means of a systematic mapping study (Artículo relevante)

Artículo publicado en Journal of Systems and Software (JSS). JSS es clasificada como Q1 en JCR 2017. @article{FERNANDEZSANCHEZ201722,title = «Identification and analysis of the elements required to manage technical debt by means of a systematic mapping study»,journal = «Journal of Systems and Software»,volume = «124»,pages = «22 – 38»,year = «2017»,issn = «0164-1212»,doi = «https://doi.org/10.1016/j.jss.2016.10.018»,url = «http://www.sciencedirect.com/science/article/pii/S0164121216302138»,author = «Carlos Fernández-Sánchez and Juan Garbajosa and Agustín YagÃŒe and Jennifer Perez»,keywords = «Technical debt, Technical debt management, Systematic mapping, Decision making, Basic decision-making factors, Cost estimation techniques, Practices and techniques for decision-making, Stakeholdersâ?? points of view, Engineering, Engineering management, Business-organizational management, Framework»,abstract = «Technical debt, a metaphor for the long-term consequences of weak software development, must be managed to keep it under control. The main goal of this article is to identify and analyze the elements required to manage technical debt. The research method used to identify the elements is a systematic mapping, including a synthesis step to synthesize the elements definitions. Our perspective differs from previous literature reviews because it focused on the elements required to manage technical debt and not on the phenomenon of technical debt or the activities used in performing technical debt management. Additionally, the rigor and relevance for industry of the current techniques used to manage technical debt are studied. The elements were classified into three groups (basic decision-making factors, cost estimation techniques, practices and techniques for decision-making) and mapped according three stakeholdersâ?? points of view (engineering, engineering management, and business-organizational management). The definitions, classification, and analysis of the elements provide a framework that can be deployed to help in the development of models that are adapted to the specific stakeholdersâ?? interests to assist the decision-making required in technical debt management and to assess existing models and methods. The analysis indicated that technical debt management is context dependent.»}

Autores: Carlos Fernández-Sánchez / Juan Garbajosa / Agustín Yagüe / Jennifer Perez / 
Palabras Clave: Basic decision-making factors - Business-orga - Cost estimation techniques - Decision Making - Engineering - Engineering management - Practices and techniques for decision-making - Stakeholders’ points of view - Systematic mapping - technical debt - Technical debt management

7 - A Data-Interoperability Aware Software Architecture

Making heterogeneous data sources homogeneous manually and off-line can become a high time-consuming task. This paper presents a software architecture that extends the standardized-based architectures for heterogeneous sensors with components to also support devices and data that are not compliant with standards. The defined architecture is based on Internet of Things (IoT) layered architectures that establish perception, network, middleware, application, and business as main layers. To define the architecture, an architectural framework was used; this framework supports the identification of non-compliant data, providing then a different processing path. This proposed architecture covers a wide spectrum of data interoperability addressing the IoT challenge of «Interoperability and Standardization». The implemented solution proved that the processing time between data acquisition and the feeding of analysis algorithms can be reduced from 100% to approximately to 1% with systems based on the proposed architecture compared with those that manage data manually and off-line.

Autores: Hector Humanes / Agustin Yague / Jennifer Perez / Juan Garbajosa / Llorenç Burgas / Joan Colomer / Joaquim Melendez / Carles Pous / 
Palabras Clave: interoperability - IoT - Software Architecture