A Framework for Integrating ESL Tools - IRIT

In our framework, a domain specific model (DSM) for business logic is used
to provide a compact and clear interface between modeling languages and code
generators. Based on the analysis of visual modeling languages for behavioral
aspects of systems, we designed this domain specific model for business logic to
support all relevant modeling concepts needed for business logic code generation
of information systems. After the discussion of related work in Sect. 2, we analyse
several visual modeling languages for systems behavior in Sect. 3 before we
define a domain specific model for business logic in Sect. 4. Then, we give a
brief overview of the usage of the business logic DSM as part of a framework in
Section 5 and conclude in Section 6.
2 Related Work
In general, we follow Waddington et al. who states in [17] that „multiple modeling
notations and interpretations (views) are necessary to represent each of the
different aspects of concern and to fulfill different roles within MCSD [Model-
Centric Software Development] such as verification of correctness, human understanding
through visual interpretation, and code generation”. In tool chains
and frameworks for embedded systems (such as provided by Konrad et al. [8],
) structural aspects are integrated with scenario models or state chart models
or both, which are commonly applied behavioral modeling concepts for reactive
systems. Ryndina et al. connected process and state modeling in [13] through
generation of object live cycles based on process models, but they do not focus
on an abstract model providing an integrated view. Gerth et al. provide in
[4] a so-called “intermediate representation (IR)” of process models as abstract
representation of process models and applied it for model change management
purposes. However, this approach do not consider structural or state modeling
concepts. Mohan et al. provides with their FlexFlow model in [9] an integration
of structural and state modeling, but they do not consider process modeling
aspects. However, for business logic generation for information systems we need
integrated model supporting process modeling (containing all actions and control
flow specification), structural modeling (containing all business objects that
are relevant during process execution) and state modeling (containing domain
states of business objects and object live cycles).
In context of modeling systems behavior there are several approaches that
transform visual behavior diagrams into special purpose languages. One purpose
for such transformation is to get a formal-founded structure for automated model
quality assurance. Target models are for example process algebras (e.g. Engels et
al. in [3]) or Petri nets variants (as discussed by Stains in [15]) which are suitable
for automated reasoning or simulation. However, the high level of abstraction
of formal models makes them difficult to handle them as technical interfaces
for business logic code generators. Otherwise, in case of using domain specific
behavioral models for code generation, they are designed for proprietary tool
chains (such as FlexFlow [9] or J3 [18]) or specific target platforms (such as BPEL
in [7], or Embedded Systems e.g. in [8]). As a difference to related approaches,
24