Search programme

​Use the search function to search amongst programmes at Chalmers. The study programme and the study programme syllabus relating to your studies are generally from the academic year you began your studies.

Syllabus for

Academic year
DAT240 - Model-driven engineering  
 
Syllabus adopted 2016-02-03 by Head of Programme (or corresponding)
Owner: MPSOF
7,5 Credits
Grading: TH - Five, Four, Three, Not passed
Education cycle: Second-cycle
Major subject: Computer Science and Engineering, Information Technology
Department: 37 - COMPUTER SCIENCE AND ENGINEERING


Teaching language: English
Open for exchange students

Course module   Credit distribution   Examination dates
Sp1 Sp2 Sp3 Sp4 Summer course No Sp
0110 Examination 3,0c Grading: TH   3,0c   15 Mar 2017 am L,  08 Jun 2017 pm L,  21 Aug 2017 am L  
0210 Project 4,5c Grading: UG   4,5c    

In programs

MPIDE INTERACTION DESIGN AND TECHNOLOGIES, MSC PROGR, Year 2 (elective)
MPSOF SOFTWARE ENGINEERING AND TECHNOLOGY, MSC PROGR, Year 1 (compulsory elective)

Examiner:

Universitetslektor  Thorsten Berger



Eligibility:


In order to be eligible for a second cycle course the applicant needs to fulfil the general and specific entry requirements of the programme that owns the course. (If the second cycle course is owned by a first cycle programme, second cycle entry requirements apply.)
Exemption from the eligibility requirement: Applicants enrolled in a programme at Chalmers where the course is included in the study programme are exempted from fulfilling these requirements.

Course specific prerequisites

To be eligible for the course the student should have 1) have a bachelor degree in Software Engineering, Computer Science or equivalent, 2) successfully completed a course in object oriented programming e.g. DAT042, DAT050, DAT055, DAT170, TDA545, TDA550 or equivalent, and 3) successfully completed a course in software modeling e.g.TDA593 or equivalent.  

Aim

Standard visual modeling languages, such as UML, taken out of the box, often do not fit an organization's needs. Extending modeling languages with necessary constructs and features, or creating complementary languages, requires specialist knowledge beyond that of software modeling. The purpose of this course is for the student to get familiarized with contemporary technologies and notations for creation, adaptation, and transformation of modeling languages.    

Learning outcomes (after completion of the course the student should be able to)

Knowledge and understanding
  • explain the following concepts: models, metamodel, constraints, transformation, semantics, abstract and concrete syntax;
  • explain the architecture of contemporary modeling frameworks
  • explain how domain specific modeling languages can be realized within a contemporary modeling framework
Skills and abilities
  • construct domain specific languages, e.g. specify metamodels including syntax and semantics
  • define syntactic constraints using a constraint language
  • realize metamodels within a modeling framework
  • construct model editors within a modeling framework
  • create model validators within a modeling framework.
  • specify model transformations and realizes them within a modeling framework.
  • apply the domain specific modeling approach to an authentic case
Judgement and approach.
  • recognize emerging technologies for model driven engineering using relevant information sources
  • select appropriate modeling technologies for a modeling tooling problem at hand

Content

Standard visual modelling languages, such as UML, do often not fit an organization's needs out of the box. Extending modelling languages with necessary constructs and features, or creating complementary languages, requires specialist knowledge beyond that of software modelling. The purpose of this course is to familiarize the student with contemporary technologies and notations for creation, adaptation, and transformation of modeling languages.

Organisation

The course consists of a series of lectures and a project. The lectures introduce each theme; the project explores the themes by development of a modeling tool. The tool is aimed at an authentic situation, and is realized by a contemporary modeling framework. The project consists of weekly iterations, during which the modeling tool is incrementally developed.  Project work is carried out in teams of 6 students, with support of a group supervisor.

Literature

Brambilla, Marco, Jordi Cabot, and Manuel Wimmer. "Model-driven software engineering in practice." Synthesis Lectures on Software Engineering 1.1 (2012): 1-182.

Examination

Examination consists of two parts: a written examination (4,5 hec) and a project examination (3 hec). The written examination is individual. The project examination is based on the outcome of the group work.

For the written examination the grading scale used is Five, Four, Three, Not passed.

For the project the grading scale used is Passed and Not passed.

For Passed (3) as a complete course grade, both the written exam and the project part must have been awarded Passed. For 4 or 5, the Project part must have been awarded Passed, and the written exam must have been awarded 4 respectively 5.


Page manager Published: Mon 28 Nov 2016.