Meeting Minutes

Meeting Minutes 1

The goal of this page is to record the meeting contents for all sprints/deliverables. Details are below:

Sprint 1/Deliverable 1

Saturday February 6th 2021 - General Kickoff

• Creating a Google drive and doc for Minutes (Victoria)
• JDK 11 had some issue
• JDK 1.8 for the project -> consistent with all the members
• Finding meeting time (weekly) - Saturdays at 3pm
• Using the same tools as tutorials and instructors
• Domain model -> lucid chart (drawing charts)
• Helpful also for use case diagrams...
• Next week, Saturday go over the first three parts of Deliverable 1

40min - Attendants: All

---

Sunday February 14th 2021 - Sprint_1 Domain Modelling and Use Case Diagram

• Discussion on the Top 15 Requirements
  • In case of emergency or occasional schedule cancel, the system has an “on-call” technician to cover each day
  • Customer point of view: choose category-->choose available time slot-->wait for notification.
  • Algorithm for distributing fairly the jobs throughout the day/week
• Worked on the use case diagrams
• Questions for the TA:
  • Can we group use cases together in the diagrams (i.e. add, update and delete services…)
  • How descriptive do our “use cases” need to be
  • Use case for sending notifications when an appointment is scheduled? (use case for sending and receiving?)
  • Can we structure the diagram with “use cases” to the right

TODO

• 5 most important use cases
  • Book an appointment (Jiatong)
  • Make schedule (Victoria)
  • Edit appointments (Zichen)
  • Send notification (Mat)
  • Create profile (Jack)
• Edit/comment on the domain model (everyone) (before Tuesday)
• Initialize repo and register requirements to issues (Zichen)

2hr - Attendants: All

---

Tuesday February 16 2021 @3pm - Sprint_1 Domain Modelling and Use Case Diagram

• Went over domain model, still needs work
• Discussed many important aspects of the model
• Might need to visit the professor during his Thursday office hours + TA during friday’s

TODO

• Still 5 most important use cases

2hr - Attendants: Yi Wei/Victoria/Mathieu/Jiatong

---

Wednesday February 17 2021 @8pm

PLANNED

• Go over 5 most important Use Case flows
• Domain Model MAYBE
• Part 3
• Part 4
• Part 5 of Sprint 1 (setup Travis CI,...)
• Separate work for part 6

Design Decisions:

• Unique ID of creating Profile(account):
  If user is using the website, they can register using e-mail/phone number

2hr - Attendants: Yi Wei/Victoria/Mathieu/Zichen

---

Friday February 19 2021 @9am - Sprint_1 JPA Annotations for Persistence Layer

PLANNED

• Go to OH
• Go over the domain model again

Design Decisions:

• New class WeeklyAvailabilities for each technicians

• Resolve the loop problem within Appointment-Resource-Service

• TODO (JPA Notations)

  • Zichen

    AutoRepairShop/CompanyProfile/TimeSlot

  • Jiatong

    Resource/Service/Technician

  • Victoria

    Vehicle/Invoice/Appointment

  • Jack

    DailyAvailability/Customer/Admin

  • Mat

    Profile/Employee

1hr - Attendants: All

---

Weekend February 20-21 2021 @3pm

PLANNED

• Go over unit testing
• Overall bug testing and fixing performed
• Completing the loose ends of the deliverable for Sprint_1

20hr - Attendants: All

---

Sprint 2/Deliverable 2

---

Saturday March 6 2021 @3pm

Planned

• Recap on the feedback of Sprint1
• Start off on the Sprint2

Questions:

1. Should we separate the test code into several individual classes?
2. Appointment-Technician association, confirm that our design is good based on the feedback?
3. Resources class: add explanation in wiki.
4. Send reminder/send notification, should we change the detailed requirements? What was the intended change?
5. Does the difference in name that IsotopeCR and root class autoRepairShop cause problems?

1hr - Attendants: All

---

Sprint 3/Deliverable 3

Sprint 4/Deliverable 4

Sprint 5/Deliverable 5