Architectural Characteristics
Non-functional requirements ends with 'iliites' are not new in architecture community. The other meaning for NFR is architectural characteristics. If you carefully listen to stakeholders problems, you will discover many architectural characteristics in the form of domain concerns and they do not need to be explicitly documented by business analysts. These characteristics forms the basis for correct justifiable architecture decisions and style. A common anti-pattern is having all the non-functional requirements in the checklist and try to just each one of them in your solution. Keep the final list simple and relevant. For example, time to budget domain concerns leads to architectural characteristics such as simplicity and feasibility. One of the safest architectural style suitable to simplicity and feasibility is layered architecture not microservices architecture.