Specification of a requirement as a prime example for implementation

Problem

We need first requirements for the backlog that are suitable for development.

Goal

A vertical breakthrough is suggested for quick specification. This is based on the rough scope of the target system (T approach). The necessary requirements for a selected functional area are determined and formulated using an example.

ACs

• The scope of the system business context has been roughly defined, see #165 (closed)
• A step in the subprocess was selected within the scope for the functional area. This step is a use case. Example: use case “Citizen sends requested document to authority” in the subprocess “Follow-up communication.” > prepared for CoP RE 2025-09-11
• The use case contains functional requirements. These are formulated as examples. > preparated for CoP RE 2025-09-11
• The attribution of a requirement is oriented towards the ZAPuK methodology. > prepared for CoP RE 2025-09-11
• The requirements are linked to already known quality requirements and user requirements. An example of this could be the deletion of user data belonging to private individuals.
• The requirements are referenced to relevant requirements from the "Leistungsbeschreibung" or ZAPuK requirements list.
• The example for the requirement has the maturity level for the creation of implementation tickets.
• The procedure and type of specification can be used to describe further requirements.

Notes/ resources

As stated in CoP RE 2025-09-11, we need to work out the requirements sources for the deletion concept. The open tasks for this issue will therefore be continued later.

Who needs to be involved / informed

• reviewers: tbd
• involved: tbd
• informed: tbd