Profile picture for user Bentise

Hi, I have been looking into modelling risks in relation to products for a internal business customer. I originally assumed that because risks could be related to functions and application system types, then you would be able to relate products to risks. But I have found that you are unable to create relationships between products and risks. Does anyone understand why this is the way it is? I understand that you can infer a relationship between risks and products thru relating them to the same function (in a FAD) but this method falls down when you have multiple risks and products associated with a function, especially when you add controls into the mix. To me, if you can relate a risk to an application system, then logically you should be able to do the same with a product. p.s. using ARIS version 7.1.478722. Thanks in advance

by Ivo Velitchkov
Posted on Thu, 07/01/2010 - 11:33

The ARIS method provides capabilities for operational risk management. There is risk exposure when you do something. That I suppose is the main reason Risks are normally connected to functions or other objects representing or having behaviour.

I understand your need. I would recommend you create your own "product" object type based on technical term and if needed - "product tree" based on Technical Term diagram etc. You can model the "affects" type connection in Business Controls Diagram and Matrix Model (Check 15.2 in Method Manual if that connection is allowed in other models as well). The good thing is that the allowed connection types betweeen Technical Term and other objects include most if not all connection types of Product/Service and many more, some of them very useful.

0
by ben jones Author
Posted on Thu, 07/01/2010 - 23:24

Thanks Ivo, that sounds like a good idea, if it weren't for the fact that the product object has been apart of our filter for a while now and there is are too many artefacts in our repository to consider rework. I will still see if there is some way we could implement the technique using your method.

0
by Ivo Velitchkov
Posted on Wed, 07/07/2010 - 21:20

Then "Replace object types" report or similar technique might be an option.

0
by ben jones Author
Posted on Thu, 07/08/2010 - 01:06

Unfortunately replacing the object type would not be appropriate in our situation because it would break the meta-model. Technical terms do not have the same relationships as products. E.g a technical term cannot be related to a distribution channel.

Also, from experience I have found that the more you mess with the standard meta-model, the more of a mess you get yourself into!

But thanks for your ideas! I think we will have to create an inferred relationship via a relevant function.  

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