While gathering nonfunctional requirements for developing a portal, which three aspects should a business analyst check to ensure that the solution developed will be fit for use by the customer?…

The correct answer is B. Uptime D. Ease of use E. Reliability. Nonfunctional requirements define HOW a system performs, not WHAT it does. Uptime (B) is an availability/reliability metric specifying when the system must be operational. Ease of use (D) is a usability requirement describing how intuitively customers can interact with the…

Business Analysis Frameworks

Question

While gathering nonfunctional requirements for developing a portal, which three aspects should a business analyst check to ensure that the solution developed will be fit for use by the customer? (Choose three.)

Options

ANavigation
BUptime
CData integrity
DEase of use
EReliability

How the community answered

(36 responses)

A
3% (1)
B
86% (31)
C
11% (4)

Explanation

Nonfunctional requirements define HOW a system performs, not WHAT it does. Uptime (B) is an availability/reliability metric specifying when the system must be operational. Ease of use (D) is a usability requirement describing how intuitively customers can interact with the portal. Reliability (E) specifies how consistently the system performs without failure. These three are classic nonfunctional (quality attribute) requirements. Navigation (A) describes functional UI flows, and data integrity (C) is a functional data correctness requirement - neither falls under nonfunctional 'fit for use' quality attributes.

Topics

#Nonfunctional requirements#Requirements gathering#Business analysis#Usability

Community Discussion

No community discussion yet for this question.

Full CAPM Practice