Difference between revisions of "EProcedure Back-office Backend"

From DE4A
Jump to navigation Jump to search
 
(10 intermediate revisions by one other user not shown)
Line 1: Line 1:
<div class="res-img">
+
[[File:EProcedure_Back-office_Backend.png | eProcedure Back-office Backend]]
[[File:x.png | eProcedure Back-office Backend|link=Special:FilePath/X.png]]
 
</div>
 
 
 
 
{| class="wikitable"
 
{| class="wikitable"
 
|+ Classification/description
 
|+ Classification/description
Line 12: Line 9:
 
|-
 
|-
 
| description  
 
| description  
| TODO
+
| This component implements backend functionlaity like collecting relevant data for a subscription request, determining an appropriate response to request and updating logs.
 
|-
 
|-
 
| pattern(s)  
 
| pattern(s)  
Line 18: Line 15:
 
|-
 
|-
 
|application collaboration
 
|application collaboration
|[[Cross-border Subscriptions]]
+
|[[EProcedure Back-office]]
 
|-
 
|-
  
Line 30: Line 27:
 
|-
 
|-
 
| Subscription Initiation
 
| Subscription Initiation
|  
+
| This service takes care of collecting relevant data in preparation of subscription request.
 
| [[Subscription and Notification Pattern|S&N]]
 
| [[Subscription and Notification Pattern|S&N]]
 
|-
 
|-
 
|Update Subscription Log
 
|Update Subscription Log
 +
|The subscription is recorded in the subscription log upon receiving the conformation. The subscription log serves as an overview for the DC of all their subscriptions at different DPs.
 +
|[[Subscription and Notification Pattern|S&N]]
 +
|-
 +
|Event Evaluation
 
|
 
|
 +
A service for determining the appropriate event response. Depending on the event, different courses of action are possible:
 +
 +
* Event is not relevant (can be dismissed)
 +
* Event requires a new (i.e. updated) evidence
 +
* A business response required
 +
* Some exception occurs
 +
|[[Subscription and Notification Pattern|S&N]]
 +
|-
 +
|Update Notification Response Log
 +
|This service logs the responses derived from received event notification.
 
|[[Subscription and Notification Pattern|S&N]]
 
|[[Subscription and Notification Pattern|S&N]]
 
|-
 
|-

Latest revision as of 15:30, 25 June 2021

eProcedure Back-office Backend

Classification/description
Item Description
name eProcedure Back-office Backend
description This component implements backend functionlaity like collecting relevant data for a subscription request, determining an appropriate response to request and updating logs.
pattern(s) S&N
application collaboration EProcedure Back-office

Application Services realized by this component
Application Service Description Pattern
Subscription Initiation This service takes care of collecting relevant data in preparation of subscription request. S&N
Update Subscription Log The subscription is recorded in the subscription log upon receiving the conformation. The subscription log serves as an overview for the DC of all their subscriptions at different DPs. S&N
Event Evaluation

A service for determining the appropriate event response. Depending on the event, different courses of action are possible:

  • Event is not relevant (can be dismissed)
  • Event requires a new (i.e. updated) evidence
  • A business response required
  • Some exception occurs
S&N
Update Notification Response Log This service logs the responses derived from received event notification. S&N

DE4A Common Components & BBs & MS Solutions
Component Source UC Description
xyz descr xyz [[]] Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat.
abc descr abc [[]] Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat.