Architectural requirement
An architectural requirement is a requirement whose fulfillment or correctness substantially influences or can change a system’s architecture.
Decision Engineering
An architecturally significant requirement is a requirement whose correctness or fulfillment can determine or substantially change a system's architecture.
- How it is used
- Flags requirements that merit architectural attention before a team commits to a solution.
- How deep it goes
- Defines ASRs and gives a three-step identification test, while leaving judgment about a particular design’s limits to the team.
- Examples
- Contrasts full-text search across customer-related entities with ordinary filters, then places both in a customer-record search requirements table.
- What you can do after
- Practice identifying architecture-shaping requirements by testing what would force abandonment of a minimal design.
Read how Decision Engineering explains architectural requirement →
Microservices Patterns, Second Edition
An architecturally significant requirement is a requirement that has a substantial influence on a system's architecture.
- How it is used
- Frames requirements that architecture must satisfy, including runtime behavior and development-time concerns.
- How deep it goes
- Defines the perspectives and illustrates runtime requirements, without detailing a method for identifying significant requirements.
- Examples
- Uses FTGO order-creation throughput and response time to illustrate a runtime requirement.
- What you can do after
- Evaluate how runtime and development-time requirements bear on architectural choices.
Read how Microservices Patterns, Second Edition explains architectural requirement →
Also covered in
Related concepts
- nonfunctional requirementincludes · A nonfunctional requirement specifies a system quality, constraint, or operating condition rather than a particular function or behavior.
- requirementskind of · A requirement is a stated need, capability, quality, condition, or constraint that a system, product, solution, or project is expected to satisfy.
- software architectureconfigures · Software architecture is the significant structure of a software system, including its components, relationships, and design decisions that shape how the system is built and behaves.
Questions about architectural requirement
What is architectural requirement?
An architectural requirement is a requirement whose fulfillment or correctness substantially influences or can change a system’s architecture.
Which Manning books explain architectural requirement?
Decision Engineering and Microservices Patterns, Second Edition.
What kinds of architectural requirement are there?
Kinds of architectural requirement include nonfunctional requirement.
What is architectural requirement a kind of?
Architectural requirement is a kind of requirements. A requirement is a stated need, capability, quality, condition, or constraint that a system, product, solution, or project is expected to satisfy.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

