2014
DOI: 10.1007/s10664-014-9336-6
|View full text |Cite
|
Sign up to set email alerts
|

Quantifying structural attributes of system decompositions in 28 feature-oriented software product lines

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2014
2014
2023
2023

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 8 publications
(4 citation statements)
references
References 58 publications
0
4
0
Order By: Relevance
“…By these techniques, variability is implemented in code units provided by a host language, such as classes or functions, which do not align well with domain features. Therefore, occasionally and orthogonal to this main decomposition, some approaches are used for annotating (e.g., using preprocessors in C [37]) or putting into separate modules (e.g., with feature modules [6]) all lines of code that belong to each specific domain feature [7,53]. But, while annotations in the form of conditional compilations have received significant attention, their use is often criticized for the code pollution due to #ifdef-s [35,54] and for the occurrence of syntactic and semantic errors during the product derivation [31].…”
Section: Introductionmentioning
confidence: 99%
“…By these techniques, variability is implemented in code units provided by a host language, such as classes or functions, which do not align well with domain features. Therefore, occasionally and orthogonal to this main decomposition, some approaches are used for annotating (e.g., using preprocessors in C [37]) or putting into separate modules (e.g., with feature modules [6]) all lines of code that belong to each specific domain feature [7,53]. But, while annotations in the form of conditional compilations have received significant attention, their use is often criticized for the code pollution due to #ifdef-s [35,54] and for the occurrence of syntactic and semantic errors during the product derivation [31].…”
Section: Introductionmentioning
confidence: 99%
“…To overcome such variability management difficulties, existing approaches use annotations, often preprocessor directives [59], or have proposed to put into separate modules, for example, into aspects, feature modules, or delta modules [6], all lines of code that belong to each specific domain feature [7,83]. In addition, different tools are proposed, for example, pure::variants [36], code tagging [42], or those that propose to use colors, at the representation layer of code, for distinguishing the lines of code that implement each feature [49].…”
Section: Introductionmentioning
confidence: 99%
“…Consequently, they lack of standard terminology and formalism, leading to definitions of measures, which are ambiguous and/or difficult to understand. A growing number of studies have identified structural properties of product lines [SOBERNIG et al 2014, QUEIROZ et al 2015 and metrics for product-line [ VAN DER HOEK et al 2003, LIEBIG et al 2010, APEL and BEYER 2011 to overcome the problems aforementioned. Their common goal is the association between: (i) the quantification of characteristics governing either product lines or programming techniques, and (ii) their impact on software maintainability.…”
Section: The Role Of Feature Dependency Properties On Change Propagationmentioning
confidence: 99%
“…The Role of Feature Dependency Properties on Change Propagation 109 evolution. Sobernig and colleagues quantified structural attributes of system decomposition in 28 feature-oriented software product lines [SOBERNIG et al 2014]. They analyse how the alternative decompositions of feature orientation and object orientation compare to each other in terms of their association with observable properties of system structure (i.e., coupling and cohesion).…”
Section: Related Workmentioning
confidence: 99%