This EPackage includes concepts to describe a "functional system", i.e an IT landscape with (privacy-relevant) information flows between data sources and data recipients. A particular concept is that the overall functional system description can be partitioned into different partitions relating to a particular data controller. Note that partitions can be nested and can overlap.
This package specifically does not cover any privacy-relevant concepts. However, there is (probably) little point in specifying any information flows that are not privacy-relevant, unless specific other model analyses are done.
| Name | Type | Description |
|---|---|---|
| InformationType | null | This EEnum categorizes the information type. |
| Name | Description |
|---|---|
| FunctionalSystemDescription | This EClass is the root of the "functional system" description, i. |
| FunctionalSystemDescriptionPartition | Defines partitions of the functional system description, characterized by data controllers and information flows (often across partition boundaries). |
| InfoFlowDestination | This EClass defines the information flow destination. |
| InfoFlowSource | This EClass defines the information flow source. |
| Information | This EClass defines the information flow's information. |
| InformationFlow | This EClass defines an information flow, consisting of a source, a destination, the information, and privacy protection mechanisms applied to the information flow. |
| Name | Description |
|---|---|
| functional_system_description_concepts_Diagram0 |