FAST FOOD RESTAURANT MANAGEMENT SOFTWARE FINAL REPORT Management Information Systems Class code: ITE1129E.Truc Group 7 Le Thuy Vi-205121293 Le Nguyen Trieu Giang-205120305 Nguyen Mai Nguyet-205121241 Ho Chi Minh City – October,2023 1 TABLE OF CONTENTS CHAPTER I: OVERVIEW.1 Reasons for choosing C#.2 Reasons for choosing SQL. THE CURRENT STATUS SURVEY.11 CHAPTER II: SYSTEM ANALYSIS DESIGN. USE CASE VIEW.1 Use case diagram.2 Use case description. Explanation of classes.
ENTITY-RELATIONSHIP DIAGRAM. 35 CHAPTER III: INFORMATION SECURITY.xxviii CHAPTER III: APPLY IoT TO DESIGN AN AUTOMATIC FIRE ALARM SYSTEM.xlviii CHAPTER V: KMS.36 CHAPTER VI: CONCLUSION.xlix TABLE DIRECTORY Table 1: Project Process. Manage Category Information. Manage Product Information.
Manage Staff Information. Confirm status of orders .19 Table 9: Class “Category” .20 Table 10: Class “Product”.21 Table 11: Class “Details” .21 Table 12: Class “User”. 21 Table 13: Class “Staff” .22 Table 14: Class “Main” .22 Table 15: Class “Table” .22 4 FIGURE CATEGORY Figure 1: Business Process of Restaurant Management System.13 Figure 2: Use case diagram.14 Figure 3: Class diagram.20 Figure 4: Database diagram. 23 Figure 5: Relationship diagram.23 Figure 6: Sequence diagram of Login.24 Figure 7: Sequence diagram of Manage Category.25 Figure 8: Sequence diagram of Manage Product.26 Figure 9: Sequence diagram of Manage Table.27 Figure 10: Sequence diagram of Manage Staff.28 Figure 11: Sequence diagram of Order.29 Figure 12: Sequence diagram of Setting.30 Figure 13: Activity dỉgram of Login.31 Figure 14: Activity dỉgram of Product.32 Figure 15: Activity dỉgram of Order.33 Figure 16: Activity dỉgram of Payment.34 Figure 17: Activity dỉgram of Confirm order.35 Figure 18: Activity dỉgram of Setting.36 Figure 19: Security process.38 Figure 20: Automatic fire alarm system.40 Figure 21: Fire alarm system in normal time.41 Figure 22: Fire alarm system when there is a risk of fire.42 5 REVIEW AND EVALUATION ……………………………………………………………………………………… ……………………………………………………………………………………… ……………………………………………………………………………………….
Monday, 7th October 2023 Giảng viên N.TRÚC 6 THANK YOU First and foremost, we would like to thank Ho Chi Minh City University of Finance and Economics and the instructor for the course "Management Information Systems" for their assistance. We have had the chance to study and discover fresh and significant information because of this issue. Truc actively shared her expertise with us and was always available to help us as we learned. Everyone in our organization is really interested in this topic and recognizes its importance.
Our future growth route will allow us to better prepare ourselves with the support of this core knowledge. However, given our lack of experience, our products will inevitably have flaws. Your opinions and feedback are crucial to our ability to do better in the future. We appreciate you very much! 7 INTRODUCTION Fast food is evolving into a vital component of world cuisine.
This sort of cuisine gradually grows significantly and becomes important in daily life due to its quickness and convenience, especially in today's hectic life. With several restaurant chains, fast food industry is expanding in Vietnam and is gaining support and funding for expansion. These are goods that have a large economic impact on the nation. Our team decided to focus on "Building fast food restaurant management software" in order to satisfy the industry's significant development trend.
This program is created to help fast food business managers and shop owners. This aids business owners in maintaining daily data and raw supplies at each branch's warehouse. Concurrently, enhance staff service procedures. The program will also assist managers in managing human resources by department, income, etc., as well as in tracking sales activity.
Additionally, capabilities for ordering and door-to-door delivery are linked to make it simpler and easier for customers to make purchases. We will assist fast food businesses in simply and effectively gathering information from the service and cooking departments, assisting managers in making choices through full reports and summary reports, thanks to our fast food restaurant management software. Create future strategies, plans, and initiatives from there. INTRODUCTION Nowadays, many restaurants have been created to meet the demands of those who eat.
However, many restaurants still use the old method of ordering food. This seemingly insignificant action takes a long time and occasionally results in errors. If a crowded restaurant continues to allow this condition to occur for an extended period of time, it will influence employee work pressure and reduce satisfaction with customers. To address the issue, our team developed a restaurant management system.
It is designed to streamline and enhance the operations of a restaurant or food service establishment and become an indispensable tool in the modern food service industry, harnessing the power of technology to improve efficiency, customer satisfaction, and overall business performance and minimize human errors. The order processing and management process is run sequentially, simply but effectively. Everything runs smoothly and makes the guests feel satisfied. Project scope Our restaurant management system will be implemented on the cashier computer system in the small and medium restaurant, allowing cashiers to settle customers' bills swiftly and accurately, as well as conveniently generate invoices for customers.
About theory: - Learn programming techniques, how it works and objects in C#. - Understand how SQL Server database management system stores data. About program setting: - Using C# language and SQL Server administration system to build software. - Research some framework to build more effective functions.
Reasons for choosing C# Advantages: - Robust Programming Language: C# is a powerful and readable programming language, enabling rapid and efficient application development. - Support for Object-Oriented Programming (OOP): C# supports OOP, aiding structured code organization and code reuse.NET Framework: C# seamlessly integrates with the .NET Framework, a robust platform for developing Windows and web applications. 9 Disadvantages: Limitations for Cross-Platform Development: C# is primarily used for Windows applications, and developing cross-platform applications may require additional measures. Reasons for choosing SQL: Advantages: - Popular Database Management System: SQL Server (or other SQL-based database management systems) is one of the most widely used database systems globally, with extensive support and documentation.
- Integration with C#: SQL Server integrates well with the C# programming language through ADO.NET, making database operations more straightforward. - Powerful Query Support: SQL provides robust features for data querying, analysis, and reporting. Disadvantages: Database Costs and Management: Database management systems like SQL Server come with associated usage and management costs, especially in large enterprise environments. Project target The fast food software, programmed in C# and using SQL for the database, is designed with two main objectives: - Gain in-depth expertise in the restaurant industry and the operational environment of the system: - Ensure that this software is developed based on professional knowledge of the restaurant industry.
- Understand the operational processes and specific requirements of the restaurant environment. - Develop an application with high practicality and ease of deployment: - Develop an application that meets the real-world needs of users, especially those in the fast food business. - Create a user-friendly and convenient interface, allowing users to perform tasks simply and quickly. The main goal of the fast food software is to provide an efficient solution for businesses in the fast-food industry, helping them manage and operate their restaurants effectively while also meeting the needs of customers conveniently and quickly.
DECRIPTION Our restaurant management system includes 3 main components: Section for cashier: 10 - When creating an order, the cashier proceeds to enter information including order ID, name of items, quantity, din in or take away, table number, waiter name (if any) and total amount. - If the customer buys for the first time, the cashier updates customer information into the database before create an order Section for manager: - Manage food categories, enter and edit dish names, unit prices, quantities,… - Manage all staff information: staff ID, full name, phone number, role (waiter, cashier, .) Section for kitchen staff: - When the cashier sends order information to the kitchen department, the kitchen staff executes the order and updates the order status. THE CURRENT STATUS SURVEY After examining the current condition, the group discovered the following: - Product management: the following information is used to manage the selling price: Product Image, Product Type, Product Name, and Unit Price are all required. - Employee management: The following information is used to manage each employee: Employee information includes name, phone number, and role.
- Product type management: the following information is managed for each product type: Enter the product name. - The sales procedure is as follows: When selling, the system will determine whether the number of items purchased by clients is in stock. If it is, the quantity of products in stock will be updated. Notify the amount is insufficient if it is out of stock.
When clients purchase goods, the system saves customer information, sales personnel, and order time. The sales invoice will then be saved. - Administrator (admin): The person who owns the system and has authority over all system actions. To accomplish their tasks, the administrator is given a username and password to login to the system.
- If the login process is successful, the manager will be able to monitor and update product and staff information, check orders, and process orders. PROJECT PROCESS Table 1: Project process Stage Work Purpose Planning - Come up with ideas for the system Build a restaurant interface. management system - Identify system features and content. - Assign work - System deployment - System testing and development Research - Research about consumer behavior Unify system layout - Refer to other management systems - Learn about the available technologies and the necessary functions Design - Design database Create a restaurant - Design the interface management system with a user-friendly interface System - Deploy system Test the restaurant deployment - Point out the limitations of the system management system System - Testing and evaluating the system Ensuring software quality Development - Optimize system limitations Maintenance - Eliminate errors and upgrade restaurant Maintain software quality management system 12 CHAPTER II.
SYSTEM ANALYSIS DESIGN 1. BUSINESS PROCESS Figure 1: Business Process of Restaurant Management System The main actors include the customer, cashiers, kitchen and delivery department. We can divide them into two groups: the selling entity which is the restaurant, and the buying entity which is the customer. The first event starts when the customer visits the website to select a menu and then chooses the quantity.
The restaurant offers three options: takeaway, home delivery, and dine-in. The customer can choose one of these options. If the customer selects dine-in, they will continue to choose a table and waiter. If they opt for delivery, they provide information such as the delivery address and phone number.
Next, the cashier receives the order request, confirms it. The customer will wait for notification to receive the orders. At the same time, the kitchen will prepare the food. When it's ready, the kitchen staff confirms completion to notify customers to come to the counter to pick up food.
If customers wait too long and do not receive notification, they can complain and urge the staff. In case the customer chooses delivery, the delivery staff picks up the food at the counter and delivers it to the customer. The customer receives the order and pays the bill. USE CASE VIEW 2.
Use case diagram Figure 2: Use case diagram 2. Use case decription Table 2: UC - 1. Login Use case ID UC-1.0 Use case names Login Description Only users have access to the system Actor Management staff, Kitchen staff, Cashier Pre-conditions Users must have an account. Users access the application.
The application will display the login’s form. If the users select the function “Exit”, the application will be finished. If users select the function “Login”, the application will follow steps below. - Fill in the required user and password.
- Click the function “Login”. - The application will display the main interface (Home page). Post- conditions If entered the correct information: - Display the main interface (Home page). 14 If entered the wrong information: - Display an error and requiring to re-enter Table 3: UC - 2.
Manage Category Information Use case ID UC - 2.