Difference between revisions of "Procedure Management"
Jump to navigation
Jump to search
| (12 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
<div class="res-img"> | <div class="res-img"> | ||
| − | [[File: | + | [[File:Procedure Management.png |Procedure Management]] |
</div> | </div> | ||
| Line 12: | Line 12: | ||
|- | |- | ||
| description | | description | ||
| − | | | + | | Application component managing the procedure, possibly spanning multiple sessions, for the user. Completing a request for a public service might take longer than one session, e.g. waiting for evidence to be exchanged between DP and DC. Furthermore, exception flows must be considered as errors may occur in the flow. Saving the (public) service request to continue at a later point in time is therefore important functionality making the user’s life easier. The component takes care of persisting the session so it can be resumed at a later point in time avoiding that the user has to start all over again but instead can take it from he/she left off. |
| + | |- | ||
|- | |- | ||
| pattern(s) | | pattern(s) | ||
| − | | [[Intermediation Pattern|IM]], [[USI]], [[VC]] | + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Verifiable Credentials Pattern|VC]] |
|- | |- | ||
| − | + | |application collaboration | |
| + | |[[EProcedure Portal|eProcedure Portal]] | ||
|} | |} | ||
---- | ---- | ||
| Line 26: | Line 28: | ||
! Application Service !! Description !! Pattern | ! Application Service !! Description !! Pattern | ||
|- | |- | ||
| − | | | + | | eProcedure Save and Resume |
| − | | | + | | Handling the session management for the user. |
| − | | [[Intermediation Pattern|IM]], [[ | + | | [[Intermediation Pattern|IM]], [[User-supported Intermediation Pattern|USI]], [[Verifiable Credentials Pattern|VC]] |
| − | |||
| − | |||
| − | |||
| − | |||
| − | | | ||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| Line 48: | Line 42: | ||
! Component!! Source !! UC !!Description | ! Component!! Source !! UC !!Description | ||
|- | |- | ||
| − | | | + | | n/a MVP? |
| − | | descr | + | | descr |
| [[]] | | [[]] | ||
| Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. | | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. | ||
|- | |- | ||
|- | |- | ||
| − | | | + | | ... |
| − | | descr | + | | descr |
| [[]] | | [[]] | ||
| Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. | | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. | ||
Latest revision as of 15:12, 14 June 2021
| Item | Description |
|---|---|
| name | Procedure Management |
| description | Application component managing the procedure, possibly spanning multiple sessions, for the user. Completing a request for a public service might take longer than one session, e.g. waiting for evidence to be exchanged between DP and DC. Furthermore, exception flows must be considered as errors may occur in the flow. Saving the (public) service request to continue at a later point in time is therefore important functionality making the user’s life easier. The component takes care of persisting the session so it can be resumed at a later point in time avoiding that the user has to start all over again but instead can take it from he/she left off. |
| pattern(s) | IM, USI, VC |
| application collaboration | eProcedure Portal |
| Application Service | Description | Pattern |
|---|---|---|
| eProcedure Save and Resume | Handling the session management for the user. | IM, USI, VC |
| Component | Source | UC | Description |
|---|---|---|---|
| n/a MVP? | descr | [[]] | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. |
| ... | descr | [[]] | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. |