Practical Course Continuous Software Engineering SS26

Aus SDQ-Wiki
Practical Course Continuous Software Engineering ({TODO})

Semester: Sommersemester 2026
LP (ECTS): 6
SWS: 4
Studiengang: Master Informatics, Master Information Engineering
Ansprechpartner: Mahdi Jafari, Nathan Hagel
Ort und Zeit der Lehrveranstaltung
unregelmäßig, siehe Beschreibungstext
unbekannt
ILIAS-Bereich

https://ilias.studium.kit.edu/goto.php?target=crs 2916465&client id=produktiv

Seite im Vorlesungsverzeichnis

Registeration

  • There are approximately 12 possible positions available.
  • Registration is possible from 14.04.2026 by joining the ILIAS course.
  • Topics will be assigned in a preliminary meeting (mandatory attendance). Please also participate if you are on the waiting list (see the waiting list policy).

Appointments

Registration from (Register by joining the Ilias course)
Appointment-new.png
Tuesday, 14. Apr 2026, 10:00
Preliminary meeting with topic presentation (mandatory attendance)
Appointment-new.png
Monday, 27. Apr 2026, 10:00 - 11:00 Uhr in Room 010, Building 50.34
Topic assignment (mandatory attendance)
Appointment-new.png
Thursday, 30.04.2026 13:00-13:30 in Room 010, Building 50.34
Block seminar with final lectures (mandatory attendance)
Appointment-new.png
End of the lecture-free period


Topic assignment

  • Topics are assigned according to the order of registration in ILIAS, on a first-come, first-servedbasis.

Substitute candidate rule

  • Even as a latecomer (participant on the waiting list), experience shows there is a good chance of receiving a topic.
  • Any remaining topics will be allocated to alternates during the topic allocation process.
    • Therefore, please also participate in the meetings for topic presentation and topic allocation, even if you are on the waiting list.
    • If you are unable to attend these dates for reasons beyond your control, your practical course registration will be forfeited.
    • Only in rare cases, if individual topics become available after the topic allocation, do we inform the remaining candidates on the waiting list by email.

Practical Course Overview

Agile software development methods refer to a class of iterative-incremental development methods that place particular emphasis on executable software, early feedback from stakeholders, and the acceptance of necessary changes. These development methods critically examine efforts that are not directly related to producing working software.

Modeling helps developers deal with complex systems and issues and find a suitable level of abstraction for upcoming decisions. In the context of agile development, sketches of models are primarily created on whiteboards for communication and solution development (agile modeling), but are not further persisted or processed to save effort.

In this practical course, participants use and expand upon current tools from practice and research to support agile modeling. Two types of tools are considered:

  • Tools for the analysis of natural language and/or model sketches to derive semi-formal models and statements about software systems
  • Tools to derive models semi-automatically from source code and runtime information, especially performance data.
  • Tools for simpler, domain-specific modeling

Depending on the topic being addressed, different technologies are used, including

  • Eclipse platform
  • EMF (Eclipse Modeling Framework)
  • Palladio Simulator
  • Protégé Ontology Editor
  • Natural Language Processing Toolkit (Stanford CoreNLP)
  • more plugins for Eclipse

practical course assignments are individually graded, and group work is planned. The practical course is integrated into the chair's current research projects and offers ample opportunity for creativity. The practical course tasks are practically oriented and prepare students for realistic tasks in research and industry.


Learning objectives

Students can:

  • Understand scientifically motivated problems and, in cooperation with supervisors, derive requirements for the software to be developed/extended.
  • Create medium-sized programs using current development environments, or familiarize yourself with medium to large programs and develop them further.
  • Present the project progress to supervisors at regular meetings and identify any potential obstacles.
  • Evaluate third-party programs as part of code reviews, identify potential weaknesses and discuss them.
  • to present a (further) developed program in the context of a short presentation.
  • Document a (further) developed program.

Procedural Details

  • Participation in the topic presentation and topic allocation is required.
  • Further appointments will be arranged individually with the supervisor.

Documents

The materials will be made available on the ILIAS platform.

Administrative

Lehrangebot nach Studiengang

Informatik

Bachelor · Master

Informationswirtschaft

Bachelor · Master