liveBook · Manning

Nonfunctional requirement

As explained in Software Architecture Decision-Making

A requirement describing a system quality or constraint, such as operability, security, performance, or adaptability, rather than a business function.

A nonfunctional requirement names the qualities and constraints that let a system remain viable beyond feature delivery: security, scalability, observability, resilience, cost, operability, data integrity, and adaptability. Its failure is often delayed. A feature may ship successfully while the system accumulates an exposure that appears later in an incident, audit, migration, cost review, or urgent production failure. section 1.6

These requirements are architectural commitments, not a checklist applied after design. They emerge when vague business intent is clarified into technical objectives: functional and nonfunctional requirements, flows, boundaries, constraints, integration points, and the trade-offs among them. Premature solution choices can turn uncertain assumptions into difficult-to-reverse commitments. section 1.4

Keeping nonfunctional requirements effective requires ongoing attention:

  • Assign clear ownership for cross-cutting decisions; centralized and distributed responsibility can both work, while unowned concerns fade beneath deadline pressure. section 1.2
  • Preserve the reasoning behind constraints so that teams can distinguish an important protection from an obsolete temporary decision. section 1.2 section 1.6
  • Revisit assumptions as production feedback exposes costs, weak boundaries, legacy behavior, operational gaps, and technical debt. section 1.6
  • Apply restraint: protect decisions that preserve security, operational stability, data integrity, or boundaries, but do not redesign for every signal. section 1.6
Figure 1.2 Architectural responsibility can be centralized, distributed, or left unclear. The real risk is not the absence of an architect title, but the absence of clear ownership for cross-cutting technical decisions.

Ownership may be centralized or distributed; the material risk is leaving cross-cutting technical concerns without clear accountability. section 1.2

A useful decision heuristic is to make quality constraints explicit before feature pressure erases them, then test whether they still fit the system’s direction. Architecture remains coherent when decisions, consequences, and feedback stay visible across delivery, operations, security, finance, and leadership. section 1.8

How Software Architecture Decision-Making covers it

How deep it goes
Explains ongoing ownership, trade-offs, feedback, and revision, without prescribing quality-attribute metrics or implementation techniques.
Examples
Uses incidents, audits, migrations, cost reviews, production failures, security reviews, and alternative ownership models as concrete contexts.
What it assumes
Assumes familiarity with system delivery and stakeholders while clarifying how vague intent becomes requirements, constraints, and trade-offs.
What you can do after
Evaluate/understand when quality constraints need protection, renewed scrutiny, or restraint as operational evidence changes.
How it connects
Connects nonfunctional requirements to architecture, technical objectives, system boundaries, trade-offs, observability, security, and technical debt.

Also explained in

Compare how 9 books explain nonfunctional requirement →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Software Architecture Decision-Making. The section links point to the parts of the book it draws on.