Project git source code: https://gitee.com/oklongmm/biye
1 Introduction
1.1 Background At
present, with the rapid development of information, information technology has gradually become the foundation of various technologies, and information has become the core element of a company’s competitiveness . The survival and development of an enterprise depends on correct decision-making, and the basis of decision-making is information. Therefore, the competitiveness of an enterprise depends entirely on its ability to obtain and process information. For enterprises to obtain and process information accurately and quickly, enterprise informatization is an inevitable choice. Enterprises must accelerate internal information exchanges, improve their business processes and management models, increase operational efficiency, reduce costs, and improve competitiveness. Information construction is a requirement for enterprises to adapt to social development. Enterprise management information system, or enterprise MIS, is an important part of enterprise informatization. With the continuous advancement of my country's reform and opening up, the people's living standards are improving day by day, and the tourism economy is booming, all of which have driven the development of the hotel industry. In addition, there are more and more inbound tourists, and there are more and more foreign guests entering for business activities. Traditional craftsmanship can no longer meet the needs of modern hotel management. Timely, accurate, and all-round networked information management becomes necessary. Hotel is a service-oriented industry. From the beginning of the guest's reservation to the check-in to the final check-out, each step must maintain a consistent level of service. A missed step will make its image of hard work fall short. To become a successful hotel, you must feel at home. Facing the fierce competition in the hotel industry, all hotels are striving to expand the breadth and depth of their service areas. Although the computer is not a key element for the success of the hotel, it can help those elements that really affect the success or failure to play a greater role. Therefore, the use of a brand-new computer network and management system will become one of the important means to improve the management efficiency of the hotel and improve the service standard.
1.2 Purpose
Facing the opportunities and challenges of the information age, the use of technological means to improve hotel guest room management is undoubtedly an effective way. The use of brand-new computer networks and guest systems has become one of the important ways to improve hotel guest room management systems.
The system can meet the basic functional requirements of small and medium-sized hotels. Its biggest feature is that it organizes a large amount of redundant data information into an easy-to-manage database, provides a practical and advanced guest room management mode for small and medium-sized hotels, and improves the efficiency of guest room hotel management. .
1.3 Feasibility analysis
(1) Economic feasibility
In today's fiercely competitive environment, whoever leaves a good service impression on customers and attracts customers to visit again can ultimately win business opportunities. The original manual hotel room management can no longer adapt to today's increasingly busy work needs, errors inevitably occur and work efficiency is low. The end result is that employees cannot work normally, and guests also have dissatisfaction and complaints about hotel management. The original management method cannot be improved by effective measures, which will eventually lead to the idleness and waste of human, financial, and material resources, which is the main reason why companies cannot achieve better performance. To change this situation, companies must consider from multiple parties, comprehensively manage, integrate resources, improve organizational efficiency, and effectively reduce operating costs.
In contrast, the application of the system has the following benefits:
①It can replace a lot of manpower to deal with various tedious tasks, saving labor costs;
②It saves time for customers, and the convenient and fast service is improved again. The respective efficiency is saved and a lot of time is saved. For enterprises, time is money;
③Being able to make full use of lower-cost social resources (computers) and apply them to high-quality services (hotel management) is the rational allocation of social resources, the utilization of resources, and the Save social costs at one time;
④Because the system can serve customers indirectly and quickly, it can attract more customers, greatly increase passenger flow, and ultimately make the company continue to make profits.
(2) Management feasibility
How to provide guests with high-quality services to the greatest extent possible to enhance their recognition of the hotel and enhance the image of the hotel is a problem that the manager of the hotel has been thinking about and solving. For a long time, hotel managers definitely don't want too many errors when entertaining customers. If the hotel room management system can be used for daily hotel business management, it can reduce the workload of employees, reduce the error rate, and increase work efficiency exponentially. The application of this system plays a huge role in improving the quality of hotel services. Hotel managers-especially middle and senior managers-will certainly be happy to accept and strongly support the application of this system in hotels after understanding its role. Therefore, the system is feasible in management. (3) Technical feasibility The
hotel development management system uses VB6.0 as the main development tool, the database uses Access2000, and the technology has mature software program support. For the daily operation and management of the system, as long as the relevant staff are trained, they can be competent, and there is no need to worry too much about major errors or problems in the operation, so it is technically feasible.
Through the above feasibility analysis, the hotel guest room management information system can help the hotel's actual business processing, which is beneficial to reduce management costs, reduce error rates, and improve customer satisfaction and recognition; related technologies are mature and easy to implement, and can help hotels realize computer-assisted modernization Scientific management.
1.4 Development environment
Development language: javaee
development platform: windows 7, 1G memory, integrated graphics.
Development tools: javaee version of eclipse, mysql.
2 System requirement analysis stage
2.1 Objectives of the requirement analysis stage
(1) Understand the basic content of hotel guest room management;
(2) Comprehensively understand the needs of the managers at all levels of hotel guest room management;
(3) Understand the basic business of hotel guest room management Process;
(4) Understand the working overview of hotel guest room manual management mode and information system, and the difference between them;
(5) Through investigation and communication with hotel guest room management personnel, understand the user’s business requirements for hotel guest room management system, Security and integrity requirements;
2.2 Tasks in the demand analysis stage
Processing objects:
The processing objects of the system are customer reservation and unsubscription information management, customer check-in information management, customer room change information management, customer check-out information management and Financial statistical information management.
The system's processing objects involve the following information:
customer basic information (Guest): customer number, customer name, customer gender, customer ID number, customer phone number, customer address, customer advance payment, customer points, customer discounts Degree, customer balance.
Basic room information (RoomInfo): room number, room type, room price, room floor, room orientation.
Basic consumer item information (Atariff): consumer item number, consumer item name, consumer item price.
Basic information of guest room items (RoGoInfo): guest room item number, guest room item name, original price of guest room items, guest room item compensation multiple.
Room State Information (RoomState): room number, customer number, check-in time, check-out time, booked check-in time, booked check-out time, check-in price, room state modification time, flag.
Processing functions and requirements:
(1) A certain amount of customer information can be stored, and corresponding customer data operation and management can be conveniently and effectively carried out, which mainly includes:
Entry, deletion and modification of customer information.
Keyword search for customer information.
(2) It can perform corresponding operations on the customer's reservation and cancellation information, check-in information, room exchange information, check-out information, consumption information and damaged item information, which mainly include:
Customer reservation cancellation, check-in, room exchange, and withdrawal Room registration, deletion and modification (ie registration, deletion and modification of room status information).
Registration, deletion and modification of customer consumption information.
(3) A certain security mechanism can be provided to provide authorized access, modification and deletion of data information to prevent random inquiry, modification and deletion.
(4) For queries, the statistical results can be displayed in a list.
2.3 Achievements in the demand analysis stage The
experience and harvest of
system demand analysis is mainly through consultation with surrounding hotel room management staff, asking for advice, understanding the rules and operating mechanism of hotel room management, and searching for relevant hotel room management system knowledge on the Internet to understand hotel rooms The current situation of management, and some problems in the management process. Since we have never been in contact with hotel management business before, we always didn't know which business should be the focus of our understanding. When drawing the business flow chart and the data flow chart, I encountered many problems and found many imperfect parts of the oven. After repeated reconsideration, re-analysis and improvement, I gradually clarified the business and finally successfully completed the requirements. Tasks in the analysis phase.
The business flow chart and data flow diagram of the
hotel guest room management system This article starts with the business of the hotel guest room management system, and draws the business flow chart of booking and unsubscribing, check-in business flow, room change flow, and check-out business flow chart. According to the business flow chart, a data flow diagram corresponding to the business flow chart was drawn.
Business flow chart
(1) Business flow chart of booking and unsubscribing
(2) Flow chart of check-in business
(3) Flow chart of check-out business
(4) Flow chart of house swap
(5) Flow chart of financial statistics business
Data flow diagram
(1) Top-level data flow diagram
(2) The first layer data flow diagram
(3) Reservation and unsubscription data stream
(4) Data flow diagram of room change
(5) Check-in data flow diagram
(6) Flow chart of financial statistics
(7) Check out the data flow diagram
3 Overall design of system functions
3.1 System function module division
Combining the results of the previous requirement analysis stage for comprehensive processing, the functions that need to be completed by the guest room management system are determined, which are mainly divided into the following modules:
(1) System
① modify password ② add user
(2) Guest room information management
Set guest room standard
①Add guest room standard ②Modify guest room standard ③Delete guest room standard
Set guest room information
①Add guest room information ②Modify guest room information ③Delete guest room information ④Query guest room information
(3) Reservation information management
①Check remaining guest room information ②Add Reservation Information
③Modify Reservation Information ④Query Reservation Information
(4) Settlement Information Management
① Add Settlement Information ② Modify Settlement Information
③ Query Settlement Information
3.2 Functional Module Diagram of the System
4 System database design
4.1 Hotel guest room management system data dictionary The
data dictionary is a collection of various data descriptions in the system, and is the main result of detailed data phone and number nine analysis. Data dictionary occupies a very important position in database design. Data dictionary usually includes 6 parts: data items, data structure, data flow, data storage, processing process and external entities.
A data item is a data unit that cannot be subdivided.
The data structure reflects the combination of data.
The data stream is the path through which the data structure is transmitted in the system.
Data storage is the place where the data structure stays or is saved, and it is also one of the sources and destinations of the data flow.
The specific processing logic of the processing process is generally described by a decision table or a decision tree. The data dictionary is descriptive information that needs to describe the processing process.
The data items included in this article. Data structure. The processing process is as follows:
Data item
Table 4-1 Data item table
Data phase number Data item name Data item alias Data item type Length range Remarks
Dl-1 Gno Customer code Char 20
Dl-2 Gname Customer name Char 20
Dl-3 Gsex Customer gender Char 2 "Female", "Male"
Dl-4 Gid Customer ID number Char 18
Dl-5 Gtel Customer phone Char 11
Dl-6 Gaddress Customer address Char 20
Dl-18 Rno Room number Char 20
Dl-19 Rtype Room type Char 20
Dl-20 Rprice Unit price of room float
Dl-21 Floor Room floor Int
Dl-22 Toward Room facing Char 10
Dl-24 Atime Check-in datetime
Dl-25 Rtime Booking date datetime
Dl-26 Ltime Check-out datetime
Dl-27 Tntoprice Check-in price float
Dl-28 Stime1 Reservation modification time datetime
Dl-34 Stime2 Unsubscription modification datetime
Dl-35 Stime3 Check-in modification datetime
Dl-36 Stime4 Change room modification datetime
Dl-37 Stime5 Check-out modification Room status datetime
Data structure
Table 4-2 Data structure
Data structure number Data structure name Data structure meaning Data structure composition
DS-1 guest Customer information Gno, Gname, Gsex, Gid, Gtel, Gaddress, Account, balance, grade, discount
DS-2 Into Check-in Information DS-1+DS-8
DS-3 reserve Reservation information DS-1+DS-8
DS-4 return Unsubscribe information DS-1+DS-8
DS-7 RoomType Room information Rno,Rtype,Rprice,Floor,Toward
DS-8 RoomState Room State Information Rno, Atime, Rtime, RLtime, Ltime, Gno, Intoprice, Stime
DS-9 consum consumption list Cono, Gno, account, balance, Amoney, Dmoney, Cotime
DS-10 Amuse customer consumption form DS- 6+DS-1
Data Processing
Table 4-3 Processing Process
Processing Logic Number Processing Logic Name Brief description of input data flow Processing output data flow
P1.1 Check customer requirements. The front desk checks whether there is room customer reservation data, room status information, and room type according to the room type and room status information. Check whether there are rooms that meet the customer's requirements and feedback the customer information that meets the requirements. And customer information.
P1.2 Reservation registration assigns customers to rooms that meet the requirements, and records customer information and room information that meet the requirements at the front desk. According to the information that meets the requirements, register, modify the room status reservation form, and archive the reservation form. Feedback to the customer
P1.3 Unsubscribe registration Unsubscribe processing of the customer's unsubscription data According to the customer's unsubscription information, room status and room status information, update the room status information according to the room status information
P2.1 Check-in registration front desk has booked a room The customer registers the reservation information given by the customer to check in, revises the room status information after the change, and the new check-in record.
P3.1 Check the customer's requirements. Check whether the hotel's vacant rooms meet the customer's requirements. The customer's room-changing requirements are based on the customer's requirements. Request, check whether there are vacant rooms that meet customer requirements meet/unsatisfied information, check balance requirements
P3.2 Check balance check the customer’s consumption balance Check balance request Check the customer’s consumption list according to the customer’s consumption list, check whether the balance can meet the exchange Room price balance is sufficient/insufficient information
P3.3 Registration of room change. The balance of room change registration is sufficient for the room changer. Register the room
changer and modify the room status information. P3.4 Open the renewal notice and fill in the required payment notice for the room change customer. Insufficient amount Fill in the renewal notice Renewal notice
P4.1 Check-out check-out front desk confirms the guest’s check-out. The guest check-out data will update the room status information according to the guest’s check-out information, and archive the new room status information
P4 .2 Print consumption list According to the customer consumption summary of the finance department, print customer consumption data, the source finance department prints the consumption list according to the customer consumption summary of the finance department, and feeds back to the customer consumption list, and feeds back to the customer their consumption status
P5.1 Statistics of consumption items Check the customer's consumption according to the customer's consumption items and consumption items owned by the housekeeping department. The customer's consumption items are checked according to the consumption items owned by the housekeeping department. The consumption items of the customer are counted according to the consumption items owned by the housekeeping department. Section
P5.2 Summarize customer consumption items. Summarize the customer’s consumption, compensation for damaged items, customer information and member information. Summarize all the customer’s expenses. If a member offers a discount, a customer’s all expenditure
database model and User sub-schema definition
Database schema definition
Table 4-4 Customer basic information (guest)
column name data type can be empty Description
Gno char(20) not null Customer number
Gname varchar(20) not null Customer name
Gsex varchar(2) not null Customer gender
Gid char(19) not null Customer ID
Gtel char(11) Customer phone
Gaddress varchar(20) Customer address
Table 4-5 Roominfo
column name data type can be empty Description
Rno char(10) not null Room number
Rtype varchar(20) not null Room type
Rprice money not null Room price
Rfloor int not null Room floor
Toward char (10) not null Room orientation
Table 4-6 Room State Information RoomState
column name data type can be empty Description
Rno char(10) not null Room number
Gno char(20) not null Customer number
Atime datetime Actual check-in time
Ltime datetime Actual check-out time
Rtime datetime Booked check-in time
Rltime datetime Book check-out time
IntoPrice money Check-in price
Days int Check-in days
flag varchar(4) Book check-in flag
4.2 Conceptual design stage
The process of abstracting user needs obtained from demand analysis into an information structure, that is, a conceptual model, is conceptual structure design. It is the key to the entire database design.
Tasks and goals of the conceptual design stage
(1) Select the underlying data stream as the entry point, usually the subsystems in the actual system;
(2) Design the sub-ER diagram, that is, the ER diagram of each sub-module;
(3) Generate a preliminary ER diagram , Through the merger method, to achieve the unity of the entities, attributes, and connections of the subsystems;
(4) Generate a global ER diagram to eliminate conflicts and other aspects.
In this hotel guest room management system, starting from the second-level data flow chart, analyze the second-level data flow chart and data dictionary, and know that the functions of the entire system revolve around the processing of "customers", "rooms" and "consumption". According to the two criteria between the corpse and the attribute: ○1 As a "attribute", it can no longer have the nature that needs to be described. ○2 "Attributes" cannot be related to other entities. The data flow chart 2.8, figure 2.9, figure 2.10, and figure 2.11 can be integrated into sub-ER figure 3.1 of booking, unsubscribe, check-in, room exchange and check-out, and the data flow diagram 2.12 can be abstracted into sub-ER figure 3.2. Then the step-by-step integration is adopted. The method merges the sub-ER diagrams, eliminates unnecessary redundancy and conflicts, and generates a basic ER diagram 3.3.
Stage results
(1) According to different objects, start with the second-level data flow chart, and draw each sub-ER diagram separately :
(A) ER diagram abstracted from data flow diagrams in Figure 2.8, Figure 2.9, Figure 2.10 and Figure 2.11:
(B) ER diagram abstracted from data flow diagram Figure 2.12:
(C) The total ER diagram synthesized from the sub-ER diagrams in Figure 3.1 and Figure 3.2 by eliminating conflicts and redundancy:
(2) The attributes of each entity in each E-R diagram are as follows:
Customer: Guest (Gno, Gname, Gsex, Gid, Gtel, Gaddress, Account, Ggrade, discount, balance)
Basic guest room information: RoomInfo (Rno, Rtype, Rprice, Rfloor, Toward)
Consumption items: Atariff (Atno, Atname, Atprice)
Room item information: RoGoInfo (Goodsno, Goodsname, Oprice, Dmultiple)
The attributes of each ER diagram are as follows:
Reservation: Reserve(Stime1,Rtime, Rltime)
Unsubscribe: Back(Stime2)
Check-in: Into(Stime3, Atime, Ltime)
Change room: Change(Stime4)
Check-out: Return(Stime5)
Consumption: Consumelist(Amount, Wtime)
4.3 The logic design stage
logic design tasks and
The conceptual design stage above the target is independent of any kind of data model, but the logic design stage is related to the selected DBMS product. The task of system logic design is to convert the basic ER diagram designed in the conceptual design stage to the selected DBMS The logical structure corresponding to the data model supported by the product. The specific content includes two major tasks: data organization (converting the ER diagram into a relational model, model optimization, database schema definition, user sub-mode design) and data processing (drawing a diagram of system function modules).
Data organization
Convert ER diagram to relational model
The entity type is converted to the relational model. The attribute of the entity is the attribute of the relationship, and the code of the entity is the code of the relationship. For the connection between entities, there are the following different situations:
an m:n connection is transformed into a relational model. The codes of the entities connected to the connection and the attributes of the connection itself are all converted into the attributes of the relationship, and the code of the relationship is a combination of the codes of the entities.
A 1:n connection can be converted into an independent relational pattern, or it can be merged with the n-terminal corresponding relational pattern. If it is converted to an independent relational model, the codes of the entities connected to the connection and the attributes of the connection itself are converted to the attributes of the relation, and the code of the relation is the code of the n-terminal entity.
A 1:1 relationship can be converted into an independent relationship model, or it can be merged with the relationship model corresponding to either end. A multiple connection between three or more entities can be transformed into a relational model. The codes of the entities connected with the multiple connection and the attributes of the connection itself are all converted into the attributes of the relationship, and the code of the relationship is the combination of the code of each entity and the relationship mode with the same code can be combined.
Since the contact between the customer and the guest room is 1:n (one-to-many), the contact between them can be merged with the n-terminal physical guest room, or it can be independently used as a relationship mode, and we choose to use it as an independent relationship mode. Since the customer and the guest room items, the contact mode of the consumption item is n:n (many-to-many), the relationship between them can be transformed into an independent relationship model. The specific basic ER diagram is transformed into a relationship model as follows:
Customer: Guest (Gno, Gname, Gsex, Gid, Gtel, Gaddress, Account, Ggrade, discount, balance)
Basic room information: RoomInfo (Rno, Rtype, Rprice, Rfloor, Toward)
Consumption items: Atariff (Atno, Atname, Atprice)
room items Information: RoGoInfo (Goodsno, Rno, Goodsname, Oprice, Dmultiple)
Reservation: Reserve(Gno,Rno,Stime1,Rtime, Rltime)
Unsubscription: Back(Gno,Rno,Stime2)
Check-in: Into(Gno,Rno,Stime3,Atime,Ltime)
Change room: Change(Gno,Rno,Stime4)
Check out: Return (Gno, Rno, Stime5)
Consumption: Consumelist (Atno, Gno, Amount, Wtime)
Item Compensation Sheet GoAmInfo (Goodsno, Gno, Rno, Amendstime, Dnum)
(Note: the double line is the main code)
model Optimize the
relationship mode
Guest, RoomInfo, Atariff, RoGoInfo, Reserve, Back, Into, Change, Return, Consumelist, GoAmInfo. There is no partial functional dependence of non-primary attributes on the primary attributes, and there is no transfer function dependence. It has reached 3NF, but The main codes of the relation modes Reserve, Back, Into, Change and Return are all the same. If five relation modes are used to represent these relations, there is a lot of redundancy, so the five relation modes are optimized to the relation mode:
basic room status Table: RoomState (Gno, Rno, Atime, Ltime, Rtime, Rltime, IntoPrice, Days, Stime, flag), where flag is a flag bit, indicating that the state of the room is reservation, check-in, and empty.
Database schema definition The
database schema definition includes three aspects:
(1) The logical structure of the data;
(2) The connection between the data;
(3) Data-related integrity constraints and security requirements.
User sub-mode definition After
converting the conceptual model to the global logic model, the user's external mode should be designed according to the needs of the local application and combined with the characteristics of the specific DBMS. The user model focuses on considering the user's habits and convenience. Including:
Use aliases that are more in line with user habits.
Different Views can be defined for users of different levels to ensure the security of the system.
Simplify the user's use of the system.
Relationship mode:
PW(u_no,u_na,e,password);
Guest(Gno,Gname,Gsex,Gid,Gtel,Gaddress,Account,Ggrade,discount,balance)
RoomInfo(Rno,Rtype,Rprice,Rfloor,Toward)
Atariff( Atno,Atname,Atprice)
RoGoInfo(Goodsno,Rno,Goodsname,Oprice,Dmultiple)
Reserve(Gno,Rno,Stime1,Rtime, Rltime)
Back(Gno,Rno,Stime2)
Into(Gno,Rno,Stime3,Atime,Ltime)
Change(Gno,Rno,Stime4)
Return(Gno,Rno,Stime5)
Consumelist(Atno,Gno,Amount,Wtime)
GoAmInfo(Goodsno,Gno,Rno, Amendstime ,Dnum)
分解分析：
1）各分量都是不可分割的数据项。满足第一范式；
2）每一个关系中的非码属性都完全函数依赖于码，符合第二范式；
3）每个关系中的主属性不传递依赖关系中的每个关系键，符合第三范式；
4）关系中所有非主属性对每个码都是完全依赖，且所有主码对于每个不包含它的码也是完全函数依赖，没有任
何属性完全函数依赖非码的任何一组属性
4.4 Database design and implementation
Figure 4-16
图4-17
图4-18
图4-19
图4-20
图4-21
5 System implementation
1. login interface
2. Main page
3. Room reservation management
4. Add room information
5. Customer Information Management
6. Bill query
6 System Testing
6.1 Testing Method
Due to the complexity of software errors, software testing requires comprehensive application testing techniques. The software testing steps are unit testing, integration testing, confirmation testing and system testing. Unit testing is to test each program unit in the source program to check whether each module correctly implements the specified function, so as to find errors in the module's coding or algorithm. This stage involves coding and detailed design documentation. After each module undergoes unit testing, the modules are assembled for integration testing to check the software architecture related issues related to the design. The confirmation test mainly checks whether the implemented software meets the various requirements determined in the requirements specification. System testing combines the determined software with other system elements (such as hardware, other supporting software, data, and labor, etc.) for testing.
6.2 Basic function test
Add guest room standard:
The results show that:
Modify guest room standard:
Show results:
Query the remaining rooms that are not booked:
6 Experience The
two-week short and substantial course design is finally over. For me, it is a comprehensive training. This
course design is not only a summary of the knowledge of the database for this semester, but also a knowledge inspection since enrollment. This not only requires mastery of database principles, but also proficiency in a programming language. I used the C# language in the VS2010 development environment that I just learned this semester, and I designed the Windows Forms interface operation mode. In this way, not only can you learn the database, but also can consolidate the knowledge of C#. Knowledge is interrelated, and no one exists alone. Therefore, if you want to learn a course well, you should think horizontally and make more connections, so that you will learn more deeply.
For this course design, I chose "Hotel Guest Room Management System". This topic is closer to daily life. Therefore, we must consider the actual situation of the hotel, conduct demand analysis according to the actual situation, and conceive functional modules. This is the basis of the design process, and it is also the most difficult and time-consuming step. Whether the analysis as a "foundation" is done adequately and accurately determines the speed and quality of building a database building on it. Poor requirements analysis can even lead to the rework of the entire database design. Then there is the conceptual structure design, which is also the key to the entire database design. It forms an independent concrete conceptual model by synthesizing, summarizing and abstracting user needs. Then there is the logical structure design, and finally the programming work. As long as there is no problem with the previous conceptual design and logical design, the database can be settled very quickly.
The next one can also be said to be the most difficult, software programming. In general, this system has basically fulfilled the requirements of the subject. I added some functions according to the actual situation to make it more humane and meet actual needs. On the way to programming, the problems encountered can also be described as various. First, because some controls did not respond to the event, the click had no effect when running, and then there was a problem with the single quotes and double quotes of the string in the SQL statement, and there was no error when the program was debugged, and there was an error when running. Finally, the parameter is passed on the parent form and child form. According to the requirements I began to design, the user can modify his password when logging in to the main interface, so the user name entered by the user in the login interface must be passed to the main interface. Then transfer to the user name to modify your password. After many tests and solving various problems, this system was finally born!
After several days of struggling, seeing this result, on the whole, I am still very pleased. This system is not perfect, and there are still some areas that can be better. This also motivates me more. In the future, I must master each part of the knowledge and cultivate my own practical operation ability, so that I can compile a more perfect and user-friendly system.