Building distributed web applications based on model versioning with CoObRa: An experience report

Abstract

Originally, model versioning has been developed to enable teams of developers to work on common model data, concurrently. We have the idea to use the same techniques to facilitate the collaboration of collaboration applications. Multi threaded applications share a common main memory. Thus, all threads have access to the full data structures and each thread may query and update the data structures, concurrently, in order to fulfill its tasks. In distributed applications, each distributed process has access only to its own share of the data model. In order to query and update remote data structure parts, the process has to send an appropriate request to the process, that owns that data. Transferring complex data structures, e.g. as query result, from one process to the other requires tedious data serialization and deserialization mechanisms. To overcome these problems, this paper proposes to replicate model data for each process and to use model versioning techniques to synchronize the different model data replicas. We have built a web based workflow editor and a web based version of a Ludo game to validate this idea. This paper reports about our experiences with the data replication approach and our experiences in using it for web applications.

Developing Enterprise Web Applications Using the Story Driven Modeling Approach

“…This results in the need of having the class diagrams of the data model in the WFUP process, too. Having special annotations and interfaces in the application data model will enable the use of the WebCoobra Framework [1] for the data model. This gives us support for automatic replication of data between the server and multiple clients, enabling the system to keep consistency.…”

“…Also we tried to support the process with tool integration of the new requirements. We propose the use of the Google Web Toolkit (GWT) 1 as user interface and client side logic library. GWT automatically generates browser specific JavaScript code from Java Code.…”

Using Actions Charts for Reactive Web Application Modeling

“…At runtime, the model is instantiated on both sides of the application and is synchronized, even between multiple clients and the server, using the WebCoObRA features introduced in [1]. This holds for the application data model which is generated out of the class diagram and its associated story diagrams.…”