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

flag

Software Architecture

Module name (EN):
Name of module in study programme. It should be precise and clear.
Software Architecture
Degree programme:
Study Programme with validity of corresponding study regulations containing this module.
Applied Informatics, Master, ASPO 01.10.2011
Module code: PIM-SAR
SAP-Submodule-No.:
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.
P221-0059
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.
2V+2F (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.
6
Semester: 1
Mandatory course: yes
Language of instruction:
German
Assessment:
Project

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

DFI-SAR (P610-0279) Computer Science, Master, ASPO 01.10.2018 , semester 1, mandatory course
KI747 Computer Science and Communication Systems, Master, ASPO 01.04.2016 , semester 1, optional course, informatics specific
KIM-SAR (P221-0059) Computer Science and Communication Systems, Master, ASPO 01.10.2017 , semester 1, optional course
PIM-SAR (P221-0059) Applied Informatics, Master, ASPO 01.10.2011 , semester 1, mandatory course
PIM-SAR (P221-0059) Applied Informatics, Master, ASPO 01.10.2017 , semester 1, mandatory course
Workload:
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 180 hours (equivalent to 6 ECTS credits).
There are therefore 135 hours available for class preparation and follow-up work and exam preparation.
Recommended prerequisites (modules):
None.
Recommended as prerequisite for:
Module coordinator:
Prof. Dr. Markus Esch
Lecturer:
Prof. Dr. Reiner Güttler


[updated 14.11.2013]
Learning outcomes:
After successfully completing this module, students will be capable of naming the basic concepts and methods of software architecture. They will be able to describe the tasks and role of a software architect in a project team and understand the importance of software architecture in large software projects.
 
They will be capable of deriving properties of a software architecture from user requirements and of developing and documenting a design using modern architectural approaches. In addition, they will also be able to analyze the advantages and disadvantages of an architecture and derive potential for improvement.
 
In the case studies accompanying the lectures, students will learn to work independently in small groups. They will be able to present their results and to document them in the form of a scientific publication.


[updated 24.02.2018]
Module content:
- Requirements for a software architecture
- The role and tasks of a software architect
- Process models
- Architectural views
- Architecture styles and patterns
- The documentation of a software architecture


[updated 20.12.2017]
Teaching methods/Media:
Lecture slides, annotated lecture slides as a script

[updated 20.12.2017]
Recommended or required reading:
Len BASS, Rick KAZMAN, Paul CLEMENTS: Software Architecture in Practice, Addison Wesley, 3rd Edition 2012
 
Gernot STARKE: Effektive Softwarearchitekturen: Ein praktischer Leitfaden, Hanser Verlag, 7. Auflage, 2015
 
Stefan ZÖRNER: Softwarearchitekturen dokumentieren und kommunizieren: Entwürfe, Entscheidungen und Lösungen nachvollziehbar und wirkungsvoll festhalten, Hanser Verlag, 2. Auflage, 2015
 
Rick KAZMAN, Humberto CERVANTES: Designing Software Architectures - A Practical Approach, Addison Wesley, 2016
 
George FAIRBANKS: Just Enough Software Architecture: A Risk-Driven Approach, Marshall & Brainerd, 2010

[updated 30.07.2021]
Module offered in:
WS 2018/19, WS 2017/18, WS 2016/17, WS 2015/16, WS 2014/15, ... 
[Thu Nov 21 15:34:29 CET 2024, CKEY=ps, BKEY=pim, CID=PIM-SAR, LANGUAGE=en, DATE=21.11.2024]