DBA 2nd iteration Solution Architecture

Introduction

Approach: we follow the SA as was done for Intermediation (1st iteration)

Scope and focus

• Within scope
  • Modify DO/DE Mocks for S&N en Lookup patterns
  • Common component voor Cross-border subscriptions (optional for MS to use, i.e. not mandatory)
  • Event Notification + Evidence Lookup flavour, in line with PSA 2nd iteration
• Outside scope
  • Resend a subscription request in case of an error (instead the possibility to inspect the logs and manually resend a request is deemed sufficient (MVP))
  • Include the Evidence in the notification (instead pure notification + lookup)
  • Attribute Lookup

Design choices

Describe what WON'T be implemented for the pilot as well as design choices (see also scope section)

DBA eIDAS solution

Shared solution

Process realisation

Mapping processes/activities to application services and components (PSA --> tables).

Component description

Classify components: DE/DO/Common component.

Requirements

Describe the requirements for application services.

Component Implementation

Describe the implementation of the components.

Expected logical interfaces

Describe the (logical) interfaces between the components.

DBA OOP TS solution

Maybe this is the place to insert explanation of the subscription application collaboration (and notification?), i.e. front-end/back-end w.r.t. notifications.

The shared solution for the OOP TS consists of all common functionality of the OOP technical system. Most of the common OOP TS components need to be implemented by the data requestor and data transferor, although the OOP TS uses central components as well.

Shared solution OOP TS

Image might need an update

DC-specific solution

Probably makes sense to split (two images) in notification and subscription