Overview of important quality properties affecting architecture

Description

We need to know, what are the most important quality properties regarding our project and what knowledge is missing there for us to make adequate decisions.

This is important, because if we don't consider them properly the project could fail or we could introduce significant additional expenditure to include / fix them.

Background information

• Requirements Concept Board
• List of requirements source: #248 (closed)
• see list of related issues linked down below
• Requirements uIDs: LB_46

Acceptance criteria

• An overview of important quality properties we need to consider in order to be compliant with existing legislation is documented as a mindmap using mermaid (in GitLab) (see https://github.com/mermaid-js/mermaid/blob/develop/docs/syntax/mindmap.md as an example).
• The overview is provided as a table with at least the following columns: topic/area (e.g. GDPR, security requirement, a11y, etc.), description (what do we need to keep in mind here inkl. at least 1 example for each property), sources (existing legislation and other requirement sources that are important here), status (did we already do something here?), and list of existing issues (that deal with this topic)

Priority

• low (sometime in the future...)
• medium (important for the current project phase, no project delay yet according to sprint planning)
• high (important for the next sprint)
• utmost urgent (needs to be resolved during the current sprint)

History (documented by team::requirements)

• 2025-09-xx: ...

Next steps (defined by team::requirements)

• Create a document that gives an overview of the most important quality properties (e.g. Interaction Capability (Usability, a11y, ...), Functional Suitability (OZG, GDPR,...), ...)
• Describe the relevance to the project for each quality property
• Give at least one example for each quality property how it affects other