- Author
- Not stated
- Published
- Last edited 8 July 2026
- Kind
- Wikipedia reference article on a software quality practice
- Original
- en.wikipedia.org/wiki/Software_assurance
- Subject
- Formal methods and proof
What it is
Volunteer editors wrote this overview. It defines the term and describes how organisations pursue it. It also collects definitions from several bodies.
What it says
- The article defines software assurance as a process ensuring reliability, safety and security of software.
- It quotes NIST: confidence that software is free from vulnerabilities, intended or accidental.
- It cites a security author saying design flaws account for 50% of security problems.
- It lists tool types such as static analysis, dynamic analysis and fuzz testing tools.
- It says machine learning is increasingly used to detect software problems.
- It describes initiatives as programs and activities to ensure software quality, reliability and security.
- It gathers alternate definitions from DHS, DoD, NASA, OMG and other bodies.
What evidence it gives
The article offers definitions and descriptions of practices. It cites standards, government documents and papers. It gives no data or case studies.
Interests and limits
Volunteers wrote the article and no author is named. The prose is general, and the techniques are described briefly. The claim about design flaws comes from one cited book. The reference list was not checked. A hatnote warns the topic is not the Microsoft product of the same name.