Skip to content

2. Fachgespräch 1

Estimated time to read: 18 minutes

TL;DR – What this lab is about

This lab is the transition from theory to project work.

Before starting your project, you must show that you understand the key concepts of the course.

In Fachgespräch 1 you should be able to explain methods from:

  • user research
  • requirements engineering
  • design
  • usability evaluation

Since lab sessions are scheduled at different times across groups, please book your slot for Expert Discussion 1 in Moodle early — do this as a team. For details on what to prepare and what to expect, refer to the Fachgespräch 1 description. Every team member should be individually well prepared: having worked through the theory and confident with the key terminology. Remember — this is a conversation, not an examination. Come ready to share your thinking, and engage with follow-up points. The quality of the discussion depends on everyone's active participation.

Schedule

Please note that the regular lab session is replaced by the bookable slots in Moodle. Successful completion of Fachgespräch 1 is a prerequisite for continued participation in the course.

2.1 Preparation

  • Read and understand the theory.
  • Book a time slot in Moodle as a team.
  • Prepare a 2-minute project pitch (as a team).

2.1.1 Project Idea

Bring a project idea to the discussion. To develop it, spend at least 15 minutes observing people in a dynamic, real-world location relevant to your theme — note what captures their attention, what brings them joy, and what causes frustration. These observations will help shape your direction.

Also explore APIs that could align with your project's objectives.

2.2 After the Lab

project

After Fachgespräch 1, the project phase begins.You should now start applying the theory to your own project.

You will get a gitlab repository and maintain a project portfolio hosted on GitLab Pages throughout the semester. The provided CI/CD pipeline offers basic infrastructure — verify it works for your project and adjust as needed.

Source referencing is mandatory. Credit all external materials (code, ideas, research). Learn the different resource types, how to manage lit.bib, and how to cite using mkdocs-bibex.

Portfolio content should document your journey from idea to solution — not just the outcome, but the reasoning behind your decisions, including the application and critical reflection of the concepts covered in this course.

Your portfolio is both a record of your progress and a foundation for your BPSE and future projects. Ground your documentation in the theory and show how you applied it in practice.

2.2.1 Projekbericht = Gitlab Pages

Your project report will be delivered as a GitLab Pages website, automatically generated from the repository I provide.

This means:

  • Do not write your documentation in external files such as Word, PDF, or LaTeX.
  • Write your documentation directly in the Markdown files inside the docs/ folder.

If you already created content elsewhere, move it into the Markdown files of this repository.

Please ensure you can read and write Markdown, test the generated page locally using the Docker container, and know how to access the repository's generated website. We're happy to clarify any questions or issues during lectures, open lab sessions, or practical courses.

2.2.2 🧰 Problem Description

Begin your portfolio by documenting the problem your project addresses in docs/problem.md. This entry should cover:

  • Problem & Goals — Describe the problem concisely: What is the problem, who is affected by it, and in what context does it occur? State the goals your solution aims to achieve.
  • Ideal Outcome — Paint a picture of the situation once the problem has been successfully solved.
  • Existing Solutions — Review comparable apps or approaches. What do they do well, and where do they fall short? Why is there still a need for your solution?
  • Scope & Delimitation — Clarify what is not part of your solution — related problems or topics you are intentionally setting aside.
  • Assumptions — State the assumptions you are making to frame and model the problem.

Checklist

  • [ ] GitLab repository is functional
  • [ ] MkDocs runs on your computer
  • [ ] docs/ folder contains all pages
  • [ ] GitLab Pages is live and viewable
  • [ ] Problem description is visible online