For developing safety-critical software might there be "key factors for success" ?

Might there be "key factors for success" for developing software ?


Might "software refinement" be a key factor for success, a pre-requisite for any kind of quality ?

Might "prototyping" be a key factor for success, pre-requisite for any kind of quality ?

What visibility would you have that "prototyping" is actually occurring ?

Even if some of your staff rediscover the necessity for "prototyping", what guarantees are there that this fact won't be "forgotten" again so that the "development section" goes back to "business as usual" ?

Would some organisations supposedly developing safety-critical software forget, and re-remember, many times, the necessity for "prototyping" ?

no such thing exist...

If its as important as I think it is then they wont let them selfs forget as long as the software stays at a level they can understand.

Prototyping is a methodology that has been historically used for identifying requirements for an expensive product. It is only because the software industry is so immature that workers in this industry think the concepts of production are all new.
In relation to "safety-critical software" there is great doubt about the ability of the developer to obtain complete requirements before starting coding of an application. It might be possible to achieve the goal of extreme reliability by using alternative methods of obtaining requirements. I work with a programmer that has worked in support of engineering of Aerospace vehicles for 46 years. He understands the requirements related to the tools he is asked to create almost before the engineers ask for them.

it is not necessary