Extracting and Evolving Code in Product Lines with Aspect-Oriented Programming

Abstract

Abstract. For some organizations, the proactive approach to product lines may be inadequate due to prohibitively high investment and risks. As an alternative, the extractive and the reactive approaches are incremental, offering moderate costs and risks, and therefore sometimes may be more appropriate. However, combining these two approaches demands a more detailed process at the implementation level. This paper presents a method and a tool for extracting a product line and evolving it, relying on a strategy that uses refactorings expressed in terms of simpler programming laws. The approach is evaluated with a case study in the domain of games for mobile devices, where variations are handled with aspect-oriented constructs.

Taming Dynamically Adaptive Systems using models and aspects

“…Automatic runtime adaptations are attained by using the knowledge documented in variability models. As many authors [1,2,22] advocate that aspect-oriented software development (AOSD) is an effective technique to support feature variability, this approach is close to ours. Automatic runtime adaptations are attained by using the knowledge documented in variability models.…”

“…Then, we automatically analyse both diff and match models to obtain the relevant changes between the source model and the target model e.g., addition/removal of components/bindings, changes of attribute 1 See http://www.eclipse.org/modeling/emft/ values, etc. However, it is not possible to adapt the running system during this analysis.…”

Safe evolution templates for software product lines

“…Essentially, this product line uses aspects as a variability implementation mechanism (Alves et al, 2007;Gacek & Anastasopoules, 2001). In particular, the AppMenu aspect, due to usability issues, should not be present in products that have only one of the Media features, which is what the fifth row specifies.…”

“…It is also bidirectional, given that we observe the restrictions. Finally, Extract preprocessed code is useful for situations where we want to change a feature variation implementation, for example when we want to extract the feature code annotated with preprocessing directives to an aspect (Alves et al, 2007) or to a super class. The template defines that it is possible to extract a code fragment annotated with preprocessing directives from an asset and place it in another new asset, as long as the set of modified assets refines the original asset.…”

Porting mobile games in an aspect-oriented way: An industrial case study

“…By localizing porting-related features in code aspects, not only a modular separation of concern is devised, but the software development of mobile games can also be incrementally transitioned to product line engineering where orders of magnitude improvements in productivity and timeto-market are expected [6].…”