In traditional solution development, the detailed specifications describe the functional and qualitative solution characteristics. They are based on the solution requirements and the product concept or, in the case of IT projects, the system concept and the solution architecture. They are designed in sufficient detail in terms of content and planning to form a reliable basis for the realization (development and adaptation or development and parameterization) of the solution. The detailed specifications form the basis for the creation of detailed test case descriptions.

In agile solution development, the detailed specifications largely correspond to a sprint backlog, but from the project management perspective they serve only to document the current planning of those requirements that the development team has selected in a self-organized manner and that are to be completed within the relevant iteration. The detailed specifications are continued in an iterative and incremental manner as part of the manage and control project task, so that the requirements of previous iterations that have already been completed in the document are each supplemented by a new chapter.

In traditional solution development, the content of the detailed specifications depends on the item being implemented and the specification method used. The following specification is possible on a supplementary basis:

1. Detailed requirements with
2. 1. Organizational requirements
   2. Functional requirements
   3. Quality requirement, framework condition

In agile solution development, on the other hand, the content is characterized by the agile development methods used.