Requirements

Glossary

• Sample Word: Sample Text

Functional Requirements

• 1. User Requirements

1.1. Basics
• 1.1.1. Sign Up

  • 1.1.1.1. Sample Text

• 1.1.2. Login

  • 1.1.2.1. Sample Text

• 1.1.3. Profile

  • 1.1.3.1 Sample Text


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. Sample Text

• 1.4.2. Registered Users

  • 1.4.2.1. Common Users

    • 1.4.2.1.1 Sample Text

  • 1.4.2.2. Community Members

    • 1.4.2.2.1 Sample Text

  • 1.4.2.3. Community Moderators

    • 1.4.2.3.1. Sample Text

  • 1.4.2.4. Community Creators

    • 1.4.2.4.1. Sample Text

• 1.4.3 Admin Users

  • 1.4.3.1. Sample Text

• 2. System Requirements

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.