Skip to main content

I have a question regarding data management in LeanIX, specifically about representing weak coupling relationships. Currently, I can establish strong dependency relationships as follows:

  • Create IT Components in the IT Component section.
  • Link Applications to IT Components via the "Technology Stack" field in the Application Factsheet.

This approach effectively represents strong dependencies where an Application relies on specific components to function properly.

However, I also need to handle cases where a weak coupling relationship exists:

  • The Application can use an IT Component, but it is not a strong dependency.
  • The Application can still function normally without this component by using alternative components.

In the current system, I can link the Application to the IT Component, but there is no way to explicitly indicate that this relationship is "replaceable" or "weakly coupled."

My Request:

  • Is there a way to visually represent weak coupling relationships in the Relation Explorer?
  • Is there a feature or functionality that allows me to mark a component as "replaceable" within this relationship?

If this is not currently possible, could you suggest any alternative solutions or workarounds?

Hello,

  1. If you want to showcase different types of relationships you will probably have to make those relationships in LeanIX by changing the meta model.

      2. Yes, you can create a field inside the relationship (not in the fact sheet). Afterwards you can see this field in the report by selecting the field from the FIELD ON RELATIONS section in the View drop down (top left of the report).

To test this try and populate some Obsolescence Risk Status fields in the IT Component - Application relation. Then create a report with base fact sheet IT Components (or applications for that matter it just that ITC makes more sense), cluster by Applications and then select the Obsolescence Risk Status as a view and see what happens.

So to try and help you in your initial question you can probably do either, I guess it depends on what fits with you and your team the most.

Keep in mind though importing fields on relation takes a long time to upload, in case you are handling a lot of data and you are doing the data upload via excel imports.

Hope this helped.

 

 

 

Reply


Terms & ConditionsCookie settings