The Kiel Integrated Environment for Layout Eclipse Rich Client, or short KIELER, is a research project about enhancing the graphical model-based design of complex systems. The basic idea is to consistently employ automatic layout in all graphical components of the diagrams within the modeling environment. This opens up new possibilities for diagram editing, browsing, and dynamic visualizations (e.g. for simulation runs). Hence the focus of this project is the pragmatics of model-based system design, which can improve comprehensibility of diagrams, improve development and maintenance time, and improve the analysis of dynamic behavior.
This project is a continuation of the old KIEL project. The main differences are that KIELER aims to integrate a variety of modeling languages (not just Statecharts), and that it integrates into the rich client platform Eclipse. It attempts a tight integration with the modeling projects of Eclipse (EMF, GMF, Xtext, etc.) to bring new modeling approaches to a broad set of modeling paradigms and user communities.
KIELER is is developed as open source software, licensed under the Eclipse Public License and can thus be downloaded and used free of charge.
Being a research project, there are different people working in different areas of the project. The project is basically divided into the Layout, Pragmatics, and Semantics, but we also have a bunch of demonstrators and even a number of projects useful to end users published as part of OpenKieler:
(Note: this image is also available as a PDF file and as the original SVG file and can freely be used in theses of our students. If you are not a student at our group but want to use this image, feel free to get in touch.)
The layout area provides the foundation for pretty much everything else in KIELER. Much effort in the Pragmatics area has gone into freeing the user from so-called "enabling steps": things a developer has to do to prepare for the model change he actually wants to make. This will usually be things like moving nodes around to make space for other nodes, taking care of edge routing etc. Good layout algorithms are necessary to be able to free the user from tasks like this that don't actually contribute anything to the final model.
Our layout infrastructure and algorithms are available under the umbrella of the Eclipse Foundation as the Eclipse Layout Kernel (ELK) project.
Learn more about layout
With the term 'pragmatics' (don't confuse it with 'pragmatism') we denote the set of all practical aspects that influences the daily work of modelers in the context of Model-Driven Engineering (MDE). This comprises the creation and modification of models (abstract syntax as in the sense of the MVC) as well as the synthesis of diverse views on those models tailored to different stakeholders and different purposes.
Exemplary projects addressing these topics are the KIELER Structure-based Editing (KSbasE) and the KIELER Lightweight Diagrams (KLighD). The first one aims at providing operations for changing models based on its abstract syntax (introduce new elements, modify them in some way, connect them, or delete them). The second one targets the synthesis of graphical representations of models or model excerpts in a lightweight and transient way. This means, representations are synthesized on the modeler's demand and dismissed later on without saving them on the disk, unless the modeler wants to do that. Both techniques are enabled by the ability of automatically arranging diagram elements as provided by our layout corner.
Learn more about pragmatics
We also provide an infrastructure to define execution semantics for a meta model. This can be a simulator based on C (see S/SC projects) or Ptolemy (see KlePto project). Simulators can easily be integrated using the KIELER Execution Manager (KIEM). We also support textual simulations (see Esterel and S project). Another recent main contribution are SCCharts. To get an overview about all projects concerning semantics in KIELER follow the link below.
Learn more about semantics
Since this is a research project, we cannot provide support for all subprojects forever. Those that are no longer considered in active development and future releases are listed on the discontinued projects page. We have still some archived documentation for these old subprojects: