Requirement closure implementation
corrina benjamin
Member Posts: 1
I am transitioning an existing aerospace V&V management tool into JAMA and have a few questions on how to get the functionality we are used to.
Corrina
------------------------------
corrina benjamin
------------------------------
- My team has many requirements mapped to each test case. How can I show that 2 requirements have failed, while 5 have passed in a given test run? Currently all I can figure out how to do is mark the entire test run as passed or failed or passed with errors. I dont see a way to indicate pass/fail per requirement. What I want to show is that the test run was completed and mark which requirements are passed or failed.
- Is there a test case approval process implemented? We dont allow a test case (i.e. test procedure) to be executed until the test procedure has been approved and signed. Is this implemented/possible to enforce in JAMA?
- Is there a data review approval process implemented? Currently it looks like the requirements are closed after a test run is passed. We dont allow formal requirement closure until there has been a data review approval. Is this implemented/possible to enforce in JAMA?
- How do I show traceability from Test Cases to requirements (upstream relationship trace view)? Right now all I can figure out is how to show trace from requirement to test case, which is not the filtering I need to see. I need to see the rollup of all requirements into a few test cases.
Corrina
------------------------------
corrina benjamin
------------------------------
0
Comments
-
Hi Corrina,
Great questions! Our User Guide is a wonderful resource, and I'll link some articles from it that may be helpful here.
1. In executing a test run, you should be able to mark each step as passed or as failed -- for more granularity, a custom report may be needed. 2., 3. By doing an Approval Review, the review would stay open until/unless the review moderator finalizes and closes the review. You can also opt for baselines to be signed electronically, if/as needed.- Item workflow for Approval Reviews
- Close and finalize Approval review
- Reviews in Jama Connect > Moderator tasks
- Sign a baseline electronically
------------------------------
Carly Rossi // she/her
Community Manager // Jama Software
Portland, OR
------------------------------
-------------------------------------------
Original Message:
Sent: 01-05-2023 09:32
From: corrina benjamin
Subject: Requirement closure implementation
I am transitioning an existing aerospace V&V management tool into JAMA and have a few questions on how to get the functionality we are used to.- My team has many requirements mapped to each test case. How can I show that 2 requirements have failed, while 5 have passed in a given test run? Currently all I can figure out how to do is mark the entire test run as passed or failed or passed with errors. I dont see a way to indicate pass/fail per requirement. What I want to show is that the test run was completed and mark which requirements are passed or failed.
- Is there a test case approval process implemented? We dont allow a test case (i.e. test procedure) to be executed until the test procedure has been approved and signed. Is this implemented/possible to enforce in JAMA?
- Is there a data review approval process implemented? Currently it looks like the requirements are closed after a test run is passed. We dont allow formal requirement closure until there has been a data review approval. Is this implemented/possible to enforce in JAMA?
- How do I show traceability from Test Cases to requirements (upstream relationship trace view)? Right now all I can figure out is how to show trace from requirement to test case, which is not the filtering I need to see. I need to see the rollup of all requirements into a few test cases.
Corrina
------------------------------
corrina benjamin
------------------------------0