cryafonic / doctors_r_us

Project Name: Doctor R us

Project Doctor R us is a Appointment system that involves the prevention of spending covid and assisting those in need o an medical appointment. It will feature seamless UI/UX content and contain all the logic needed for admin/user privileges as well as a Appointment system functionality.

Site

**Deployed to Heroku here https://https://doctors-r-us.herokuapp.com/ NB. DO NOT CLICK SITE. DOWN FOR MAINTENANCE. TRYING TO FIX HEROKU DEPLOYMENT ISSUES. PLEASE OPEN UP A LOCAL VERSION ON YOUR PC TO SEE THE APPLICATION.

Installation

• Fork a copy or

• Clone a copy using git. git clone https://github.com/Cryafonic/Doctors_R_us.git

  • Example in terminal type https://github.com/Cryafonic/Doctors_R_us.git
  • Rename the local repository's current 'origin' to 'upstream'. "git remote rename origin upstream"
  • Give the local repository an 'origin' that points to your repository. "git remote add origin https://github.com/your-account/your-repository.git"
  • Push the local repository to your repository on github. "git push origin master"

• Alternatively under 'Code' click 'Download as Zip'

• Alternatively click [here]https://github.com/Iceteatree/Timeless/archive/refs/heads/main.zip

Usage

• cd into main Doctor R us folder.
• Make sure you have latest NPM components installed by typing npm install in terminal
• To run type npm start in terminal.
• Open another terminal
• cd into Doctors R us client folder.
• Make sure you have latest NPM components installed by typing npm install in terminal
• To run type npm start in terminal.

If you are an end-user

• Simply click this link to open the website.

If you want to play with the admin functions use these login details:

email: [email protected]
password: Password1

If you would like to play with the code

• Open any of the files you would like to edit in the code editor of your choice. Example. Visual Studio Code.

Testing

• If you would like to run the test modules do the following:

  • cd into the main folder

  • Type npm test into the console to run server tests.

  • cd into client folder

  • Type npm test into console to run client-side tests.

Third party API's?

There no 3rd party API's being used in this project.

Software requirements documentation

This document will be split into two main sections.

1. System Architecture
2. System Requirements Specification

System Architecture

Stack Choice

Those chosen web stack that we will be using to design this web application is the MERN stack.

Motivation

The reason why I've chosen to use the MERN stack is that it is an unopinionated stack that allows total freedom in how the developer gets to work to get to the final product. I am really excited to use React and in particular Create-React-App for the frontend because I can see the benefits it provides . I'm the most comfortable with it so far, therefore I am able to push my own abilities farther than they already are. I am using Express and Node js to power the backend and am connecting that to a Mongo database. With these in place I can reliably assume that my application will always have 100% run time and can easily scale in the future if I need it to.

Deployment

The site will be deployed to Heroku. They not only have multiple servers around the world ensuring reliability but also all the server side logic can be handled by them allowing me the developer to concentrate more on the controller logic.

Styling

We will be making use of Bootstrap and standard CSS for the styling. Bootstrap not only allows use to save time by having beautiful default components but also allows all those components to be responsive as well. This makes the transition between mobile and larger screens a breeze.

System Requirements Specification

What is the function of the app?

This app will be a mutli page , multi-role application that make it earsier for doctor and patient to create appiontments. The patient (end-user) will login and see all of the previously created appointments.Where they will be able to edit old and or create new appointments. There is also a doctor and admin login. Where they can insert a diagnosis, schedule a date or as a admin edit and delete the appointment aswell. It will have a registration and login page functionality. If not logged in the user will not be able to navigate to any route except the login and registation page. Authentication will be directly linked to the ability to create appointment. We will have basic tracking of appointment functionality between patient, doctor and admin. There will be no loading into other pages. We use re-rendering to show the different routed paths. Users will be able to use CRUD functions by posting, editing and deleting appointments.

Functional and Non-Functional Requirements

Functional Requirements

• The web application shall create new users within a database that will contain that users information.
• The web application shall maintain and store user and appointment data.
• The web application shall have a dedicated admin page, where the admin in question can edit,delete and add date scheduled appointment information into the database.
• The web application will have a normal login/registration authentication method.
• The web application will allow appointments to be created.

Non-Functional Requirements

• Usability

  • The web application shall have a clean, executive interface.
  • The web application shall have a great user experience.
  • The web application shall be documented.

• Reliability

  • The web application shall have a robust backend that has multiple global servers which can act as nodes/backups in the event of failure.
  • The web application shall be divided into smaller modules and components to ensure that it is easy to create tests.
  • The web application shall be tested by multiple developers to ensure reliability.

• Performance

  • The web application will be responsive and performs as smoothly as possible for the users.
  • The web application will inform the user if there are performance issues. (Loading screen and the like)
  • The web application will have a quick recovery time in the event of a failure.
  • The web application shall have a low resource usage on the end-users side.
  • The web application shall be cost-effective to maintain.

• Security

  • The web application shall use the latest in web encryption technologies to secure user data.
  • The web application shall inform all relevant parties if a data breach has been detected.

Users

The users who would use this application are people who are inneed of medical assistans.

User Stories

1. As an admin, I can create, edit and delete different appointments so that I am able to continually assist patients and doctors with there appointments.
2. As an admin, I want to have access to analytical tools that present easy to understand processed data so that I can improve on my end user experience.(For the future though, definitely not achievable in this project)
3. As an end-user I want to have a seamless user experience so that I can recommend this website to my friends and family.
4. As an end-user I want to know that my data is being kept securely so that I do not have to worry if someone has logged into my account and stolen my personal information.
5. As an end-user I want to be able to see created appointments so that I do not have to waste time scrolling through pages and pages of useless information.
6. As an end user I want to be able to have a variety of payment options, so that I can conveniently use the payment option I'm most comfortable with.

Product Comparison

• My product doesn't have complex menus. Everything is easily accessible and understandable.
• Offers a better cost to product ratio than competitors.
• The appointment system will be a smooth experience.

Credits

Tutorials

• Redux Crash Course with React - Brad Traversy
• Complete React Tutorial(with Redux) - Net Ninja

Bootcamp

• HyperionDev
• If you would like to leave any feedback and suggestions please feel free to contact me.

Brendon van der nest | Copyright 2021 |