The scene: We have created our Conceptual data model using a technical term diagram. To ensure that the concepts are integrated into the process maps and all their relationships are captured I wanted to create a cluster pick list from these concepts in an IE Data Model. These clusters could them be used in the epc models capturing the end to end processes.
The problem: I cannot create the pick list as ARIS will not allow me to create the IE Data model using the concepts from the technical term diagram. Now I have had to create a mirror model pick list in IE Data model which has the names and definitions of the concepts in the pick list but not the relationships.
What do I need to do to be able to link the Conceptual data model in the technical term diagram to the IE data model pick list which can then be used in the epc? Do I need to re-model the Data model in a different model? Which one?
Sakari Lehtonen on
Scott, great to see You to apply ARIS in data modelling also, in addition to process modelling. ARIS enables both, this being one of the most important differentiators and advantages ARIS has. The business language consists of two equal parts completing each other, process language and data language. Some people argue, processes are most important, some others stick on shared data. Needless to argue, both are needed. ARIS has still one advantage, ARIS enables to connect process and data descriptions seamless way. Your question also relates to that, how to combine process and data descriptions best practice way?
ARIS enables data modelling on two abstraction levels, conceptual modelling using Technical terms diagram, and logical data modelling using IE data model, like You mention. Now you ask, how to link these two, is a kind of mirroring or remodelling needed? Let me reply by considering various modelling requirements ARIS customers have. Some customers emphasize conceptual data modelling, close to business processes and without any need to proceed into more precise logical data modelling. For those customers, the Technical terms diagram is the right solution. It provides all the suffcient constructs to express the data language part at the same conceptual level together with processes.
Some customers emphasize the logical data modelling, then the IE data model is the right solution. So again, ARIS enables both requirements, serving a wide variety of customers. The IE data model provides the full scale proven entity-relationship modelling, originating from early 80'ies, and being still a valid and widely applied method. All the modern data modelling constructs, like data domain hierarchies, business object descriptions, all those can be expressed by applying the flexible data cluster concept, just like You mention.
Finally my reply, and my recommendation, is to avoid overlapping modelling. At best, a certain customer selects, their method is to apply logical data modelling, and to give up conceptual modelling. Another customer selects conceptual modelling, and they have no need to apply logical data modelling. If you select both, you have to guarantee resources as well, who can model and update both models, even to maintain the links in between and that mirroring you refer. My experience is, that rare companies have resources to maintain both conceptual and logical data models. Most often customers select logical data modelling today. So, my recommendation is to concentrate into logical data modelling. You can keep conceptual data models as well, or gradually give up. To establish data models first time, in transition phase you have certain remodelling to do, but later on you will have just logical data models to maintain.