|
Home General Staff Contact Partners Alumni Research Areas Projects Papers Books Reports Awards Teaching Lectures Exams B.Theses M.Theses PhD Theses Go Abroad Misc Talks Library Gallery Links Search Webmaster |
Project in Software EngineeringLast update: 2026-01-23
The kickoff meeting as well as the final presentation meeting are both happing in person in room SP3 218, attendance is mandatory for all participants. GoalThe goal of this course is to do a non-trivial software project over a whole semester and to go through all its phases (requirements definition, design, implementation, testing, documentation). The projects can be done in teams of 2 (with doubled workload), but can also be selected by a single student. At the end of the semester, the results have to be presented in a 15 minutes presentation. TopicsOpen TopicsThe following list contains open thesis topics that can be adjusted to fit as topic for Project in Software Engineering.
If you are interested in working on one of these topics, please contact the respective supervisor and discuss the scope of the work.
If you did not choose a topic before the introduction meeting, which has mandatory participation for everybody, you have to select one of the remaining topics during that meeting.
Already Started, Winter Semester 25/26 (presentation on Mo. 02.03.2026)
Assigned Topics, Summer Semester 2026 (presentation on Mo. 15.06.2026 (TBC))Assignments will be finalized during the introduction meeting. Late Projects, Winter Semester 26/27 (presentation during kickoff meeting of summer semester 2027)Final PresentationThe results of every project have to be presented by all team members in a 15 minutes presentation at the end of the semester. The presentation should mainly consist of a demo, and a brief explanation of the problems tackled in this project and how you solved them. Please prepare and discuss a slide deck with your supervisor. Avoid bullet point presentations and rather use graphics and examples to illustrate the problems and solutions. GradingThe grading is performed based on the quality of the implemented software (functionality, user friendlyness, robustness, readability and maintainability, documentation) as well as from the final presentation and the commitment during the semester. |