Quality Attributes

Definition

Quality attributes describe the non-functional properties of a business capability, service, or supporting system: how fast it responds, how securely it handles data, how reliably it operates under load, how easily it can be changed, and how well it scales as demand grows. They sit alongside functional requirements — what the capability must do — as the second half of any complete requirements picture. A claims processing capability, for example, has a functional definition (adjudicate and settle claims) and a set of quality attributes that determine whether it does so acceptably (turnaround time, auditability, fault tolerance, data confidentiality). In business architecture, quality attributes are most often expressed as targets or thresholds attached to a capability, value stream stage, or service — not as abstract engineering jargon. Common categories include performance, availability, security, scalability, usability, maintainability, interoperability, and compliance/auditability. These targets become the bridge between business expectations articulated in strategy or customer commitments and the technical architecture decisions made downstream by solution and technical architects. Quality attributes are bounded by context: they are not universal ideals to be maximized but trade-off decisions calibrated to business criticality, risk appetite, and cost tolerance. A capability supporting a regulated, customer-facing process typically carries far stricter quality attribute targets than an internal reporting capability, even if both sit in the same operating model.

Origin & Context

The term originates in software and systems engineering, formalized in standards such as ISO/IEC 25010 (the SQuaRE model) and long referred to informally as "non-functional requirements" or the "ilities." TOGAF incorporates quality attributes into its Architecture Definition and Requirements Management phases, requiring architects to capture them alongside functional requirements when defining target-state architectures. Business architecture practice, guided by frameworks like the BIZBOK, adopted the concept to ensure capability and value stream definitions capture expected performance and risk characteristics, not just scope.

Why It Matters

Business architects who leave quality attributes undefined hand solution architects a blank check — leading to over-engineered, expensive builds or under-engineered ones that fail under real-world load or audit scrutiny. CIOs and CTOs rely on clearly stated quality attributes to size infrastructure investment correctly and to defend architecture decisions during budget reviews. Compliance and risk leaders care because attributes like auditability and data security often map directly to regulatory obligations. Getting quality attributes right at the capability level materially reduces costly rework, failed audits, and production incidents traced back to requirements no one wrote down.

Common Misconceptions

Myth: Quality attributes belong to technical architecture, not business architecture.

Reality: Business architects define the business-relevant thresholds — how resilient a capability must be, how quickly a service must respond to customers, how auditable a process must remain — before solution and technical architects translate those into system-level design. Skipping this step means technical teams guess at business risk tolerance.

Myth: Higher quality attribute targets are always better — maximum availability, maximum security, maximum speed.

Reality: Every quality attribute target carries a cost and often trades off against another attribute. Near-perfect availability increases infrastructure spend substantially; maximum security controls can degrade usability. Architects set targets to match business criticality, not theoretical ideals.

Myth: Quality attributes and service level agreements (SLAs) are the same thing.

Reality: Quality attributes are architectural design targets; SLAs are the contractual or operational commitments negotiated with a business unit or external customer, usually derived from — but narrower and more formal than — the underlying quality attribute definitions.

Practical Example

A business architect maps the claims processing capability for a mid-sized insurer and identifies it as a strategic differentiator tied to customer retention. Rather than leaving performance implicit, the architect works with the claims operations lead and enterprise architecture team to define quality attribute targets: response time for straightforward claims, availability during catastrophe events, auditability for regulatory examination, and data confidentiality for sensitive medical information. These targets are documented directly on the capability model and shared with solution architects designing the supporting claims platform. During a subsequent vendor selection, the quality attribute targets become explicit evaluation criteria rather than an afterthought, allowing the architecture review board to reject a lower-cost platform that could not meet the auditability requirement. The capability owner also uses the same targets later to set realistic expectations with the business during a period of claims volume surge tied to a major weather event.

Industry Applications

Financial Services

Regulatory reporting and transaction processing capabilities carry strict auditability, traceability, and data integrity quality attributes tied directly to examiner and regulator expectations.

Healthcare

Patient data and care coordination capabilities emphasize security, privacy, and availability quality attributes to satisfy patient safety requirements and health data protection obligations.

Manufacturing

Supply chain visibility and production scheduling capabilities prioritize low-latency data and scalability quality attributes to support real-time operational decision-making.

Insurance

Claims and underwriting capabilities set reliability and responsiveness quality attributes that directly shape customer experience during high-stress moments like a claim event.

Related Terms

• Solution Architecture: the discipline that translates quality attribute targets into system design