Another good document for military standards for software safety is AOP-52.

Has some fun anecdotes in it. My favorite being the nuclear certified supersonic aircraft having a latent defect discovered during integration of a new subsystem. Turns out all of the onboard flight computers crashed at the transition from sub to supersonic, thankfully the aircraft had enough inertia to "ride through" all of their flight computers simultaneously crashing during the transonic boundary.

Moral of that story is your software people need to have the vocabulary to understand the physical properties of the system they're working on.