In short
- Definition: The degree to which a system follows applicable laws, regulations, industry standards and internal policies.
- Goal: Avoid legal penalties and reputational damage, and maintain stakeholder trust.
- Example S.M.A.R.T. requirement: Zero high-severity findings in the annual compliance audit, and 100% of mandatory controls implemented.
1. Definition
As a non-functional requirement, compliance describes how well a system follows the laws, regulations, industry standards and internal policies that apply to it [1], [2], [3].
“Must be compliant” is not a requirement. “Must meet article X of rule Y, shown by evidence Z” is.Key takeaway
Typical sources are privacy laws, financial and health regulations, accessibility laws, records-keeping rules and the organization’s own security and data policies. Each one becomes concrete requirements: controls, records, approvals, reports.
Compliance is not a single property. The work is to list the applicable rules, translate each into testable requirements, and keep evidence that they are met.
2. Goal
The goal is to avoid fines, legal action and reputational damage, and to keep the trust of customers, partners and regulators.
Non-compliance found after launch can force a service to stop, data to be deleted or costly changes to be made under a regulator’s deadline.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| Applicable rules mapped | % of obligations traced to requirements | 100% | Compliance matrix |
| Mandatory controls implemented | % | 100% | Control testing by internal audit |
| High-severity findings | Count per audit | 0 | Audit report |
| Time to close findings | Days | < 90 days | Corrective action tracker |
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Privacy: “Before go-live, every personal data field shall be listed in the record of processing, with its legal basis and retention period, and approved by the privacy officer.”
- Finance: “The system shall meet all internal controls over financial reporting that apply to it, with no high-severity finding at the annual audit.”
- Policy: “All production changes shall follow the change-management policy, with 100% of changes linked to an approved ticket.”
5. Questions to Ask Stakeholders
- Which laws, regulations and standards apply in each country where the system is used?
- Which internal policies apply (security, data, records, procurement)?
- Who owns compliance for this system?
- What evidence will auditors expect, and where will it be kept?
- Are there upcoming regulatory changes we must anticipate?
- What is the impact of a breach of each rule?
6. Common Pitfalls
- Leaving compliance to legal alone. Rules must be turned into concrete system requirements with the delivery team.
- Not keeping evidence. Being compliant without proof does not pass an audit.
- Ignoring change. Regulations evolve. Schedule periodic reviews of the compliance matrix.
7. Related NFRs
- Certification — third-party confirmation of compliance with a standard.
- Privacy — privacy laws are a major source of compliance requirements.
- Auditability and Control — audit trails provide compliance evidence.
- Data Retention — many rules set how long records must be kept.
- Legal and Licensing — covers licensing and intellectual property obligations.
8. FAQ
The organization as a whole, but each system should have a named owner who keeps the compliance matrix and evidence up to date.
Break it into obligations, decide how the system meets each one, and write a testable requirement with the expected evidence.
No. Laws, policies and the system itself change, so compliance must be reviewed regularly.
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. | [4] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| FAQ | Frequently asked questions | List of common questions with their answers. | [5] |
| 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. | [3] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Audit trail | Chronological record of who did what and when, used to verify activity. | [6] |
| Personal data | Any information that relates to an identifiable person. | [7] |
| Procurement | Process of selecting and buying goods or services from suppliers. | [8] |
| Production environment | The live system that real users use, as opposed to test environments. | [9] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [10] |
10. Sources and Further Reading
- [1] “Regulatory compliance.” Wikipedia. https://en.wikipedia.org/wiki/Regulatory_compliance (accessed Nov. 18, 2026).
- [2] “ISO/IEC 27001:2022 Information security management systems.” ISO. https://www.iso.org/standard/27001 (accessed Nov. 18, 2026).
- [3] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [4] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [5] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [6] “Audit trail.” Wikipedia. https://en.wikipedia.org/wiki/Audit_trail (accessed Nov. 19, 2026).
- [7] “Personal data.” Wikipedia. https://en.wikipedia.org/wiki/Personal_data (accessed Nov. 19, 2026).
- [8] “Procurement.” Wikipedia. https://en.wikipedia.org/wiki/Procurement (accessed Nov. 19, 2026).
- [9] “Deployment environment.” Wikipedia. https://en.wikipedia.org/wiki/Deployment_environment (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 @hyson; inline photo by @pavstyuk, both on Unsplash.




