Migrating business logic to an incremental computing DSL: a case study

Abstract

To provide empirical evidence to what extent migration of business logic to an incremental computing language (ICL) is useful, we report on a case study on a learning management system. Our contribution is to analyze a real-life project, how migrating business logic to an ICL affects information system validatability, performance, and development effort.We find that the migrated code has better validatability; it is straightforward to establish that a program 'does the right thing'. Moreover, the performance is better than the previous hand-written incremental computing solution. The effort spent on modeling business logic is reduced, but integrating that logic in the application and tuning performance takes considerable effort. Thus, the ICL separates the concerns of business logic and performance, but does not reduce effort.CCS Concepts • Information systems → Web applications; Enterprise information systems; • Software and its engineering → Domain specific languages;

OIL: an industrial case study in language engineering with Spoofax

“…There are three types of areas: regions, states and zones (lines [14][15][16][17][18][19][20][21][22][23][24][25][26][27][28][29][30][31][32][33]. A region always refers to an enum variable and contains a number of states.…”

“…15 An SDF3 code snippet of the grammar of transitions in OILDSL Fig. 16 An example transition in OILXML and OILDSL with the corresponding ASTs Fig. 17 A (simplified) import graph of IDL's and OIL's expression grammars, that depicts how modules are reused.…”

“…From this it can be derived that it should be more productive to implement a DSL with Spoofax compared to when not using a language workbench. Although it has been demonstrated that Spoofax is able to deliver on its original promises for non-industrial greenfield situations, e.g., in the area of web programming [13,14], or declarative data modeling [15,16], it is unclear to what extent the original claims of Spoofax still hold for our industrial case. This leads to the following research question: RQ: How does the productivity of implementing an industrial language in Spoofax compare to the productivity when using a GPL and available libraries?…”

Evolution of the WebDSL runtime: reliability engineering of the WebDSL web programming language

“…This led to all student transactions being in conflict, because they were trying to update the same row storing the average grade in the database. The problem of describing derived values concisely and deriving a robust evaluation was inspiration for the IceDust language [9,10].…”