RFC: Requirements tracking

[atodorov]

Several people have expressed to me verbally or via email the need for requirements tracking functionality without defining that into more details. This is a required feature for development and testing in heavily regulated areas (e.g. medical, aerospace, finance) or more conservative software companies.

Currently we can express requirements documents via Parent-Child test plans and using the extra link/requirements link of test cases. However this is not integrated with reporting or anything else.

RFCs, ideas and examples of how other TMS systems are providing this functionality are welcome. Vote with a :+1: (top-right corner) to boost this issue!

[atodorov]

Here are some standards that govern testing in the aerospace industry:

• ECSS‐E‐ST‐10‐02 - Verification
• ECSS‐E‐ST‐10‐03C ‐ Testing
• ECSS‐Q‐ST‐10‐09 ‐ Non-conformance control System (others call that bug reports, issue tracking)

[nuess0r]

This is an example how far the integration between two tools can go, for Simulink and DOORS: https://ch.mathworks.com/help/slrequirements/ibm-rational-doors-traceability.html?s_tid=srchtitle

It's very luxury because one can browse the DOORS requirements directly from Simulink and create links (which are stored in DOORS). So document exports from DOORS will also show this outgoing links.

In the end of the day, our customers expect three documents:

• Technical specification (In our case DOORS requirements module)
• Verification plan, describes how each requirement is verified including it's method. Some will be verified by test. Only this ones need to be traced in Kiwi. (In our case DOORS verification module)
• Verification report, states that the requirements are successfully verified. Contains lots of tables linking each requirement to the executed verification as described in the plan. Attached are test reports with further details. (In our case this is also an export of the DOORS verification module now including the verification state and links to the according reports)

Normally a test report contains tables to show, which test case verified which requirement. For the reporting it would be helpful to select if this table is sorted by test case or by requirement because one test case often verifies several requirements (Also true for the opposite, a requirement like "initial state after reset is ..." is verified in several test cases). This tables is what I would expect that Kiwix generates/handles somewhere in the test planning and reports to be able to trace the requirements.

Optimum is like in the Simulink example, that Kiwi transfers the test status (pass/fail) with date and reference to the report into the DOORS verification module. But this is far down the road :-)

[gArtur]

Hi,

I think that for start it would be great if requirement tracking will work like this:

• At first user creates new requirements for product with fields: Title, Description, Tests (more fields to add in future, like Type etc...)
• After that user can add requirements to test cases
• New metric is added to Test Plan and Test Run - Requirement coverage [%]
• User can check from requirements details what test cases are linked to specific requirement

[Gaket]

Here is how the requirements traceability implemented in Testrail and in Qase and a small picture in Kuality

[petr-nechaev]

Adding requirements as a separate entiry and making them traceable and versioned would make possible to generate a Requirements Traceability Matrix which is needed for ASPICE automotive process.