(Source code attached) Hospital registration appointment management system computer completion 42832

In the information society, there is a need for targeted ways to obtain information, but the expansion of the ways is basically the direction that people strive for. Due to deviations in the perspective, people can often obtain different types of information, which is also the most difficult to overcome with technology. subject. In view of problems such as the hospital registration appointment management system, the hospital registration appointment management system was researched and analyzed, and then a hospital registration appointment management system was developed and designed to solve the problem.

The main functional modules of the hospital registration appointment management system include carousel chart (carousel chart management) system announcement management (system announcement) system users (administrators, ordinary users, doctor users) resource management (medical news, news classification) module management (doctors Visits, departments, registration information, department introductions), adopts an object-oriented development model for software development and hardware setup, which can well meet the needs of actual use and improves the corresponding software setup and program coding work. MySQL is used as the main storage unit for backend data, and SSM framework, Java technology, and Ajax technology are used to code and develop the business system, realizing all the functions of this system. This report first analyzes the background, role, and significance of the research, laying the foundation for the rationality of the research work. Analyze the various needs and technical issues of the hospital registration appointment management system, prove the necessity and technical feasibility of the system, and then give a basic introduction to the technical software and design ideas that need to be used to design the system, and finally implement the hospital registration Appointment management system and deployment runs using it.

Keywords: hospital registration appointment management system; ssm; MYSQL

Abstract

In the information society, there is a need for targeted information acquisition channels, but the expansion of channels is basically the direction of people's efforts. Due to the deviation in perspective, people often can obtain different types of information, which is also the most difficult topic for technology to overcome. To address issues such as the hospital registration and appointment management system, research and analyze the system, and then develop and design a hospital registration and appointment management system to address these issues.

The main functional modules of the hospital registration and appointment management system include rotation chart (rotation chart management), system announcement management (system announcement), system user (administrator, ordinary user, doctor user), resource management (medical news, news classification), module management (doctor visits, departments, registration information, department introduction), adopting an object-oriented development model for software development and hardware installation, It can well meet the actual usage needs, improve the corresponding software installation and program coding work, adopt MySQL as the main storage unit for backend data, and use SSM framework, Java technology, Ajax technology for business system coding and development, achieving all the functions of the system. This report first analyzes the background, role, and significance of the research, laying the foundation for the rationality of the research work. Analyze the various requirements and technical issues of the hospital registration and appointment management system, prove the necessity and technical feasibility of the system, and then provide a basic introduction to the technical software and design ideas required for designing the system. Finally, implement the hospital registration and appointment management system and deploy and operate it.

Keywords:Hospital registration and appointment management system; ssm； MYSQL

1 Introduction

1.1 Significance of the research topic

Since the reform and opening up, although the national health department has repeatedly reformed large, medium and small hospitals across the country, especially strengthening the management of large general hospitals, each large hospital has its own advantages, and patients have the right to freely choose a large hospital. Therefore, the problem of difficulty in hospital registration cannot be completely solved in the short term. Although the health department and the media have made a lot of publicity, many private clinics and community medical clinics have emerged in various places, diverting the pressure on patients from some large comprehensive hospitals. However, private clinics and community medical clinics can only deal with the problems in daily life. They do not have complete examination, examination and diagnosis and treatment equipment, and it is difficult to make accurate judgments on complex diseases. In this case, patients will naturally choose more powerful large-scale doctors to flee. "In large and medium-sized cities, the outpatient registration halls of some well-known comprehensive hospitals are overcrowded and congested. Not only does this not allow patients to have a comfortable space and get psychological comfort the moment they step into the hospital door, , to reduce the pressure caused by physical discomfort, on the contrary, it will leave the patient with a very poor impression of the medical experience, and may also cause cross-infection of the disease in the hospital. Therefore, how to reasonably and effectively divert outpatients has become an urgent need for large hospitals Breakthrough dilemma.

Today, the country must realize informatization, departments must realize informatization, and hospitals must realize informatization management in order to meet the requirements of the times and meet the needs of patients. With the continuous development of the Internet, using browsers on computers, mobile phones, and tablets to surf the Internet has almost become an indispensable operation for people every day, which has laid a solid foundation for us to realize medical informatization. Therefore, how to develop an appointment registration management system that makes registration convenient for patients and easy for hospitals to manage is of extremely important practical significance:

1. You can make an appointment anytime and anywhere, which not only saves time and reduces costs, but also allows you to better arrange medical plans according to the appointment time. Compared with the traditional method, making an appointment allows patients to browse the medical treatment process guide chart on the webpage in advance, and more intuitively understand the process and steps of online appointment and hospital treatment, which can reduce unnecessary errors in the upcoming appointment and medical treatment; it also can You can learn more about the hospital's departments, doctor information and areas of expertise on the web page, and choose the corresponding doctor according to your own condition. You don't need to waste too much time explaining the symptoms with the registration clerk like on-site registration.

2. Able to optimize doctor scheduling and call source allocation. The schedule of registered doctors on duty is relatively fixed, and it is generally difficult to adjust it on the day when the doctor visits. The appointment method is not only convenient for patients, but also the hospital outpatient department can also adjust the number of visiting doctors in each department and the doctor's time slot based on the appointment situation. Optimize the allocation of resources and minimize the difficulty of finding the number one expert in some departments or experts.

3. It can reduce the pressure on the outpatient registration office. Many of the bustling crowds at the outpatient registration desk of the hospital are patients suffering from illnesses. Under such a premise, excessive waiting time in line is very likely to lead to conflicts among patients who jump in line, or the patient's dissatisfaction with the registration staff. Unsatisfactory registration efficiency leads to unhappiness: or patients with infectious nature are among the crowd for a long time and at close range, which will inevitably cause cross-infection. The diversion of patients according to time periods through appointment can effectively reduce the probability of occurrence of the above problems and reduce the pressure on the outpatient registration office7]. 4. It can enhance the reputation of the hospital. Let more people learn about hospital-related information from the Internet. That is, the hospital can use the network to promptly update information such as number source allocation, basic information of doctors or experts, changes in medical staff, adjustments to the department environment, new progress in academic research, achievements in the application of new equipment and new technologies, etc., thereby expanding the hospital's recognition in the whole society. awareness and influence. With the development of social economy and the continuous advancement of computer and network technology, informatization has been unconsciously integrated into all walks of life. In this environment, all things that stick to the rules will eventually be eliminated. Hospitals should respond to the changes in the information age. The call is to keep up with the pace of medical informatization reform, actively carry out appointment registration management, and continuously improve the hospital's visibility and comprehensive competitiveness.

1.2 Development status at home and abroad

1.2.1 Overview of overseas appointment registration methods

In foreign countries, it has almost become a tradition for patients to confirm the date and time of treatment with the doctor in advance by making an appointment, especially in the United States and some developed countries in Europe. The main reason is that the hierarchical diagnosis and treatment system in these countries is very standardized. Large foreign general hospitals generally do not accept patients' appointments or self-discipline except for critical patients in emergencies. When ordinary people get sick, they must first make an appointment with a general family doctor in the community medical department of the hospital, who will conduct preliminary diagnosis and treatment. When the condition is difficult to handle, the doctor will contact a specialist medical center or a large general hospital for the patient and issue a Referral form. After obtaining the referral permission, patients can make an appointment with the medical department to be referred through various methods such as telephone, online, and mobile APP, and arrive at the hospital on time. Therefore, in large general hospitals abroad, there are not many outpatients, and most of them arrange appointments through referrals. Patients are treated in an orderly manner, and there is almost no overcrowding in the outpatient halls. Of course, there are also many private medical institutions abroad that are not subject to this restriction. Patients can go directly to the site and queue up for treatment. However, the fees of these medical institutions will be much more expensive than those of hospitals with normal appointment procedures. Developed countries in Europe and the United States not only have complete hierarchical diagnosis and treatment and referral mechanisms, but are also relatively mature in the informatization construction of appointment diagnosis and treatment. All major medical institutions have flexible and convenient appointment diagnosis and treatment systems.

1.2.2 Overview of domestic appointment registration methods

In China, with the progress of society, people are gradually paying more and more attention to health. Compared with the growing number of patients, medical resources are in short supply. The clinic halls of major hospitals are basically congested. As the capital of China, Beijing can be said to be the political and cultural center of our country. As early as 1999, the Beijing Municipal Health and Family Planning Commission began to organize some large general hospitals in the city to conduct trial appointments for registration. At that time, it was mainly through phone calls and text messages. Appointment services are provided. As the queuing situation at outpatient clinics in pilot hospitals has improved, this method of appointment registration has gradually become widely used. In recent years, under the general trend of continuous popularization of computer and network technology, many large hospitals in first-tier cities have successively introduced online appointment registration systems. However, because the early web interface design was not user-friendly enough, the system stability was not high, and the telephone number at that time was It is still the mainstream communication tool. Patients are more likely to think of making a phone call when making an appointment. So online booking was not popular at that time.

Guangxi Zhuang Autonomous Region is relatively backward in domestic economic development and has a low level of informatization. There is a lot of room for improvement in medical informatization. As early as 2009, the National Health and Family Planning Commission gave guidance on the implementation of appointment registration work in major hospitals, and pointed out in a notice issued again in 2011 that further strengthening appointment registration services, deepening the reform of the medical and health system, and combining Informatization construction and the use of multiple channels including the Internet to carry out appointment registration services are the general trend. Health departments at all levels and various public hospitals should implement them as soon as possible to achieve the purpose of reducing patient queuing time and improving the level of hospital information management. In 2018, in the "National Hospital Information Construction Standards and Specifications" issued by the National Health Commission, there were clear requirements for the hospital appointment registration function.

Whether at home or abroad, implementing a standardized and reasonable appointment system and designing and implementing an advanced appointment registration management system can not only greatly improve the quality of the hospital's outpatient appointment service and improve the efficiency of medical services, but also have a positive impact on the actual operation of the outpatient department. Resource allocation has important implications.

1.3 Research content

1. Login issues for different administrators: According to the administrator’s category (administrator, ordinary user, doctor user), the administrator’s operating permissions are distinguished and different operation interfaces are displayed.

2. Database connection problem: Database connection is a key technology in the system.

3. Data consistency and security issues: This system must ensure data consistency and security in order to achieve effective management. Do not allow administrators without permission to operate on the data and back up the database regularly.

4. Interface development: The design of the system interface is very important to make the interface friendly.

5. Analyze the current status of informatization;

6. Study the current status and existing problems of the hospital registration appointment management system;

7. Research the overall architecture, overall design, database design, database security design and functional design of the system platform;

8. Research the functions and implementation methods of each subsystem of the platform, the integration of information technology, and the maintenance of information security technology.

9. Carry out functional design of the hospital registration and appointment management system.

1.4 Introduction to ssm framework

The SSM (Spring+SpringMVC+MyBatis) framework set is integrated by the two open source frameworks Spring and MyBatis (SpringMVC is part of Spring). It is often used as a framework for web projects with relatively simple data sources.

1.8.1 Spring
Spring is like a big factory that assembles beans in the entire project. In the configuration file, you can specify the use of specific parameters to call the constructor method of the entity class to instantiate the object. It can also be called the glue in the project.
The core idea of Spring is IoC (Inversion of Control), which means that programmers no longer need to explicitly `new` an object, but let the Spring framework do it all for you.
1.8.2 SpringMVC
SpringMVC intercepts user requests in the project. Its core Servlet, DispatcherServlet, assumes the responsibilities of intermediary or front desk, and matches user requests to the Controller through HandlerMapping. The Controller is the specific operation performed in response to the request. SpringMVC is equivalent to struts in the SSH framework.
1.8.3 mybatis
mybatis is an encapsulation of jdbc, which makes the underlying operations of the database transparent. The operations of mybatis are centered around a sqlSessionFactory instance. Mybatis is associated to the Mapper file of each entity class through the configuration file. The Mapper file is configured with the SQL statement mapping required for each class to the database. Every time you interact with the database, get a sqlSession through sqlSessionFactory, and then execute the sql command.

The page sends a request to the controller, the controller calls the business layer processing logic, the logic layer sends a request to the persistence layer, the persistence layer interacts with the database, and then returns the result to the business layer, the business layer sends the processing logic to the controller, and the controller then Call the view to display the data.

1.5 Paper structure and chapter arrangement

The paper will be organized hierarchically. In addition to the abstract, acknowledgments, and literature references, the main text will also analyze the website requirements, describe the general design and implemented functions, and finally list some debugging records. The main structure of the paper is as follows:

Chapter 1: Introduction. The first chapter mainly introduces the background of the project research, the current situation of system development and the research purpose and main work of this article.

Chapter 2: System requirements analysis. Chapter 2 mainly conducts demand analysis from the aspects of users and functions of the system.

Chapter 3: System Design. Chapter 3 mainly carries out functional design of the system framework, system function modules and database.

Chapter 4: System implementation. Chapter 4 mainly introduces the system framework construction and the implementation of the system interface.

Chapter 5: System Testing. Chapter 5 mainly tests some interfaces of the system and tests the main functions.

Chapter 6: Summary.

2 Analysis of hospital registration and appointment management system

System analysis is a prerequisite for developing a project. Through system analysis, the basic needs of the main users of the system can be well understood, and this is also the reason for the development of the project. Then, a feasibility analysis is performed on the system development, which usually includes technical feasibility, economic feasibility, etc. The feasibility analysis is also an analysis from the overall perspective of the project. Then the specific requirements of the project are analyzed. The analysis method is generally implemented through the user's use case diagram. The following is a detailed introduction.

2.1 Feasibility analysis

(1) Economic feasibility:

Most of the tools used in the project are currently popular open source and free, so in the early stage of development, the funds used for the project will be greatly reduced, and the development of the software will not be affected by funds during the project startup period, so It is still economically feasible. Try to meet the needs of users with the least amount of money. Save money on labor costs and equipment costs. We will go further and further on the road of paperlessness and high efficiency.

So there is no problem with economic feasibility.

(2) Operational feasibility:

The design of this project refers to several cases of website development under this mode, analyzes their operation interfaces, and combines many cases to highlight people-oriented simplified operations, so people with basic computer knowledge can operate this project.

Therefore, there is no problem with operational feasibility.

(3) Technical feasibility:

Technical feasibility refers to the feasibility of building a framework, as well as the system's adaptability to technological upgrading when better technologies emerge, and the development time and cost ratio.

The existing ssm technology can cater to the construction of all e-commerce systems. When developing this hospital registration appointment management system, I used ssm+MYSQL to run the overall program.

In summary, there is no problem with the technical feasibility.

(4) Legal feasibility:

From a developer's perspective, ssm and MYSQL are open source and free online, and there will be no legal disputes regarding intellectual property rights.

From a user perspective, as long as contraband is no longer sold on the system, treaties and agreements are made with the system, and illegal payments are eliminated.

In summary, there is no problem with the legal feasibility.

2.2 System process analysis

The business process uses some specific symbols and lines to demonstrate the user's process when using the system. When performing system analysis, the business process can help developers better understand the business, discover errors, and improve the system.

2.2.1 Data addition process

After the user successfully logs in to the system , he or she can add data. The number of the added data is specific and generated by the system. The user cannot fill it in at will. Except for the number, the user fills in other added information by himself. The filled-in information is verified by the system and is legal. If it passes, it will show that the data has been added successfully. If it is passed, it will not be added successfully. Figure 2-1 shows the process of adding data.

Figure 2-1 Data addition flow chart

2.2.2 Data modification process

The process of data modification is similar to the process of data addition described above, as shown in Figure 2-2 .

Figure 2-2 Data modification flow chart

2.2.3 Data deletion process

If there is some useless data in the system , the relevant managers can also delete the data. Figure 2-3 is the flow chart for data deletion.

Figure 2-3 Data deletion flow chart

2.3 System function analysis

2.3.1 Functional analysis

According to the roles of the hospital registration appointment management system, I divided it into three parts: the doctor user management module, the ordinary user module and the administrator management module.

Ordinary user management module:

(1) User registration and login: Visitors can enter the system at any time and browse the information in the system. However, if they want to implement doctor visits and department introduction operations, they must have an account in this system. If they do not have an account, they can register as a member user. Perform related operations, and users can also control personal information and operation information through the "My Account" button.

(2) View the home page information of the hospital registration appointment management system: The home page information of the hospital registration appointment management system includes the home page, system announcements, medical news, guidance desk, doctor visits, department introduction, my (my account, my Collection, personal center).

(3) System Announcement: The user clicks the "System Announcement" menu to display all system announcement information released by the administrator in the background, and can view the system announcement details.

(4) Medical news: Users click on the "Medical News" menu to display all medical news information. They can filter medical news according to conditions or enter keywords for local search. Clicking can enter the detailed display interface of medical news, where users can Favorites, likes and comments.

(5) Doctor’s visit: Users can check the doctor’s visit. When they find the doctor they want to know about, they can enter to view the detailed introduction. Clicking the "Registration Appointment" button will jump to the registration appointment information. Interface, fill in the registration appointment information according to the prompts, click "Submit" and the registration appointment will be completed. In the doctor's visit details interface, it also supports the function of users to comment on their favorite doctors' visits.

(6) Department introduction: Users can view department introduction information. When they find the department introduction they want to know about, they can enter to view the detailed introduction.

(7) My Account: When the user clicks the "My" button in the upper right corner, a submenu will appear. Clicking "My Account" can set and manage personal information, passwords for logging into the system, and information collected by oneself;

Administrator management module:

(1) Login: The administrator can enter the username + password to log in in the background. The administrator's username and password are set directly in the database.

(2) Carousel image: Administrators can click the "Carousel image" menu to add, delete, modify, and check the carousel image displayed on the home page.

(3) System announcements: Administrators can click the "System Announcements" menu to view all system announcements in the system. Administrators can modify existing system announcements, add new system announcements, or delete system announcements.

(4) System users: Administrators can click the "System Users" menu to manage users existing in the system, including administrator users, doctor users and ordinary users.

(5) Resource management: Administrators can click on the "Resource Management" menu to add, delete, modify and check the categories of medical news and news.

(6) Module management: Under the "Module Management" menu, we will see doctor visits, departments, registration information, and department introductions, and the administrator can add, delete, modify, and check them.

2.3.2 Non-functional analysis

The non-functional requirements of the hospital registration appointment management system include the security, reliability, performance, scalability, etc. of the hospital registration appointment management system. The details can be expressed in the following 3-1 table:

Table 3-1 Non-functional requirements table for hospital registration and appointment management system

safety	It mainly refers to the installation of the database of the hospital registration and appointment management system. The use of the database and the setting of the password must comply with the standards.
reliability	Reliability means that the hospital registration appointment management system can be operated according to the user's instructions. After testing, the reliability is over 90%.
performance	Performance is a necessary condition for the hospital registration appointment management system to occupy the market, so it is best to have good performance.
Scalability	For example, the database reserves multiple attributes, such as the use of interfaces, to ensure the non-functional requirements of the system.
Ease of use	Users only need to follow the page display content of the hospital registration appointment management system and operate.
maintainability	The maintainability of the hospital registration appointment management system is very important. After testing, there is no problem with the maintainability.

2.4 System use case analysis

Through the analysis of 2.3 functions, the use case diagram of the hospital’s registration and appointment management system is obtained:

An example of a common user role is shown in Figure 2-3.

Figure 2-3 Use case diagram of ordinary user roles in the hospital registration appointment management system

The administrator on the web background management maintains all data information in the entire hospital registration and appointment management system. An example of the administrator role is shown in Figure 2-4.

Figure 2-4 Use case diagram of administrator role in hospital registration appointment management system

2.5 Summary of this chapter

This chapter mainly determines the functions to be realized by the entire hospital registration appointment management system through feasibility analysis, process analysis, functional requirements analysis, and system use case analysis of the hospital registration appointment management system. At the same time, it also provides standards for code implementation and testing of hospital registration appointment management systems.

3 Overall design of hospital registration and appointment management system

The main contents discussed in this chapter include the functional module design and database system design of the hospital registration appointment management system.

3.1 System architecture design

The hospital's registration and appointment management system is divided into three layers in terms of architecture: presentation layer (UI), business logic layer (BLL) and data layer (DL).

Figure 3-1 System architecture design diagram of hospital registration appointment management system

Presentation layer (UI): Also known as the UI layer, it mainly completes the UI interaction function of the hospital's registration and appointment management system. A good UI can improve the user experience and enhance the user's comfort when using the hospital's registration and appointment management system. . The UI interface design must also adapt to different versions of hospital registration appointment management systems and different size resolutions to achieve good compatibility. The UI interaction function requirements are reasonable, and users must obtain consistent interaction results when performing interactive operations. This requires the presentation layer to be well connected with the business logic layer.

Business logic layer (BLL): mainly completes the data processing function of the hospital's registration and appointment management system. The data transmitted by the user from the presentation layer is processed by the business logic layer and delivered to the data layer. The data read by the system from the data layer is processed by the business logic layer and delivered to the presentation layer.

Data layer (DL): Since the data of the hospital's registration appointment management system is placed in the mysql database on the server side, the parts that belong to the service layer can be directly integrated into the business logic layer, so there is only the database in the data layer, which is mainly completed The data storage and management functions of the hospital's registration and appointment management system.

3.2 System function module design

3.2.1 Overall functional module design

In the previous chapter, the functional requirements and non-functional requirements of the system were mainly analyzed, and the use cases in the hospital's registration appointment management system were analyzed based on the requirements. Then the next step is to start designing the architecture, main functions and database of the hospital's registration and appointment management system. The hospital registration appointment management system is derived based on the demand analysis in the previous chapter. Its overall design module diagram is shown in Figure 3-2.

Figure 3-2 Function module diagram of hospital registration and appointment management system

3.2.2 User module design

The backend manager can add, delete, modify and check the users registered in the frontend. The user module structure diagram is as follows:

Figure 3-3 User module structure diagram

3.2.3 Comment management module design

The hospital registration appointment management system is an open platform for communication. Users and administrators can comment on the information on the platform to increase the interaction between users. But at the same time, in order to better standardize the content of comments and give administrators the function of deleting inappropriate comments, a comment management module needs to be specially designed. The specific structure diagram is as follows:

Figure 3-4 Structure diagram of comment module

3.1.4 Design of doctor visit management module

The hospital registration appointment management system needs to store a lot of doctor visit information. Its module functional structure, the specific structure diagram is as follows:

Figure 3-5 Doctor visit module structure diagram

3.3 Database design

Database design generally includes three major processes: demand analysis, conceptual model design, and database table creation. The demand analysis has been explained in the previous chapter, and the conceptual model design has two parts: conceptual model and logical structure design.

3.3.1 Database conceptual structure design

The following is the total ER entity relationship diagram of the main database tables in the entire hospital registration appointment management system.

Figure 3-7 General ER relationship diagram of the hospital registration appointment management system

3.3.2 Database logical structure design

Table comment (comment)

serial number	name	type of data	length	Decimal places	Allow null values	primary key	default value	illustrate
1	comment_id	int	10	0	N	Y		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	Y	N		content:
5	nickname	varchar	255	0	Y	N		Nick name:
6	avatar	varchar	255	0	Y	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	Y	N		Source table:
10	source_field	varchar	255	0	Y	N		Source field:
11	source_id	int	10	0	N	N	0	Source ID:

Table department (department)

serial number	name	type of data	length	Decimal places	Allow null values	primary key	default value	illustrate
1	department_id	int	10	0	N	Y		Department ID
2	department	varchar	64	0	Y	N		Department
3	recommend	int	10	0	N	N	0	Intelligent Recommendation
4	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	creation time
5	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	Update time

Table department_introduction (department introduction)

serial number	name	type of data	length	Decimal places	Allow null values	primary key	default value	illustrate
1	department_introduction_id	int	10	0	N	Y		Department introduction ID
2	department	varchar	64	0	Y	N		Department
3	department_director	varchar	64	0	Y	N		Department director
4	department_cover	varchar	255	0	Y	N		Department cover
5	department_address	varchar	64	0	Y	N		Department address
6	department_introduction	longtext	2147483647	0	Y	N		Department introduction
7	hits	int	10	0	N	N	0	Clicks
8	recommend	int	10	0	N	N	0	Intelligent Recommendation
9	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	creation time
10	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	Update time

Table doctor_user (doctor user)

serial number	name	type of data	length	Decimal places	Allow null values	primary key	default value	illustrate
1	doctor_user_id	int	10	0	N	Y		Doctor User ID
2	doctor_no	varchar	64	0	Y	N		Doctor's ID number
3	doctors_name	varchar	64	0	Y	N		Doctor's name
4	visiting_photos	varchar	255	0	Y	N		Photos of medical visits
5	department	varchar	64	0	Y	N		Department
6	examine_state	varchar	16	0	N	N	passed	Approval Status
7	recommend	int	10	0	N	N	0	Intelligent Recommendation
8	user_id	int	10	0	N	N	0	User ID
9	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	creation time
10	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	Update time

Table doctor_visits (doctor visits)

serial number	name	type of data	length	Decimal places	Allow null values	primary key	default value	illustrate
1	doctor_visits_id	int	10	0	N	Y		Doctor's visit ID
2	visit_number	varchar	64	0	Y	N		Visit number
3	doctor_user	int	10	0	Y	N	0	Doctor user
4	doctor_no	varchar	64	0	Y	N		Doctor's ID number
5	doctors_name	varchar	64	0	Y	N		Doctor's name
6	visiting_photos	varchar	255	0	Y	N		Photos of medical visits
7	department	varchar	64	0	Y	N		Department
8	number_of_appointments	int	10	0	Y	N	0	Number of reservations
9	visit_details	longtext	2147483647	0	Y	N		Details of medical visits
10	recommend	int	10	0	N	N	0	Intelligent Recommendation
11	timer_title	varchar	64	0	Y	N		timer title
12	timing_start_time	datetime	19	0	Y	N		Timing start time
13	timing_end_time	datetime	19	0	Y	N		Timing end time
14	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	creation time
15	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	Update time

Table hits (user clicks)

serial number	name	type of data	length	Decimal places	Allow null values	primary key	default value	illustrate
1	hits_id	int	10	0	N	Y		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	Y	N		Source table:
6	source_field	varchar	255	0	Y	N		Source field:
7	source_id	int	10	0	N	N	0	Source ID:

Notice (announcement)

serial number	name	type of data	length	Decimal places	Allow null values	primary key	default value	illustrate
1	notice_id	mediumint	8	0	N	Y		Announcement id:
2	title	varchar	125	0	N	N		title:
3	content	longtext	2147483647	0	Y	N		text:
4	create_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	Creation time:
5	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	Update time:

Table ordinary_users (ordinary users)

serial number	name	type of data	length	Decimal places	Allow null values	primary key	default value	illustrate
1	ordinary_users_id	int	10	0	N	Y		Common user ID
2	user_name	varchar	64	0	Y	N		username
3	gender	varchar	64	0	Y	N		gender
4	previous_medical_history	varchar	64	0	Y	N		Past medical history
5	family_history	varchar	64	0	Y	N		Family history
6	eating_habits	varchar	64	0	Y	N		eating habits
7	exercise_situation	varchar	64	0	Y	N		Sports situation
8	behavioral_habits	varchar	64	0	Y	N		behavioral habits
9	examine_state	varchar	16	0	N	N	passed	Approval Status
10	recommend	int	10	0	N	N	0	Intelligent Recommendation
11	user_id	int	10	0	N	N	0	User ID
12	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	creation time
13	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	Update time

Express praise (like)

serial number	name	type of data	length	Decimal places	Allow null values	primary key	default value	illustrate
1	praise_id	int	10	0	N	Y		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	Y	N		Source table:
6	source_field	varchar	255	0	Y	N		Source field:
7	source_id	int	10	0	N	N	0	Source ID:
8	status	bit	1	0	N	N	1	Like status: 1 is like, 0 is canceled

Table registration_information (registration information)

serial number	name	type of data	length	Decimal places	Allow null values	primary key	default value	illustrate
1	registration_information_id	int	10	0	N	Y		Registration information ID
2	visit_number	varchar	64	0	Y	N		Visit number
3	doctor_user	int	10	0	Y	N	0	Doctor user
4	doctor_no	varchar	64	0	Y	N		Doctor's ID number
5	doctors_name	varchar	64	0	Y	N		Doctor's name
6	number_of_appointments	int	10	0	Y	N	0	Number of reservations
7	department	varchar	64	0	Y	N		Department
8	registered_users	int	10	0	Y	N	0	registered user
9	user_name	varchar	64	0	Y	N		username
10	gender	varchar	64	0	Y	N		gender
11	previous_medical_history	varchar	64	0	Y	N		Past medical history
12	family_history	varchar	64	0	Y	N		Family history
13	eating_habits	varchar	64	0	Y	N		eating habits
14	exercise_situation	varchar	64	0	Y	N		Sports situation
15	behavioral_habits	varchar	64	0	Y	N		behavioral habits
16	number_of_registered_persons	varchar	64	0	Y	N		Number of registered people
17	sort_number	varchar	64	0	Y	N		sort number
18	examine_state	varchar	16	0	N	N	Not reviewed	Approval Status
19	examine_reply	varchar	16	0	Y	N		moderation reply
20	recommend	int	10	0	N	N	0	Intelligent Recommendation
21	create_time	datetime	19	0	N	N	CURRENT_TIMESTAMP	creation time
22	update_time	timestamp	19	0	N	N	CURRENT_TIMESTAMP	Update time

3.4 Summary of this chapter

The demand analysis of the entire hospital registration appointment management system mainly focused on the design of the overall system architecture and functional modules. The database system design was completed by establishing the ER model and database logic system design.

4 Detailed design and implementation of hospital registration and appointment management system

The detailed design and implementation of the hospital registration appointment management system is mainly based on the previous demand analysis of the hospital registration appointment management system and the overall design of the hospital registration appointment management system to design the page and implement business logic. This article mainly introduces the two parts of hospital registration appointment management system interface implementation and business logic implementation.

4.1User function module

4. 1.1 Front page interface

When entering the hospital registration appointment management system, the first thing that catches the eye is the navigation bar of the system. Below is the carousel chart and system content. The main interface is shown in Figure 4-1 below.

Figure 4-1 Front page interface diagram

4. 1.2 User login interface

医院挂号预约管理系统中的前台上注册后的用户是可以通过自己的账户名和密码进行登录的，当用户输入完整的自己的账户名和密码信息并点击“登录”按钮后，将会首先验证输入的有没有空数据，再次验证输入的账户名+密码和数据库中当前保存的用户信息是否一致，只有在一致后将会登录成功并自动跳转到医院挂号预约管理系统的首页中；否则将会提示相应错误信息，用户登录界面如下图4-2所示。

图4-2用户登录界面图

登录关键代码如下所示。

/**

* 登录

* @param data

* @param httpServletRequest

* @return

@PostMapping("login")

public Map<String, Object> login(@RequestBody Map<String, String> data, HttpServletRequest httpServletRequest) {

log.info("[执行登录接口]");

String username = data.get("username");

String email = data.get("email");

String phone = data.get("phone");

String password = data.get("password");

List resultList = null;

QueryWrapper wrapper = new QueryWrapper<User>();

Map<String, String> map = new HashMap<>();

if(username != null && "".equals(username) == false){

map.put("username", username);

resultList = service.selectBaseList(service.select(map, new HashMap<>()));

}

else if(email != null && "".equals(email) == false){

map.put("email", email);

resultList = service.selectBaseList(service.select(map, new HashMap<>()));

}

else if(phone != null && "".equals(phone) == false){

map.put("phone", phone);

resultList = service.selectBaseList(service.select(map, new HashMap<>()));

}else{

return error(30000, "账号或密码不能为空");

}

if (resultList == null || password == null) {

return error(30000, "账号或密码不能为空");

}

//判断是否有这个用户

if (resultList.size()<=0){

return error(30000,"用户不存在");

}

User byUsername = (User) resultList.get(0);

Map<String, String> groupMap = new HashMap<>();

groupMap.put("name",byUsername.getUserGroup());

List groupList = userGroupService.selectBaseList(userGroupService.select(groupMap, new HashMap<>()));

if (groupList.size()<1){

return error(30000,"用户组不存在");

}

UserGroup userGroup = (UserGroup) groupList.get(0);

//查询用户审核状态

if (!StringUtils.isEmpty(userGroup.getSourceTable())){

String res = service.selectExamineState(userGroup.getSourceTable(),byUsername.getUserId());

if (res==null){

return error(30000,"用户不存在");

}

if (!res.equals("已通过")){

return error(30000,"该用户审核未通过");

}

//查询用户状态

if (byUsername.getState()!=1){

return error(30000,"用户非可用状态，不能登录");

}

String md5password = service.encryption(password);

if (byUsername.getPassword().equals(md5password)) {

// 存储Token到数据库

AccessToken accessToken = new AccessToken();

accessToken.setToken(UUID.randomUUID().toString().replaceAll("-", ""));

accessToken.setUser_id(byUsername.getUserId());

tokenService.save(accessToken);

// 返回用户信息

JSONObject user = JSONObject.parseObject(JSONObject.toJSONString(byUsername));

user.put("token", accessToken.getToken());

JSONObject ret = new JSONObject();

ret.put("obj",user);

return success(ret);

} else {

return error(30000, "账号或密码不正确");

}

public String select(Map<String,String> query,Map<String,String> config){

StringBuffer sql = new StringBuffer("select ");

sql.append(config.get(FindConfig.FIELD) == null || "".equals(config.get(FindConfig.FIELD)) ? "*" : config.get(FindConfig.FIELD)).append(" ");

sql.append("from ").append("`").append(table).append("`").append(toWhereSql(query, "0".equals(config.get(FindConfig.LIKE))));

if (config.get(FindConfig.GROUP_BY) != null && !"".equals(config.get(FindConfig.GROUP_BY))){

sql.append("group by ").append(config.get(FindConfig.GROUP_BY)).append(" ");

}

if (config.get(FindConfig.ORDER_BY) != null && !"".equals(config.get(FindConfig.ORDER_BY))){

sql.append("order by ").append(config.get(FindConfig.ORDER_BY)).append(" ");

}

if (config.get(FindConfig.PAGE) != null && !"".equals(config.get(FindConfig.PAGE))){

int page = config.get(FindConfig.PAGE) != null && !"".equals(config.get(FindConfig.PAGE)) ? Integer.parseInt(config.get(FindConfig.PAGE)) : 1;

int limit = config.get(FindConfig.SIZE) != null && !"".equals(config.get(FindConfig.SIZE)) ? Integer.parseInt(config.get(FindConfig.SIZE)) : 10;

sql.append(" limit ").append( (page-1)*limit ).append(" , ").append(limit);

}

log.info("[{}] - 查询操作，sql: {}",table,sql);

return sql.toString();

}

public List selectBaseList(String select) {

List<Map<String,Object>> mapList = baseMapper.selectBaseList(select);

List<E> list = new ArrayList<>();

for (Map<String,Object> map:mapList) {

list.add(JSON.parseObject(JSON.toJSONString(map),eClass));

}

return list;

}

4.1.3用户注册界面

不是医院挂号预约管理系统中正式用户的是可以在线进行注册的，如果你没有本医院挂号预约管理系统的账号的话，添加“注册”，当填写上自己的账号+密码+确认密码+昵称+邮箱+手机号等后再点击“注册”按钮后将会先验证输入的有没有空数据，再次验证密码和确认密码是否是一样的，最后验证输入的账户名和数据库表中已经注册的账户名是否重复，只有都验证没问题后即可用户注册成功。其用用户注册界面展示如下图4-3所示。

图4-2用户注册界面图

注册关键代码如下所示。

/**

* 注册

* @return

@PostMapping("register")

public Map<String, Object> signUp(HttpServletRequest request) throws IOException {

// 查询用户

Map<String, String> query = new HashMap<>();

Map<String,Object> map = service.readBody(request.getReader());

query.put("username",String.valueOf(map.get("username")));

List list = service.selectBaseList(service.select(query, new HashMap<>()));

if (list.size()>0){

return error(30000, "用户已存在");

}

map.put("password",service.encryption(String.valueOf(map.get("password"))));

service.insert(map);

return success(1);

}

public Map<String,Object> readBody(BufferedReader reader){

BufferedReader br = null;

StringBuilder sb = new StringBuilder("");

try{

br = reader;

String str;

while ((str = br.readLine()) != null){

sb.append(str);

}

br.close();

String json = sb.toString();

return JSONObject.parseObject(json, Map.class);

}catch (IOException e){

e.printStackTrace();

}finally{

if (null != br){

try{

br.close();

}catch (IOException e){

e.printStackTrace();

}

return null;

}

public void insert(Map<String,Object> body){

E entity = JSON.parseObject(JSON.toJSONString(body),eClass);

baseMapper.insert(entity);

log.info("[{}] - 插入操作：{}",entity);

}

4.1.4医疗新闻界面

用户点击“医疗新闻”菜单显示所有的医疗新闻信息，可以按照条件进行医疗新闻的筛选或者输入关键词进行局部搜索，点击可以进入医疗新闻详细展示界面，在此界面用户可以收藏、点赞和评论。界面如图4-4所示。

图4-4医疗新闻界面图

4.1.5医生出诊详情界面

用户可以查看医生出诊，在查询到自己想要了解的医生出诊的时候，可以进入查看详细的介绍，点击“挂号预约”这一按钮以后会跳转到挂号预约信息填写的界面，根据提示填写好挂号预约的信息，点击“提交”以后挂号预约就完成了，在医生出诊详情这个界面，同时支持用户对喜欢的医生出诊进行评论的功能，医生出诊详情展示页面如图4-5所示。

图4-5医生出诊详情界面图

4.1.6 科室介绍详情界面

用户可以查看科室介绍信息，在查询到自己想要了解的科室介绍的时候，可以进入查看详细的介绍。界面如下图4-6所示。

图4-6 科室介绍详情界面图

4.1.7我的账户界面

当用户点击右上角“我的”这个按钮，会出现子菜单，点击“我的账户”可以对个人的资料、登录系统的密码以及自己收藏的信息进行设置管理，我的账户界面如下图4-7所示。

图4-7我的账户界面图

4.2管理员功能模块

医院挂号预约管理系统的理员拥有最高的权限，可以对用户信息、系统信息以及医院挂号预约管理系统相关信息进行管控。

4.2.1登录界面

管理员在后台可以通过账号和密码进行登录，管理员的账号和密码是在数据库中直接设定的。界面展示如下图4-8所示。

图4-8登录界面图

4.2.2系统用户管理界面

管理员点击“系统用户”这一菜单会显示管理员、医生用户、普通用户这三个子菜单，管理员可以对这三个角色的信息进行增删改查操作。界面如下图4-9所示。

图4-9系统用户管理界面图

系统用户管理管理关键代码如下所示。

public List selectBaseList(String select) {

List<Map<String,Object>> mapList = baseMapper.selectBaseList(select);

List<E> list = new ArrayList<>();

for (Map<String,Object> map:mapList) {

list.add(JSON.parseObject(JSON.toJSONString(map),eClass));

}

return list;

}

4.2.3系统公告管理界面

管理员点击“系统公告管理”菜单可以查看到系统中的所有系统公告，对已经存在的系统公告，管理员可以修改，也可以添加新的系统公告或者删除系统公告。界面如下图4-10所示。

图4-10系统公告管理界面图

4.2.4资源管理界面

管理员点击“资源管理”菜单能够对其下子菜单医疗新闻和新闻的分类进行增删改查。界面如下图4-11所示。

图4-11资源管理界面图

4.2.5模块管理界面

医院挂号预约管理系统中的管理人员在“模块管理”这一菜单下是可以对医院挂号预约管理系统内的医生出诊、科室、挂号信息、科室介绍进行管控的，其管理界面如下图4-12所示。

图4-12模块管理界面图

模块管理关键代码如下所示。

@RequestMapping("/get_obj")

public Map<String, Object> obj(HttpServletRequest request) {

List resultList = service.selectBaseList(service.select(service.readQuery(request), service.readConfig(request)));

if (resultList.size() > 0) {

JSONObject jsonObject = new JSONObject();

jsonObject.put("obj",resultList.get(0));

return success(jsonObject);

} else {

return success(null);

}

5系统测试

5.1系统测试的目的

系统开发到了最后一个阶段那就是系统测试，系统测试对软件的开发其实是非常有必要的。因为没什么系统一经开发出来就可能会尽善尽美，再厉害的系统开发工程师也会在系统开发的时候出现纰漏，系统测试能够较好的改正一些bug，为后期系统的维护性提供很好的支持。通过系统测试，开发人员也可以建立自己对系统的信心，为后期的系统版本的跟新提供支持。

5.2 系统测试用例

系统测试包括：用户登录功能测试、医生出诊展示功能测试、医生出诊添加、医生出诊搜索、密码修改功能测试，如表5-1、5-2、5-3、5-4、5-5所示：

用户登录功能测试：

表5-1 用户登录功能测试表

用例名称	用户登录系统
目的	测试用户通过正确的用户名和密码可否登录功能
前提	未登录的情况下
测试流程	1) 进入登录页面 2) 输入正确的用户名和密码
预期结果	用户名和密码正确的时候，跳转到登录成功界面，反之则显示错误信息，提示重新输入
实际结果	实际结果与预期结果一致

医生出诊查看功能测试：

表5-2 医生出诊查看功能测试表

用例名称	医生出诊查看
目的	测试医生出诊查看功能
前提	用户登录
测试流程	点击医生出诊列表
预期结果	可以查看到所有医生出诊
实际结果	实际结果与预期结果一致

管理员添加医生出诊界面测试：

表5-3 管理员添加医生出诊界面测试表

用例名称	医生出诊发布测试用例
目的	测试医生出诊发布功能
前提	用户正常登录情况下
测试流程	1）点击医生出诊管理就，然后点击添加后并填写信息。 2）点击进行提交。
预期结果	提交以后，页面首页会显示新的医生出诊
实际结果	实际结果与预期结果一致

医生出诊搜索功能测试：

表5-4医生出诊搜索功能测试表

用例名称	医生出诊搜索测试
目的	测试医生出诊搜索功能
前提	无
测试流程	1）在搜索框填入搜索关键字。 2）点击搜索按钮。
预期结果	页面显示包含有搜索关键字的医生出诊
实际结果	实际结果与预期结果一致

密码修改功能测试：

表5-5 密码修改功能测试表

用例名称	密码修改测试用例
目的	测试管理员密码修改功能
前提	管理员用户正常登录情况下
测试流程	1）管理员密码修改并完成填写。 2）点击进行提交。
预期结果	使用新的密码可以登录
实际结果	实际结果与预期结果一致

5.3 系统测试结果

通过编写医院挂号预约管理系统的测试用例，已经检测完毕用户登录模块、医生出诊查看模块、医生出诊添加模块、医生出诊搜索模块、密码修改功能测试，通过这5大模块为医院挂号预约管理系统的后期推广运营提供了强力的技术支撑。

结论

至此，医院挂号预约管理系统已经结束，在开发前做了许多的准备，在本系统的设计和开发过程中阅览和学习了许多文献资料，从中我也收获了很多宝贵的方法和设计思路，对系统的开发也起到了很重要的作用，系统的开发技术选用的都是自己比较熟悉的，比如Web、ssm技术、MYSQL，这些技术都是在以前的学习中学到了，其中许多的设计思路和方法都是在以前不断地学习中摸索出来的经验，其实对于我们来说工作量还是比较大的，但是正是由于之前的积累与准备，才能顺利的完成这个项目，由此看来，积累经验跟做好准备是十分重要的事情。

当然在该系统的设计与实现的过程中也离不开老师以及同学们的帮助，正是因为他们的指导与帮助，我才能够成功的在预期内完成了这个系统。同时在这个过程当中我也收获了很多东西，此系统也有需要改进的地方，但是由于专业知识的浅薄，并不能做到十分完美，希望以后有机会可以让其真正的投入到使用之中。

参考文献

[1]付恩狄,姚明亮,梁宇柔,彭伟军.基于JAVA技术的设备绝缘状态自动化监控方法[J].电气自动化,2023,45(02):36-38+41.

[2]赵将.Java语言在计算机软件开发中的应用[J].数字技术与应用,2023,41(03):160-162.DOI:10.19695/j.cnki.cn12-1369.2023.03.46.

[3]张浩.SSM框架在Web应用开发中的设计与实现研究[J].电脑知识与技术,2023,19(08):52-54.DOI:10.14004/j.cnki.ckt.2023.0353.

[4]刘丹青,李超,王青海.基于Java技术的藏汉双语学前教育云平台设计与实现[J].信息技术,2023,47(02):17-23.DOI:10.13274/j.cnki.hdzj.2023.02.004.

[5]伍德鹏,李佩学.基于SSM框架的高职院校教学办公用品管理信息系统设计研究[J].轻工科技,2023,39(01):99-101.

[6]常婉纶,谈姝辰,屈小娥,田召.基于SSM框架的二级学院教科研信息共享系统的设计与实现[J].电脑知识与技术,2022,18(34):39-41.DOI:10.14004/j.cnki.ckt.2022.2208.

[7]巩蕾.医院挂号预约管理系统设计[J].电脑编程技巧与维护,2022(02):66-68+80.DOI:10.16184/j.cnki.comprg.2022.02.033.

[8]林易康, 基于Java的web应用程序控制管理软件. 湖北省,武汉东湖学院,2021-10-01.

[9]王洪平. 面向医院和诊所经营者的智能排班和患者预约管理系统[P]. 广东省：CN113284595A,2021-08-20.

[10]陈小兵. 一种面向诊所经营者的智能排班和患者预约管理系统[P]. 浙江省：CN113223685A,2021-08-06.

[11]白新宇, 基于Java技术短信发送性能测试方式及系统. 湖北省,武汉东湖学院,2021-05-01.

[12]Witsarut Sriratana,Vittaya Khagwian,Sutham Satthamsakul. Analysis of Electric Current by Using MySQL Database on Web Server for Machine Performance Evaluation: A Case Study of Air Conditioning System[J]. 제어로봇시스템학회 국제학술대회 논문집,2020.

[13]. Information Technology - Data Management; Data on Data Management Reported by Researchers at Port Said University (Performance Evaluation of Iot Data Management Using Mongodb Versus Mysql Databases In Different Cloud Environments)[J]. Computer Technology Journal,2020.

[14]Margaretha Ohyver,Jurike V. Moniaga,Iwa Sungkawa,Bonifasius Edwin Subagyo,Ian Argus Chandra. The Comparison Firebase Realtime Database and MySQL Database Performance using Wilcoxon Signed-Rank Test[J]. Procedia Computer Science,2019,157(C).

[15]方春露,杨文琦,陈滔等. 基于Javaweb技术广东省学生体质争优运动处方数据库和视频库的构建[C]//中国生理学会运动生理学专业委员会,北京体育大学.2018年中国生理学会运动生理学专业委员会会议暨“科技创新与运动生理学”学术研讨会论文集.2018年中国生理学会运动生理学专业委员会会议暨“科技创新与运动生理学”学术研讨会论文集,2018:161-162.

[16]贾晶晶,柴磊,鲁世清.医院专家分时段预约挂号系统的设计与实现[J].信息与电脑(理论版),2016(23):154-156.

[17]杨博.浅谈医院预约挂号管理系统的应用[J].世界最新医学信息文摘,2016,16(41):167.

致谢

逝者如斯夫，不舍昼夜。转眼间，大用户用户活便已经接近尾声，人面对着离别与结束，总是充满着不舍与茫然，我亦如此，仍记得那年秋天，我迫不及待的提前一天到了学校，面对学校巍峨的大门，我心里充满了期待：这里，就是我新生活的起点吗？那天，阳光明媚，学校的欢迎仪式很热烈，我面对着一个个对着我微笑的同学，仿佛一缕缕阳光透过胸口照进了我心里，同时，在那天我认识可爱的室友，我们携手共同度过了这难忘的两年。如今，我望着这篇论文的致谢，不禁又要问自己：现在，我们就要说再见了吗？

感慨莫名，不知所言。遥想当初刚来学校的时候，心里总是想着工科学校会过于板正，会缺乏一些柔情，当时心里甚至有一点点排斥，但是随着我对学校的慢慢认识与了解，我才认识到了她的美丽，她的柔情，并且慢慢的喜欢上了这个校园，但是时间太快了，快到我还没有好好体会她的美丽便要离开了，但是她带给我的回忆，永远不会离开我，也许真正离开那天我的眼里会满含泪水，我不是因为难过，我只是想将她的样子映在我的泪水里，刻在我的心里。最后，感谢我的老师们，是你们教授了我们知识与做人的道理；感谢我的室友们，是你们陪伴了我如此之久；感谢每位关心与支持我的人。

少年，追风赶月莫停留，平荒尽处是春山。

请关注点赞+私信博主，免费领取项目源码