Which components are included in a formal software lifecycle for safety-critical systems?

Which components are included in a formal software lifecycle for safety-critical systems?

• A. Requirements, design, verification and validation
• B. Coding, compilation, deployment
• C. Maintenance only
• D. No formal lifecycle

Answer: (A)

Key idea: in safety-critical software, a formal lifecycle ensures safety by starting from clear safety requirements and proving through verification and validation that the final product meets those requirements. The essential approach includes four activities: capturing and managing requirements that state what the system must do and its safety constraints; designing a solution that fulfills those requirements; verifying that the design and implementation satisfy the requirements through reviews, analyses, and tests; and validating that the final product operates safely in the intended environment and meets safety goals. This structured flow provides traceability from requirements to implementation and the evidence needed to demonstrate safety. Merely coding, compiling, and deploying doesn’t provide the upfront and ongoing assurance needed for safety-critical contexts; maintenance alone focuses on keeping the system running rather than establishing safety assurances, and having no formal lifecycle means there’s no approved process to guarantee safety.

Key idea: in safety-critical software, a formal lifecycle ensures safety by starting from clear safety requirements and proving through verification and validation that the final product meets those requirements. The essential approach includes four activities: capturing and managing requirements that state what the system must do and its safety constraints; designing a solution that fulfills those requirements; verifying that the design and implementation satisfy the requirements through reviews, analyses, and tests; and validating that the final product operates safely in the intended environment and meets safety goals. This structured flow provides traceability from requirements to implementation and the evidence needed to demonstrate safety. Merely coding, compiling, and deploying doesn’t provide the upfront and ongoing assurance needed for safety-critical contexts; maintenance alone focuses on keeping the system running rather than establishing safety assurances, and having no formal lifecycle means there’s no approved process to guarantee safety.