On the Realization of Meta-Circular Code Generation: the Case of the Normalized Systems Expanders

On the Realization of Meta-Circular Code Generation: the Case of the Normalized Systems Expanders

ICSEA 2019 : The Fourteenth International Conference on Software Engineering Advances On the Realization of Meta-Circular Code Generation: The Case of the Normalized Systems Expanders Herwig Mannaert Koen De Cock and Peter Uhnak Normalized Systems Institute Research and Development University of Antwerp, Belgium NSX BVBA, Belgium Email: [email protected] Email: [email protected] Abstract—The automated generation of source code is a widely II. AUTOMATIC AND HOMOICONIC PROGRAMMING adopted technique to improve the productivity of computer In this section, we briefly discuss two fundamental and programming. Normalized Systems Theory (NST) aims to create software systems exhibiting a proven degree of evolvability. A long-standing approaches to increase the programming pro- software implementation exists to create skeletons of Normalized ductivity: automatic and homoiconic programming. Systems (NS) applications, based on automatic code generation. This paper describes how the NS model representation, and the A. Automatic or Meta-Programming corresponding code generation, has been made meta-circular, a The automatic generation of code is nearly as old as feature that may be crucial to improve the productivity of the coding or software programming itself. One often makes a development of software for source code generation. The detailed distinction between code generation, the mechanism where a architecture of this meta-circular code generation software is presented, and some preliminary results are discussed. compiler generates executable code from a traditional high- level programming language, and automatic programming, the Keywords–Evolvability; Normalized Systems; Meta-circularity; Automated programming; Case Study act of automatically generating source code from a model or template. In fact, one could argue that both mechanisms are quite similar, as David Parnas already concluded in 1985 I. INTRODUCTION that ”automatic programming has always been a euphemism Increasing the productivity in computer programming has for programming in a higher-level language than was then been an important and long-term goal of computer science. available to the programmer” [2]. Though many different approaches have been proposed, dis- cussed, and debated, two of the most fundamental approaches Another term used to designate automatic programming toward this goal are arguably automated code generation is generative programming, aiming to write programs ”to and homoiconic programming. Increasing the evolvability of manufacture software components in an automated way” [3], Information Systems (IS) on the other hand, is crucial for the in the same way as automation in the industrial revolution productivity during the maintenance of information systems. has improved the production of traditional artifacts. As this Although it is even considered as an important attribute de- basically corresponds to an activity at the meta-level, i.e., termining the survival chances of organizations, it has not yet writing software programs that write software programs, this received much attention within the IS research area [1]. Nor- is also referred to as meta-programming. Essentially, the goal malized Systems Theory (NST) was proposed to provide an ex- of automatic programming is and has always been to improve ante proven approach to build evolvable software by leveraging programmer productivity. concepts from systems theory and statistical thermodynamics. Software development methodologies such as Model- In this paper, we present an integrated approach that combines Driven Engineering (MDE) and Model-Driven Architecture both Normalized Systems theory to provide evolvability, and (MDA), focusing on creating and exploiting conceptual domain automated code generation and homoiconic programming to models and ontologies, are also closely related to automatic offer increased productivity. programming. In order to come to full fruition, these method- The remainder of this paper is structured as follows. In ologies require the availability of tools for the automatic gen- Section III, we briefly discuss two fundamental approaches eration of code. Currently, these model-driven code generation to increase the productivity in computer programming: auto- tools are often referred to as Low-Code Development Platforms matic and homoiconic programming. In Section III, we briefly (LCDP), i.e., software that provides an environment for pro- present NST as a theoretical basis to obtain higher levels of grammers to create application software through graphical user evolvability in information systems. Section IV discusses the interfaces and configuration instead of traditional computer application of these fundamental concepts to the Normalized programming. As before, the goal remains to increase the Systems code expansion in general and the Prime Radiant in productivity of computer programming, though the realization particular. Section V elaborates on the declaration of both of this goal is not always straightforward [4]. the various expanders generating the code artifacts, and the configuration parameters that control the expansion process. B. Homoiconicity or Meta-Circularity Finally, we discuss some results in Section VI and present our Another technique in computer science aimed at the in- conclusion in Section VII. crease of the abstraction level, and thereby the productivity, Copyright (c) IARIA, 2019. ISBN: 978-1-61208-752-8 171 ICSEA 2019 : The Fourteenth International Conference on Software Engineering Advances of computer programming, is homoiconicity. A language is by manual programming. Therefore, the theory also proposes a homoiconic if a program written in it can be manipulated set of patterns to generate significant parts of software systems as data using the language, and thus the program’s internal which comply with these theorems. More specifically, NST representation can be inferred just by reading the program proposes five elements that serve as design patterns [9][10]: itself. As the primary representation of programs is also a data • data element structure in a primitive type of the language itself, reflection in the language depends on a single, homogeneous structure • action element instead of several different structures. It is this language feature • workflow element that conceptually enables meta-programming to become much • connector element easier. The best known example of an homoiconic program- ming language is Lisp, but all Von Neumann architecture • trigger element systems can implicitly be described as homoiconic. An early Based on these elements, NST software is generated in a and influential paper describing the design of the homoiconic relatively straightforward way. First, a model of the considered language TRAC [5], traces the fundamental concepts back to universe of discussion is defined in terms of a set of data, task an even earlier paper from McIlroy [6]. and workflow elements. Next, code generation or automated Related to homoiconicity is the concept of a meta-circular programming is used to generate parameterized copies of evaluator (MCE) or meta-circular interpreter (MCI), a term the general element design patterns into boiler plate source that was first coined by Reynolds [7]. Such a meta-circular code. Due to the simple and deterministic nature of this code interpreter, most prominent in the context of Lisp as well, is generation mechanism, i.e., instantiating parametrized copies, an interpreter which defines each feature of the interpreted it is referred to as NS expansion and the generators creating language using a similar facility of the interpreter’s host the individual coding artifacts are called NS expanders. This language. The term meta-circular clearly expresses that there generated code can, in general, be complemented with custom is a connection or feedback loop between the activity at code or craftings to add non-standard functionality that is not meta-level, the internal model of the language, and the actual provided by the expanders themselves, at well specified places activity, writing models in the language. (anchors) within the boiler plate code. III. NORMALIZED SYSTEMS THEORY AND EXPANSION B. Variability Dimensions and Expansion In this section, we introduce NST as a theoretical basis to In applications generated by a Normalized Systems expan- obtain higher levels of evolvability in information systems, and sion process, we identify four variability dimensions, as visu- its realization in a code generation or expansion framework. alized in Figure 1. As discussed in [11][12], the combination of these dimensions compose an actual Normalized Systems A. Evolvability and Normalized Systems application codebase, and therefore determine how such an The evolvability of information systems (IS) is considered application can evolve throughout time, i.e., how software as an important attribute determining the survival chances of created in this way exhibits evolvability. organizations, although it has not yet received much attention First, as represented at the upper left of the figure, one within the IS research area [1]. Normalized Systems Theory should specify or select the models or mirrors he or she wants (NST), theoretically founded on the concept of stability from to expand. Such a model is technology agnostic (i.e., defined systems theory, was proposed to provide an ex-ante proven without any reference to a particular technology that should approach to build evolvable software [8][9][10]. Systems the-

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    6 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us