Difference between revisions of "EProcedure Rules Engine"
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
|- | |- | ||
| − | |} | + | |} |
---- | ---- | ||
Revision as of 12:56, 22 March 2021
| Item | Description |
|---|---|
| name | name of AC |
| description | descr op comp. |
| pattern(s) | IM, USI, VC |
| Application Service | Description | Pattern |
|---|---|---|
| Procedural requirements determination | The DC determines the applicable requirements for a procedure. This service supports this requirements determination and bundles UI and logic to do so. | IM, USI VC |
| Requirements/evidence matching | The DC matches the requirements with available evidence. This service bundles UI and logic to match the requirements with available evidence in order to establish if there is a delta (missing evidence).
The first use of this service takes place after establishing the procedural requirements (i.e. evidence already available in the DC MS), the second use is after evidence collection to establish completeness (i.e. then also including exchanged evidence). |
IM, USI, VC |
| Component | Source | UC | Description |
|---|---|---|---|
| xyz | descr xyz | DBA (UC1) | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. |
| abc | descr abc | SA (UC1) | Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin suscipit mauris eu dui aliquet, feugiat porttitor eros placerat. |