Stumbled upon the relationship view during training and wondered what value it adds or an application for it the inbuilt help did not give me much additional context
Ian
Stumbled upon the relationship view during training and wondered what value it adds or an application for it the inbuilt help did not give me much additional context
Ian
Well, it shows objects connected to the currently selected object. This can come in handy if you want to navigate your models in the repository. For example, you could look up for which functions an IT system is used.
Wouldn't it better if a view combining both the "occurrences" and "relationships" is available.
Currently "occurrences" shows multiple entries of a model name, if the object have multiple occurrences in that model while the "relationships" view will show all objects connected to the selected object (along with implicit relationships, etc.).
Even Publisher follows a similar approach of listing the models with object occurrences as one section and related objects & connections in another section, in the details frame.
Query to IDS:
Query to Designer / Architect / Publisher users:
Thanks & Regards,
Shankar
Well, both views show different information. Each object may have several occurrences. The view shows exactly that. An object might be also connected to several objects, which is shown in the second view. I don't think it is useful to mix both.
Well - I would differ on that.
For instance, if an "Object O" have multiple occurrences in 2 models ("Model A" & "Model B")...
It does not help much seeing multiple entries of "Model A" and "Model B" in the occurrences view and then each connected object & relationship in the relationship view (without the process / model name).
Instead if I see the view displaying the connected object, corresponding relationship and the corresponding model I can understand the process / model better & it will help in process analysis as well.
Why do you state combining these views is not useful? Could you elaborate?
Occurrrences always need a model, but relationships can exist on definition level only. Therefore, it is not always possible to show Object-Model-Relationship-Object.