In short
- Definition: The ability of a system to avoid causing harm to people, property or the environment, including a safety margin beyond expected conditions.
- Goal: Prevent accidents and limit the consequences of failures.
- Example S.M.A.R.T. requirement: All identified hazards mitigated to an acceptable risk level, and a factor of safety of at least 2 on critical loads.
1. Definition
As a non-functional requirement, safety describes the ability of a system to avoid causing harm to people, property or the environment, including when things go wrong [1].
Safety is about what the system must never do, even when everything else fails.Key takeaway
Safety matters wherever software controls or influences the physical world: medical devices, vehicles, industrial machines, energy, railways, aviation. Standards such as IEC 61508 for functional safety define processes and safety integrity levels for such systems [2], [3].
Safety work starts with a hazard analysis: what could go wrong, how badly, and how likely. Each hazard then gets measures that reduce its risk to an acceptable level, often with a safety margin beyond expected conditions.
2. Goal
The goal is to prevent accidents and to limit the consequences of failures.
Unsafe systems can injure or kill people, and expose the organization to criminal liability, recalls and bans.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Hazards identified and mitigated | % of hazards with accepted residual risk | 100% | Hazard log |
| Factor of safety on critical loads [4] | Ratio | ≥ 2 (or as set by the applicable standard) | Engineering analysis |
| Safety-related incidents | Count | 0 | Incident records |
| Safety requirements verified | % | 100% before release | Verification matrix |
Safety targets depend heavily on the sector and its standards. Always derive them from the applicable regulation and a qualified safety assessment.
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Machine control: “All identified hazards shall be mitigated to an acceptable risk level, as recorded in the hazard log approved by the safety officer before commissioning.”
- Fail-safe: “On loss of communication with the controller, the conveyor shall stop within 1 second.”
- Medical: “The infusion pump software shall prevent any dose above the configured maximum, verified by tests covering all input combinations defined in the hazard analysis.”
5. Questions to Ask Stakeholders
- Could the system harm people, property or the environment?
- Which safety standards and regulations apply in our sector?
- What are the worst credible failures?
- What is the safe state when something goes wrong?
- Who is responsible for the safety assessment?
- How will safety requirements be verified and documented?
6. Common Pitfalls
- Treating safety like security. Safety is about accidental harm; it needs hazard analysis, not only protection from attackers.
- Relying on software alone. Critical protections often need hardware interlocks too.
- Late safety analysis. Hazards found late require costly redesign.
7. Related NFRs
- Reliability — fewer failures reduce, but do not replace, safety measures.
- Robustness — handling abnormal conditions safely.
- Physical — hardware design contributes to safety.
- Certification — safety-critical products often need certification.
- Ethics — avoiding harm to people is shared with ethics.
8. FAQ
The part of safety that depends on a system working correctly in response to its inputs, as covered by standards such as IEC 61508.
The condition the system moves to when a failure is detected, such as stopping a machine.
The ratio between what a system can withstand and the load it is expected to carry.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [5] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [6] |
| IEC | International Electrotechnical Commission | International standards body for electrical and electronic technologies; it publishes joint “ISO/IEC” standards with ISO. | [7] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [1] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Incident | Unplanned interruption or degradation of a service. | [8] |
| Log | Time-stamped record of events written by software, used for troubleshooting and audit. | [9] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [10] |
10. Sources and Further Reading
- [1] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [2] “Functional safety.” Wikipedia. https://en.wikipedia.org/wiki/Functional_safety (accessed Nov. 18, 2026).
- [3] “IEC 61508.” Wikipedia. https://en.wikipedia.org/wiki/IEC_61508 (accessed Nov. 18, 2026).
- [4] “Factor of safety.” Wikipedia. https://en.wikipedia.org/wiki/Factor_of_safety (accessed Nov. 18, 2026).
- [5] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [6] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [7] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [8] “Incident management.” Wikipedia. https://en.wikipedia.org/wiki/Incident_management (accessed Nov. 19, 2026).
- [9] “Logging (computing).” Wikipedia. https://en.wikipedia.org/wiki/Logging_(computing) (accessed Nov. 19, 2026).
- [10] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @tanyapaquet; inline photo by @umityildirim, both on Unsplash.




