Railway passenger ticket system business migration and reconstruction method and system thereof

Abstract

The invention discloses a railway passenger ticket system business migration reconstruction method, which comprises the steps of extracting data model public capability of each business of a railway passenger ticket through a data consanguinity analysis technology; carding the logic relationship of each business process of the railway ticket, and extracting the logic public capability of each business of the railway ticket; the method comprises the following steps: analyzing business cases, business scenes and business processes of railway tickets through an event storm technology, extracting field objects of businesses of the railway tickets, aggregating the field objects according to business correlation, and dividing a limit context; domain modeling, data model modeling and model mapping are carried out on a domain object, and technical modeling is generated; and based on technical modeling, constructing a corresponding business hierarchy architecture, and generating a migration reconstruction strategy for railway passenger ticket business logic development. According to the method, the clear domain model is constructed through the same service term, the railway passenger ticket service is reconstructed, the service complexity is reduced, and the expandability and maintainability of the system are improved.

Description

Technical Field

[0001] This application relates to the technical field of business migration and reconstruction, and particularly to a method and system for migrating and reconstructing the business of the railway passenger ticket system. Background Art

[0002] In recent years, with the continuous growth of the business volume of the railway passenger ticket system, the business scenarios have become increasingly diversified and complex, and the existing system faces many challenges. The scope of the passenger ticket business is extensive, covering complex processes such as ticket sales, ticket checking, ticket refunding, and ticket changing, and new services are continuously introduced along with business expansion. There is a tight coupling between these businesses, resulting in heavy maintenance work and high costs. Each business team develops independently, lacking a unified common capability platform and resource sharing mechanism, causing some functions to be repeatedly built and wasting R & D resources. In addition, when different business teams within the system handle the same business logic or concept, they often use different terms to express it, which to a certain extent increases the difficulty of business understanding and communication. In the long run, it not only affects the efficiency of team collaboration but also hinders the further improvement of the overall system performance.

[0003] After continuous business accumulation, the railway passenger ticket system has accumulated a huge historical code library. The development of new functions requires careful consideration of historical legacy issues, the maintainability of the code is gradually weakened, the system stability is facing tests, and the accident risk has increased.

[0004] In view of this, for the above-mentioned technical problems existing in the prior art, there is an urgent need to introduce a scientific method for migrating and reconstructing the railway passenger ticket business, aiming to comprehensively sort out and reconstruct the existing business, effectively reduce or mask the complexity of the business by refining and solidifying business knowledge, thereby significantly improving the scalability, maintainability, and overall operation efficiency of the system. Summary of the Invention

[0005] To solve the defects of the above-mentioned prior art, the present invention proposes a method and system for migrating and reconstructing the business of the railway passenger ticket system.

[0006] In a first aspect, an embodiment of the present application provides a method for migrating and reconstructing the business of the railway passenger ticket system, the method including:

[0007] Business capability refinement step: Through data lineage analysis technology, refine the common capabilities of the data models of each business of the railway passenger ticket; sort out the logical relationships of each business process of the railway passenger ticket, and refine the logical common capabilities of each business of the railway passenger ticket;

[0008] Business modeling step: Based on the common capabilities of the data model and the logical common capabilities, through event storming technology, analyze the use cases, business scenarios, and business processes of each business of the railway passenger ticket, extract the domain objects of each business of the railway passenger ticket, aggregate the domain objects according to business relevance, and divide the bounded contexts;

[0009] Technical modeling steps: Conduct domain modeling, data model modeling, and model mapping for domain objects to generate technical modeling.

[0010] Application layer development steps: Based on technical modeling, construct the corresponding business-level architecture to generate the migration and reconstruction strategy for the development of railway passenger ticket business logic.

[0011] In the embodiments of the present invention, the above-mentioned business refinement steps include:

[0012] Business annotation steps: Build a code knowledge base by functionally annotating business modules; sort out the call relationships between business modules and organize business process knowledge.

[0013] Logical common ability refinement steps: Analyze business process knowledge, refine business sub-modules with the same logic in the same business scenario, and refine logical common abilities.

[0014] In the embodiments of the present invention, the above-mentioned business refinement steps further include:

[0015] Data lineage analysis steps: Systematically organize business-related data model knowledge through data lineage analysis technology.

[0016] Data model common ability refinement steps: Organize and summarize the business knowledge contained in common fields to refine data model common abilities.

[0017] In the embodiments of the present invention, the above-mentioned business modeling steps further include:

[0018] Event storming steps: Through event storming technology, summarize and analyze the data model common abilities and logical common abilities of railway passenger ticket business.

[0019] Domain object generation steps: According to the results of event storming, split railway passenger ticket business use cases, business scenarios, and business processes respectively, extract core business information and business processes related to the business, and classify and generate railway passenger ticket business domain objects, which include: user domain, basic domain, seat domain, core transaction domain, fare domain, financial revenue domain, insurance domain, and operation and maintenance domain.

[0020] Clustering and partitioning steps: Cluster according to the business relevance between domain objects, and classify multiple clusters into bounded contexts according to business classification and semantic boundaries.

[0021] Bounded context generation steps: The finally formed bounded context serves as the service boundary in the business-level architecture.

[0022] In the embodiments of the present invention, the above-mentioned technical modeling steps further include:

[0023] Domain modeling steps: Generate application layer objects and domain layer objects through application layer modeling and domain layer modeling;

[0024] Data modeling steps: Construct a data model based on the data table structure of railway passenger ticket services, and implement the correspondence between the data table structure and the data model;

[0025] Model mapping steps: Establish mapping relationships between domain objects, data models, application layer objects, and domain layer objects.

[0026] In the embodiments of the present invention, the above domain modeling steps include:

[0027] Application layer modeling steps: Based on the knowledge of railway passenger ticket business processes, sort out the external services provided by the bounded context, implement domain modeling of the application layer, and generate application layer objects.

[0028] In the embodiments of the present invention, the above domain modeling steps include:

[0029] Domain layer modeling steps: Based on business events and behaviors, construct a domain entity object model and domain services, and generate domain layer objects.

[0030] In a second aspect, the embodiments of the present application provide a migration and reconstruction system for railway passenger ticket system services. Using the migration and reconstruction method for railway passenger ticket system services as described above, the system includes:

[0031] Business capability refinement module: Used to refine the common capabilities of the data models of each railway passenger ticket service through data lineage analysis technology; sort out the logical relationships of each railway passenger ticket business process, and refine the logical common capabilities of each railway passenger ticket service;

[0032] Business modeling module: Used to analyze each business use case, business scenario, and business process of railway passenger tickets through event storm technology based on the common capabilities of data models and logical common capabilities, extract the domain objects of each railway passenger ticket service, aggregate domain objects according to business relevance, and divide bounded contexts;

[0033] Technical modeling module: Used to perform domain modeling, data model modeling, and model mapping for domain objects to generate technical modeling;

[0034] Application layer development module: Used to construct the corresponding business layer architecture based on technical modeling, and generate a migration and reconstruction strategy for the development of railway passenger ticket business logic.

[0035] In a third aspect, the embodiments of the present application provide a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the steps of the above migration and reconstruction method for railway passenger ticket system services are implemented.

[0036] Fourthly, an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the steps of the above-mentioned migration and reconstruction method for the railway passenger ticket system service are implemented.

[0037] Compared with the related prior art, it has the following prominent beneficial effects:

[0038] 1) The method of the present invention proposes a migration and reconstruction strategy suitable for the business of the railway passenger ticket system. By means of the same business terms, constructing a clear domain model, and dividing the bounded contexts of each business domain, etc., the railway passenger ticket business is reconstructed to reduce business complexity and improve system scalability and maintainability;

[0039] 2) The method of the present invention proposes a method for reconstructing and optimizing the railway passenger ticket business based on domain-driven design, and realizes the abstraction and reuse mechanism of common capabilities;

[0040] 3) The method of the present invention proposes a clear domain model and bounded context division, which improves system scalability and maintainability;

[0041] 4) The method of the present invention proposes a visual interface of domain-driven tools, which greatly improves the user interaction and maintainability of the migration and reconstruction functions. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The drawings described herein are used to provide a further understanding of the present application, and constitute a part of the present application. The schematic embodiments of the present application and their descriptions are used to explain the present application, and do not constitute an improper limitation to the present application. In the drawings:

[0043] Figure 1 It is a schematic flowchart of the migration and reconstruction method for the railway passenger ticket system service of the present invention;

[0044] Figure 2 It is a schematic flowchart of the migration and reconstruction method for the railway passenger ticket system service in an embodiment of the present invention;

[0045] Figure 3 It is a schematic flowchart of the refund business process in an embodiment of the present invention;

[0046] Figure 4 It is a schematic diagram of the generation of domain objects in an embodiment of the present invention;

[0047] Figure 5 It is a schematic diagram of domain objects in the passenger ticket system in an embodiment of the present invention;

[0048] Figure 6 It is a schematic diagram of the application service in the passenger ticket system in an embodiment of the present invention;

[0049] Figure 7Schematic diagram of the user interface of the method for migrating and reconstructing the railway ticket system in the embodiments of the present invention;

[0050] Figure 8 Schematic diagram of the system for migrating and reconstructing the railway ticket system business of the present invention;

[0051] Figure 9 Schematic diagram of the computer hardware of the present invention. Detailed implementation manners

[0052] It should be noted that the processor described in the present invention is the control center of the electronic device, which can be a single processor or a collective term for multiple processing elements. For example, it can be one or more central processing units (CPUs), or an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present invention. For example: one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs).

[0053] Optionally, the processor can execute various functions of the electronic device by running or executing the software program stored in the memory and calling the data stored in the memory.

[0054] In a specific implementation, as an embodiment, the processor can include one or more CPUs. Each of these processors can be a single core processor or a multi-core processor. Here, the processor can refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions). The electronic device can include: servers, desktop computers, laptop computers, smart phones, tablet computers, embedded computers, etc., where the embedded computer includes vehicles and robots, etc.

[0055] The memory is used to store the software program for implementing the solution of the present invention and is controlled by the processor for execution. The specific implementation manner can refer to the above method embodiments and will not be elaborated here.

[0056] It should be noted that the structure of the electronic device shown in the drawings of the present invention does not constitute a limitation thereto. The actual knowledge structure recognition device may include more or fewer components than shown in the drawings, or combine some components, or have different component arrangements.

[0057] The above embodiments can be implemented in whole or in part by software, hardware (such as circuits), firmware, or any other combination. When implemented using software, the above embodiments can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions described in the embodiments of the present invention are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that contains one or more collections of available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, or magnetic tape), an optical medium (such as a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state drive.

[0058] It should also be understood that the term "and / or" in this document is merely a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. Here, A and B can be singular or plural. In addition, the character " / " in this document generally represents an "or" relationship between the associated objects before and after, but it may also represent an "and / or" relationship, which can be specifically understood with reference to the context before and after.

[0059] In the present invention, "at least one" means one or more, and "a plurality" means two or more. "At least one of the following" or its similar expressions refer to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, a - b, a - c, b - c, or a - b - c, where a, b, and c can be single or multiple.

[0060] It should also be understood that in various embodiments of the present invention, the magnitudes of the sequence numbers of the above processes do not mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

[0061] In several embodiments provided by the present invention, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections between each other can be through some interfaces. The indirect couplings or communication connections of the devices or units can be in electrical, mechanical, or other forms.

[0062] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0063] In addition, in each embodiment of the present invention, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0064] If the above functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs, etc., all kinds of media that can store program codes.

[0065] To make the above features and effects of the present invention more clearly and understandably described, specific embodiments are hereinafter given and detailed descriptions are made in conjunction with the accompanying drawings of the specification as follows. This specification discloses one or more embodiments incorporating the features of the present invention. The disclosed embodiments are only for illustrative purposes. The protection scope of the present invention is not limited to the disclosed embodiments, and the present invention is defined by the appended claims.

[0066] The following is a system embodiment corresponding to the above method embodiment. This embodiment can be implemented in cooperation with the above embodiment. The relevant technical details mentioned in the above embodiment are still valid in this embodiment. To avoid repetition, they will not be elaborated here. Correspondingly, the relevant technical details mentioned in this embodiment can also be applied to the above embodiment.

[0067] The present invention proposes a method for reconstructing and optimizing the railway passenger ticket business based on domain-driven design, aiming to reconstruct the railway passenger ticket business by means of the same business terms, constructing a clear domain model, dividing the bounded contexts of each business domain, etc., reducing business complexity, and improving the scalability and maintainability of the system.

[0068] The following will be described in detail with specific embodiments.

[0069] Embodiment 1

[0070] As Figure 1 shown, Figure 1 is a method for migrating and reconstructing the business of a railway passenger ticket system disclosed in an embodiment of the present invention. The method includes:

[0071] Business capability refinement step 101: Through data lineage analysis technology, refine the common capabilities of the data models of each business of railway passenger tickets; sort out the logical relationships of each business process of railway passenger tickets, and refine the logical common capabilities of each business of railway passenger tickets;

[0072] Business sorting involves in-depth analysis of the existing code library and stored procedures, aiming to refine the core knowledge of the business process, summarize the common capabilities, and lay a knowledge foundation for the subsequent business modeling work. Through data lineage analysis technology, systematically organize the data model knowledge related to the business, such as orders, stubs, train numbers, dispatching orders, etc. At the same time, sort out and summarize the business knowledge contained in the common fields, and refine the common capabilities of the data model. Through careful annotation of the business code, build a code knowledge base for subsequent personnel to learn and refer to. At the same time, sort out the call relationships between the codes, so as to sort out the knowledge of the business process. Through in-depth analysis of the business process, the codes with similar logic in similar business scenarios can be refined as common capabilities to enhance the cohesion of the business.

[0073] Business modeling step 102: Based on the common capabilities of the data model and the logical common capabilities, through event storming technology, analyze each business use case, business scenario, and business process of railway passenger tickets, extract the domain objects of each business of railway passenger tickets, aggregate the domain objects according to business relevance, and divide the bounded context;

[0074] Business modeling classifies and organizes the knowledge extracted during the business process, clarifies domain objects, and divides bounded contexts such as core transactions, basics, seats, and users. Through event storming of operations such as normal ticket refund, section refund difference, special handling ticket refund, and connecting ticket refund, use case analysis, scenario analysis, and business process analysis are carried out to identify key events, behaviors, and business dependencies, and then core objects in the domain such as entities and value objects are generated. Domain objects cluster the same data models used in different functions according to their relevance to the business, and according to business classification and semantic boundaries, multiple clusters are assigned to one bounded context. The finally formed bounded context will serve as the service boundary in the microservice architecture.

[0075] Technical modeling step 103: Perform domain modeling, data model modeling, and model mapping for domain objects to generate technical modeling;

[0076] Technical modeling is a process of performing domain modeling, data model modeling, and model mapping for domain objects based on business modeling. Domain modeling includes two parts: application layer (App layer) design and domain layer (Domain layer) design. Application layer design mainly sorts out the external services provided by the bounded context based on business knowledge. Domain layer design constructs domain entity object models such as ticket refund orders, ticket refund stubs, handling fees, and transaction information, as well as domain services such as recording orders, applying for free children, and obtaining ticket refund handling fees, based on business events and behaviors. Data model design constructs the data model according to the table structure to achieve the correspondence between the data table structure and the model. Model mapping is to establish the mapping relationship between domain objects and data models, and between application layer objects and domain objects, providing data support for the automatic conversion of domain and application objects.

[0077] Application layer development step 104: Based on technical modeling, construct the corresponding business layer architecture to generate the migration and reconstruction strategy for the development of railway passenger ticket business logic.

[0078] Based on the technical modeling design, the corresponding code layer architecture can be formulated and the development of business logic can be carried out.

[0079] Embodiment 2

[0080] As Figure 2 shown, Figure 2 shown, a method for migrating and reconstructing the business of a railway passenger ticket system, the method includes:

[0081] Business capability refinement step 201: Through data lineage analysis technology, refine the common capabilities of the data models of each business of railway passenger tickets; sort out the logical relationships of each business process of railway passenger tickets and refine the common logical capabilities of each business of railway passenger tickets;

[0082] In the embodiment of the present invention, the above-mentioned service refinement step 201 includes:

[0083] Service annotation step 2011: By functionally annotating the service modules, construct a code knowledge base; sort out the call relationships between service modules and organize service process knowledge;

[0084] Logical common ability refinement step 2012: Analyze service process knowledge, refine service sub-modules with the same logic in the same service scenario, and refine logical common abilities, where the logical common abilities are processes and events that can provide reuse capabilities in service logic.

[0085] In the embodiment of the present invention, the above-mentioned service refinement step 201 further includes:

[0086] Data lineage analysis step 2013: Through data lineage analysis technology, systematically organize the data model knowledge related to services;

[0087] Data model common ability refinement step 2014: Organize and summarize the service knowledge contained in common fields, and refine the data model common abilities.

[0088] As Figure 3 shown, in a specific embodiment of the present invention, taking the ticket refund service as an example, the service sorting and refinement ability is as follows: Through stored procedure analysis, sort out the ticket refund service process and logic. The process is sorted into a swimlane diagram. The ticket refund service is divided into 2 main processes, namely pre-ticket refund check and confirm ticket refund. Among them, the pre-endorsement check is further divided into 4 sub-processes, and the confirm ticket refund is divided into 5 sub-processes as shown in the following figure.

[0089] Service modeling step 202: Based on the data model common ability and logical common ability, through event storm technology, analyze each service use case, service scenario, and service process of railway passenger tickets, extract the domain objects of each railway passenger ticket service, aggregate the domain objects according to service relevance, and divide the bounded context;

[0090] In the embodiment of the present invention, the above-mentioned service modeling step 202 further includes:

[0091] Event storm step 2021: Through event storm technology, analyze the data model common ability and logical common ability of railway passenger ticket services, extract the domain objects of each railway passenger ticket service, and divide the bounded context;

[0092] Domain object generation step 2022: According to the results of the event storm, split the service use cases, service scenarios, and service processes of railway passenger tickets respectively, extract the core service information and service processes related to services, and classify and generate the domain objects of railway passenger ticket services. The domain objects include: user domain, basic domain, seat domain, core transaction domain, fare domain, financial receipt domain, insurance domain, and operation and maintenance domain;

[0093] Clustering division step 2023: Cluster according to the business relevance between domain objects, and classify multiple clusters into bounded contexts based on business classification and semantic boundaries;

[0094] Bounded context generation step 2024: The finally formed bounded context serves as the service boundary in the business hierarchical architecture.

[0095] 1) Business modeling: Through event storming, all domain objects are sorted out through use cases, scenarios, and business process analysis, aggregates are formed according to business relevance, and bounded contexts are further divided.

[0096] As Figure 4 shown, in the specific embodiment of the present invention, it can be seen from the storm that business use cases are as follows: users are divided into customers and staff, so the user domain is abstracted to be responsible for relevant functions such as user information permissions. Business scenarios are as follows: when a customer buys a ticket, the ticket price is required, so the ticket price domain is sorted out. Information such as the stop time and seat of the seat is required to refine the seat domain. An order needs to be recorded when buying a ticket, so the core transaction domain is formed. Customers may buy accident insurance, so the insurance domain is formed. Business processes are as follows: the finance department needs to count information such as ticket sales amounts, so the financial revenue domain is formed. In case of emergencies such as checking for missing numbers and stubs, the operation and maintenance domain is formed.

[0097] 2) As Figure 5 shown, finally, the passenger ticket system is divided into 8 domains in total. The user domain is responsible for all information related to user permissions, etc. The basic domain is responsible for all information related to the road network basic data and train number information basic data. The seat domain is responsible for all information related to seats, dispatching orders, plans, etc. The core transaction domain is responsible for the execution of various transactions.

[0098] Technical modeling step 203: Perform domain modeling, data model modeling, and model mapping for domain objects to generate technical modeling;

[0099] In the embodiment of the present invention, the above technical modeling step 203 further includes:

[0100] Domain modeling step 2031: Generate application layer objects and domain layer objects through application layer modeling and domain layer modeling;

[0101] Data modeling step 2032: Construct a data model according to the data of railway passenger ticket business to realize the correspondence between the data table structure and the data model;

[0102] Model mapping step 2033: Establish a mapping relationship between domain objects, data models, application layer objects, and domain layer objects.

[0103] In the embodiment of the present invention, the above domain modeling step 2031 includes:

[0104] Application layer modeling steps: Based on the knowledge of railway passenger ticket business processes, sort out the external services provided by the bounded context, implement domain modeling of the application layer, and generate application layer objects.

[0105] In the embodiment of the present invention, the above-mentioned domain modeling step 2031 includes:

[0106] Domain layer modeling steps: Based on business events and behaviors, build domain entity object models and domain services to generate domain layer objects.

[0107] like Figure 6 and Figure 7 As shown, in the specific embodiment of the present invention, technical modeling is performed on the above-mentioned fields. Application services, domain services, data models, etc. are designed. Taking the basic domain as an example, it is divided into 5 application services, refund rate application service (calculate refund rate), small dictionary application service (provide small dictionary information), cross-border application service (judge cross-border information), online refund basic domain application service (this service aggregates multiple parameters that need to be obtained from the basic domain and returns them at one time to reduce the number of RPCs), stop application service (provide stop information), and train number application service. Data modeling is mainly based on the existing table structure, and the relevant data models are classified into the corresponding fields. For example, the stop data model is classified into the basic domain.

[0108] Application layer development step 204: Based on technical modeling, build a corresponding business layer architecture and generate a migration and reconstruction strategy for railway ticket business logic development.

[0109] Embodiment 3

[0110] like Figure 8 As shown, Figure 8 The embodiment of the present application provides a railway ticket system service migration and reconstruction system, using the railway ticket system service migration and reconstruction method, the system includes:

[0111] Business capability extraction module 301: used to extract the common capabilities of the data model structure of each railway passenger ticket business through data lineage analysis technology; sort out the logical relationship of each railway passenger ticket business process, and extract the common logical capabilities of each railway passenger ticket business;

[0112] Business modeling module 302: used to analyze various business use cases, business scenarios, and business processes of railway passenger tickets based on data model common capabilities and logic common capabilities through event storming technology, extract domain objects of various railway passenger ticket businesses, aggregate domain objects according to business relevance, and divide bounded contexts;

[0113] Technical modeling module 303: used to perform domain modeling, data modeling and model mapping for domain objects and generate technical modeling;

[0114] Application layer development module 304: It is used to build the corresponding business layer architecture based on technical modeling and generate a migration and reconstruction strategy for the development of railway passenger ticket business logic.

[0115] Example 4

[0116] An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, the steps of the above-mentioned migration and reconstruction method for the railway passenger ticket system business are implemented.

[0117] Example 5

[0118] An embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the steps of the above-mentioned migration and reconstruction method for the railway passenger ticket system business are implemented.

[0119] In addition, combined with Figure 1 The migration and reconstruction method for the railway passenger ticket system business described in the embodiments of the present application can be implemented by an electronic device, such as a computer device. Figure 9 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present application.

[0120] In some of these embodiments, the computer device may further include a communication interface 83 and a bus 80. Among them, as Figure 9 shown, the processor 81, the memory 82, and the communication interface 83 are connected through the bus 80 to complete mutual communication.

[0121] Specifically, the above-mentioned processor 81 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured as one or more integrated circuits for implementing the embodiments of the present application.

[0122] The memory 82 can be used to store or cache various data files required for processing and / or communication, as well as possible computer program instructions executed by the processor 81.

[0123] The processor 81 reads and executes the computer program instructions stored in the memory 82 to implement any one of the above-mentioned migration and reconstruction methods for the railway passenger ticket system business.

[0124] The technical features of the above-mentioned embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above-mentioned embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope described in this specification.

[0125] The embodiments described above merely represent several implementation manners of the present application. The description is relatively specific and detailed, but it should not be construed as a limitation on the scope of the invention patent. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all fall within the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the appended claims.

Claims

1. A method for migrating and reconstructing railway ticket system services, characterized in that: The method comprises: Business capability extraction steps: Extract the domain public capabilities of typical railway passenger ticket businesses through data lineage analysis technology; sort out the logical relationship of typical railway passenger ticket business processes and extract the application public capabilities of typical railway passenger ticket businesses; Business modeling step: Based on the domain common capabilities and logical common capabilities, the typical business use cases, business scenarios, and business processes of railway passenger tickets are analyzed through event storming technology, subdomain objects of the typical railway passenger ticket business are extracted, the subdomain objects are aggregated according to business relevance, and bounded contexts are divided; Technical modeling step: performing domain modeling, data model modeling and model mapping for the domain objects to generate a technical model; Application layer development steps: Based on the technical modeling, build the corresponding business layer architecture and generate the migration and reconstruction strategy for the railway ticket business logic development.

2. The method for migrating and reconstructing railway ticket system services according to claim 1, characterized in that: The business refining steps include: Business annotation step: Build a code knowledge base by annotating the functions of business modules; sort out the calling relationships between the business modules and organize business process knowledge; Logical common capability extraction step: Analyze the business process knowledge, extract business sub-modules with the same logic in the same business scenario, and extract logical common capabilities, where the logical common capabilities are processes and events in the business logic that can provide reuse capabilities.

3. The method for migrating and reconstructing railway ticket system services according to claim 2, characterized in that: The business refining step also includes: Data lineage analysis steps: By analyzing and organizing the data relevance of existing business processing flows, a visual display of the dependency relationship between data and business is provided; Data model common capability extraction step: sort out and summarize the business knowledge contained in the common fields, and extract the data model common capabilities, where the data model common capabilities are data model reading events that can provide reuse capabilities in business logic.

4. The method for migrating and reconstructing railway ticket system services according to claim 1 or 3, characterized in that: The business modeling step further includes: Event Storming Steps: Use event storming technology to sort out, summarize and analyze the data model public capabilities and logical public capabilities of the railway passenger ticket business; Domain service generation step: according to the result of the event storm, the railway passenger ticket business use cases, business scenarios and business processes are split respectively, the core business information and business processes related to the business are extracted, and the railway passenger ticket business domain objects are classified and generated. The domain services include: user domain, basic domain, seat domain, core transaction domain, fare domain, financial collection domain, insurance domain and operation and maintenance domain; Clustering step: clustering is performed according to the business relevance between the domain objects, and multiple clusters are classified into bounded contexts according to business classification and semantic boundaries; Bounded context generation step: The bounded context finally formed serves as the application service boundary in the business level architecture.

5. The method for migrating and reconstructing railway ticket system services according to claim 1 or 3, characterized in that: The technical modeling step further comprises: Domain modeling steps: Generate application layer objects and domain layer objects through application layer modeling and domain layer modeling; Data modeling step: constructing a data model according to the data structure of the railway passenger ticket business to achieve the correspondence between the data structure and the data model; Model mapping step: establishing a mapping relationship between the domain object and the data model, application layer objects and domain layer objects.

6. The method for migrating and reconstructing railway ticket system services according to claim 5, characterized in that: The domain modeling steps include: Application layer modeling step: Based on the railway passenger ticket business process knowledge, sort out the external services provided by the bounded context, implement domain modeling of the application layer, and generate the application layer objects.

7. The method for migrating and reconstructing railway ticket system services according to claim 5, characterized in that: The domain modeling steps include: Domain layer modeling step: Based on business events and behaviors, build domain entity object models and domain services to generate the domain layer objects.

8. A railway ticket system service migration and reconstruction system, using a railway ticket system service migration and reconstruction method as claimed in any one of claims 1 to 7, characterized in that: The system comprises: Business capability extraction module: It is used to extract the data model common capabilities of typical railway passenger ticket businesses through data lineage analysis technology; sort out the logical relationship between various business processes of railway passenger tickets, and extract the logical common capabilities of various railway passenger ticket businesses; Business modeling module: used to analyze various business use cases, business scenarios, and business processes of railway passenger tickets based on the common capabilities and logical common capabilities of the data model through event storming technology, extract the domain objects of various railway passenger ticket businesses, aggregate the domain objects according to business relevance, and divide the bounded context; Technical modeling module: used to perform domain modeling, data modeling and model mapping for the domain objects, and generate technical modeling; Application layer development module: used to build the corresponding business layer architecture based on the technical modeling and generate the migration and reconstruction strategy for the railway ticket business logic development.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the migration and reconstruction method of the railway passenger ticket system business described in any one of claims 1-7 are implemented.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps of the migration and reconstruction method of the railway passenger ticket system business as described in any one of claims 1 to 7 are implemented.

Images