Could links be managed in DNG as fine as by using linksets in DOORS?
Hello,
could links be managed in DNG as fine as by using linksets in DOORS?
Example:
- Links between input and output requirements should be "realize" links.
- Links between requirements of the same level in an subsystem should be "refers" links.
- Links from a requirement to an item outside the subsystem are not allowed.
Thank you for an answer,
Bernd
2 answers
Using DNG, traceability type are very flexible since you can customise link type as you want. It uses preferred linktype per an artifact type rather than fixed to be a certain link type. Which means relationships between requirements need to be managed by process rather than a tool configuration. I guess it can be easily managed by treeview with full traceability.
Within a same project, I'm not sure if you could prevent requirements from having links but again, it can be managed by view and filter rather than linkset in DOORS.
Within a same project, I'm not sure if you could prevent requirements from having links but again, it can be managed by view and filter rather than linkset in DOORS.
Hallo Seo,
Thank you for your answer.
I have found no solution to check the relationships between requirements with the help of DNG too.
Today we use DOORS in teams between 5 and 50 developers where most of them are hardware or software specialists but not DOORS specialists.
With the help of DOORS linksets creating correct links is very simple for everybody and the number of wrong links is minimized.
Without the help of DNG we have much more manual work to check links than using DOORS with linksets.
While DNG has no technique like DOORS linksets it would be hard to change to DNG.
Bernd
Comments
