Course syllabus - Model-based development: Theory and practice (MBD-TP)

Objectives

Model-Driven Development is a technique aiming at reducing the complexity of development and management of modern software applications through the exploitation of models. Even it is a young methodology, it gained more and more interest in industry, which considers it as a possible solution to alleviate the ever growing pressures of maximizing quality factors, notably time-to-market, performances, and maintainability. The aim of the course is to give an in-depth knowledge on the fundamentals of software systems modeling, analysis, and the automated generation of the implementation. The student will be made aware of both the state of art in research and state of practice in industry, with a special focus on UML modelling techniques and the general problems of managing evolution.
 
 
 

Learning outcomes

After completing the course, the student shall be able to:

1. understand the possibilities and limitations of Model-Driven Development for the design, analysis, and automated generation of software applications
2. evaluate scenarios and apply appropriate software modeling techniques in development projects (both in theory and in practice)
3. analyze evolution pressures and foresee possible issues in the management of the application lifecycle

Course content

The focus of this course will be on Model-Driven Development. The basics on software modeling technologies will be provided together with the issues related to the automated derivations of corresponding artifacts (models, analysis formats, code, documentation) and evolution management. The theoretical concepts will be paired with corresponding practical implementations, in order to get hands on existing technologies.

The course includes:
- Introduction to Software Engineering and Modeling
- Model-Based Development, Model-Driven Engineering, Model-Driven Architecture
- Metamodeling, modeling languages, domain-specific languages
- UML, profiling, action languages
- Model transformations, classification and their usage
- Evolution management in Model-Driven Development

Tuition

(Virtual) theoretical and practical lectures, theoretical and practical assignments.

Specific requirements

120 credits of which at least 80 credits within technology or informatics, including at least 30 credits in programming or software development.
In addition, Swedish course B/Swedish course 3 and English course A/English course 6 are required. For courses given entirely in English exemption is made from the requirement in Swedish course B/Swedish course 3.
 

Examination

Written assignment (INL1, module 1, 0,5 credits, (examines the learning objectives 1-3), marks Fail (U), Pass (G), or Pass with distinction (VG)
Written assignment (INL2), module 2, 1 credit, (examines the learning objectives 2 och 3), marks Fail (U), Pass (G), or Pass with distinction (VG)
Laboratory work (LAB1), module 2, 2 credits, (examines the learning objectives 2 och 3), marks Fail (U), 3, 4, or 5
Written assignment (INL3), module 3, 1 credit, (examines the learning objectives 2 och 3), marks Fail (U), Pass (G), or Pass with distinction (VG)
Laboratory work (LAB2), module 3, 2 credits, (examines the learning objectives 2 och 3), marks Fail (U), 3, 4, or 5
Written assignment (INL4), module 4, 1 credit, (examines the learning objectives 1-3), marks Fail (U), Pass (G), or Pass with distinction (VG)
 

A student who has a certificate from MDU regarding a disability has the opportunity to submit a request for supportive measures during written examinations or other forms of examination, in accordance with the Rules and Regulations for Examinations at First-cycle and Second-cycle Level at Mälardalen University (2020/1655). It is the examiner who takes decisions on any supportive measures, based on what kind of certificate is issued, and in that case which measures are to be applied.

Suspicions of attempting to deceive in examinations (cheating) are reported to the Vice-Chancellor, in accordance with the Higher Education Ordinance, and are examined by the University’s Disciplinary Board. If the Disciplinary Board considers the student to be guilty of a disciplinary offence, the Board will take a decision on disciplinary action, which will be a warning or suspension.

Grade

Grading scale: 5, 4, 3

Interim Regulations and Other Regulations

The course completely overlaps with DVA436 Model-Driven Engineering and DVA461 Model-Based Development (MBD), distance course.