Model Driven Engineering 


Modelling and Simulation to Tackle Complexity
presentation [pdf] exploring the causes of complexity.

Dissecting Modelling Languages
presentation [pdf] [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).
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].
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].

Jean-Marie Favre. Megamodelling and Etymology. Proceedings of Dagstuhl Seminar 05161 - Transformation Techniques in Software Engineering. 2006. [pdf]
Thomas Kühne. Matters of (Meta-) Modeling. Software and System Modeling 5(4): 369-385. 2006. [pdf]
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]
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.

Model Transformation
Eugene Syriani. T-Core: Transformation Languages Tailored to Your Needs. [presentation .ppt].



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 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).

A list of tentative project topics can be found here
Some criteria for a good presentation

Matthias De Cock Microsoft's DSLTools project page
Dieter De Hen Precise Modelling of Model Transformation Languages project page
Ronald De Klerk Population Dynamics vs. Agent-Based modelling (using AnyLogic) project page
Simon Van Mierlo Rule-based transformation for/in MetaEdit+ project page
Tom Wijsman SpecifyingSpecifying and executing behavioral requirements: the play-in/play-out approach project page
Kevin Wyckmans Statechart modelling of NPCs project page