-
Notifications
You must be signed in to change notification settings - Fork 3
Meeting Minutes
The goal of this page is to record the meeting contents for all sprints/deliverables. Details are below:
- 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
- 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)
2hrs - Attendants: All
- 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
2hrs - Attendants: Yi Wei/Victoria/Mathieu/Jiatong
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
2hrs - Attendants: Yi Wei/Victoria/Mathieu/Zichen
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
-
1hrs - Attendants: All
PLANNED
- Go over unit testing
- Overall bug testing and fixing performed
- Completing the loose ends of the deliverable for Sprint_1
20hrs - Attendants: All
Planned
- Recap on the feedback of Sprint1
- Start off on the Sprint2
Questions:
- Should we separate the test code into several individual classes?
- Appointment-Technician association, confirm that our design is good based on the feedback?
- Resources class: add explanation in wiki.
- Send reminder/send notification, should we change the detailed requirements? What was the intended change?
- Does the difference in name that IsotopeCR and root class autoRepairShop cause problems?
1hrs - Attendants: All
Planned
- Go over the requirements and generate a list of service methods.
- Distribute to each person to work on service methods individually.
1.5hrs - attendants All
Planned
- Service Method
- Dto objects
Questions:
- What to do with the ID generation inside for the services. -- create ID inside one method?
- Where should we check the input validity? at what point? -- inside service method?
- Connection btw service&controller method
1.6hrs - Attendants: All
Planned:
- Writing controller methods.
- Prepare to test on controller methods.
Decision: Make every necessary input check inside service method.
5hrs - Attendants: All
Planned:
- Wrapping up controller methods.
- Test the controller methods in the REST Api
10hrs - Attendants: All
Planned:
- Write Unit tests
- Test the controller methods in REST Api
5hrs - attendants Zichen/Jack/Jiatong
Planned:
- Go over the Unit tests coverage
- Double check the Sprint2 requirements
- Start on Documentation
5hrs - attendants All
Planned:
- General overview of the deliverable
- Double check the Sprint2 requirements
- Submission of the deliverable
1hr - attendants All
PLANNED:
- General overview of the deliverable
- Submission of the deliverable
3hrs - attendants All
PLANNED:
- Frontend design
- Seperation of work
- AXIOS function
5hrs - attendants All
PLANNED:
- Frontend design
- AXIOS function
4hrs - attendants Victoria / Zichen / Jack Wei
PLANNED:
- Frontend design
4hrs - attendants Victoria / Zichen / Jack Wei
PLANNED:
- Frontend design
4hrs - attendants Victoria / Zichen / Jack Wei
PLANNED:
- Frontend design
- Finishing up the deliverable
5hrs - attendants All
PLANNED:
- Frontend design
- Finishing up the deliverable
8hrs - attendants All
PLANNED:
- Submitting and finalizing the deliverable
8hrs - attendants All
PLANNED:
- Organizing final deliverable schedule
- Decisions made upon which features will be available within our Android application
40min - attendants All
PLANNED:
- Familiarization with Android development
- Initial stages of the implementation of the chosen features.
4hr - attendants All
PLANNED:
- Log-in feature implemented for the application.
- Continuation of our Android development.
5hr - attendants All
PLANNED:
- Book Appointment resolved.
- Continuation of our Android development.
- Start of documentation on Github wiki.
3hr30min - attendants All
PLANNED:
- Continuation of our Android development.
- Continuation of documentation on Github wiki.
4hr - attendants All
PLANNED:
- Continuation of documentation on Github wiki.
- Submitting and finalizing the deliverable.
3hr - attendants All