Difference between revisions of "EProcedure Back-office"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
|- | |- | ||
|[[eProcedure Back-office Backend]] | |[[eProcedure Back-office Backend]] | ||
| − | |This component implements backend functionlaity like | + | |This component implements backend functionlaity like collecting relevant data for a subscription request, determining an appropriate response to request and updating logs. |
|[[Subscription and Notification Pattern|S&N]] | |[[Subscription and Notification Pattern|S&N]] | ||
|- | |- | ||
|[[eProcedure Back-office Front-end]] | |[[eProcedure Back-office Front-end]] | ||
| − | | | + | |This component provides a UI for user tasks to analyze wrong subscriptions. |
|[[Subscription and Notification Pattern|S&N]] | |[[Subscription and Notification Pattern|S&N]] | ||
|} | |} | ||
Revision as of 12:59, 4 June 2021
The eProcedure Back-office application collaboration consists of two high-level component realizing the functionality needed.
- Graphic representations of the eProcedure Back-office application collaboration
.png)
| Application Component | Description | Pattern(s) |
|---|---|---|
| eProcedure Back-office Backend | This component implements backend functionlaity 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 analyze wrong subscriptions. | S&N |