Difference between revisions of "EProcedure Back-office"
Jump to navigation
Jump to search
m (typo) |
m |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | The eProcedure Back-office application collaboration consists of two high-level | + | 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; | * (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 | + | * (front-end) a UI for user tasks to analyse wrong subscriptions. |
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
.png)
| 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 |