Hi HN, I'm curious what tools your team is using to maintain a database of requirements that are linked to test cases and test case results.<p>I'm personally looking for something lightweight and self hosted, (maybe like git-bug) oriented for small teams or individuals. However, I'm also interested in what large teams are doing as well.
The old school approach is to use Excel and a Requirements Traceability Matrix. It’s not fancy, but it works, especially when plans, procedures and test results point back to the matrix. The failure in traceability is usually human error or lack of compliance. It has to be a team priority and enforced by management and work style/environment.<p>Here are some options/things to look at in making your decision:<p><a href="https://www.dau.edu/tools/Documents/SAM/resources/RTM_Risk_Register.html" rel="nofollow">https://www.dau.edu/tools/Documents/SAM/resources/RTM_Risk_R...</a><p><a href="https://www.perforce.com/blog/alm/what-traceability" rel="nofollow">https://www.perforce.com/blog/alm/what-traceability</a><p><a href="https://www.jamasoftware.com/requirements-management-guide/requirements-traceability/what-is-traceability-and-why-does-it-matter-for-product-teams/" rel="nofollow">https://www.jamasoftware.com/requirements-management-guide/r...</a><p><a href="https://www.inflectra.com/Ideas/Topic/Requirements-Traceability.aspx" rel="nofollow">https://www.inflectra.com/Ideas/Topic/Requirements-Traceabil...</a>