Final Video - Record

[kliu57]

**Deadline: Sat Apr 6 2024 11:59pm (so there is time to combine)

Total time must be between 10-12 minutes**

1. Intro - 30 seconds (product, project name, team members) (Vivy)

2. Problem statement and product vision - 1 min 30 sec (Danny- problem statement 45sec, katie- product vision 45sec)

3. Walkthrough of network diagram (2min) (Kevin) (Remind to ask him on thursday do we need to walkthrough everything or just the stuff after video 3)

4. Demo 2-3 important use cases - (4 min) (Katie)

Demo: (1. Owner make restaurant, 2. Customer going to restaurant and make order, and owner processing order in admin portal, and customer tracking order)

5. Overview of project code on github - 2 min (Vivy)

6. Do three of the tests on the system test plan excel sheet (choose three test cases that are not in Number 3 (walkthough and demo) - 4 min (Yumei) (maybe no time to show the test case just run the test case)

   1- Theme (3 themes) (Classic, Dark, Modern)
   2- Promotion
   3- Order history

7. (project) Summary and lessons learned - 1 min (Kevin) DONE!

8. Combine (Danny)

[Vivy24]

Sent my part to Danny Lesson learn: Through this project, I have learned about how to deploy server and database to third party dedicated server using Ubuntu OS. I also learned how important of assigning tasks and dividing tasks into milestones so we can always keep track of the project progress and make sure that we could have final product on time.

[kliu57]

Example of lessons learned:

[kliu57]

Katie's lesson learned: (a challenged I faced, and something I learned that can help me in my next project) (you could also put something positive that happened that you can use next time as well)

- Important to have regular team meetings

At the beginning the term we tried to work asynchronously with minimal team meetings that were infrequent and not set on a regular basis. This slowed down our progress, because it was hard for those who needed help to get a hold of other members. Also, without a regular time, it was difficult to constantly try to schedule new meeting times, which sometimes caused the meeting to not happen. Regular weekly or biweekly team meetings are essential to the timely completion of a project. Not only can people get a hold of others who may be blocking their progress, it allows the project manager to get a progress check. This means there is lower chance of missed deadlines due to a block or due to misunderstanding of deadlines.

[kliu57]

I also learned how important of assigning tasks and dividing tasks into milestones so we can always keep track of the project progress and make sure that we could have final product on time.

This is really good one! Just need some more supporting evidence of what challenge we faced and how doing the task division help us overcome it. but kevin can write it I think.

[WangGithub0]

The Importance of Addressing Every Bug

During the development of our application, we encountered a recurring issue where previously inputted data would disappear, initially dismissed as minor glitches or accidental deletions. However, it happened again, upon deeper investigation, we discovered that the root cause was the use of outdated backend code by some team members. This revelation highlighted the critical importance of addressing every bug, no matter how insignificant it might seem at first glance. We learned valuable lessons about the necessity of maintaining consistency across our development environment by ensuring all team members regularly update their local copies with the latest backend code changes. Implementing this practice effectively eliminated the data loss issue, underscoring the importance of vigilance, effective communication, and adherence to best practices in version control and team collaboration to prevent similar problems in the future.