In the era of network information, many softwares have been developed, giving users a lot of choices, and people are increasingly pursuing more personalized needs. In this context, supermarkets can only be user-oriented, organize production in small batches according to varieties, and use continuous product innovation as the most important means of competition for supermarkets.
The system adopts a B/S structure, and all business modules adopt a browser interaction mode. MySQL is selected as the database of the system, and My eclipse is selected as the development tool for system design. It has basically realized the main functional modules that a digital supermarket management system should have. This system has two functional modules: administrator and user. It realizes administrator: homepage, website management (carousel chart, supermarket announcement) personnel management (administrator, member user) , employee users) module management (warehouse information, suppliers, product types, product information, product removal, warehousing information, order information, employee management, salary information, employee sign-in, sales information, message feedback) personal management and other operations.
After testing the system, the program logic and code were improved. At the same time, it is ensured that all programs in the system can run normally, all functions can be operated, and the system has a good operating experience, achieving a win-win situation for administrators and users.
Keywords: digital supermarket management system; Mysql;
In the era of network information, many software have been developed, which brings users a lot of choices, and people are increasingly pursuing more personalized needs. Under this background, supermarkets can only be user-oriented, organize production in small quantities according to varieties, and take the continuous innovation of products as the most important means of competition.
The system adopts B / S structure, adopts browser interaction mode for all business modules, selects MySQL as the database of the system, and selects my eclipse as the development tool to design the system. The main functional modules of the community online supermarket shopping system are basically realized. The system has two functional modules: administrator and user Site management (rotation chart, bulletin board) user management (administrator, registered user) content management (message board, message classification, good material information, information classification) mall management (mall center, classification list, order list) more management (commodity allocation, commodity inventory, purchase warehousing, sales outbound, commodity return, user points, after-sales application, commodity loss report) Users: home page, message board, order list, user points, after-sales application and other operations.
After testing the system, the program logic and code are improved. At the same time, ensure that all programs in the system can run normally, all functions can be operated, and the system has a good operation experience, which realizes a win-win situation for administrators and users.
Key words: online supermarket shopping system; Mysql；
Table of contents
Chapter 2 Technology and Principles
2.1 Development technical description
Chapter 3 Requirements Analysis
3.2 System feasibility analysis
3.3 Project design goals and principles
Chapter 5 System Implementation
Chapter 1 Preface
1.1 Research background
The traditional supermarket management method is carried out offline. Due to the difference in product structure, users need to go offline for actual experience, which has great space and time constraints. With the continuous popularization of product types and the transparency of their performance and modules, more and more people are becoming interested in online management for various reasons. The traditional management model can no longer meet people's needs.
The emergence of the Internet has brought about the rapid development of the network again, and people's lives have undergone earth-shaking changes. People can enjoy the convenience and speed brought by the Internet anytime and anywhere, and all aspects of their life and work needs can be realized on the Internet, such as learning, management, etc. In other words, the Internet has become the most direct, convenient and easiest access point for people at present.
In today's world, with the rapid development of the Internet, how to use the Internet to create a simpler and more efficient life is our first priority. Websites related to supermarket information management are needed. On the one hand, administrators can timely update and informatize supermarket information, and can easily obtain the management status of each brand of merchandise. On the other hand, users can use the Internet to view supermarket related information more intuitively. Compared with traditional management methods, users can purchase more easily and the system operates more accurately. This is a potential trend that may effectively accelerate the popularity of supermarkets.
1.2 Research status
After investigation, it has been found that the pace of life of modern people is accelerating and the pressure of life is gradually increasing. People can use the functions of smart products to bring convenience to people. As people's online management continues to increase, more and more people are beginning to has joined the trend of online management, but our country's online product management information management effect is low, and the error rate is also high. Therefore, everyone is looking for a more professional product management system.
With the continuous emergence of digital supermarket management systems and the increasing needs of users, the digital supermarket management system has also continued to grow. This system is mainly based on the actual needs of users and managers to facilitate users to use the Internet to understand the digital supermarket management system. , comparison, and even trading. At the same time, managers can manage the actual needs of users and all understanding and management of each brand's products through this system. The main purpose of designing this system is to facilitate people's horizontal comparison of various types of goods, help people save time, and reduce managers' capital investment.
1.3 System development goals
For the front-end design of the website, it is necessary to ensure that the main interface is clean and orderly, can catch people's eyes, and will not cause visual fatigue. More importantly, it should give people an intuitive feeling that is easy to operate, so as to retain users to use it. , increasing the duration of the three-point heat. In the background design of the system, very simple and effective technology should be adopted to facilitate development and future maintenance. Not only do we need to ensure that all functions can meet the needs of users, but users must also be able to take the initiative to achieve the desired operations through the website, and managers can simply understand and manage user needs through the website. To achieve this goal, the following goals are proposed:
(1) Users can view the latest product information and related information in real time;
(2) Users can compare the information of major products and choose the products they are more satisfied with;
(3) Users can communicate with each other about their purchasing experience through the forum;
(4) Administrators can conveniently manage various information on the front-end web page in the background;
(5) Administrators can easily query and summarize users’ usage status.
Chapter 2 Technology and Principles
2.1Opening technique description
The front-end part of this system is developed based on the MVVM model, using the B/S mode, and the back-end part is developed based on the Java springboot framework.
Front-end part: The front-end framework uses the popular progressive JavaScript framework Vue.js. Use Vue-Router and Vuex to realize dynamic routing and global state management, Ajax to realize front-end and back-end communication, Element UI component library to quickly prototype the page, and the project front-end to achieve responsiveness through grid layout, which can be adapted to PC, tablet, mobile phone, etc. Perfect layout display for different screen sizes.
Back-end part: Use springboot as the development framework, and integrate MyBatis, Redis and other related technologies.
2.2 JAVA technology
The Java language is currently the most commonly used language program, and its code is open source and can be used by any software developer. It has already had a profound impact on the history of human computer programming language development. Therefore, the Java language is very mature. It is a good choice to apply it to the development of our system, and because it is common, most people can operate it.
The Java language has a variety of features. It is very simple to write code and has a variety of writing methods. It is very object-oriented, and it does not have any requirements for the platform it is used. All platforms can be used. Operation, its safety performance is also very high, so it is very suitable for the development of this system.
Java does not have any platform requirements and can be run on any platform. It can start running without the need to use other language editors to edit the code. This is very good, not only the ones we are using It is more convenient and can be implemented without the help of other programs, so it can save our development costs. Moreover, the program code edited by Java can be used directly without recompiling, so it is very convenient. Moreover, the application of the program does not require professional skills to run, which provides great feasibility for software development.
2.3 MySQL database
The mysql database has many advantages. It is very simple to operate. You only need to write a small piece of code to achieve the corresponding functions, and the written code can be used on any platform. There are no requirements for the use of the platform. Therefore Any software developer can use the mysql database to develop and design the system. At the same time, it can also save a lot of overhead for software development. The mysql database has large storage capacity and simple operation. It is so powerful that it is completely possible to use it as the data storage of this system.
The mysq database is an open architecture that can be used by any software developer. With the continuous development of computer networks, the MySQL database is constantly improving in terms of functionality and is more suitable for the development of all systems. We are improving the database When operating, it is very simple and easy to use. We only need to write a small piece of code to achieve the corresponding function, and the edited code can be used on any platform without the need for secondary compilation. Because the MySQL database has many of the above advantages, we use it as the first choice for database application in system development. Because its size is very small and the cost of development is also very low, it is loved by many software developers and is more popular. Most of them are used in the opening of the system, so this system also uses the MySQL database to store and edit all data.
2.4 B/S structure
The B/S (browser/server) structure is currently the most commonly used structure model. It can make system development simpler, easier to operate, and can also be maintained. When using this structure, you only need to install a database in your computer and some commonly used browsers. The browser will connect the information with the database, which can realize many functions. The B/S structure can be used directly, and the B/S structure greatly reduces the maintenance work during use. Based on B/S software, all databases are independent of each other, so they are very safe. Because based on the B/S structure, you can clearly see the business being processed by the system, and allow managers to make decisions in a timely manner, thus avoiding losses to the supermarket. The basic feature of the B/S structure is the centralized management model. After users use the system to generate data, the data can be stored in the system's database for future use, thus meeting all people's needs.
Figure 2-1 Three-layer structure diagram of B/S mode
Chapter 3 Requirements Analysis
3.1 Requirements analysis
In the process of developing the system, it is particularly important to investigate the functional demands of users and perform demand analysis on the functions that need to exist. It is of practical significance to the development of the system. The design of the digital supermarket management system is based on the analysis of user needs and the combination of Carry out development research based on the actual situation, create a complete basic framework for all user needs, and then complete and implement it step by step. Requirements analysis can provide a goal for system development. Only by developing and designing according to this goal can complete development be carried out. Only in this way can the designed system be meaningful to use, survive in the fiercely competitive software market, and truly help People solve problems and improve practical efficiency.
3.2 System feasibility analysis
This system uses the most widely used programs for technical support. The main technical support is the Java language. As a fairly mature language program, it plays a large role in many software developments. Moreover, the program edited in Java language can be run directly without the need to use other translators for translation. So it is completely feasible in terms of technology.
The original intention of developing this project is to save money, because all the processes of system development are developed by me, and the technologies used in the development process are also common and easy to operate on the market, so there is no need to hire professionals. Funds were used to develop the system, and I also learned more knowledge during the project development process. The software developed can be downloaded for free on the Internet and does not have high requirements for computer software and hardware. Therefore, this project is very affordable and completely feasible in terms of economy.
Operational feasibility is the usability of the system. Whether a system is easy to operate determines the usability of the system. I design the operation of the system in a concise and easy-to-understand manner. The entire menu interface of the operation is neat and orderly. The functions are arranged in an orderly manner, and there will be no overlap or need for conversion. Users can directly operate whatever operations they want, so anyone can operate the system, and no relevant professional skills are required. It is much easier to operate.
3.3 Project design goals and principles
1. Basic requirements for digital supermarket management system
(1) Functional requirements: Administrators can view and manage all products, manage products, view management status in a timely manner, and view and manage messages and other functional modules.
(2) Performance: Because there is a lot of information that needs to be stored in supermarket management, there are great requirements for the storage capacity of the system. The support of a powerful database is needed to ensure that all information can be stored safely and stably.
(3) Security and confidentiality requirements: Users must pass the administrator's review before they can enter the system.
(4) Environmental requirements: Supports the use of multiple operating systems such as Windows series and Vista systems.
2. Development goals
The main development goals of the digital supermarket management system are as follows:
(1) Users can view the latest product information and related information in real time;
(2) Users can compare the information of major products and choose the products they are more satisfied with;
(3) Users can communicate with each other about their purchase experience through messages;
(4) Administrators can conveniently manage various information on the front-end web page in the background;
3. Design principles
This digital supermarket management system uses SSM technology and Mysql database development to fully ensure system stability and integrity.
(1) System response efficiency: Since it is a digital supermarket management system, the response efficiency of the system needs to be very high and it can support many people using the system at the same time.
(2) The interface is simple and clear: the system interface should be simple and orderly, and all functions should be clear at a glance.
(3) High storage: Because it is a digital supermarket management system, the database requirements are relatively strict, and a lot of information is entered, and it is rich and complex. This requires a powerful database to store more data and ensure data. timeliness.
(4) Ease of learning: The design of the system must be simple so that people can use it very easily.
(5) Stability requirements: The system must remain stable during use and avoid lags, blurs, etc.
(6) Stability: Since it is a digital supermarket management system, the system operation must be very stable.
3.4 System process analysis
Users need to have their own account and password, and they must be correct, so that they can successfully log in to the system. After entering the website, users can check various products by themselves. At the end of the details page of the product they are satisfied with, they can directly choose to purchase. The specific process is shown in Figure 3-1 below:
Figure 3-1 User operation flow chart
In order to ensure the security of the system, if you want to use this system to manage system information, you must first log in to the system. The specific login flow chart is shown in Figure 3-2:
Figure 3-2 System operation flow chart
Chapter 4 Framework design
4.1 System architecture
The structure of the digital supermarket management system is shown in Figure 4-1:
Figure 4-1 System structure
Login system structure diagram, as shown in Figure 4-2:
Figure 4-2 Login structure diagram
System structure diagram, as shown in Figure 4-3:
Figure 4-3 System structure diagram
4.2 Database entity design
The function of the database is to store and manage all data in the system. All data can be stored in the database in real time, making it convenient for users to use. Moreover, the data in all databases should also be shared to a certain extent. Any system can use some data, and at the same time, it should maintain a certain degree of independence. The data in each database has strong security and can be used It is well stored in the database. This data cannot be viewed and used without identity verification. The design of the database needs to clarify the connection between each entity. The E-R diagram of the system is shown below:
The administrator entity mainly stores management information including serial number, user name, and password attributes. The administrator information attribute diagram is shown in Figure 4-4.
Figure 4-4 Administrator information entity attribute diagram
Product information management mainly includes attributes such as index, product number, warehouse name, product classification, product name, supplier, product picture, quantity, product price, etc. The product information management attribute diagram is shown in Figure 4-5.
Figure 4-5 Product information management entity attribute diagram
The warehouse information management entity attributes mainly include attributes such as index, warehouse name, location, person in charge, contact number, area, etc. The warehouse information management entity attribute diagram is shown in Figure 4-6.
Figure 4-6 Warehouse information management entity attributes
4.3 Database table design
When the digital supermarket management system is running, the database must ensure its independence. Select the corresponding setting options for which part of the data you want, and the corresponding data will be displayed in the form of a table. When this function is set, it will connect to the database and the corresponding data source will pop up in the dialog box.
Table access_token (login access duration)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
token_id |
int |
10 |
0 |
N |
AND |
Temporary access badge ID |
|
| 2 |
token |
varchar |
64 |
0 |
AND |
N |
temporary access badge |
|
| 3 |
info |
text |
65535 |
0 |
AND |
N |
||
| 4 |
maxage |
int |
10 |
0 |
N |
N |
2 |
Maximum lifespan: Default 2 hours |
| 5 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 6 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
user ID: |
Table auth (user rights management)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
auth_id |
int |
10 |
0 |
N |
AND |
Authorization ID: |
|
| 2 |
user_group |
varchar |
64 |
0 |
AND |
N |
user group: |
|
| 3 |
mod_name |
varchar |
64 |
0 |
AND |
N |
Module name: |
|
| 4 |
table_name |
varchar |
64 |
0 |
AND |
N |
Table Name: |
|
| 5 |
page_title |
varchar |
255 |
0 |
AND |
N |
page title: |
|
| 6 |
path |
varchar |
255 |
0 |
AND |
N |
Routing path: |
|
| 7 |
position |
varchar |
32 |
0 |
AND |
N |
Location: |
|
| 8 |
mode |
varchar |
32 |
0 |
N |
N |
_blank |
Jump method: |
| 9 |
add |
tinyint |
3 |
0 |
N |
N |
1 |
Is it possible to add: |
| 10 |
of the |
tinyint |
3 |
0 |
N |
N |
1 |
Can it be deleted: |
| 11 |
set |
tinyint |
3 |
0 |
N |
N |
1 |
Whether it can be modified: |
| 12 |
get |
tinyint |
3 |
0 |
N |
N |
1 |
Is it possible to view: |
| 13 |
field_add |
text |
65535 |
0 |
AND |
N |
Add fields: |
|
| 14 |
field_set |
text |
65535 |
0 |
AND |
N |
Modify fields: |
|
| 15 |
field_get |
text |
65535 |
0 |
AND |
N |
Query fields: |
|
| 16 |
table_nav_name |
varchar |
500 |
0 |
AND |
N |
Cross-table navigation name: |
|
| 17 |
table_nav |
varchar |
500 |
0 |
AND |
N |
Cross-table navigation: |
|
| 18 |
option |
text |
65535 |
0 |
AND |
N |
Configuration: |
|
| 19 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 20 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
collect_id |
int |
10 |
0 |
N |
AND |
Collection ID: |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Collector ID: |
| 3 |
source_table |
varchar |
255 |
0 |
AND |
N |
Source table: |
|
| 4 |
source_field |
varchar |
255 |
0 |
AND |
N |
Source field: |
|
| 5 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
| 6 |
title |
varchar |
255 |
0 |
AND |
N |
title: |
|
| 7 |
img |
varchar |
255 |
0 |
AND |
N |
Cover: |
|
| 8 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
comment_id |
int |
10 |
0 |
N |
AND |
Comment ID: |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Commenter ID: |
| 3 |
reply_to_id |
int |
10 |
0 |
N |
N |
0 |
Reply comment ID: empty is 0 |
| 4 |
content |
longtext |
2147483647 |
0 |
AND |
N |
content: |
|
| 5 |
nickname |
varchar |
255 |
0 |
AND |
N |
Nick name: |
|
| 6 |
avatar |
varchar |
255 |
0 |
AND |
N |
Avatar address: [0,255] |
|
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 9 |
source_table |
varchar |
255 |
0 |
AND |
N |
Source table: |
|
| 10 |
source_field |
varchar |
255 |
0 |
AND |
N |
Source field: |
|
| 11 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
Table employee_management (employee management)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
employee_management_id |
int |
10 |
0 |
N |
AND |
Employee management ID |
|
| 2 |
number |
varchar |
64 |
0 |
AND |
N |
serial number |
|
| 3 |
employee_user |
int |
10 |
0 |
AND |
N |
0 |
employee user |
| 4 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 5 |
position |
varchar |
64 |
0 |
AND |
N |
Position |
|
| 6 |
base_pay |
int |
10 |
0 |
AND |
N |
0 |
Basic wage |
| 7 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 8 |
limit_times |
int |
10 |
0 |
N |
N |
0 |
Limit the number of times |
| 9 |
limit_type |
tinyint |
4 |
0 |
N |
N |
1 |
Limit type 1-times per day, 2-total times |
| 10 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 11 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table employee_sign_in (employee sign-in)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
employee_sign_in_id |
int |
10 |
0 |
N |
AND |
Employee sign-in ID |
|
| 2 |
number |
varchar |
64 |
0 |
AND |
N |
serial number |
|
| 3 |
employee_user |
int |
10 |
0 |
AND |
N |
0 |
employee user |
| 4 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 5 |
position |
varchar |
64 |
0 |
AND |
N |
Position |
|
| 6 |
sign_in_date |
date |
10 |
0 |
AND |
N |
Check-in date |
|
| 7 |
examine_state |
varchar |
16 |
0 |
N |
N |
Not reviewed |
Approval Status |
| 8 |
examine_reply |
varchar |
16 |
0 |
AND |
N |
moderation reply |
|
| 9 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 10 |
user_id |
int |
10 |
0 |
N |
N |
0 |
User ID |
| 11 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 12 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table employee_user (employee user)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
employee_user_id |
int |
10 |
0 |
N |
AND |
Employee User ID |
|
| 2 |
employee_no |
varchar |
64 |
0 |
N |
N |
employee ID |
|
| 3 |
employee_name |
varchar |
64 |
0 |
AND |
N |
employee's name |
|
| 4 |
gender |
varchar |
64 |
0 |
AND |
N |
gender |
|
| 5 |
examine_state |
varchar |
16 |
0 |
N |
N |
passed |
Approval Status |
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
User ID |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
Table goods_off_the_shelf (products off the shelf)
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
goods_off_the_shelf_id |
int |
10 |
0 |
N |
AND |
Product removal ID |
|
| 2 |
serial_number |
varchar |
64 |
0 |
N |
N |
serial number |
|
| 3 |
article_no |
varchar |
64 |
0 |
AND |
N |
Product Number |
|
| 4 |
trade_name |
varchar |
64 |
0 |
AND |
N |
product name |
|
| 5 |
product_cover |
varchar |
255 |
0 |
AND |
N |
Product cover |
|
| 6 |
commodity_type |
varchar |
64 |
0 |
AND |
N |
Product Types |
|
| 7 |
specification_unit |
varchar |
64 |
0 |
AND |
N |
Specification unit |
|
| 8 |
responsible_employees |
int |
10 |
0 |
AND |
N |
0 |
Responsible employee |
| 9 |
item_pricing |
int |
10 |
0 |
AND |
N |
0 |
Commodity price |
| 10 |
off_shelf_quantity |
int |
10 |
0 |
AND |
N |
0 |
Quantity removed from shelves |
| 11 |
recommend |
int |
10 |
0 |
N |
N |
0 |
Intelligent Recommendation |
| 12 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
creation time |
| 13 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time |
| serial number |
name |
type of data |
length |
Decimal places |
Allow null values |
primary key |
default value |
illustrate |
| 1 |
hits_id |
int |
10 |
0 |
N |
AND |
Like ID: |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
Liked by: |
| 3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Creation time: |
| 4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
Update time: |
| 5 |
source_table |
varchar |
255 |
0 |
AND |
N |
Source table: |
|
| 6 |
source_field |
varchar |
255 |
0 |
AND |
N |
Source field: |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
Source ID: |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
member_users_id |
int |
10 |
0 |
N |
Y |
会员用户ID |
|
| 2 |
user_name |
varchar |
64 |
0 |
Y |
N |
用户姓名 |
|
| 3 |
gender |
varchar |
64 |
0 |
Y |
N |
性别 |
|
| 4 |
membership_certificate |
varchar |
255 |
0 |
Y |
N |
会员证明 |
|
| 5 |
examine_state |
varchar |
16 |
0 |
N |
N |
未审核 |
审核状态 |
| 6 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 7 |
user_id |
int |
10 |
0 |
N |
N |
0 |
用户ID |
| 8 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 9 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
message_feedback_id |
int |
10 |
0 |
N |
Y |
留言反馈ID |
|
| 2 |
message_user |
int |
10 |
0 |
Y |
N |
0 |
留言用户 |
| 3 |
user_name |
varchar |
64 |
0 |
Y |
N |
用户姓名 |
|
| 4 |
feedback_content |
text |
65535 |
0 |
N |
N |
反馈内容 |
|
| 5 |
message_date |
date |
10 |
0 |
Y |
N |
留言日期 |
|
| 6 |
examine_state |
varchar |
16 |
0 |
N |
N |
未审核 |
审核状态 |
| 7 |
examine_reply |
varchar |
16 |
0 |
Y |
N |
审核回复 |
|
| 8 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 9 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
notice_id |
mediumint |
8 |
0 |
N |
Y |
公告id： |
|
| 2 |
title |
varchar |
125 |
0 |
N |
N |
标题： |
|
| 3 |
content |
longtext |
2147483647 |
0 |
Y |
N |
正文： |
|
| 4 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
order_information_id |
int |
10 |
0 |
N |
Y |
订单信息ID |
|
| 2 |
order_number |
varchar |
64 |
0 |
Y |
N |
订单号 |
|
| 3 |
serial_number |
varchar |
64 |
0 |
Y |
N |
序号 |
|
| 4 |
trade_name |
varchar |
64 |
0 |
Y |
N |
商品名称 |
|
| 5 |
product_cover |
varchar |
255 |
0 |
Y |
N |
商品封面 |
|
| 6 |
commodity_type |
varchar |
64 |
0 |
Y |
N |
商品类型 |
|
| 7 |
specification_unit |
varchar |
64 |
0 |
Y |
N |
规格单位 |
|
| 8 |
responsible_employees |
int |
10 |
0 |
Y |
N |
0 |
负责员工 |
| 9 |
member_users |
int |
10 |
0 |
Y |
N |
0 |
会员用户 |
| 10 |
item_pricing |
int |
10 |
0 |
Y |
N |
0 |
商品单价 |
| 11 |
purchase_quantity |
int |
10 |
0 |
Y |
N |
0 |
购买数量 |
| 12 |
order_date |
date |
10 |
0 |
Y |
N |
下单日期 |
|
| 13 |
examine_state |
varchar |
16 |
0 |
N |
N |
未审核 |
审核状态 |
| 14 |
examine_reply |
varchar |
16 |
0 |
Y |
N |
审核回复 |
|
| 15 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 16 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 17 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
praise_id |
int |
10 |
0 |
N |
Y |
点赞ID： |
|
| 2 |
user_id |
int |
10 |
0 |
N |
N |
0 |
点赞人： |
| 3 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 4 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
| 8 |
status |
bit |
1 |
0 |
N |
N |
1 |
点赞状态:1为点赞，0已取消 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
product_information_id |
int |
10 |
0 |
N |
Y |
商品信息ID |
|
| 2 |
serial_number |
varchar |
64 |
0 |
Y |
N |
序号 |
|
| 3 |
article_no |
varchar |
64 |
0 |
Y |
N |
商品编号 |
|
| 4 |
trade_name |
varchar |
64 |
0 |
Y |
N |
商品名称 |
|
| 5 |
product_cover |
varchar |
255 |
0 |
Y |
N |
商品封面 |
|
| 6 |
commodity_type |
varchar |
64 |
0 |
Y |
N |
商品类型 |
|
| 7 |
specification_unit |
varchar |
64 |
0 |
Y |
N |
规格单位 |
|
| 8 |
responsible_employees |
int |
10 |
0 |
Y |
N |
0 |
负责员工 |
| 9 |
number_of_shelves |
int |
10 |
0 |
Y |
N |
0 |
上架数量 |
| 10 |
item_pricing |
int |
10 |
0 |
Y |
N |
0 |
商品单价 |
| 11 |
product_introduction |
longtext |
2147483647 |
0 |
Y |
N |
商品介绍 |
|
| 12 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 13 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 14 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
product_type_id |
int |
10 |
0 |
N |
Y |
商品类型ID |
|
| 2 |
product_type |
varchar |
64 |
0 |
Y |
N |
商品类型 |
|
| 3 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 4 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 5 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
salary_information_id |
int |
10 |
0 |
N |
Y |
工资信息ID |
|
| 2 |
employee_user |
int |
10 |
0 |
Y |
N |
0 |
员工用户 |
| 3 |
employee_name |
varchar |
64 |
0 |
Y |
N |
员工姓名 |
|
| 4 |
position |
varchar |
64 |
0 |
Y |
N |
职位 |
|
| 5 |
base_pay |
int |
10 |
0 |
Y |
N |
0 |
基本工资 |
| 6 |
achievement_bonus |
int |
10 |
0 |
Y |
N |
0 |
绩效奖金 |
| 7 |
full_attendance_bonus |
int |
10 |
0 |
Y |
N |
0 |
全勤奖金 |
| 8 |
penalty_amount |
int |
10 |
0 |
Y |
N |
0 |
惩罚金额 |
| 9 |
wages_payable |
varchar |
64 |
0 |
Y |
N |
应发工资 |
|
| 10 |
release_date |
date |
10 |
0 |
Y |
N |
发放日期 |
|
| 11 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 12 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 13 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
sales_information_id |
int |
10 |
0 |
N |
Y |
销售信息ID |
|
| 2 |
order_number |
varchar |
64 |
0 |
N |
N |
订单号 |
|
| 3 |
serial_number |
varchar |
64 |
0 |
Y |
N |
序号 |
|
| 4 |
trade_name |
varchar |
64 |
0 |
Y |
N |
商品名称 |
|
| 5 |
product_cover |
varchar |
255 |
0 |
Y |
N |
商品封面 |
|
| 6 |
commodity_type |
varchar |
64 |
0 |
Y |
N |
商品类型 |
|
| 7 |
specification_unit |
varchar |
64 |
0 |
Y |
N |
规格单位 |
|
| 8 |
responsible_employees |
int |
10 |
0 |
Y |
N |
0 |
负责员工 |
| 9 |
member_users |
int |
10 |
0 |
Y |
N |
0 |
会员用户 |
| 10 |
item_pricing |
int |
10 |
0 |
Y |
N |
0 |
商品单价 |
| 11 |
purchase_quantity |
int |
10 |
0 |
Y |
N |
0 |
购买数量 |
| 12 |
discount |
int |
10 |
0 |
Y |
N |
0 |
折扣 |
| 13 |
purchase_amount |
varchar |
64 |
0 |
Y |
N |
购买金额 |
|
| 14 |
payment_date |
date |
10 |
0 |
Y |
N |
支付日期 |
|
| 15 |
pay_state |
varchar |
16 |
0 |
N |
N |
未支付 |
支付状态 |
| 16 |
pay_type |
varchar |
16 |
0 |
Y |
N |
支付类型: 微信、支付宝、网银 |
|
| 17 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 18 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 19 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
slides_id |
int |
10 |
0 |
N |
Y |
轮播图ID： |
|
| 2 |
title |
varchar |
64 |
0 |
Y |
N |
标题： |
|
| 3 |
content |
varchar |
255 |
0 |
Y |
N |
内容： |
|
| 4 |
url |
varchar |
255 |
0 |
Y |
N |
链接： |
|
| 5 |
img |
varchar |
255 |
0 |
Y |
N |
轮播图： |
|
| 6 |
hits |
int |
10 |
0 |
N |
N |
0 |
点击量： |
| 7 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 8 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
supplier_id |
int |
10 |
0 |
N |
Y |
供应商ID |
|
| 2 |
supplier_name |
varchar |
64 |
0 |
Y |
N |
供应商名称 |
|
| 3 |
supplier_telephone |
varchar |
16 |
0 |
Y |
N |
供应商电话 |
|
| 4 |
address |
varchar |
64 |
0 |
Y |
N |
地址 |
|
| 5 |
person_in_charge |
varchar |
64 |
0 |
Y |
N |
负责人 |
|
| 6 |
mobile_phone_of_responsible_person |
varchar |
16 |
0 |
Y |
N |
负责人手机 |
|
| 7 |
product_details |
longtext |
2147483647 |
0 |
Y |
N |
产品详情 |
|
| 8 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 9 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
upload_id |
int |
10 |
0 |
N |
Y |
上传ID |
|
| 2 |
name |
varchar |
64 |
0 |
Y |
N |
文件名 |
|
| 3 |
path |
varchar |
255 |
0 |
Y |
N |
访问路径 |
|
| 4 |
file |
varchar |
255 |
0 |
Y |
N |
文件路径 |
|
| 5 |
display |
varchar |
255 |
0 |
Y |
N |
显示顺序 |
|
| 6 |
father_id |
int |
10 |
0 |
Y |
N |
0 |
父级ID |
| 7 |
dir |
varchar |
255 |
0 |
Y |
N |
文件夹 |
|
| 8 |
type |
varchar |
32 |
0 |
Y |
N |
文件类型 |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
user_id |
mediumint |
8 |
0 |
N |
Y |
用户ID：[0,8388607]用户获取其他与用户相关的数据 |
|
| 2 |
state |
smallint |
5 |
0 |
N |
N |
1 |
账户状态：[0,10](1可用|2异常|3已冻结|4已注销) |
| 3 |
user_group |
varchar |
32 |
0 |
Y |
N |
所在用户组：[0,32767]决定用户身份和权限 |
|
| 4 |
login_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
上次登录时间： |
| 5 |
phone |
varchar |
11 |
0 |
Y |
N |
手机号码：[0,11]用户的手机号码，用于找回密码时或登录时 |
|
| 6 |
phone_state |
smallint |
5 |
0 |
N |
N |
0 |
手机认证：[0,1](0未认证|1审核中|2已认证) |
| 7 |
username |
varchar |
16 |
0 |
N |
N |
用户名：[0,16]用户登录时所用的账户名称 |
|
| 8 |
nickname |
varchar |
16 |
0 |
Y |
N |
昵称：[0,16] |
|
| 9 |
password |
varchar |
64 |
0 |
N |
N |
密码：[0,32]用户登录所需的密码，由6-16位数字或英文组成 |
|
| 10 |
|
varchar |
64 |
0 |
Y |
N |
邮箱：[0,64]用户的邮箱，用于找回密码时或登录时 |
|
| 11 |
email_state |
smallint |
5 |
0 |
N |
N |
0 |
邮箱认证：[0,1](0未认证|1审核中|2已认证) |
| 12 |
avatar |
varchar |
255 |
0 |
Y |
N |
头像地址：[0,255] |
|
| 13 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
group_id |
mediumint |
8 |
0 |
N |
Y |
用户组ID：[0,8388607] |
|
| 2 |
display |
smallint |
5 |
0 |
N |
N |
100 |
显示顺序：[0,1000] |
| 3 |
name |
varchar |
16 |
0 |
N |
N |
名称：[0,16] |
|
| 4 |
description |
varchar |
255 |
0 |
Y |
N |
描述：[0,255]描述该用户组的特点或权限范围 |
|
| 5 |
source_table |
varchar |
255 |
0 |
Y |
N |
来源表： |
|
| 6 |
source_field |
varchar |
255 |
0 |
Y |
N |
来源字段： |
|
| 7 |
source_id |
int |
10 |
0 |
N |
N |
0 |
来源ID： |
| 8 |
register |
smallint |
5 |
0 |
Y |
N |
0 |
注册位置: |
| 9 |
create_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间： |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间： |
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
warehouse_information_id |
int |
10 |
0 |
N |
Y |
仓库信息ID |
|
| 2 |
article_no |
varchar |
64 |
0 |
Y |
N |
商品编号 |
|
| 3 |
trade_name |
varchar |
64 |
0 |
Y |
N |
商品名称 |
|
| 4 |
product_cover |
varchar |
255 |
0 |
Y |
N |
商品封面 |
|
| 5 |
commodity_type |
varchar |
64 |
0 |
Y |
N |
商品类型 |
|
| 6 |
specification_unit |
varchar |
64 |
0 |
Y |
N |
规格单位 |
|
| 7 |
inventory_quantity |
int |
10 |
0 |
Y |
N |
0 |
库存数量 |
| 8 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 9 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 10 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
表warehousing_information (入库信息)
| 编号 |
名称 |
数据类型 |
长度 |
小数位 |
允许空值 |
主键 |
默认值 |
说明 |
| 1 |
warehousing_information_id |
int |
10 |
0 |
N |
Y |
入库信息ID |
|
| 2 |
warehousing_no |
varchar |
64 |
0 |
Y |
N |
入库号 |
|
| 3 |
article_no |
varchar |
64 |
0 |
Y |
N |
商品编号 |
|
| 4 |
trade_name |
varchar |
64 |
0 |
Y |
N |
商品名称 |
|
| 5 |
product_cover |
varchar |
255 |
0 |
Y |
N |
商品封面 |
|
| 6 |
commodity_type |
varchar |
64 |
0 |
Y |
N |
商品类型 |
|
| 7 |
specification_unit |
varchar |
64 |
0 |
Y |
N |
规格单位 |
|
| 8 |
receipt_quantity |
int |
10 |
0 |
Y |
N |
0 |
入库数量 |
| 9 |
receipt_unit_price |
int |
10 |
0 |
Y |
N |
0 |
入库单价 |
| 10 |
receipt_amount |
varchar |
64 |
0 |
Y |
N |
入库金额 |
|
| 11 |
warehousing_date |
date |
10 |
0 |
Y |
N |
入库日期 |
|
| 12 |
supplier_name |
varchar |
64 |
0 |
Y |
N |
供应商名称 |
|
| 13 |
recommend |
int |
10 |
0 |
N |
N |
0 |
智能推荐 |
| 14 |
create_time |
datetime |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
创建时间 |
| 15 |
update_time |
timestamp |
19 |
0 |
N |
N |
CURRENT_TIMESTAMP |
更新时间 |
第5章 系统实现
5.1 管理员功能模块
管理员登录，管理员通过输入界面上显示的信息然后点击登录就能登录到系统进行系统的使用了，如图5-1所示。
图5-1管理员登录界面图
管理员登录进入数字化超市管理系统之后，就可以对所有的信息进行查看，可以查看到首页、网站管理（轮播图、超市公告）人员管理（管理员、会员用户、员工用户）模块管理（仓库信息、供应商、商品类型、商品信息、商品下架、入库信息、订单信息、员工管理、工资信息、员工签到、销售信息、留言反馈）个人管理等，并且还可以对其进行相应的操作管理，如图5-2所示。
图5-2管理员功能界面图
用户管理，在用户管理页面中可以对索引、用户名、会员姓名、性别、年龄、头像等信息进行详情、修改或删除等操作，如图5-3所示。
图5-3用户管理界面图
商品信息管理，在商品信息管理页面中可以对索引、商品信息等信息进行详情、修改或删除等操作，如图5-4所示。
图5-4商品信息管理界面图
入库管理，在入库管理页面中可以对索引、商品编号、商品名称、入库数量、供应名称、入库单价等信息进行详情、修改或删除等操作，如图5-5所示。
图5-5入库管理界面图
5.2员工功能模块
员工登录进入数字化超市管理系统可以对首页、首页、仓库信息、商品信息、商品下架、订单信息、员工管理、工资信息、员工签到、销售信息、个人管理等进行相应的操作管理，如图5-6所示。
图5-6员工功能界面图
留言反馈，在留言反馈页面中可以填写反馈内容、留言日期、审核状态等信息进行操作，如图5-7所示。
图5-7留言反馈界面图
订单信息管理，在订单信息管理页面中可以对订单号、序号、商品名称、商品封面、商品类型等信息进行详情等操作，如图5-8所示。
图5-8订单信息管理界面图
第6章 系统测试
6.1 测试目的
随着互联网不断的发展，目前各大领域都利用互联网进行了信息的管理，因此产品能否存货，质量问题是很重要的标准，也决定着是否有更多的人使用。所以软件的质量我们必须要把关，必须要把软件做好，做到位，少出不必要的问题，这样才能有更多的用户使用，并且得到更多的推广。所以，我们在开发完系统后，需要进行大量的测试，以确保系统的稳定性和可使用性，并要确定系统的质量能否做到满足不同人的需求。这是系统在开发设计中非常重要的环节，测试的结果直接关系到系统的好坏。
集成测试：在系统测试当中会出现很多的问题，我们要及时的进行标注并且在进行测试的时候要采取自动化的测试，这样即准确又快速，而且不会出现疲劳，手动的测试很容易出现疲劳期，而且测试的结果也有时候会出错，所以在测试的时候才去自动测试时最好的测试方法。
在测试的过程中及时的发现问题，并且进行问题的解决，这样设计出的系统可以正常稳定的运行，不会出现重大的问题。我所进行的软件测试参照以下三个步骤进行测试：
(1)模块测试：对系统中的每一项都进行针对的测试，发现并找到问题。
(2)系统测试：让系统长时间进行各种情况下的运行，反馈运行期间的稳定性问题并解决。
(3)验收测试：其他测试完成后，最后检测阶段，确保软件准备就绪。
6.2 测试方法
在对系统进行测试的时候我们主要应用到两种测试的方法，通过测试我们就能找出可能存在的问题保证系统成功运行。
从软件的内部构造和具体实施是否有关系的观点来看：黑盒测试和白盒测试。
1）黑盒测试：测试系统功能，当用户进行相应的操作时，系统是否能够及时且准确的反馈数据，并执行相应功能。需要对功能以及使用方法进行详细的测试，保证所有的操作信息都能够完整的输出输入。
2）白盒测试：主要是对系统的结构进行测试，了解系统在运行过程中是否可以正常的工作。
数字化超市管理系统的测试也会从下面几方面进行：
(1)窗体测试：例如用户登录界面，在用户名和密码输入时，需要界面窗口弹出，给予用户反馈，我对窗口的设计进行了测试，确保每一个窗口在用户进行相应操作后，能够及时的弹出。
(2)数据跟踪：进行数据跟踪，我们就能知道系统功能是否在顺利的执行当中。将数据库中的相关的信息进行调动，弹出我们需要的相对应的数据信息。同时，在追踪过程中，我们也更容易的发现系统的问题所在，便于解决问题和维护系统。
(3)综合测试：完成上述测试后，需要对系统进行由内而外的重新检测，来宏观的发现系统中存在的问题，并且及时的进行解决，系统的设计要结合实际的使用情况有针对性的进行开发，可以满足不同人的需求。
本数字化超市管理系统设计基本达到我理想的开发状态，在各个功能的运行方面，表现较为良好，基本满足用户的使用需求，及时矫正了较多的错误信息。总体说来，软件通过了相应的测试。
表6-1：用户登录测试表
| 模块名称 |
测试用例 |
预期结果 |
实际结果 |
是否通过 |
| 登录模块 |
用户名：admin 密码：123 |
弹出错误提示，提示密码错误 |
弹出错误提示，提示密码错误 |
通过 |
| 登录模块 |
用户名：123 密码：admin |
弹出错误提示，提示用户名错误 |
弹出错误提示，提示用户名错误 |
通过 |
| 登录模块 |
用户名：admin 密码：admin |
管理员登录成功 |
管理员登录成功 |
通过 |
表6-2：修改密码测试表
| 模块名称 |
测试用例 |
预期结果 |
实际结果 |
是否通过 |
| 修改密码模块 |
原密码：666 新密码：123 确认密码：123 |
弹出错误提示，提示原密码错误 |
弹出错误提示，提示原密码错误 |
通过 |
| 修改密码模块 |
原密码：admin 新密码：123 确认密码：333 |
弹出错误提示，提示确认密码不一致 |
弹出错误提示，提示确认密码不一致 |
通过 |
| 修改密码模块 |
原密码：admin 新密码：123 确认密码：123 |
密码修改成功 |
密码修改成功 |
通过 |
6.4 测试结论
测试的过程要按照指定好的计划一步一步的实行，测试时候一定不要着急，并且将测试的结果进行详细的记录，我们在进行测试的时候做好选择自动化的测试，这样更加的准确也更快捷，如果采用人工测试的方法就不会这么的方便，很可能会出现一些问题，而且极其测试不会疲劳也不会出现问题。在测试的时候一定要非常专注，时刻关注着测试的结果，一旦发现异常及时进行修改，；最后，测试完之后的文档应该保存下来，方便以后测试时用到。
通过测试，我们也可以直观的感受到，在我们最开始进行系统设计的时候，先把思路理清楚，才能有机会把代码写好。有好的逻辑性的代码在后期的测试中才能避免出现问题，也可以给我们节省很多的时间和不必要的操作。
第7章 结 论
数字化超市管理系统为用户提供了公平的、相互包容的、操作方便的使用系统，基本满足了用户的使用需要，以及我最初的开发目标和方向。Java语言、MySQL数据库等技术时是我开发的基础，这些技术都有各自的优点，学好这些技术，至关重要。通过这些优点设计出来的系统能够正常稳定的运行，并且可以满足人们的所有需求，在对系统的需求以及各个模块进行了详细的分析后，有针对性的进行设计，最后通过测试，系统能够正常的运行，该数字化超市管理系统设计完成。
本次开发过程中使用的是Java技术，该技术具有代码编写简单方便，对平台没有要求对技术方面也没有要求，并且有很好的面像对象性，所以在技术方面是相当成熟的。利用java技术作为系统主要的技术支持可以使得系统能够正常的运行并且实现相应的功能。在这次的系统的设计过程中遇到了很多的困难，幸好有老师同学们的帮助，在他们的帮助下完成了这次系统的设计。
除开系统的设计方面，就商业因素而谈，该网站具有很好的商业前景。数字化超市管理系统不像线下实体店，品牌价值在购买影响因素中尚未成较大比例，诸多国内外新兴商品正纷纷涌进。这也使得品牌复杂多样，商品种类繁多，而且不能单纯的以商品论好坏。消费者在选购产品时，容易凌乱，不清楚自己的实际需要，从而造成不必要的耗费。此网站的设立就是为了将各类型商品的具体信息进行统计规划，让消费者可以方便的在各商品之间进行横向对比。而且，网站还会提供最新的商品小时情报，做出新的消息报道。且宣传网站的成本要比品牌低的多，在预算层面，我的网站有着相应的优势。
[1]谭慧敏,白桦,闫星臣,郑竞恒.基于系统动力学的连锁超市多级库存优化研究[J].物流工程与管理,2022,44(02):36-39.
[2]王茹葳.Java编程语言在大数据开发中的应用[J].电子技术,2022,51(01):160-161.
[3]孙辉中.JAVA编程语言在计算机软件开发中的应用[J].网络安全技术与应用,2022(01):49-50.
[4]沙之洲.Java编程语言在计算机软件开发中的应用[J].电子世界,2021(24):125-127.DOI:10.19353/j.cnki.dzsj.2021.24.052.
[5]李贞,耿海军.基于Java交互式页面的远程农机设计系统研究[J].农机化研究,2022,44(10):176-180.DOI:10.13427/j.cnki.njyi.2022.10.028.
[6]李雅琴.Java编程语言的优势及其应用实践研究[J].互联网周刊,2021(24):60-62.
[7]王瑛瑛.基于Java技术的英语学习激励系统设计与实现[J].微型电脑应用,2021,37(12):71-73+77.
[8]宋文彬.探讨Java平台及应用Java技术的安全问题研究[J].数字通信世界,2021(12):51-52+60.
[9]王宇,夏丽丽,何颖刚.基于SSM框架的高校毕业论文管理系统的设计与实现[J].电子技术与软件工程,2021(22):26-29.
[10]张文,方巍,贾雪磊.基于SSM框架的合租系统设计与实现[J].计算机技术与发展,2021,31(11):159-164.
[11]Alessandro Midolo,Emiliano Tramontana. Refactoring Java Loops to Streams Automatically[C]//Proceedings of 2021 4th International Conference on Computer Science and Software Engineering (CSSE 2021).,2021:147-151.DOI:10.26914/c.cnkihy.2021.052091.
[12]周游,张国华.基于SSM框架智慧养老系统设计[J].软件,2021,42(10):47-49.
[13]Jun Ma, Jun Mao, Long Chen , Lili Yin. Design and Implementation of Multi-terminal Debugging System based on SSM Framework[J]. International Core Journal of Engineering,2021,7(7):
[14]吴春梅,曹美琪,汪金辉,檀枭,李冬雪,杨渤.智慧便民超市系统的管理与设计[J].电子制作,2021(01):55-56+69.DOI:10.16589/j.cnki.cn11-3571/tn.2021.01.018.
[15]Paul Krill. Eclipse weighs Java 11 support for Jakarta EE 9[J]. InfoWorld.com,2020:
[16]张娜,李盛,孙健平.超市自助导购结算系统[J].电脑知识与技术,2020,16(14):131-132+137.DOI:10.14004/j.cnki.ckt.2020.1525.
[17] Design and Implementation of ERP System Based on SSM Framework[J]. ,2020,440(5):
[18]侯东洋,杨梓靖,贾宇琛.基于RFID的无人超市系统优化方案[J].网络安全技术与应用,2019(12):62-63.
[19]Ping Wanxin,Chen Yuankun,Hou Xiaoyan. Design of Campus Bicycle Rental Management System Based on SSM Framework[J]. Journal of Physics: Conference Series,2019,1314:
[20]吴玥璇,贺雪梅.基于IDAC的超市系统服务设计[J].工业设计,2019(08):81-83.
光阴似箭，一晃大学生活即将过去了。一直以严谨的态度和积极的热情投身于学习和工作中，虽然有竞争，也有泪水，但是通过我不断学习和奋斗不断的完善自己，不仅很好的完成了我的学业而且也让我的各方面得到了发展，取得了很大的进步。
大学的生活也即将结束，虽然也有许多的不舍，但是终究是要告别的。回想大学的学习生活，有泪水也有汗水。在此期间我严格要求自己，凭着对知识的强烈追求，刻苦钻研，勤奋好学，态度端正，目标明确，牢固的掌握了一些专业知识和技能，做到了理论联系实际。除了专业知识的学习外，我还不断的扩展我的知识面，从不同的领域以不同的方式来获得新的知识。争取成为一名各方面都很合格的大学生。
这次的毕业设计，是我独自完成周期最长，也是耗力最大的一个项目。值得庆幸的是，在我毕业设计完成的过程当中，有许多帮助我的同学和老师。在几个月的开发过程中，我遇到了大大小小无数个问题。是我的舍友和老师，不断地帮助鼓励。
我的指导老师，在自身工作十分繁忙的情况下，依然能做到及时恢复我们发去的问题邮件，并抽时间对我们进行线下的辅导。指出我们设计上的失误，逻辑错误以及产品力规划问题，可以说没有导师的帮助，我的毕设会陷入死胡同，是导师为我指点了迷津，像迷雾中的路灯，为我指明方向！
免费领取项目源码，请关注点赞+私聊