# Introducing Traceability in GitHub for Medical Software Development

arXiv: https://arxiv.org/abs/2110.13034 · HTML: https://mlsanity.com/paper/2110.13034/

## Key facts

- Cited by 1 papers in the map (data through 14 Oct 2026).
- First posted on arXiv 25 Oct 2021.

## Built on by (most cited first, 1 of 1)

- [Continuous Design Control for Machine Learning in Certified Medical Systems](https://mlsanity.com/paper/2209.05843/) (2022)

## Abstract (arXiv)

Assuring traceability from requirements to implementation is a key element when developing safety critical software systems. Traditionally, this traceability is ensured by a waterfall-like process, where phases follow each other, and tracing between different phases can be managed. However, new software development paradigms, such as continuous software engineering and DevOps, which encourage a steady stream of new features, committed by developers in a seemingly uncontrolled fashion in terms of former phasing, challenge this view. In this paper, we introduce our approach that adds traceability capabilities to GitHub, so that the developers can act like they normally do in GitHub context but produce the documentation needed by the regulatory purposes in the process.