Model Driven Engineering 

Schedule


  Grading Scheme

Micro theory exam written 10%
Assignments 10% per assignment 50%
Project reading part (7% on report, 3% on presentation) 10%
Project project part (10% on report, 10% on work, 10% on presentation) 30%

Note that you need to pass (i.e., obtain a score of at least 50%) all parts of the course to pass. If not, your grade will be "AFW" - absent. If you do attend/submit every part, you still need an overall score of 50% to pass the course. Additionally, if for at least one part your score is strictly below 40%, your overall grade will be min(7, your_score). your_score is the score you would get when applying the weights given above.

For the supplemental exam period, partial exemptions for specific parts of the course may be given. This is discussed individually.


A project typically contains a "reading" part and a "building" part. The first part describes (in a report and a presentation) what you found in the literature and/or by trying/evaluating existing tools. The second part will describe your own (prototype) development/implementation (possibly using MDE tools). The whole project will be due during the January 2016 exam period. A date will be fixed for the project presentations to be attended by all (and evaluated by all). The "reading" presentations will be held during the last lecture slot of the semester. After around mid November, there will be no more formal lectures, but rather individual meetings to discuss project progress. Those individual meetings (by appointment, made via e-mail) will actually start the moment project topics have been chosen.

The micro theory exam will cover the highlighted papers below. It is intended to refresh your knowledge of the topics covered in the theory lectures.

  Lectures and References

Blackboard scribbles [pdf].

Domain-Specific Modelling Languages: the need for Modelling Language Engineering
Presentation [pdf]. This presentation covers Domain-Specific Modelling (DSM) and Meta-Modelling (and some more not covered in class).

Modelling Languages: Meta-Modelling (Abstract Syntax)
Thomas Kühne. Matters of (Meta-) Modeling. Software and System Modeling 5(4): 369-385. 2006. [pdf].
Linguistic Conformance Check (as implemented in the Modelverse).
Colin Atkinson and Thomas Kühne. Rearchitecting the UML infrastructure. ACM Transactions on Modeling and Computer Simulation (TOMACS). Volume 12, Issue 4. pp 290 - 321. October 2002. [pdf].
Jean-Marie Favre. Megamodelling and Etymology. Proceedings of Dagstuhl Seminar 05161 - Transformation Techniques in Software Engineering. 2006. [pdf].
Jonathan Sprinkle, Bernhard Rumpe, Hans Vangheluwe, and Gabor Karsai. Metamodelling: State of the Art and Research Challenges. In Model-Based Engineering of Embedded Real-Time Systems. Volume 6100 of Lecture Notes in Computer Science, chapter 3, pages 57-76. Springer 2011. [pdf].

Modelling Languages: Concrete Visual Syntax
Presentation [pdf].
G. Costagliola, A. Delucia, S. Orefice and G. Polese. A Classification Framework to Support the Design of Visual Languages, Journal of Visual Languages and Computing, Volume 13, Issue 6, December 2002, pages 573-600. [pdf].
Daniel L. Moody. The "Physics" of Notations: Toward a Scientific Basis for Constructing Visual Notations in Software Engineering. IEEE Transactions on Software Engineering, vol. 35, no. 6, pp. 756-779, November/December, 2009. [pdf].

Modelling Languages: Semantics
Presentation [pdf].
David Harel, Bernhard Rumpe. Meaningful Modeling: What's the Semantics of "Semantics"?, IEEE Computer, vol. 37, no. 10, pp. 64-72, October, 2004. [pdf].
David Harel, Bernhard Rumpe. Syntax, Semantics, and all that stuff (the original technical report on which the IEEE Computer paper is based).
Hans Vangheluwe and Juan de Lara. Computer Automated Multi-Paradigm Modelling for Analysis and Design of Traffic Networks. Winter Simulation Conference 2004, pages 249-258. [pdf].

Model Transformation
Model Transformation. Presentation [pdf].

Putting it all together: the FTG+PM
Formalism Transformation Graph and Process Model. Presentation [pdf].

  Tools

metaDepth, a framework for multi-level meta-modelling

A Tool for Multi-formalism and Meta-Modelling: AToM3.
Tutorials [basic] and [slightly more advanced] on meta-modelling with AToM3.
Use Juan de Lara's in-depth AToM3 programming tutorial: the AToM3 Python API for details about AToM3's internal representation of models, about constraints and actions, and about manipulation of concrete syntax (visual) objects.

AToMPM, A Tool for Multi-Paradim Modelling.
To whet your appetite: the AToMPM teaser video for the MoDELS 2013 conference.
A tutorial on AToMPM can be found here.
The AToMPM user manual [pdf].

  Examples

The examples page will be updated after each practical session. It will demonstrate the techniques learned using a simple, but complete, example.

  Assignments

1. Domain-Specific Modelling: meta-modelling (abstract syntax modelling) and action-code based operational semantics for a railway formalism in metaDepth.
2. Domain-Specific Modelling: meta-modelling (abstract and concrete syntax modelling) for a railway formalism in AToMPM.
3. Domain-Specific Modelling: rule-based model transformation for operational semantics of a railway formalism in AToMPM.
4. Domain-Specific Modelling: rule-based model transformation for translational semantics of a railway formalism (by mapping onto Petri Nets).
5. Domain-Specific Modelling: template-based model-to-text transformation for code synthesis.

  Projects

Topics
A list of tentative project topics can be found here.

Report info
Your project report should be written in LaTeX. If you're new to LaTeX, many tutorials such as this LaTeX primer are available.
You must use Elsevier's elsarticle style. You should download the elsarticle.zip archive. elsdoc.pdf contains the user documentation and elsarticle-template-harv.tex is the document template you should use as a starting point for your report.
Your report should contain at least the following:
  • A title capturing the essence of your work.
  • Author name, affiliation, and contact information.
  • An abstract presenting the paper's contribution. Based on the abstract, readers will decide whether or not your paper is worth reading.
  • Keywords summarising the paper.
  • A introduction presenting the problem/context. The introduction section should end with an overview of the rest of the paper. For example: ``Section 2 gives an overview of related work. Section 3 presents the design of our new architecture. ... Section 7 concludes.
  • A related work section, with references. If it is not elaborate enough to warrant its own section, related work may go into the introduction section.
  • A number of sections presenting the details of your contribution. This could contain details of your design.
  • If applicable, a section presenting the experience with using your work, including a performance evaluation.
  • A comparison of your work with that of others (what is new/better/...).
  • Conclusions and future work.
  • A bibliography. You must use bibTeX!
Note that your report should be a cross between a journal publication (where only the essence of the novel contribution should be presented) and a technical report (where technical details may be explained and there is no limitation on the number of pages used).

Presentation info

Project Material