This repository has been archived by the owner on Dec 30, 2021. It is now read-only.
Architecture
The overall architecture is shown below. In short, the client sends a request to the route that passes the necessary parameters to the controller. The controller then calls the service layer to perform any necessary operations before calling the the repository layer to retrieve or update data from the database.
- View, pin and review Services
- View, save Jobs
- View, save Events
- Access the Chatbot that helps navigate the application
- Forum to ask questions
- Report Bugs
- Login using email+password, Facebook or Google login
- Answer questions to improve the data we have on the user
- View, create Services
- View, create Jobs
- View, create Events
- Access the Chatbot that helps navigate the application
- Forum to ask Questions
- Report Bugs
- Login using email+password
- Manage (Delete) Services
- Manage (Delete) Jobs
- Manage (Delete) Events
- Access the Chatbot that helps navigate the application
- Forum to ask Questions
- Manage (Change Status) Bugs
- Login using email+password
The application consists of two components: the client and the server. The user accesses the client, where the requests are then sent to the server to retrieve/update data.
The below two diagrams are the overall class diagrams of the client and server components of the application. The main classes can be seen in the diagrams
