Requirement management in safety critical software development context

General
1

Hi
regarding Using GitLab for ISO 26262-6:2018 - Product development at the software level | GitLab post,

The standard recommends defining requirements in accordance with ASIL level of a software application under development. These requirements need to be built and maintained in a traceable, versioned way.

You can manage work items needed to build requirements (as well as code) using GitLab issues.

I was wondering if requirements were actually written in the issue, and in that case it would not comply with the standard as Issue cannot be versioned, or if requirements were written in files versioned by Git ?

Or we can do both: Using Gitlab Issue to manage requirements day to day and then export requirement into textual files managed under configuration control by Git.

ISO26262, DO178

1 Like
2

Hi, did you get anywhere on this topic? I’ve just started to take a look at how to use gitlab for safety critical software projects, would be good to hear if/how others have done it.