Is it possible to generate Database Scripts as a result of Physical Data modeling?
So that I can use those scripts to genrate the Database Structure for the Data Models which I have modeled in ARIS. If Yes than how? Please suggest me the approach.
As per my understanding if you want to do Data Modeling at Conceptual or Logical level then eERM models are the best options (however this depends on number of others factors as well), but if you want to do Physical Modeling than I might need to use UML models.
Please correct me if I am wrong somewhere.
Hi Parveen,
Great topic! Thank you for raising it. As far as I know there is no such option and according to me that is a very big drawback of ARIS. The whole point of logical data modeling is lost if you cannot create DB script out of it. And as it is a standard capability of much simpler tools like Rational and Erwin, it evades me why it is missing in ARIS. Well, some conceptual data modeling within EA is fine and integrating data within processes as quite useful. Then for logical modeling, I’m quite happy with UML Class Diagrams in ARIS. But stopping there and going to another tool only for a DDL is quite inefficient. Anyway, I discussed this in LinkedIn some 6 months ago and the advice was to use the interfaces to other tools. I really hope that things have changed or there is something in the pipeline.
I’m looking forward to reading next comments in this discussion.
Ivo
Hi folks,
actually it is not true that such scripts do not exist. However, it is true that they are not a standard feature shipped with ARIS. There have been many projects where such scripts were used to generate data descriptions. If you are interested in such scripts, one option might be to contact your local sales representative so that he can establish the necessary contacts to our customized solution consultants.
Regards,
Sebastian
Hi,
In general, I have not seen much write-ups on how to use ARIS for data mgmt... so this is a good avenue to learn more.
I am interested to find out how others are using ARIS for describing their ER models, data dictionary, subject areas and code tables.
The features that I have seen in ARIS seems to suggest that it is quite limited for those using the ER models. Specifically, some things which I can't seem to do are:
a. Not being able to display the attributes with the entity in the ER models
b. Not able to define and display data dictionary in tabular form
c. Not being able to capture domain values and enumerations for data elements
Any advice and pointers to the right info will be much appreciated.
thanks.
Hi All,
Thanks a lot for your expert views and the overwhelming response for the topic.
@ Ivo: I am also very much in line with your thinking, I feel, creating DDL or Database Scripts is a sure shot value addition to your efforts put up for Data modeling. I am surprised to know that such an important feature missing in ARIS (Standard Platform).
Your LinkedIn discussion is also very helpful to understand this limitation.
@Sebastian: Just out of curiosity, could you share the reason behind this feature missing in the ARIS standard features set, offcourse if any :)
Regards
Parveen
Hi HC,
Use of ER models depends upon the level of details we want to put in. There are lots of data objects available in ARIS like Entity/Entity types, D attribute etc. which we can use to define our ER models. You can also use Information carrier and Knowledge Category as per your requirements.
As per my understanding Technical Terms Model is the best way to define Data Dictionary. To show subject areas we can use Cluster which may be described in more detail by entity or relationship types.
We can use Entity-Attribute models (describing for D attributes).
Regards
Parveen
Thanks for the inputs, Parveen..
Can anyone tell me if the technical terms model captured in ARIS can be published as a table in Biz Publisher.
It is just not natural to see a glossary of terms in a model where most of the accompanying data are not shown.
thanks
@Parveen: Good question why such export scripts are not a standard feature. I think if we would add them to the standard products, we would need to add several more features to make the offering complete (some kind of ARIS Data Modeller). So far, there were other features more requested by our customers, so we have not done there the investment.
Regards,
Sebastian
@Sebastian: Thanks for your prompt response. You have very well addressed my concern.
I am quite excited to see "ARIS as a Data Modeller".
One more concern, I haven't found much write up about adding values to Process Models with Data Objects (Data View). However you and Ivo discussed about the suitability of data models in other discussions, which is very helpful.
I am interested to know more about the AS-IS capabilities of ARIS and how ARIS can address the various Data Modeling scenarios (Something more about suitability of Data Objects).
Scope of my question may be very vast, but I know you can brief me with your thoughtful replies.
I really appreciate your documentation.
Thanks & Regards
Parveen
@ Sabastian
I'm surprised to hear you had problems joining LinkedIn ARIS User Community. Many IDS Scheer employees are members. Javed, the group owner is ex-employee of IDS Scheer UK. Of course it's natural to expect that the LinkedIn community will be killed by this one. But I really do not believe that this might be the reason behind your not getting approval.
Ivo
Hi Ivo,
it is not our intention to "kill" other ARIS communities. I think ARIS will be even stronger if we have several communities around the planet. Not everyone will like ARIS Community and so it is good to have alternatives available.
Lets wait and see if my membership request gets approved...
Cheers,
Sebastian
Well, I know but still, as I said, it's natural to expect that. Mostly because people prefer to have one place than many. It has a drawback, it's vendor led. But then let's face it, for two months it has 2k members. ARIS user group reached 1/4 of that for several years and LinkedIn communities the same amount although much faster.
Hi All,
To carry on this discussion, I have a small doubt, just thought of how you will interpret this.
I am thinking of designing a hierarchial structure for my standalone Data Models as we are doing for process models (L1- L5). What I mean is that, as in Process Modeling we can design the hierarchial structure starting L1 - Enterprise model and then to move down we can use VACD and EPC, what should be the mapping for data models.
L1 (Conceptual Data Models) - ?
L2 (Logical Data Models) - eERM models, IE models etc
L3 (Physical Data Models) - Attribute Allocation Diagram, UML etc.
Thanks
Parveen
Hi Parveen,
It depends somewhat on what you are trying to achieve with the various models but here is the set of models I generally start with for data:
L1 (Conceptual Data Models) - Technical Terms
L2 (Logical Data Models) - Technical Terms for a Data Dictionary and/or either IE Data Model or eERM for the formal Data Model
L3 ( Physical Data Models) - The various physical data models depending on the implementation of the data: SAP SERM, DW Structure, Relations Diagram or IE Data Model or eERM for relational, DTD for XML, OMT Object Model or UML Class Model for Objects
I also use the Technical Terms model to map Technical Terms to any/all of the other models to show where and how the data is implemented. I have used the various attribute allocation diagrams at various levels to model the attribtues. I have also done custom filters that allow the attributes to be displayed inside the entity or table box (like most data modeling tools do).
I use the Technical Terms to represent data in the business models.
Also to address a comment made elsewhere in this discussion, it is possible to model domains and data types in ARIS. Domains are an object available in the various attribute allocation diagrams and it has attributes to describe the data types. There is also an Enumartion object which can be attached to show a list of values.
In summary, ARIS has extensive data modeling capabilities that are seldom used. In particular, the flexibility of modeling data without worrying about whether it is an attribute, entity or relationship by using Technical Terms is very powerful and none of the leading data modeling tools support it. I also like the ability to retain non-standard terms in the Technical Terms models and relate them to the standard term. This provides the ability for people to view the term they may be familiar with (the non-standard one) and see the link to the new standard term for it. Again, something that the leading DM tools can't do.
Rick
Hi Rick,
Thanks for your thoughtful response.
My thoughts are quiet inline with yours. Its good to know that I am on the right track.
I am quite interested to explore the data modeling capabilities of ARIS, good to find some impressive fetaures.
It would be great if we can extend this discussion futher with the "Suitability of Data Objects" based on different scenarios.
Best Regards
Parveen
