A non-functional requirement specifies how well an application performs its functions and how easily it can be developed and maintained. These requirements are closely tied to architecture. section 3.1.3
They describe two aspects of an application:
- Runtime behavior, such as scalability and performance. section 3.1.3
- Development-time characteristics, such as how easily the application can be changed and deployed. section 3.1.3
FTGO performance target
One example is handling 233 create-order 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
Compare the traditional non-functional-requirements perspective with architecturally significant requirements and quality attributes. section 3.1.3








