Development

docs/agile docs/Living Document.md

@@ -255,9 +255,7 @@ Our system consists of several key software components that interact to provide
 
 ### d) Diagram of StressLess system's architecture.
 
-[https://docs.google.com/presentation/d/1bnXGg1ByNbccVPqFxQus0D66CyCj5prQ6tJ-d1poBzU/edit?usp=sharing](https://docs.google.com/presentation/d/1bnXGg1ByNbccVPqFxQus0D66CyCj5prQ6tJ-d1poBzU/edit?usp=sharing)
-
-![image.png](Living%20Document%200cfda53982fb40e0bb52a6b3a1228e37/image%202.png)
+![StressLess Demo.png](Living%20Document%200cfda53982fb40e0bb52a6b3a1228e37/StressLess_Demo.png)
 
 ### e) Assumptions underpinning our chosen architecture
 
@@ -422,28 +420,27 @@ Find an optimal schedule which gives her enough time to attend her practicals, s
 
 ### **Trigger**
 
-Julie receives her practical and curriculum schedules at the beginning of the semester.
+Julie brainstorms productivity times as well as her start/end times for her workday.
 
 ### **Preconditions**
 
 Julie has set blocks of times in which she knows she has to be at school or at the hospital.
 
 ### **Postconditions**
 
-Julie gets a custom schedule integrating all of her set responsibilities generated, which suggests available time for self-care and friends/family.
+Julie is able to take a survey accounting for her productivity times and work hour preferences.
 
 ### **Flow:**
 
 1. Julie opens the homepage of the app and completes the sign-up process.
-2. Julie takes the survey .
-3. Input major upcoming dates practical shifts and curriculum exams into the calendar (i.e. dates, locations, times)
-4. Calendar becomes populated, including major upcoming dates as well as suggested study blocks, practical shift preparation times, self-care hours, and days for family and friends
+2. Julie takes the survey.
+3. Julie saves her responses.
 
 ### **Alternative Flow:**
 
-1. Julie’s professor has an unexpected family emergency mid-semester, and thus, her curriculum schedule changes.
-2. Julie clicks the “Retake Survey” button in the profile page.
-3. She can update the old dates according to the new schedule, and the app will adjust to these changes by customizing her schedule again and developing new suggested times for other activities such as studying and hanging out with family and friends.
+1. While filling out the survey, Julie realizes she had input the wrong productivity times in her response.
+2. She drags the slider to edit her productivity times.
+3. Then, her changes are saved after she saves her responses.
 
 ## Use Case 4
 

docs/agile docs/Sprint 4/SprintReview4.md

@@ -0,0 +1,46 @@
+# Sprint Review 4
+
+During this sprint, we updated the frontend by adding a user help guide, adding a sidebar to be able to navigate from the calendar page to the user route page, and users can now edit their display name on their user profile. We also edited questions in the frontend, so they are more consistent with the rest of the questions like instead of half of them being in military time and the other half of the questions being in an AM/PM format, they are now all in an AM/PM format. We also added a log out button as well that reroutes to the landing page. We also fetched the user preferences from the backend to be able to display the user’s preferences in the front end and users can now edit their display name as well. 
+
+In the backend, we added routes and controllers for navigating deadlines. We also set up testing API base and configured CI and wrote tests for the user and calendar routes and how the backend helps update the database. We also protected the routes, so users can’t access their information unless they’re logged in. We also implemented the logic for a log out button as well. In the backend, they added a put preference controller as well. 
+
+## Sprint Review Questions
+
+- How has your product improved or progressed from a customer perspective?
+    - We Implemented some changes to allow our product to be more easier for users to navigate. We added a help button with detailed instructions for how to use each page and navigate our app. Also we altered the initial preferences questions to allow for a more intuitive experience. We changed the preference questions to specify what type of unit user response should be(minute/hours), and converted the time display to AM/PM format. User’s are able to stay logged in without being prompted to sign in. We added a navigation bar that allows users to route between calendar and profile page, and added a log out button that routes users back to landing page. Calendar is visible in night mode as well.
+- Describe in terms of high-level features that a non-technical user could recognize and appreciate.
+    - Protected routings that users can’t access unless logged in
+    - Accessible routing transition between calendar and profile page
+    - Logout button terminates user’s authentication requiring them to re-authenticate to access account again
+- What progress have you made that is not visible to a common user?
+    - We started working on storing calendar events to the backend
+    - Created testing to see how well the backend communicates with the database
+    - We started working on displaying instructions in the help page that pertains to the current page
+
+## Customer-visible Progress
+
+- Implemented a User Help Button and Guide
+    - The user can now hover over the help button to see the user help guide that helps tell users what they should do with the website
+- Adding a sidebar to navigate between the calendar and user profile page
+    - A sidebar now exists on the side, so if the user clicks on the calendar they will go to the calendar page and if the user clicks on the user profile page, they will go to the user profile page
+- Can edit their display name on the user profile
+    - In the profile page, the user can now edit their name in their profile
+- Edited questions on user preferences survey, so time format was more consistent
+    - Before questions had a mix of AM/PM and military time, but now all of the questions have been converted to all have consistent times of AM/PM time
+- Log out button exists
+    - The user is now able to log out and be directed to the home page
+- User’s can now see their preferences entered in frontend
+    - The personal preferences that a user enters is displayed in the user’s profile in the frontend
+
+## Customer-invisible Progress
+
+- Added routes and controllers for managing deadlines
+    - Created controllers and routes in the backend for deadlines similar to the ones that already exist for user authentication, user routes, and user deadlines
+- Set up testing API base and configured CI
+    - Set up testing environment to run tests for backend
+- Wrote tests for the user and calendar routes
+    - Wrote tests for the user and calendar routes to ensure that the code works for all types of cases
+- Protected the routes
+    - A user can only access their information when they’re logged in and not if they’re logged out
+- Implemented put preference controller
+    - Allows the user to update their preferences