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-20 09:00:00 +00:00
parent 1af6f17dc4
commit f15912e4c6
1 changed files with 1 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
application/harmonize-data.md
View File

@@ -1,10 +1,9 @@
# Corporate Data Model # 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 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). 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**. Different names for entities and attributes **MAY** be used **ONLY** if the **CDM** is not including them. If a different name is introduced then it **MUST** be included in the **CDM**.
Consistency of the names of entities and attributes across the whole application **MUST** be maintained. Consistency of the names of entities and attributes across the whole application **MUST** be maintained.