Analysis and planning for NFRs
The software architect collates and leverages knowledge about the domain and the system under development. Analysis and planning for non-functional requirements includes leveraging an organization-specific NFR framework and artifacts and initial gathering of non-functional requirements. Certain non-functional requirements can be arrived at via planning and analysis activities. As a case in point, business continuity requirements can be arrived at via business impact analysis, service impact analysis, and risk analysis; all three analytical activities are part of the service continuity management in the ITIL framework. Similarly, cost of service unavailability analysis can help the organization arrive at service ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access