Skip to content

joycemap/Appt-Tracker

Repository files navigation

Appt-Tracker

Appointment Tracker https://pacific-shore-10633.herokuapp.com/ This Tracker is designed for use by senior citizens to keep track of the various medical appointments they may have. Care was taken to ensure that the colors used are in high constrast font size and buttons are large enough for senior citizens to see and click on, and a special font design to ensure accessibility was used throughout the application.

The functions of the appointment tracker allows registered users to add appointments, view all appointments, edit existing appointments and delete appointments.

The technologies used in this application are: Javascript React Express Bootstrap Customized CSS

To use this application, users must have an internet connection. No other installations are needed.

The approach taken is to:

  1. Identify a user group with a problem.

  2. Form a hypothesis of the problem.

  3. Test the hypothesis.

  4. Formulate a solution to address the problem.

  5. Formulate a plan to execute the solution. The Pre-execution materials are: a. a user problem definition, user stories and solution proposal: https://github.com/joycemap/Appt-Tracker/blob/master/WIREFRAME_PROJECT_2.pdf b. flowchart of the user path: https://github.com/joycemap/Appt-Tracker/blob/master/Appointment_Flowchart.pdf c. an Entity Relationship Diagram (ERD) of the tables in the database: https://github.com/joycemap/Appt-Tracker/blob/master/ApptTrackerDatabaseERDiagramCrowSFoot.pdf d. Wireframe: https://github.com/joycemap/Appt-Tracker/blob/master/Wireframe_Pg_1.JPG and https://github.com/joycemap/Appt-Tracker/blob/master/Wireframe_Pg_2JPG.JPG

  6. While executing the plan, I maintained a "must-do" list, a bug tracking list and a "nice to have" features list. I made sure to clear all items on the first two list to get an MVP and moved on to implement some items on the "nice to have" list.

  7. The MVP was then tested during soft launch to get feedback from the instructional team. Further comments from classmates on color were incorporated.

  8. For User Acceptance Testing, I did an automated test and an actual user test. a. Automated testing: I ran the website through the following accessibility checkers. Based on the feedback, I included labels on my JSX files to ensure that screen readers can read it, and http://juicystudio.com/services/luminositycontrastratio.php#specify https://tenon.io/test-now-results?type=url-result

b. I sought feedback from an actual senior citizen with low vision and made changes to the background color to increase the constrast and font sizes, so that the target user group will be able to use it.

Unsolved problems: Yet to implement solution to prevent appointment conflicts, and hide past appointments.