Software Engineering for Smart Data Analytics & Smart Data Analytics for Software Engineering

User Tools

Site Tools


  • Course title: Seminar Model-driven Software Engineering
  • Course number in module handbook: MA 3218
  • Course number in Basis: 612013218
  • Hours per week: 2
  • Credit points: 4.
  • Prerequisites: Foundtions of object-oriented programming and UML.

Seminar Overview

The seminar will be two-fold:

  1. One part will introduce basic MDSE concepts and, in particular, declarative MDSE.
  2. The second part will present application scenarios in which we will use MDSE.

These include generic problems such as building a precise control-flow or data-flow graph.


If you are interested in the seminar and lab attend the info meeting. The seminar topics listed below will be assigned to interested participants during the info meeting:

  1. Basics: Ecore, EMF
  2. Text to Model: Xtext / Customization
  3. Text to Model: Xtend / Language
  4. Model to Text: Xtend / Xpand
  5. Model to Model: ATL


Preparation. Following the info meeting's assignment of individual topics, you will have time to

  • study the provided material
  • possibly gather more material
  • try out tools
  • structure the material
  • gather open questions to be clarified
  • make a mind map of the topic domain
  • determine key concepts and the material to use for presenting them
    • definitions and examples,
    • source code
    • images, figures, tables, …
  • Monday, August 3 to Friday, August 7

Clarification. Each participant will be assigned a slot on Friday, August 7 (for discussing the above, and, most importantly, addressing all the problems that he / she still faces (unclear concepts, unclear presentation ideas, …)

  • Friday, August 7, between 9:00 and 16:00

Draft presentation . After clarifying the basic questions, continue your preparation and distill the information that you would like to present. Make a draft presentation that focuses on content

  • main ideas
  • order in which you want to present them (dependency graph)
  • code examples, images, figures, tables that you will use to illustrate the ideas
  • basic layout of the presentation (no animations yet)

If you send me the draft presentation by 24.8. you will get feedback and suggestions for improvement within at most two days.

  • → 24.8.2015 Send draft presentation BEFORE this date
  • ← 26.8.2015 Get feedback / tips for improvement

Rehearsal presentation. In the second week of October participants will deliver their draft presentation.

The draft presentation will be delivered live, as a general rehearsal, that is, not just the slides but by actually giving the talk. Then the participants will have two days left for including any remainings suggestions for improvement (slides and presentation / speech) and delivering their final presentation.

Official Presentations

Each seminar participant is required to attend each official presentation.

Every presentation should take 30 minutes + 15 minutes for demo (if needed) and discussion.

Final deliverables: Slides and Report After the presentation you may still update the slides and finalize the written report about your topic.

  • October 12: Deliver final presentation slides and final report (8-10 pages)
The report must be understandable to someone who did not attend your presentation – that is, it must be self-contained (except for references to orginal literature).

In the report you must express everything in your own words. Copying text from other sources without explicitly marking such copies as citations is considered plagiarism and will lead to failure of the seminar (grade 5.0).

teaching/labs/mdse/2015/seminar.txt · Last modified: 2018/05/09 01:59 (external edit)

SEWiki, © 2023