It's all about the answers!

Ask a question

Linking artifacts/traceability within a module - what are the downsides.

Daniel Nakonecznyj (132) | asked Jun 03 '16, 4:04 p.m.

Is it a good idea to link artifacts within a module?  I have a module with several sections - High-Level Requirements & Detail Requirements.  I want to set up traceability by linking the High-level and detail requirements.  I've read that this may not be the best way to set up traceability but I can't really see any downsides.  Has anyone else done something like this?

Accepted answer

permanent link
Keith Collyer (456511) | answered Jun 06 '16, 5:04 a.m.
Although there can be reasons for linking within a module, generally it is not a good idea. I guess you are thinking of a module as a document. Instead, think of it as a structured collection of information. If you do this, it is more natural to collect the high level requirements in one place (module) and the detailed requirements in another. (As an aside, that would generally be a better way to allocate them to documents as well).
DOORS NG doesn't restrict the types of links you can create between modules, but it does allow you to restrict the links you create between artifacts of different types. So you could have one type for high-level requirements and one for detailed requirements and restrict links to only go from detail to high-level. OK, you can still do this inside a module, so make use of the default artifact type settings for a type of module so that you have to consciously add artifacts that are not of the default types to a module.
You can do all this within one module, in practice you will find it is simply easier and cleaner to separate the levels. It is also easier to explain and understand if you ever need to draw the information architecture. Things that are easier to understand are more likely to be used properly.
Daniel Nakonecznyj selected this answer as the correct answer

Your answer

Register or to post your answer.