← Notes
Architecturally-significant Requirement (ASR)
An architecturally-significant requirement (ASR) is any requirement—functional or non-functional—that has a measurable effect on a software system’s architecture. ASRs drive structural decisions, influence trade-offs, and often manifest as quality attributes such as scalability, performance, security, or reliability.
Why ASRs Matter
- Guide architectural choices and trade-offs
- Expose quality attributes that shape structure
- Help prioritize work in Architecture Decision Records
- Provide early warning when requirements threaten feasibility
Related Concepts
- [[Architecture Decision (AD)]] — design choices that address ASRs
- [[Architecture Decision Records]]
- [[Engineering Strategy]]
- [[Pre-Mortem Analysis]] — surfacing risky requirements early
Definition referenced from standard software architecture practice.
Linked References
- [[Architecture Decision (AD)]]
A software design choice that addresses an architecturally-significant requirement.
- [[Architecture Decision Log (ADL)]]
A collection of all Architecture Decision Records for a project or organization.
- [[Architecture Decision Records (ADRs)]]
Lightweight documentation format for recording architectural decisions and their context.