
What is the easiest way to generate a meta model of type ERD, UML Class Diagram (preferably) or IE Data model from an existing ARIS model having many user-defined attributes so that: all classes (or entity types) are created from the respective object types but are different depending on the symbol, their attributes - from the pertinent attribute types with their data type. Associations to be created from the respective connection types (to get their name from) and their attribute types for association attributes. Multiplicity (cardinality) could be added manually. The "pertinent" could be determined based on "maintained" status or using the filter or some other method.
The business case is to document a user defined method extension.
Anybody tried similar thing and/or has suggestion how to go about it?
Regards
Ivo
The easiest way IMHO is to create the models you want in a new database with the Entire Method filter. Obiously you will have to create the derived models/objects/atributes first in the method section of the Administration module. There you can also change the symbols for objects and the template you like to use (e.g. to show attributes by default in the model).
Once you're done with your example models you can create a new project filter "from an existing database". This then can be merged with other filters you might be using in your projects (create new filter).
Does this make sense?
Hello Roland,
is this a build-in functionality from ARIS, the "create a new project filter from an existing database"? If yes, what release I have to have, because in my one (7.1) I can only create a method filter by hand.
Thanks in advance
Volker
Thank you Roland but If by "create" you mean model manually, yes, that's what I usually do in such cases. What I had in mind was some automated way which I hoped was conveyed by "generate" in my question.
Ivo,
sounds as a very interesting customized solution. I assume that such a solution should parse amc file
/Konstantin
Interesting question, Ivo, because you imply that your instance model is complete enough to "use" (instantiate) everything what your meta model allows.
Sebastian,
Of course there might be a need to modify the generated meta model. The objective is to save time modeling things already existing in the method and further "specified" by the instance model. One time consuming task is checking objects and connections allowed in a model which can be done in the Method Help, but, unfortunately, the allowed connection types are only documented in the Method Manual appendix, so there is no single place, or preferably a model, to show all method details for a particular model. That's why I apply this approach which I wouldn't call "elegant", to specify customised method extension in cases where there is a specific interpretation of standard method elements plus a lot of user-defined elements.
This is built into ARIS since years now. Go to your create new filter wizard (in the Admin module) and in step 2 chose "create automatically" which then leads to this screen:
After you created the new filter, save it and create a new project specific filter by merging the new one with an existing one (option 3 on the screenshot above), so that you keep the source filter.
It also saves you the other 13 steps of the create>new wizard and you only have to maintain your meta-model in an ARIS database :-)