Design of management database for Mihiyo company

. The mihoyo Sales Management System was developed to adjust to the dynamic business environment and maintain a competitive edge. In the context of this era, the mihoyo Sales Management System utilizes a robust database structure to optimize sales operations. In this paper, a management database for Mihiyo company is designed. The customer module stores customer information, linked to orders, payments, and expenses. An order table tracks order details, linked to customers and products. Payment and shipment tables manage transaction and delivery information. The inventory table enables real-time monitoring of stock levels. Financial management tables record sales, payment, and expense data. User tables store information related to different user roles. The system's interface seamlessly interacts with the database, allowing users to access and update information efficiently. The reporting and analytics module analyzes data from the database, facilitating decision-making and performance evaluation. Database testing requires completing relevant test cases and achieving a robust system.


Introduction
The mihoyo Sales Management System was designed to adapt to the rapidly changing business landscape and stay competitive [1].Manual processes were inefficient, prompting the need for automation.The system streamlined sales operations, enhanced customer satisfaction, and enabled datadriven decision-making.It centralized customer information, expedited order processing, and provided real-time inventory monitoring [2].Financial management capabilities ensured accurate tracking for analysis and informed decision-making.
One of the core features of the system is the customer management module, which enables sales representatives to maintain a comprehensive database of customer information [3].This module allows for efficient tracking of customer interactions, purchase history, and preferences, enabling personalized and targeted sales approaches.By understanding their customers better, mihoyo sales representatives can provide tailored solutions and build stronger relationships, ultimately driving customer satisfaction and loyalty.
Another crucial component of the mihoyo Sales Management System is the order management module.This module facilitates seamless order processing, tracking, and fulfillment.Sales representatives can easily create and manage orders, while the system automatically updates order status, manages payments, and tracks shipment details [4].This integration ensures accurate and timely order management, resulting in improved customer satisfaction and faster order fulfillment cycles.
Database design has undergone continuous development and evolution in the field of computer science.Early relational databases such as IBM's DB2 and Oracle adopted tabular structures and SQL query language.With the growth of data volume and changing application requirements, object-oriented databases, NoSQL databases, and Big Data technologies emerged.Object-oriented databases like MongoDB allow storing and accessing data in an object-oriented manner, suitable for complex data models.NoSQL databases like Cassandra and Redis emphasize high performance and scalability, suited for handling unstructured big data [2,5].Recently, emerging technologies such as graph databases and time-series databases have emerged for processing relational and time-based data.In summary, database design continues to evolve in various scenarios to meet changing needs and technological challenges [1].

Introduction to Database
The following figure 1 is a functional structure diagram, which includes four system modules.

Entities and Relationships in the Database:
Customers -This entity represents the individuals or organizations that purchase mihoyo products or services.It stores customer information such as name, contact details, and purchase history.
Products -This entity contains details about the various products offered by mihoyo, including product names, descriptions, specifications, and prices.
Orders -This entity records information about customer orders, including the products purchased, order date, payment details, and order status.
Suppliers -This entity stores information about the suppliers from whom mihoyo sources components and materials for its products.
Employees -This entity represents mihoyo's workforce and includes details such as employee names, contact information, job roles, and department information.
Inventory -This entity tracks the stock levels of mihoyo's products, helping the company manage its supply chain and ensure product availability.
Sales -This entity captures sales-related data, including transaction details, quantities sold, revenue generated, and associated customer and product information.
Payments -This entity records payment details for completed orders, including payment methods, transaction IDs, and payment dates [3].
Shipment -This entity tracks shipment details, such as tracking numbers, delivery dates, and the associated order information [1].

Normalization First Normal Form (1NF):
Each table has a primary key (PK) that uniquely identifies each record.All attributes are atomic, meaning they cannot be further divided.

Second Normal Form (2NF):
The Orders table has a composite primary key (Order_ID, Customer_ID).We can remove the Customer_ID from the Orders    • Check the current stock level for a specific product, (Figure 6)

Conclusion
By implementing this system, mihoyo successfully streamlined sales operations, leading to improved efficiency and increased customer satisfaction.The centralization of customer information allowed for a more comprehensive understanding of customers' preferences and behaviors, enabling personalized experiences and targeted marketing strategies.Furthermore, the system expedited order processing, reducing the time from order placement to delivery.Its real-time inventory monitoring feature ensured optimal stock levels, minimizing instances of stockouts and improving fulfillment rates.The automation of these processes resulted in enhanced operational efficiency and a smoother overall customer experience.The financial management capabilities of the Sales Management System provided accurate tracking of payments, transactions, and revenues, facilitating effective financial analysis and informed decision-making.This enabled mihoyo to identify trends, make data-driven business decisions, and allocate resources more efficiently.
Looking forward, the mihoyo Sales Management System has the potential for further growth and improvement.With ongoing advancements in technology, the system can be upgraded to incorporate additional features such as predictive analytics for demand forecasting, automated supplier management, and integration with external e-commerce platforms.Embracing emerging technologies, such as artificial intelligence and machine learning, can also enhance the system's capabilities in areas like customer segmentation, personalized recommendations, and fraud detection.In conclusion, the mihoyo Sales Management System has proven to be a valuable asset in adapting to the dynamic business landscape.Its automation of key processes, centralization of customer information, and data-driven decision-making capabilities have contributed to improved operational efficiency and customer satisfaction.Constant innovation and integration of new technologies will be crucial to staying ahead in the market and achieving long-term success.

Table 1
In this section, this work lists databases as an example to show how to create the database in MySQL platform ( table and create a separate table for Customer_Order relationship to resolve partial dependency.Customer_Order (Customer_ID PK, Order_ID PK) The Sales table has a composite primary key (Payment_ID, Amount).We can remove the Amount from the Sales table and create a separate table for Payment_Sale relationship to resolve partial dependency.Payment_Sale (Payment_ID PK, Transaction_ID) Third Normal Form (3NF): The Orders table has a transitive dependency on the Customer_ID attribute, as OrderDate and Status depend on Customer_ID.We can create a separate table for Customer details to resolve this.Customers (Customer_ID PK, Name, ContactInfo, PurchaseDate) The Orders table has a transitive dependency on the Payment_ID attribute, as OrderDate and Status depend on Payment_ID.We can create a separate table for Payment details to resolve this.Payments (Payment_ID PK, Amount)6.SQL command for creating database