Project Report (Sprint 1)

Effort Table

Team Member	Roles / Tasks	Time Spent (Hours)
Annabelle Dion	Requirements Model, Domain Mode, Persistence Layer & Testing Persistence Layer	10
Sia Ham	Requirements Model, Domain Model, Build System & Persistence Layer	13
Thomas Jarvis	Requirements Model, Domain Model, Build System, Persistence Layer & Bug fixing	10
Norman Kong	Requirements Model, Domain Model, Documentation, Build System & Testing Persistence Layer	10
Catherine Van Gheluwe	Requirements Model, Domain Model, Documentation, Build System, Persistence Layer & Bug fixing	17

Documentation

1. Requirement Model
2. Domain Model Iterations

Meeting Minutes

Meeting 1 : Tuesday, February 9th

• Agenda

  • Sprint Planning (schedule next meeting)
  • Task Division

• Attendance

  • Everyone was present

• Decisions Made

  1. Sprint Planning

     • Meeting 2: Monday, February 15th @7:30PM
     • Divide the team in a group of 3 & group of 2. Each team writes the 15 requirements and domain model and present it on Sunday's meeting. Merge the work to have a final requirement and UML class diagram.
     • Have final changes made to models, present persistence layer and testing layer.
     • Work & review the documentation on Github
     • Update welcome page, README files

  2. Task Division

     • Documentation will be a rotational task. One person will be assigned documentation on top of their coding task for each sprint.
     • Persistence, Testing Suite , Building System will be divided amongst the five of us once the requirement model is completed

note that these tasks are not set in stone

Team Member	Roles / Tasks
Annabelle Dion	Testing
Sia Ham	Database design
Thomas Jarvis	Build System
Norman Kong	Testing
Catherine Van Gheluwe	Database design

Meeting 2: Monday, February 15th 2021

• Agenda:

  • Compare the requirements models and domain models of both sub teams (team1: Norman, Thomas; team2: Catherine, Sia, Annabelle) and reach consensus for initial versions of the models.
  • Plan tasks

• Attendance

  • Everyone was present

• Decisions Made

  1. Requirements Model:
     • Notable design decisions:
       • Decided that customers can choose to filter available appointments by technician, time and/or services.
       • Decided that technicians will alert the administrator if they must cancel an appointment.
       • Database size estimate: 0.5MB per image, 1 image per appointment, 7 appointments per day, 1 week per appointment = 24.5 MB, x2 in anticipation of peak service, + 10MB for text = 60MB.
  2. We discussed and edited the requirements model, use case diagram and class diagrams.
     • Todo:
       • Norman and Thomas: Clean up and finalize class diagram, then add to documentation and repo (see Issues).
       • Annabelle, Sia and Catherine: Clean up and finalize and finalize requirements model and use case diagram, then add to documentation and repo (see Issues).
  3. Last tasks for deliverable 1:
  • Thomas will work on the Build System and Continuous Integration on Feb 15. He will then help with other tasks that need help. Catherine and Sia will finish the Persistence Layer as soon as possible.
  • Norman and Annabelle will read into the Testing of Persistence Layer and then apply it once Catherine and Sia finish their task.

Meeting 3: Saturday, February 20th 2021

• Agenda:

  • Update on everyone's progress
  • Schedule last meeting

• Update:

  • Catherine, Thomas and Sia did the Gradle Build Project, worked on the Persistence Layer and Umple code. There are still some errors to be corrected.
  • Annabelle got the SpringBoot, the CRUD repo and Unit Tests set up, the test do not run yet. Error might be due to the Entity Manager. Working on the UnitTesting Branch
  • Norman worked on documentation and Umple code.

• Schedule next meeting:

  • Monday, February 22nd 6:00 PM

• Attendance

  • Everyone was present

Meeting 4: Monday, February 22nd 2021

• Agenda:

  • Review the elements of deliverable 1.

• Attendance

  • Everyone was present