Requirements

Required: 📖, Desired: 💼, Aspirational 📈

General Requirements

1. The application will be deployed to Digital Ocean. 📖
   1.1 The application will utilize Fly.io's automated Postgre database management system. 💼
2. The application will integrate LinkedIn into its capabilities, with ideally LinkedIn profile information embedding and profile sharing. 💼
3. All data/records will be kept in the PostgreSQL database. 📖

Account Creation/Log-In

4. Users shall be able to create an account. 📖
   4.1 Users will provide their email, phone number, username, password when creating an account. 📖
   4.2 Users can also provide their employee ID and department ID if applicable. 📖
         4.2.1 Depending on employee ID/job position, users can gain special permissions/restrictions in regards to discussion and performance capabilities. 💼
   4.3 User can upload a profile picture. 💼
   See Sign-In Screen
5. Users shall be able to log-in. 📖
   5.1 Users will provide their username and password when logging in. 📖
   See Log-In Screen
6. Users shall be able to sign out of their accounts. 📖
   See Sign-out Screen
7. Account information will be stored in the application's PostgreSQL database. 📖

Password Reset

8. Users shall be able to change their password. 💼
   8.1 Users will supply account information to the application. 💼
   8.2 The application will then verify the user's account information and identity through a security question. 💼
   8.3 Users will then be prompted to change their password. 💼
   See Forget Password Screen 1
   See Forget Password Screen 2

User Profile

9. Users shall be able to access their user profile. 📖
10. Users shall be able to edit the aspects of their User Profile, including the name, job title, supervising manager, office location, department, email address, and phone number. 📖
    10.1 Users shall be able to change their profile picture. 💼
11. Users shall be able to schedule a meeting with another user when on their profile 💼
12. Users shall be able to message another user when on their profile page. 💼
    See User Profile Screen

Navigation Bar/Side Menu

13. The user shall be able to navigate the application through the navigation bar. 📖
    13.1 The navigation bar will be accessible on each screen of the application. 📖
    13.2 Users shall be able to access the calendar, messages, user profile, and the side menu from the navigation bar. 📖
14. The user shall be able to navigate the application through the side menu. 📖
    14.1 The side menu will be accessible on each screen of the application. 📖
    14.2 Users shall be able to access the calendar, messages, tasks, performance, setting and sign out functionality from the side menu. 📖
    See Navigation Bar/Side Menu Screen

Discussions

15. Users shall be able to view discussions that they are a part of. 📖
    See Discussions Screen 1
16. Users shall be able to create discussions. 📖
    See Discussions Screen 2
17. Users shall be able to add or remove people from the discussions. 💼
    17.1 Users are able to remove people only from discussions that the user themselves has created. 💼

Tasks

18. Users shall be able to create projects and assign tasks to them. 📖
    18.1 Users shall be able to create tasks using the titles, due dates, and team members of the tasks. 📖
    18.2 Users shall be able to edit task content. 📖
    18.3 Users shall be able to delete tasks. 📖
    18.4 Users shall be able to mark tasks as complete/not complete. 📖
    18.5 Users shall be able to search for tasks using a search bar. 📖
    See Tasks Screen

Calendar

19. Users shall be able to oversee their events through the calendar. 📖
    See Calendar Screen
    19.1 Users shall be able to view events through the calendar. 📖
    19.2 Users shall be able to create events as a meeting or deadline. 📖
            19.2.1 If creating a meeting, users will specify the meeting description, participants, start time, and end time. 📖
    See Meeting Screen
            19.2.2 If creating a deadline, users will specify the deadline title, description, participants, end time, and importance/urgency. 📖
    See Deadline Screen
    19.3 Users shall be able to cancel events. 📖
    See Cancel Event Screen
    19.4 Users shall be able to theme their meetings by color. 📈
    19.5 Users shall be able to set a theme/color for specific event scenarios. 📈

Settings

18. Users shall be able to access the settings. 📖
    See Settings Screen
19. Users shall be able to change their account settings. 📖
    19.1 Users shall be able to edit their user profile. 📖
    19.2 Users shall be able to change their username. 💼
    19.3 Users shall be able to change their password. 💼
    See Account Settings Screen
20. Users shall be able to change their notification settings. 📖
    20.1 Users shall be able to disable/enable notifications. 📖
    20.2 The User should be able to receive notifications how they have specified. 💼
    20.3 Users shall be able to select the specific topics that they are notified about. 💼
    20.4 Users shall be able to select how they want to be notified. 💼
    20.5 Users shall be able to receive notifications within the web application. 💼
    20.6 Users shall be able to receive notifications outside of the web application. 📈
            20.6.1 Users shall be able to receive notifications via email. 📈
            20.6.2 Users shall be able to receive notifications via SMS. 📈
    See Notification Settings Screen
21. Users shall be able to access the Help and Support information. 📖
    See Help and Support Screen
22. Users shall be able to read the Privacy Policy agreement. 📖
    See Privacy Policy Screen
23. Users shall be able to read the About Us information. 📖
    See About Us Screen
24. Users shall be able to enable/disable a "Dark Mode" appearance setting of the application. 📈
    See Appearance Screen

Performance

25. Users shall be able to view information that measures their project team's performance. 💼
    View Performance & Statistics Screen
    25.1 Users shall be able to view the number of tasks completed, the number of tasks completed compared to what is expected, and the percentage of tasks completed on time of a particular team member. 💼
    25.2 Users shall be able to view a line chart that plots the expected number of tasks completed over time and the actual number. 💼
    See Performance Screen
    25.3 Users shall be able to view the overall percentage of tasks completed and meetings attended by team members. 💼
    25.4 Users shall be able to view the number of completed tasks, uncompleted tasks, tasks completed on time, tasks completed late, meetings attended, and meetings missed of a particular team member. 💼
    See Attendance Screen
    See Employee Attendance Overview Screen