The solution requirements, as a crucial HERMES outcome, include the specialist and technical requirements, but also other elements such as characteristics, functions, optimizations, and defect corrections, legal as well as solution-relevant and regulatory requirements that the future system or product must fulfill. They include the business requirements, operational requirements, support requirements, and security requirements that flow directly into the solution.

In traditional solution development, the solution requirements are prepared in the concept phase on the basis of the study and the situation analysis in the final level of detail and are successively updated during solution development via change management as needed.

In agile solution development, the solution requirements are prepared for the first time on the basis of the study and the situation analysis in the execution phase in the form of an authoritative initial product backlog. The solution requirements correspond to a list of unambiguously prioritized requirements, subdivided into releases as needed, which are ordered according to business-specific or other aspects and logical dependencies important for the project. They are continuously updated as part of self-organized agile development. As a HERMES outcome, they are updated iteratively and incrementally, and they consequently have only informative and documentary character.

The content is strongly influenced by the project and the approach.

Possible content:

1. Overview of all orders (possibly subdivided by releases)
2. Releases
3. General description
4. 1. Business and systemic context
   2. Impact/benefit
   3. Use case
5. Requirement with
6. 1. Priority
      (e.g. according to requirement type, overall context, importance, urgency, etc.)
   2. Designation/title
   3. Order/identification number
   4. Product/system overview
   5. Objective to be achieved
   6. Specialist description
   7. 1. Free text
      2. Organization, function, quality, etc.
      3. For the system:
         Requirements for the operating concept, solution architecture, data archiving, migration concept, from the ISDP concept
      4. Expectations of the user
      5. Consultation with the user
   8. Function description
   9. Benefits/added value
   10. Business relevance
   11. Acceptance criteria
   12. Product compliance
   13. Realization date
   14. Estimated outlay
   15. Test criteria
   16. Other aspects and criteria