Tidy-ups

Author: RoelantVos

design-patterns/design-pattern-data-vault-hub.md

@@ -69,6 +69,7 @@ Defining Hub ETL processes as atomic modules, as defined in this Design Pattern,
 
 ## Related Patterns
 
+- [Design Pattern - Logical - Core Business Concept](xref:design-pattern-logical-core-business-concept)
 - Design Pattern 006 - Generic - Using Start, Process and End Dates
 - Design Pattern 009 - Data Vault - Loading Satellite tables
 - Design Pattern 010 - Data Vault - Loading Link tables

design-patterns/design-pattern-logical-core-business-concept.md

@@ -0,0 +1,45 @@
+---
+uid: design-pattern-logical-core-business-concept
+---
+
+# Design Pattern - Core Business Concept
+
+## Purpose
+
+This design pattern defines a Core Business Concept (CBC) entity.
+
+## Motivation
+
+A CBC can help organizations to agree on terms and definitions. CBCs capture what is important in the business, how this is named, and how it is defined.
+
+## Applicability
+
+This pattern can be used during information/data modeling, including conducting workshops with business subject matter experts (SMEs).
+
+## Structure
+
+A Core Business Concept (CBC) represents everything that is important for the organization. These are the terms (words) used when people in the business are explaining what they do in the business, and what their process and responsibilities are.
+
+These terms used can be identified and be described, so they are not metrics or descriptive information themselves.
+
+Basically the Core Business Concepts are the words (verbs and nouns) used by the business they want to know more about.
+
+Core Business Concepts can be categorized into:
+
+* Events (including transactions)
+* Person (people and organizations)
+* Place
+* Thing (physical or Virtual)
+* Other Concepts (everything that is important, but does not fit the other categories)
+
+## Implementation Guidelines
+
+A Core Business Concept is typically implemented as a 'Hub' table using Data Vault methodology.
+
+## Considerations and Consequences
+
+N/A
+
+## Related Patterns
+
+* [Design Pattern - Data Vault - Hub](xref:design-pattern-data-vault-hub)

design-patterns/design-pattern-logical-natural-business-relationship.md

@@ -0,0 +1,36 @@
+---
+uid: design-pattern-logical-natural-business-relationship
+---
+
+# Design Pattern - Natural Business Relationship
+
+## Purpose
+
+This design pattern defines a Natural Business Relationship (NBR) entity.
+
+## Motivation
+
+A NBR assists in explaining how [Core Business Concepts](xref:design-pattern-logical-core-business-concept) interact together. This, in turn, clarifies how business processes are structured.
+
+## Applicability
+
+This pattern can be used during information/data modeling, including conducting workshops with business subject matter experts (SMEs).
+
+## Structure
+
+The Natural Business Relationship (NBR) describes how the Core Business Concepts (CBCs) are related to each other in a way the business is using them, and talking about them.
+
+If there can be multiple different ways the same concepts can be related to each other it will result in multiple business relationships.
+
+## Implementation Guidelines
+
+* A Natural Business Relationship is typically implemented as a 'Link' table using Data Vault methodology.
+* When working with multiple relationships between the same concepts, it is not advisable to 'type' these e.g. by adding a relationship type or identifier. Instead, it is preferred to model this as separate relationships.
+
+## Considerations and Consequences
+
+N/A
+
+## Related Patterns
+
+* [Design Pattern - Data Vault - Link](xref:design-pattern-data-vault-link)