Chapter 10. Cross-Functional Requirements Testing
Functional requirements are the core services businesses offer customers, like booking a ride with a ride-hailing app or making a payment with an internet bank. However, just implementing these functional requirements isn’t enough to guarantee success. If the process takes too long, is too complex, or exposes your personal data, you won’t want to use that app. That’s where cross-functional requirements (CFRs) come in: characteristics of the application that have to be built into every functional feature. They complete the application, increase its quality, and make it competitive in the market. Here are some examples of CFRs for a ride-hailing app:
-
The app should respond to users within x seconds.
-
Users should be able to perform any action within n steps.
-
The app should transmit and store the users’ details securely.
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