UNIVERSITY OF TECHNOLOGY
FACULTY OF COMPUTER SCIENCE AND ENGINEERING
Software Engineering / Semester 211
Team iGears
This project is proudly done by:
- Front-end:
- Back-end:
- API
- Version Control:
- UML Diagram:
- Report:
This project is targeted to be a web-based point-of-service (POS) system that empowers restaurants administrative with class management tools in order to operate their business efficiently. Apart from the regular dine-in service mode, this system also incorporates Internet-based and QRcode-enabled applications to address the difficulties occurred during the COVID-19 pandemic. It facilitates simplified, straight-forward and contact-less interactions between restaurant customers and staffs, e.g. food ordering, servicing, and payment in any convenience. The application also supports automation of various internal restaurant management tasks, such as order recording, order status managing, transaction recording, etc.
The relevant stakeholders of this proposed system may include human resources such restaurant owner, managers, and staff (including clerks, chefs and janitors), and external consumerism, e.g.restaurant customers/clients.
The system consists of the following features that enable the complete functionality:
- A menu screen for displaying the restaurant’s menu; customers can make their selections in this screen.
- A detail screen for each food, which will provide pictures and/or related information of a specific food.
- A cart that visually display customer’s selected food; this screen allows customers to re-check, edit and place their orders.
- A payment screen that offers different payments options.
- An order processing screen that will be displayed while the food being made; this screen contains status of customer’s pending order.
- A feedback screen to receive customers’ feedback on qualities of the restaurant’s food and services.
The following section describes the all functional and non-functional requirements in context of the desired system. A use case diagram is also presented to cohesively illustrate the interactions of the said system.
The central objective of this project is to propose a web-based solution for restaurant owners, to help them maintain the normal operation of their business, while limiting physical / direct interactions between restaurant customers and staff as much as possible. To illiterate in clearer details, the in and out scopes are as follows:
- A responsive website with attractive UI, categorization, filter and search functionality.
- A back-end system to provide support for multiple restaurants, with the ability of handling approximately 300 transactions per day.
- An online database that supports inventory management.
- Interactive platform to facilitate contactless interactions between restaurant staff.
- Restaurant staff management system.
- Delivery management system.
- Payment processing system.
This section will perform laid-out diagrams to capture the major functional requirements of the desired restaurant POS system. It is divided into three caconicals of an activity diagram, a sequence diagram and a class diagram.
.png)
A fundamental approach to visualize the structural integrity of the entire restaurant point-ofsale system presented in this project is via a cohesive blueprint of the overall architecture. In this section, all of the foundational components of the application are described in detail, with reasoning of choice and facilitation.
There are numerous architectural patterns that capture the design structures of various systems and elements of software so that they can be reused. For this project’s system, to fully utilize the power of cloud-based ordering point-of-sale, using application programming interfaces (APIs) instead of a fixed model, a much more advanced version of Model-View-Controller (MVC) pattern is needed.
Cloud-native architecture is a suitable upgrade for MVC. It allows dynamic and agile application development techniques that take a modular approach (API with user-interfaces and services) to building, running, and updating software through a suite of cloud-based microservices and containerization with agility and dynamism versus a monolithic application infrastructure.
The following deployment diagram models the physical deployment of artifacts on nodes, in this case, the topology of the POS system outlines six logical components: website package, customer management, order, menu, payment and seating requirements. When a user executes an order on the website, their operations are performed in a packaged online environment. One can visit the website, browse through a list of menus, make order and seating reservation, while optionally choose to sign up or sign in to their account. After everything is completed, the payment system shall be activated and can access the customer database if prompted.
