-
Notifications
You must be signed in to change notification settings - Fork 1
Sprint 3 Report
Yichen Wu edited this page Apr 4, 2021
·
26 revisions
Run the following commands to install all the plugin used in the project
npm install vue-toast-notification
npm i vue-mailchimp-email-signup-form
npm install --save vue-cal
npm install [email protected]
npm i --save vue-ctk-date-time-picker
Name | Contibutions | Hours |
Florence Yared |
|
7 |
Himel Saha |
|
46 |
Rakshitha Ravi |
|
30 |
Saikou Ceesay |
|
40 |
Yichen Wu |
|
20 |
Note: Due to Covid-19 pandemic, all meetings on conducted through online conference calls
Date: March 22, 2021
Time: 8:00PM - 8:30PM
Attendees: Florence Yared, Himel Saha, Saikou Ceesay, Rakshitha Ravi, Yichen Wu
Minutes:
- Discussion on the architecture modelling
- Division of labour for Deliverable 3:
- Florence Yared:
- General design of the web frontend
- Web frontend implementation for the timeslot class
- Integration of timeslot web frontend with backend services.
- Himel Saha:
- Web frontend implementation for the bookable service class
- Integration of bookable service web frontend with backend services.
- Rakshitha Ravi:
- Web frontend implementation for the person class
- Integration of person web frontend with backend services.
- Saikou Ceesay:
- Web frontend implementation for the business and bill class
- Integration of business and bill web frontend with backend services.
- Yichen Wu:
- Web frontend implementation for the appointment class
- Integration of appointment web frontend with backend services.
- Florence Yared:
Key Decisions:
- we agreed on applying layered architecture model to the RepairShop System
Date: March 29, 2021
Time: 12:00PM - 1:00PM
Attendees: Florence Yared, Himel Saha, Saikou Ceesay, Rakshitha Ravi, Yichen Wu
Minutes:
- Update on the change in UI (click here to see the mockup on figma)
- Modification of the domain modelling (see the new edition here)
- Revision of the division of labour
- Revision of feedback from deliverable 2
Key Decisions:
- Modification of the domain modelling:
- use the user-role pattern to distinguish between different roles
- keep one of the owner or administrator since they have the same roles