Difference between revisions of "QPR Impact Analysis"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
* relation type custom attributes | * relation type custom attributes | ||
* system relations (for example activities and organization units, or activities and information elements) | * system relations (for example activities and organization units, or activities and information elements) | ||
| + | |||
| + | To run the Impact Analysis reports you need first to | ||
| + | *1. install the Impact Analysis platform (see chapter 2) | ||
| + | *2. design the reports (see chapter 3) | ||
| + | Configuration of the reports are stored in an EA/PD model. There are two strategies to set up the configuration: | ||
Revision as of 11:33, 8 June 2017
Contents
- 1 Purpose of the reporting feature 3
- 2 Reporting platform installation 3
- 3 Configuration of reports 4
- 4 Running reports and linking to them 8
- 5 Functioning principle 9
Purpose of the Reporting Feature
Impact Analysis is a reporting platform to build reports to visualize relations between entities. These connections come through several relations, which are:
- relations made with connectors
- relation type custom attributes
- system relations (for example activities and organization units, or activities and information elements)
To run the Impact Analysis reports you need first to
- 1. install the Impact Analysis platform (see chapter 2)
- 2. design the reports (see chapter 3)
Configuration of the reports are stored in an EA/PD model. There are two strategies to set up the configuration: