How does a safety-critical computerization project ensure it is using "rigorously engineered" programs.

Question

People will wish to demonstrate experimental programs which have not been "rigorously engineered". This shouldn't matter so much as long as there is a secure audit trail of change to oprtaional baselines.

In practice though, won't the responsibility for keeping audit trails be "outsourced".

So you're very likely to end up with 4 experimental versions, and that's it. Someone decreed "Only keep the last 4 versions" so that's all you have.

Answer 1

Uhm. It does not? Duh. It ensures it's secured. But "Rigorously enginnered" calls for more than just safety.

Why is this in philosophy though?

-bf jb nm