Maintenance Iteration Dec 6, 2020 - Hayoon-Heidi/FoodDeliveryApplication GitHub Wiki

Make a category for menu
\	Support Category	Refactoring Category	Item Description	Identified By	Hours Estimation
1	enhancement	architectural refactoring	Make a database table for menu category	Yerin Shin	1 hour
2	enhancement	data refactoring	Insert some sample entries and CRUD test on h2 console	Yerin Shin	0.5 hour
3		code refactoring	Update jsp files to show, add, edit categories	Yerin Shin	1 hour
4		code refactoring	Add model class, update DAO, mapper, controller classes	Yerin Shin	4 hours
5	adaptations		Integration test	Hayoon Kim	1 hour

Customer Review
\	Support Category	Refactoring Category	Item Description	Identified By	Hours Estimation
1	enhancement	architectural refactoring, code refactoring	Add image upload feature to review	Yerin Shin	2 hours
2	enhancement	data refactoring, code refactoring	Add time constraint to customer review	Hayoon Kim	3 hours
3	corrections	code refactoring	Make review deletable only for customers	Hayoon Kim	2 hours
4	adaptations		Integration test for review	Hayoon Kim	1 hour

For the next 1-3 years, it would be better to implement a Carrier section and chat service between users (Customer to Restaurant, and Carrier)

The Carrier section needs registration and my page to organized incoming and delivering orders. Therefore, we need to create a new database table for carriers just like the customer and restaurant table. The table will store the information about the carrier such as name, contact number, driving method, etc. Moreover, the way of change order status will be different. For now, restaurants have control over the order status. But, the carrier user needs to change the status of delivery (take the order and complete the delivery) which is the carrier has access to change it exclusively.

The chat service will act as a communication platform in the application. With this feature, users do not need to contact via private phone numbers.