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.
翻译:确保从要求到执行的可追踪性是发展安全关键软件系统的一个关键要素。 传统上,这种可追踪性是通过类似瀑布的过程来保证的,在这个过程中,各个阶段相继相继,不同阶段之间的追踪可以管理。 但是,新的软件开发模式,如连续软件工程和DevOps,鼓励开发者在前阶段阶段以看似不受控制的方式以稳定的方式进行的新特征流,对这一观点提出了挑战。 在本文件中,我们引入了为GitHub增加可追踪能力的方法,以便开发者能够像在GitHub环境中通常那样行事,但提供进程中监管目的所需要的文件。