• You efficiently use object oriented programming constructs and concepts such as classes, encapsulation, inheritance, polymorphism, interfaces, exceptions
  
• You can independently use existing libraries and code implemented by others, following available documentation.
  
• You know basic UML class diagrams notation, the relational data model and the SQL language
  
• You know and can use basic constructs of declarative functional programming, in particular anonymous functions and higher order functions.
  
• You can manipulate standard data structures such as lists, trees and graphs. You have basic working knowledge of complexity and algorithms, including dynamic programming.
  
• You know basic programming language concepts, and implementation techniques (grammars, abstract and concrete syntax, parsing, interpretation and compilation). This can be gained following a compiler course, for instance "Programming Language Concepts and Implementation"
  
• You are comfortable using Eclipse as your development environment (or a similarly mature tool, for instance IntelliJ)
  
• You can read professional computing literature; you have read research papers and books about programming before (this can be gained in almost every SDT course; or by trying to read a few papers before the course commences).
  
• You know the basic of software engineering processes and quality assurance, for instance having followed an introductory software engineering course (this can be gained following the course "Software Engineering and Quality Assurance")
  

• Use modelling as a tool to comprehend legacy code


• Use test-driven approach to work with legacy code
  
• Re-engineer legacy code to model driven architectures, including product line architectures
  
• Describe the main techniques used for domain modelling and implementation (domain specific languages, modelling frameworks, transformation languages, code generators, concrete syntax and models)
  
• Implement simple applications using Eclipse technologies: use eclipse as a development platform, extend it and customize it with your own editors (it is possible to substitute Eclipse with other platforms that are suitable for your individual project objectives)
  
• Use complex industrial strength frameworks (by having experienced work with, for example, OSGi, EMF, GMF, XText, Xpand and other components of the Eclipse platform)
  
• Find, select, and read research papers in the area.
  
• Discuss, criticize and assess technologies in this space, including placing them in established classifications, and contrasting them to other significant competitors.
  
• Carry over a limited research project in a medium-sized team, contributing to the area of (automated) software engineering.
  
• Concisely report results of your project in a written work conforming to the writing standards of the relevant research community, including proper problem formulation, problem motivation, discussion of state of the art, description of the solution, its limitations and a cogent argument for quality and validity of the solution.

• Meta-modelling and design of domain specific languages
  
• Concrete Syntax, and concrete syntax editors
  
• Architecture modelling, product line architectures, variability modeling
  
• Object Constraint Language
  
• Model based test generation
  
• Model Transformation and code generation (using examples of Xtend, Xpand and ATL)
  
• Implementation of domain specific languages using generic tools; Automatic model transformation
  
• Project supervision: defining a research project, matching arguments to objectives, structure and content of a research paper in software engineering, reading and describing related work, threats to validity, text editing.

• case studies in re-engineering existing code
  
• development of technology or evaluation of technology

16 weeks semester containing approximately 25 hours of lectures, 18 hours of tutorials and a project with supervision.

This is a project cluster. There will be classes running throughout the semester to help you with your project. There is less classes though than in a regular course, and there is no homework assignments. Most of the learning happens in exercises and in a project which is implemented in a 4-person team. Normally each team implements a different project, with slightly different goals. In the project you explore a particular software project introducing model-driven development principles into it. Alternatively you explore a sub-field of model driven development as a research area, delimit a research problem, solve it, and document it in a short and formal research paper.

The project part of the course accounts for about 60%-70% of the workload.

To achieve the goal you will need to learn new technologies you have never heard about, meet up for supervision meetings, study related literature (papers, books), and co-author a research paper in the end.

Since the precise choice of technologies to use varies between the project groups, you are expected to work on your own computer (it is possible to work with the software available on ITU machines, but with limitations - for example you have to stick to Eclipse).
To achieve the goal you will need to study a significant amount of related literature (papers, books), learn new technologies you have never heard about, meet up regularly for supervision meetings, and co-author a research quality paper in the end.

Since the precise choice of technologies to use varies between the project groups, you are expected to work on your own computer (it is possible to work with the software available on ITU machines, but with limitations - for example you have to stick to Eclipse).
----------
See the course schedule here:
link to the time table
The schedule will be ready shortly before the beginning of the term.
-----
Project cluster.
This is a the project cluster: You sign up for this project cluster as if for a normal course. You will also need to enter your project agreement of a 7,5 ECTS project in the project base where it will be assessed by the supervisor and the Board of Studies.
The project cluster will not appear on your diploma but the project that you register in the project base will of course appear once you have passed the exam. 

Each research team in the cluster will have to deliver a report paper strictly adhering to requirements detailed on the course website. Paper must be maximum 15 pages in length, conforming to the Springer LNCS formatting guidelines (http://www.springer.com/computer/lncs?SGWID=0-164-6-793341-0). No changes of font, margins, or other formatting aspects are permitted.

The handed in papers will be evaluated taking into account: clarity of the problem definition, problem significance, significance of the contribution of the work, quality of the evaluation (argument for validity of the work), study of existing literature, potential impact, and adherence to formatting guidelines.  

• Martin Fowler. Rebecca Parsons. Domain-Specific Languages. Addison-Wesley 2011.
  
• T. Stahl, M. Völter: Model-Driven Software Development: Technology, Engineering, Management. Wiley (2006)
  
• Richard C. Gronbach: Eclipse Modeling Project. A Domain-Specific Language (DSL) Toolkit. Addison Wesley (2009) http://www.slbooks.dk/shop/books/book.do?action=find&id=2895078