Citation Context

...xcludes a feature B, both features cannot be part of the same product. GPS and basic screen are incompatible features. More complex cross-tree relationships have been proposed later in the literature =-=[5]-=- allowing constraints in the form of generic propositional formulas, e.g. “A and B implies not C”. 2.2. Cardinality–based feature models Some authors propose extending FODA feature models with UML-lik...

Citation Context

...otated and therefore IPCs are assumed. The result of removal analysis and patch application is shown in Figure 8(a). Based on our configuration, the instantiation algorithm removes four regions: blue =-=(3)-=- for QuickCheckoutProfile, green (2) for Guest checkout, magenta (4) for InventoryTracking, and pink (5) for PhysicalGoods. Note that they are all closeable and will be closed before removal. In the c...

Citation Context

... the requirements the feature satisfies, W the assumptions the feature takes about its environment and S its specification” 8. Zave [129]: “an optional or incremental unit of functionality” 9. Batory =-=[24]-=-: “an increment of program functionality” 10. Apel et al. [21]: “a structure that extends and modifies the structure of a given program in order to satisfy a stakeholder’s requirement, to implement an...

Citation Context

...ild must be selected, and in Alternative-groups, exactly one child is selected. A feature model may also have constraints, called crosstree constraints, that cannot be easily expressed hierarchically =-=[12, 3, 7]-=-. Cross-tree constraints can be arbitrary propositional formulas and may be written below a feature diagram as in Figure 1. Our notation is based on guidsl [3]. As in [3], a terminal or concrete featu...

Citation Context

...cations in reverse engineering and refactoring of feature models. 1 Introduction Feature modeling is a family of notations and an approach for modeling commonality and variability in product families =-=[15, 11, 4]-=-. In their basic form, feature models contain mandatory/optional features, feature groups, and implies and excludes relationships [12]. As shown by Batory [4], such feature models can be translated in...

Citation Context

...TRODUCTION A feature is an increment in program functionality [27]. It is a central abstraction in work on software product lines [4][10] (where each program of a product-line is differentiated from other programs by the set of features it has) and feature interactions (how features influence each other) [7][23][27]. Features are important because they are reusable with in a product-line and can be used to specify program variants declaratively — much like specifying PC configurations declaratively by selecting features via web-interfaces, customers want to do the same for specifying programs [6][10]. Concomitantly, program evolution can be described in a high-level and easy-to-understand way as the process of adding and removing features. Giving applications a feature-based design facilitates such extensibility. Designing an application from the groundup using features is one approach [5]; an alternative is to refactor a legacy application. This paper is about the latter. Feature oriented refactoring (FOR) is the process of decomposing a program into features. The challenge of FOR is two-fold. First, feature implementations often do not translate cleanly into traditional software mod...

Citation Context

...nipulate feature models has attracted the attention of researchers in the field [6]. An important step in this context was the provision of rules for translating feature models to propositional logic =-=[7, 18]-=-, which has opened many interesting research opportunities in the use of logic-based systems to reason on feature models, including off-the-shelf technology such as satisfiability solvers. Table 1 sho...