Requirements Engineering

Requirements Engineering

Efficiently deal with volatile and heterogenous requirements

Requirements Engineering

In the Requirements Engineering field of competence, we concentrate on developing practice-relevant approaches to efficiently deal with requirements in the early stages of software development, which is unpredictable, user-centric and often data-dominated.

The early stages of development of software-intensive systems – often simply labeled as Requirements Engineering (RE) - are a critical determinant for software quality. Many projects nevertheless still suffer from insufficient RE. One-third of software development errors are estimated to have their origin in RE and one-third of these errors are known to lead to project failures.

In a world pervaded by software, and where the majority of our daily routines are supported – if not dominated – by software-intensive systems, excellence in RE becomes key. While it’s common knowledge that various influences in industrial practices, surrounding development processes, and tools render standardization efforts of RE approaches cumbersome, much of today’s research in RE still relies on conventional and often purely academic knowledge that result in the recommendation of universal, one-size-fits- all approaches. Closing this gap between theory and practice is the high-level goal of Requirements Engineering field of competence where we strive to move from a traditional RE with universal solutions, to a next generation RE to accommodate the needs to today’s software development projects.

Research focus

We concentrate on investigating practice-relevant RE research to reproducibly control and improve quality in a requirements engineering environment that is unpredictable, data-dominated, and user-centric. To this end, our research is driven by continuous experimentation, development, evaluation, and technology transfer.

Typical issues that we address include:

  • What is the relevance of RE artifacts, how can they be structured, and what are artifacts of “sufficient” quality?
  • What does software quality mean to a particular organizational context?
  • How can data-centric techniques be used efficiently for defining the requirements and ensuring quality?
  • How can we accommodate irrational human behavior and development cultures with our RE methods?
  • How can we integrate RE into organizational processes & and cultures?

Our research activities place special emphasis on collaboration with the relevant industries and focuses on four larger (interrelated) thematic areas:

  1. Agile engineering of non-functional requirements (including concepts and tools to specify quality aspects, such as security, in agile contexts, as well as quality assurance and compliance measures)
  2. Data-driven requirements engineering (including concepts and tools for automation in RE and its quality assurance as well as RE for AI-intensive software systems)
  3. User-centric requirements engineering (including concepts and techniques for problem exploration such as design thinking and their integration into model-based engineering approaches)
  4. Model-based engineering of requirements and process integration by means of artifact orientation
Requirments Engineering
Prof. Daniel Mendez

Your contact

Prof. Daniel Mendez

+49 89 3603522 168
mendez@fortiss.org

Projects