Elicitation Questions (CMPE451)

1. User Requirements

Registration & Login

• What password safety criteria should be implemented (e.g., length, symbols, etc.)?
• How should email verification be handled, and should the link have an expiration time?
• What should happen if a user fails to verify their email address?

User Types

• Should global users have any additional functionalities beyond viewing posts, exchange rates, and profiles?
• Should registered users have more content interaction abilities beyond those listed (e.g., additional engagement features)?

Posts and Content

• What types of graphs should registered users be able to add to their posts?
• Should users be able to associate multiple currencies or stocks with a single post?

Portfolio

• Should users be able to edit their portfolios after creation?
• Should there be a specific way to visualize or analyze the portfolios?

Badges

• What specific abilities should badges grant users?
• Should badges be linked to user activity (e.g., number of posts) or performance (e.g., accuracy of posts)?

2. System Requirements

Search & Filtering

• How advanced should the semantic search be? Should it understand context or rely solely on keywords?
• Should users be able to filter search results by multiple criteria at once (e.g., post author, currency, portfolio)?

Performance

• What should happen if the system fails to load content within 3 seconds?
• Should the system give feedback to users if response times exceed certain limits?

Scalability

• Should the application be designed to handle more than 5000 concurrent users if demand increases?
• How will the system handle performance under peak usage conditions?

3. Non-Functional Requirements

Platforms & Compatibility

• Should the mobile application include any special functionality for offline use?
• Are there any specific screen resolutions or devices that need additional consideration?

Security

• What encryption algorithms should be implemented for user credentials?
• Should login activity notifications be sent to users as part of the security features?

Privacy & Legal Compliance

• How should the application allow users to manage their privacy settings (e.g., public vs. private profile)?
• Should users be informed about how their data is being used and be able to manage consent?

4. Content Updates

News & Exchange Rates

• How freqently should the exchange rates and financial news be updated?
• Should users be able to subscribe to receive notifications about specific currencies or stock updates?

5. Testing and Validation

Performance Testing

• What is the maximum expected user load, and should the system be stress-tested beyond 5000 concurrent users?
• What performance metrics will determine if the system meets the expected responsiveness?

Data Validation

• What should the system do if invalid data is entered during registration, portfolio creation, or other forms?
• How should the system handle errors like failed email verifications or forgotten password attempts?