In RRC 4.0.4 are there recommended best practices for linking within modules?
The challenge I have is that it is difficult to build a traceability view that shows end to end traceability across 4 daisy chained artifacts. The only way to accomplish that appears through linking the Base artifacts only, but then you lose the context that can be set for an artifact within a module. In many instances it is that very context that allows you to better understand what you should be tracing an artifact to.
|
3 answers
I don't quite follow you question/issue, but let me comment anyway :-)
Comments
Phil Barrett
commented Mar 01 '14, 9:54 a.m.
Thanks for your response Daniel. What we struggle with is the module provides great context in understanding how the artifacts (in our case let's use artifacts of type = requirement) might be grouped and creates an opprotunity to identify gaps and the possibility of adding a missing requirement right into the Module. The core requirment artifact is then linked multiple ways (to a business requirment, design artifact and test case). To be able to link that base artifact from within the module that provided that context, to another base artifact is key. Other wise the traceability is limited to the module itself. So if someone creates a design spec within a Design Module and links to a requirement artifact from within that module the traceability for that deisgn spec to requirment is limited wittin that Module and I can't open the business requirement at the neginning of the chain see the trace all the way to design spec. |
Phil you wrote:
>>> To be able to link that base artifact from within the module that provided that context, to another base artifact is key. Other wise the traceability is limited to the module itself. So if someone creates a design spec within a Design Module and links to a requirement artifact from within that module the traceability for that deisgn spec to requirment is limited wittin that Module and I can't open the business requirement at the beginning of the chain see the trace all the way to design spec. I still don't quite understand why you need to do linking at the base artifact level. Do you want to reuse artifacts for multiple products or multiple releases? Is there some other reason that you cannot work only in modules? Let's consider the latter possibility for a moment. What if you were to "forget" that there are base artifacts and only work in modules? Could you organize your work like this?
And by the way you can set up a view in the system requirements module showing links both to business requirements and design information, e.g.,
|
Hi Phil/Daniel,
|
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.