2005
DOI: 10.1016/j.infsof.2004.11.007
|View full text |Cite
|
Sign up to set email alerts
|

A theoretical foundation of variability in component-based development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
33
0

Year Published

2006
2006
2013
2013

Publication Types

Select...
6
2
1

Relationship

3
6

Authors

Journals

citations
Cited by 42 publications
(33 citation statements)
references
References 8 publications
0
33
0
Order By: Relevance
“…The lack of approaches may be due to the wide variety of possibilities to translate a conceptual variation point (i.e. a delayed decision) to the implementation of a variation point, as well as to the difficulty to trace this translation [20,14]. Thummalapenta and Xie [23] analyze applications that extend the same framework.…”
Section: Mining For Variation Points and Variantsmentioning
confidence: 99%
“…The lack of approaches may be due to the wide variety of possibilities to translate a conceptual variation point (i.e. a delayed decision) to the implementation of a variation point, as well as to the difficulty to trace this translation [20,14]. Thummalapenta and Xie [23] analyze applications that extend the same framework.…”
Section: Mining For Variation Points and Variantsmentioning
confidence: 99%
“…Hence in this section, we identify the inherent characteristics of core assets based on representative works on them [1,2,[10][11][12].…”
Section: Characteristics Of Core Assetsmentioning
confidence: 99%
“…2, the boundary of variability is not independent of commonality but within commonality. Variability is a minor variation within commonality and is composed of closed and open variability [12]. A mechanism to capture variability in a product line is a decision model.…”
Section: Characteristics Of Core Assetsmentioning
confidence: 99%
“…Usually developers compare software either in an ad-hoc fashion based on practical considerations or in terms of taxonomies of software features (e.g., [1,13,16,20,24]). Often these comparison methods confound systems functionality with implementation-oriented considerations.…”
Section: Introductionmentioning
confidence: 99%