AV
Hi,
I have quite a fundamental question in regards to filtertypes (i.e. the choice between a manual filter or a filter generated through a convention database).
Right now we are using ARIS 10. Background: ARIS is used within our organization as an Architecture repository.
Out of the "ARIS 10 box" comes a filter named: ArchiMate 3.0. This implementations comes very close to what we would like to use. In general our ambition is to fully support Archimate 3.0 which includes the full list of Archimate relation types.
Although not tested fully, I am under the impression that the Archimate 3.0
configuration is complete. The only customizations we prefer to have, will
only be done on the attribute level of the objects.
My question is: what filter type do you recommend?
By the looks of it, the implementation of ArchiMate 3.0 is provided in a manual filter, or at least that is what we have.
I am quite skeptic towards setting up a convention database as that would lead to:
- 58 symbol types * 58 symbol types * (approx.) 4 relation types ≈ 13456 relations to be put in a convention database. - These are then to be maintained through 24 viewpoints which multiplies the number of relations that I need to define.
What would you recommend in order to pick the right filter type? Use the existing filter and extend it, or do you still recommend building a convention database?
Up until now I haven't heart good arguments to use a convention database, and since the new Archimate 3.0 filter is a manual one my preference is to extend that one and reuse what is already there.
Perhaps I am overlooking ARIS-features that support me in creating a convention database. If so, please let me know.
Regards,
Foxfriend
Hello Arko,
Archimate indeed is a big chunk. I guarantee you will not have much fun setting up a convention database for that. You did the maths. Here are some strategies. I assume you want the entire Archimate filter plus something on top. So here is a possible way to go:
1. Create a convention DB with the extensions you are planning, e.g. the object types with the extra attributes.
2. Create a filter from the convention DB.
3. Create another (empty) filter for your production use.
4. Merge the Archimate filter delivered from Software AG onto your production filter.
5. Merge the filter from your convention DB onto your production filter.
6. (Optional) Make any restrictions of things you do not want to use
If you have separate modelling domains, such as Archimate, Information modelling, Process modelling, BPMN it may be a good trick to maintain those filters separately and merge them for production purposes. This would also make it easy for you, if you had different filters for different stakeholders. Create any combination of your "filter modules" for the stakeholders you have. So if you do not want the entire Archimate method, make a copy of the filter, make the necessary restrictions and use that as your "Archimate filter module".
This way you can combine the advantages of the filter creation methods (manual, automatic, pre-defined).
Keep in mind, also a filter has got an identity (GUID) like any other ARIS object. So after importing the Archimate filter, make a copy of it and work with that. This way you keep the original filter as a reference. If you ever re-import the delivered filter, you won't destroy your work.
BTW: I assume you will define your own viewpoints as model types or at least modify the delivered ones in some way, so there will be some reconfiguration of the Archimate filter as well. Most probably you will exclude the generic "Archimate 3.0" model type, which is the "Entire method" model type of Archimate.
Regards, M. Zschuckelt
