2013
DOI: 10.1007/978-3-642-38977-1_22
|View full text |Cite
|
Sign up to set email alerts
|

Feature Location in a Collection of Software Product Variants Using Formal Concept Analysis

Abstract: Formal Concept Analysis (FCA) is a theoretical framework which structures a set of objects described by properties. In order to migrate software product variants which are considered similar into a product line, it is essential to identify the common and the optional features between the software product variants. In this paper, we present an approach for feature location in a collection of software product variants based on FCA. In order to validate our approach we applied it on a case study based on ArgoUML.… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
26
0

Year Published

2016
2016
2022
2022

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 26 publications
(26 citation statements)
references
References 13 publications
0
26
0
Order By: Relevance
“…Depending on the granularity, feature location can focus on code fragments in the case of source code [27,28,29,30], model fragments in the context of models [31] or software components in software architectures [19,20,21,22,23,24]. Therefore, existing techniques are composed of two phases: An abstraction phase, where the different artefact variants are abstracted, and the location phase where algorithms analyse or compare the different product variants to obtain the implementation elements associated to each feature.…”
Section: Background On Feature Location In Feature-based Variantsmentioning
confidence: 99%
“…Depending on the granularity, feature location can focus on code fragments in the case of source code [27,28,29,30], model fragments in the context of models [31] or software components in software architectures [19,20,21,22,23,24]. Therefore, existing techniques are composed of two phases: An abstraction phase, where the different artefact variants are abstracted, and the location phase where algorithms analyse or compare the different product variants to obtain the implementation elements associated to each feature.…”
Section: Background On Feature Location In Feature-based Variantsmentioning
confidence: 99%
“…Moreover, Iris approach used only the source code of software variants as inputs of the software metrics mining process. Also Iris extracts the source code of each software variant based on the static code analysis 14 . Iris code parser used to access and read the source code of software systems.…”
Section: Extracting Software Codementioning
confidence: 99%
“…However, depending on the nature of the variants, this can concern code fragments in the case of source code [2,11,23,34], model fragments in the context of models [12,20] or software components in software architectures [1,14]. Therefore, existing techniques are composed of the following two phases: 1) Abstraction, where the different product variants are abstracted and represented as implementation elements; 2) Location, where algorithms analyse and compare the different product variants to create groups of implementation elements.…”
Section: Feature Locationmentioning
confidence: 99%
“…In addition, the granularity of the sought implementation elements may vary from coarse to fine [16]. Some use fine granularity using AST nodes that cover all source code statements while others use purposely a little bit bigger granularity using object-oriented building elements [2] Continuing with Eclipse terminology, a simultaneous release (release hereafter) is a set of packages which are public under the supervision of the Eclipse Foundation. Every year, there is one main release, in June, which is followed by two service releases for maintenance purposes: SR1 and SR2 usually around September and February.…”
Section: Feature Locationmentioning
confidence: 99%
See 1 more Smart Citation