Skip to content

UML Diagram for Deliverable 1

Jump to bottom
Ege Odaci edited this page Feb 12, 2019 · 2 revisions

Uml diagram

Assumptions:

  • We assumed that we have one tax credit form and one coop placement form for a single coop.
  • We assumed that employer is going to be notified once they accepted the invitation of the event.
  • We assumed that event can exist even if no employer is invited or attending.
  • StartConfirmation class and EvaluationForm class is supposed to be an association class, but UML lab doesn't support association classes.
  • This diagram supports same instance of StartConfirmation class and CoopPosition class to be associated with different instances of Employer class. This shouldn't be allowed.
  • This diagram supports same instance of EvaluationForm class and CoopPosition class to be associated with different instances of Employer class. This shouldn't be allowed.

How to run Frontend?

  • Once we push to git, the frontend will be automatically depoloyed using Travis

Frontend link: https://coop-frontend-g8.herokuapp.com/

How deploy run Backend?

  • Once we push to git, the backend will be automatically depoloyed using Travis

Trying functionalities:

*Creating Student in Backend:

Clone this wiki locally