Analyzing Trends in Software Product Lines Evolution Using aCladistics Based Approach

A software product line is a complex system the aim of which is to provide a platform dedicated to large reuse. It necessitates a great investment. Thus, its ability to cope with customers’ ever-changing requirements is among its key success factors. Great effort has been made to deal with the software product line evolution. In our previous works, we carried out a classification of these works to provide an overview of the used techniques. We also identified the following key challenges of software product lines evolution: the ability to predict future changes, the ability to define the impact of a change easily and the improvement in understanding the change. We have already tackled the second and the third challenges. The objective of this paper is to deal with the first challenge. We use the cladistics classification which was used in biology to understand the evolution of organisms sharing the same ancestor and their process of descent at the aim of predicting their future changes. By analogy, we consider a population of applications for media management on mobile devices derived from the same platform and we use cladistics to construct their evolutionary tree. We conducted an analysis to show how to identify the evolution trends of the case study products and to predict future changes

Desarrollo de familias de aplicaciones web con transformación de modelos

Tesis (Doctor en Ciencias de la Computación)--Universidad Nacional de Córdoba, Facultad de Matemática, Astronomía, Física y Computación, 2020.El desarrollo de Líneas de Productos de Software (SPL, por sus siglas en inglés) trae aparejado beneficios importantes para el desarrollo de sistemas de software: reducción de tiempos de desarrollo y comercialización, mejoras en la calidad. La evolución de las aplicaciones web, el surgimiento de sitios colaborativos (como el repositorio gitHub) de desarrollo de aplicaciones web y la gran cantidad de sistemas de escritorio que han ido migrando a la web, hizo que se generen muchas aplicaciones web de gran escala y altamente configurables que son desarrolladas individualmente y que podrían ser tratadas como líneas de productos o familias de aplicaciones, para así aprovechar los beneficios que este tipo de desarrollo provee. Para este fin, este trabajo presenta un proceso de desarrollo de familias de aplicaciones web que comprende modelado de dominio, proceso de configuración de modelos de dominio, modelado de aplicaciones y proceso de desarrollo de interfaz de usuario web responsiva. El proceso definido aquí ataca los principales problemas hallados en el área de investigación: construcción manual de modelo de features (en adición a modelos de dominio); no provisión de automatismos para generar configuraciones de modelos de dominio; no modelado ni consideración de variabilidad en interfaces de usuario y no prescripción de método para modelar interfaz de usuario. Además, tiene en cuenta problemas generales del área de SPL y aspectos propios del área de aplicaciones web.The development using Software Product Lines (SPL) brings important benefits for the development of software systems: reduction of development and commercialization times, improvements in quality. The evolution of web applications, the emergence of collaborative web application development sites (such as the gitHub repository), and the large number of desktop systems that have been migrating to the web, led to many large-scale web applications and highly configurable that are developed individually and that could be treated as product lines or application families, in order to take advantage of the benefits that this type of development provides. For this purpose, this paper presents a web application family development process that includes domain modeling, domain model configuration process, application modeling and responsive web user interface development process. The process defined here addresses the main problems found in the research area: manual construction of feature models (in addition to domain models); no provision of automation to generate domain model configurations; no modeling or consideration of variability in user interfaces and no method prescription for modeling user interface. In addition, it takes into account general problems in the SPL area and aspects of the web applications area.publishedVersionFil: Casalánguida, Hernán. Universidad Nacional de Córdoba. Facultad de Matemática, Astronomía, Física y Computación; Argentina