CN117151820A - Aviation ticket booking system - Google Patents
Aviation ticket booking system Download PDFInfo
- Publication number
- CN117151820A CN117151820A CN202311134677.XA CN202311134677A CN117151820A CN 117151820 A CN117151820 A CN 117151820A CN 202311134677 A CN202311134677 A CN 202311134677A CN 117151820 A CN117151820 A CN 117151820A
- Authority
- CN
- China
- Prior art keywords
- information
- database
- ticket booking
- data
- payment
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000005516 engineering process Methods 0.000 claims abstract description 14
- 238000007405 data analysis Methods 0.000 claims abstract description 9
- 238000000034 method Methods 0.000 claims description 89
- 230000006870 function Effects 0.000 claims description 65
- 238000007726 management method Methods 0.000 claims description 58
- 238000012795 verification Methods 0.000 claims description 50
- 238000012545 processing Methods 0.000 claims description 39
- 230000008569 process Effects 0.000 claims description 35
- 238000012550 audit Methods 0.000 claims description 12
- 238000012360 testing method Methods 0.000 claims description 12
- 238000012986 modification Methods 0.000 claims description 11
- 230000004048 modification Effects 0.000 claims description 11
- 238000013475 authorization Methods 0.000 claims description 8
- 238000012423 maintenance Methods 0.000 claims description 8
- 230000004044 response Effects 0.000 claims description 8
- 230000003068 static effect Effects 0.000 claims description 8
- 238000004458 analytical method Methods 0.000 claims description 7
- 238000010276 construction Methods 0.000 claims description 6
- 238000004519 manufacturing process Methods 0.000 claims description 6
- 238000004806 packaging method and process Methods 0.000 claims description 6
- 238000004088 simulation Methods 0.000 claims description 6
- 238000011161 development Methods 0.000 claims description 5
- 230000000694 effects Effects 0.000 claims description 5
- 235000010627 Phaseolus vulgaris Nutrition 0.000 claims description 4
- 244000046052 Phaseolus vulgaris Species 0.000 claims description 4
- 230000010006 flight Effects 0.000 claims description 4
- 230000003993 interaction Effects 0.000 claims description 4
- 238000013507 mapping Methods 0.000 claims description 4
- 238000012544 monitoring process Methods 0.000 claims description 4
- 230000002688 persistence Effects 0.000 claims description 4
- 230000010354 integration Effects 0.000 claims description 3
- 238000012800 visualization Methods 0.000 claims description 3
- 230000006399 behavior Effects 0.000 claims description 2
- 230000008859 change Effects 0.000 claims description 2
- 238000004140 cleaning Methods 0.000 claims description 2
- 238000007418 data mining Methods 0.000 claims description 2
- 238000013500 data storage Methods 0.000 claims description 2
- 230000001419 dependent effect Effects 0.000 claims description 2
- 230000000977 initiatory effect Effects 0.000 claims description 2
- 238000002347 injection Methods 0.000 claims description 2
- 239000007924 injection Substances 0.000 claims description 2
- 230000002045 lasting effect Effects 0.000 claims description 2
- 238000010801 machine learning Methods 0.000 claims description 2
- 230000008520 organization Effects 0.000 claims description 2
- 238000003860 storage Methods 0.000 claims description 2
- 238000012549 training Methods 0.000 claims description 2
- 230000002159 abnormal effect Effects 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 11
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 230000006872 improvement Effects 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 238000010223 real-time analysis Methods 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
- G06Q30/0635—Processing of requisition or of purchase orders
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- Economics (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Marketing (AREA)
- Development Economics (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses an aviation ticket booking system, in particular to an online aviation ticket booking system based on a database and an internet technology, which is a technical scheme in the field of internet data service. The ticket booking system users are divided into ticket booking personnel and management personnel, in the ticket booking personnel system, account numbers are used for logging in, and real-time ticket information can be inquired in a ticket hall through departure places, destinations and departure time, so that various operations such as ticket booking, payment, personnel management and the like can be performed. In the manager system, the information of the modified inquiring role can be added and deleted, unified scheduling management can be carried out on all interfaces, the login condition, the operation condition and the abnormal condition of the user can be checked, and the information of the modified inquiring plane, the information of the airline company and the information of the air ticket can be added and deleted. According to the scheme, the user experience and the management efficiency of the aviation ticket booking system are improved by utilizing a big data analysis means, the automation level of ticket booking business is optimized by utilizing a data analysis technology, and the working efficiency is improved.
Description
Technical Field
The invention relates to the field of internet data service, in particular to an aviation ticket booking system, and specifically relates to an online aviation ticket booking system based on a database and an internet technology.
Background
With the continuous development of economy, the demands of aviation travel are increasing, and besides direct booking to the point of sale or an airport, various large airlines develop services such as telephone booking, online booking and the like in a dispute manner, so that the demands of booking by clients are met, and the use effect of booking by clients conveniently and rapidly is achieved. The online aviation ticket booking is gradually accepted by people, and gradually becomes a trend. The online aviation booking has been developed for more than ten years and enters a modernization stage, but due to insufficient management of an airline company on an online booking system and insufficient knowledge of database management, most booking systems only can roughly simplify engineering programs, reduce working strength and improve working efficiency, and advanced database technology, information technology and big data analysis technology are not comprehensively utilized, and if a patent technology is not utilized, real-time analysis can be carried out on booking personnel and flight data by comprehensively utilizing the advanced database technology, the information technology and the big data analysis technology, better use experience can be provided for booking users, and the airline company can be assisted to improve management efficiency and expand service range.
Disclosure of Invention
The invention aims to provide a new scheme of an aviation ticket booking system, which is continuously reasonable, concise and systematic, and aims to improve the user experience and management efficiency of the aviation ticket booking system by utilizing a big data analysis means, continuously promote the upgrading of a database technology, optimize the automation level of complicated business content by utilizing a data analysis technology, improve the working efficiency of ticket selling management and bring great economic value to airlines.
In order to achieve the above purpose, the present invention adopts the following technical scheme:
the aviation ticket booking system comprises a front-end webpage display module, a server-end integration module and a data system processing module, wherein the front-end webpage display module is used for presenting content related to a front-end webpage, a ViewModel controller is used for connecting a model layer and a view layer, receiving user input, sending a request to a rear end and responsible for monitoring modification of the model layer and the view layer, and is an interface for a user to directly interact with the system; the server-side integrated module is mainly responsible for processing interaction with the front end, data storage and business logic, and is used for realizing information management and various basic functions required by the server and meeting the requirements of different scenes; the data system processing module is used for collecting and cleaning data, effectively processing and storing management, backing up and recovering, synchronizing and integrating functions, and sending the processed data to the server for relevant processing.
The aviation booking system according to the foregoing is characterized in that the front-end web page display module creates a new Vue item by using WebStorm, introduces the Element UI style into the new item, creates the Vue component required by the aviation booking system, the component includes a login page, a flight search page and an order page, writes business logic in the component, the business logic includes flight search, order generation and payment functions, verifies the data input by the booking personnel by using the form component and verification rule provided by the Element UI, and then realizes the page interaction effect by the event and method provided by the Vue component and the Element UI component; the global state is managed by using the state management of the Vue, wherein the global state comprises the login state of ticket booking personnel and order information, the correctness and the stability of the system are ensured through debugging and testing, and a static file of a production environment is constructed; front-end code is packaged into static files using the packaging tool provided by WebStorm and deployed to a server.
The aviation ticket booking system is characterized in that the server-side integrated module builds projects by adopting Spring Boot versions, front-end pages transmit request data to a control layer through Http/Https protocols, the control layer analyzes and verifies the data after receiving the front-end requests, the data is transmitted to a Service layer for Service logic processing, a database server is accessed through a data persistence layer in the Service processing process, and related database operation is carried out; when the service processing result returns to the control layer, the control layer transmits the service processing result to the front-end page for processing, a new Spring Boot item is created by using IDEA, relevant dependence of the Spring Boot is configured, a database table is created, a corresponding entity class and a Mapper interface are created by using MyBatis-Plus, a method for processing an HTTP request is written in the controller, a service layer and a storage library are called for carrying out service logic operation, finally mapping of static resources is configured in the Spring Boot item, HTML, CSS and JavaScript codes of the front-end page are written, the HTML, CSS and JavaScript codes are pointed to a front-end page file, a Tomcat server is used for running and testing a front-end module, and a production environment of an executable jar file is constructed and deployed on the Tomcat server.
The aviation ticket booking system according to the foregoing is characterized in that the data system processing module uses a Navicat to connect to a MySQL database server, newly builds a database list in the Navicat, selects a database to be provided with a Character Set and a sorting rule, then selects an attribute and Database Properties, switches to a Character Set or a Character Set tab selection Character Set in an opened database attribute window, switches to a sorting rule or a sorting rule tab selection sorting rule in the same database attribute window, and clicks an Apply button to change and close the database attribute window after confirming the selected Character Set and sorting rule; after the sorting rule is selected, the initial data required by the aviation ticket booking system is imported by utilizing the data importing function of the Navicat, and SQL query sentences are executed by using the Navicat to perform data adding, deleting and checking operations; after the database system is built, the back end code of the aviation booking system is utilized, the JDBC driver of MySQL is used for connecting to the database, and SQL sentences operated by the database are written in the code and are used for inquiring passenger information, booking flights and paying orders; finally, navicat is used for monitoring the performance and the running state of the database, and a MySQL database server is deployed to the production environment; the data system processing module stores the relationship data base system in different tables by establishing a relationship data base management system of an open source code, thereby realizing the safety maintenance of the system.
The aviation ticket booking system is characterized in that the system uses personnel to define ticket booking personnel and management personnel, the system comprises a ticket booking personnel module and a management personnel module, the ticket booking personnel module comprises an account number and password login of the ticket booking personnel, ticket booking is scheduled, ticket booking personnel information is modified, order payment is achieved, and the management personnel module comprises an account number and password login of the management personnel, information of the management ticket booking personnel and aviation, and log-in.
The aviation ticket booking system is characterized in that the specific functions of the ticket booking personnel module comprise account number and password login, ticket booking personnel information maintenance and order payment;
the password login implementation process is as follows:
the method comprises the steps that a Spring framework is used for developing a back-end module in IDEA, a new Spring Boot project is firstly created in IntelliJ IDEA, and Spring Web, spring Security and related dependent items are selected in the project creation process; then defining entity class and database model, using Spring Data JPA frame to map entity class into database table; then creating a database access layer (replier), using Spring Data JPA or a custom Data access layer, creating a replier interface and corresponding implementation class for accessing the database, defining a query method in the replier, searching ticket booking personnel information by using a user name or ID in the query, then creating a Service layer (Service), calling a corresponding replier method in the Service layer for Data access and processing, then creating a Controller layer (Controller), defining a request path and method in the Controller class by using @ RequestMapping or other annotations, calling a corresponding Service layer method, and processing HTTP requests and responses; configuring Spring Security to provide identity verification and authorization functions, limiting access to resources according to roles or rights, creating a class for realizing a UserDetails service interface, loading user information of ticket booking personnel, and configuring authentication and authorization rules; finally, the test function is as follows: testing a management and authentication function of a ticket booking person by using a testing framework (JUnit), constructing a function module for managing and authenticating the ticket booking person, realizing identity verification and access control of the ticket booking person by using Spring Security after construction, storing account information and password hash values of the ticket booking person in a database by using Navicat and MySQL, developing a login interface of the ticket booking person by using front WebStorm and Vue.2x, and realizing account password input and form verification by using an ElementUI; after verification, the front end sends a login request to the rear end through API call and establishes connection with the rear end, and the rear end realizes a login function by verifying the correctness of the account password;
The realization process of the predetermined vote module is as follows:
the method comprises the steps of realizing flight information management and ticket booking functions by using a Spring frame at the rear end, combining a Hadoop big data processing frame, combining flight information and aviation related data sources stored in a database, performing model training and prediction on historical flight data and passenger behavior data by using a machine learning and data mining technology to generate simulated aviation journey, storing the generated simulated aviation journey data into a data warehouse (namely a MySQL database), and performing simulation and analysis of aviation journey for a subsequent flight inquiry function; transmitting data after flight number, departure place, destination, departure time and arrival time simulation to a front section through a Navicat database, developing a flight inquiry and reservation ballot interface by the front end through WebStorm and Vue.2x, and providing input and selection operation of a ballot booking person through ElementUI visualization operation; finally, the front end sends a flight inquiry and ticket booking request to the rear end through API call, and the rear end receives the reservation ticket function according to the selection of ticket booking personnel and the available flight condition;
the ticket booking personnel information maintenance implementation process is as follows:
in the back-end development process, an API endpoint (URL) and a GET request method are defined and an API endpoint for acquiring, modifying and deleting specific information is created; then creating an API endpoint requested by a corresponding request method (GET) for acquiring information of a user, providing an identity verification certificate when the user sends a GET request at the front end WebStorm and Vue.2x, confirming the identity of the user after passing through the back end verification certificate, returning corresponding user information, and giving ticket booking personnel permission capable of modifying personal information; finally, a WebStorm and Vue.2x personal information modification interface is used at the front end, input and verification of ticket booking personnel are provided through an element UI, the front end sends a modification request to the rear end through API call, and the rear end realizes the information modification function of the ticket booking personnel according to verification and authorization;
The order payment implementation process is as follows:
the back end is used for creating an order by providing an API interface, the interface is used for receiving order information of a ticket booking person and generating a new order, when the order is generated, a unique order number can be allocated for the order, and the order information is stored in a database; then, acquiring order details, wherein the back end is used for acquiring the order details by providing an API interface, the interface is used for receiving order numbers as parameters and returning response data containing order information, and the response data according to the order information corresponds to the order information and is returned to a ticket booking person through the front end; immediately after returning, the back end initiates a payment request by providing an API interface for initiating the payment request, wherein the interface should receive parameters of order numbers and payment amounts and return payment related data (payment links), and when the front end receives the payment links, the SDK or the API of a third party payment platform (such as a payment treasures and WeChat payment) is used for calling the corresponding payment interface to initiate the payment request; when the payment platform finishes payment, sending a payment result notice to the rear end, wherein an API interface is called at the moment, verifying and processing the payment result in the interface, and executing related business logic processing payment callback; finally, the back end is used for canceling the order by providing an API interface, the interface should receive the order number as a parameter and execute corresponding order cancellation operation, and the cancellation operation can be processed according to the service requirement (including updating the order state to cancelled and refund); and finally, the front end sends a payment request to the rear end through API call, develops an order payment interface by using WebStorm and Vue.2x, provides payment mode selection and payment operation through an element UI, and processes payment logic and updates the order payment state after the rear end receives the payment request.
The aviation ticket booking system is characterized in that the specific functions of the manager module comprise account password login, management ticket booking personnel and aviation information and log management;
the account password login implementation process is as follows:
firstly developing a back-end module in an IDEA (integrated data analysis) by using a Spring framework, wherein the back-end module comprises an administrator account management and authentication function, realizes administrator identity authentication and access control by using Spring Security, adds relevant dependence of Spring Security in a construction configuration file of a project, creates a configuration class, inherits from a 'WebSecurityConfigurererAlatter', uses a '@EnableWebSecurityThicy' annotation tag, rewrites a 'configuration ()' method, configures Spring Security inside the method, and then uses an 'AuthenticationBuilder' configuration manager identity authentication mode, and realizes user service based on memory configuration by calling a 'infinity authentication ()' and a 'userDeilDeilservice ()') method; using the access control rule of 'https quality' configuration request level, calling an 'authenticationrequests ()' method to set the access rule, then using 'antmatrichers ()' to specify a URL mode, using 'hasRole ()' or 'hasA method ()' to specify a required role or authority, using 'authenticated ()' to specify that a user is required to perform identity verification, or using 'premium ()' to specify that open access to all users is realized to configure access control; when an administrator needs to carry out identity verification through a login page, a 'form Login ()' method can be used for configuring a path of the login page and parameter information of the login form, and configuring the path and parameters of the login page; finally, configuring a logout function by using a logout ()' method, designating a logout URL and a redirected path, storing account information and password hash values of an administrator in a later database by using Navicat and MySQL, sending the obtained result to a front end, using WebStorm and Vue.2x development administrator login interfaces by the front end, realizing account password input and form verification by using an ElementUI, calling a login request to a rear end by using an API, and realizing the login function by using the verification of the correctness of the account password by the rear end;
The management ticket booking personnel and aviation information implementation process is as follows:
the method comprises the steps of constructing management functions of ticket booking personnel and aviation information by using a Spring framework at the rear end, firstly creating a Spring Boot project, configuring relevant dependence and environment, respectively defining entity classes of the ticket booking personnel and the aviation information according to service requirements, using a relation between the entity classes and attributes of annotation marks, simplifying Data access operation by using Spring Data JPA, and defining interfaces and realization for accessing a database; then writing a Service layer code, packaging business logic, performing an operation of adding, deleting and checking ticket booking personnel and aviation information, and calling a data access layer (DAO) in the Service layer to realize the persistence operation of data and the creation of the Service layer (Service); the creation of the service layer lays a foundation for the creation of the controller, and business logic is packaged by writing a service layer code; a data access layer (DAO) can be called in the service layer to realize the lasting operation of data, ticket booking personnel and aviation information management functions are realized according to requirements, and a method of the service layer is called in the controller layer to finish corresponding operation; after the operation is finished, configuring a route and request mapping in a configuration file of a Spring Boot project, routing the request to a corresponding controller method, and using a tool to perform interface test to verify whether a management function operates normally; after verification, an administrator uses a database to store a table of ticket booking personnel and aviation information, the table comprises corresponding fields and association relations, the ticket booking personnel and the aviation information are added, deleted and checked through an API (application program interface), a management interface of a manager is developed by using WebStorm and Vue.2x at the front end after the operation is finished, a friendly operation interface of the ticket booking personnel is provided through an ElementUI, the front end sends a management request to the rear end through API call, and the rear end realizes the management function of the ticket booking personnel and the aviation information according to authority and verification;
The log record implementation process is as follows:
firstly, designing a login log table, creating a login log table in a database, wherein a table structure comprises field login time, an administrator ID and login IP and is used for recording login information of an administrator; after the ticket booking personnel successfully logs in, logging relevant logging information (comprising ticket booking personnel name and logging time) into a logging log table in a database, logging the logging log by utilizing an interceptor or an AOP function of a Spring framework at the rear end, and storing the table of the logging log (comprising ticket booking personnel name, logging time and logging IP) in the database;
secondly, when an administrator logs in the system, logging in log information is recorded and stored in a log table, and logging in time, an administrator ID and logging in IP information are written in the log table in code logic after successful logging in; creating an API interface after logging in a log table, receiving query parameters, writing corresponding business logic in a back-end code, realizing the query and analysis functions of logging in log information, inquiring and analyzing the information of the logging in the log by an administrator through the API interface according to the received query parameters, recording the logging in the log by the administrator, inquiring the log table by using SQL sentences, acquiring the logging in information conforming to the conditions, packaging the inquired logging in information into response data, returning the data to the administrator by using a JSON format, finally carrying out authentication and authority control in the API interface, realizing the identity verification and authorization functions by using Security frameworks such as Spring Security and developing corresponding interfaces at the front end for displaying and searching the logging in the log.
An aviation booking system according to the foregoing, wherein the security maintenance of the system includes firewall, security audit, security vulnerability scanning;
the firewall implementation process is as follows:
the IDEA is used for developing a back-end module, the back-end module comprises a ticket booking personnel authentication and access control function, and security control is configured in Spring, and the method specifically comprises the following steps: adding related dependence of Spring Security into the project through Maven and Gradle construction tools, then creating a Security configuration class inherited from WebSecurityConfigurererAdapter ', starting a Security function based on Web by using @ EnableWebSecurityAnnotation on the class, rewriting a @ configure (AuthenticationManagerBuilder auth) ' method, configuring user authentication information, carrying out user authentication in a database mode after the configuration is finished, defining a ' UserDetasService ' interface realized by user detail service, loading user information, configuring various Security rules in a method chain mode after loading, allowing/rejecting specific URL access, configuring login pages, configuring logout functions, rewriting a @ configure (HttpSecurity http) ' method, starting CSRF protection rights by using @ cs (), configuring Security rules and controlling; finally, starting a Spring application program, configuring Security control by utilizing a Spring Security application, realizing access control based on roles and preventing common Security attack, and limiting illegal access and malicious requests;
The security audit implementation process is as follows:
using Spring AOP (section-oriented programming) characteristics, the added section is recorded for the security audit log: firstly creating a class marked as @ Aspect ', representing that the class is a section class, defining a tangent point by using @ Pointcut' annotation for matching a method needing to add log records, secondly writing a corresponding front notification or rear notification by using @ Beforex 'or @ After' annotation, writing logic of log records in the notification method, recording related security audit information, configuring a file by Spring After the completion of audit, enabling an automatic proxy function of the Aspect by using @ AOP: aspect j-automatic proxy 'element to support automatic organization of the Aspect, declaring the section class as a bean, registering the bean into a Spring container, and finally recording an operation personnel or sensitive operation of a key business logic method by using Spring AOP' Beforex or @ After, and recording the operation personnel or sensitive operation of the log record in a database and inquiring the audit log database;
the implementation process of the security hole scanning is as follows:
developing a front-end module by using WebStorm and Vue.2x, wherein the front-end module comprises a ticket booking personnel interface and a form verification function, connecting Navicat to a MySQL database, managing the security configuration and access rights of the database by the database, and providing an easy-to-use and secure UI component by combining with an ElementUI library; in Vue.2x, front-end input verification is realized, and cross-site scripting attack (XSS), SQL injection and other common front-end security vulnerabilities are prevented; in WebStorm, performing static analysis and auditing of codes, and identifying and repairing potential safety problems; in MySQL, role-based access control is configured, a database is backed up periodically to prevent data loss or corruption, and active security vulnerability scanning is implemented on the system in combination with the use of a professional security vulnerability scanning tool OWASP ZAP.
The main technical effects of the aviation ticket booking system provided by the invention comprise:
1. convenient and fast: the online aviation ticket booking system can provide 24-hour uninterrupted flight inquiry and booking service, and a user can search flight information, select seats and book air tickets through a webpage or a mobile application program at any time without going to an entity ticket selling point or making telephone booking, so that time and energy are greatly saved.
2. Real-time information: the online booking system may provide accurate and real-time flight information including flight schedule, departure time, fare, seat availability, etc. The user can make reasonable selection according to the latest information, so that the accuracy and satisfaction of ticket booking are improved.
3. And (3) selecting various: the online airline ticket booking system generally integrates the flight information of a plurality of airlines, and a user can acquire the flight information of the airlines on the same platform and compare the prices and services of different airlines so as to make optimal selection.
4. Self-service operation: the online aviation ticket booking system can enable a user to operate autonomously, select flights, seats and services according to personal requirements, and directly complete a payment process. The user can freely conduct operations such as flight searching, date selection, reservation modification and the like, and greater flexibility and convenience are provided.
5. And (3) electronic management: the online aviation ticket booking system electronizes the ticket booking process, manages data such as user information, order records, payment states and the like through a database, and is convenient to manage and inquire. And meanwhile, an electronic ticket can be generated and provided for the user to carry out identity verification and use of journey certificates.
6. Customer service support: the online aviation ticket booking system can provide customer service support, comprises channels such as online customer service, telephone consultation, problem feedback and the like, and can timely obtain answering and support when a user encounters a problem or needs help in the booking process, so that user experience and satisfaction are improved.
7. Data analysis and statistics: the online booking system collects and records a large amount of booking data, and an airline company can know information such as market demands, passenger preferences and the like through analyzing and counting the data so as to better make decisions such as route planning, price strategies, service improvement and the like.
In summary, the aviation ticket booking system provided by the invention provides a plurality of advantages of convenience, real-time, various selections and the like, so that a user can more easily book flights, and meanwhile, the management efficiency and the service level of an airline company are improved.
Drawings
Fig. 1: aviation ticket booking system function module diagram
Fig. 2: login interface diagram
Fig. 3: basic overall view of ballot hall
Fig. 4: detail drawing of ticket in ballot hall
Fig. 5: payment order interface diagram
Fig. 6: flight information interface diagram
Fig. 7: character management interface diagram
Fig. 8: log interface diagram
Detailed Description
The invention will now be further described with reference to examples, figures:
the general business flow chart of the aviation ticket booking system is shown in figure 1, and the general business flow of the system is constructed through a front-end webpage display module, a server-end integration module and a data system processing module.
According to the overall business flow diagram, the analysis is performed on the angles of different roles, and the specific interfaces of each part are subjected to the visualization operation through the front-end webpage simulation module. The first character is a ticket booking person, the login interface diagram of the ticket booking person is shown in fig. 2, and the ticket booking person can input an account number and a password and perform account login through a verification code. When the user clicks the login button, the front end transmits a login request to the back end through the HTTP protocol. The request contains information such as account number, password, verification code and the like input by the user. The back-end server receives the login request sent by the front end and acquires information such as an account number, a password, a verification code and the like from the request. The back end verifies the received verification code. The verification mode may be to compare whether the verification code input by the user is consistent with the verification code generated at the back end. And the back end verifies the received account number and password. The verification may be by comparing whether the account number password matches user information stored in the database. And the back end generates a corresponding login result according to the verification result of the verification code and the account password. If the verification is passed, a login credential is generated and returned to the front end. If the verification is not passed, an error message is returned to the front end. After the front end receives the login result returned by the rear end, corresponding processing is carried out according to the result. If the login is successful, the front end can jump to the personal homepage of the user or other functional pages which need to be logged in for use. If the login fails, the front end may prompt the user to reenter or display the error message. And then entering a ballot interface, wherein the basic overall view of the ballot hall is shown in fig. 3, the form of flight information displayed on the page is similar to an expandable form displayed by a data system processing module and a front-end webpage simulation module, and a user expands the flight information by clicking a sharp corner at the front left of the form, so that the first page can be more concise. The ticket booking personnel can search and inquire the ticket information in the ticket hall through inquiring the departure place, the destination and the departure time in the ticket hall interface, and can see the price corresponding to the first class cabin, the business cabin and the economy cabin corresponding to the ticket after clicking the ticket. When the ticket booking person clicks the inquiry button, the front end sends an inquiry request to the rear end through the HTTP protocol. The request contains information such as departure place, destination, departure time and the like input by the ticket booking person. The back-end server receives the inquiry request sent by the front end and acquires information such as departure place, destination, departure time and the like from the request. And the back end writes a query statement by using a database query language according to the received query request, and executes query operation in the database. The query statement screens out the air ticket information meeting the conditions according to the conditions of the departure place, the destination, the departure time and the like. The back end acquires the queried air ticket information from the database, encapsulates the result into a proper data format and returns the proper data format to the front end. After the front end receives the air ticket information returned by the rear end, the air ticket information is analyzed and displayed on a ballot hall interface. The corresponding price can be displayed according to the flight ticket's bunk (first class, business class, economy class). The detail view of the ticket in the ballot hall is shown in fig. 4, according to the prices of different cabins, a user can click a following 'order' button to conduct reservation ticket operation, then a window similar to a drawer appears on the right side of a webpage, the user can select the needed ticket booking information in the window, the user can select the ticket booking information to be added and selected in the right-side ticket booking button, and then the output of the ticket booking information can be seen. When a ticket booking person selects a ticket booking person, information of the preset ticket is displayed, so that the effect of previewing in advance is achieved, and if related errors exist, the previous step is clicked or the shadow part of the drawer interface is clicked to exit the ticket booking operation. When the ticket information is confirmed to be correct, the final payment interface is entered, the payment order interface diagram is shown in fig. 5, and after the front end finishes the operations of ticket selection, passenger information filling and the like, the front end sends a request to the rear end to generate an order. The request contains selected ticket information, passenger information and other parameters. The back-end server receives the order generation request sent by the front end and acquires order related information from the request. The back-end stores the order information in a database. The detailed information, amount, status, etc. of the order are stored in the order table through database operation, and an order number is generated. After the back end generates the order number, the order number is returned to the front end as the identification of the subsequent payment flow. The front end displays corresponding payment information according to the order number and the payment amount, and the user selects a payment mode (such as a payment bank, a WeChat, a bank card and the like) on a payment interface. When the user clicks the payment button, the front end sends a payment request to the back end through the HTTP protocol. The request contains information such as order number, payment mode, payment amount, etc. The back-end server receives the payment request sent by the front-end and acquires payment-related information from the request. And the back end calls a corresponding third party payment platform interface according to the payment mode in the payment request. The back end transmits information such as order numbers, payment amounts and the like to the payment platform so as to complete the payment flow. After the payment platform processes the payment request, the payment result (success or failure) is returned to the back end. And updating the payment state of the corresponding order in the database by the back end according to the payment result. If the payment is successful, the front end receives the payment result and then carries out corresponding display according to the payment result, such as displaying a prompt message of the payment success or the payment failure; if the payment fails, updating the order state to the payment failure, and returning the payment result to the front end by the back end. If an order to be paid in my order is selected to be paid later, which corresponds to the order, after which we can make the payment of the order again. In addition, the client also has a ticket booking person information interface, and the information of the ticket booking person can be added, deleted, revised and checked on the interface. The ticket booking person can choose to modify the gender, mailbox, user name, mobile phone number information, query the user information and the like of the ticket booking person in the menu bar and update the information in the database. When the ticket booking personnel performs the operations of adding, modifying, deleting or inquiring on the interface, the front end sends a corresponding request to the rear end through the HTTP protocol. The back-end server receives the request sent by the front-end and obtains the operation type and related parameters from the request. The backend performs the corresponding operations through database operations (e.g., insert, update, delete, and query statements) depending on the type of request received. For example, when an addition request is received, the back end inserts new ticket booking personnel information into the database; when receiving the modification request, the rear end updates corresponding ticket booking personnel information in the database; when a deletion request is received, the rear end deletes corresponding ticket booking personnel information from the database; when a query request is received, the back end retrieves qualified ticket booking personnel information from the database according to the parameters. The backend packages the results of the operation into the appropriate data format (e.g., JSON) and returns it to the front-end. For example, for add, modify, delete operations, a message may be returned that the operation was successful or failed; for the query operation, the queried ticket booking information list can be returned to the front end. After the front end receives the result returned by the back end, the result is analyzed and displayed on the ticket booking personnel information management interface. For example, when a list of ticketing staff information is queried, the front end will present the list on an interface for viewing by the user. Finally, an order interface diagram is presented after all of the above operations are completed, the user can see all of the historical orders, and the orders can be divided into two states, paid and unpaid. All business processes of the client interface are introduced and completed.
The second role is that of an administrator who logs in through an airline administrator account password, and the login interface is similar to that of fig. 2. In the manager system, the manager can conduct department management, a flight information interface diagram is shown in fig. 6, the manager can add, modify and delete the names and the levels of the departments which the manager wants, in the role management, the manager can add, delete, modify and inquire the role information of the manager, and the front end is responsible for collecting the input of the manager and sending a corresponding request to the back end. The back end receives and processes the request, and executes the related ticket booking person information management operation after the identity verification. The database stores ticket booking information and provides corresponding inquiry, insertion, update, deletion and other functions. The front and back ends communicate via HTTP protocol, and the database stores ticket booking information and corresponding management operations, such as ticket booking client roles, administrator roles, etc. And secondly, a user management layer can be used for adding, modifying, deleting and exporting user information on a user management interface, and menu management can be used for carrying out unified scheduling management on all interfaces of the page, modifying icon hierarchical relation, deleting and the like. The role management interface is shown in fig. 7, and an administrator can add and delete and revise airplane information, airline information, and ticket information. Finally, in log management, the log logging interface is shown in fig. 8, and the front end is responsible for collecting the input of the administrator and sending the corresponding request to the back end. The back end receives and processes the request, and retrieves the eligible log data through a database query operation. The database stores log data and provides corresponding query functions. The front end and the back end communicate through the HTTP protocol, establish proper indexes in the database to accelerate the query operation, and store the log data and the corresponding management operation. The administrator can check the login condition, the operation condition and the abnormal condition of the user, can perform condition inquiry through the user name and the state, and can derive all login log information afterwards. The above is a general business flow of the airline reservation system.
The foregoing description of the preferred embodiments of the present invention is provided for the purpose of illustration, and is not intended to limit the scope of the claims.
Claims (8)
1. The aviation ticket booking system is characterized by comprising a front-end webpage display module, a server-end integration module and a data system processing module, wherein the front-end webpage display module is used for presenting content related to a front-end webpage, a ViewModel controller is used for connecting a model layer and a view layer, receiving user input, sending a request to the rear end and responsible for monitoring modification of the model layer and the view layer, and is an interface for a user to directly interact with the system; the server-side integrated module is mainly responsible for processing interaction with the front end, data storage and business logic, and is used for realizing information management and various basic functions required by the server and meeting the requirements of different scenes; the data system processing module is used for collecting and cleaning data, effectively processing and storing management, backing up and recovering, synchronizing and integrating functions, and sending the processed data to the server for relevant processing.
2. The airline reservation system of claim 1, wherein the front-end web page display module creates a new Vue project using WebStorm, introduces a style of Element UI in the new project, creates Vue components required for the airline reservation system, the components including a login page, a flight search page, and an order page, writes business logic in the components, the business logic including flight search, order generation, and payment functions, verifies data entered by a reservation staff using form components and verification rules provided by the Element UI, and then implements page interaction effects through events and methods provided by the Vue components and the Element UI components; the global state is managed by using the state management of the Vue, wherein the global state comprises the login state of ticket booking personnel and order information, the correctness and the stability of the system are ensured through debugging and testing, and a static file of a production environment is constructed; front-end code is packaged into static files using the packaging tool provided by WebStorm and deployed to a server.
3. The aviation ticket booking system according to claim 1, wherein the server side integrated module builds projects by adopting Spring Boot versions, a front end page transmits request data to a control layer through Http/Https protocols, the control layer analyzes and verifies the data after receiving the front end request, the data is transmitted to a Service layer for Service logic processing, and a database server is accessed through a data persistence layer in the Service processing process to perform related database operation; when the service processing result returns to the control layer, the control layer transmits the service processing result to the front-end page for processing, a new Spring Boot item is created by using IDEA, relevant dependence of the Spring Boot is configured, a database table is created, a corresponding entity class and a Mapper interface are created by using MyBatis-Plus, a method for processing an HTTP request is written in the controller, a service layer and a storage library are called for carrying out service logic operation, finally mapping of static resources is configured in the Spring Boot item, HTML, CSS and JavaScript codes of the front-end page are written, the HTML, CSS and JavaScript codes are pointed to a front-end page file, a Tomcat server is used for running and testing a front-end module, and a production environment of an executable jar file is constructed and deployed on the Tomcat server.
4. The airline reservation system of claim 1, wherein the data system processing module connects to a MySQL database server using a Navicat, newly builds a database list in the Navicat, selects a database to be provided with a Character Set and a ranking rule, then selects "attribute" and "Database Properties", then switches to a "Character Set" or "Character Set" tab selection Character Set in an open database attribute window, and switches to a "ranking rule" or "collection" tab selection ranking rule in the same database attribute window, after confirming the selected Character Set and ranking rule, clicks an "Apply" or "Apply" button to Apply a change and closes the database attribute window; after the sorting rule is selected, the initial data required by the aviation ticket booking system is imported by utilizing the data importing function of the Navicat, and SQL query sentences are executed by using the Navicat to perform data adding, deleting and checking operations; after the database system is built, the back end code of the aviation booking system is utilized, the JDBC driver of MySQL is used for connecting to the database, and SQL sentences operated by the database are written in the code and are used for inquiring passenger information, booking flights and paying orders; finally, navicat is used for monitoring the performance and the running state of the database, and a MySQL database server is deployed to the production environment; the data system processing module stores the relationship data base system in different tables by establishing a relationship data base management system of an open source code, thereby realizing the safety maintenance of the system.
5. An airline reservation system as claimed in claim 1, wherein the system is defined as a reservation person and a manager, the system comprising a reservation person module and a manager module, the reservation person module function comprising a reservation person account number code login, reservation ticket, reservation person information modification, order payment, the manager module function comprising a manager account number code login, management reservation person and airline information, log.
6. An airline reservation system as claimed in claim 5, wherein specific functions of the reservation personnel module include account number password login, reservation of a ballot, reservation personnel information maintenance and order payment;
the password login implementation process is as follows:
the method comprises the steps that a Spring framework is used for developing a back-end module in IDEA, a new Spring Boot project is firstly created in IntelliJ IDEA, and Spring Web, spring Security and related dependent items are selected in the project creation process; then defining entity class and database model, using Spring Data JPA frame to map entity class into database table; then creating a database access layer (replier), using Spring Data JPA or a custom Data access layer, creating a replier interface and corresponding implementation class for accessing the database, defining a query method in the replier, searching ticket booking personnel information by using a user name or ID in the query, then creating a Service layer (Service), calling a corresponding replier method in the Service layer for Data access and processing, then creating a Controller layer (Controller), defining a request path and method in the Controller class by using @ RequestMapping or other annotations, calling a corresponding Service layer method, and processing HTTP requests and responses; configuring Spring Security to provide identity verification and authorization functions, limiting access to resources according to roles or rights, creating a class for realizing a UserDetails service interface, loading user information of ticket booking personnel, and configuring authentication and authorization rules; finally, the test function is as follows: testing a management and authentication function of a ticket booking person by using a testing framework (JUnit), constructing a function module for managing and authenticating the ticket booking person, realizing identity verification and access control of the ticket booking person by using Spring Security after construction, storing account information and password hash values of the ticket booking person in a database by using Navicat and MySQL, developing a login interface of the ticket booking person by using front WebStorm and Vue.2x, and realizing account password input and form verification by using an ElementUI; after verification, the front end sends a login request to the rear end through API call and establishes connection with the rear end, and the rear end realizes a login function by verifying the correctness of the account password;
The realization process of the predetermined vote module is as follows:
the method comprises the steps of realizing flight information management and ticket booking functions by using a Spring frame at the rear end, combining a Hadoop big data processing frame, combining flight information and aviation related data sources stored in a database, performing model training and prediction on historical flight data and passenger behavior data by using a machine learning and data mining technology to generate simulated aviation journey, storing the generated simulated aviation journey data into a data warehouse (namely a MySQL database), and performing simulation and analysis of aviation journey for a subsequent flight inquiry function; transmitting data after flight number, departure place, destination, departure time and arrival time simulation to a front section through a Navicat database, developing a flight inquiry and reservation ballot interface by the front end through WebStorm and Vue.2x, and providing input and selection operation of a ballot booking person through ElementUI visualization operation; finally, the front end sends a flight inquiry and ticket booking request to the rear end through API call, and the rear end receives the reservation ticket function according to the selection of ticket booking personnel and the available flight condition;
the ticket booking personnel information maintenance implementation process is as follows:
in the back-end development process, an API endpoint (URL) and a GET request method are defined and an API endpoint for acquiring, modifying and deleting specific information is created; then creating an API endpoint requested by a corresponding request method (GET) for acquiring information of a user, providing an identity verification certificate when the user sends a GET request at the front end WebStorm and Vue.2x, confirming the identity of the user after passing through the back end verification certificate, returning corresponding user information, and giving ticket booking personnel permission capable of modifying personal information; finally, a WebStorm and Vue.2x personal information modification interface is used at the front end, input and verification of ticket booking personnel are provided through an element UI, the front end sends a modification request to the rear end through API call, and the rear end realizes the information modification function of the ticket booking personnel according to verification and authorization;
The order payment implementation process is as follows:
the back end is used for creating an order by providing an API interface, the interface is used for receiving order information of a ticket booking person and generating a new order, when the order is generated, a unique order number can be allocated for the order, and the order information is stored in a database; then, acquiring order details, wherein the back end is used for acquiring the order details by providing an API interface, the interface is used for receiving order numbers as parameters and returning response data containing order information, and the response data according to the order information corresponds to the order information and is returned to a ticket booking person through the front end; immediately after returning, the back end initiates a payment request by providing an API interface for initiating the payment request, wherein the interface should receive parameters of order numbers and payment amounts and return payment related data (payment links), and when the front end receives the payment links, the SDK or the API of a third party payment platform (such as a payment treasures and WeChat payment) is used for calling the corresponding payment interface to initiate the payment request; when the payment platform finishes payment, sending a payment result notice to the rear end, wherein an API interface is called at the moment, verifying and processing the payment result in the interface, and executing related business logic processing payment callback; finally, the back end is used for canceling the order by providing an API interface, the interface should receive the order number as a parameter and execute corresponding order cancellation operation, and the cancellation operation can be processed according to the service requirement (including updating the order state to cancelled and refund); and finally, the front end sends a payment request to the rear end through API call, develops an order payment interface by using WebStorm and Vue.2x, provides payment mode selection and payment operation through an element UI, and processes payment logic and updates the order payment state after the rear end receives the payment request.
7. The aviation ticket booking system according to claim 5, wherein the specific functions of the manager module comprise account number and password login, management ticket booking personnel and aviation information, and login log management;
the account password login implementation process is as follows:
firstly developing a back-end module in an IDEA (integrated data analysis) by using a Spring framework, wherein the back-end module comprises an administrator account management and authentication function, realizes administrator identity authentication and access control by using Spring Security, adds relevant dependence of Spring Security in a construction configuration file of a project, creates a configuration class, inherits from a 'WebSecurityConfigurererAlatter', uses a '@EnableWebSecurityThicy' annotation tag, rewrites a 'configuration ()' method, configures Spring Security inside the method, and then uses an 'AuthenticationBuilder' configuration manager identity authentication mode, and realizes user service based on memory configuration by calling a 'infinity authentication ()' and a 'userDeilDeilservice ()') method; using the access control rule of 'https quality' configuration request level, calling an 'authenticationrequests ()' method to set the access rule, then using 'antmatrichers ()' to specify a URL mode, using 'hasRole ()' or 'hasA method ()' to specify a required role or authority, using 'authenticated ()' to specify that a user is required to perform identity verification, or using 'premium ()' to specify that open access to all users is realized to configure access control; when an administrator needs to carry out identity verification through a login page, a 'form Login ()' method can be used for configuring a path of the login page and parameter information of the login form, and configuring the path and parameters of the login page; finally, configuring a logout function by using a logout ()' method, designating a logout URL and a redirected path, storing account information and password hash values of an administrator in a later database by using Navicat and MySQL, sending the obtained result to a front end, using WebStorm and Vue.2x development administrator login interfaces by the front end, realizing account password input and form verification by using an ElementUI, calling a login request to a rear end by using an API, and realizing the login function by using the verification of the correctness of the account password by the rear end;
The management ticket booking personnel and aviation information implementation process is as follows:
the method comprises the steps of constructing management functions of ticket booking personnel and aviation information by using a Spring framework at the rear end, firstly creating a Spring Boot project, configuring relevant dependence and environment, respectively defining entity classes of the ticket booking personnel and the aviation information according to service requirements, using a relation between the entity classes and attributes of annotation marks, simplifying Data access operation by using Spring Data JPA, and defining interfaces and realization for accessing a database; then writing a Service layer code, packaging business logic, performing an operation of adding, deleting and checking ticket booking personnel and aviation information, and calling a data access layer (DAO) in the Service layer to realize the persistence operation of data and the creation of the Service layer (Service); the creation of the service layer lays a foundation for the creation of the controller, and business logic is packaged by writing a service layer code; a data access layer (DAO) can be called in the service layer to realize the lasting operation of data, ticket booking personnel and aviation information management functions are realized according to requirements, and a method of the service layer is called in the controller layer to finish corresponding operation; after the operation is finished, configuring a route and request mapping in a configuration file of a Spring Boot project, routing the request to a corresponding controller method, and using a tool to perform interface test to verify whether a management function operates normally; after verification, an administrator uses a database to store a table of ticket booking personnel and aviation information, the table comprises corresponding fields and association relations, the ticket booking personnel and the aviation information are added, deleted and checked through an API (application program interface), a management interface of a manager is developed by using WebStorm and Vue.2x at the front end after the operation is finished, a friendly operation interface of the ticket booking personnel is provided through an ElementUI, the front end sends a management request to the rear end through API call, and the rear end realizes the management function of the ticket booking personnel and the aviation information according to authority and verification;
The log record implementation process is as follows:
firstly, designing a login log table, creating a login log table in a database, wherein a table structure comprises field login time, an administrator ID and login IP and is used for recording login information of an administrator; after the ticket booking personnel successfully logs in, logging relevant logging information (comprising ticket booking personnel name and logging time) into a logging log table in a database, logging the logging log by utilizing an interceptor or an AOP function of a Spring framework at the rear end, and storing the table of the logging log (comprising ticket booking personnel name, logging time and logging IP) in the database;
secondly, when an administrator logs in the system, logging in log information is recorded and stored in a log table, and logging in time, an administrator ID and logging in IP information are written in the log table in code logic after successful logging in; creating an API interface after logging in a log table, receiving query parameters, writing corresponding business logic in a back-end code, realizing the query and analysis functions of logging in log information, inquiring and analyzing the information of the logging in the log by an administrator through the API interface according to the received query parameters, recording the logging in the log by the administrator, inquiring the log table by using SQL sentences, acquiring the logging in information conforming to the conditions, packaging the inquired logging in information into response data, returning the data to the administrator by using a JSON format, finally carrying out authentication and authority control in the API interface, realizing the identity verification and authorization functions by using Security frameworks such as Spring Security and developing corresponding interfaces at the front end for displaying and searching the logging in the log.
8. An airline reservation system as claimed in claim 1, wherein security maintenance of the system includes firewalls, security audits, security hole scans;
the firewall implementation process is as follows:
the IDEA is used for developing a back-end module, the back-end module comprises a ticket booking personnel authentication and access control function, and security control is configured in Spring, and the method specifically comprises the following steps: adding related dependence of Spring Security into the project through Maven and Gradle construction tools, then creating a Security configuration class inherited from WebSecurityConfigurererAdapter ', starting a Security function based on Web by using @ EnableWebSecurityAnnotation on the class, rewriting a @ configure (AuthenticationManagerBuilder auth) ' method, configuring user authentication information, carrying out user authentication in a database mode after the configuration is finished, defining a ' UserDetasService ' interface realized by user detail service, loading user information, configuring various Security rules in a method chain mode after loading, allowing/rejecting specific URL access, configuring login pages, configuring logout functions, rewriting a @ configure (HttpSecurity http) ' method, starting CSRF protection rights by using @ cs (), configuring Security rules and controlling; finally, starting a Spring application program, configuring Security control by utilizing a Spring Security application, realizing access control based on roles and preventing common Security attack, and limiting illegal access and malicious requests;
The security audit implementation process is as follows:
using Spring AOP (section-oriented programming) characteristics, the added section is recorded for the security audit log: firstly creating a class marked as @ Aspect ', representing that the class is a section class, defining a tangent point by using @ Pointcut' annotation for matching a method needing to add log records, secondly writing a corresponding front notification or rear notification by using @ Beforex 'or @ After' annotation, writing logic of log records in the notification method, recording related security audit information, configuring a file by Spring After the completion of audit, enabling an automatic proxy function of the Aspect by using @ AOP: aspect j-automatic proxy 'element to support automatic organization of the Aspect, declaring the section class as a bean, registering the bean into a Spring container, and finally recording an operation personnel or sensitive operation of a key business logic method by using Spring AOP' Beforex or @ After, and recording the operation personnel or sensitive operation of the log record in a database and inquiring the audit log database;
the implementation process of the security hole scanning is as follows:
developing a front-end module by using WebStorm and Vue.2x, wherein the front-end module comprises a ticket booking personnel interface and a form verification function, connecting Navicat to a MySQL database, managing the security configuration and access rights of the database by the database, and providing an easy-to-use and secure UI component by combining with an ElementUI library; in Vue.2x, front-end input verification is realized, and cross-site scripting attack (XSS), SQL injection and other common front-end security vulnerabilities are prevented; in WebStorm, performing static analysis and auditing of codes, and identifying and repairing potential safety problems; in MySQL, role-based access control is configured, a database is backed up periodically to prevent data loss or corruption, and active security vulnerability scanning is implemented on the system in combination with the use of a professional security vulnerability scanning tool OWASP ZAP.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311134677.XA CN117151820A (en) | 2023-09-05 | 2023-09-05 | Aviation ticket booking system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311134677.XA CN117151820A (en) | 2023-09-05 | 2023-09-05 | Aviation ticket booking system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117151820A true CN117151820A (en) | 2023-12-01 |
Family
ID=88886538
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311134677.XA Pending CN117151820A (en) | 2023-09-05 | 2023-09-05 | Aviation ticket booking system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117151820A (en) |
-
2023
- 2023-09-05 CN CN202311134677.XA patent/CN117151820A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7574483B1 (en) | System and method for change management process automation | |
| US7069234B1 (en) | Initiating an agreement in an e-commerce environment | |
| US7610233B1 (en) | System, method and article of manufacture for initiation of bidding in a virtual trade financial environment | |
| US7167844B1 (en) | Electronic menu document creator in a virtual financial environment | |
| US6629081B1 (en) | Account settlement and financing in an e-commerce environment | |
| US20220215120A1 (en) | Providing a computational script into an input slot of a computational step of a data pipeline | |
| US20020069081A1 (en) | Methods and systems for providing employment management services over a network | |
| US20020035584A1 (en) | icFoundation web site development software and icFoundation biztalk server 2000 integration | |
| EP3956777A1 (en) | Multi-participant and cross-environment pipelines | |
| US20120173297A1 (en) | Method and system for task tracking and allocation | |
| US20060185019A1 (en) | Method and system for observational data collection | |
| JP2018530092A (en) | Intellectual property portfolio management system | |
| CN111880839A (en) | API processing method and device | |
| Li | Jira 7 Essentials | |
| US20190295185A1 (en) | Secure, Customizable and Efficient System for Charitable Organization | |
| Li | Jira 8 Essentials: Effective issue management and project tracking with the latest Jira features | |
| CN117151820A (en) | Aviation ticket booking system | |
| Simaanya | Employee Management System | |
| US11113664B2 (en) | Data provisioning system and method | |
| CN112381509A (en) | Management system for major special topic of national science and technology for creating major new drug | |
| CN110807583A (en) | Configurable ERP role authority verification system and method based on RBAC | |
| US20070260983A1 (en) | Method for providing a summary of user activities | |
| Brambilla et al. | Exception handling within workflow-based web applications | |
| US20210224829A1 (en) | Communication System | |
| Wickramasinghe | IT Demand Manager Requests Management System |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |