Reengineering legacy applications into software product lines: a systematic mapping

Assunção, Wesley K. G.; Lopez-Herrejon, Roberto E.; Linsbauer, Lukas; Vergílio, Silvia Regina; Egyed, Alexander

doi:10.1007/s10664-017-9499-z

Cited by 118 publications

(51 citation statements)

References 33 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the area of SPL evolution, Laguna et al made an assessment of the maturity level of techniques to migrate individual systems or groups of software variants into SPLs . Recent work by Assunção et al has further extended and updated the work of Laguna et al to provide a deeper analysis of techniques, tools, and case studies for migration to SPLs . Also, recently, Montalvillo et al performed a mapping study whose focus is on evolution of SPL as consequence of change in requirements.…”

Section: Related Workmentioning

confidence: 99%

“…34 Recent work by Assunção et al has further extended and updated the work of Laguna et al to provide a deeper analysis of techniques, tools, and case studies for migration to SPLs. 61 Also, recently, Montalvillo et al performed a mapping study whose focus is on evolution of SPL as consequence of change in requirements. 62 There have been 2 studies on variability management in general.…”

Section: Spl Surveysmentioning

confidence: 99%

See 1 more Smart Citation

A systematic mapping study of information visualization for software product line engineering

Lopez-Herrejon

Illescas

Egyed

2017

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

Software product lines (SPLs) are families of related systems whose members are distinguished by the set of features they provide. Over 2 decades of research and practice can attest to the substantial benefits of applying SPL practices such as better customization, improved software reuse, and faster time to market. Software product line engineering (SPLE) refers to the paradigm of developing SPLs. Typical SPLE efforts involve a large number of features that are combined to form also large numbers of products, implemented using multiple and different types of software artifacts. Because of the sheer amount of information and its complexity, visualization techniques have been used for different SPLE activities. In this paper, we present an extended systematic mapping study on this subject. Our research questions aim to gather information regarding the techniques that have been applied, at what SPLE activities, how they were implemented, the publication fora used, the methods of empirical evaluation, and the provenance of the evaluation examples. Our driving goal is to identify common trends, gaps, and opportunities for further research and application.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Spl Surveysmentioning

confidence: 99%

A systematic mapping study of information visualization for software product line engineering

Lopez-Herrejon

Illescas

Egyed

2017

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

show abstract

“…Then, the extractive SPL approach might be used to transform such already developed software products into an SPL. This approach uses the SPL reengineering process to take a number of product variants and transform them into an SPL with the use of techniques, methods, and tools …”

Section: Introductionmentioning

confidence: 99%

“…However, an extractive approach is the most indicated when the organization already has a set of software variants because it allows to identify and extract the commonalities and the variabilities among them. This process of extraction is called SPL reengineering …”

Section: Introductionmentioning

confidence: 99%

“…The term reengineering can be described as “the examination and alteration of a subject system to reconstitute it in a new form and the subsequent implementation of the new form.” In the SPL context, reengineering is used to transform a system, a system family, or system variants into an SPL. According to the work of Assunção et al, the SPL reengineering process is composed of three main phases (Figure ): detection, analysis, and transformation. During the first phase, ie, detection, the variabilities and commonalities of the products are identified and extracted from the system variants through the use of feature retrieval techniques.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

PAxSPL: A feature retrieval process for software product line reengineering

et al. 2019

View full text Add to dashboard Cite

Software product lines (SPLs) are a well-known solution to systematically create reusable software products. Among the approaches to create an SPL, the extractive approach is usually used when the organization already has a set of similar systems. These systems are analyzed to extract, categorize, and group their common and variant features throughout the SPL reengineering process. As there are different scenario variables, such as available artifacts and team experience, the activities and techniques used to perform these tasks may change. This may increase the effort and decrease the quality of retrieved features when users with low experience in SPL reengineering perform such tasks. However, there is a lack of a process supporting these tasks considering different scenarios. Therefore, we specify the Prepare, Assemble, and Execute Process for SPL Reengineering (PAxSPL), a process that provides support to prepare, assemble, and execute feature retrieval throughout the analysis of documentation and team experience. To initially evaluate PAxSPL, we conducted and reported an exploratory case study in a real development environment. The results indicated that our proposal helps in the assembly of a feature retrieval process according to user needs. Results were important to identify points for improvement in PAxSPL. We also could use the information gathered to improve the guidelines and provide this information to be used as basis of comparison for future users. KEYWORDS feature model, feature retrieval, software product line, software product line reengineering, software reengineering, software reuse 1278

show abstract

Opportunities for software reuse in an uncertain world: From past to emerging trends

Capilla

Gallina

Cetina

et al. 2019

J Software Evolu Process

View full text Add to dashboard Cite

Much has been investigated about software reuse since the software crisis. The development of software reuse methods, implementation techniques, and cost models has resulted in a significant amount of research over years. Nevertheless, the increasing adoption of reuse techniques, many of them subsumed under higher level software engineering processes, and advanced programming techniques that ease the way to reuse software assets, have hidden somehow in the recent years new research trends on the practice of reuse and caused the disappearance of several reuse conferences. Also, new forms of reuse like open data and feature models have brought new opportunities for reuse beyond the traditional software components.From past to present, we summarize in this research the recent history of software reuse, and we report new research areas and forms of reuse according to current needs in industry and application domains, as well as promising research trends for the upcoming years.

show abstract

Reengineering legacy applications into software product lines: a systematic mapping

Cited by 118 publications

References 33 publications

A systematic mapping study of information visualization for software product line engineering

A systematic mapping study of information visualization for software product line engineering

PAxSPL: A feature retrieval process for software product line reengineering

Opportunities for software reuse in an uncertain world: From past to emerging trends

Contact Info

Product

Resources

About