The additional ( first ) slide pack shows the JOSIF tool chain which gives a good insight to what a more modern transformation tool IDE would need to do.
Original Message:
Sent: Jan 22, 2024 11:46
From: Dave Milham
Subject: Use of SID to define data model in ODS
I contributed the Slides to the Component and Canvas team that hosts the ODA Production and modeling teams
- TAC-810 MTOP MTOSI JOSIF mapping guidelines from SID to Interface data models
- NOTE This set of slides was developed for an MTOSI Josif workshop in 2014. the material was presented publicly by HP based on work in the MTOSI JOSIF team So I think the content is RAND but has a copyright notice which I think is on the specific slides not the content or concepts.
------------------------------
Dave Milham
TM Forum, Chief Architect
Original Message:
Sent: Jan 22, 2024 08:54
From: Shishil Shetty
Subject: Use of SID to define data model in ODS
Hi David,
Thank you for your response, (1) and (2) from your response is exactly what I plan to do. wrt modelling relationships even I feel attribute is the easier way of doing it. I do see some entities defined in SID related using classes though. do you have any pointers as to which approach for modelling relationships can be taken in which situation -> 1:1 relationship as attribute and 1:N as entity?
Regards,
Shishil
Regards,
Shishil
------------------------------
Shishil Shetty
Epam Systems Ltd
Original Message:
Sent: Jan 19, 2024 23:30
From: Fazhong (David) Deng
Subject: Use of SID to define data model in ODS
Based on our experience in using SID (which is not in DWH ODS), there few things you might wanna do:
1. find the right pattern and classes in SID
2. extend the SID by extending your classes or add more attributes as desired
Mapping non-SID data model data to SID data model can be complicated but it can be done even the most difficult ones. Personally, I would first define how to handle relationship: should use relationship by a class or using attribute? When I design and implement our SID module in our product, I support both but during solution development I found that using attribute is much simpler in terms of software complicity (software itself and database design if you use database). Once you have designed your SID extension the mapping would be straightforward using the mapping rules designed.
This is a big topic and whatever you choose to do will have long term implications in your system so spend enough time to design it will return very good benefit to you. However, the benefits are probably to prevent bad results would happen down the road and not likely to be extra values besides you will have good system.
Good luck.
------------------------------
Fazhong (David) Deng
OSSEra
Original Message:
Sent: Jan 18, 2024 08:54
From: Shishil Shetty
Subject: Use of SID to define data model in ODS
Hi,
Has anyone come across a scenario where they have used SID models to define data model for the ODS layer in a data warehouse architecture. My question was,
- Is it recommended to use SID models to model entities in the DWH ODS layer if the operational data in the source systems is not necessarily compliant with SID?
- If there are entities which are not part of the standard business entities defined in SID how do we model such entities
Regards,
Shishil
#AIandData
------------------------------
Shishil Shetty
Epam Systems Ltd
------------------------------