Configure symmetric / asymmetric links
Hi there,
I am trying to figure out how to use link validity for our projects best. I read this article and it is quite good. The thing that I miss is, how do I configure a linktype to be symmetrical or asymmetrical?
Could you also have a look at example 2 - is it correct, that the link summary for System requirement M v2 stays valid? I cannot reproduce this.
2 answers
So whoever may have the same question - this is what I found out.
You cannot configure this, this is baked in. The answer is in the article itself, but I didn't get it while reading. Basically while working within DOORS Next / RM / /rm the links are all symmetrical. ("Requirements are considered
symmetric
to each other. For example, stakeholder requirements are symmetric to system requirements: a change to either artifact affects the validity status of the link between them.")
So this relates to all artefacts within /rm, if those are requirements or not (you maybe use /rm for "something else" than pure requirements).
The links are asymmetric when they are between applications, e.g. /rm and another (downstream) application, e.g. /qm (ETM):
"
- Requirements are upstream of models, designs, and tests.
- Tests are downstream of requirements, models, and designs"
So this is all the magic. It is written down, but getting it took a while. Hope this helps. And maybe this isn't the whole truth behind it, it is just what I found out by now!
To add a little to this...
If you're looking at the Systems Engineering V, it is the artifact that is "lower" and "to the right" that should have the OUTGOING link. The artifact with the outgoing link is where the link is saved and "owns" the link, whereas incoming links are calculated. Thus there's really no such thing as an asymmetric engineering link...I guess except for a link to a Web URL that is not OSLC.
Hope this helps.