| Business Data Model Data Model |
| Description | A group of objects that form a tree structure in which parent concepts on higher levels branch out into child concepts on lower levels. For example: Balanced hierarchy: Concept types within a level are logically consistent. All branches have the same depth and no levels are skipped. For example a calendar hierarchy with years, quarters, months, weeks and days as levels. Unbalanced hierarchy: Levels are not consistent across branches. Branches can have different depths. For example an organization chart with managers and employees where not all the employees reporting to the same manager have functionally equivalent positions. Ragged hierarchy: Concept types within a level are logically consistent. Branches can have different depths and levels can be skipped on some branches. For example an administrative division hierarchy with country, state, county, and city. |
| Attributes | |
Depth Level Num |
|
Hierarchy Type |
|
| Generalization | |
Generalization1 |
|
| Dependencies | |
NONE |
|
| Reverse Dependencies | |
|
|
| Attribute Details |
Depth Level Num
| Description | Indicates the number of levels in the hierarchy. |
| Data Type | Standards - Data Domains.ddm/Data Domains/Number Integer [INTEGER] |
| Is Part Of PrimaryKey | false |
| Is Required | false |
| Is Derived | false |
| Is Surrogate Key | false |
Hierarchy Type
| Description | Indicates the nature of the hierarchy. For example: Legal Hierarchy Management Hierarchy Reporting Hierarchy Administrative Divisions Hierarchy |
| Data Type | Standards - Data Domains.ddm/Data Domains/Enumeration [VARCHAR(20)] |
| Is Part Of PrimaryKey | false |
| Is Required | false |
| Is Derived | false |
| Is Surrogate Key | false |
| Generalization Details |
Generalization1
| Supertype | Group |
| Subtype | Hierarchy |
| Transform As | TABLE |
| Business Data Model Data Model |