MercerFrey
commented
1 year ago Backend: 1.1.1.1.1 Users shall provide their first name and last name. 1.1.1.1.2 Users shall provide a username and e-mail address that are unique in the system. 1.1.1.1.3 Users shall be prevented from registration if they enter a username or email address that is already in use . 1.1.1.1.4 Users shall set a password that is longer than 8 characters and contains at least one upper-case letter, one lower-case letter, and one number. 1.1.1.1.5 Users shall confirm the password by writing the same password again. 1.1.1.1.6 Users shall verify their registration process via email verification. 1.1.1.2.1 Users shall provide their e-mails and passwords for signing in. 1.1.1.2.2 Users shall get a warning message if the provided e-mail or password is wrong. 1.1.1.2.3 Users shall see the home page after signing in successfully. 1.1.1.2.4 Users shall be able to reset their passwords. 1.1.1.3.1 Users shall provide their e-mail accounts for resetting their passwords. 1.1.1.3.2 Users shall be able to select a new password after verifying the code that is sent to their emails. 1.1.2.1.1 Users shall be able to create posts. 1.1.2.1.2 Users shall be able to comment under other users' posts and comments. 1.1.2.1.3 Users shall add a title while creating posts. 1.1.2.1.4 Users shall add body text to their posts and comments. 1.1.2.1.5 Users shall be able to add images to their posts and comments. 1.1.2.1.6 Users shall select categories of their posts from a specified set of categories. 1.1.2.1.7 Users shall be able to share locations in their posts and comments. 1.1.2.1.8 Users shall be able to read a post shared by another user. 1.1.2.1.9 Users shall be able to edit their posts and comments. 1.1.2.1.10 Users shall be able to delete their posts and comments. 1.1.2.1.12 Users shall be able to upvote other users' posts and comments. 1.1.2.1.13 Users shall be able to see all posts.
1.1.2.2.1 Users shall have a profile page. 1.1.2.2.2 Users shall see other users' user type from their profile pages. 1.1.2.2.3 Users shall see other users' avatars from their profile pages. 1.1.2.2.4 Users shall see other users' past comments and post from their profile pages. 1.1.2.2.5 Users shall have their usernames visible on their profile pages. 1.1.2.2.6 Users shall have a label above their avatars that indicates their user type. 1.1.2.2.7 Health professionals shall have a label above their avatars that indicates their user type. 1.1.2.2.8 Health professionals shall have their real names visible on their profile pages. 1.1.2.2.9 Admins shall have a label above their avatars that indicates they are admins. 1.1.2.2.1 Users shall be able to send text messages to each other. .2.5.1. The system shall show the number of upvotes given to a post or comment.
1.2.5.2. The system shall show the number of comments made to a post or comment.
1.2.5.3. The system shall show the category of a post.
1.2.5.5. The system shall delete the whole discussion thread if the main post is deleted.
2.1.1. The system shall always run up to 2000 users. 2.1.2. The system shall be portable for website and application. 2.1.3. The system shall respond to any user no later than 4 seconds.
2.2.1. The system language shall be English. 2.2.2. The system shall be available as a native web application in browsers. 2.2.3. The system shall be available as a native mobile application on Android platforms. 2.5.1 The system shall contain a comprehensive, clear, and accessible privacy policy. 2.5.2. The system shall comply with the Law on the Protection of Personal Data No. 6698 (KVKK). 2.5.3. The system shall comply with GDPR. 2.5.4. Users shall accept the privacy policy suggested when registering.
All groups should deliver the requierements they covered in the milestone2. Then we can split all of the remaining requirements to the teams.