Which pairing correctly matches functional and non-functional examples?

Which pairing correctly matches functional and non-functional examples?

• A. Functional: response time; Non-functional: login function
• B. Functional: data model; Non-functional: color of UI
• C. Functional: security; Non-functional: data backup frequency
• D. Functional: login function; Non-functional: response time

Answer: (D)

The difference you’re being tested on is between what the system can do (functional) and how well it does it (non-functional). A functional requirement describes a specific task or operation the software must perform, like the login process. A non-functional requirement describes a quality or constraint on that capability, such as how quickly the system should respond during login. The best match is: functional aspect is the login function, a concrete operation the system performs; non-functional aspect is the response time, which specifies how fast that operation should complete. Why the others don’t fit: in the first option, the function and the performance measure are swapped—the functional item is a performance metric, not a function, while login is the actual function. In the second option, a data model is a design artifact that underpins how data is handled (not a direct user-facing function), whereas color of the UI is a non-functional quality; mixing a design artifact as functional isn’t consistent with the distinction. In the third option, security and data backup frequency are both quality attributes (non-functional), with no clear functional operation described.

The difference you’re being tested on is between what the system can do (functional) and how well it does it (non-functional). A functional requirement describes a specific task or operation the software must perform, like the login process. A non-functional requirement describes a quality or constraint on that capability, such as how quickly the system should respond during login.

The best match is: functional aspect is the login function, a concrete operation the system performs; non-functional aspect is the response time, which specifies how fast that operation should complete.

Why the others don’t fit: in the first option, the function and the performance measure are swapped—the functional item is a performance metric, not a function, while login is the actual function. In the second option, a data model is a design artifact that underpins how data is handled (not a direct user-facing function), whereas color of the UI is a non-functional quality; mixing a design artifact as functional isn’t consistent with the distinction. In the third option, security and data backup frequency are both quality attributes (non-functional), with no clear functional operation described.