HO

Greetings:

In a model we want to include the relation between a cluster and the process that produces it. So we have come up with option A to show that relation. What we usually do is not to attach the cluster to any interface but the event with the interface (option B). However, as you can see it is not actually accurate since the catalog is created once per year and then it doesn't change whereas the requirements are received at any time.

Since ARIS allows it I suppose option A would be better. But I'd like to hear other opinions or solutions about it.

 

 

Regards

Holger

 

 

 

File attachments
by Holger Edgar Oviedo Cahuata Author
Posted on Mon, 05/25/2015 - 22:15

just in case the options are in the file attached (question cluster 2.jpg)

Regards

 

0
by M. Zschuckelt
Posted on Tue, 05/26/2015 - 09:22

Hello Holger,

surely it's a matter of taste, but I would vote for Option B.

If it is important to show the source of the cluster object, show another occurrence copy of the cluster next to the interface in option B and draw the connection "Interface has as output Cluster" there. I think that was the intention of allowing that connection.

With option A the reader may get confused about the nature of the process flow.

Regards, M. Zschuckelt

0
by Holger Edgar Oviedo Cahuata Author
Posted on Tue, 05/26/2015 - 17:38

In reply to by M. Zschuckelt

Hi M Zschuckelt:

Thanks for your input. That is a good option, but the problem with option B is the AND condition. The process is triggered when the requirement is received and it will have to wait the event "catalog created", which could only happens once a year in order to proceed to the activity. What actually happens is that the activity "register requirement" uses the cluster "Good and services catalog". Like you said what we wanted to show is the origin of that cluster which is the product of the "Making good and service catalog" process.

Best regards

Holger Oviedo

 

0
by M. Zschuckelt
Posted on Tue, 05/26/2015 - 18:28

Hi Holger,

this depends, how you look at it. If you are running simulations with your processes, the cardinality between your process instances indeed may be a problem. If you just look at those processes from a business perspective, you may be happy to read, that you must have a completed catalogue and a requirement as prerequisite for your process, regardless of the cardinality.

If you look at it strictly, your catalogue is some product of an entirely different (once-a-year) process, represented by the general availability of the catalogue cluster object. On VACD level you just chart out, that you have some "product development" process, which incidentally produces a catalogue once a year (maybe you state that in the FAD of "product development"). Then you would leave out the AND branch altogether in your example and just use the catalogue as a given resource. Further information on the origin of the catalogue then can be looked up in the properties of the cluster object, where the "product development" process (or some function inside it) will produce it as output. Then it may also be a good idea to have your process represented by a value added chain in the VACD process landscape and assign the catalogue as an input to it in the corresponding FAD.

Was that clear or too confusing?

Regards, M. Zschuckelt

0
by Holger Edgar Oviedo Cahuata Author
Posted on Wed, 05/27/2015 - 22:19

Hi M. Zschuckelt,

Not at all, it is OK. Just to be sure VACD means Value Added Chain Diagram and FAD is Function Allocation Diagram right?. Thanks for your advice!

Regards

Holger

 

 

0
by M. Zschuckelt
Posted on Fri, 05/29/2015 - 14:07

Hello Holger,

precisely. Sorry for the acronyms.

Regards, M. Zschuckelt

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