NFRs and System Architecture

(1) To meet a performance NFR, you may have to organize the system to minimize communications between components

(2) A single security NFR may generate multiple related functional requirements that define new system services and restrict existing ones

(3) Reliability NFRs may require redundant components spread across the entire system

Explanation

NFRs can affect architecture in two ways: (1) They may affect the overall structure (e.g., minimizing inter-component communications for performance, or adding redundancy for reliability). (2) A single NFR like a security requirement may generate a number of related functional requirements defining new services. NFRs do NOT always map to a single component — their implementation is often diffused through the system.