Difference between revisions of "EProcedure Back-office"

From DE4A
Jump to navigation Jump to search
(Created page with "The Data Logistics application collaboration consists of one high-level component realizing the functionality needed to implement all data logistics surrounding the exchange o...")
 
m
 
(15 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
The Data Logistics application collaboration consists of one high-level component realizing the functionality needed to implement all data logistics surrounding the exchange of messages between DC and DP. It offers an interface to expose its functionality to other components, e.g. evidence interchange management.
+
The eProcedure Back-office application collaboration consists of two high-level components realizing the functionality needed. It encompasses:
  
−
Graphic representations of the Data Logistics application collaboration
+
* (backend) collecting relevant data for a subscription request, determining an appropriate response to request and updating logs;
−
Graphic representation of the Data Logistics application collaboration
+
* (front-end) a UI for user tasks to analyse wrong subscriptions.
−
IM, USI and S&N
 
  
−
Application Components of Data Logistics
+
 
−
Application Component Description Pattern(s)
+
 
−
Data Exchange Shares the functionality that enables the secure exchange of messages, records, forms and other kinds of data between different ICT systems. This includes data routing, except endpoint discovery. IM, USI, S&N
+
<gallery widths="400" perrow="1" caption="Graphic representations of the eProcedure Back-office application collaboration">
−
Data Exchange Gateway The Data Exchange Component exposes an interface in order for other components to make use of it. IM, USI, S&N
+
File:EProcedure_Back-office_(S&N).png|alt=Graphic representation of the eProcedure Back-office application collaboration in the Subscription & Notification Pattern|[[Subscription and Notification Pattern|S&N]]
 +
</gallery>
 +
 
 +
{| class="wikitable"
 +
|+Application Components of eProcedure Back-office
 +
|-
 +
!Application Component!!Description!!Pattern(s)
 +
|-
 +
|[[eProcedure Back-office Backend]]
 +
|This component implements backend functionality like collecting relevant data for a subscription request, determining an appropriate response to request and updating logs.
 +
|[[Subscription and Notification Pattern|S&N]]
 +
|-
 +
|[[eProcedure Back-office Front-end]]
 +
|This component provides a UI for user tasks to analyse wrong subscriptions.
 +
|[[Subscription and Notification Pattern|S&N]]
 +
|}

Latest revision as of 11:55, 1 July 2021

The eProcedure Back-office application collaboration consists of two high-level components realizing the functionality needed. It encompasses:

  • (backend) collecting relevant data for a subscription request, determining an appropriate response to request and updating logs;
  • (front-end) a UI for user tasks to analyse wrong subscriptions.


  • Graphic representations of the eProcedure Back-office application collaboration
  • Graphic representation of the eProcedure Back-office application collaboration in the Subscription & Notification Pattern

    S&N

Application Components of eProcedure Back-office
Application Component Description Pattern(s)
eProcedure Back-office Backend This component implements backend functionality like collecting relevant data for a subscription request, determining an appropriate response to request and updating logs. S&N
eProcedure Back-office Front-end This component provides a UI for user tasks to analyse wrong subscriptions. S&N
Retrieved from ‘https://wiki.de4a.eu/index.php?title=EProcedure_Back-office&oldid=2854’