Module Handbook

  • Dynamischer Default-Fachbereich geändert auf INF

Module INF-30-52-M-7

Software-Engineering 2 (M, 8.0 LP)

Module Identification

Module Number Module Name CP (Effort)
INF-30-52-M-7 Software-Engineering 2 8.0 CP (240 h)


CP, Effort 8.0 CP = 240 h
Position of the semester 1 Sem. in WiSe/SuSe
Level [7] Master (Advanced)
Language [DE/EN] German or English as required
Module Manager
Area of study [INF-SE] Software-Engineering
Reference course of study [INF-88.B16-SG] M.Sc. Socioinformatics
Livecycle-State [NORM] Active


Module examination: joint oral examination on the two chosen courses.

Proof of performance: exercise certificates in the two selected courses.


Type/SWS Course Number Title Choice in
Presence-Time /
SL SL is
required for exa.
PL CP Sem.
2V+1U INF-31-31-K-5
Software Project and Process Management
WP 42 h 78 h
- PL1 4.0 SuSe
2V+1U INF-31-52-K-6
Product Line Engineering
WP 42 h 78 h
- PL1 4.0 WiSe
2V+1U INF-31-53-K-6
Empirical Model Formation and Methods
WP 42 h 78 h
- PL1 4.0 SuSe
2V+1U INF-33-56-K-6
Quality Management and Quality Assurance of Software
WP 42 h 78 h
- PL1 4.0 WiSe
  • About [INF-31-31-K-5]: Title: "Software Project and Process Management"; Presence-Time: 42 h; Self-Study: 78 h
  • About [INF-31-31-K-5]: The study achievement "[U-Schein] proof of successful participation in the exercise classes (ungraded)" must be obtained.
  • About [INF-31-52-K-6]: Title: "Product Line Engineering"; Presence-Time: 42 h; Self-Study: 78 h
  • About [INF-31-52-K-6]: The study achievement "[U-Schein] proof of successful participation in the exercise classes (ungraded)" must be obtained.
  • About [INF-31-53-K-6]: Title: "Empirical Model Formation and Methods"; Presence-Time: 42 h; Self-Study: 78 h
  • About [INF-31-53-K-6]: The study achievement "[U-Schein] proof of successful participation in the exercise classes (ungraded)" must be obtained.
  • About [INF-33-56-K-6]: Title: "Quality Management and Quality Assurance of Software"; Presence-Time: 42 h; Self-Study: 78 h
  • About [INF-33-56-K-6]: The study achievement "[U-Schein] proof of successful participation in the exercise classes (ungraded)" must be obtained.

Examination achievement PL1

  • Form of examination: oral examination (30-45 Min.)
  • Examination Frequency: each semester

Evaluation of grades

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


Based on the contents of the lecture "Foundations of Software Engineering", which explains the technical aspects, this lecture explains how to establish and realise a successful project management and quality assurance (QA). On the basis of practical examples, it shows:
  • how large projects are planned,
  • which elements a project plan contains,
  • which methods exist for project management and QA,
  • how project management and QA are different to each other and how they complement one another.

Topics of the lecture:

  • Definition of project management and QA
  • Basic terms of software project execution
  • Process and quality models as a basis for systematic project management and QA
  • Principles of project and process management
  • Principles of measurement and evaluation
  • Techniques / methods / tools for supporting project management and QA
  • Examples from practical projects
  • Basic concepts of product lines (commonality, variability, decisions)
  • Role and concepts of architectures (styles, patterns, and scenarios)
  • Implementation technologies (MDA, Preprocessors, aspect-orientend development)
  • Technology transfer (Adaptation and adoption of technologies, migration strategies)
  • Reverse-Engineering (basic and detailed analyses, reconstruction of architectural views and structures)
  • Domain analysis (product map, management of varying requirements and system characteristics)
  • Definition of the basic terms of empirical / experimental software engineering
  • The procedure of experimentation
  • Formulation of hypotheses
  • Design of empirical studies
  • Acquisition, validation and analysis of data
  • Interpretation of data
  • Empirical modelling
  • Examples of concrete empiric studies
Quality management and quality assurance should always be considered together. Quality management deals with organisational aspects; quality assurance with technical content. Insufficient quality can have negative consequences. Such consequences range from economic losses to human lives being endangered. Demonstrating compliance with quality management standards and the use of appropriate quality assurance techniques is therefore very important.

The course covers important aspects of software quality management and software quality assurance:

  • Techniques for software quality management and software quality assurance are introduced and their characteristics (advantages, disadvantages, limitations) are discussed.
  • Furthermore, practical examples of analysis and testing methods are covered.

Competencies / intended learning achievements

The students gain a deeper insight into self-chosen topics of software engineering. The knowledge in this area can reach up to the state of the art. Students can thus follow the state of the art in research.

Upon successful completion of the module, students will be able to

  • explain principles, methods and tools of software engineering
  • evaluate process and quality models,
  • assess the advantages and disadvantages of different methods, tools and models
  • derive the transferability of these concepts to practical problems
  • derive which parameters influence the success of project management in practice.


  • Ernest Wallmüller: "Software-Qualitäts-Management in der Praxis", Hanser-Verlag, 2001.
  • Peter Liggesmeyer: "Software-Qualität: Testen, Analysieren und Verifizieren von Software", Spektrum-Verlag, 2002.
  • Pankaj Jalote: Software Project Management in Practice Addison-Wesley Professional, 2002.
  • Hughes, Cotterrell: Software Project Management, McGraw-Hill Publishing Co., 2002.
  • A Guide to the Project Management Body of Knowledge (Pmbok Guide) - 5th Edition - Project Mgmt Inst, 2013.
  • Adam Trendowics: Software Cost Estimation, Benchmarking, and Risk Assessment, Springer, 2013.
  • Atkinson et. al., Component-based Product Line Engineering with UML. Addison-Wesley 2001.
  • Weiss, Lai: Software Product-Line Engineering. A Family-Based Software Development Process Addison-Wesley, 1999.
  • Clements: Software Product Lines. Practices and Patterns. Northrop, 2002.
  • Victor Pankratius: Product Lines for Digital Information Products, Universitätsverlag Karlsruhe, 2007.
  • F. van der Linden, K. Schmid und E. Rommes: Software Product Lines in Action: The Best Industrial Practice in Product Line Engineering. Springer, 2007.
  • Pohl, Böckle, van der Linden: Software Product Line Engineering: Foundations, Principles and Techniques, Springer, 2005.
  • Juristo, N., and Moreno, A.: Basics of Software Engineering Experimentation, Kluwer Academic Publishers, 2001.
  • Prechelt, L.: Kontrollierte Experimente in der Softwaretechnik: Potenzial und Methodik, Springer Verlag Berlin Heidelberg 2001.
  • C. Wohlin, P. Runeson, M. Höst, M. C. Ohlsson, B. Regnell and A. Wesslén, "Experimentation in Software Engineering", Springer, ISBN 978-3-642-29043-5, 2012.
  • Boehm, Rombach, Zelkowitz (Eds): Foundations of Empirical Software Engineering, Legacy of Victor R. Basili, Springer Berlin Heidelberg New York, 2005.
  • Basili, Trendowics, Kowalczyk, Heidrich, Seaman, Münch, Rombach: Aligning Organizations Through Measurement.The GQM+Strategies Approach, Springer, 2014.
  • Liggesmeyer P., Software-Qualität (2.Aufl.), Heidelberg: Spektrum Akademischer Verlag, 2009
  • Spillner A., Linz T., Basiswissen Softwaretest (6. Aufl.), Heidelberg, dpunkt.Verlag, 2019
  • Myers G.J., Badgett T., Sandler C., The Art of Software Testing (3rd Edition), Hoboken, John Wiley & Sons, 2012

Requirements for attendance of the module (informal)


Requirements for attendance of the module (formal)


References to Module / Module Number [INF-30-52-M-7]

Course of Study Section Choice/Obligation
[INF-88.B16-SG] M.Sc. Socioinformatics [Compulsory Modules] Computer Science [P] Compulsory