Reasoning and Why

Norms

There are many different reasons, why you need bidirectional traceability. E.g. in the automotive industry it is the ISO26262 or ASPICE.

As the ASPICE specification is public available let’s what is requested: https://vda-qmc.de/wp-content/uploads/2023/12/Automotive-SPICE-PAM-v40.pdf

Or within is documentation for Version Automotive-SPICE-PAM-v4.1 Figure D.4 — Bidirectional traceability and consistency.

Implemented with Sphinx-Needs

With Sphinx-Needs we get one tool to cover all demands of ASPICE (often you want to use a planning tool for change request management). Everything should be reviewed with github pull-requests or gitlab merge requests as a single point of review tool. You can protect branches with rules, so you can enforce all content is reviewed.

If you want to use sphinx-needs even as your ticket management tool, here are some hints:

You can find a Example with all classical ASPICE artifacts in this open source repository: