Requirements

Glossary

• Sample Word: Sample Text

Functional Requirements

• 1. User Requirements

1.1. Basics
• 1.1.1. Registration

  • 1.1.1.1. Guest users shall register by providing a valid username, e-mail address, and password.
    • 1.1.1.1.1. Valid password shall consist of 8-16 alphanumeric characters.
    • 1.1.1.1.2. Valid usernames and emails shall be unique.
  • 1.1.1.2. After completing step 1.1.1.1, guest users shall validate their e-mail addresses to complete the registration process.
  • 1.1.1.3. Guest users should also be able to join with their Google or Facebook accounts.

• 1.1.2. Login/Logout

  • 1.1.2.1. Registered users shall be able to log in via their registered username/e-mail address and password.
  • 1.1.2.2. Registered users should also be able to login with their provided Google or Facebook accounts.
  • 1.1.2.3. Registered users shall be able to log out after logging in.

• 1.1.3. Account Management

  • 1.1.3.1. Registered users shall be able to reset their passwords.
  • 1.1.3.2. Registered users' accounts shall be deleted if they behave abusively.
  • 1.1.3.3. Registered users should be able to delete their accounts.

• 1.1.4. Profile

  • 1.1.4.1. Registered users shall have a profile page.
  • 1.1.4.2. Registered users shall be able to add profile pictures to their profile pages.
    • 1.1.4.2.1. Profile pictures shall have JPG or PNG extensions.
  • 1.1.4.3. Registered users shall be able to add their personal information to their profiles pages.
  • 1.1.4.4. Registered users shall be able to edit the content of their profile pages.
  • 1.1.4.5. Registered users shall be able to set their profiles as public or private to other users.
    • 1.1.4.5.1. Usernames shall be visible to guests and registered users on both public and private profiles.


1.2. Community
• 1.2.1 Search & Follow

  • 1.2.1.1. Sample Text

• 1.2.2 Interaction

  • 1.2.2.1. Sample Text


1.3. User Interaction
• 1.3.1. Search

  • 1.3.1.1. Sample Text

• 1.3.2. Follow

  • 1.3.2.1. Sample Text

• 1.3.3.Private Messaging

  • 1.3.3.1 Sample Text


1.4. User Roles
• 1.4.1. Guest Users

  • 1.4.1.1. Guest users shall be able to view public user-profiles and community content read-only.
  • 1.4.1.2. Guest user shall be able to use searching functionality.

• 1.4.2. Registered Users

  • 1.4.2.1. Common Users

    • 1.4.2.1.1 Common users shall be able to have all privileges of guest users.
    • 1.4.2.1.1 Common users shall be able to follow public communities directly.
    • 1.4.2.1.1 Common users shall be able to send a request to join private communities.

  • 1.4.2.2. Community Members

    • 1.4.2.2.1 Community members shall be able to post content with or without tag(s) in the community.
    • 1.4.2.2.2 Community members shall be able to post content with or without tag(s) in the community.
    • 1.4.2.2.3 Community members shall be able to comment on posts.
    • 1.4.2.2.4 Community members shall be able to replay comments
    • 1.4.2.2.5 Community members shall be able to like posts and also comments.
    • 1.4.2.2.6 Community members shall be able to search posts according to their content, tag, title.
    • 1.4.2.2.7 Community members shall be able to turn on notifications for the community.
    • 1.4.2.2.8 Community members shall be able to turn on notifications for a specific one or more posts in the community

  • 1.4.2.3. Community Moderators

    • 1.4.2.3.1. Community moderators shall be able to have all privileges of basic community members.
    • 1.4.2.3.2. Community Moderators shall be able to review reports.
    • 1.4.2.3.3. Community moderators shall be able to remove posts, comments, users from the her-him community.
    • 1.4.2.3.4. Community moderators shall be able to organize events.
    • 1.4.2.3.5. Community moderators shall be able to open discussions.

  • 1.4.2.4. Community Creators

    • 1.4.2.4.1. Community creators shall be able to have all privileges of community moderator.
    • 1.4.2.4.2. Community creators shall be able to assign a new moderator or remove existing moderators from the him-her community.
    • 1.4.2.4.3. Community creators shall be able to change community between public & private.
    • 1.4.2.4.4. Community creators shall be able to close him-her community.

• 1.4.3 Admin Users

  • 1.4.3.1. Admin shall be able to have all privilidges of community creators.
  • 1.4.3.2. Admin shall be able to delete communities and also delete/block users

• 2. System Requirements

2.1. Recommendation
• 2.1.1. The system shall recommend communities and posts to users based on the communities they follow and the posts they like.
• 2.1.2. The system shall provide trending posts and communities to users.
• 2.1.3. The system shall recommend the posts of followed users.
• 2.1.4. The system shall recommend the communities of followed users.


2.2. Notification
• 2.2.1. The system shall notify users when they get private messages.
• 2.2.2. The system shall notify users when their posts get a like/dislike.
• 2.2.3. The system shall notify users when someone comments on their posts.
• 2.2.4. The system shall notify community admins when a user requests to enter their private communities.


2.3. Community
• 2.3.1. The system shall disable users if they try to perform unauthorized actions.
• 2.3.2. The system shall allow community members to organize an event.
• 2.3.3. The system shall warn community admins if a post gets a predefined amount of reports.
• 2.3.4. The system shall allow community admins to pin a post.
• 2.3.5. The system shall highlight the posts in a community based on their popularity.


2.4. Searching/Filtering
• 2.4.1. The system shall have a semantic search mechanism.
• 2.4.2. The system shall allow users to filter other users by:
  • 2.4.2.1. Number of followers
  • 2.4.2.2. Their locations
  • 2.4.2.3. Followed communities
• 2.4.3. The system shall allow users to filter communities by:
  • 2.4.3.1. Number of followers
  • 2.4.3.2. Number of posts
  • 2.4.3.3. Popularity
  • 2.4.3.4. Tags
• 2.4.4. The system shall allow users to filter posts by:
  • 2.4.4.1. Number of likes
  • 2.4.4.2. Number of comments
  • 2.4.4.3. Date
• 2.4.5. The system shall allow users to filter comments by:
  • 2.4.5.1. Number of likes
  • 2.4.5.2. Date

Non-Functional Requirements

3.1. Security
• 3.1.1. User names and e-mails for registrations shall be valid and unique for each user.
• 3.1.2. Passwords shall be 8-16 characters long and must not contain special characters.
• 3.1.3. Passwords shall be encrypted with SHA-256 before being stored in database.
• 3.1.4. Database system shall be protected against cyber-attacks.
• 3.1.5. In the case of a log in attempt from a different device, a verification code should be sent to the e-mail address of the account owner.
• 3.1.6. In the case of a password change attempt, a verification code should be sent to the e-mail address of the account owner.


3.2. Privacy
• 3.2.1. System shall obey the rules defined by GPDR and KVKK.
• 3.2.2. System should provide the mechanisms to preserve the uniqueness of Copyright contents.
• 3.2.3. Users must agree to Privacy Policy and User Agreement before registration.


3.3. Performance and Reliability
• 3.3.1. Respond times shall not exceed 3 seconds.
• 3.3.2. If an error occurs, the problem should be fixed within an hour.
• 3.3.3. Downtime occurance shall not be more than once in a month.
• 3.3.4. The platform shall support up to 10000 simultaneous users. This number should be scalable when necessary.


3.4. Accessibility and Availability
• 3.4.1. System shall be accessed via Android based mobile application.
• 3.4.2. System shall be accessed via web application which is supported by modern web browsers such as Chrome, Firefox, Opera and Safari.
• 3.4.3. Platform should support English language.
• 3.4.4. Platform should support all ASCII symbols and Turkish symbols.


3.5. Standards
• 3.5.1. The implementation should obey the guidelines of W3C Activity Stream Standard 2.0.
• 3.5.2. The semantic taggings should be supported with Wikidata.