- Introduction
- System context and domain model
- Architecture drivers
- System decomposition
- Quality concepts
- Further notes
Architectural concept
This section introduces a reference architecture for realizing a Data Protection Cockpit (DPC, also referred to as DSC from the German “Datenschutz-Cockpit”).
System overview
In a digital data ecosystem, data is the core asset exchanged among participants through an enabling digital platform. While data providers use the platform to provide their data, data consumers use the platform to access the data.
The DPC is a software component integrated into the digital platform where privacy-related data is exchanged among participants. It gives participants (providers and consumers) a central point for managing data-related requests (e.g., information, access grants).
Constraints
The DSC shall support legal compliance with data protection regulations (e.g., GDPR).
Stakeholders
In the context of the DPC, there are three primary stakeholders:
- The data provider: in this documentation, we refer to data providers as individuals whose data is used in the digital ecosystem of interest. They are also known as data subjects.
- The data consumer: also referred to as service providers, data consumers are companies whose digital services use data providers’ data intermediated through the platform of the digital ecosystem of interest.
- The platform operator: The company responsible for the platform that enables the digital ecosystem and, among other things, intermediates the data exchange between data providers and consumers.
 Interaktionspatterns |
2. System context and domain model  |