Courses
Courses of the current semester (SS 24)
- Component-based Software Engineering (Lecture with exercise)
- Softwaremanagement (Lecture with exercise)
- Future-Proof Software Systems (Lecture with exercise)
- Academic Skills in Software Engineering (Lecture with exercise)
- Softwaretechnologie (Lecture with exercise)
- Automotive Software Engineering (AutoSOFT) (Lecture)
- Adaptive, Mobile Information Provision in Digital Health (Main seminar)
Courses of the next semester (WS 24/25)
Permanent courses
- University, where you visited the courses
- URLs of these courses or other information
- Translation to ECTS credit points
- Which courses of ST you want to substitute
- The exams, for which the acknowledged courses shall be used
Student Theses
Here you can find information to currently offered topics for minor and major theses, as well as on currently running or finished theses. Please click on "more", to get more information. Hints on how to write a thesis exist as pdf. For theses, a LaTeX package is offered, which helps in adhering to the required layout.[back] [Proposals of topics] [finished topics] [RSS-Feed Proposals of topics]
Normally, additional data is needed as input in each transformation step besides a number of source models to be translated to a number of target models. Profiles, such as proposed for the Unified Modelling Language (UML), are one solution in order to inject such annotations into a specific step of a transformation chain. Profiles provide a model extension mechanism on the meta-layer. Hence, annotations are directly added to the source-models of a transformation. We claim that this makes the source models hard to maintain since source models are polluted with this additional information, which is needed to generate the target models. In case the annotations are not used for this, but for a later transformation step, all in-between steps needs to be unnecessarily polluted with the annotations in the same way. In the MDPE case, for instance, five different kinds of annotations are defined based on business process models which are used as input for a four step transformation chain. The annotations are used in the second transformation step and the third transformation step. Thus, it is not needed to deal with the annotated information in, for instance, the first transformation step.
We claim that a more flexible solution than a profile based one is needed to implement model annotations in transformation chains as described above. Such a solution needs to support annotations based on arbitrary models in a transformation chain. A brief description about our first ideas towards a solution follows:
Figure 1 gives an overview of our proposed architecture. In order to annotate a Source Model (development model in Figure 1) in a non-intrusive way, without actually altering or extending it, we propose a systematic architecture integrating the following three model types in a systematic manner: - Annotation and Composition Models are used in order to represent annotations including the linkage information about which annotation is associated with which model element in the original source models. Hence, an Annotation and Composition Model consists of two parts: One for the annotation itself and one for the linkage information. Due to the fact that the linkage information is included in the Annotation and Composition Models, we are not required to pollute the original Source Model with these data.- Tracing Models contain the information about which source model element has been transformed to which target model element in a Transformation Chain (see centre of Figure 1). Hence, tracing models contain associations between models conforming to two different meta-models.
- A M2M Navigation Model is used to associate models in a Transformation Chain with the related Tracing Models. This is required since we assume that the models in a transformation chain are non-changeable and therefore cannot be polluted with the tracing model linkage information. Within this thesis, a prototype for the proposed architecture needs to be implemented. In detail, two modules are required, one for the generic purpose of model annotation (see Annotation Tool in Figure 1) and one for generically using the annotated information at an arbitrary step in a transformation chain. Based on a discovery and discussion of implementation options, a solution needs to be implemented and applied as part of the implementation of the MDPE process. Figure 1
Student: Simon Mitschke
Courses of the previous semester
In this overview you can find all over the course of the Chair. In addition to those of the previous semesters can be found here and those that are held in current and upcoming semester.[back] [to tabular view]
You may select this summary also in tabular view.
Overview of courses
Course | SWS | WS/SS | INF | MINF | IST | DSE | CL | INF | FAK | MATH | |||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
BA | MA | DIPL | BA | MA | DIPL | DIPL | MA | MA | LE | BA | MA | ||||
Academic Skills in Computer Science (ASiCS) | 2/2/0 | WS/SS | B-510 B-520 | VERT3 | 04-FG-SWT B-520 VERT3 | B-530 B-540 | AQUA | INF-B-540 | PCS | ||||||
Automotive Software Engineering & Functional Safety | 4/0/0 | SS | B-510 B-520 | VERT3 | 04-FG-SWT B-520 BAS3 | B-530 B-540 | BI-4 | INF-B-540 MINF-04-FG-EMW | 05-FG-SWT | ||||||
Component-Based Software Engineering | 2/2/0 | SS | B-520 | VERT3 | 04-FG-SWT B-520 | B-540 | BI-4 | MINF-04-FG-EMW INF-B-540 | 05-FG-SWT | 10-E5 14-E4 | CSE | ||||
Design Patterns and Frameworks | 2/2/0 | WS | VERT3 | 04-FG-SWT BAS3 VERT3 B-520 | BI-4 | MINF-04-FG-EMW | 10-M4 | CSE | MA | INFSEN | |||||
Enterprise Software - Applications, Technologies and Programming | 2/0/0 | WS | VERT3 | 04-FG-SWT BAS3 VERT3 | INF-BI-5 MINF-04-FG-EMW | ||||||||||
Future-Proof Software Systems | 2/0/0 | WS | VERT3 | 04-FG-SWT VERT3 | BI-4 | MINF-04-FG-EMW | 10-E5 14-E4 | ||||||||
Hauptseminar Softwaretechnologie | 0/2/0 | WS/SS | VERT3 | 04-HS BAS3 VERT3 | AQUA | ||||||||||
Komplexpraktikum Softwaretechnologie | 0/0/4 | WS/SS | MA-PR VERT3 | 04-KP PM-FPA VERT3 | E-4 | 05-KP | |||||||||
MINF-BI-5 | 2/2/0 | SS | |||||||||||||
Model-Driven Software Development in Technical Spaces | 2/2/0 | WS | BAS3 VERT3 04-FG-SWT | BI-4 | INF-BI-5 MINF-04-FG-SE | ||||||||||
Praktikum Softwaretechnologie in der industriellen Praxis | 0/0/2 | WS | 04-P | ||||||||||||
Proseminar Softwaretechnologie | 0/2/0 | SS | B-510 B-520 | 04-PS B-520 D-520 | B-530 B-540 | INF-B-540 | |||||||||
Requirements Engineering und Testen | 2/2/0 | WS | B-510 | VERT3 | 04-FG-SWT BAS3 VERT3 | B-530 | MINF-04-FG-EMW | ||||||||
Role-based Software Infrastructures | 2/0/0 | WS | B-510 B-520 | BAS4 VERT3 VERT4 | B-520 BAS3 VERT3 | BI-2 BI-4 | |||||||||
Selected International Research in SE | 1/0/0 | WS | VERT3 | 04-FG-SWT VERT3 | INF-BI-5 | ||||||||||
Seminar Modellierung und Architektur von Softwaresystemen | 0/2/0 | WS/SS | VERT3 | 04-FG-SWT | 05-FG-SWT | INF-FF | |||||||||
Software Reengineering | 2/2/0 | SS | VERT3 BAS3 | 04-FG-SWT VERT3 BAS3 | BI-4 | MINF-04-FG-EMW | 05-FG-SWT | 10-M4 | |||||||
Software Reengineering and Software Measurement | 2/2/0 | SS | |||||||||||||
Software-Entwicklungswerkzeuge | 2/2/0 | WS | VERT3 | 04-FG-SWT BAS3 VERT3 | INF-BI-5 MINF-04-FG-EMW | ||||||||||
Softwarearchitektur (Ausgewählte Kapitel der Softwaretechnologie) | 2/0/0 | SS | B-520 | BAS3 04-FG-SWT VERT3 B-520 | B-540 | BI-4 | INF-BI-5 MINF-04-FG-EMW INF-B-540 | 05-FG-SWT | 10-M4 | MA | INFSEN | ||||
Softwareentwicklung in der industriellen Praxis | 2/0/0 | WS | B-510 B-520 | VERT3 | 04-FG-SWT B-520 BAS3 VERT3 | B-530 B-540 | BI-4 | INF-B-540 MINF-04-FG-EMW | MA | INFSEN | |||||
Softwaremanagement | 2/2/0 | SS | B-510 B-520 | 04-FG-SWT B-520 BAS3 | B-530 B-540 | BI-4 | INF-B-540 INF-BI-5 MINF-04-FG-EMW | 05-FG-SWT | MA | INFSEN | |||||
Softwaretechnologie | 2/2/0 | SS | D-240 | B-310 | 05-PF-GS | EUI MA PHY WW | INFC | INFSEN | |||||||
Softwaretechnologie II | 2/2/0 | WS | B-510 B-520 | BAS3 | 04-FG-SWT B-520 BAS3 | B-530 B-540 | INF-B-540 MINF-04-FG-EMW | ||||||||
Softwaretechnologie-Projekt | 0/0/4 | WS | B-320 B-321 | B-320 B-321 | MA | INFD | INFSEN |
- INF-BA → Bachelor Informatik
- INF-MA → Master Informatik
- INF-DIPL → Diplom Informatik
- MINF-BA → Bachelor Medieninformatik
- MINF-MA → Master Medieninformatik
- MINF-DIPL → Diplom Medieninformatik
- IST-DIPL →
- DSE-MA → Master Distributed Systems Engineering
- CL-MA → Master Computional Logic
- INF-LE →
- FAK →
- MATH-BA →
- MATH-MA →