Prepare solution requirements

Purpose

All relevant requirements for the solution and its deployment, operation, utilization, etc., are prepared.

In traditional solution development, the requirements form the basis for the development of the solution architecture or product concept.

In agile solution development, the fleshed out and prioritized requirements are the cornerstone for their successive continuation and completion.

Basic idea

The following outcomes are produced:

  1. The situation analysis is more in-depth than the status report from the study and shows the need for action.
  2. The solution requirements build on the objectives from the study and from the execution order, flesh out the rough requirements from the study, and expand on them based on the need for action identified in the situation analysis.

The formulated solution requirements are neutral with regard to the solution.

HERMES-specific

The solution requirements are designed and prioritized in sufficient detail in terms of content and planning to form a reliable basis for the development or procurement of the system. If the system is procured, the solution requirements are incorporated into the specifications.

In traditional solution development, the accepted solution requirements are updated, where needed, only by way of change management.

In agile solution development, the level of detail of the initially defined solution requirements varies depending on the criticality of a system element. The solution requirements are then continuously updated as part of the manage and control project task.

Basis/prerequisites

  1. Study
  2. Legal basis analysis
  3. Procurement analysis
  4. Protection needs analysis
  5. Execution order
  6. Stakeholder list

Activities

  1. Critically question the framework conditions from the execution order and analyze the influences on the project's success.
  2. Comprehensively supplement the status report from the study and go into more depth.
  3. Flesh out requirements, document them as solution requirements, and prioritize them clearly.
  4. Coordinate the solution requirements with the stakeholders.

Outcomes

  1. Situation analysis
  2. Solution requirements

Relationships

Module Task Task responsibility Outcome Involved in creation of outcome
Product Prepare solution requirements User representative Situation analysis User representative , Business analyst
Solution requirements User representative , Business analyst
IT system Prepare solution requirements User representative Situation analysis User representative , IT architect, Business analyst
Solution requirements User representative , IT architect, Business analyst