A business requirement defines a high-level goal or objective of the business, focusing on the "what" and "why" from a business value perspective. "Providing the best end-user experience" is a qualitative business objective aimed at improving user satisfaction and productivity. It does not specify technical implementation details, unlike the other options which define technical capabilities, quality of service attributes, or specific service level agreements (SLAs). These latter types are classified as technical or non-functional requirements that are derived from the overarching business requirement.

B. This is a technical requirement or constraint, specifying a technical capability needed for implementation rather than a primary business goal.

C. This describes non-functional requirements (security, resiliency) that support a business goal, focusing on how well the system should operate.

D. This is a specific, measurable non-functional requirement (availability) defining a quality of service, not a high-level business objective.

1. Arrasjid

J. Y.

Gabryjelski

M.

& McCain

C. (2013). IT Architect: Foundation in the Art of Infrastructure Design: A Practical Guide for IT Architects. VMware Press. Chapter 3

"The Discovery Process

" pp. 35-37

distinguishes between high-level business goals (e.g.

"improve customer service") and the more detailed functional and non-functional requirements derived from them.

2. VMware. (2020). VMware Validated Design 6.2 - Architecture and Design. In the "Introduction to VMware Validated Design" section

the documentation clearly separates "Business Objectives" from "Non-Functional Requirements

" listing Availability (SLAs)

Security

and Recoverability under the latter category. This framework classifies specific SLAs and resiliency as non-functional

supporting the idea that the high-level goal is the business requirement.