Meeting Minutes

Meeting 1 (February 3rd):

• First meeting for the project.
• We decided to work individually on requirements to have more ideas,
• We decided to meet again on Sunday to merge our ideas and complete parts 1 and 2 of the first deliverable.

Meeting 2 (February 7th):

• We merged the requirements and reduced them to the 15 most important ones.
• We split the requirements into different categories and assigned each category to a member.
• We will work on our use cases individually and meet again on February 9th to discuss our work and move on to part 2.

Meeting 3 (February 14th):

• We created the project in GitHub and wrote our To Do, In progress and Done lists.
• We finalized the domain model.
• We shared our use cases and arranged them.
• Divided the use cases for the detailed specifications.

Meeting 4 (February 15th):

• Zoom meeting with two breakout rooms.
• First breakout room finalized the requirements and set them as issues.
• Second breakout room finalized the use case diagrams and wrote the detailed specifications on the wiki.
• We decided to watch tutorial 3 before February 16 at night to start with parts 3-4-5 of the project.

Meeting 5 (February 20th):

• We set up the build system using Gradle and pushed it on GitHub.
• We created the database system with a Heroku app.
• We wrote the key decisions and posted the domain model in the wiki.
• We decided to watch tutorial 4 individually and meet again later in the day to continue with parts 4 and 5 of the deliverable.

Meeting 6 (February 20th):

• We wrote the JPA annotations
• Started to implement the persistence layer.
• Decided to meet tomorrow after watching tutorial 5.

Meeting 7 (February 21th):

• We added the Ids for the Database tables.
• We split the work for testing the persistence layer.

Meeting 8 (February 21th):

• We had difficulties with the JPA annotations. We were having lots of errors.
• Debugged to solve the errors.
• Added some of our testing codes by merging the parts that were done.

Meeting 9 (February 22nd):

• We spent the whole day on a zoom call debugging our errors.
• We had non-ending errors due to the JPA annotations. Every time we used to solve a problem, another one popped.
• With research and debugging, we were able to run our code without any error.
• We divided the tests among us and rewrote them. We then added them to the code one by one by checking if they work.
• We finalized the wiki of the project and made some minor edits to the domain model.
• We submitted and are done with Sprint 1.

-------------------------------------------------------------END OF SPRINT 1------------------------------------------------------------

Meeting 10 (March 1st):

• First meeting for Sprint 2.
• We decided to use the mapping method.
• We divided the features so that each of us works individually on the dto, service and controller methods of the specific features.
• We did a list of questions and posted them on the discussion board.
• We decided to meet at the end of the week.

Meeting 11 (March 11):

• We merged the DTO and service classes.
• Brainstormed and decided what we should include in the controller.
• Made some changes in the model.
• Discussed the tutorial and the plans for the next meeting.

Meeting 12 (March 16):

• We merged the unit testings.
• We planned how to implement the controller methods.
• Tried to understand how to do the integration testing.
• Tested the coverages.

Meeting 13 (March 17)

• We merged the controller methods and started integration testing with POSTMAN.
• We stayed on zoom together to debug and fix the errors each one of us had.

Meeting 14 (March 18)

• We finalized our POSTMAN screenshots and included them in the wiki.
• We merged our code into the main branch.
• We wrote the report and submitted the link to our last commit.

-------------------------------------------------------------END OF SPRINT 2------------------------------------------------------------

Meeting 15 (March 25) - First meeting of Sprint 3

Goals of this meeting

• Discuss what to do for deliverable 3 and plan appropriately
• Designate tasks to different members of the group

Meeting conclusion

• Meet again tomorrow to discuss and implement architecture design pattern
• Created a list of pages we have to implement and divided different pages to different members of the group
  • Eric: Login/Account pages
  • Fadi: Business Info (Owner)
  • Robert: Service: Add/Update/Delete (Owner page)
  • Marc: Operating Hours (Assistant page)
  • Mohammad: Review page
  • Tamara: Appointment page

Meeting 16 (March 26)

Goals of this meeting

• Discuss which software architecture model best suits our system
• Design and implement such architecture
• Begin working on Frontend

Meeting conclusion

• Decided to implement a layered architecture design pattern
• Established that every group member should slightly adjust the backend so the code aligns with the layered architecture
• Every group member understands their assigned tasks and should start working on Frontend

Meeting 17 (April 2)

Goals of this meeting

• Discuss whether to use cookies in the authentication process
• Discuss how to implement pop-ups to catch exceptions from the Backend
• Discuss which tabs should be present in the navigation bar of the Web Frontend
• Finalize Web Frontend

Meeting conclusion

• Decided not to use cookies and use local storage in the authentication process
• Decided to import the plugin "npm install --save sweetalert" to display alerts
• Decided to have different tabs in the navigation bar depending on which page the user is on
• Finalized Web Frontend

-------------------------------------------------------------END OF SPRINT 3------------------------------------------------------------

Meeting 18 (April 10) - First meeting of Sprint 4

Goals of this meeting

• Start deliverable and discuss what needs to be done.
• Created a list of pages we have to implement and divided different pages to different members of the group
  • Eric: Account page (Edit Profile, Add Car, Remove Car, View Profile, View Cars)
  • Fadi: Homepage (View Services, View Reviews, View Reminders, View Appointments)
  • Robert: Homepage(View Services, View Reviews, View Reminders, View Appointments
  • Marc: Login page (Password, Username, "Don't have an account?", Signup fields, "Already have an account?")
  • Mohammad: Review page (Write, Edit, Delete, View Review)
  • Tamara: Appointment page (Make appointment, update appointment, cancel appointment, view appointment)

Meeting conclusion.

• Successfully designated different tasks to different team members.
• Decided to stick to the original plan; that is, to make the android frontend deal with customer management only.

Meeting 19 (April 13)

Goals of this meeting

• Oversee and check if everyone is working on the project.
• Discuss any additional concerns regarding the deliverable.

Meeting conclusion.

• Everyone is on track and working on their designated tasks.
• Decided to have one home page and each feature corresponding to the customer management has its own page.

Meeting 20 (April 16)

Goals of this meeting

• Finalize everything.
• Check if everything is working correctly.

Meeting conclusion

• Decided to use the "sweetalert" import to display alerts and pop-ups when the customer is using the android frontend.
• Checked and ran tests over everything to ensure everything is functioning correctly.
• Finalized everything including android frontend, user documentation, and project report.