Profile picture for user m3b

Hello all,

When the architecture repository grows, it may come that we have to deal with homonyms.

Let's say for example that "Program" may cause us a problem because :

  • we need a "cluster/data model" element "Program" for a computer program
  • we need a "cluster/data model" element "Program" for a program encompassing multiple business projects.

So far, I'm thinking of two solutions, but I'm happy with none.

Solution 1: give different names to different objects. One would be "computer program," the other "business program."  The downside is: these terms may not appeal to stakeholders, they do not reflect the way of expressing themselves, they never use "business program". Moreover, these terms are quite verbose.

Solution 2: have two different object definitions, with the same name "Program." The trouble is, how to help the modeler (aris user)  using the correct object (computer program and not business program for example)?

Thanks for your feedback!

Michel

by M. Zschuckelt
Posted on Fri, 03/29/2019 - 15:35

How about building a glossary using a technical terms model? At the occurrence of your clusters you assign the proper technical term "Program (Computer)" or "Program (Business)" and deliver proper definitions of these terms. Your clusters remain different objects with the same name "Program". I would always prefer being more specific in the first place. But a glossary is a nice by-product of such an effort of standardizing your business.

0
by Michel Bénard Author
Posted on Fri, 03/29/2019 - 16:31

OK thanks !

Is there any way for a modeler to  pick the "correct" Program object corresponding to his context ?

I tried the following : 

  • Create two different "Program" cluster/data model objects
  • Create a new model, add a cluster/data model
  • start typing "Pro" -> a pop-up appears, listing "Program" and "Program".
  • When hovering the mouse pointer over the "Program" labels on the popup , the path to the "Program" object appears in a tooltip 

This would imply to create a model group structure that helps differentiating the cluster/data models objects for future reuse, and put the objects in the corresponding groups

 

for example : 

  • Main Group/Projects and Programs/Program (cluster /data object)
  • Main Group/Computer Science/Program (cluster /data object)

 

 

 

0

Featured achievement

Rookie
Say hello to the ARIS Community! Personalize your community experience by following forums or tags, liking a post or uploading a profile picture.
Recent Unlocks

Leaderboard

|
icon-arrow-down icon-arrow-cerulean-left icon-arrow-cerulean-right icon-arrow-down icon-arrow-left icon-arrow-right icon-arrow icon-back icon-close icon-comments icon-correct-answer icon-tick icon-download icon-facebook icon-flag icon-google-plus icon-hamburger icon-in icon-info icon-instagram icon-login-true icon-login icon-mail-notification icon-mail icon-mortarboard icon-newsletter icon-notification icon-pinterest icon-plus icon-rss icon-search icon-share icon-shield icon-snapchat icon-star icon-tutorials icon-twitter icon-universities icon-videos icon-views icon-whatsapp icon-xing icon-youtube icon-jobs icon-heart icon-heart2 aris-express bpm-glossary help-intro help-design Process_Mining_Icon help-publishing help-administration help-dashboarding help-archive help-risk icon-knowledge icon-question icon-events icon-message icon-more icon-pencil forum-icon icon-lock