Advantage of different visibility of links, comments and tags?
![]() Hello everybody, In my point of view the behavior of DNG regarding the visibility of links is very confusing. After reading the DNG documentation I understand how it works but not why it works on this way. Link to the documentation: http://www-01.ibm.com/support/knowledgecenter/SSYMRC_5.0.2/com.ibm.rational.rrm.help.doc/topics/t_reuse_artifacts_modules.html?lang=en I don’t understand what the advantage is to see links tags and comments not equal in every context (base artifact or module). For example I create a specification using a module. Then I will use the drag & drop link feature within the module. All links I will create on this way won´t be visible in the “base” Artifact View. Why? What is the logic behind this behavior? Does anyone have a use case where the different visibility of comments, links and tags make sense? I am grateful for any hint. |
Accepted answer
![]()
To my understanding, Alastair response is right on spot. This capability does seem to be intended for requirements reused in different contexts.
It'd really depend on usage, as in our scenario, even on reuse we'd like the links on the base artifact so we could see everything it impacts. It also cripples filtering by links sometimes and impact analysis.
I see 2 relevant WIs associated with this
https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=96280
https://jazz.net/jazz03/web/projects/Requirements%20Management#action=com.ibm.team.workitem.viewWorkItem&id=90059
Hopefully we'll see changes soon.
Stefan Riedmüller selected this answer as the correct answer
|
4 other answers
![]()
I agree it is confusing and in my case it does get in the way of how I want to use the product.
However the use case I think they are trying to meet is for re-usable requirements. For example, say you have a legal compliance requirement that you need all of your products to meet. You could create this as a base artefact once (so that if the law changes in future you only make the change in one place) and then include it in a numebr of modules for each separate product. But when you want to link those requirements to design elements or test activities you would want to do that at the 'where used in a module' level not on the base artefact - otherwise all of those links would be visible to every product team. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.