In short
- Definition: The accuracy, consistency and completeness of data throughout its life cycle, protected against unauthorized or accidental change.
- Goal: Ensure decisions and transactions rely on correct and trustworthy data.
- Example S.M.A.R.T. requirement: Zero checksum mismatches and fewer than 0.01% of records failing validation rules in monthly reconciliation.
1. Definition
As a non-functional requirement, data integrity describes the accuracy, consistency and completeness of data throughout its life, and its protection against unauthorized or accidental change [1], [2].
Wrong data that looks right is worse than missing data. Integrity requirements must say how errors will be detected.Key takeaway
It covers several layers: validation when data is entered, constraints in the database (keys, types, references), safe handling of concurrent updates, checksums when data is stored or transferred, and access controls that prevent tampering.
In ISO/IEC 25010:2023, integrity is a sub-characteristic of security, focused on preventing unauthorized modification. In daily practice, data quality errors caused by bugs or bad inputs are just as important [3].
2. Goal
The goal is that decisions, payments, reports and legal records are based on data that is correct and can be trusted.
Integrity failures are often silent: a rounding error, a duplicated record or a truncated file can spread through many systems before anyone notices.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Records failing validation | % of records | < 0.01% | Monthly data-quality checks |
| Checksum mismatches | Count | 0 | Automated verification on storage and transfers |
| Reconciliation differences | Count or amount | 0 unexplained differences | Reconciliation between source and target systems |
| Unauthorized changes detected | Count | 0 | Audit logs and integrity monitoring |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Financial data: “Daily reconciliation between the order system and the accounting system shall show zero unexplained differences; any difference shall raise an alert within 1 hour.”
- Data migration: “After migration, record counts and control totals shall match the source system exactly for 100% of tables.”
- File transfers: “Every file exchanged with partners shall be verified with a checksum, and corrupted files shall be rejected automatically.”
5. Questions to Ask Stakeholders
- Which data is critical for money, safety or legal obligations?
- Where does the data come from, and how reliable are those sources?
- Which validation rules apply when data is entered or imported?
- How will differences between systems be detected and resolved?
- Who is allowed to change critical data, and is every change recorded?
- What should happen when corrupted data is detected?
6. Common Pitfalls
- Validating only in the user interface. Imports and APIs bypass the screens. Validate at the service and database level too.
- Ignoring concurrency. Two users updating the same record can silently overwrite each other. Use locking or version checks.
- No reconciliation. Without regular comparisons between systems, drift goes unnoticed for months.
7. Related NFRs
- Security — protects data against unauthorized change.
- Auditability and Control — records who changed data and when.
- Backup — good backups let you restore correct data after corruption.
- Durability — ensures stored data is not lost or degraded.
- Interoperability — data exchanged between systems must keep its meaning and accuracy.
8. FAQ
Data quality is the broader fitness of data for use; integrity focuses on accuracy, consistency and protection against improper change.
A checksum is a value computed from the data. If it changes after storage or transfer, the data has been altered or corrupted.
Partly. Security protects against malicious change, but bugs and bad inputs also damage integrity, so both must be covered.
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. |
|---|---|---|---|
| ISO | International Organization for Standardization | Independent international body that publishes standards, such as ISO/IEC 25010 for software quality. Its short name comes from the Greek “isos” (equal) and is said as a word. | [4] |
| 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. |
|---|---|---|---|
| API | Application programming interface | Defined way for one program to request data or services from another. | [6] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [7] |
| IEC | International Electrotechnical Commission | International standards body for electrical and electronic technologies; it publishes joint “ISO/IEC” standards with ISO. | [8] |
| 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. | [2] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Checksum | Small value computed from data to detect accidental changes or corruption. | [9] |
| Concurrent users | Users active on the system at the same moment. | [10] |
| Data migration | Moving data from one system or format to another. | [11] |
| Database | Organized store of data that software can query and update. | [12] |
| Log | Time-stamped record of events written by software, used for troubleshooting and audit. | [13] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [14] |
| Transaction | Unit of work, such as a payment or an order, that must complete fully or not at all. | [15] |
10. Sources and Further Reading
- [1] “Data integrity.” Wikipedia. https://en.wikipedia.org/wiki/Data_integrity (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “ISO/IEC 25010 product quality model.” ISO 25000. https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 (accessed Nov. 18, 2026).
- [4] “International Organization for Standardization.” Wikipedia. https://en.wikipedia.org/wiki/International_Organization_for_Standardization (accessed Nov. 19, 2026).
- [5] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [6] “API.” Wikipedia. https://en.wikipedia.org/wiki/API (accessed Nov. 19, 2026).
- [7] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [8] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [9] “Checksum.” Wikipedia. https://en.wikipedia.org/wiki/Checksum (accessed Nov. 19, 2026).
- [10] “Concurrent computing.” Wikipedia. https://en.wikipedia.org/wiki/Concurrent_computing (accessed Nov. 19, 2026).
- [11] “Data migration.” Wikipedia. https://en.wikipedia.org/wiki/Data_migration (accessed Nov. 19, 2026).
- [12] “Database.” Wikipedia. https://en.wikipedia.org/wiki/Database (accessed Nov. 19, 2026).
- [13] “Logging (computing).” Wikipedia. https://en.wikipedia.org/wiki/Logging_(computing) (accessed Nov. 19, 2026).
- [14] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [15] “Database transaction.” Wikipedia. https://en.wikipedia.org/wiki/Database_transaction (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @purzlbaum; inline photo by @kommumikation, both on Unsplash.




