Software Requirements Engineering

Short Name
Module Code
Module Coordinator
  • Burkhardt Renz
  • Burkhardt Renz
Short Description

Understanding the relevance of requirements analysis for the specification and implementation of software systems.

Learning Objectives

Students understand the significance of analysis of the fields of application for creating high-quality software. They can sys-tematically comprehend requirements, document and categorize concerning its functionality and quality characteristics. They can evaluate conceptual integrity of requests for one area of application. They structure requirements in a goal model and are able to derive a systems specification from the goal model.

  • Methods for the elicitation of requirements
  • Classification and documentation of requirements
  • Prioritization fo requirements with respect to the requests of stakeholders
  • Analysis of requirements
  • Building of a goal modell
  • Deriving a systems specification from the goal modell
Duration in Semester
Instruction Language
Total Effort
6 CrP; an estimated 180 hours, of which approximately 60 are spent in class.
Weekly School Hours
Method of Instruction

Vorlesung 2 SWS, Übung 2 SWS

Requirements for the awarding of Credit Points

Prüfungsvorleistung: Keine

Prüfungsleistung: Projekt (Projektarbeit mit Ausarbeitung, Präsentation der Ergebnisse)

As Needed
  • Literatur
  • A. van Lamsweerde: Requirements Engineering Wiley
  • K. Pohl: Requirements Engineering dpunkt.verlag
  • M. Jackson: Problem Frames: Analyzing and structuring software development problems Addison Wesley
  • B. L. Kovitz: Practical Software Requirements: A Manual of Content & Style Manning
  • aktuelle Forschungsarbeiten zum Thema „Konzeptuelle Integrität”