Supporting software product lines development

Soares, Sérgio; Calheiros, Fernando; Nepomuceno, Vilmar; Menezes, Andrea Carvalho; Borba, Paulo; Alves, Vander

doi:10.1145/1449814.1449837

Cited by 5 publications

(2 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Additionally, the FLiP tool was developed to implement the previously mentioned catalog of AO-based refactoring templates and the associated strategy to support the extractive and the reactive SPL adoption strategies. The tool provided semi-automated support for the task of modularizing portability-based features in three case studies involving industrial-strength mobile games (Alves et al, 2008;Soares et al, 2008).…”

Section: Key Challengesmentioning

confidence: 99%

The crosscutting impact of the AOSD Brazilian research community

Kulesza

Soares

Chávez

et al. 2013

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

Background: Aspect-Oriented Software Development (AOSD) is a paradigm that promotes advanced separation of concerns and modularity throughout the software development lifecycle, with a distinctive emphasis on modular structures that cut across traditional abstraction boundaries. In the last 15 years, research on AOSD has boosted around the world. The AOSD-BR research community (AOSD-BR stands for AOSD in Brazil) emerged in the last decade, and has provided different contributions in a variety of topics. However, despite some evidence in terms of the number and quality of its outcomes, there is no organized characterization of the AOSD-BR community that positions it against the international AOSD Research community and the Software Engineering Research community in Brazil. Aims: In this paper, our main goal is to characterize the AOSD-BR community with respect to the research developed in the last decade, confronting it with the AOSD international community and the Brazilian Software Engineering community. Method: Data collection, validation and analysis were performed in collaboration with several researchers of the AOSD-BR community. The characterization was presented from three different perspectives: (i) a historical timeline of events and main milestones achieved by the community; (ii) an overview of the research developed by the community, in terms of key challenges, open issues and related work; and (iii) an analysis on the impact of the AOSD-BR community outcomes in terms of well-known indicators, such as number of papers and number of citations. Results: Our analysis showed that the AOSD-BR community has impacted both the international AOSD Research community and the Software Engineering Research community in Brazil.

show abstract

Section: Key Challengesmentioning

confidence: 99%

The crosscutting impact of the AOSD Brazilian research community

Kulesza

Soares

Chávez

et al. 2013

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

show abstract

“…Once this relation has been explicitly represented, it can be used for a number of purposes, most importantly to automatically derive product instances based on product-configuration specifications, but also for other purposes such as trace-link generation and consistency checking of SPL models. Due to its relevance, this topic is currently an area of intensive research and a number of approaches have been proposed [5][6][7][8][9]. Initial research focused on using general-purpose model transformations to encode product derivation [10][11].…”

Section: Introductionmentioning

confidence: 99%

VML* – A Family of Languages for Variability Management in Software Product Lines

Zschaler

Sánchez

Santos

et al. 2010

Software Language Engineering

View full text Add to dashboard Cite

Abstr act. Managing variability is a challenging issue in software-product-line engineering. A key part of variability management is the ability to express explicitly the relationship between variability models (expressing the variability in the problem space, for example using feature models) and other artefacts of the product line, for example, requirements models and architecture models. Once these relations have been made explicit, they can be used for a number of purposes, most importantly for product derivation, but also for the generation of trace links or for checking the consistency of a product-line architecture. This paper bootstraps techniques from product-line engineering to produce a family of languages for variability management for easing the creation of new members of the family of languages. We show that developing such language families is feasible and demonstrate the flexibility of our language family by applying it to the development of two variability-management languages.

show abstract