How does NANTeL ensure software integrity for safety-critical logic?

How does NANTeL ensure software integrity for safety-critical logic?

• A. By using ad-hoc bug fixes without formal process
• B. Formal software lifecycle with independent verification and validation against safety requirements
• C. By performing only post-deployment smoke tests
• D. By relying solely on hardware redundancy

Answer: (B)

A formal software lifecycle with independent verification and validation against safety requirements ensures software integrity for safety-critical logic. This approach creates structured stages—clear safety requirements, disciplined design and coding standards, systematic reviews, rigorous testing, and formal verification and validation activities—so every change is traceable from what the system must do to how it’s built and tested. Independent verification and validation adds an objective check by a separate team or group, ensuring evidence-backed assessment that the software actually meets safety criteria, not just what developers claim. This combination provides traceability, controlled change management, and documented evidence that the protection logic behaves correctly under defined conditions, including safety-critical scenarios. Ad-hoc bug fixes bypass formal review and documentation, risking unseen defects. Post-deployment smoke tests cover only superficial checks and don’t exhaust safety-critical failure modes.Relying solely on hardware redundancy addresses failures in hardware but does not guarantee the software behaves correctly or safely; software integrity requires deliberate, verifiable processes.

A formal software lifecycle with independent verification and validation against safety requirements ensures software integrity for safety-critical logic. This approach creates structured stages—clear safety requirements, disciplined design and coding standards, systematic reviews, rigorous testing, and formal verification and validation activities—so every change is traceable from what the system must do to how it’s built and tested. Independent verification and validation adds an objective check by a separate team or group, ensuring evidence-backed assessment that the software actually meets safety criteria, not just what developers claim. This combination provides traceability, controlled change management, and documented evidence that the protection logic behaves correctly under defined conditions, including safety-critical scenarios.

Ad-hoc bug fixes bypass formal review and documentation, risking unseen defects. Post-deployment smoke tests cover only superficial checks and don’t exhaust safety-critical failure modes.Relying solely on hardware redundancy addresses failures in hardware but does not guarantee the software behaves correctly or safely; software integrity requires deliberate, verifiable processes.