Module Handbook

  • Dynamischer Default-Fachbereich geändert auf INF

Module INF-34-31-M-6

System- and Software Architecture (M, 4.0 LP)

Module Identification

Module Number Module Name CP (Effort)
INF-34-31-M-6 System- and Software Architecture 4.0 CP (120 h)


CP, Effort 4.0 CP = 120 h
Position of the semester 1 Sem. in SuSe
Level [6] Master (General)
Language [EN] English
Module Manager
Area of study [INF-SE] Software-Engineering
Reference course of study [INF-88.79-SG] M.Sc. Computer Science
Livecycle-State [NORM] Active


Type/SWS Course Number Title Choice in
Presence-Time /
SL SL is
required for exa.
PL CP Sem.
2V+1U INF-34-31-K-6
System- and Software Architecture
P 42 h 78 h
ja PL1 4.0 SuSe
  • About [INF-34-31-K-6]: Title: "System- and Software Architecture"; Presence-Time: 42 h; Self-Study: 78 h
  • About [INF-34-31-K-6]: The study achievement "[U-Schein] proof of successful participation in the exercise classes (ungraded)" must be obtained.
    • It is a prerequisite for the examination for PL1.

Examination achievement PL1

  • Form of examination: written exam (Klausur) (60-180 Min.)
  • Examination Frequency: each summer semester
  • Examination number: 63432 ("System- and Software Architecture")

Evaluation of grades

The grade of the module examination is also the module grade.


  • Definition of the terms distributed system, software architecture, component and interface
  • Design process of distributed systems integrated into the system development process
  • View and UML based specification of software architectures: Technical view, technological view, distribution view, deployment view, etc.
  • Analysis and evaluation of architectures with ATAM
  • Design patterns, standard architectures and approaches for different problems; for example, for persistence, transaction management, and workflow management.
  • Examples of software architectures for information systems, complex systems and embedded systems

Competencies / intended learning achievements

The lecture communicates the fundamental knowledge that a successful software architect needs. Using a basic set of examples, which are derived from standard usage, it demonstrates:
  • How large system divide into components and which relationships exist among these.
  • How the process of software design looks like.
  • Which methods and description techniques are suitable.
  • Which established solutions exist for technical aspects such as transaction administration or persistence.


  • Jens Knodel, Matthias Naab: Pragmatic Evaluation of Software Architectures, Springer, ISBN 978-3-319-34176-7, 2016.
  • George Fairbanks Just Enough Software Architecture Marshall & Brainerd, 2010.
  • Richard N. Taylor, Nenad Medvidovic, Eric M. Dashofy Software Architecture: Foundations, Theory, and Practice Wiley, 2009.
  • Eoin Woods, Nick Rozanski Software Systems Architecture Addison Wesley, 2005
  • Len Bass, Paul Clements, Rick Kazman Software Architecture in Practice (third edition) Addison Wesley, 2012.
  • Paul Clements, Felix Bachmann, Len Bass, David Garlan, James Ivers, Reed Little, Robert Nord, Judith Stafford Documenting Software Architectures - Views and Beyond (second edition) Addison-Wesley, 2010.
  • Douglas Schmidt, Michael Stal, Hans Rohnert, Frank Buschmann Pattern-Oriented Software Architecture, Volume 2: Patterns for Concurrent and Networked Objects, Wiley, 2001.
  • Siegel, Jon. "An overview of CORBA 3." Distributed Applications and Interoperable Systems II. Springer US, 1999. 119-132.
  • further literature will be announced in the lecture.

Requirements for attendance of the module (informal)


Requirements for attendance of the module (formal)


References to Module / Module Number [INF-34-31-M-6]

Course of Study Section Choice/Obligation
[INF-88.79-SG] M.Sc. Computer Science [Specialisation] Specialization 1 [WP] Compulsory Elective