Defining a strategy to introduce a software product line using existing embedded systems

Yoshimura, Kazuyoshi; Ganesan, Dharmalingam; Muthig, Dirk

doi:10.1145/1176887.1176897

Cited by 23 publications

(20 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In the list representation of the similarity graph, the textual similarity of signatures is used to categorize similarities as described in [23] enabling the developer to determine how easy it is to unify the code.…”

Section: Testo Agmentioning

confidence: 99%

See 1 more Smart Citation

Supporting the Grow-and-Prune Model in Software Product Lines Evolution Using Clone Detection

Mende¹,

Beckwermert²,

Koschke³

et al. 2008

2008 12th European Conference on Software Maintenance and Reengineering

View full text Add to dashboard Cite

Software Product Lines (SPL) can be used to create and maintain different variants of software-intensive systems by explicitly managing variability. Often, SPLs are organized as an SPL core, common to all products, upon which product-specific components are built. Following the so called grow-and-prune model, SPLs may be evolved by copy&paste at large scale. New products are created from existing ones and existing products are enhanced with functionalities specific to other products by copying and pasting code between product-specific code. To regain control of this unmanaged growth, such code may be pruned, that is, identified and refactored into core components upon success. This paper describes tool support for the grow-andprune model in the evolution of software product lines by identifying similar functions which can be moved to the core. These functions are identified in two steps. First, token-based clone detection is used to detect pairs of functions sharing code. Second, Levenshtein distance measures the textual similarity among these functions. Sufficient similarity at function level is then lifted to the architectural level.The approach is evaluated by three case studies, one using an open source email client to simulate the initial creation of an SPL, and two monitoring existing industrial product lines from the embedded domain.

show abstract

Section: Testo Agmentioning

confidence: 99%

“…The migration towards a software product line is also supported using clone detection in [23]. They use a categorization based on the similarity of the signature.…”

Section: Related Workmentioning

confidence: 99%

Supporting the Grow-and-Prune Model in Software Product Lines Evolution Using Clone Detection

Mende¹,

Beckwermert²,

Koschke³

et al. 2008

2008 12th European Conference on Software Maintenance and Reengineering

View full text Add to dashboard Cite

show abstract

“…There is a method of CVA of code elements using code clone detection [11]. A code clone is a code fragment that is identical or similar to another in the code.…”

Section: Commonality and Variability Analysismentioning

confidence: 99%

Recovering Traceability Links between Requirements and Source Code Using the Configuration Management Log

Tsuchiya

Washizaki

Fukazawa

et al. 2015

IEICE Trans. Inf. & Syst.

Self Cite

View full text Add to dashboard Cite

SUMMARYTraceability links between requirements and source code are helpful in software reuse and maintenance tasks. However, manually recovering links in a large group of products requires significant costs and some links may be overlooked. Here, we propose a semi-automatic method to recover traceability links between requirements and source code in the same series of large software products. In order to support differences in representation between requirements and source code, we recover links by using the configuration management log as an intermediary. We refine the links by classifying requirements and code elements in terms of whether they are common to multiple products or specific to one. As a result of applying our method to real products that have 60KLOC, we have recovered valid traceability links within a reasonable amount of time. Automatic parts have taken 13 minutes 36 seconds, and non-automatic parts have taken about 3 hours, with a recall of 76.2% and a precision of 94.1%. Moreover, we recovered some links that were unknown to engineers. By recovering traceability links, software reusability and maintainability will be improved. key words: traceability recovery, configuration management log, commonality and variability analysis, software product line

show abstract

“…Several strategies for introducing SPL engineering have been reported, e.g., [201,110,226,156]. Yoshimura et al [226] present a migration process composed of the following activities: estimate economic benefits, redefine the development process, restructure the organization, assess the merge potential, perform merging, and maintain the software product line.…”

Section: Processesmentioning

confidence: 99%

“…Yoshimura et al [226] present a migration process composed of the following activities: estimate economic benefits, redefine the development process, restructure the organization, assess the merge potential, perform merging, and maintain the software product line. Krsek et al [156] propose a set of relevant processes: define funding, structure the organization, define the product line, manage risks, develop acquisition strategy, and others.…”

Section: Processesmentioning

confidence: 99%

Software diversity: state of the art and perspectives

Schaefer

Rabiser²,

Clarke

et al. 2012

Int J Softw Tools Technol Transfer

136

View full text Add to dashboard Cite

Abstract. Diversity is prevalent in modern software systems to facilitate adapting the software to customer requirements or the execution environment. Diversity has an impact on all phases of the software development process. Appropriate means and organizational structures are required to deal with the additional complexity introduced by software variability. This introductory article to the special section "Software Diversity -Modeling, Analysis and Evolution" provides an overview of the current state of the art in diverse systems development and discusses challenges and potential solutions. The article covers requirements analysis, design, implementation, verification and validation, maintenance and evolution as well as organizational aspects. It also provides an overview of the articles which are part of this special section and address particular issues of diverse systems development.

show abstract

Defining a strategy to introduce a software product line using existing embedded systems

Cited by 23 publications

References 15 publications

Supporting the Grow-and-Prune Model in Software Product Lines Evolution Using Clone Detection

Supporting the Grow-and-Prune Model in Software Product Lines Evolution Using Clone Detection

Recovering Traceability Links between Requirements and Source Code Using the Configuration Management Log

Software diversity: state of the art and perspectives

Contact Info

Product

Resources

About