• Requirements analysis & determination
• Systems modeling
• Project planning
• Prototyping
• Unified Modeling Language (UML)
• Human-Computer Interaction

• understand the fundamentals of Systems Analysis and Design.
• have basic project management skills.
• can determine systems requirements.
• have basic skills in different modelling techniques.
• can specify classes and methods.
• have basic design skills.

Timeline

Introductory Session

Friday, 13 October 2023, 10:00am – 1:30pm, Location: Room S24, building 106 (Seminar Building)

On the first day of the semester, we will hold an introductory session to explain the course organization and give you an introduction to the course’s topics. We will cover the syllabus (linked above) as well as the lecture and tutorial for unit 1.

Regular Sessions

• Thursday Sessions (usually Lectures)
  • 2:00pm to 3:30pm (every week)
  • Location: Room S11, building 106 (Seminar Building)
• Friday Sessions (usually Tutorials)
  • 10:00am to 11:30am (every week)
  • 12:00pm to 1:30pm (on five days only)
  • Location: Room S24, building 106 (Seminar Building)

A detailed timeline is available in the syllabus as well as in ILIAS.

Important Dates

• KLIPS Exam Registration Deadline: 31 October 2023, 11:59pm (via KLIPS2)
• Team Registration Survey Deadline: 31 October 2023, 11:55pm (via ILIAS)
• eExam Registation Survey Deadline: 21 January 2024, 11:55pm (via ILIAS)
• Q&A-Session: TBA
• Team Project Submission Deadline: 29 January 2024, 11:55pm (via ILIAS)
• eExam (1st option): 7 February 2024, 4:00pm to 5:30pm, Room S91 (Philosophikum, building 103)
• eExam (2nd option): 17 March 2023, 1:00pm to 2:30pm, Room S89 (Philosophikum, building 103)

Assessment

This course will be assessed as a portfolio exam.

1) eExam (60 points)

A 60-minute exam covering the whole lecture and tutorial. This will be written as an electronic exam in the PC pool at the Philosophikum.

2) Team Project (30 points)

A team project focusing on the modeling components of the course. It will be structured in small weekly tasks, which are based on that week's content. You don't have to submit them each week, instead you combine them at the end of the semester into one big submission. Further details will be announced.

Required components:

• System request
• Requirements definition
• Use-case & activity diagrams
• Class diagram
• Sequence diagrams & behavioral state machines
• Architecture model
• User interface design
• Executive summary

You are not required to build or program the system.