|
|
|
| Module code: MST2.SYSE |
|
|
2V+2PA (4 hours per week) |
|
5 |
| Semester: 5 |
| Mandatory course: no |
Language of instruction:
German |
Assessment:
Oral exam and project documentation
[updated 02.12.2025]
|
E2572 (P221-0184) Electrical Engineering and Information Technology, Bachelor, ASPO 01.10.2018
, semester 5, optional course, non-technical
MST2.SYSE (P221-0184) Mechatronics and Sensor Technology, Bachelor, ASPO 01.10.2020
, semester 5, optional course
|
60 class hours (= 45 clock hours) over a 15-week period. The total student study time is 150 hours (equivalent to 5 ECTS credits). There are therefore 105 hours available for class preparation and follow-up work and exam preparation.
|
Recommended prerequisites (modules):
None.
|
Recommended as prerequisite for:
|
Module coordinator:
Prof. Dr. Martin Buchholz |
Lecturer: Prof. Dr. Martin Buchholz
[updated 08.11.2023]
|
Learning outcomes:
After successfully completing this module, students will be able to apply the formal methods of systems engineering to a specific project. They will be familiar with the tools needed to translate an interdisciplinary task involving a complex system (customer requirements) into a concrete result using a methodical approach.
[updated 02.12.2025]
|
Module content:
1. Lecture (with a focus on holistic product development): - Motivation and history of systems engineering - System concepts (black/white box, recursion, emergence) - Fundamentals of problem solving - Classic product development methodology (V-model according to VDI 2206/2221, RFLP approach) - Activities during system development (according to ISO 15288) - Model creation for describing systems - Modeling systems with SysML (in the Gaphor modeling tool using a concrete example with exercises) 2. Project work: Students must develop a cyber-physical product from scratch. To do so, they will use the modeling tool Gaphor and apply the methods learned in the lecture. The aim is to describe the product to be developed in sufficient detail, to make development decisions comprehensible, and to create a consistent system model in the process. In principle, any self-contained “cyber-physical” products, i.e., those that can generate all functionality within themselves (or with the help of a connected service, which is the “cyber” part), are suitable products for the project work. The specific purpose of the product should be easily understood.
[updated 02.12.2025]
|
Teaching methods/Media:
Lecture, coaching during the project
[updated 02.12.2025]
|
Recommended or required reading:
Recommended reading according to project. Trade journals and data sheets
[updated 02.12.2025]
|