This EClass is the root of the "functional system" description, 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.
The functional system description specifically does not cover any privacy-relevant concepts (to facilitate reuse, flexibility, stakeholder separation etc.). 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 | Cardinality | Description |
|---|---|---|---|
| functionalSystemDescriptionComment | EString | 0..1 | Informal textual comments about the functional system description. |
| functionalSystemDescriptionName | EString | 0..1 | Informal textual name of the functional system description. |
| Name | Target | Containment | Cardinality | Opposite | Description |
|---|---|---|---|---|---|
| partition | FunctionalSystemDescriptionPartition | Yes | * | Reference(s) to partitions of the functional system description. A partition is defined as a subset of the overal functional system description for which a particular data controller is responsible. The purpose of partitioning the functional system description is to explicitly capture the boundaries of responsibility of data controllers. Note that "subset" includes the entire functional system description, i.e. there may be only one data controller. Also note that partitions can be nested and/or overlapping depending on who is responsible. |