inf108 - Requirements Engineering and Management (Course overview)

inf108 - Requirements Engineering and Management (Course overview)

Department of Computing Science 6 KP
Module components Semester courses Winter semester 2023/2024 Examination
Lecture
  • No access 2.01.108 - Requirements Engineering and Management Show lecturers
    • Prof. Dr. Andreas Winter
    • Florian Schmalriede
    • Dr. rer. nat. Christian Schönberg

    Wednesday: 12:00 - 14:00, weekly (from 18/10/23)
    Thursday: 12:00 - 14:00, weekly (from 19/10/23)
    Dates on Friday, 22.03.2024 09:00 - 15:00

    The basic terms and concepts of requirements analysis are taught, and methods and techniques of requirements elicitation and management are discussed and practically tested. Topics covered include: -Need for requirements elicitation and requirements management. -requirements engineering in the software development process (in the waterfall model, in the unified process, in agile development) -Requirements engineering process (participants, documents, activities) -Understand application domain (create vision, document system environment, create domain model, identify use cases) -Evoke requirements (functional and non-functional requirements, gather requirements, document requirements, validate requirements, negotiate requirements) -Manage requirements

Exercises
  • No access 2.01.108 - Requirements Engineering and Management Show lecturers
    • Prof. Dr. Andreas Winter
    • Florian Schmalriede
    • Dr. rer. nat. Christian Schönberg

    Wednesday: 12:00 - 14:00, weekly (from 18/10/23)
    Thursday: 12:00 - 14:00, weekly (from 19/10/23)
    Dates on Friday, 22.03.2024 09:00 - 15:00

    The basic terms and concepts of requirements analysis are taught, and methods and techniques of requirements elicitation and management are discussed and practically tested. Topics covered include: -Need for requirements elicitation and requirements management. -requirements engineering in the software development process (in the waterfall model, in the unified process, in agile development) -Requirements engineering process (participants, documents, activities) -Understand application domain (create vision, document system environment, create domain model, identify use cases) -Evoke requirements (functional and non-functional requirements, gather requirements, document requirements, validate requirements, negotiate requirements) -Manage requirements

Hinweise zum Modul
Prüfungszeiten

At the end of the lecture period

Module examination

Portfolio: joint report,  individual self assement report, and short oral exam

Skills to be acquired in this module

The objective of the module "Requirements Engineering and Management" is to convey the core concepts and technology of the requirements engineering and requirements management. 

The lecture follows research oriented teaching methodologies by applying these methods and techniques practically to develop an exemplary requirements definition, starting in the second part of the semester.


Professional competence

The students:

  • are aware of the necessity of requirements engineering and management
  • integrate the process of requirements engineering in the software engineering process
  • name methods and tools of requirements engineering and management
  • differentiate classical and agile methods and techniques of requirements documentation and management 
  • select and apply methods and tools from requirements engineering and management to solve given problems appropriately
  • illustrate the key tasks of the requirements engineering and management
  • name essential concepts to develop and to structure ideas
  • discuss methods of anayzing requirements and develop validation concepts

Methodological competence

The students:

  • apply methods of elicitation, documentation,validation and confirmation of requirements
  • create a comprehensive requirement document in group work
  • follow problem oriented procedures
  • abstract from concrete programming languages

Social competence

The students:

  • communicate with all stakeholders dealing with software development
  • design project visions in groups
  • collect requirements in interviews
  • design requirements for software systems collaboratively
  • contrast classical and agile requirements documents in groups

Self-competence

The students:

  • reflect their problem-solving behaviour by applying requirements engineering and management capabilities