1. Screenshots of the system (if you need a demo video, you can chat privately)
The traditional method of managing information firstly takes more time, secondly, the data error rate is relatively high, and it is also difficult to change the wrong data, and finally, retrieving data is laborious and laborious. Therefore, installing the scenic spot homestay reservation system software on the computer to play its role in efficient information processing can standardize the information management process and make the management work systematic and procedural. At the same time, the effective use of the scenic spot homestay reservation system can help managers Process information accurately and quickly.
The hotel booking system for scenic spots is also very careful in the selection of development tools. In order to facilitate development and implementation, the selected development tool is Eclipse, and the selected database tool is Mysql. In this way, the development environment is set up to realize the function of the reservation system of the scenic spot homestay. Among them, administrators manage users and news announcements.
Scenic homestay reservation system is an application system designed and realized by using software development technology. It can achieve fast goals in information processing. Whether it is for processing requirements such as data addition, data maintenance and statistics, and data query, the scenic spot homestay reservation system can Can be easily dealt with.
Keywords : Scenic B & B reservation system; SpringBoot framework, system analysis, database design
directory
1.1 Motivation for topic selection
1.3 Arrangement of paper structure
Chapter 2 Development Environment and Technology
3.1.1 Operation Feasibility Analysis
3.1.2 Economic Feasibility Analysis
3.1.3 Technical Feasibility Analysis
3.3 System performance analysis
4.1 Interface Design Principles
4.2 Functional structure design
4.3.2 Database physical design
Chapter 5 System Implementation
5.1 User Information Management
5.2 Room information management
5.3 Attraction information management
Chapter 1 Introduction _
1.1 Motivation for topic selection
The current network technology and software technology all have a mature theoretical basis, and there are also software developed by various technologies on the market. These software are used in various fields, including the fields of life and work. With the widespread use of computers and notebooks, as well as the improvement and upgrading of various computer hardware, the performance of computers and notebooks on the market has been improved, and the software that can be supported has gradually increased. The role of geoinformation processing is very popular among people. For public transport information, it is inappropriate to deal with a huge amount of information through manual processing. Firstly, it takes a lot of time, and secondly, the data error rate is relatively high, and it is relatively difficult to change the wrong data. Difficulty, and finally, retrieving data is laborious. Therefore, in order to solve the above problems, it is necessary to establish a scenic spot homestay reservation system to standardize the bus information management process, so that the management work can be systematized and programmed. At the same time, the effective use of the scenic spot homestay reservation system can help managers process information accurately and quickly .
1.2 Purpose and significance
The scenic homestay reservation system can centrally manage bus information, which can truly avoid the defects of traditional management. Scenic homestay reservation system is an application system designed and realized by using software development technology. It can achieve fast goals in information processing. Whether it is for processing requirements such as data addition, data maintenance and statistics, and data query, the scenic spot homestay reservation system can Can be easily dealt with. Therefore, the use of the reservation system for homestays in scenic spots is the best way to upgrade bus information management. It can meet the convenience requirements of information processing, and can also standardize the process of information processing, making transaction processing a simple matter in the hands of managers, rather than the difficult thing that was previously handled manually. Although the scenic spot homestay reservation system has relatively complete functions, it also requires managers to use their spare time to improve their own quality and personal ability. When operating the scenic spot homestay reservation system, they can maximize the use of the functions provided by the scenic spot homestay reservation system, so that the system can meet high requirements. While processing data efficiently, it can also run stably at all times, and can also ensure the reliability of data and the quality of data processing.
1.3 Arrangement of paper structure
This article is divided into 6 chapters in total, and each chapter describes different contents of the system. Next, the research content of this paper is described.
Chapter 1: This chapter is the introduction part of the thesis. Explain the system to be developed from the perspective of the background and significance of the topic.
Chapter 2: This chapter is the technical introduction part. Elaborate the system from the point of view of the technical knowledge that the system needs to use.
Chapter 3: This chapter is the system analysis part. Elaborate the system from the perspectives of system feasibility analysis, system function and performance analysis.
Chapter 4: This chapter is the system design part. The system is expounded from the perspective of system function structure and database design.
Chapter 5: This chapter is the system implementation part. The system is described from the perspective of the operating effect of the system function modules.
Chapter 6: This chapter is the system testing part. The system is described from the perspective of testing system functions and system testing methods.
Chapter 2 Development Environment and Technology
The development of a reservation system for scenic spots needs to build a programming environment. It also needs to conduct investigations, analyze various related technologies, and select technologies and tools suitable for the development of this system.
2.1 MYSQL database
After the topic is determined to be an application program, the design and analysis will begin step by step. This topic requires the database as a data management tool and data carrier. From program function analysis to data analysis, choosing an appropriate relational database is an important part of the current choice. There are not many options for relational databases. There are two from Oracle, two from Microsoft, and one from IBM, that is, these five. Functions and differences do not affect the choice of databases, because these databases can implement applications. If the function is required, then we can only comprehensively consider which database is more suitable from other aspects. As far as the computer hardware used for development is concerned, I bought it when I was a freshman. I didn’t have much money to buy a better computer. It was just for learning. So after so many years of use, the computer has aged and its performance has declined. It is quite powerful, and there are still a lot of learning materials that need to be used. I am facing graduation, and choosing a school computer room is not a long-term plan. It is the most important to choose an old laptop with a suitable database for learning and developing current applications. The result of comprehensive consideration is to choose the MySQL database as the application database, because the MySQL database is small in size and occupies a small amount of memory, does not affect the operation of other software on the computer, and does not need to reinstall the system because of the installation and maintenance of the MySQL database. MySQL database.
2. 2 Introduction to Tomcat
When I first started learning the Java language, I didn't know that Tomcat was still there. Various grammars and various outputs were output on the console. When the Java website was developed, it was inevitable to learn the Tomcat server. To be precise, Tomcat is not a server. It can be said to be a Vue engine or a container. These are more appropriate academically or in principle, but in actual work, Tomcat is used as a web server, because it can realize the website. Publish and run. Because of the working principle, Tomcat generally exists as a lightweight server for small and medium-sized enterprises and the concurrency is not prominent. For example, application systems in certain industries do not have many clients and do not require many connections. , generally use Tomcat. Multiple websites can be configured in Tomcat, and the suffix of the configuration file is config, which is similar to the structure of XML and is relatively clear. Whenever a new version of Java is released, Tomcat will also be upgraded to match the version of Java. The current version of Tomcat has reached version 10. The Tomcat logo is a little yellow cat. When the Tomcat configuration is successful and the general test can see this kitten, it is considered successful, and the next step of configuration can be performed. The Tomcat server is quite suitable for Java website development.
2.3 vue technology
Vue technology allows beginners to start writing dynamic websites as soon as possible. It does not need to become an advanced Java programmer to write code, which greatly improves the efficiency of learning and writing. It becomes possible to focus on web page developers and back-end logic development for separate and cooperative development, which reduces the cost of learning. If there is no need to consider the program running, interpreting and compiling stages, the vue web page itself can be understood as an ordinary Servlet. The Vue structure is mainly divided into two aspects, one is the exclusive Vue engine, in layman's terms, it is a thing that can realize the interpretation of Vue after compiling, and the other is the web server. Vue running and compiling requires the cooperation and cooperation between the Vue engine and the web server. Of course, their division of labor is also very clear, so that it can really run. The vue container and engine have Tomcat. This Tomcat actually also has the part of Apache statically interpreting the code. Although it looks similar in effect, it is actually two completely different tools, and the directories in the file system are also different. Of course, if there is Special requirements can also be configured in a special way, and the configuration is relatively flexible. Although Tomcat can run web pages for customers to visit after deploying the website, Tomcat is only a vue engine rather than a web server. For example, both JRUN and Resin are Vue engines, and the responsibility of the web server is relatively simple, which is to process client requests and return to the client to display the processed data of the request. The vue engine can run websites written in pure HTML, and can also run dynamic websites written in vue. It is only more efficient than a simple web server. It is much more powerful, and it is nothing to improve a little efficiency. For the functions that must be realized, Vue technology is chosen.
2.4 Spring Boot framework
Java has always been criticized for being bloated and troublesome. When we are still working hard to build the project, Python programmers may have already written the functions. The reason for this is two points: complex configuration. The various configurations of the project are actually a loss during development, because we are thinking about Spring feature configuration Thinking needs to be switched between solving business problems and solving business problems, so writing configuration squeezes the time for writing application logic. One is messy dependency management. Project dependency management is also a thankless task. Deciding which libraries to use in a project is enough of a headache, but knowing which versions of those libraries don't conflict with other libraries is a difficult problem. Moreover, dependency management is also a loss, adding dependencies is not writing application code. Once the wrong dependent version is selected, the ensuing incompatibility problem will undoubtedly be a productivity killer. And SpringBoot makes all this a thing of the past! Spring Boot simplifies Spring-based application development, and only needs to be "run" to create an independent, production-level Spring application. Spring Boot provides out-of-the-box settings for the Spring platform and third-party libraries (provides default settings, and the package that stores the default configuration is the starter), so that we can start simply. Most Spring Boot applications require very little Spring configuration. We can use SpringBoot to create a java application and start it with java –jar to get a production-level web project.
Chapter 3 System Analysis
The needs of users and other systems similar to this system that exist in the market can be used as reference materials in system analysis. Analysts can determine the functions of this system and analyze the performance of this system based on these information.
3.1 Feasibility analysis
Although the system is produced according to the user's requirements, it is necessary to analyze its feasibility before confirming the production.
3.1.1 Operation Feasibility Analysis
I am familiar with the tools needed to develop this system, so I can use these tools to fully develop the hotel booking system for scenic spots. In addition, in terms of functions, the hotel booking system in scenic spots basically completes the processing of information, covering addition, modification, deletion, etc., and the operator is faced with various functional operation interfaces, not the coding background, so ordinary users Information processing can be easily completed through the operation interface. Therefore, the system operation is feasible.
3.1.2 Economic Feasibility Analysis
To develop this system, there is no investment in purchasing development tools. Because the development tools used are all downloaded and installed on my computer from Baidu in advance, with the maturity of software development technology, the coding of system function realization is also modularized, which is easy to obtain through major software development websites, and through A small part of code changes is applied to this system, which does not require capital investment. At the same time, the structure of this system development uses B/S, and the cost can be ignored.
3.1.3 Technical Feasibility Analysis
The software required by this system includes Eclipse, Tomcat, Mysql, etc. These tools have been used and used. As for JAVA, B/S, vue, Html and other technologies, the library has corresponding books for reference and learning, plus the usual classroom These techniques are explained in the small programming projects I learned. In addition, I also exercised my programming skills from the course design assignments. So technically, it is possible to complete the programming and development of the hotel booking system in scenic spots.
Through the above analysis, it has been determined that the system is economically feasible, the system is technically feasible, and the system is operationally feasible. From this, it can be concluded that under the current conditions, the design and implementation of the scenic homestay reservation system can continue.
3.2 System flow analysis
When the system processes data, its internal operation logic also needs to be displayed using corresponding tools.
On the data entry page of this system, there are corresponding inspection rules for each piece of data provided by the operator. For example, the data information cannot have illegal characters, or the data that should be Chinese characters cannot be replaced by letters, and there are restrictions on the data content. The length, etc. are standardized, and such inspection rules that can ensure the accuracy of the data are written in advance when coding. The process of adding data is shown in the figure below. If the data has been saved into the database, it means that the content and format of the data provided by the operator meet the requirements.
Figure 3.1 Add information flow chart
Many times, in the face of a large amount of data in the system, it is inevitable that some errors will be found, so it is necessary to correct the errors in time. This system also provides the function of modifying the data in the later stage. The process is shown in the figure below. But the updated data also needs to pass the data validity check. If it can be finally written into the database, it means that the modified data meets the requirements.
Figure 3.2 Modify information flow chart
Faced with a large amount of data in the database, in the foreground of the system, if you want to quickly obtain the required information, you need to use the query function. Its process is shown in the figure below. This function requires the operator to input keywords in advance. When the background database of the system saves the data matching the keywords, it will be displayed in time, and the whole process takes a very short time.
Figure 3.3 Query information flow chart
3.3 System performance analysis
The analysis of the performance requirements of the scenic spot homestay reservation system is mainly analyzed from the following five angles, which are the practicability of the system, the adaptability of the system, the ease of operation of the system, the security of the system and the ease of maintenance of the system.
Performance requirement 1: The practicability of the system. This system mainly allows managers to centrally process relevant information, and can provide convenient and quick operations such as adding information and editing information. While improving the work efficiency of information managers, it can also reduce management costs and greatly reduce the daily tedious workload of managers.
Performance requirement two: system adaptability, this system does not have high requirements for the operating environment, and can be widely used in daily life. Because users can run this system as long as they build an operating environment on their daily computers or portable notebooks, and the basic functions provided by the system, including adding and modifying, can be operated at any time.
Performance requirement three: the ease of operation of the system. The functions provided by this system are the same as those of the same type of system. It also has simple addition, deletion and modification operations. The logic of the operation process is also in line with the needs of users. Users will use this system to manage data. Very smooth.
Performance requirement 4: System security. The safety factor of the system must meet the standard in data storage and management. In the design and coding stage, through the allocation of user rights, the functions of the system are allocated according to the roles of different users. When developing the system, guide different users to enter different operation interfaces by writing safety-verified code modules. It is also possible to encrypt and save basic user information including login account passwords, etc., which can be realized by using the mature MD5 encryption technology commonly used today.
Performance requirement five: easy maintenance of the system. In the later operation of the system, a lot of data information will be generated according to the user's operation. In order to facilitate maintenance, it is required that these data can be exported from the database through tools. For some stages Data can be deleted in batches to achieve the goal of light-load data processing, making the system lighter.
Chapter 4 System Design
The well-designed systems on the market have a common feature, that is, the theme is clear and prominent. Through the concise and clear layout of the page, the content of the page, including text language, or video pictures and other elements, can clearly express the theme of the system. So that visiting users do not need to spend too much energy and time looking for the content they need.
4.1 Interface Design Principles
Generally speaking, most users use the system, some want to obtain the required information from the system, and some use the services provided by the system. Therefore, in order to improve the user experience and increase the utilization rate of the system, the following principles should be followed when designing the system interface.
The first point is to analyze the users, understand the purpose and way of using the system, consider the reading habits of most users, and design a Z-shaped or F-shaped structure to facilitate users to obtain information.
The second point: design effective navigation, which includes the display of navigation bars on each page, and sometimes the navigation bar can be designed at the bottom of the page. When the user enters a specific page, it is necessary to design a corresponding location prompt, in the page For a special location, you need to design a return link, which can return to the previous page or the home page, etc.
The third point: use a unified design scheme for the entire system, including the consistency of the color scheme, the similarity of the page templates, etc., and the description of the same operations and technical terms should also be consistent throughout the system.
The fourth point: the designed interface should ensure that the conveyed content is clear and accurate. It is necessary to avoid designing a lot of content on the same page. In addition, the system content can be accurately classified, and the position where the user's vision is concentrated on the page can be used to display important information.
As a beginner, I don't have that much design experience, but I can use the interface design principles mentioned above to design a better system, which can give users a good experience.
4.2 Functional structure design
In order to make the coding of the system go smoothly, the functions of this system are subdivided and designed, and the designed system function structure is shown in the figure below.
Figure 4.1 System function structure diagram
4.3 Database design
Developing a system also requires designing the database in advance. The database here is a collection of related data, and these data stored together are also organized in a certain way. At present, the database can serve a variety of applications because of its optimal storage method and low data redundancy rate. Although the database provides information storage services for the program, it can also maintain a high degree of independence from the program. All in all, the database has experienced a long period of development, from being unknown at the beginning to now being well known, its related technologies are becoming more mature, and it also has a solid theoretical foundation.
4.3.1 Database conceptual design
This part of the content needs to be completed with the help of database relationship diagrams, and tools that specialize in drawing database relationship diagrams are also required. For example, Visio tools can design ER diagrams (database relationship diagrams). The design of the database also needs to be carried out according to the design process. First, it is necessary to complete the determination of the entity according to the requirements, analyze the characteristics of the entity, and determine the relationship between the entities. Finally, the ER diagram of the system is drawn using the representation method of the ER model. Whether you use Edraw software or Visio tool, the symbols for ER models are the same. Usually, rectangles represent entities, relationships between entities are represented by diamond symbols, and the attributes of entities, that is, the characteristics of entities, are represented by symbol ellipses. Finally use straight lines to connect symbols like rectangles, rhombuses and ellipses. Then start to draw the ER diagram of this system.
(1) The figure below shows the user entity and its attributes.
Figure 4.1 User entity attribute graph
(2) The figure below shows the dictionary table entity and its attributes.
Figure 4.2 Dictionary table entity attribute diagram
(3) The figure below shows the room information entity and its attributes.
Figure 4.3 Room Information Entity Property Diagram
(4) The figure below shows the attraction reservation entity and its attributes.
Figure 4.4 Attraction Reservation Entity Attribute Map
(5) The figure below shows the attraction feedback entity and its attributes.
Figure 4.5 Attraction Feedback Entity Attribute Map
(6) The figure below shows the food feedback entity and its attributes.
Figure 4.6 Food Feedback Entity Attribute Map
(7) The figure below shows the announcement entity and its attributes.
Figure 4.7 Announcement Entity Attribute Diagram
(8) The figure below shows the work record entity and its attributes.
Figure 4.8 Work Record Entity Attribute Diagram
(9) The figure below shows the room feedback entity and its attributes.
Figure 4.9 Room Feedback Entity Property Diagram
(10) The figure below shows the staff entity and its attributes.
Figure 4.10 Worker Entity Attribute Diagram
(11) The figure below shows the room reservation entity and its attributes.
Figure 4.11 Room Reservation Entity Attribute Diagram
(12) The figure below shows the scenic spot information entity and its attributes.
Figure 4.12 Attraction Information Entity Attribute Diagram
(13) The figure below shows the food information entity and its attributes.
Figure 4.13 Food information entity attribute diagram
(14) The figure below shows the user table entity and its attributes.
Figure 4.14 User table entity attribute diagram
(15) The figure below shows the gourmet reservation entity and its attributes.
Figure 4.15 Gourmet Reservation Entity Attribute Map
Table 4.1 Dictionary table table
| serial number |
column name |
type of data |
illustrate |
allow empty |
| 1 |
Id |
Int |
id |
no |
| 2 |
dic_code |
String |
field |
yes |
| 3 |
dic_name |
String |
field name |
yes |
| 4 |
code_index |
Integer |
coding |
yes |
| 5 |
index_name |
String |
encoding name |
yes |
| 6 |
super_id |
Integer |
parent field id |
yes |
| 7 |
beizhu |
String |
Remark |
yes |
| 8 |
create_time |
Date |
creation time |
yes |
Table 4.2 Room information table
| serial number |
column name |
type of data |
illustrate |
allow empty |
| 1 |
Id |
Int |
id |
no |
| 2 |
fangjian_name |
String |
room name |
yes |
| 3 |
fangjian_photo |
String |
room picture |
yes |
| 4 |
fangjian_tese |
String |
room features |
yes |
| 5 |
fangjian_peizhi |
String |
room configuration |
yes |
| 6 |
fangjian_money |
BigDecimal |
price (day) |
yes |
| 7 |
fangjian_types |
Integer |
Room type |
yes |
| 8 |
fangjian_number |
Integer |
number of rooms remaining |
yes |
| 9 |
fangjian_clicknum |
Integer |
The number of clicks |
yes |
| 10 |
fangjian_content |
String |
room details |
yes |
| 11 |
create_time |
Date |
creation time |
yes |
Table 4.3 Room Feedback Form
| serial number |
column name |
type of data |
illustrate |
allow empty |
| 1 |
Id |
Int |
id |
no |
| 2 |
fangjian_id |
Integer |
Room |
yes |
| 3 |
yonghu_id |
Integer |
user |
yes |
| 4 |
fangjian_liuyan_text |
String |
Feedback content |
yes |
| 5 |
reply_text |
String |
reply content |
yes |
| 6 |
insert_time |
Date |
feedback time |
yes |
| 7 |
update_time |
Date |
Response Time |
yes |
| 8 |
create_time |
Date |
creation time |
yes |
Table 4.4 Room Reservation Form
| serial number |
column name |
type of data |
illustrate |
allow empty |
| 1 |
Id |
Int |
id |
no |
| 2 |
fangjian_id |
Integer |
Room |
yes |
| 3 |
yonghu_id |
Integer |
user |
yes |
| 4 |
fnagjian_yuye_time |
Date |
appointment date |
yes |
| 5 |
fnagjian_yuye_text |
String |
Appointment Remarks |
yes |
| 6 |
fnagjian_tiwen |
BigDecimal |
recent body temperature |
yes |
| 7 |
fnagjian_text |
String |
recent itinerary |
yes |
| 8 |
fnagjian_yuye_yesno_types |
Integer |
Audit results |
yes |
| 9 |
fnagjian_yuye_yesno_text |
String |
review feedback |
yes |
| 10 |
create_time |
Date |
creation time |
yes |
Table 4.5 Work Record Form
| serial number |
column name |
type of data |
illustrate |
allow empty |
| 1 |
Id |
Int |
id |
no |
| 2 |
gongzuorenyuan_id |
Integer |
工作人员 |
是 |
| 3 |
gongzuorenyuan_tiwen |
BigDecimal |
体温 |
是 |
| 4 |
insert_time |
Date |
添加时间 |
是 |
| 5 |
gongzuorenyuan_text |
String |
工作记录 |
是 |
| 6 |
gongzuorenyuan_delete |
Integer |
假删 |
是 |
| 7 |
create_time |
Date |
创建时间 |
是 |
表4.6工作人员表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
gongzuorenyuan_uuid_number |
String |
工号 |
是 |
| 3 |
gongzuorenyuan_name |
String |
工作人员姓名 |
是 |
| 4 |
gongzuorenyuan_photo |
String |
头像 |
是 |
| 5 |
gongzuorenyuan_phone |
String |
联系方式 |
是 |
| 6 |
gongzuorenyuan_email |
String |
邮箱 |
是 |
| 7 |
gongzuorenyuan_delete |
Integer |
假删 |
是 |
| 8 |
create_time |
Date |
创建时间 |
是 |
表4.7景点信息表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
jingdian_name |
String |
景点名称 |
是 |
| 3 |
jingdian_photo |
String |
景点图片 |
是 |
| 4 |
jingdian_types |
Integer |
景点类型 |
是 |
| 5 |
jingdian_money |
BigDecimal |
景点价格 |
是 |
| 6 |
jingdian_number |
Integer |
景点数量 |
是 |
| 7 |
jingdian_clicknum |
Integer |
点击次数 |
是 |
| 8 |
jingdian_content |
String |
景点详情 |
是 |
| 9 |
create_time |
Date |
创建时间 |
是 |
表4.8景点反馈表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
jingdian_id |
Integer |
景点 |
是 |
| 3 |
yonghu_id |
Integer |
用户 |
是 |
| 4 |
jingdian_liuyan_text |
String |
反馈内容 |
是 |
| 5 |
reply_text |
String |
回复内容 |
是 |
| 6 |
insert_time |
Date |
反馈时间 |
是 |
| 7 |
update_time |
Date |
回复时间 |
是 |
| 8 |
create_time |
Date |
创建时间 |
是 |
表4.9景点预约表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
jingdian_id |
Integer |
景点 |
是 |
| 3 |
yonghu_id |
Integer |
用户 |
是 |
| 4 |
jingdian_yuye_time |
Date |
预约日期 |
是 |
| 5 |
jingdian_yuye_text |
String |
预约备注 |
是 |
| 6 |
jingdian_yuye_yesno_types |
Integer |
审核结果 |
是 |
| 7 |
jingdian_yuye_yesno_text |
String |
审核反馈 |
是 |
| 8 |
create_time |
Date |
创建时间 |
是 |
表4.10美食信息表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
meishi_name |
String |
美食名称 |
是 |
| 3 |
meishi_photo |
String |
美食图片 |
是 |
| 4 |
meishi_types |
Integer |
美食类型 |
是 |
| 5 |
meishi_number |
Integer |
美食数量 |
是 |
| 6 |
meishi_money |
BigDecimal |
价格 |
是 |
| 7 |
meishi_clicknum |
Integer |
点击次数 |
是 |
| 8 |
meishi_content |
String |
美食详情 |
是 |
| 9 |
create_time |
Date |
创建时间 |
是 |
表4.11美食反馈表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
meishi_id |
Integer |
美食 |
是 |
| 3 |
yonghu_id |
Integer |
用户 |
是 |
| 4 |
meishi_liuyan_text |
String |
反馈内容 |
是 |
| 5 |
reply_text |
String |
回复内容 |
是 |
| 6 |
insert_time |
Date |
反馈时间 |
是 |
| 7 |
update_time |
Date |
回复时间 |
是 |
| 8 |
create_time |
Date |
创建时间 |
是 |
表4.12美食预约表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
meishi_id |
Integer |
美食 |
是 |
| 3 |
yonghu_id |
Integer |
用户 |
是 |
| 4 |
meishi_yuye_time |
Date |
预约日期 |
是 |
| 5 |
meishi_yuye_text |
String |
预约备注 |
是 |
| 6 |
meishi_yuye_yesno_types |
Integer |
审核结果 |
是 |
| 7 |
meishi_yuye_yesno_text |
String |
审核反馈 |
是 |
| 8 |
create_time |
Date |
创建时间 |
是 |
表4.13公告表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
news_name |
String |
公告标题 |
是 |
| 3 |
news_types |
Integer |
公告类型 |
是 |
| 4 |
news_photo |
String |
公告图片 |
是 |
| 5 |
insert_time |
Date |
公告时间 |
是 |
| 6 |
news_content |
String |
公告详情 |
是 |
| 7 |
create_time |
Date |
创建时间 |
是 |
表4.14用户表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
yonghu_name |
String |
用户姓名 |
是 |
| 3 |
yonghu_photo |
String |
头像 |
是 |
| 4 |
yonghu_phone |
String |
联系方式 |
是 |
| 5 |
yonghu_id_number |
String |
用户身份证号 |
是 |
| 6 |
yonghu_email |
String |
邮箱 |
是 |
| 7 |
yonghu_delete |
Integer |
假删 |
是 |
| 8 |
create_time |
Date |
创建时间 |
是 |
表4.15用户表表
| 序号 |
列名 |
数据类型 |
说明 |
允许空 |
| 1 |
Id |
Int |
id |
否 |
| 2 |
username |
String |
用户名 |
是 |
| 3 |
password |
String |
密码 |
是 |
| 4 |
role |
String |
角色 |
是 |
| 5 |
addtime |
Date |
新增时间 |
是 |
第5章 系统实现
这个环节需要使用前面的设计方案，包括对系统模块的设计，还有对程序后台的数据支持的数据库的设计等。不过这部分内容还是强调系统编码人员的开发能力，要把前面设计的内容通过编码的形式以一个完整的，可以运行的系统呈现出来。
功能模块的实现
5.1用户信息管理
如图5.1显示的就是用户信息管理页面，此页面提供给管理员的功能有：用户信息的查询管理，可以删除用户信息、修改用户信息、新增用户信息，
还进行了对用户名称的模糊查询的条件
图5.1 用户信息管理页面
5.2 房间信息管理
如图5.2显示的就是房间信息管理页面，此页面提供给管理员的功能有：查看已发布的房间信息数据，修改房间信息，房间信息作废，即可删除，还进行了对房间信息名称的模糊查询 房间信息信息的类型查询等等一些条件。
图5.2 房间信息管理页面
5.3景点信息管理
如图5.3显示的就是景点信息管理页面，此页面提供给管理员的功能有：根据景点信息进行条件查询，还可以对景点信息进行新增、修改、查询操作等等。
图5.3 景点信息管理页面
5.1公告信息管理
如图5.4显示的就是公告信息管理页面，此页面提供给管理员的功能有：根据公告信息进行新增、修改、查询操作等等。
图5.4 公告信息管理页面
第6章 系统测试
尽管系统在编码过程中，程序的编制人员也会对编程的功能模块进行逐个测试，但还是避免不了已经组合完成的系统整体没有错误。很多时候，面对功能繁多，逻辑复杂的系统时，系统的测试就需要不同人来测试，并设计一些故障来检验系统的应对能力，以及发现很多系统内部的潜在问题。并通过寻求解决办法去完善系统，确保系统质量。
6.1 系统测试方法
根据系统的测试流程，划分的系统测试方法有单元测试，集成测试，系统测试，验收测试。接下来就开始描述这些内容。
单元测试：这个测试环节在编码中用得最多，主要是编程人员进行的，通常对编码实现的各个子模块当成一个单元完成测试，主要基于代码的层面去发现问题，所以它也是白盒测试中的一种。
集成测试：这个环节进行的前提是，已经把系统的各个子模块进行了组合，然后把组合的完整系统进行测试，检验组成目标系统的各个子模块是否具备兼容性，还有目标系统是否根据预期目标正常运行。
系统测试：这个环节用到了黑盒测试，主要是检验系统的功能。并确定目标系统的各个功能是否运行正常。
验收测试：这个环节需要用户参与，让用户在系统操作界面上通过对不同数据的输入，检测系统的输出结果，以此检验目标系统与用户需求之间存在的差异程度。存在的差异越小，就代表着越符合用户的期望。
6.2 功能测试
景区民宿预约系统的目标用户最终面向的是系统的功能，所以检验本系统的功能也是一项重要任务，只有该系统的功能都能保证正常使用，才会吸引更多的用户来使用。
6.2.1 登录功能测试
本系统在编码时，提前在登录模块编写了安全验证规则，通过判断访问者提供的数据，引导符合要求的用户进入指定页面。测试表如下。错误的数据输入，在本系统中会得到及时的反馈提示。
表6.1 登录功能测试表
| 录入的数据 |
预期结果 |
实际结果 |
结论 |
|
| 管理员登录 |
用户名：空 |
提示请填写用户名 |
通过测试 |
|
| 管理员登录 |
用户名：guanliyuan 密码：空 |
提示请填写密码 |
通过测试 |
|
| 管理员登录 |
用户名：guanliyuan |
提示用户名密码不匹配 |
提示用户名密码不匹配 |
通过测试 |
| 管理员登录 |
用户名：guanliyuan |
提示登录成功，并跳转到功能操作区 |
提示登录成功，并跳转到功能操作区 |
通过测试 |
6.2.2 查询功能测试
在庞大的数据中，通过信息检索功能，可以帮助操作人员快速找到信息，节省操作时间。测试表如下。检索数据需要提取正确的关键词，一旦信息不匹配，就不容易找到信息。
表6.2 查询功能测试表
| 功能 |
录入的数据 |
预期结果 |
实际结果 |
结论 |
| 查询车次 |
提示信息不能为空 |
提示信息不能为空 |
通过测试 |
|
| 查询车次 |
线路名称：%&* |
提示无效的数据 |
提示无效的数据 |
通过测试 |
| 查询车次 |
线路名称：c006 |
查询出信息并显示 |
查询出信息并显示 |
通过测试 |
6.3 测试结果分析
通过测试，可以发现景区民宿预约系统具备完善的功能，同时具备易操作性和易维护性的特点，在系统安全性上也有比较健全的数据保护机制。至此，景区民宿预约系统可以投入使用。
结 论
之前在课本上学习过软件开发的知识，包括开发流程的了解，开发技术的学习，还有如何进行系统需求分析与设计，老师也选取了比较有代表性的管理系统在课堂上进行讲解，并在课后布置作业让我们练习，期间老师也让我们也对系统实现与测试进行了了解。所以面对本次景区民宿预约系统的开发制作，我的脑海里还是有比较清晰的思路。在系统制作中，以及配套文档的编写中，我都是按照软件开发流程一步步开展我的工作。
从系统的角度讲，景区民宿预约系统制作中，它的难点在于功能的确定，对系统结构的设计，还有设计性能优良的数据库，以及采用成熟的技术实现系统功能等，这些是我面临的困难。针对这些难点，我采取了一定的措施。在不知道系统的功能时，我在网上寻找了很多相似系统，并把这些系统的大致功能进行了记载，把对本系统有用的功能部分进行了采用，另外，我也从网上获取了大量关于系统设计方面的知识，包括系统模块划分，设计原则，数据库表的设计与创建等知识，也从软件开发类博客中，获取了程序编码的技术知识，包括数据增删改代码模块的编写与使用。在本系统编码完成其对应功能后，我对系统的所有功能进行了耐心的测试，最后发现我开发的系统是合格的，可以进行验收。因为本系统除了具备简洁美观的界面外，在功能上可以满足使用者对于数据操作的需求，并且本系统的功能与系统分析设计的功能保持高度一致，而且系统运行稳定，面对用户的误操作，也建立了报错反馈机制，系统的质量可靠。唯一不足的就是系统数据表的设计在字段考虑上并不全面，为字段匹配的数据类型也不精确，还有系统代码部分，有很多地方还没有进行注释，代码编写不够简洁等。
从文档的角度来讲，在完成景区民宿预约系统制作后，对其制作过程需要进行描述，包括如何进行的需求分析，如何完成系统的设计，以及实现的系统功能的运行效果等都要进行描述。这期间我也花费了将近一个月时间来完成，为了达到学院要求的文档排版标准，我也多次在导师建议下，学习办公软件的使用，还有排版技巧。功夫不负有心人，我编写的文档在面临多次编写修改后终于完成了。
总而言之，制作毕设虽然经历了很多环节，但是认真对待这个事情，我们将会在各个环节获取很多知识，也会在各个环节的实际操作中，锻炼我们的实践能力。通过本项目制作，我开始明白，很多知识并不只是来源于书本，来源于老师课堂上讲解的知识，也需要来源于各大学习网站以及生活实践等。至此，我还是会继续努力，保持新知识的主动学习习惯。
参考文献
[2]高岳,张腾.基于基站定位的公交查询系统设计[J].无线互联科技,2015(03):32-35.
[3]钱佳加,唐海江,夏莎莎,姚宇杰,张祥杰.公交查询系统的设计与实现[J].现代商业,2015(17):67-68.
[4]邓林.MySQL存储过程调试技巧[J].四川职业技术学院学报,2017,27(04):157-159.
[5]张继东.MySQL数据库的权限及其安全缺陷[J].信息与电脑(理论版),2017(08):165-166.
[6]邹青松.计算机软件Java编程特点及其技术运用[J].黑龙江科学,2020,11(06):62-63.
[7]王丽,刘佳,杨俊叶.Java的数据库应用框架的研究设计与探讨[J].数字通信世界,2020(04):63.
[8]李燕安.基于Java的Web开发技术的探讨[J].中国新通信,2020,22(08):73.
[9]蒋治学.vue技术及其在动态网页开发中的应用分析[J].浙江水利水电学院学报,2020,32(02):75-77.
[10]康牧.vue动态网站开发实用教程[M].清华大学出版社,2015.
[11]薛茹.基于SpringBoot框架的Web系统研究与应用[J].计算机产品与流通,2018(07):30.
[12]邱丹萍.Web开发中SpringBoot框架的分析[J].电脑知识与技术,2020,16(17):81-82.
[13]王建国.数据库设计在网站开发中的应用[J].山东农业工程学院学报,2017,34(04):158-159+164.
[14]张知青.基于关系数据库的查询方法及优化技术分析[J].煤炭技术,2015,31(05):218-220.
[15]杨堃.计算机软件的运行与维护方法[J].中国高新区,2018(04):179.
[16]李晓琳.安全技术在计算机软件开发中的价值和应用[J].信息与电脑(理论版),2020,32(18):88-89.
[17]Benymol Jose, Sajimon Abraham. Performance analysis of NoSQL and relational databases with MongoDB and MySQL. 2020, 24(Pt 3):2036-2043.
[18]Dragos-Paul Pop, Adam Altar. Designing an MVC Model for Rapid Web Application Development[J]. Procedia Engineering, 2017.
致 谢
虽然项目制作已经完成，但是回想近段时间所经历的事情，内心还是感触良多。自从进入校园后，我对知识的学习就没有那么刻苦了，也不会想着去主动学习，日常课程虽然不缺席，但是对待课后作业也是比较马虎。但是这次毕业设计，却真正唤醒了我。让我开始努力去做一件事。
说到毕业设计，心中比较敬重和感恩的人是导师，导师让我明白，知识不足可以通过后期学习进行弥补，他让我看到了希望，虽然我一直怀疑自己不可能独自完成系统开发，但是在得到导师的帮助后，我做了很多改变自己看法的事情。我竟然可以一步步根据开发流程，完成系统的制作，真的很开心，同时也对导师表示感谢！
还有一群最容易被忽视的人们，就是我身边的同学。他们无论是在课堂上还是在课下，始终陪伴着我。也就是无论学习还是生活，我的身边都有他们，所以大家互相帮助是在所难免的，但是因为这样的陪伴，也充实了我的校园生活。要毕业了，我想说，谢谢你们，我的同学们！
那些给我们上课的老师们也是值得感恩的，他们也是我校园生活中不可缺少的一部分，而且也是教会我知识，让我明白许多生活的道理的老师们，他们一直像蜜蜂一样辛勤的工作，不厌其烦的教授一批又一批校园学子。所以他们值得我们尊敬和感谢！
大学校园的环境是最美的，我也很庆幸来到这里上学，感谢我的学校，愿我的母校越来越好！