Undesirable behavior in Traceability Report (Enhancement Request) Hot

by Ribhu Sanyal on July 03, 2015
When running a Traceability Report, I get a result that limits the usability of this report. Here is the use case. I can demonstrate this if needed:

1) Per the recommendation by Serena to list Projects as Categories when we want to share requirements across projects, we have it set up that way (DimRM Admin guide v12.2.1, Feb 2015, page 24)
2) Since Test Cases are standardized tests, they are all contained in the root level category to facilitate reuse across all projects
3) We have items in the Requirements Class that are specific to a project, so they are contained in that project’s category.
4) These Requirements need to be linked to Test Cases that are in the root category. This is allowed in the tool.
5) When running a traceability report, I need to filter only the requirements applicable to a specific project, so I set the filter on the Requirements class to point to that project’s category
6) What I expect is that the category filter only apply to the top level class in question, and that the traceability report show me all links to the other selected classes, regardless of which category they reside in.
7) In this scenario, since the Test Cases are in the root level category, they are ignored altogether and not displayed, leading to a misleading result.
I am requesting a priority enhancement to change this behavior, and allow us to find linked items across all categories by filtering for categories only on the top level class.
  • Ideas

    Status
  • Please login to view any attachments.

  • I'm not sure I agree with Serena's suggestion to use Categories as a means of sharing requirements across projects. It seems that this would make the use of categories overly complex in terms of category hierarchies. We prefer to share requirements across projects by copying the "shared" requirements into the new projects. This allows us to maintain the original history of requirements across projects and simplifies our category trees.
    dmarcelo Commented by dmarcelo August 25, 2015
    Top 500 Reviewer  -  

    I'm not sure I agree with Serena's suggestion to use Categories as a means of sharing requirements across projects. It seems that this would make the use of categories overly complex in terms of category hierarchies. We prefer to share requirements across projects by copying the "shared" requirements into the new projects. This allows us to maintain the original history of requirements across projects and simplifies our category trees.

    We are adding with next release (12.3.1) the possibility to define the category based on class within the traceability report wizard.
    Kay Fuhrmann Commented by Kay Fuhrmann August 12, 2015
    Top 500 Reviewer  -  

    We are adding with next release (12.3.1) the possibility to define the category based on class within the traceability report wizard.

    Hi Ribhu, I ran into this same issue running a traceability report where I wanted all top level requirements in a specific container. When the traceability report is ran, it is only looking for all the traced classes in that same container. If you are savy with the script language, you can go in and remove the lines making the traced classes be in the selected project or container. You will want to remove the "where group in ('container that was selected at top level')" from the classes you do not wish to be in the container or project. I was successful using this method.
    Blake Ketterl Commented by Blake Ketterl July 24, 2015
    Top 500 Reviewer  -  

    Hi Ribhu, I ran into this same issue running a traceability report where I wanted all top level requirements in a specific container. When the traceability report is ran, it is only looking for all the traced classes in that same container. If you are savy with the script language, you can go in and remove the lines making the traced classes be in the selected project or container. You will want to remove the "where group in ('container that was selected at top level')" from the classes you do not wish to be in the container or project. I was successful using this method.

     

PrintEmail

Recent Tweets