Design a system concept


The system requirements and system architecture are compiled with the system concept. They form the basis for the procurement or realization of the system.

Basic idea

The following outcomes are produced:

  1. The situation analysis is more in-depth than the study analysis.
  2. The system requirements substantiate the requirements resulting from the study.
  3. The system architecture describes the IT system with its components and structure (architecture), as well as the interfaces with peripheral systems. The system architecture also describes the relationship between the IT architecture and the business processes.
  4. Detailed studies supplement the system architecture. They describe solution concepts for specific issues (e.g. user administration and access rights, archiving).

Options are established and evaluated in this task. The options selected are combined in the system architecture to form a comprehensive solution.


System requirements and the system architecture are designed in sufficient detail in terms of content and planning that they form a reliable basis for the procurement or realization of the system. They are included in the project specifications and form the basis for the decision on acceptance.

The level of detail varies depending on the critical nature of a system element.

The system requirements are fleshed out further in the form of detailed specifications in the implementation phase.

The system architecture forms the basis for the system architecture decision. It is fleshed out further in the implementation phase.


  1. Critically question the framework conditions from the project order and analyze the influences on the project's success
  2. Check whether the situation analysis in the study was sufficiently comprehensive; if necessary, supplement it and go into more detail
  3. Flesh out requirements and document them as system requirements
  4. Create the system architecture
  5. Create detailed studies and integrate them into the system architecture or reference them as appendices
  6. If necessary, check the system architecture with prototypes (test installation)
  7. Coordinate the outcomes with the stakeholders