1. Communities
1.1. A community is a grouping of other communities and domains. It often corresponds to functional divisions in a company and works best if it is aligned with the company's governance organization.
1.2. Each community can contain any number of subcommunities.
1.3. You can recognize a community by the following icon: .
1.4. Where are communities?
1.4.1. Under the Organisation tab
2. Terminology Assets, Domains, Traceability and relations
2.1. Domains
2.1.1. What is a domain?
2.1.1.1. A domain is a logical grouping of assets. It always has a domain type and belongs to exactly one community.
2.1.1.1.1. Within the Domain overall, you have domain type assets
2.1.1.1.2. Not true! Subcommunities
2.1.1.2. Domains represent logical groupings of assets. Their Domain Type determines what asset types they can hold: e.g., the Enterprise Rules and Policies domain is of the type Governance Asset Domain and therefore can only contain assets of the type Policy or Rule, both being Governance Assets.
2.1.1.3. Domains only belong to one community
2.1.2. Where are domains?
2.1.2.1. Under the browse tab, then organisation
2.2. What is an Asset?
2.2.1. An Asset is the capital building block for which you want to capture information
2.2.1.1. (in terms of attributes and relations).
2.2.2. An asset belongs to exactly one Domain and has a unique name within its Domain.
2.2.3. An Asset is the instance of exactly one Asset Type.
2.2.4. An Asset Type formally defines the semantics of an asset in terms of
2.2.4.1. attribute types that can be instantiated for it.
2.2.4.2. relation types that can be instantiated for it.
2.2.4.3. instantiate meaning
2.2.4.3.1. Technical
2.2.4.3.2. Non technical
2.2.5. In other words, it serves as a template. Asset types are assigned to one or more domain types.
2.2.6. Example Assets
2.2.6.1. 'Personal Privacy Policy' is the name of an asset of type 'Policy'.
2.2.6.2. 'Customer' is the name of an asset of type 'Business Term'.
2.2.6.3. 'CRM' is the name of an asset of type 'System'.
2.3. Relation Types
2.3.1. A Relation defines how two Assets are related to each other. A Relation is an instance of exactly one Relation Type.
2.3.2. A Relation Type formally defines the type of a relation between two Asset Types.
2.3.2.1. A Relation Type is bidirectional:
2.3.2.2. going from the header asset (source)
2.3.2.3. to the tail asset (target) of the relation and the other way around.
2.3.2.4. The source and target of a relation are both asset types.
2.3.3. Governance Asset
2.3.3.1. [ Data Quality Rule ] Classified by ➡️ Classifies [ Data Quality Dimension ]
2.3.3.2. [ Data Quality Rule ] Allowed Value Set ➡️ Allowed Value Set for [ Code Set ]
2.3.3.3. [ Data Quality Rule ] Allowed Value ➡️ Allowed Value for [ Code Value ]
2.3.3.4. [ Governance Asset ] Violated by ➡️ Violates [ Issue ]
2.3.3.5. [ Governance Asset ] Resolves ➡️ Resolved by [ Issue ]
2.3.3.6. [ Policy ] Implemented by ➡️ Implements [ Rule ]
2.3.4. Business Asset Domain
2.3.4.1. [ Business Asset ] Acronym ➡️ Acronym for [ Acronym ]
2.3.4.2. [ Business Asset ] Represents ➡️ Represented by [ Data Asset ]
2.3.4.3. [ Business Asset ] Groups ➡️ Grouped by [ Business Asset ]
2.3.4.4. [ Business Rule ] Implemented by ➡️ Implements [ Data Quality Rule ]
2.3.4.5. [ Business Term ] Code ➡️ Business Term [ Code Value ]
2.3.4.6. [ Business Term ] Allowed Value ➡️ Allowed Value of [ Business Term ]
2.3.4.7. [ Business Term ] Synonym ➡️ Synonym of [ Business Term ]
2.3.5. Data Asset Domain
2.3.5.1. Generic Data Asset Relationships
2.3.5.1.1. [ Asset ] Governed by ➡️ Applies to [ Asset ]
2.3.5.1.2. [ Asset ] Related to ➡️ Impacted by [ Asset ]
2.3.5.1.3. [ Asset ] Complies to ➡️ Governs [ Governance Asset ]
2.3.5.1.4. [ Asset ] Uses ➡️ Used In [ Asset ]
2.3.5.2. Code List Data Asset Relationships
2.3.5.2.1. [ Code Set ] Target of ➡️ Target [ Crosswalk ]
2.3.5.2.2. [ Code Set ] Source of ➡️ Source [ Crosswalk ]
2.3.5.2.3. [ Code Value ] Is Part of Codeset ➡️ Contains Code Value [ Code Set ]
2.3.5.2.4. [ Code Value ] Groups ➡️ Grouped by [ Code Value ]
2.3.5.3. Data Element
2.3.5.3.1. [ Data Asset ] Implemented in ➡️ Implements [ Technology Asset ]
2.3.5.3.2. [ Data Element ] Is Part OF ➡️ Contains [ Data Structure ]
2.3.5.3.3. [ Data Element ] Allowed Value Set ➡️ Applies to [ Code Set ]
2.3.5.3.4. [ Data Element ] Allowed Value ➡️ Allowed Value for [ Code Value ]
2.3.5.3.5. [ Data Entity ] Is Part of ➡️ Consists of [ Data Model ]
2.3.5.3.6. [ Data Entity ] Consists of ➡️ Is Part of [ Data Attribute ]
2.3.5.4. Data Structure
2.3.5.4.1. [ Data Structure ] Source of ➡️ Source [ Mapping Specification ]
2.3.5.4.2. [ Data Structure ] Target of ➡️ Target [ Mapping Specification ]
2.3.5.4.3. [ Database Table ] Database ➡️ Table [ Database ]
2.3.5.4.4. [ Table Column ] Table ➡️ Column [ Database Table ]
2.3.6. Technology Domain
2.3.6.1. [ Technology Asset ] Source System for ➡️ Source System [ Data Asset ]
2.3.6.2. [ Technology Asset ] System of Record for ➡️ System of Record [ Business Term ]
2.3.6.3. [ Technology Asset ] System of Use for ➡️ System of Use [ Business Term ]
2.3.6.4. [ Technology Asset ] System of Record for ➡️ System of Record [ Data Asset ]
2.3.6.5. [ Technology Asset ] Source System for ➡️ Source System [ Business Term ]
2.3.6.6. [ Technology Asset ] System of Use for ➡️ System of Use [ Data Asset ]
2.3.7. Issue
2.3.7.1. [ Issue ] Duplicates ➡️ Duplicated by [ Issue ]
2.3.8. Other
2.3.8.1. [Thing] Has Category ➡️Category for [Thing]
2.3.8.2. [Thing] Categorized by ➡️Categorizes [Thing]
2.4. Traceability
2.4.1. By assigning all assets to a particular Asset Type, relating them to one another with different Relation Types, and organize them in Communities and Domains, we achieve traceability. An example of traceability is shown in the diagram below:
2.4.1.1. Diagram
2.5. Icons
2.5.1. Community and Domain
2.5.1.1. Here
2.5.2. Database (Technology Asset)
2.5.2.1. Here
2.5.3. System (Technology Asset)
2.5.3.1. Here
2.5.4. Tableau Workbook
2.5.4.1. Here
2.5.5. Tableau Project
2.5.5.1. Here
2.5.6. Tableau Site
2.5.6.1. Here
2.5.7. Tableeau Server
2.5.7.1. Here
2.5.8. KPI
2.5.8.1. Here
2.5.9. Tableau Data Source
2.5.9.1. Here
2.5.10. Schema
2.5.10.1. Here
2.5.11. Table
2.5.11.1. Here
3. Organisation Diagram
3.1. Community 1
3.1.1. Domain A Gov
3.1.1.1. Gov Assets
3.1.2. Domain B Business
3.1.2.1. Explanation [Attribute] (Non-Domain Specific)
3.1.2.2. **Customer** [Business Term 1] (Type of Business Asset)
3.1.2.3. **Gender** [Business Term 2] (Type of Business Asset)
3.1.3. Subcommunity 3
3.1.3.1. Domain E Data
3.1.3.1.1. Data Assets
3.1.3.2. Domain F Tech
3.1.3.2.1. Tech Assets
3.2. Community 2
3.2.1. Domain C Data
3.2.1.1. Data Assets
3.2.2. Domain D Data
3.2.2.1. Data Assets
3.3. Example
3.3.1. Here
4. Domains and Asset Types
4.1. Asset Type Examples
4.1.1. Number 1
4.1.2. Number 2