Employer Viewpoint Architecture

Description Attached above is an encapsulated and simplified architecture for the Employer viewpoint of the My-CoOp System. The architecture is divided into 4 main components.

Frontend We are developing a web frontend and an Android frontend with limited functionality. The web frontend starts with a login page where the employer has to enter credentials sent to them by the administrator. There's also an option for them to request different credentials if they forget the existing one. After logging in, the employer is redirected to the homepage where they can access different modules to perform the different operations pertaining to the client requirements for the Employer Viewpoint (Please refer to the Requirements document for details) The android frontend starts in a similar manner as the web frontend. Once the employer is logged in, they can only perform a few select tasks from their phones. They can send/receive messages, search for students completing their co-ops, and view notifications and event invites. If an employer wishes to perform more complex tasks they will need to access the web frontend.

Backend The backend section of the architecture highlights the key services we have implemented for our System. Every time an employer interacts with the system, RESTful service calls call the appropriate services necessary to execute the command in the backend. There are additional service calls that have intentionally been left out from the diagram, because they are only used to execute minor functionalities.

External Services For some of our services we need to make RESTful API calls to other viewpoints. For example, to receive notifications we need to call Group 17's methods.

Persistence Whenever we perform a service call that includes a CRUD operation in our backend, we modify data in the persistence layer. We also use the persistence layer to handle queries.