liveBook · Manning

Architectural requirement

As explained in Microservices Patterns, Second Edition

An architecturally significant requirement is a requirement that has a substantial influence on a system's architecture.

Architecturally significant requirements are requirements that substantially influence a system’s architecture. They identify concerns architecture must satisfy, unlike many user-facing features that can be implemented under a range of architectures. section 3.1.3

Three perspectives describe what architecture must address:

  • Non-functional requirements specify how well the system performs its functions and how easily it can be developed and maintained. section 3.1.3
  • Architecturally significant requirements focus on requirements that shape architectural choices; quality attributes offer another way to frame architecture’s purpose. section 3.1.3

Runtime requirement

An FTGO example specifies handling 233 order-creation requests per second with an average response time of 356 milliseconds. section 3.1.3

Figure 3.2 Three different perspectives on the purpose of an architecture’s architecture, which is multidimensional: traditional non-functional requirements, modern architecturally significant requirements, and quality attributes
purpose of architecture

Compare the three perspectives on the purpose of architecture: non-functional requirements, architecturally significant requirements, and quality attributes. section 3.1.3

How Microservices Patterns, Second Edition covers it

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.
How it connects
Connects architecturally significant requirements with non-functional requirements, quality attributes, and functional requirements.

Also explained in

Compare how 2 books explain architectural requirement →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.