A Comparison of Mechanisms for Integrating Handwritten and Generated Code for Object-Oriented Programming Languages

Abstract

Code generation from models is a core activity in model-driven development (MDD). For complex systems it is usually impossible to generate the entire software system from models alone. Thus, MDD requires mechanisms for integrating generated and handwritten code. Applying such mechanisms without considering their effects can cause issues in projects with many model and code artifacts, where a sound integration for generated and handwritten code is necessary. We provide an overview of mechanisms for integrating generated and handwritten code for object-oriented languages. In addition to that, we define and apply criteria to compare these mechanisms. The results are intended to help MDD tool developers in choosing an appropriate integration mechanism. * K. Hölldobler is supported by the DFG GK/1298 Algo-Syn. on different properties of code integration mechanisms to assess and compare these mechanisms. The presented criteria are based on a decade of experiences in object-oriented software engineering and MDD research (Rumpe, 2011; Rumpe, 2012), code generator development and code integration research Schindler, 2012), and experiences with MDD processes within various domains including automotive , cloud computing (Navarro Pérez and Rumpe, 2013), robotics (Ringert et al., 2013), and smart buildings (Kurpick et al., 2012).We introduce eight handwritten code integration mechanisms and evaluate each with respect to our criteria. Moreover, we show strengths and weaknesses of each integration mechanism in the evaluation results. By means of this, we seek to increase the comparability between the integration mechanisms. In particular, this overview is intended to be used by MDD tool developers to find a proper integration mechanism on a case-by-case basis.Please note, that the list of integration mechanisms and evaluation criteria presented in this paper does not claim to be complete. However, if further integration mechanisms need to be compared or the mechanisms [GHK+15] T.

The Virtual Developer

“…[ Greifenberg et al 2015] present six language-based and two language-independent integration mechanisms, which the designer of transformation rules can exploit to reduce collisions. [Kelly and Tolvanen 2008] also discuss pragmatic approaches, such as protected areas, inclusion of code in models, templates, and language-or framework-specific patterns.…”