Model-based Software und Function DevelopmentModule description #40580 / Version 3
- 6 CP
- Portfolio examination
- Graded
- Winter and summer semester
- German
This module description is not valid in the current semester (Winter semester 2026/27).
| Module / Version | #40580 / #3 |
|---|---|
| Validity | SS 2017 – SS 2018 |
| Available language(s) | German |
| Credit points | 6 |
| Person responsible for the module | Gühmann, Clemens |
| Grading | Graded |
| Exam format | Portfolio examination |
| Language(s) of instruction | German |
Affiliation
| Faculty | Fakultät IV |
|---|---|
| Institute | Institut für Energie und Automatisierungstechnik |
| Academic chair | 34311600 FG Elektronische Mess- und Diagnosetechnik |
Contact
| Office | EN 13 |
|---|---|
| Contact person | Beyer, Christine |
| E-mail address | christine.beyer@tu-berlin.de |
| Website | http://www.mdt.tu-berlin.de |
Learning outcomes
The number of electrical control units used in automobiles has increased tremendously in recent years. In luxury vehicles, for example, about 100 different electronic control units are crosslinked in order to ensure drive, safety and driving comfort. The module mediates, through the lecture "Model-based Software und Function Development" the modern, integrated model-based function and software development process controls for motor vehicles. After having accomplished the module, the students should not only be able to apply methods but also the model-based software development and function complex tools such as rapid prototyping systems and hardware-in-the-loop simulators.
The percentage of software in the automotive industry is growing rapidly. It is known that the failure of software projects is caused in more than 80% of cases by inadequate requirements engineering and design. In the second focus of the module, students acquire in the seminar "Model-based Requirements and Systems Engineering" advanced knowledge for Requirements.
Students acquire through this approach the necessary basics of RE, get up to speed on the cutting edge of research / technology by modeling and have a basic understanding of the importance of requirements and systems engineering wherever software is developed, but especially in developing safety-related software to a control unit of a car. The seminar is aligned with the course "Model-based Software und Function Development" and adds greater depth in the above topics.
The percentage of software in the automotive industry is growing rapidly. It is known that the failure of software projects is caused in more than 80% of cases by inadequate requirements engineering and design. In the second focus of the module, students acquire in the seminar "Model-based Requirements and Systems Engineering" advanced knowledge for Requirements.
Students acquire through this approach the necessary basics of RE, get up to speed on the cutting edge of research / technology by modeling and have a basic understanding of the importance of requirements and systems engineering wherever software is developed, but especially in developing safety-related software to a control unit of a car. The seminar is aligned with the course "Model-based Software und Function Development" and adds greater depth in the above topics.
Content
The content of the lecture "Model-based Software und Function Development" are presented in a lecture and a seminar.
The lecture "Model-based Software und Function Development" first provides an overview of model-based development process and is structured as follows
* Theoretical System and information technology basics
* Processes to function and software development
* Methods and tools in the model-based development
* Testing
In the seminar "Requirements- und Testengineering" or "Modeling and Automation in Requirements Engineering" participants learn how to document and develop requirements using models. In addition, the participants become acquainted with tstate of the art in the field of requirements engineering. They prepare a short paper and present the contents of it.
The lecture "Model-based Software und Function Development" first provides an overview of model-based development process and is structured as follows
* Theoretical System and information technology basics
* Processes to function and software development
* Methods and tools in the model-based development
* Testing
In the seminar "Requirements- und Testengineering" or "Modeling and Automation in Requirements Engineering" participants learn how to document and develop requirements using models. In addition, the participants become acquainted with tstate of the art in the field of requirements engineering. They prepare a short paper and present the contents of it.
Module components
Compulsory area
The following courses are mandatory for this module:
| Courses | Type | Number | Frequency | Language | Hours per week | Course catalog |
|---|---|---|---|---|---|---|
| Modellgestütze Software- und Funktionsentwicklung | Lecture | 0430 L 324 | Summer semester | – | 2 | ISIS |
Compulsory elective area
A selection of the following courses must be completed:
Workload and credit points
Modellgestütze Software- und Funktionsentwicklung (Lecture)
| Workload description | Multiplier | Hours | Total |
|---|---|---|---|
| Präsenzzeit | 15 | 2 h | 30 h |
| Prüfungsvorbereitung | 15 | 2 h | 30 h |
| Vor- und Nachbereitung | 15 | 2 h | 30 h |
| 90 h | |||
Modeling and Automation in Requirements Engineering (Seminar)
| Workload description | Multiplier | Hours | Total |
|---|---|---|---|
| Ausarbeitung inkl. Präsentation | 1 | 56 h | 56 h |
| Präsenzzeit Einführung | 3 | 2 h | 6 h |
| Präsenzzeit Vorträge | 1 | 4 h | 4 h |
| Vor-/Nachbearbeitung | 6 | 4 h | 24 h |
| 90 h | |||
Requirements- und Testengineering (Seminar)
| Workload description | Multiplier | Hours | Total |
|---|---|---|---|
| Ausarbeitung inkl. Präsentation | 1 | 56 h | 56 h |
| Präsenzzeit Einführung | 3 | 2 h | 6 h |
| Präsenzzeit Vorträge | 1 | 4 h | 4 h |
| Vor-/Nachbearbeitung | 6 | 4 h | 24 h |
| 90 h | |||
The workload of the module adds up to 270 hours. The module therefore comprises 6 credit points.
Description of teaching and learning methods
Vorlesungen (VL): Frontalvortrag
Seminar (Sem)
Seminar (Sem)
Requirements for participation and examination
Desirable prerequisites for participation in the courses:
a) obligatorisch: Bachelor Technische Informatik, Elektrotechnik, Informatik oder Fahrzeugtechnik
Mandatory requirements for the module examination registration:
This module has no examination requirements.
Completion of the module
| Grading | Graded |
|---|---|
| Exam format | Portfolio examination |
| Type of portfolio examination | 100 points in total |
| Language | German |
Test elements
| Name | Points/Weight | Category | Duration/Extent |
|---|---|---|---|
| (Ergebnisprüfung) SE: Dokumentation | 30 | written | 8-10 Seiten |
| (Ergebnisprüfung) SE: Vortrag | 20 | oral | 20 Minuten |
| (Punktuelle Leistungsabfrage) Mündlicher Test für die VL Modellgestützte Software und Funktionsentwicklung | 50 | oral | 30 Minuten |
Exam description
Die Prüfungsform ist die Portfolioprüfung.
Insgesamt können 100 Portfoliopunkte erreicht werden:
* Vorlesung (50 Portfoliopunkte)
* Seminar (50 Portfoliopunkte)
Die Gesamtnote gemäß §47 (2) AllgStuPO wird nach dem unten stehenden Notenschlüssel ermittelt (entspricht Notenschlüssel 2 der Fakultät IV):
Punktzahl Note
mehr oder gleich 95 1,0
mehr oder gleich 90 1,3
mehr oder gleich 85 1,7
mehr oder gleich 80 2,0
mehr oder gleich 75 2,3
mehr oder gleich 70 2,7
mehr oder gleich 65 3,0
mehr oder gleich 60 3,3
mehr oder gleich 55 3,7
mehr oder gleich 50 4,0
weniger als 50 5,0
Insgesamt können 100 Portfoliopunkte erreicht werden:
* Vorlesung (50 Portfoliopunkte)
* Seminar (50 Portfoliopunkte)
Die Gesamtnote gemäß §47 (2) AllgStuPO wird nach dem unten stehenden Notenschlüssel ermittelt (entspricht Notenschlüssel 2 der Fakultät IV):
Punktzahl Note
mehr oder gleich 95 1,0
mehr oder gleich 90 1,3
mehr oder gleich 85 1,7
mehr oder gleich 80 2,0
mehr oder gleich 75 2,3
mehr oder gleich 70 2,7
mehr oder gleich 65 3,0
mehr oder gleich 60 3,3
mehr oder gleich 55 3,7
mehr oder gleich 50 4,0
weniger als 50 5,0
Duration of the module
The following number of semesters is estimated for taking and completing the module: 1 semester(s).
This module can be started in the following semesters: Winter and summer semester.
Maximum number of participants
The maximum capacity of participants is 32.
Registration procedures
Zur Teilnahme an dem Seminar ist eine Anmeldung unter https://www.dcaiti.tu-berlin.de/teaching/ erforderlich.
Recommended reading, lecture notes
Lecture notes
unavailable
Electronic lecture notes
unavailable
Recommended literature
- Angermann, A.; Beuschel, M.; Rau, M.; Wohlfarth, U.: Matlab-Simulink-Stateflow. Oldenbourg-Verlag 2003
- Bosch: Kraftfahrtechnisches Taschenbuch., 25. Auflage, Wiesbaden, Vieweg Verlag, 2004
- Förster: Die Kraftübertragung im Fahrzeug vom Motor bis zu den Rädern. Verlag TÜV Rheinland, Köln, 1987
- Gipser, M.: Systemdynamik und Simulation. B. G. Teubner Stuttgart - Leipzig 1999
- Krüger, M.: Grundlagen der Kfz-Elektronik, Hanser-Verlag, 2004
- Krüger, M.: Grundlagen der Kfz-Elektronik, Hanser-Verlag, 2004
- Lechner, G.; Naunheimer, H.: Fahrzeuggetriebe. Springer-Verlag, Berlin 1995
- Lemke, K.; Paar, C; M. Wolf: Embedded Security in Cars.
- Liggesmeyer, P.; Rombach , D.: Software Engineering eingebetteter Systeme, Grundlagen - Methodik - Anwendungen
- Reif, K.: Automobilelektronik ATZ/MTZ-Fachbuch, 2006
- Schäuffele, J., Zurawka, T.: Automotive Software Engineering, ATZ/MTZ-Fachbuch, 3. Auflage 2006
- Scholz: Softwareentwicklung eingebetteter Systeme
- Spillner, A.; Roßner, T.; Winter, M; Linz,T.; Praxiswissen Softwaretest - Testmanagement
- Wietzke, J.; Tran, M.T: Automotive Embedded Systeme
- Zimmermann, W.; Schmidgall, R.:Bussysteme in der Fahrzeugtechnik ATZ/MTZ Fachbuch, 2006
Assigned programs
This module is not used in any program.
Miscellaneous
Not specified