Difference between revisions of "DBA 2nd iteration Solution Architecture"
Jump to navigation
Jump to search
| Line 37: | Line 37: | ||
==== Expected logical interfaces ==== | ==== Expected logical interfaces ==== | ||
| + | Describe the (logical) interfaces between the components. | ||
=== DC specific solution === | === DC specific solution === | ||
| Line 63: | Line 64: | ||
== DBA OOP TS solution == | == 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. | ||
=== Shared solution === | === Shared solution === | ||
Revision as of 10:26, 27 July 2021
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
DE4A preconditions
Design choices
Describe what WON'T be implemented for the pilot as well as design choices (see also scope section)
eIDAS and OOP TS
DBA eIDAS 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.
DC specific solution
Process realisation
Component description
Requirements
Component implementation
Expected logical interfaces
DP specific solution
Process realisation
Component description
Requirements
Component implementation
Expected logical interfaces
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.