Fraud Case (CDQ.POOL)
Fraud case
Jump to navigation
Jump to search
Name Name of a concept, e.g. a data model concept. In contrast to terms, the name does not depend on a given context, e.g. a country-specific language. | Fraud Case |
---|---|
Description Informal and comprehensive human-readable definition of a concept. | A set of Information about a banking data fraud that was recognized by one of the CDL partners. Typically, such a fraud comprises an invoice from a known and "real" supplier that was intercepted by a scammer who changed e.g. the bank data of the invoice to a bank account that is under his control. In most cases, such an attack is backed by additionally hacking email accounts or telephone systems. The latter enables the attacker to answer requests regarding changed banking data in the name of the supplier. |
Part of Hierarchical relation between two concepts of the CDQ Data Model. | Data source CDQ.POOL |
Technical key Defines a unique key by which e.g. data model concepts can be referenced in a technical integration context. These keys are unique in the CDL context. | FRAUD_CASE
|
Parent concept Hierarchical relation between two concepts of a data model, e.g., the CDQ Data Model. | No parent concept, this is the root concept. |
Cardinality Cardinality of data model concepts.<br/><code>ZERO_OR_ONE</code>: Optional, but max. 1 instance related to its parent.<br/><code>EXACTLY_ONE</code>: Exactly 1 instance related to its parent.<br/><code>ZERO_OR_MORE</code>: Optional, multiple instances related to its parent may exist.<br/><code>ONE_OR_MORE</code>: Mandatory, multiple instances related to its parent may exist. | ZERO_OR_MORE
|
Data type Data type of a data model concept, i.e., <code>ARRAY</code>, <code>BOOLEAN</code>, <code>DATE</code>, <code>ENUM</code>, <code>INTEGER</code>, <code>OBJECT</code>, or <code>STRING</code>. | n/a |
Path JSON Path to identify attributes in a data item. | fraudCase
|
Concept role The role of a Category:Data model concept in the tree structure of a data model.<br/><code>ROOT</code>: Root concept in a data model, i.e., no parent concepts.<br/><code>NODE</code>: Structure concepts in a data model, i.e., parent and child concepts.<br/><code>LEAF</code>: Leaf concept in a data model, i.e., no child concepts, provides the effective data values.<br/> | ROOT
|
Mapping |
Sub concepts