Software safety is a ______ activity that focuses on the identification and…

Concept

Software quality assurance (SQA) is the umbrella process activity that runs in parallel with every other software engineering activity. It fixes the standards a project must meet and then applies planned, systematic procedures to give management independent confidence that the process and the product conform to those standards. Safety is one of the concerns this discipline carries: whenever a failure can cause loss of life, injury, damage, or the collapse of the surrounding system, the same systematic apparatus is turned on hazards instead of ordinary defects.

Application to this question

The blank has to name the activity whose focus is the identification and assessment of potential hazards. In the standard software engineering treatment, software safety is defined precisely as a software quality assurance activity of exactly that kind, and it is carried out in three steps:

1. Hazards are identified and categorised by criticality and by risk. For a computer-controlled cruise control, one such hazard is "causes uncontrolled acceleration that cannot be stopped".

2. Analysis techniques such as fault tree analysis, real-time logic, or Petri net models are used to trace how each hazard could propagate from a component fault into a system-level failure.

3. Safety-related requirements are then specified so that the hazard is eliminated, or so that its consequences are controlled if it does occur.

The blank therefore names the umbrella quality activity under which hazard identification and assessment is performed, which is software quality assurance.

Cross-check against the other choices

• Risk mitigation, monitoring and management is the step that follows once risks have already been listed: it plans how to reduce each risk, tracks its indicators, and fires a contingency plan when a risk becomes a real problem. It can be pointed at technical and safety-related risks too, but it acts on risks that have already been identified, so it is not the umbrella quality activity that the standard definition names.

• Software cost estimation converts an estimate of product size in lines of code or function points into effort, schedule and cost through a model such as COCOMO. It carries no hazard dimension at all.

• Defect removal efficiency is a metric rather than an activity: DRE = E / (E + D) reports the proportion of problems caught before delivery, which measures how good the project's filters were rather than identifying or assessing any hazard.