Leveraging Software Product Lines Engineering in the development of external DSLs: A systematic literature review

Abstract

The use of domain-specific languages (DSLs) has become a successful technique in the development of complex systems. Consequently, nowadays we can find a large variety of DSLs for diverse purposes. However, not all these DSLs are completely different; many of them share certain commonalities coming from similar modeling patternssuch as state machines or petri netsused for several purposes. In this scenario, the challenge for language designers is to take advantage of the commonalities existing among similar DSLs by reusing, as much as possible, formerly defined language constructs. The objective is to leverage previous engineering efforts to minimize implementation from scratch. To this end, recent research in software language engineering proposes the use of product line engineering, thus introducing the notion of language product lines. Nowadays, there are several approaches that result useful in the construction of language product lines. In this article, we report on an effort for organizing the literature on language product line engineering. More precisely, we propose a definition for the life-cycle of language product lines, and we use it to analyze the capabilities of current approaches. In addition, we provide a mapping between each approach and the technological space it supports. of the system [4]; consequently, nowadays there is a large variety of DSLs conceived for diverse purposes [5]. We can find, for example, DSLs to build graphical user interfaces [6], or to specify security policies [7]. Although each of the existing DSLs is unique and has been developed for a precise purpose, not all the existing DSLs are completely different among them. Recent research has shown the existence of DSLs providing similar language constructs [8,9]. A possible explanation to such phenomenon is the recurrent use of certain modeling patterns that, with proper adaptations, are suitable for several purposes. Consider, for instance, the case of finite state machines which have inspired many DSLs dealing with diverse problems such as the design of integrated circuits [10], performing software components composition [11], or the alignment of business processes with legislation [12]. In this context, the challenge for language designers is to take advantage of the commonalities existing among similar DSLs by reusing, as much as possible, formerly defined language constructs [13]. The objective is to leverage previous engineering efforts to minimize implementation from scratch. Ideally, the reuse process should be systematic. This requires, on one hand, to define reusable segments of language specifications that can be included in the definition of several DSLs, and on the other hand, an appropriate management of the variability introduced by the particularities of each DSL [2]. To overcome this challenge, the research community in software language engineering has proposed the use of Software Product Lines Engineering (SPLE) in the construction of DSLs [14]. Indeed, the notion of Language Product Lines Engineering (LPLE)i....

Controlled and Extensible Variability of Concrete and Abstract Syntax with Independent Language Features

“…To this effect, all models that are conform to a language defined by a set of selected features, are still valid models of a language that is based on these features and arbitrary other additional selected features. Through a systematic literature review [20] comparing different approaches for LPLs, the authors identified 14 approaches realizing LPLs, where many different concepts are involved. Some of the approaches support variability in abstract syntax only [10,23,29].…”

Concern-oriented language development (COLD): Fostering reuse in language engineering

“…A recent advance in SLE is the notion of language product lines [8,9] . In analogy with software product lines [35] , a language product line is a product line where the products are languages.…”

“…Over the last decade, the Software Language Engineering (SLE) community has proposed various reuse techniques, mostly leveraging previous experiences in software reuse (e.g., aspects [2] , polymorphic [3] and parametric [4] reuse, composition operators [5,6] , language product lines [7][8][9] ). Although these techniques address a wide range of scenarios, the development of realistic languages is still difficult as it requires to combine them.…”

Reverse engineering language product lines from existing DSL variants

“…The objective is to leverage previous engineering efforts to minimize implementation from scratch. To achieve such a challenge, the research community in software language engineering has proposed the use of Software Product Line Engineering (SPLE) in the construction of DSLs [13,14]. This led to the notion of Language Product Line Engineering (LPLE) -i.e., the construction of software product lines where the products are languages [12,15]-.…”