• R1 - Description of website
• R2 - Dataflow Diagram
• R3 - Application Architecture Diagram
• R4 - User Stories
• R5 - Wireframes
• R6 - Project Managment

The primary purpose of this web application is to streamline and standardise the note-taking process for support workers during their one-on-one sessions with clients. This addresses the problem of inconsistent and often inadequate note-taking practices which result in incomplete client profiles. Such gaps in documentation can affect the quality of client care and add undue workload to team leaders. By ensuring that each interaction with a client is consistently documented in a structured manner, the application aims to enhance the quality of client care, reduce oversight errors, and alleviate the burden on team leaders.

Client Profiles: These profiles contain information about each client, including their care plan, personal details, who their care leader is. Each profile will have an option to view a full history of previous progress notes for that Client. Structured Note Entry: This feature leads support workers through a structured form when they document a shift after it has completed. This ensures progress note standards for increased readability and better outcomes for Clients. Dashboard: When a user is logged in, they have a dashboard where they can select to see upcoming shifts, see if they are missing any notes and a history of their previous notes. Workers can also see a list of the Clients they work with. User Authentication: Login function to ensure users can only see details they are allowed to. This would also allow for admins to be authenticated so they are able to create Client and Worker profiles. Would include other admin tools like removing users as well. Database Tables: Will have separate tables for Clients, Workers, Progress Notes and Rosters to manage the data efficiently. Data Encryption: In an effort to maintain confidentiality and ensure privacy of client interactions, all notes and client profiles will be encrypted.

Organisations or Businesses would use this software as their way to support their employees in tracking their shifts, clients and note taking. Support Leaders and Administrators would use this software to add new clients and workers, manage their pairings and track progress notes. Support Workers: This would be the largest section of users who would interact with the system regularly. Used to look up Client information, shift information and submitting their progress notes.

Frontend: React will be used to create an interactive and responsive frontend. Backend: Node.js and Express.js. Node will allow the application to execute Javascript on the server side and express will be used to create the applications API. Database: MongoDB - NoSQL database that will store data in a JSON format. Authentication: JWT will be used for user authentication. Encryption: The application will use bcrypt for hashing passwords and encrypting the data that needs to be hashed for privacy reasons.

• User : As a support worker, I want to log in to the application so that I can access and input client notes efficiently.

  Acceptance Criteria : There should be a secure login page with appropriate authentication measures. Upon successful login, the support worker should be directed to their dashboard.

• User : As a support worker, I want to select a client from my list and enter structured notes for them.

  Acceptance Criteria : On the dashboard, there should be a clear list of clients assigned to the support worker. I can select a client from the list and be directed to a note entry form. The note entry form should have fields for essential details such as date, client's mood, challenges faced, interventions used, and future recommendations. The form should guide me through filling out the essential details.

• User :As a support worker, I want to receive reminders to complete client notes before ending my shift.

  Acceptance Criteria : The application should send notifications or reminders to the support worker as their shift is about to end. Reminders should encourage timely and consistent note-taking.

• User :As a support worker, I want to view a chronological list of all notes for a specific client.

  Acceptance Criteria : When I select a client, I should be able to see a history of all the notes I've entered for that client in a chronological order. Each note should display key details at a glance to facilitate quick understanding.

• User : As a support worker, I want to easily edit or update previously entered notes.

  Acceptance Criteria : In the client's note history, I should have the option to edit or update any previously entered notes. Changes should be logged with a timestamp to maintain transparency and accountability.

• User : As a team leader, I want a unified view of all client notes entered by my team for effective oversight.

  Acceptance Criteria : Team leaders should have a separate dashboard that provides an overview of all client notes entered by their team. The overview should include filters to sort and search for specific clients or notes.

• User : As a team leader, I want to identify inconsistencies or missing information in client notes to ensure comprehensive documentation.

  Acceptance Criteria : The application should have a feature that analyses notes and highlights potential inconsistencies or missing details. This analysis should help team leaders guide support workers to improve their note-taking practices.

• User :As a team leader, I want to export client notes for reporting and analysis purposes.

  Acceptance Criteria : There should be an option to export client notes, either individually or in bulk, in a downloadable format such as PDF or CSV.

• User :As a support worker, I want to easily clock in and out of my shifts to accurately track my working hours.

  Acceptance Criteria : There should be a dedicated interface to clock in and out. Clocking in and out should record the timestamp of the action.

• User :As a support worker, I want to receive reminders for scheduled breaks during my shift.

  Acceptance Criteria : The application should send timely notifications reminding me to take scheduled breaks. The reminders should include details about the recommended break duration.

• User : As a support worker, I want a clear overview of my shifts for the week, including start and end times.

  Acceptance Criteria : There should be a weekly calendar view that displays all scheduled shifts for the support worker. Each shift should show the start and end times to help with planning.

• User : As a team leader, I want to view and track the clocking compliance of my team members.

  Acceptance Criteria : The team leader's dashboard should provide a visual representation of each team member's clocking in and out status. Compliance status should be easily distinguishable (e.g., green for on time, red for late).

• User : As a support worker, I want to receive notifications about upcoming shifts, including start times.

  Acceptance Criteria : The application should send reminders or notifications to support workers in advance of their upcoming shift Reminders should include the shift start time and any relevant information

• User : As a manager I would like to be able to assign a shift to a worker so that they can work with that Client

  Acceptance Criteria : There needs to be a way for managers to be able to see the list of workers, and clients and assign them to each other. So that workers are able to see the details about Clients they are working with.

• User :As a support worker I want to be led through the note taking process so that I do not need to remember the structure or worry about missing information.

  Acceptance Criteria : Workers when entering progress notes should be led through the process. After choosing a shift they wish to enter notes for, they need to be presented with different text boxes to enter different information. These should not be able to be left blank, and hints should be provided to ensure that the workers knows what information needs to be entered.

Desktop and Mobile

Desktop and Mobile

1. Everyone has now has tasks which they are working on. R1, R2 and R5.
2. None yet
3. Complete R1, R2 and R5 and complete project management board with smaller tasks for each criteria
4. Managing different schedules can make planning/communication harder at times

1. Have added R1, R2, R4, R6.
2. Still working on the scope of what our application does but not an issue, just something to think about.
3. Finish Part A
4. Learnt about how easy it is for scope to get away too quickly.

1. All requirments have been added and are ready to submit for assessment.
2. Virtual communication can be difficult at times.
3. Next step is to plan who will be working on which part of the code. Planning deadlines and how we want to tackle it.
4. Learnt that its important to have backups of things incase things fail or dont update correctly.