Expand all | Collapse all

multiple units, same rerequirement

Jump to Best Answer
  • 1.  multiple units, same rerequirement

    Posted 03-15-2017 12:18
    Hi, I have multiple units that operate and look the same.   What is an easy way to track and verify in JAMa each unit that have the same requirement?



  • 2.  RE: multiple units, same rerequirement
    Best Answer

    Posted 03-15-2017 14:09
    Hi Gilbert,

    Would you please describe your use case a little more? I could be wrong, but  one solution could involve using links/relationships.

    Unit 1 
         links to Req t1
         links to Reqt 2

    Unit 2
         links to Reqt 2
         links to Reqt 3

    So you will know that Unit 1 and 2 have Reqt 2 in common.

    Have you explored the enterprise re-use and sharing function in Jama yet. Perhaps that can enable some ways for you to manage units that have similar/same requirements.

    Good luck with your search for your answers.

    Stephen Woo
    Oakland CA

  • 3.  RE: multiple units, same rerequirement

    Posted 03-15-2017 14:18
    By the way, the user guide on Jama enterprise re-use and sharing is here: Work in Jama > Work in Projects > Reuse and Synchronization

    Take a peek to see some of these functions address your needs. We can then discuss more of your detailed questions.

    Good luck.

    Jamasoftware remove preview
    Work in Jama > Work in Projects > Reuse and Synchronization
    Reuse and Synchronization
    View this on Jamasoftware >

    swoo Woo
    Oakland CA

  • 4.  RE: multiple units, same rerequirement

    Posted 03-15-2017 14:49
    Edited by gilbert dutchover 03-15-2017 15:09

    Thanks, Swoo.  Let me and my co-worker see if that will work.





  • 5.  RE: multiple units, same rerequirement
    Best Answer

    Posted 03-19-2017 07:36
    We have set up a "Standard Requirements" repository that covers the things our products have in common. Each requirement is also linked to a standard test case. These standard requirements and test cases are reviewed and updated as necessary. 

    When we start a new project we "reuse" everything in this repository into the new project and keep the items synced. This captures a snapshot in time of the requirements and ensures you know what requirements and test cases the product was designed to. We also add a section for Product Specific Requirements to capture the stuff that is unique about this product.

    To weed out the standard requirements the are not applicable we go through them and mark the ones that don't apply to this new product as "Not Applicable" (typically 1-2 hours  for our 480 standard requirements). To do this we have added a state in the status field called "Not Applicable". We also send this list of not applicable requirments for review to ensure we haven't mistakenly marked something as not applicable.

    Test cases are created for the product specific requirements. Once this is done we generate a test plan that covers the test cases of the remaining "applicable" requirements. The test cases for the "Not Applicable" standard requirements are filtered out. This is then routed for review and approval.

    One cool thing about reuse is the approval status follows the requirement from the Standard Repository. This eliminates the need to review and approve these common requirements and test cases over and over again.

    Randy - Delta Controls