Navegación

Búsqueda

Búsqueda avanzada

El autor Jennifer Perez ha publicado 6 artículo(s):

2 - 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

3 - Agile Product Line Engineering–A Systematic Literature Review

Software Product Line Engineering (SPLE)[1] demands upfront long-term investment in (i) designing a common set of core-assets and (ii) managing variability across the products from the same family. When anticipated changes in these coreassets have been predicted with certain accuracy, SPLE has proved significant improvements. However, when large/complex product-line projects have to deal with changing market conditions, alternatives to supplement SPLE are required.

Autores: Jessica Díaz / Jennifer Pérez / Pedro P. Alarcón / Juan Garbajosa / 
Palabras Clave:

4 - Agile Moodle: Una plataforma para el Aprendizaje Ágil en Ingeniería del Software

En la actualidad, la universidad española todavía tiene retos pendientes de superar para adaptarse al marco del Espacio Europeo de Educación Superior (EEES). Uno de los más importantes es el de proporcionar mecanismos para fomentar y evaluar la adquisición de competencias generales o transversales: capacidades, habilidades y/o aptitudes que el alumno debe desarrollar para aplicarlas a lo largo de su carrera profesional.Por otro lado, en la última década, las metodologías ágiles [1] han adquirido una gran relevancia en el área de la industria software, debido a que su adopción en las empresas está revirtiendo en un aumento de la calidad y competitividad en el mercado [2]. Esto hace indispensable que los contenidos necesarios para el aprendizaje de las metodologías ágiles se impartan en asignaturas pertenecientes a la rama de ingeniería del software, así como su práctica durante el ciclo formativo del ingeniero de software. Asimismo, las metodologías ágiles, y especialmente SCRUM [3], se centran en la gestión de proyectos basados en equipos auto-organizados donde se potencia a sus individuos. En este sentido, las metodologías ágiles se presentan como un marco perfecto para la adquisición de competencias generales de forma flexible y sencilla.

Autores: Pablo Ortíz / Jennifer Pérez / Santiago Alonso / José Luis Sánchez / Javier Gil / 
Palabras Clave:

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

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. Artículo publicado en Journal of Systems and Software (JSS). JSS es clasificada como Q1 en JCR 2017.

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

6 - 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