Alternative flow: [A1]: Actor clicks No then the message will disappear and return to the list of POS Exception flow: E1]: “POS contains menu, table and invoice” notification is displa
Introduction
Purpose
The Functional Requirements Specification will:
❖ Define the scope of business objectives, business functions, and organizational units covered,
❖ Identify the business processes that the solution must facilitate,
❖ Facilitate a common understanding of what the functional requirements are for all parties involved,
❖ Establish a basis for defining the acceptance tests for the solution to confirm that what is delivered meets requirements
This document aims to gather and analyze various ideas that define the system and its requirements concerning consumers Additionally, it seeks to predict and organize potential product usage to enhance project understanding, outline future development concepts, and document ideas that may be considered or discarded as the product evolves.
Overview
IC Hub is an innovative system designed to streamline menu creation and table layouts for establishments like coffee shops and restaurants It efficiently records and calculates bills for each account associated with these services, enabling customers to place orders through an electronic menu linked to their specific table The system logs all orders, allowing store management to monitor and manage them effectively Furthermore, IC Hub handles payment information, facilitating seamless Point of Sale operations for the store.
Intended Audience and Reading Suggestions
This document is intended for:
❖ Development team: Responsible to develop detailed design, implement and perform unit test Also perform test manual
❖ Project Owner: Responsible to manage the Product backlog for the application
SMEs Small and Medium Enterprise
Related work
Posapp
Founded in 2013, Mobitouch aimed to revolutionize business operations through technology, and in 2019, it transitioned into a joint stock company, officially rebranding as PosApp Technology.
Founded as a technology start-up focused on outsourcing software products for partners in Japan, Canada, and Malaysia, we specialize in delivering solutions tailored for small and medium enterprises (SMEs) In 2014, we identified the growing demand for effective sales and management tools among small shops and stores, leading to the development of our innovative sales management solution, PosApp.vn.
This comprehensive management system streamlines customer management, storage management, human resource management, and POS management, offering a user-friendly dashboard for effective oversight Key features include menu management, which allows clients to analyze dish trends and easily add, delete, or edit menu items Customers can conveniently place orders directly at their tables using a QR code, ensuring a seamless online and offline sales experience and facilitating an efficient end-to-end process for orders and payments.
Last modified on 1 Dec –24 o Order to payment process:The process is relatively complete
Odoo
Odoo is an open-source suite of business applications designed to meet all your company's needs, including CRM, eCommerce, accounting, inventory management, point of sale, and project management With a wide range of features, Odoo can effectively address nearly all your business requirements.
The software offers essential features tailored for small and medium-sized enterprises (SMEs) and large communities, including comprehensive table management that allows users to create, edit, and delete tables while visualizing them in a diagram Customers can also manage the availability of tables within the POS system Additionally, the dashboard provides insightful analytics on sales and revenue through charts, enabling clients to easily interpret data and assess their business performance, complemented by precise information presented in a statistics table.
Bindo labs
• Introduction: The Omnichannel POS and Payment Solution to Scale Your Business Bindo provides solutions for the F&B, Retail, Hospitality, and other industries in today’s fast-paced and challenging business environment
The platform offers a comprehensive suite of features tailored for SMEs, highlighted by its visually appealing user interface It includes robust table management capabilities, allowing users to create, edit, and delete tables while visualizing them in a diagram Customers can efficiently manage the number of tables available in their POS system, align table positions, and oversee bookings, including booking times and table combinations Additionally, the dashboard provides insightful visualizations of sales and revenue, enhancing the overall user experience with its beautifully designed layout.
High Level Requirements
System structure
The system architecture will be described in the software development phase.
Workflow
This section outlines the sequential tasks performed by users within the system to successfully complete a business process It details the actions taken at each stage of the process and describes the conditions required to advance to the next stage or return to a previous one.
Use Case Diagram
The use case diagram illustrates the user's interaction with the system, highlighting specific goals and objectives The eclipse within the system boundary signifies the functions or use cases of the system, while the stickman symbolizes the actor or user The connecting line between the actor and the use case indicates that the actor can execute that function to accomplish a goal.
IC Hub Operations Team: the person who is responsible for operating and managing the system
Client: the person who creates and uses the services
Client's Customer: the person who place orders and make payments at the POS
Client's POS Admin: the person managing the POS for the Client
The individual responsible for managing the Cursus system plays a crucial role in overseeing the approval and rejection of instructor-led courses, ensuring the overall quality and integrity of the course offerings Additionally, this role involves maintaining the health and functionality of the Cursus system, contributing to a seamless educational experience.
Permission matrix
Permission Matrix mapping functions and user roles for application is described as below: Remark:
“O” means that user has permission on corresponding function For more information about what the actor can do on that function, please refer to corresponding use case
“X” means that user does not have permission on corresponding function
Confirm order – change order status O O X X
Manage person (pos admin account)
View list pos admin account O X X X
Create new pos admin account O X X X
Use Case Specifications
Client and client pos admin functions
Objective: Allow actors register for an account to be able to log in to the system
Pre-condition: Actor has no account yet
Post-condition: Actor creates new account successfully can use that account to log into the system
Main flow: (1) In home page, actor choose sign in
(2) Page sign in pop up, actor choose sign up
(4) User fills in the required information (Name, Username, Password, Phone number(optional))
(5) Actor clicks sign up button (E1) (E2) (E3)
(8) Authentication code is sent via Gmail
(10) Actor enters the authentication code
(11) Actor clicks the Authentication button (E4) (E5)
Exception [E1]: “Wrong Email, Phone number format” notification was displayed
[E2]: “Phone number, Email, Username exist” notification was displayed
[E3]: “Email, Username, Password, Phone number, Name is blank” was displayed [E4]: “Verification incorrect” notification was displayed
[E5]: “Verification expired” notification was displayed
4.1.2 UC 02: Login for Client and Client pos admin
Objective: Allow actors log in the system using Username and Password
Pre-condition: The actor's account has been registered on the system
Post-condition: Successful login: Actor moves to the system's Client home page
Basic flow: (1) In home page, actor choose sign in
(2) Page sign in pop up, actor enters Username and Password
Exception [E1]: “Username or Password are blank” notification was displayed
[E2]: “Username or Password is incorrect” notification was displayed
Objective: Allow actors service payment and use service in page
Pre-condition: The actor has successfully sign up
Post-condition: The actor pays successfully and actor the service
(1) After sign up successfully, actor get inside web
(2) Actor clicks Menu icon or Seating Diagram icon on the left bar
(3) The system check if the actor’s service order is active
(4) If the actor’s service order is not active then show popup “You need to hire the service”
(5) Actor clicks the See Features button
(6) Page Payment pop up, web page have 2 service Standard (15$) and Premium (20$)
(7) Actor can choose appropriate service and clicks Order Now
(8) Page credit card details pop up, actor enter information credit card and click buy (E1) (A1)
(9) Message show payment service successfully
(10) Actor clicks close and continue use service
Alternative flow [A1] The actor click “Cancel” button and then the system navigates back to home page of client
[E1]: “Credit card information is blank or incorrect” notification was displayed
Objective: Allow actors creates POS to manage branches
Pre-condition: Actor has payment service successfully
Post-condition: The Actor creates POS successfully
(3) Actor clicks Add New Store
(4) System display Popup Store Detail, actor can be allow fill in the required information (Name, Manager, Province, District, Local Detail)
(5) Actor clicks Create to creation store (E1) (A1)
(6) Message show creating POS successfully
[A1]: Actor clicks Cancel to back the store
Exception [E1]: “Name, District, Street name, Province is blank” notification was displayed
Objective: Allow actors updates POS
Pre-condition: Actor has created at least 1 POS
Post-condition: Actor edits successfully attributes of POS
(3) Actor clicks pencil icon on the right hand side on each line for editing
(4) System display popup page detail, actor customizes the information of this store (Name, Manager, Province, District, Local Detail)
(5) Actor can edit status store from active to Inactive or opposite
(6) Status Inactive will not store not inactive
(7) Actor clicks the Save button (E1) (A1)
Alternative flow: [A1]: Actor clicks Cancel to back the store
Exception flow: [E1]: “Name, District, Street name, Province is blank” notification was displayed
Objective: Allow actor deletes POS
Pre-condition: POS does not have any menus, ordering or invoices
Post-condition: The actor deleted POS successfully
Main flow: (1) Actor clicks Store
(3) Actor clicks x mark on the right hand side on each line for deleting
(4) A message appears asking if you want to delete POS
(5) Actor clicks the Yes then POS will be deleted (A1) (E1)
(6) The list of pos will disappear from the line you just deleted
Alternative flow: [A1]: Actor clicks No then the message will disappear and return to the list of POS
Exception flow: E1]: “POS contains menu, table and invoice” notification is displayed
Objective: Allow actors create new menu
Pre-condition: The actor has at least 1 store
Post-condition: The actor creates menu successfully
(2) Actor choose store want to create menu
(3) Actor clicks plus sign on each row of the list
(4) The system displays a screen menu detail
(5) Actor clicks plus icon in categories bar and press enter
(6) Actor clicks plus icon below the categories bar to create dish item
(7) The system displays food detail popup
(8) Actor fills information food name, price, detail and upload image
(10) The system show create successfully message, reload the menu item list
Alternative flow: [A1]: Actor clicks Cancel then you will return to menu
Exception flow: [E1]: “Name, price, detail, image dish is blank” notification was displayed
Objective: Allow actors update menu
Pre-condition: The actor has created at least 1 Menu
Post-condition: The actor updated menu successfully
Main flow: (1) Actor clicks Menu
(2) Actor choose store want to create menu
(3) The system display menu list
(4) Actor clicks pencil icon on the right hand side on each line for editing
(5) The system displays a screen menu detail
(6) Actor clicks edit name category
(7) Actor clicks into category name
(9) Popup page, Actor edits information about the name, price, upload photo and detail of the dish
(11) On the right side there is a list of menus for that pos, the actor can select any and edit it
(12) Actor can edit menu store from active to Inactive or opposite
(13) Status Inactive will not menu not inactive
Alternative flow: [A1]: Actor clicks Cancel then you will return to page
Exception flow: [E1]: “Name, price, detail, image dish is blank” notification was displayed
Objective: Allow actors delete menu
Pre-condition: Actor has created at least 1 menu
Post-condition: The actor deleted menu successfully
Main flow: (1) Actor clicks Menu
(2) Actor choose store want to delete menu
(3) The system display menu list
(4) Actor clicks x mark on the right hand side on each line for deleting
(5) A message appears asking if you want to delete menu
(6) Actor click Yes then Menu will be deleted (A1) (E1)
(7) Actor clicks clicks pencil icon on the right hand side on each line
(8) Actor clicks x mark on category
(9) A message appears asking if you want to delete category
(10) Actor click Yes then category will be deleted (A1) (E2)
(11) Actor clicks x mark on dish
(12) A message appears asking if you want to delete category
(13) Actor click Yes then dish will be deleted (A1) (E3)
Alternative flow: [A1]: Actor clicks Cancel then you will return to menu
Exception flow: [E1]: “The menu is in use or has a dish created in it” notification was displayed
[E2]: “The category is in use or has a dish created in it” notification was displayed [E3]: “Dish is using by customer ” notification was displayed
4.1.10 UC 10: Create new seating diagram
Objective: Allow actors create new seating diagram
Pre-condition: The actor has at least 1 store
Post-condition: The actor created successfully seating diagram
Main flow: (1) Actor clicks SDiagram
(2) Actor choose store want to create menu
(3) The system display seating diagram list
(4) Actor clicks plus sign on each row of the list
(5) The system open popup create new seating diagram
(6) Actor clicks plus sign to add floor
(7) Actor clicks create, table detail appear
(8) In table detail, actor fills information (Name, Capacity), the qr code is automatically generated
(9) Actor click Save then table will be created (A1) (E1) (E2)
(10) The system show create successfully message, reload the menu item list
Alternative flow: [A1]: Actor clicks Cancel then you will return to seating diagram
Exception flow: [E1]: “Name, capacity table is blank” notification was displayed
[E2]: “Capacity table is not format” notification was displayed
Objective: Allow actors update seating diagram
Pre-condition: The actor has at least 1 seating diagram
Post-condition: The actor updated successfully seating diagram
Main flow: (1) Actor clicks SDiagram
(2) Actor choose store want to create menu
(3) The system display seating diagram list
(4) Actor clicks pencil icon on the right hand side on each line for editing
(5) The system displays seating diagram detail screen
(6) Actor clicks table and move anywhere
(7) Actor clicks edit table, the system displays the table detail popup
(8) The actor change name and capacity of table and click Save (A1) (E1)(E2)
(9) Actor can edit status seating diagram from active to Inactive or opposite
(10) Status Inactive will not seating diagram not inactive
Alternative flow: [A1]: Actor clicks Cancel then you will return to seating diagram
Exception flow: [E1]: “Name, capacity table is blank” notification was displayed
[E2]: “Capacity table is not format” notification was displayed
Objective: Allow actor delete seating diagram
Pre-condition: Actor has created at least 1 seating diagram
Post-condition: The actor deleted successfully seating diagram
Main flow: (1) Actor clicks SDiagram
(2) Actor choose store want to create menu
(3) The system display seating diagram list
(4) Actor clicks x mark on the right hand side on each line for deleting
(5) A message appears asking if you want to delete seating diagram
(6) Actor click Yes then seating diagram will be deleted (A1) (E1)
(7) Actor clicks clicks pencil icon on the right hand side on each line
(8) Actor clicks x mark on floor
(9) A message appears asking if you want to delete floor
(10) Actor click Yes then seating diagram will be deleted (A1) (E2)
(11) Actor clicks x mark on table
(12) A message appears asking if you want to delete table
(13) Actor click Yes then table will be deleted (A1) (E3)
Alternative flow: [A1]: Actor clicks Cancel then you will return to menu
Exception flow: [E1]: “Seating diagram is in use or has tables created in it” notification was displayed
[E2]: “The floor is in use or has tables created in it” notification was displayed [E3]: “Tables is using by customer ” notification was displayed
4.1.13 UC 13: Create new pos admin account
Objective: Allow actor create new pos admin account
Pre-condition: The actor has successfully logged in, the actor is on the Website
Post-condition: The actor created successfully pos admin account
Main flow: (1) Actor clicks person management menu on left-bar
(2) The system display user list [E1]
(3) The actor click button add user
(4) The system open popup creates user account
(5) The actor input (name, username, password, pos, phone number, email) and click
Alternative flow: [A1]: Actor clicks “Cancel” then system close popup, nothing changes
Exception flow: [E1]” The system display warning popup “You need to create the POSs before!”
[E2]: The system display Error Message “Invalid data”
4.1.14 UC 14: Update pos admin account
Objective: Allow actor update pos admin account
Pre-condition: The actor has successfully logged in, the actor is on the Website
Post-condition: The actor updated successfully pos admin account
Main flow: (1) Actor clicks person management menu on left-bar
(2) The system displays the user list
(3) The actor clicks edit button on the item which they want to update
(4) The system open popup update user account
(5) The actor can edit (name, username, password, pos, phone number, email) and click
Alternative flow: [A1]: Actor clicks “Cancel” then system close popup, nothing changes
Exception flow: [E1]: The system display Error Message “Invalid data”
4.1.15 UC 15: Delete pos admin account
Objective: Allow actor delete pos admin account
Pre-condition: The actor has successfully logged in, the actor is on the Website
Actor has created at least 1 pos admin account
Post-condition: The actor deleted successfully pos admin account System display delete successfully message
Main flow: (1) Actor clicks Person management menu on left-bar
(2) The system display user list
(3) The actor click delete button inline of the item which they want to delete
(4) The system open delete user account popup
(5) The actor clicks “Delete” button (A1)
Alternative flow: [A1]: Actor clicks “Cancel” then system close popup, nothing change
Objective: Allow actor view and print receipt of the order item
Actor: Client and Client Pos Admin
Pre-condition: The actor has successfully logged in, the actor is on the Website
Post-condition: The actor view successfully the order list or print receipt of the order successfully
Main flow: (1) Access the website
(2) The system displays the menu of the store assigned for management
The store menu shows a list of orders
(3) Click on an order item
(4) The system displays the order details
Operation team functions
Objective: Allow actor to view information at homepage
Pre-condition: The actor has successfully logged in, the actor is on the Website
Basic flow: (1) The actor clicks Revenue Dashboard menu on the left bar
(2) The system displays the Revenue Dashboard screen
4.2.2 UC 18: Login For Operation Team
Objective: Allow actors logs into the system using User Name and Password
Pre-condition: The actor's account has been registered on the system
Post-condition: Successful login: Actor moves to the system's Operation Team home page and the system display message login successfully
(1) Actor accesses the login page
(2) Actor enters log id and password
(3) Actor clicks the Login button(E1) (E2)
Exception [E1]: “Log id or password are blank” notification was displayed
[E2]: “Log id or password is incorrect” notification was displayed
Objective: Allow actor update client account
Pre-condition: The actor has successfully logged in, the actor is on the Website
Post-condition: The actor updated successfully client account
Main flow: (1) Actor clicks customer management menu on left-bar
(2) The system display customer list
(3) The actor clicks view button on the item which they want to update
(4) The system open popup user detail
(5) The actor edit (name, username, password, email) and click “Update” button (A1)(E1)
Alternative flow: [A1]: Actor clicks “Cancel” then system close popup, nothing changes
Exception flow: [E1]: The system display Error Message “Invalid data”
Objective: Allow actor manage service order
Pre-condition: The actor has successfully logged in, the actor is on the Website
Post-condition: The actor viewed the service order successfully and changed status of the service order successfully
Main flow: (1) Actor clicks service order management menu on left-bar
(2) The system display service order list
(3) The actor selects the service order which they want to change status
(4) The system displays the popup “Do you want to change status of this service order?”
(5) The actor clicks “Yes” button (A1)
Alternative flow: [A1]: Actor clicks “No” then system close popup, nothing changes
Client’s customer functions
Objective: Allow actor place an order through digital menu
Post-condition: The Actor placed order successfully and the order was displayed in the order list of client
Main flow: (1) The actor uses mobile phone scan the QR code in the table
(2) The system displays the screen digital menu
(3) The actor clicks menu category
(4) The system shows the menu items belongs to category
(5) The actor clicks add button to add item to cart
(6) The actor clicks cart icon
(7) The system shows popup order detail
(8) The actor can update the quantity of the item
Alternative flow: [A1]: Actor clicks “No” then system close popup, nothing changes
Objective: Allow actor make a payment for their order
Pre-condition: The actor placed order successfully and the system navigated to payment screen
Post-condition: The Actor made payment successfully
(1) The actor click make a payment button in the payment screen
(2) The system show popup page pay pal sandbox, if actor not account in this Actor must register and enter information required
(3) After actor will sign in and pay for the service (A1) (E1)
(4) The system show message make payment successfully
(5) The system navigates payment successfully screen
Alternative flow: [A1] The actor click “Cancel” button and then the system navigates payment screen
Exception flow: [E1] The system show error message “ Made payment failed”
Database
Operation account
Table Desc Operation Account Table
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 NCK_NM VARCHAR(100) Not Null Nick Name
8 LOG_ID VARCHAR(100) Not Null Log in ID
9 PASSWORD VARCHAR(100) Not Null Password
10 EMAIL VARCHAR(100) Not Null Email Address
Service order
Table Desc Operation Account Table
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 CLIENT_RID VARCHAR(32) Not Null Client Rid
8 STATUS_CD VARCHAR(20) Not Null Status Code
9 TOTAL_PRICE DOUBLE Total Price
10 AUTO_RENEWABLE_END_DATE DATE Not Null Autorenewable End Date
Client
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 NCK_NM VARCHAR((100) Not Null Nick Name
8 FULL_NM VARCHAR((200) Not Null Full Name
9 EMAIL VARCHAR((100) Not Null Email Address
10 PHONE_NO VARCHAR((100) Phone Number
11 LOG_ID VARCHAR((100) Not Null Login ID
12 PASSWORD VARCHAR((100) Not Null Password
13 ROLE_TYPE_CD VARCHAR((20) Not Null Role Type Code
District
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 NAME VARCHAR((100) Not Null Name
8 LEVEL VARCHAR((100) Not Null Level
9 PROVINCE_RID VARCHAR((32) Not Null Province RID
Province
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 NAME VARCHAR((100) Not Null Name
8 LEVEL VARCHAR((100) Not Null Level
Point of sales
Table Name POINT OF SALES
Table Desc Point Of Sales Table
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 NAME VARCHAR((100) Not Null Name
8 DISTRICT_RID VARCHAR((32) Not Null District RID
9 STREET_NAME VARCHAR((200) Not Null Street Name
10 HOUSE_NO VARCHAR((50) Not Null House Number
11 POST_CODE VARCHAR((100) Post Code
14 CLIENT_RID VARCHAR((32) Not Null Client RID
Menu
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 NAME VARCHAR((100) Not Null Name
8 POS_RID VARCHAR((32) Not Null Point Of Sale RID
Menu Item group
Table Name MENU_ITEM_GROUP
Table Desc Menu Item Group Table
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 NAME VARCHAR((100) Not Null Name
8 MENU_RID VARCHAR((32) Not Null Menu RID
9 GROUP_TYPE VARCHAR((100) Not Null Menu Group Type
Menu Item
Table Desc Menu Item Table
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 NAME VARCHAR((100) Not Null Name
8 GROUP_RID VARCHAR((32) Not Null Group RID
9 PRICE DOUBLE Not Null Price
Seating diagram
Table Desc Seating Diagram Table
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 NAME VARCHAR((100) Not Null Name
8 POS_RID VARCHAR((32) Not Null Point Of Sale RID
9 WIDTH INT Not Null Width
10 HEIGHT INT Not Null Height
Positions
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 DIAGRAM_RID VARCHAR((32) Not Null Diagram RID
8 POS_X FLOAT Not Null Position X
9 POS_Y FLOAT Not Null Position Y
10 IS_TABLE BOOL Not Null Is Table Flag
Tables
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 POSITION_RID VARCHAR((32) Not Null Position RID
8 TABLE_NUMBER VARCHAR((50) Not Null Table Number
9 SEATING_CAPACITY INT Not Null Seating Capacity
10 STATUS_CD VARCHAR((20) Not Null Status Code
Reservation
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 TABLE_RID VARCHAR((32) Not Null Table RID
8 CUSTOMER_RID VARCHAR((32) Not Null Customer RID
9 RESERVATION_TIME DATETIME Reservation Time
11 STATUS_CD VARCHAR((20) Status Code
Customer
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 NCK_NM VARCHAR((100) Not Null Nick Name
8 FULL_NM VARCHAR((200) Not Null Full Name
9 EMAIL VARCHAR((100) Not Null Email Address
10 PHONE_NO VARCHAR((100) Phone Number
11 LOG_ID VARCHAR((100) Not Null Log ID
12 PASSWORD VARCHAR((100) Not Null Password
Order
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 TABLE_RID VARCHAR((32) Not Null Table RID
8 CUSTOMER_RID VARCHAR((32) Null Customer RID
9 TOTAL_PRICE DOUBLE 0 Total Price
10 STATUS_CD VARCHAR((20) Status Code
Order item
Table Desc Order Item Table
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 ORDER_RID VARCHAR((32) Not Null Order RID
8 MENU_ITEM_RID VARCHAR((32) Not Null Menu Item RID
9 AMOUNT INT Not Null Amount
File: 48
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
8 ALTERNATIVE_TEXT VARCHAR((255) Alternative Text
File related morph
Table Name FILE_RELATED_MORPH
Table Desc File Related Morph Table
NO Field Type Nullable Default PK/FK Comments (ENG)
1 SYS_CREATE_BY VARCHAR(32) Creator
2 SYS_MODIFY_BY VARCHAR(32) Modifier
3 SYS_CREATE_DATE DATETIME Create Date
4 SYS_MODIFY_DATE DATETIME Modify Date
5 SYS_FLAG CHAR(1) 1 Active (Active: 1 / Inactive: 0)
6 ID VARCHAR((32) Not Null ID
7 RELATED_RID VARCHAR((32) Related RID
8 RELATED_TYPE VARCHAR((255) Related Type
9 FILE_RID VARCHAR((32) File RID
User Interface
Home page
Login
Sign up
DashBoard
Tables management
Table diagram
Table detail
Menu Management Add
Menu Empty
Create Food
Food Detail
Cashier List Order Detail
Customer Categories
Customer Food
Customer Cart
Advance Account
Receipt and Credit Card
POS Management Add
POS Management Update
Person Management Add
Person Management Update
FAQ
Dashboard User
User Account Management
User Order Detail
Warning
Brand
Brand name: InnoConvenioHub (ICHub)
- Inno stands for innovation, reflecting the creative and cutting-edge aspect of the software
- Convenio highlights the convenience the software brings to store customers
- Hub represents the central point where all services, such as managing menus, orders, and payments, are streamlined
IC effectively communicates "I see," demonstrating an understanding of customer needs and fostering a user-friendly, service-oriented environment This personalized approach highlights the organization's commitment to meeting and exceeding customer expectations.