Rapid technological advancements have disrupted multiple sectors, including communication, banking, and business. Before the Web's advent, businesses were confronting obstacles in connecting with the customers, boosting service speed, and monitoring the business climate. The Web bridged the gap and played a crucial role in transforming the business climate completely. Also, emerging technological trends are forcing companies to adopt and integrate new technologies to improve customer experience. Though technology disrupted conventional business practices, it also empowered small businesses to strive to broaden their horizons. The feeders attempt to leverage the Web's potential for bridging the gap between customers and business. Big players like Uber Eats have adopted technologies that quickly address and resolve customer's issues. Feeders.com is an effort to boost the capabilities of a newly launched restaurant that provides online food delivery services. Feeders currently are being operated in a single city. They don't have much muscle in allocating massive sums of money for improving customer experience, and their complaint management is also incapable of managing compliments quickly. The venture is in infancy; therefore, the quick attention to complaints can provide a competitive advantage. Also, having a well-functioning complaint management system can facilitate a healthy flow of information within the organization. Feeders will integrate an online complaint management system in the form of a portal on its site. With the site, users will be able to provide feedback related to the taste, food delivery, and any other issues. The integrated mechanism, then, automatically sorts the complaints. Moreover, the constructed portal will serve as a bridge between customers and the restaurant staff. Presently, the team manages complaints manually, which consumes a considerable amount of time. The website of the restaurant is also not upgraded. So, the team is required to redesign the site and in order to improve its user experience. The program will automatically schedule the complaints to notify the right person. Proven and time-tested methods were utilized in the design and development of feeders.com. Languages like HTML, CSS, PHP, and MySQL are widely popular languages that are commonly used to execute such operations. To execute the project on time with no errors, a significant amount of attention has been given to each and every phase of the project. Effective project management, neat and clean coding, excellent test planning, and detailed documentation helped the team deliver a high-quality, fully functioning web portal.

1. Feeders: An Online Food Ordering
System
Akhil Patel
California Miramar University
CIS 6190 (MSCIS)- Capsonte
Professor Elizabeth McGuire

2. Overview
❏ Background
❏ Business Plan
❏ Market Statistics
❏ Stakeholders
❏ Key Non-functional
Requirements
❏ Main languages
❏ Concept
❏ Scope
❏ Key Objectives
❏ Key Project Steps
❏ Team Structure

3. Overview
❏ Key Functionalities in Final
Deliverable
❏ ERP Diagram
❏ Results of the usability test
❏ Final Implementation
Status
❏ Lessons Learned

4. Background
The project "Feedeers.com" aims to assist small businesses who want to
sell their products or dishes online in the post-pandemic world. Therefore,
the project provides a platform for business owners to list, market, and sell
their products. Besides, these business owners can quickly address the
feedback and complaints and customize their products as per customer
preferences to improve their customer service.

5. Business Plan

6. Market Statistics
The online food delivery market is expected to hit US$182,327m by
2024. America is the second most favorable market for online food
delivery and is expected to grow at CAGR of 11.7%. As you can see
in the graph in the next slide – By 2020, food delivery platforms
usage will surpass 44 million people in the U.S., reaching nearly 59.5
million by 2023.

7. Market Statistics

8. Stakeholders
❏ Administrator
❏ Restaurant owners
❏ Customers

9. Key Non-functional Requirements
❖ Fully Secure
❖ Intuitive Design
❖ Upgradeable hosting plan
❖ Partial and full backups
❖ Back-end support during initial stages

10. Main languages
To design and develop Feedeers.com, we mainly used the following
languages :
➢ HTML
➢ CSS
➢ PHP
➢ MySQL

11. Concept

12. Scope
The scope is developed after gathering information from various
stakeholders. The team utilizes the team members' skills, knowledge,
and experience to meet the considered requirements. In the given
case, it is a fully functioning website with a portal to address the
consumers' complaints related to taste and other inconveniences.

13. Key Objectives
★ Deliver the project within the time frame
★ Meet all the requirements
★ Focus on quality
★ Intuitive design
★ Seamless user experience

14. Key Project Steps
❖ Gather stakeholder Requirements
❖ Identify Team Strengths
❖ Design a rough prototype
❖ Develop a Project Plan

15. Key Project Steps
❖ Coordinate, Execute, Review, Revise plan at Each Milestone
❖ Model design and Data Flow Diagrams
❖ Functional Prototype
❖ Final website

16. Team Structure
Mohammed Osama, Tejaswi Tiwari, and Ashwini Shelar carried the
responsibility of executing all the operations.
Team Member Assumed Role
AKhil Project Manager
AKhil Developer & Tester
AKhil Designer & Technical writer

17. Key Functionalities in the Final Deliverable
➔ Food cart for visitors
➔ Order selection and placement
➔ My account for creating profiles

18. Key Functionalities in the Final Deliverable
➔ Complaint forum link on the navigation menu to provide
feedback
➔ Connection to third-party payment gateway (Optional)
➔ Review option for each dish

19. Tech Architecture

20. Entity Relationship Diagram

21. Results of the usability test
Team got following results:
➔ The website is functional on every screen.
➔ Customers successfully performed all tasks irrespective of the
device and browser.
Bugs & Issues
All bugs are resolved.

22. Final Implementation Status
Implementation status assists in measuring the project plan's effectiveness.
As the group makes progress, they also encounter some unanticipated
situations where implementing predetermined measures can make the
situation even worse. Therefore, documenting implementation progress does
not help teams find loopholes and enable them to prepare themselves for
future unanticipated events. In such cases considering implementation status
can give an advantage to the team.

23. Final Implementation Status
The final implementation report contains all the functional and non-functional
requirements that were identified during the first milestone. Team also added
some criteria on behalf of stakeholders that were to be met. The table down
below reports implement status of functionality.

24. Lessons Learned
❖ Better Planning always delivers results.
❖ Cooperation is the key to success in team projects.
❖ Good Communication resolves all problems.
❖ Efficient resource leveling and smoothing are vital for achieving success
in any project.
❖ Assigning tasks after assessing capabilities saves time and enhances
quality.

25. Thank You!