Skip to content

Elicitation Questions

Işıl Su Karakuzu edited this page Mar 18, 2024 · 2 revisions

Elicitation Questions

  1. Should the guest user be able to sign up with Google or Steam?

I advise against it. It's unnecessary effort, and I don't recommend it.

  1. Should we send email to users when signing in? and also when they forget their password?

It should be a base feature. Users expect to receive emails or SMS for these actions.

  1. We have private lists, should we also have total private profiles?

Reviews should definitely be public, while playlists could be private, shared with friends only, or public. Total private profiles should not exist.

  1. Should there be bot detection?

It's unnecessary. Instead, focus on basic security measures like preventing SQL injection and cross-site scripting.

  1. Should a user use the platform without logging in? If so, which features require them to be login or signed-up?

It's reasonable to allow users to access the platform without logging in, with limited content visibility.

  1. Should there be an algorithm which determines the games in the main page according to the user’s preferences such as favorite genre?

Avoid complex algorithms; consider manual curation or simpler methods like displaying posts with the most likes in the last 24 hours.

  1. Should we have special administrator accounts in the application?

Yes, there should be special administrator accounts for quick edits without accessing the database. One account should suffice, and to regular users, it should appear as a normal user account.

  1. Should (signed-in/guest) users be able to report or block other registered users for hate, violence, etc.?

Reporting functionality should be available to signed-in users only, simplifying the interface. Guest users should not have access to this feature, as tracking their reports could be challenging.

  1. Should the search bar be visible from all pages? Should it have the same functionality across all pages?

Having an advanced search option visible on every page would be beneficial. Consistent functionality across all pages is essential for user experience.

  1. Should we have both followers and friends?

While having both followers and friends can be beneficial, it may also be excessive. Consider the potential for simplification, while ensuring necessary social features are retained.

  1. Should we silently remove deleted content or explicitly mark it as deleted by the user? (both in the case of manually deleted reviews and deleted accounts)

It is mandatory to have account deletion and post deletion features. Whether to silently remove deleted content or explicitly mark it as deleted by the user is up to you. I recommend marking the content as 'deleted by the user,' similar to Reddit's functionality. Additionally, users can have the option to restore deleted accounts within a 30-day period if desired.

  1. Do we need to do the Responsibility Assignment Matrix, or some other planning table?

Yes. Divide the team into three groups: frontend, backend, and mobile. Consider a high-level Gantt chart within milestones, focusing solely on implementation planning. Incorporate aspects related to software design.

🏠 Home

🔬 Lab Reports

📝 Online Meeting Notes

📹 User Scenarios

📑 UML Diagrams

🎓 Who We Are

CMPE352

🔎 Research

🚀 Practice Project

📝 General Meeting Notes

📝 Backend Meeting Notes

📝 Frontend Meeting Notes

📝 Mobile Meeting Notes

🎓 Who We Are

📂 Templates

Clone this wiki locally