Mirrors/api-guidelines
1
0
Fork 0
mirror of https://github.com/adidas/api-guidelines.git synced 2025-10-25 15:19:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updates application/harmonize-data.md

Browse Source 
Auto commit by GitBook Editor
This commit is contained in:
apidesigner
2017-06-19 09:31:47 +00:00
parent 124b99744f
commit d9c7984012
2 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
SUMMARY.md
View File

@@ -25,6 +25,7 @@
* [Problem Detail](message/error-reporting.md)
* [Foreign Key Relations](message/foreign-key-relations.md)
* [Application](application/README.md)
* [Corporate Data Model](application/harmonize-data.md)
* [Common Data Types](application/common-data-types.md)
* [Evolution](evolution/README.md)
* [Naming Conventions](evolution/naming-conventions.md)

11
application/harmonize-data.md Normal file
View File

@@ -0,0 +1,11 @@
# Corporate Data Model
The design of application data model **MUST** consider the application use cases as well as the upstream and downstream systems use cases.
The design of the data model of an application **MUST** consider the [adidas Corporate Data Model](https://collaboration.adidas-group.com/sites/CS-GDM/Corporate Data Dictionary/Data Dictionary.htm) (internal link).
Different names for entities and attributes **MAY** be used **ONLY** if the **CDM** is not including them. If a different name is introduce then it **MUST** be included in the **CDM**.
Consistency of the names of entities and attributes across the whole application **MUST** be maintained.