Archi Forum

Archi => General Archi Discussion => Topic started by: eduardobbs on June 30, 2021, 13:22:29 PM

Title: Nesting validation advice
Post by: eduardobbs on June 30, 2021, 13:22:29 PM
Hi,

In the validator, Archi shows a Visual Nesting advice when the relationship is correct, in my opinion.
It says "X is nested inside of Y but there is a non-nesting relationship between them or no relationship."

I am attaching an example. Do you think the advice is correct in this example?
Maybe Archi could have a feature to suppress an individual advice that we consider to be imprecise for that specific situation?

Otherwise what will happen is that we will build up so many incorrect advice items, that we will start to ignore all of them, including the good ones.

Please and thanks 
Title: Re: Nesting validation advice
Post by: Jean-Baptiste Sarrodie on June 30, 2021, 13:24:00 PM
Hi,

The question is: which relationship do you use in this case ?

JB
Title: Re: Nesting validation advice
Post by: Jean-Baptiste Sarrodie on June 30, 2021, 13:27:51 PM
Hi,

My previous question was not clear enough: I can see that there is an assignment in the model, but did you use it in your view? On way to check is to move the processes outside the application components and see if there is a relationship visible. If not then the advice is right.

Regards,

JB
Title: Re: Nesting validation advice
Post by: eduardobbs on June 30, 2021, 13:59:20 PM
Yes, using assignment, but it could well be a realization, too, the same error would happen
This is the result of dragging it
This is all in an empty model
Title: Re: Nesting validation advice
Post by: Jean-Baptiste Sarrodie on June 30, 2021, 14:27:51 PM
Hi,

I can't reproduce it. If I create the exact same view with assignments hidden for the nestings, this validates without warning (and this is the intended behavior of course).

Can you share the model file for which you have the validation warning?

Of topic, but just in case...
Quote from: eduardobbs on June 30, 2021, 13:59:20 PM
Yes, using assignment, but it could well be a realization, too, the same error would happen

If you think about realization between Application Component and Application Process, then realization should not be used (only assignment). Such realisation would be the result of a derivation chain based on AppCmp_1 realizes AppCmp_2 assigned to AppPrc, which models a TOGAF related construct (Physical Application Component realizes Logical Application Component) which is rarely the intended meaning.

Regards,

JB
Title: Re: Nesting validation advice
Post by: eduardobbs on June 30, 2021, 15:26:54 PM
Maybe it`s because of my Archi version?
See it attached alongside the model.

Your off-topic advice was really good, I was always using assignments for this, but I did not know when it would be the case for using realization between these two concepts.

Thanks
Title: Re: Nesting validation advice
Post by: Jean-Baptiste Sarrodie on June 30, 2021, 15:49:31 PM
Hi,

There's a (strange) bug.

i'm opening an issue on GH.

Thanks for reporting it (good catch).

JB
Title: Re: Nesting validation advice
Post by: Xiaoqi on June 30, 2021, 18:07:37 PM
Hi both,

Yes, I can reproduce this similar issue using Composition relation for nesting as well.

Regards,
Xiaoqi