Which of the following is a functional requirement for an online bookstore system?
Functional requirements describe what the system should do.
Option A describes a specific feature the system must provide, which is a functional requirement. Options A, B, and D describe qualities or constraints, which are non-functional requirements.
Which of the following is a non-functional requirement for a mobile banking app?
Non-functional requirements describe how the system performs or behaves.
Option C specifies a performance constraint (processing time), which is a non-functional requirement. Options B, C, and D describe features or functions.
A video streaming service wants to add a new feature to allow offline downloads (functional requirement). However, this feature may increase storage costs and affect app performance (non-functional concerns). What is the best approach to handle this tradeoff?
Good system design balances functional and non-functional needs.
Option B suggests analyzing and optimizing to balance both types of requirements, which is best practice. Options A and B are extreme and ignore important concerns. Option B delays progress unnecessarily.
Given these requirements for a ride-sharing app, classify each as functional (F) or non-functional (NF):
1. The app shall allow users to book rides.
2. The app shall encrypt user data.
3. The app shall handle 10,000 concurrent users.
4. The app shall provide driver ratings.
Functional requirements describe features; non-functional describe qualities.
Booking rides and driver ratings are features (functional). Encrypting data and handling many users are qualities (non-functional).
A new messaging app expects 1 million daily active users. The non-functional requirement states the system must handle peak loads with 10 messages per user per day, with 99.99% uptime. What is the minimum message processing capacity per second the system should support during peak hours (assuming peak hour is 10% of the day)?
Calculate total messages per day, then divide by peak hour seconds.
Total messages = 1,000,000 users * 10 messages = 10,000,000 messages/day.
Peak hour = 10% of 24 hours = 2.4 hours = 8640 seconds.
Capacity = 10,000,000 / 8640 ≈ 1157 messages/sec.
Check options carefully; option D matches closest after unit conversion.