It's all about the answers!

Ask a question

DNG - Base artifact links vs module context links


1
3
Sean F (83712234) | asked Aug 11 '18, 11:35 a.m.
There is a distinction between linking to/from a base artifact vs linking to it in a module context but what are people doing in practice?

If all artifacts are in modules and there is no CM then is it better to use module context links or base artifact context links?

If we have a simple project (no CM) with 2 modules Stakeholder and System and each contains some St and Sys reqs then users can create links by dragging and dropping between the module representations of the respective artifacts and these will be module context links.

They can alternatively open the artifact and create the link in the artifact sidebar in which case the links will be base artifact links.

It seems like it could be quite easy to accidentally end up with a mixture of the 2 types. Is there any way to enforce all link creation as being either module context or base artifact?

5 answers



permanent link
Sean F (83712234) | answered Aug 14 '18, 8:45 a.m.
Or even if there is a way to tidy up afterwards when users have accidentally created a mixture of base and module link contexts.

Like if we could move any module links to become base artifact links (or vice versa - assuming all artifacts are in modules and appear only once)

permanent link
David Reilly (695) | answered Aug 15 '18, 11:25 a.m.
Sean,

You're asking the question that has other users of the software (like me) scratching their heads. I get the locality of modules. I suppose if users are making comments or want to show dependencies within a specific group of requirements, they'd prefer the locality of making them within the module. 


The design decision that Jazz has made is the assumption that link locality is the only reason users would link in the module. Users like myself and those I work with daily do not want to create "local" links by default. They are linking in the module because it is structural and cogent. Lack of context in artifact folders and collections makes linking impossible. 

While I'm griping, it's actually funny that there is an explicitly "local" link type called "Parent of" and "Child of." However, you aren't capable of linking by attribute with the parentBinding values you carefully populated. Extracting those values requires you to extract your requirements from every module you've ever created. GL, HF. 

Possible Fix:  There should be a way to fix this. Here's a general flow:

1. Query your project with OSLC / REST. (View -> Module)
2. GET the XML for the module. Loop over MB artifacts.
3. Extract uri and etag values. 
4. Replace "/MB_" with with rrm-core value to get the "base URI"
5. Update base uri artifact with Core etag value. 
6. POST artifact back to project.  

If there was some easy way to fix this issue, I'm sure they would have done it by now. As it stands, it's been an issue for reporting and user interaction which has no "out of the box" solution to my knowledge. 

DNG v6.0.2iFix015



permanent link
Sean F (83712234) | answered Aug 16 '18, 10:01 a.m.

Thanks for the suggestions David.

Yes, it would be good of there were explicit options to choose to always default to either module or base context for all link operations within a given project.

I am also interested in opinions on which context is best even if there is no way to force that context as a default.

Most requirements projects will have requirements created in modules and most will not require the artifacts to appear in more than one module.

So in that scenario it would seem that there should not be any difference between using either module or base artifact context in theory but in practice is that true?

Would be interesting to get a straw poll of practitioners to say which of the 2 contexts they are recommending or mandating for their users and why.

It seems to me that base artifact linking would be the better default in case artifacts are reorganised into different modules at a later date.


permanent link
Cliff Sadler (62111) | answered Sep 29 '19, 4:05 p.m.

 A year later, plus a couple of months, and it appears this is still not resolved, nor is there any guidance of substance.  Here's a reason that I would like to syncronize base artifact links and module links:

The closest thing to a traceability wizard in DNG exists only for artifacts.  It's called Tree view.
So, let's either make that available in Modules, or find a way to synchronize the links, or be able to view base artifact links in modules.
I see no way to direct a ReqIF or migration file to use base artifact links.  They are always module links, even if I don't check the box to create modules for non hierarchical modules.  BTW, this is all data coming from DOORS 9.6.1.10.

Are there any improvements in 9.7 in this area?
Any tricks that haven't been documented here?


Comments
Sean F commented Oct 03 '19, 12:37 p.m.
Hi Cliff,

i have only recently installed 9.7 and i have not yet tried the migration tool with 9.7

But I am not aware of any new features in 9.7 that would affect the migration tool's behaviour.

permanent link
David K (11) | answered Jan 14, 10:50 p.m.

Has there been any update or guidance from IBM in resolving this issue?

Your answer


Register or to post your answer.