-
Notifications
You must be signed in to change notification settings - Fork 2
Sprint 1: Meeting Minutes
Saagar Arya edited this page Nov 9, 2021
·
1 revision
Oct 7 Minutes (everyone in attendance, note-taker: Nima):
- This meeting:
- Reintroduced project requirements and established timeframe based on deliverable requirements
- Will be meeting again during reading week (between October 10-13) to reconvene after requirements engineering is done
- Established milestone on GitHub for requirements engineering deadline
- Brainstormed requirements together during today's meeting, will formalize the requirements and put them on GitHub prior to our next meeting
Oct 9 Minutes (everyone in attendance, note-taker: Arman):
-
This meeting:
- Completed list of 14 most important requirements
- Decided 6 most important requirements and assigned each member with one to describe in detail
-
To-do list for next meeting:
- Refine these requirements in use case diagrams
- Provide a detailed description of each of the 6 most important requirements (everyone does 1)
- Go over the domain model
-
Separate tasks after meeting:
- Each member will make a detailed specification of their assigned use case. (ie an activity diagram) - use an online diagram thing
- Selena, Kevin, and Nima make the use-case diagrams
- Two teams, one making a persistence layer, one tests the persistence.
Oct 12 Meeting (Everyone in attendance, note-taker: Arman):
-
This meeting:
- Reviewed use-case diagrams and detailed information about requirements
-
To-do list before next meeting:
- Catch up on tutorials
-
After/During next meeting:
- Review domain model key decisions and if any associations should be unidirectional (e.g. classes that point to TimeSlot probably could be, ItemReservation should point to Patron, RoomBooking should point to Room and to Patron)
- Decide who works on persistence and who works on testing it
- Manually translate the domain model into JPA compliant code
Oct 13 Meeting (Everyone in attendance, note-taker: Arman):
-
This meeting: Reviewed UML model and key decisions
- Set up the Spring Boot application project
- Assigned Saagar, Kevin, and Nafis to make the relational database tables and the persistence testing code
- Assigned Arman, Nima, Selena to write out the JPA compliant code for the UML class diagram and to make the persistence layer on Heroku
- GitHub issues made to track work
-
Before next meeting:
- Each team finish their main tasks
-
Next meeting:
- Make a team to organize the wiki and one to build the project
Oct 16 Meeting (everyone in attendance, note-taker: Arman)
-
Done this meeting:
- Run the persistence tests
- Worked on the persistence layer so that it builds properly
-
Next meeting:
- Fix the persistence tests so they all run and add some more so the suite is complete
Oct 18 Meeting (Everyone in attendance, note-taker: Arman)
- Done this meeting:
- Merged persistence layer branch onto main
- Closed issues for requirements and domain model
- Finishing touches on the wiki
- Completed the "success spectrum assignment"