Support

Expand all | Collapse all

Cross-Project Coverage (RTM) reporting options

  • 1.  Cross-Project Coverage (RTM) reporting options

    Posted 06-19-2017 14:20
    Hi Everyone,
    Evaluating if there is an approach in Jama to effectively report cross-projects around showing requirement-all-the-way-to-test, but where the requirement may be in one jama project but the test artifact is in a different jama project.

    Baseline:
    • Customer A Project: A customer project where they want to solve problems that span multiple products that the solution owner may already have in Jama. (assume BABOK based)
    • Customer B Project: A customer project where they want to solve (somewhat different than customer A) problems that span multiple products that the solution owner may already have in Jama.(assume BABOK based)
    • Product X Project: A product project where product X already has user stories and test cases completed. (assume Agile based)
    • Product Y Project: A product project where product Y supports different user stories and associated test cases. (assume Agile based)

    Usecase/the question:
    Given Customer A may have 3 requirements that are already met by Product X, and another 2 requirements met by Product Y, is there a way to link customer's (stakeholder) requirements to existing Product User stories and...thereby...link the product tests for those user stories for Coverage/RTM all the way back to the Customer A's requirements to (only) the respective tests in Product X and Product Y.
    --the customer may have additional requirements not met by existing product capabilities, which may create a new product project or create new user stories in respective product projects.

    To be concise: I see this in the 'Trace' feature that shows cross-project, but need a way to generate a Coverage/RTM style report and don't see how to do that cross-project.

    ------------------------------
    darren hartford
    ------------------------------


  • 2.  RE: Cross-Project Coverage (RTM) reporting options

    Posted 06-22-2017 16:11
    Hi Darren,

    That's a great question. Sorry for the delay in answering it-I had to walk through the scenario with one of my colleagues on our Product team to determine how this could work.

    So if we understand this scenario correctly, it doesn't matter what methodology you're going for; it's more that you have established a way to relate items and that it is consistent.
    Robin sketched out her interpretation of what you're asking for-please correct us if this is wrong. But what it seems to boil down to is, you need a way to trace from Requirements to Tests. So you'd relate Requirements down to your Story, and your Stories down to your Tests. It doesn't matter what project any of these items are in; you can make and view relationships cross-project.

    Assuming all of this is true, you would use the Trace View with Requirements in the Source column. From there, paging downstream would show you these three levels.However, there is no way to prevent some layers of your traceability from showing. You would need to export the view and remove, or hide, the unneeded middle column.

    Let us know if there is more to your request than meets the eye.


    ------------------------------
    Kristina King
    Jama Software
    ------------------------------