What is the drawback of markups and escapes?

A notable drawback of both markups and escapes is that they mix levels of abstraction by directly placing lower-level customizations at a higher level.

What is the main idea of a model-driven software development?

This idea is at odds with the intuitive principle that “easy things should be easy to do and progressively more complex tasks should only get progressively harder to do, not insurmountably harder.”2 Model-driven software development [MDSD, Greenfield04] has the potential to eliminate the customization cliff in traditional, code-centric implementations of SPLs by offering multi-level modeling and customization as a middle ground between configuration and custom coding, as shown in the right part of Figure 1.

What are some other techniques that can be used to separate customization from generated elements?

Such API-centric techniques include subclassing generated classes, invoking generated elements by customized elements or vice versa, and using C#’s partial classes [Greenfield04].

What is the common way of generating and changing a model?

Both generation and change propagation are achieved using the discussed feature-to-model mappings, as well as model-to-model and model-to-code mappings, which are studied extensively in the field of model transformation (see [Czarnecki06a] for a survey on this topic).

Open AccessJournal Article10.1145/1183236.1183267

Multi-level customization in application engineering

Krzysztof Czarnecki, +2 more

- 01 Dec 2006

- Communications of The ACM

- Vol. 49, Iss: 12, pp 60-65

TL;DR: Developing mechanisms for mapping features to analysis models and investigating how these mechanisms can be tuned to improve the quality of analysis models.

Abstract: The goal of software product lines (SPLs) is to improve productivity, time to market, and the quality of application development by leveraging the commonalities of systems within an application domain while managing their variations. These commonalities and variations may be packaged into a domain-specific platform (DSP), which supports application development through configuration settings or code extensions. Examples of large, vendor-provided DSPs are IBM's WebSphere Commerce for e-commerce applications and SAP's R/3 for enterprise resource management systems. The main advantage of creating a DSP is that its planned variability allows for a common product line architecture while its domain focus allows for components that are functionality-rich.

AI Agents for this Paper

Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps

Most frequently asked questions

1. What are the contributions mentioned in the paper "Multi-level customization in application engineering" ?

In this paper, Cook et al. discuss the customization cliff of software product lines ( SPL ) and propose a middle ground between configuration and custom coding.

2. What are the future works mentioned in the paper "Multi-level customization in application engineering" ?

Although a larger example in the context of a realistic e-commerce DSP within their group demonstrated the scalability of feature-based model templates [ Lau06 ], realizing the vision of multi-level customization from features to models to code remains a future work item that boasts many challenges.

3. What are some of the features that can be configured?

Feature configuration process may be guided through constraint-based facilities, such as consistency checking, choice propagation, and auto-completion [Batory05, Czarnecki05b].

4. What is the main advantage of creating a DSP?

The main advantage of creating a DSP is that its planned variability allows for a common product line architecture while its domain focus allows for domain-specific components that are functionality-rich.

Table 1 Classification of Customization Approaches

Figure 2: Multi-level representation and customization of an e-commerce system

Figure 1: The customization cliff – problem and solution

Citations

•Proceedings Article•10.1145/1363686.1363840

Configuring features with stakeholder goals

Yijun Yu, +3 more

- 16 Mar 2008

TL;DR: A new model-driven extension to an Early Requirements Engineering tool (OpenOME) is presented that generates an initial feature model of the system-to-be from stakeholder goals, enabling generative mapping and configuration constraints among variability features.

...read moreread less

Proceedings Article•10.1109/SPLC.2011.25

Product Line Engineering Using Domain-Specific Languages

Markus Voelter, +1 more

- 22 Aug 2011

TL;DR: This paper investigates the application of domain-specific languages in product line engineering (PLE) by analyzing the limits of expressivity of feature models and showing how domain- specific languages (DSLs) can serve as a middle ground between feature modeling and programming.

...read moreread less

Proceedings Article•10.1145/1985394.1985397

Engineering multi-tenant software-as-a-service systems

Bikram Sengupta, +1 more

- 23 May 2011

TL;DR: A set of research issues in the design, testing and maintenance of multi-tenant SaaS systems are outlined, and some of the interesting optimization questions that arise in the process are highlighted.

...read moreread less

•Journal Article

Automatic generation of program families by model restrictions

Andrzej Wasowski

- 01 Jan 2004

- Lecture Notes in Computer Science

TL;DR: An application of the process of modeling reactive systems with statecharts is described, establishing a trace inclusion refinement relation for automatically generated family members, inducing a behavioral inheritance hierarchy over the generated programs.

...read moreread less

•Book Chapter•10.1007/978-3-540-76811-1_9

Mapping features to aspects: a model-based generative approach

Uirá Kulesza, +6 more

- 13 Mar 2007

TL;DR: A model-based generative approach to mapping features to aspects across different artifacts of a product line and is complementary to a set of previously-proposed modularization guidelines to implement aspect-oriented frameworks.

...read moreread less

...

Expand

References

Report•10.21236/ADA235785

Feature-Oriented Domain Analysis (FODA) Feasibility Study

Kyo C. Kang, +4 more

- 01 Nov 1990

TL;DR: This report will establish methods for performing a domain analysis and describe the products of the domain analysis process to illustrate the application of domain analysis to a representative class of software systems.

...read moreread less

4.7K

Journal Article•10.21236/ada235785

Feature-Oriented Domain Analysis (FODA) Feasibility Study

K. Kang, +4 more

- 01 Nov 1990

TL;DR: This report will establish methods for performing a domain analysis and describe the products of the domain analysis process, and provide a domain analysis of window management system software.

...read moreread less

1.6K

Book Chapter•10.1007/11554844_3

Feature models, grammars, and propositional formulas

Don Batory

- 26 Sep 2005

TL;DR: This work integrates prior results to connect feature models, grammars, and propositional formulas, which allows arbitrary propositional constraints to be defined among features and enables off-the-shelf satisfiability solvers to debug feature models.

...read moreread less

1.3K

Journal Article•10.1147/SJ.453.0621

Feature-based survey of model transformation approaches

Krzysztof Czarnecki, +1 more

- 01 Jul 2006

- Ibm Systems Journal

TL;DR: A framework for the classification of several existing and proposed model transformation approaches is proposed, given as a feature model that makes explicit the different design choices for model transformations.

...read moreread less

1.2K

•Book

Model-Driven Software Development: Technology, Engineering, Management

Thomas Stahl, +2 more

- 19 May 2006

TL;DR: MDSD Tools: Roles, Architecture, SelectionCriteria, Selection Criteria, and Pointers, and MDSD Process Building Blocks and Best Practices.

...read moreread less

...

Expand

Multi-level customization in application engineering

Chat with Paper

AI Agents for this Paper

Most frequently asked questions

1. What are the contributions mentioned in the paper "Multi-level customization in application engineering" ?

2. What are the future works mentioned in the paper "Multi-level customization in application engineering" ?

3. What are some of the features that can be configured?

4. What is the main advantage of creating a DSP?

5. What are examples of large, vendor-provided DSPs?

6. What is the drawback of markups and escapes?

7. What is the main idea of a model-driven software development?

8. What are some other techniques that can be used to separate customization from generated elements?

9. What is the common way of generating and changing a model?

Figures

Citations

Configuring features with stakeholder goals

Product Line Engineering Using Domain-Specific Languages

Engineering multi-tenant software-as-a-service systems

Automatic generation of program families by model restrictions

Mapping features to aspects: a model-based generative approach

References

Feature-Oriented Domain Analysis (FODA) Feasibility Study

Feature-Oriented Domain Analysis (FODA) Feasibility Study

Feature models, grammars, and propositional formulas

Feature-based survey of model transformation approaches

Model-Driven Software Development: Technology, Engineering, Management

Related Papers (5)

Feature-Oriented Domain Analysis (FODA) Feasibility Study

Software Product Lines: Practices and Patterns

Software Product Line Engineering: Foundations, Principles and Techniques

Generative Programming: Methods, Tools, and Applications

Staged Configuration Using Feature Models