Increasing complexity of modern software calls for more effective and predictable approaches to software development. This need has led to the rise of a new paradigm: Modell-driven Software Engineering (MDSE).

MDSE is based on an explicit representation of software not just as text or binary code but as objects that can be queried and manipulated just like any application data. Such a set ob objects is called a (object) model of the software.

A model has a specific structure that reflects the concepts of the programming language in which the software was written. This structure can itself be represented by a (meta-)model. You can think of models as maps and meta-models as their legends. Meta-models model the concepts used for modelling (e.g. the symbols on the map). Meta-models let tools “understand” the concepts of a programming language (e.g. classes, methods, …).

Meta-models can be seen as just another language: A language for describing models. Much of the power of MDSE comes from one main achievement: The existence of a common understanding of the concepts that a language for describing meta-models must support. This common understanding is captured in a standardized meta-meta-model, which is the basis for arbitrary tools being able to understand and work with languages they where not specifically written for (by reading the language description expressed in the common meta-meta-model).

MDSE is being successfully used in many domains and is continuously evolving. There is a wide range of tools and technologies that use or support MDSE. Knowledge of MDSE concepts and tools has become an elementary skill for a software engineer.

The project is a pair of a seminar and a lab that address related topics. Typically, the seminar provides the foundations for the lab (in terms of concepts and tools).

It is possible to attend the seminar only. Attending the lab without prior successful participation in the seminar is not possible.

The seminar adresses

• the concepts of MDSE,
• current MDSE languages and (free) MDSE tools,
• a language and a tool developed at our department (StarTransformer).

The lab is dedicated to the use and further development of StarTransformer. The use of StarTransformer can comprise, for instance, development of:

1. a model-based version of a tool such as FindBugs,
2. refactorings for Java beyond those supported by Eclipse
3. fixes for buggy Java programs.

The further development of StarTransformer can comprise, among others,

1. the conceptual and practical integration with other existing MDSE approaches and tools
2. the extension by modules for other languages (e.g. C#, Phyton, PLSQL, or your personal favourite)

Interested in further details? Then attend the info meeting (see below).

The info meeting will introduce necessary background on model driven software development, present a catalogue of topics for the seminar and lab and clarify organisational issues.

Interested participants will then be able to choose

• whether they attend just the seminar or the seminar and lab
• which seminar / lab topic they want to pursue

These courses are part the ICM track of the M.Sc. curriculum but is also open to Diploma students. They are aimed at students who want to specialize in software engineering.

Seminar

• Course numbers
  • MA3218 (module handbook)
  • 612013218 (BASIS)
• Credit points: 4.
• Hours per week: 2
• Prerequisites: Object-oriented programming and UML.

Lab

• Course numbers
  • MA 3219 (module handbook)
  • 612013219 (BASIS)
• Credit points: 9.
• Hours per week: 6
• Prerequisites: Object-oriented programming and UML. Lab participants with experience in Prolog, Java or both are particularly

welcome and will be given priority (if there are more participants than places).

The seminar and lab will take place in the Römerstr. 164 building. For time information see seminar and lab.

• to be set up after registration of participants