Safety - Driving Development Process from the Safety Case

Link to report - It is really worth to read that report itself!
(Christopher Hobbs, Simon Diemert, Jeff Joyce)

A small article outlining that safety is developed alongside the process and continuously ensured throughout the overall development. It aims to avoid verifying safety only at the end of development by collecting ‘what is available’. Safety must be continuously planned, ensured and documented during the development process.

Especially, at beginning of a project, you should define how you intend to ensure safety. This improves the efficiency of the overall development process by focusing on the required means. If there is no plan, the participants within the team will manage safety evidence independently. Most probable it will create redundant work while forgotting important aspects because it was assumed that the other team will handle it. ==> Too much is made while not being complete.

Additionally, at the end, one is 'driven' and naturally influenced to prove safety, finding more 'completed' tasks rather than gaps. This is where confirmation bias comes into play.

Moreover, it is recommended to choose a structured representation (for example, GSN, which I personally have never heard of).

Conclusion:

• You should not search for arguments at the end.

• You should plan at start of project what arguments are needed and track them down!