FeatureCoPP: compositional annotations

Krüger, Jacob; Schröter, Ivonne; Kenner, Andy; Kruczek, Christopher; Leich, Thomas

doi:10.1145/3001867.3001876

Cited by 13 publications

(27 citation statements)

References 30 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This section discusses and compares our approach to the pure composition and annotation-based approaches and to the most relevant integrated approaches [28,35]. We partly base the discussion on the quality criteria for SPL implementation techniques defined in [2] (feature traceability, separation of concerns, information hiding, granularity, uniformity, and preplanning effort) but from a different point of view, that is, the architectural level where CVL works.…”

Section: Discussionmentioning

confidence: 99%

“…All these approaches [11,29,31,34,35] are useful in the scenarios of refactoring annotated SPL in order to utilize, or to migrate toward, composition; and to adopt SPLs from legacy systems (the extractive approach) [2]. In particular, Benduhn et al [11] apply the integration approach proposed by Kästner and Apel [28] in a real case study, by migrating Berkeley DB from C preprocessors annotations toward partial composition.…”

Section: Related Workmentioning

confidence: 99%

“…Existing approaches, both compositional and annotative approaches, as well as the combined approaches do not completely fulfill the requirements of web engineering [11,28,35].…”

Section: Limitations Of Existing Approachesmentioning

confidence: 99%

“…This is the case of the generic combination approach [28], that depends on the actual composition and annotation-based approaches used. Besides that, introducing composition into an annotation-based approach, like in FeatureCoPP [35], suffers the same problem regarding the poor quality of the generated code, modified with artificial methods created only to handle variability. Moreover, how well traceability and separation of concerns is achieved depends on the implemented solution and not on the approach itself (e.g., FOP).…”

Section: Limitations Of Existing Approachesmentioning

confidence: 99%

See 3 more Smart Citations

Integrating the common variability language with multilanguage annotations for web engineering

Horcas

Cortiñas

Fuentes

et al. 2018

Proceedings of the 22nd International Systems and Software Product Line Conference - Volume 1

View full text Add to dashboard Cite

Web applications development involves managing a high diversity of files and resources like code, pages or style sheets, implemented in different languages. To deal with the automatic generation of custom-made configurations of web applications, industry usually adopts annotation-based approaches even though the majority of studies encourage the use of composition-based approaches to implement Software Product Lines. Recent work tries to combine both approaches to get the complementary benefits. However, technological companies are reticent to adopt new development paradigms such as feature-oriented programming or aspect-oriented programming. Moreover, it is extremely difficult, or even impossible, to apply these programming models to web applications, mainly because of their multilingual nature, since their development involves multiple types of source code (Java, Groovy, JavaScript), templates (HTML, Markdown, XML), style sheet files (CSS and its variants, such as SCSS), and other files (JSON, YML, shell scripts). We propose to use the Common Variability Language as a composition-based approach and integrate annotations to manage fine grained variability of a Software Product Line for web applications. In this paper, we (i) show that existing composition and annotation-based approaches, including some well-known combinations, are not appropriate to model and implement the variability of web applications; and (ii) present a combined approach that effectively integrates annotations into a composition-based approach for web applications. We implement our approach and show its applicability with an industrial real-world system.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

“…Existing approaches, both compositional and annotative approaches, as well as the combined approaches do not completely fulfill the requirements of web engineering [11,28,35].…”

Section: Limitations Of Existing Approachesmentioning

confidence: 99%

Section: Limitations Of Existing Approachesmentioning

confidence: 99%

See 2 more Smart Citations

Integrating the common variability language with multilanguage annotations for web engineering

Horcas

Cortiñas

Fuentes

et al. 2018

Proceedings of the 22nd International Systems and Software Product Line Conference - Volume 1

View full text Add to dashboard Cite

show abstract

“…One of the main advantages of composition‐based approaches is the physical separation of features. This facilitates traceability and maintenance but also poses new challenges. For example, analysing and testing become more challenging, due to the complexity and separation of code .…”

Section: Introductionmentioning

confidence: 99%

Mutation operators for feature‐oriented software product lines

Krüger

Al-Hajjaji

Leich

et al. 2018

Software Testing Verif & Rel

Self Cite

View full text Add to dashboard Cite

Summary Mutation testing is an approach to assess the quality of test cases. Mutants are modified versions of a system that ideally compose faulty behaviour. Test cases for a system are effective if they kill these mutants. For software product lines, several works have addressed mutation testing to inject variability faults, which may only exist in some variants. These works focus on variability models or specific implementation techniques. In contrast, feature‐oriented programming has been rarely investigated, wherefore, we (1) derive corresponding mutation operators, (2) investigate the feasibility of our proposed and conventional operators on 4 software product lines, and (3) discuss open challenges in mutation testing of software product lines. The results show that our proposed operators are suitable to cause variability faults and extend the capabilities of conventional operators. Nonetheless, mutation testing of software product lines is comparably expensive, due to a high number of variants and mutants—resulting in equivalence and redundancy.

show abstract

Composing annotations without regret? Practical experiences using FeatureC

Krüger

Pinnecke

Kenner³

et al. 2017

Softw Pract Exp

Self Cite

View full text Add to dashboard Cite

Software product lines enable developers to derive similar products from a common code base. Existing implementation techniques can be categorized as composition-based and annotation-based approaches, with both approaches promising complementary benefits. However, annotation-based approaches are commonly used in practice despite composition allowing physical separation of features and, thus, improving traceability and maintenance. A main hindrance to migrate annotated systems toward a composition-based product line is the challenging and time-consuming transformation task. For a company, it is difficult to predict the corresponding costs, and a successful outcome is uncertain. To overcome such problems, a solution proposed by the previous work is to use a hybrid approach, utilizing composition and annotation simultaneously. Based on this idea, we introduce a stepwise migration process from annotation-based toward composition-based approaches to lower the adoption barrier of composition. This process itself is independent of used implementation techniques and enables developers to incrementally migrate toward composition. We support our approach with detailed examples by partially migrating a real-world system.In detail, we describe the following: (1) our migration process, (2) its application on a real-world system, and (3) discuss practical challenges we face. We implemented the proposed approach and show that appropriate tool support helps to migrate toward composition-based product lines. Based on the case study, we show that the hybrid product lines work correctly and can compete with the performance of the original annotated system. However, the results also illustrate open issues that have to be solved to apply such migrations in practice.

show abstract

FeatureCoPP: compositional annotations

Cited by 13 publications

References 30 publications

Integrating the common variability language with multilanguage annotations for web engineering

Integrating the common variability language with multilanguage annotations for web engineering

Mutation operators for feature‐oriented software product lines

Composing annotations without regret? Practical experiences using FeatureC

Contact Info

Product

Resources

About