htw saar Piktogramm QR-encoded URL
Back to Main Page Choose Module Version:
emphasize objectives XML-Code


Software Development Processes

Module name (EN):
Name of module in study programme. It should be precise and clear.
Software Development Processes
Degree programme:
Study Programme with validity of corresponding study regulations containing this module.
Computer Science and Communication Systems, Master, ASPO 01.04.2016
Module code: KI841
The exam administration creates a SAP-Submodule-No for every exam type in every module. The SAP-Submodule-No is equal for the same module in different study programs.
Hours per semester week / Teaching method:
The count of hours per week is a combination of lecture (V for German Vorlesung), exercise (U for Übung), practice (P) oder project (PA). For example a course of the form 2V+2U has 2 hours of lecture and 2 hours of exercise per week.
3V+1P (4 hours per week)
ECTS credits:
European Credit Transfer System. Points for successful completion of a course. Each ECTS point represents a workload of 30 hours.
Semester: 2
Mandatory course: no
Language of instruction:
Oral examination 40%, term paper 30%, presentation 30%

[updated 24.02.2018]
Applicability / Curricular relevance:
All study programs (with year of the version of study regulations) containing the course.

DFI-SEP (P610-0554) Computer Science, Master, ASPO 01.10.2018 , semester 2, mandatory course
KI841 (P222-0096) Computer Science and Communication Systems, Master, ASPO 01.04.2016 , semester 2, optional course, informatics specific
KIM-SEP (P221-0060) Computer Science and Communication Systems, Master, ASPO 01.10.2017 , semester 2, optional course, informatics specific
PIM-SEP (P221-0060) Applied Informatics, Master, ASPO 01.10.2011 , semester 2, mandatory course
PIM-SEP (P221-0060) Applied Informatics, Master, ASPO 01.10.2017 , semester 2, mandatory course
Workload of student for successfully completing the course. Each ECTS credit represents 30 working hours. These are the combined effort of face-to-face time, post-processing the subject of the lecture, exercises and preparation for the exam.

The total workload is distributed on the semester (01.04.-30.09. during the summer term, 01.10.-31.03. during the winter term).
60 class hours (= 45 clock hours) over a 15-week period.
The total student study time is 150 hours (equivalent to 5 ECTS credits).
There are therefore 105 hours available for class preparation and follow-up work and exam preparation.
Recommended prerequisites (modules):
Recommended as prerequisite for:
Module coordinator:
Prof. Dr.-Ing. Martin Burger
Prof. Dr. Helmut Folz

[updated 01.04.2003]
Learning outcomes:
After successfully completing this module, students will be able to compare stability-oriented and continuously adapting procedures.
- Students will be able to differentiate between contexts in which stability-oriented and agile development processes are suitable.
- They will be able to discuss the principles of agile development processes.
- Students will be able to create requirements for software systems and prioritize them.
- They will be able to plan the creation of software solutions using agile methods.
- Students will be able to discuss the importance of teamwork and communication in software development.
- Students will be able to work independently on agile software development topics, summarize their findings and present them.

[updated 30.06.2024]
Module content:
The focus of this module is the principles and practices of agile software development processes. Students will learn how to deliver high-quality software with high customer value in the shortest possible time using constantly adapting procedures.
Software Development Processes:
- Definition and importance of software development processes
- Comparing the waterfall model and agile development
Agile Basics und Principles:
- The agile manifesto and its values
- Agile principles and methods
Agile Requirements Management:
- Creating and prioritizing user stories
- Product and sprint backlog management
Agile Project Management:
- Sprint and release planning
- Velocity calculation and burndown charts
Team Work and Communication:
- Effective collaboration in a team
- Communication and transparency
This content is supplemented and further developed by topics presented by the students.

[updated 30.06.2024]
Teaching methods/Media:
Transparencies, projector

[updated 24.02.2018]
Recommended or required reading:
Agile Testing
Der agile Weg zur Qualität
Von Manfred Baumgartner, Martin Klonk, Christian Mastnak, Richard Seidl · 2023
Clean Agile. Die Essenz der agilen Softwareentwicklung
Zurück zu den Ursprüngen: Die agilen Werte und Prinzipien effektiv in der Praxis umsetzen
Von Robert C. Martin · 2020
Engineering Software Products
An Introduction to Modern Software Engineering
Von Ian Sommerville · 2019
Implementing Lean Software Development
From Concept to Cash
Von Mary Poppendieck, Tom Poppendieck · 2006
Modernes Software-Engineering
Entwurf und Entwicklung von Softwareprodukten
Von Ian Sommerville · 2020
Requirements Engineering für die agile Softwareentwicklung
Methoden, Techniken und Strategien
Von Johannes Bergsmann · 2023
Requirements-Engineering und -Management
Das Handbuch für Anforderungen in jeder Situation
Von Christine Rupp, SOPHISTen · 2020
Software Engineering
Von Ian Sommerville · 2018
Software Engineering, Global Edition
Von Ian Sommerville · 2016
Software Engineering
Grundlagen, Menschen, Prozesse, Techniken
Von Jochen Ludewig, Horst Lichter · 2023
Software Engineering - kompakt
Von Anja Metzner · 2020
Diese Literatur wird entsprechend den von den Studierenden präsentierten Themen ergänzt.

[updated 30.06.2024]
Module offered in:
SS 2020, SS 2019, SS 2018, SS 2017, SS 2016, ...
[Fri Jul 12 23:45:44 CEST 2024, CKEY=sweproz, BKEY=kim, CID=KI841, LANGUAGE=en, DATE=12.07.2024]