-
Notifications
You must be signed in to change notification settings - Fork 2
Meeting 1.4
Michael Frajman edited this page Feb 10, 2020
·
5 revisions
Meeting was held at the Trottier Building on February 7, 2020 from 11:35pm to 1:25pm
In Attendance
- Michael Frajman
- Karl Koerich
- Shi Tong Li
Items Discussed
- Shi Tong and Karl were able to review the tutorial notes and familiarized themselves with Heroku, SpringBoot and Travis. As such they began implementing these elements during the meeting and managed to link Heroku and Travis to our repository.
- We reviews the first version of our domain model with the TA and made some changes based on concerns stated in Meeting Minutes 1.3.
- Shi Tong also mentioned how he and Jia Wei were able to fix some issues with the domain model code generation from UML lab.
- Based on a discussion forum post, it was determined that a new functional requirement was needed to describe an owner's ability to respond to a question. This requirement was deemed to be different than the already existing FR9, which describes the admin's ability to respond to questions. It was reassigned code FR10 in our requirements list (with codes for already existing issues being reassigned) and issue backlog and represents our thirteenth functional requirement for the project.
Items Todo
- Shi Tong, Karl and Xinrui were assigned to complete SpringBoot implementation and to look into persistence.
- Michael volunteered to implement v2 of the domain model in the school's computer lab and was also reminded to finish organizing the minutes, wiki, and readme by the end of Saturday.
- Michael, Xinrui and Jia Wei were assigned to focus work on the persistence testing.
Follow up
- The updated domain model was agreed to be finished and pushed by the end of the day Friday.
- Most administrative duties were agreed to be finished by Saturday night.
- SpringBoot and persistence were agreed to be finished by Saturday night.
- Persistence testing was agreed to mostly be conducted over voice chat over the entire weekend with the goal of getting at least getting as much done as possible and functional before the Sprint 1 deadline.
No new formal meeting dates were proposed for the remainder of Sprint 1 however maintaining connectivity over voice chat and through Facebook Messenger over the next two days to finish pushing the Sprint was deemed imperative.
Meeting Minutes
Efforts
Report
Meeting Minutes
Efforts
Report
Meeting Minutes
Efforts
Report
Meeting Minutes
Efforts
Report