Business system transformation method and device, equipment, storage medium and program product

Abstract

The invention discloses a business system transformation method and device, equipment, a storage medium and a program product, and relates to the technical field of data processing, and the business system transformation method comprises the steps: receiving a data warehouse transformation project for an upstream business system; serial connection object identification is carried out according to the multi-warehouse reconstruction project, and a serial connection reconstruction object is obtained; and according to the serial modification object, generating a to-do task and sending the to-do task to a corresponding to-be-modified downstream business system, so that a developer of the to-be-modified downstream business system performs upstream and downstream collaborative modification according to the to-do task. According to the invention, cooperative transformation of the upstream and downstream business systems based on serial object recognition is realized, the problem of production accidents caused by improper transformation of the downstream business systems in a multi-project concurrent scene of upstream and downstream cooperation is solved, and sufficient transformation of the upstream and downstream business systems in the multi-project concurrent scene is ensured; therefore, production accidents caused by subsequent production are avoided.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a business system transformation method, device, equipment, storage medium and program product. Background Art

[0002] When the various business systems of an enterprise are transformed, the database tables will be changed or reconstructed according to daily traffic and technical transformation needs. When the objects in the data warehouse are changed due to the transformation of the business system data tables or the optimization of the objects in the warehouse themselves, the downstream layers of the data warehouse need to make corresponding adaptive modifications.

[0003] In the related technology, when multiple business system transformation projects are carried out concurrently, the downstream may not be able to recognize the impact of the data warehouse transformation content of individual projects on itself, and the downstream transformation is incomplete, resulting in production accidents when it is put into production.

[0004] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention

[0005] The main purpose of this application is to provide a business system transformation method, device, equipment, storage medium and program product, aiming to solve the technical problem of production accidents caused by inadequate transformation of downstream business systems in multi-project concurrent scenarios of upstream and downstream collaboration.

[0006] To achieve the above objectives, the present application proposes a business system transformation method, the method comprising:

[0007] Accept data warehouse transformation projects for upstream business systems;

[0008] According to the data warehouse transformation project, serial connection objects are identified to obtain serial connection transformation objects;

[0009] Based on the series transformation object, a to-do task is generated and sent to the corresponding downstream business system to be transformed, so that the developers of the downstream business system to be transformed can perform upstream and downstream collaborative transformation according to the to-do task.

[0010] In one embodiment, the data warehouse transformation project includes a plurality of transformation projects, and the step of identifying the serial connection objects according to the data warehouse transformation projects to obtain the serial connection transformation objects includes:

[0011] Identifying transformation objects associated with the plurality of transformation projects;

[0012] The transformation objects associated with the plurality of transformation projects are connected in series to obtain series-connected transformation objects.

[0013] In one embodiment, the step of generating to-do tasks according to the serial transformation object includes:

[0014] According to the serial transformation object, an impact analysis is performed on the downstream business system corresponding to the upstream business system through field-level blood relationship to obtain an impact analysis result;

[0015] Determine the downstream business system to be transformed based on the impact analysis result;

[0016] According to the series transformation object, a to-do task of the downstream business system to be transformed is generated.

[0017] In one embodiment, after the step of generating to-do tasks according to the serial transformation object and sending them to the corresponding downstream business system to be transformed, the method further includes:

[0018] Monitor whether the upstream business system has a new downstream business system connected;

[0019] If there is a newly connected downstream business system in the upstream business system, a to-do task of the newly connected downstream business system is generated according to the series transformation object and sent to the newly connected downstream business system.

[0020] In one embodiment, after the step of generating to-do tasks according to the serial transformation object and sending them to the corresponding downstream business system to be transformed, the method further includes:

[0021] Monitoring the processing status of the pending tasks;

[0022] If the processing status of the pending task is modified, determining that the downstream business system to be modified is a modified downstream business system;

[0023] Reading the transformation content of the to-do task, performing a series connection process on the series connection transformation object and the transformation content, and obtaining a series connection transformation object after the transformation;

[0024] Performing an impact analysis based on the transformed serial transformation object to determine the affected downstream business system of the transformed downstream business system;

[0025] According to the transformed serial transformation object, a to-do task is generated and sent to the affected downstream business system.

[0026] In one embodiment, the transformation project includes at least one or more information tables including a project information table, a transformation object table and a transformation object detailed design table. The transformation object detailed design table includes at least a table name before transformation, a field name before transformation, a transformation plan, a table name after transformation and one or more field attributes in the field name after transformation. The series transformation object includes at least one transformation object detailed design table before series processing and at least one series transformation object detailed design table after series processing.

[0027] In addition, to achieve the above purpose, the present application also proposes a business system transformation device, the business system transformation device comprising:

[0028] The project receiving module is used to receive data warehouse transformation projects for upstream business systems;

[0029] A series connection identification module, used to identify series connection objects according to the data warehouse transformation project to obtain series connection transformation objects;

[0030] The collaborative transformation module is used to generate pending tasks according to the serial transformation objects and send them to the corresponding downstream business systems to be transformed, so that the developers of the downstream business systems to be transformed can perform upstream and downstream collaborative transformation according to the pending tasks.

[0031] In addition, to achieve the above-mentioned purpose, the present application also proposes a business system transformation device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the business system transformation method described above.

[0032] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the business system transformation method described above are implemented.

[0033] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the business system transformation method described above are implemented.

[0034] The present application provides a business system transformation method, which first receives a data warehouse transformation project for an upstream business system to determine the initial demand for data warehouse transformation of the upstream business system transformation; obtains a serial transformation object according to serial object identification of the received data warehouse transformation project to unify different data warehouse transformation objects into a serial transformation object; generates to-do tasks for a downstream business system that needs to be transformed according to the serial transformation object, and sends the to-do tasks to the downstream business system that needs to be transformed, so that developers of the downstream business system can carry out collaborative transformation of the upstream and downstream business systems, thereby realizing collaborative transformation of the upstream and downstream business systems based on serial object identification, solving the problem of production accidents caused by inadequate transformation of the downstream business system in multi-project concurrent scenarios of upstream and downstream collaboration, ensuring sufficient transformation of the upstream and downstream business systems in multi-project concurrent scenarios, and thus avoiding production accidents in subsequent production. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0037] Figure 1 A flowchart of the first embodiment of the business system transformation method of the present application is provided;

[0038] Figure 2 A flowchart of the second embodiment of the business system transformation method of the present application is provided;

[0039] Figure 3 This is a schematic diagram of the architecture of the incremental recognition and task collaboration system involved in the third embodiment of the business system transformation method of this application;

[0040] Figure 4 An entity relationship diagram of a data change notification module involved in the third embodiment of the business system transformation method of this application;

[0041] Figure 5 A schematic diagram of the process of system data change notification involved in the third embodiment of the business system transformation method of this application;

[0042] Figure 6 A schematic diagram of a process for integrating the serial transformation objects involved in the third embodiment of the business system transformation method of the present application;

[0043] Figure 7 This is a schematic diagram of the module structure of the business system transformation device according to an embodiment of the present application;

[0044] Figure 8 This is a schematic diagram of the device structure of the hardware operating environment involved in the business system transformation method in the embodiment of the present application.

[0045] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0046] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0047] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0048] The main solution of the embodiment of the present application is: receiving a data warehouse transformation project for an upstream business system; identifying series objects according to the data warehouse transformation project to obtain series transformation objects; generating to-do tasks according to the series transformation objects and sending them to the corresponding downstream business system to be transformed, so that the developers of the downstream business system to be transformed can perform upstream and downstream collaborative transformation according to the to-do tasks.

[0049] Due to the existing technology, each business system will make changes or reconstructions to the database table in daily traffic and technical transformation needs. Common change operations include adding or deleting fields, changing field types, and reconstructions such as splitting tables into multiple new tables or merging multiple tables into one table according to specific business rules. When objects in the data warehouse are changed due to business system data table transformation or warehouse object optimization, all downstream layers of the data warehouse need to make corresponding adaptive transformations.

[0050] During the transformation of the data warehouse, there are the following pain points in upstream and downstream and inter-project collaboration:

[0051] (1) When multiple projects are running concurrently, it may not be possible to identify the transformation content of individual projects, and it is impossible to determine the impact of content changes or abandoned fields in the project on its own data warehouse model. For example, one project optimizes model A and requires the downstream to switch to another new model B; the second project needs to abandon some fields of the new model B. When the downstream is not connected to the new model B, it is impossible to identify the impact of the abandoned fields of the second project on its own model.

[0052] (2) Newly connected downstreams cannot recognize the detailed design of the model being transformed. After the detailed design of the model in the data warehouse is completed, the detailed design content will be sent to the downstream. It can only be sent to the downstream that has already been connected. Newly connected downstreams will not receive the detailed design notification.

[0053] (3) When multiple projects are running concurrently, the data warehouse object transformation design, development, testing, and production stages are not properly notified, and downstream data transformation is not timely, which can easily lead to report data errors and even production accidents.

[0054] This application solves the problem of production accidents caused by inadequate transformation of downstream business systems in multi-project concurrent scenarios of upstream and downstream collaboration through the coordinated transformation of upstream and downstream business systems for serial object identification, ensuring the full transformation of upstream and downstream business systems in multi-project concurrent scenarios, thereby avoiding production accidents in subsequent production.

[0055] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, a business system transformation device, etc. The following takes the business system transformation device as an example to illustrate this embodiment and the following embodiments.

[0056] Based on this, the present application embodiment provides a business system transformation method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the business system transformation method of the present application.

[0057] In this embodiment, the business system transformation method includes steps S10 to S30:

[0058] Step S10, receiving a data warehouse transformation project for an upstream business system;

[0059] It should be noted that the upstream business system refers to the starting point of the data flow, that is, the original system for data production and processing. Data warehouse transformation projects refer to projects that change the data warehouse structure, tables, fields, etc., usually to optimize performance, adjust data structure or support new business needs. The transformation may affect the data structure, data flow and data processing logic, so the downstream business system needs to be transformed accordingly, such as adjusting the table structure, adding or deleting data fields, changing the data processing process, etc.

[0060] It is understandable that the transformation may affect the data structure, data flow and data processing logic, which requires corresponding adjustments to the downstream business system. In order to ensure that the downstream business system is aware of the upcoming data warehouse transformation so that it can be prepared for the downstream transformation, it is necessary to obtain and identify detailed information about the data warehouse transformation project of the upstream business system.

[0061] Step S20, identifying a series connection object according to the data warehouse transformation project to obtain a series connection transformation object;

[0062] It should be noted that serial object identification refers to identifying data warehouse transformation objects that have direct data flow or dependency with upstream business systems. Serial transformation objects refer to data warehouse objects that need to be synchronously transformed according to upstream transformations in multiple concurrent transformation projects. Identifying these objects is to ensure that downstream business systems can correctly handle new data structures or processing logic.

[0063] It can be understood that in order to identify the data warehouse objects associated with the upstream transformation projects and determine how changes to these objects will affect the downstream, based on the received data warehouse transformation projects, the objects in the project that need to be synchronously transformed are identified, and these objects are connected in series to obtain serial transformation objects, ensuring that the transformation of the downstream business system is consistent with the upstream business system transformation, avoiding data inconsistency problems.

[0064] Step S30, generating pending tasks according to the serial transformation object and sending them to the corresponding downstream business system to be transformed, so that the developers of the downstream business system to be transformed can perform upstream and downstream collaborative transformation according to the pending tasks.

[0065] It should be noted that pending tasks refer to specific transformation tasks that need to be completed in the downstream business system. These tasks ensure that the downstream business system can be consistent with the upstream transformation project. Upstream and downstream collaborative transformation refers to the transformation synchronization process between the upstream and downstream business systems. Through upstream and downstream collaborative transformation, the consistency and stability of the entire system can be ensured, avoiding system failures caused by inconsistent data.

[0066] It is understandable that to-do tasks are generated based on the serial transformation objects and distributed to the developers of the downstream business systems to ensure that they can timely understand the transformation tasks that need to be performed and synchronize the transformation of the upstream business systems to carry out the corresponding downstream business system transformation processing, so as to achieve effective collaborative transformation between the upstream and downstream business systems, ensure that the downstream business systems can smoothly adapt to the changes in the upstream systems, and enable the transformation process to proceed in an orderly manner through task management, reducing the risk of inconsistent transformation between the upstream and downstream systems.

[0067] In a feasible implementation manner, the data warehouse transformation project includes a plurality of transformation projects, and the step of identifying the serial connection objects according to the data warehouse transformation projects to obtain the serial connection transformation objects includes:

[0068] Step S201, identifying transformation objects associated with the plurality of transformation projects;

[0069] It should be noted that associated transformation objects refer to transformation objects that are commonly involved or affect each other in multiple transformation projects. They need to be processed collaboratively to ensure consistency. Specific identification methods usually include analyzing project documents, dependency diagrams, and transformation requirements.

[0070] It is understandable that in a data warehouse transformation project, different transformation projects may involve the same system components or data tables. By identifying the relationships between transformation projects, we can understand how these projects affect each other, especially which transformation objects appear in multiple projects. Being able to accurately identify the relationships between transformation objects helps to carry out the transformation in a systematic manner, ensuring that all relevant parts are taken into account, thereby avoiding omissions and potential problems.

[0071] Step S202: performing serial connection processing on the transformation objects associated with the plurality of transformation projects to obtain serial connection transformation objects.

[0072] It should be noted that serial processing involves integrating related transformation objects together to perform centralized transformation, such as aggregating all related transformation objects in a unified view or data table, so that the transformation can be managed and implemented more efficiently.

[0073] It can be understood that integrating related transformation objects in multiple transformation projects in series to form series-combined transformation objects that need to be transformed synchronously can ensure the consistency and integrity of all related transformation objects, avoid duplication of work in the transformation phase and failures in upstream and downstream collaboration in the production phase.

[0074] In this implementation, the serial processing of transformation projects ensures that all related transformation objects are transformed at the same time or step, and the integrated task management provides centralized coordination and task allocation, ensuring that the transformation activities of multiple projects can be carried out in an orderly manner, thereby improving the overall efficiency of data warehouse transformation, avoiding omissions and inconsistencies, and achieving comprehensive, coordinated and efficient transformation of data warehouses in upstream and downstream collaboration and multi-project concurrent scenarios.

[0075] In a feasible implementation manner, the step of generating to-do tasks according to the serial transformation object includes:

[0076] Step S301, performing an impact analysis on the downstream business system corresponding to the upstream business system through field-level blood relationship according to the serial transformation object, and obtaining an impact analysis result;

[0077] It should be noted that field-level lineage refers to the path that describes the data flow, a mapping relationship from the source of the data to its terminal, which is used to identify dependencies between data.

[0078] It can be understood that according to the serial transformation objects, the flow path of data from the source (upstream business system) to the terminal (downstream business system) is tracked through field-level lineage analysis, and how changes in the upstream system affect the relevant data of the downstream system is identified, thus obtaining the analysis results of the impact of the upstream business system transformation on the downstream business system.

[0079] Step S302, determining the downstream business system to be transformed based on the impact analysis result;

[0080] It is understandable that the impact analysis results reveal which downstream business systems will be affected by the transformation object. Based on these results, the downstream business systems that need to be transformed are determined to ensure that the transformation work is concentrated on those systems that are actually affected by the transformation of the upstream business systems, avoid unnecessary transformation work, and improve resource utilization efficiency.

[0081] Step S303: generating to-do tasks for the downstream business system to be transformed according to the series transformation object.

[0082] It should be noted that the pending tasks refer to the specific transformation tasks formulated for each downstream business system, which may involve the content affected by the upstream transformation, the downstream operational transformation objects, the downstream transformation plan, etc.

[0083] It is understandable that based on the identified downstream business systems to be transformed, specific tasks to be done are formulated and work is assigned to relevant personnel to systematically advance the transformation project and ensure that each downstream business system to be transformed can be properly handled.

[0084] In this implementation, through field-level blood relationship analysis, the impact of upstream systems on downstream systems can be quickly and accurately identified, reducing manual errors and analysis time. Through the integrated task management platform, to-do tasks can be systematically generated and assigned to ensure that all affected downstream business systems are processed in a timely manner, and task allocation and tracking are more efficient, avoiding duplication of work and waste of resources, thereby improving the overall efficiency of the transformation project. It can achieve efficient and accurate management of data warehouse transformation projects, ensuring the orderly advancement of transformation tasks and the successful implementation of upstream and downstream collaborative transformation.

[0085] In a feasible implementation manner, the transformation project includes at least one or more information tables including a project information table, a transformation object table and a transformation object detailed design table; the transformation object detailed design table includes at least a table name before transformation, a field name before transformation, a transformation plan, a table name after transformation and one or more field attributes in the field name after transformation; the series transformation object includes at least one transformation object detailed design table before series processing and at least one series transformation object detailed design table after series processing.

[0086] It should be noted that the project information table refers to the basic information of the transformation project, such as the project name, person in charge, timetable, etc., which is used to provide the overall information and management framework of the transformation project. The transformation object table refers to the project listing all data objects that need to be transformed, including table names, field names, etc., which is used to clarify which data objects need to be transformed and provide a basis for subsequent analysis and transformation. The transformation object detailed design table contains specific field information and transformation plans before and after the transformation. The field attributes include the table name before transformation, the field name before transformation, the transformation plan, the table name after transformation, the field name after transformation, etc., which are used to provide detailed design information for the transformation and to implement and verify the transformation process. The serial transformation object includes detailed design tables before and after the transformation, which describe the data flow and changes in the transformation object, and are used to help identify and track the scope of the transformation and the data flow path.

[0087] It can be understood that the combination of the project information table, the transformation object table, the transformation object detailed design table and the detailed design table of the serial transformation objects can automatically generate and assign to-do tasks to ensure that every part of the transformation project is processed and the progress of the tasks is tracked. It can also clearly show the changes in data before and after the transformation, help to comprehensively evaluate the impact of the transformation, and make corresponding adjustments, avoiding duplication of work and waste of resources, thereby improving the overall efficiency and quality of the transformation project.

[0088] This embodiment provides a business system transformation method, which realizes the coordinated transformation of upstream and downstream business systems based on serial object identification, solves the problem of production accidents caused by inadequate transformation of downstream business systems in multi-project concurrent scenarios of upstream and downstream collaboration, ensures the full transformation of upstream and downstream business systems in multi-project concurrent scenarios, and thus avoids production accidents in subsequent production.

[0089] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the first embodiment can refer to the above introduction, and will not be repeated in the following. Figure 2 , Figure 2 This is a flow chart of the second embodiment of the business system transformation method of the present application.

[0090] In this embodiment, after the step of generating to-do tasks according to the serial transformation object and sending them to the corresponding downstream business system to be transformed, the following step is further included:

[0091] Step S401, monitoring whether the upstream business system has a newly connected downstream business system;

[0092] It should be noted that determining whether a new business system has been connected is usually done through a system integration platform or monitoring tools, which can detect changes in the system architecture, such as new equipment, new interfaces or new systems.

[0093] It is understandable that in order to ensure that the system transformation tasks can be dynamically adjusted to include newly connected downstream business systems and prevent omissions, thereby ensuring the comprehensiveness and consistency of the transformation work, the upstream business system is monitored in real time to identify whether there are new downstream business systems connected.

[0094] Step S402: If there is a newly connected downstream business system in the upstream business system, a to-do task of the newly connected downstream business system is generated according to the series transformation object and sent to the newly connected downstream business system.

[0095] It can be understood that when a newly connected downstream business system is detected, to-do tasks for the new system are generated based on the existing serial transformation objects to ensure that the transformation tasks of the newly connected downstream business system are automatically generated and allocated, so that the transformation project can be smoothly promoted without being delayed due to the access of the new system.

[0096] In a feasible implementation manner, after the step of generating to-do tasks according to the serial transformation object and sending them to the corresponding downstream business system to be transformed, the step further includes:

[0097] Step S501, monitoring the processing status of the pending tasks;

[0098] It is understandable that in order to ensure that all to-do tasks are properly processed so as to promptly discover and resolve unprocessed or improperly processed issues, the processing progress of all generated to-do tasks can be monitored by using a task management system or monitoring tool.

[0099] Step S502: if the processing status of the pending task is modified, determining that the downstream business system to be modified is a modified downstream business system;

[0100] It is understandable that the processing status of the pending tasks is checked, and after confirming that the transformation is completed, the downstream business system that has completed the transformation is marked as "transformed" to ensure the system status update and the correct execution of subsequent steps.

[0101] Step S503, reading the transformation content of the pending task, performing a series connection process on the series connection transformation object and the transformation content to obtain a series connection transformation object after the transformation;

[0102] It is understandable that after the pending tasks are processed, the transformation content of the downstream business system to be transformed is integrated into the original serial transformation object, and the content and status of the serial transformation object are updated to ensure that the transformed serial transformation object accurately reflects the current downstream transformation content.

[0103] Step S504, performing an impact analysis according to the transformed series transformation object to determine the affected downstream business system of the transformed downstream business system;

[0104] It can be understood that in order to identify and analyze the impact of the transformed downstream business on its own downstream business systems and ensure that all affected systems are taken into account, the transformed series transformation objects are used to perform impact analysis to further identify the affected downstream business systems.

[0105] Step S505: Generate a to-do task based on the transformed serial transformation object and send it to the affected downstream business system.

[0106] It is understandable that in order to ensure that all downstream business systems affected by the transformation handle relevant transformation tasks in a timely manner and maintain the consistency of data classes of various business systems, new to-do tasks are generated and assigned to the affected downstream business systems based on the impact analysis results, so that the developers of the affected downstream business systems can carry out collaborative transformation.

[0107] In this implementation, by monitoring and tracking the status of pending tasks, the status and transformation content of the downstream business system can be accurately updated to ensure that the system transformation and each system data model are in the latest associated state. At the same time, through detailed impact analysis, all affected systems are identified, and tasks are generated and assigned to ensure that all systems can handle related transformation tasks in a timely manner, thereby achieving comprehensive management of the system transformation process, improving the efficiency of the transformation and the consistency between upstream and downstream systems, and reducing potential system problems.

[0108] This embodiment proposes an efficient and automated system transformation management solution. By real-time monitoring of changes in upstream business systems, it can ensure timely identification of newly connected downstream business systems, and use automated tools to generate and assign to-do tasks, thereby ensuring a smooth and seamless transformation process. Ultimately, through the task notification and tracking system, it can ensure accurate execution of tasks and monitor task progress in real time, so that the transformation work of each business system can be dynamically adjusted to fully cover newly connected systems, improve the efficiency and overall quality of transformation projects, reduce manual intervention, and reduce error rates.

[0109] Based on the first embodiment and / or the second embodiment of the present application, in the third embodiment of the present application, the same or similar contents as those of the first and second embodiments mentioned above can be referred to the above introduction and will not be repeated later.

[0110] For example, in order to help understand the implementation process of the business system transformation method obtained by combining the first embodiment and the second embodiment, please refer to Figure 3 , Figure 3This is a schematic diagram of the architecture of the incremental identification and task collaboration system involved in the third embodiment of the business system transformation method of the present application.

[0111] In this embodiment, Figure 3 As shown, the business system transformation method is applied to the upstream and downstream collaborative transformation system. The upstream and downstream collaborative transformation system mainly includes a data change notification module, a serial transformation object processing module and a system monitoring module. The design scheme of each module is described in detail below:

[0112] 1.Data change notification module:

[0113] The functions of the data change notification module mainly include detailed design, impact analysis, pending issuance and processing, incremental downstream identification and notification functions.

[0114] like Figure 4 As shown, Figure 4 This is an entity relationship diagram of the data change notification module involved in the third exemplary embodiment of the business system transformation method of this application. Among them:

[0115] (1) The project information table mainly stores project-related information, such as project number, project description, project leader, project launch date, etc.

[0116] (2) The transformation object information table mainly stores information about objects involved in the transformation in the project, such as table name, table-level transformation plan, launch date, and flow cutoff date.

[0117] (3) The transformation object field details information table mainly stores the field-level detailed design of the transformation object, including the table name, field name, field type, field-level transformation plan, etc. before and after the transformation.

[0118] (4) The transformation object impact analysis information table mainly stores the transformation object and the affected downstream information, such as the transformation object name, field name, affected downstream object name and the person in charge of the affected downstream object.

[0119] (5) The transformation object notification feedback information table stores information such as the transformation object name, project notification stage, notification content, affected downstream objects and responsible persons, and downstream object processing status.

[0120] like Figure 5 As shown, Figure 5 This is a flow chart of the system data change notification involved in the third embodiment of the business system transformation method of this application. The system data change notification module has detailed functions of issuing, receiving, processing, and feedback, and specifically includes the following steps A1 to A3:

[0121] A1. Identify the downstream objects affected by the transformation object through field-level lineage relationships, and store the impact analysis results in the system table.

[0122] A2. If there are affected downstreams, the project leader will issue pending tasks to the affected downstreams based on the impact analysis generated at each stage of the project.

[0123] A3. The downstream processes the to-do items based on the upstream object-level transformation plan, field-level detailed design, project plan and other information displayed on the task interface in the system. If it affects the downstream, the downstream can continue to do the design in the system and pass the task to the downstream.

[0124] In addition, the system data change notification module also provides the function of automatically issuing incremental to-do tasks. The system generates impact analysis for the transformation objects in unfinished projects every day through scheduled tasks, and compares the downstream objects and persons in charge generated by the impact analysis of the transformation objects in each project with the downstream objects and persons in charge who have been notified. When there are newly generated downstream objects and persons in charge who are not within the notified range, they are identified as newly connected downstreams. After the identification of the newly connected downstream is completed, the system automatically executes the issuance of to-do tasks for the newly connected downstream.

[0125] 2. Connect the transformation object processing module in series:

[0126] The serial transformation object processing module has two main functions: one is to identify the serial transformation objects of the unfinished projects at the current time point; the other is to integrate the field-level detailed designs of the identified serial objects and provide a page for downstream data classes to query the integrated detailed designs and project information.

[0127] The system is mainly used for upstream and downstream collaboration in data warehouse data transformation. There are hundreds of unfinished projects in the system every day. There may be multiple transformation objects in each project. The detailed design of each transformation object includes the table design before and after the transformation and the migration plan.

[0128] For example, Figure 6 As shown, Figure 6 The following is a flow chart of the detailed integration of the serial transformation objects involved in the third embodiment of the business system transformation method of this application. Assuming that there are currently unfinished projects 1 and 2, when object A in project 1 is transformed and migrated to object B, and object B in project 2 is transformed to object C, the system identifies similar serial transformation objects A->B->C through scheduled tasks every day.

[0129] After identifying all the projects and objects similar to the above, the system will integrate the detailed design of the serial objects. Through the two field-level detailed designs of A->B and B->C, the two detailed designs are integrated according to the fields of table B, and the integrated detailed designs and the production plans of projects 1 and 2 are displayed on the interface. The downstream can search by project number, object name, person in charge, etc.

[0130] 3. System monitoring module:

[0131] The system monitoring module mainly includes: detailed setting and distribution monitoring, pending task monitoring, serial transformation object monitoring and monitoring related reports, specifically:

[0132] (1) Detailed design and delivery monitoring: The system monitors the completion of detailed design and pending delivery of all affected objects in all projects through scheduled tasks every day.

[0133] When the impact analysis generation and to-do tasks are completed for all objects except those without impact, the detailed design of the project is considered to be completed. Otherwise, an early warning notice will be sent to the person in charge of the objects that have not completed the detailed design and to-do tasks on the seventh, third and first day before the project goes into production, respectively, via email and call, to remind the person in charge to handle it in time.

[0134] If there are still details or pending tasks that have not been completed after the project goes into production, overdue notices will be sent to the person in charge via email and phone calls every day.

[0135] (2) To-do task monitoring: The system monitors the completion status of to-do tasks issued in all projects every day through scheduled tasks.

[0136] When all the to-do statuses in the project are not incomplete, the to-do tasks of the project are considered to be completed.

[0137] Otherwise, an early warning notification will be sent to the person in charge of the unfinished tasks via email and call on the seventh, third and one day before the project goes into production, reminding them to deal with them in a timely manner.

[0138] If there are still unfinished tasks after the project goes into production, overdue notifications will be sent to the person in charge via email and phone calls every day.

[0139] (3) Monitoring of serial transformation objects: The system identifies serial transformation objects in unfinished projects through scheduled tasks every day, and sends weekly reminder notifications to the affected downstream of the first-level objects through emails and calls, informing them of the existence of serial transformations, and paying attention to the transformation plans of related projects and the integrated field-level detailed design.

[0140] On the seventh, third and one day before the production of the subsequent project, early warning notifications will be sent to the first-level downstream objects via email and calls.

[0141] After the subsequent projects are put into production, if there are still unfinished ones, overdue notices will be sent to the relevant persons in charge via email and greetings every day.

[0142] (4) Monitoring reports: In addition to the regular notification function mentioned above, it also provides detailed dispatch monitoring, pending task monitoring, and serial transformation object monitoring related report functions. Project managers can follow up on the progress of their own projects or downstream transformation through reports.

[0143] In this embodiment, the coordinated transformation of upstream and downstream business systems through serial object identification solves the problem of production accidents caused by inadequate transformation of downstream business systems in multi-project concurrent scenarios of upstream and downstream collaboration, ensuring the full transformation of upstream and downstream business systems in multi-project concurrent scenarios, thereby avoiding production accidents in subsequent production.

[0144] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the business system transformation method of the present application. More simple transformations based on this technical concept are all within the scope of protection of the present application.

[0145] This application also provides a business system transformation device, please refer to Figure 7 , the business system transformation device comprises:

[0146] A project receiving module 10 is used to receive a data warehouse transformation project for an upstream business system;

[0147] A series connection identification module 20, configured to identify series connection objects according to the data warehouse transformation project to obtain series connection transformation objects;

[0148] The collaborative transformation module 30 is used to generate pending tasks according to the serial transformation objects and send them to the corresponding downstream business systems to be transformed, so that the developers of the downstream business systems to be transformed can perform upstream and downstream collaborative transformation according to the pending tasks.

[0149] Optionally, the data warehouse transformation project includes several transformation projects, and the series identification module 20 is further used for:

[0150] Identifying transformation objects associated with the plurality of transformation projects;

[0151] The transformation objects associated with the plurality of transformation projects are connected in series to obtain series-connected transformation objects.

[0152] Optionally, the collaborative transformation module 30 is further used for:

[0153] According to the serial transformation object, an impact analysis is performed on the downstream business system corresponding to the upstream business system through field-level blood relationship to obtain an impact analysis result;

[0154] Determine the downstream business system to be transformed based on the impact analysis result;

[0155] According to the series transformation object, a to-do task of the downstream business system to be transformed is generated.

[0156] Optionally, the collaborative transformation module 30 is further used for:

[0157] Monitor whether the upstream business system has a new downstream business system connected;

[0158] If there is a newly connected downstream business system in the upstream business system, a to-do task of the newly connected downstream business system is generated according to the series transformation object and sent to the newly connected downstream business system.

[0159] Optionally, the collaborative transformation module 30 is further used for:

[0160] Monitoring the processing status of the pending tasks;

[0161] If the processing status of the pending task is modified, determining that the downstream business system to be modified is a modified downstream business system;

[0162] Reading the transformation content of the to-do task, performing a series connection process on the series connection transformation object and the transformation content, and obtaining a series connection transformation object after the transformation;

[0163] Performing an impact analysis based on the transformed serial transformation object to determine the affected downstream business system of the transformed downstream business system;

[0164] According to the transformed serial transformation object, a to-do task is generated and sent to the affected downstream business system.

[0165] Optionally, the transformation project includes at least one or more information tables including a project information table, a transformation object table and a transformation object detailed design table; the transformation object detailed design table includes at least a table name before transformation, a field name before transformation, a transformation plan, a table name after transformation and one or more field attributes in the field name after transformation; the series transformation object includes at least one transformation object detailed design table before series processing and at least one series transformation object detailed design table after series processing.

[0166] The business system transformation device provided by this application adopts the business system transformation method in the above embodiment, which can solve the technical problem of production accidents caused by inadequate transformation of downstream business systems in multi-project concurrent scenarios of upstream and downstream collaboration. Compared with the prior art, the beneficial effects of the business system transformation device provided by this application are the same as the beneficial effects of the business system transformation method provided by the above embodiment, and the other technical features in the business system transformation device are the same as the features disclosed in the above embodiment method, which will not be repeated here.

[0167] The present application provides a business system transformation device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the business system transformation method in the above-mentioned first embodiment.

[0168] Reference below Figure 8 , which shows a schematic diagram of the structure of a business system transformation device suitable for implementing the embodiment of the present application. The business system transformation device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 8 The business system transformation device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0169] like Figure 8 As shown, the business system transformation device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the business system transformation device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the business system transformation device to communicate with other devices wirelessly or wired to exchange data. Although the figure shows a business system transformation device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided instead.

[0170] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.

[0171] The business system transformation equipment provided by this application adopts the business system transformation method in the above embodiment, which can solve the technical problem of production accidents caused by inadequate transformation of downstream business systems in multi-project concurrent scenarios of upstream and downstream collaboration. Compared with the prior art, the beneficial effects of the business system transformation equipment provided by this application are the same as the beneficial effects of the business system transformation method provided by the above embodiment, and the other technical features in the business system transformation equipment are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.

[0172] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0173] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0174] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the business system transformation method in the above-mentioned embodiment.

[0175] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.

[0176] The above-mentioned computer-readable storage medium may be included in the business system transformation device; or it may exist independently without being assembled into the business system transformation device.

[0177] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the business system transformation device, the business system transformation device: D exclusive rights D.

[0178] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0179] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flowchart, and the combination of boxes in the block diagram and / or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0180] The modules involved in the embodiments of the present application may be implemented by software or hardware, wherein the name of the module does not limit the unit itself in some cases.

[0181] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned business system transformation method, and can solve the technical problem of production accidents caused by inadequate transformation of downstream business systems in multi-project concurrent scenarios of upstream and downstream collaboration. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the business system transformation method provided by the above-mentioned embodiment, and will not be elaborated here.

[0182] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned business system transformation method when executed by a processor.

[0183] The computer program product provided by this application can solve the technical problem of production accidents caused by inadequate transformation of downstream business systems in multi-project concurrent scenarios of upstream and downstream collaboration. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the business system transformation method provided in the above embodiment, and will not be repeated here.

[0184] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A business system transformation method, characterized in that: The method comprises: Accept data warehouse transformation projects for upstream business systems; According to the data warehouse transformation project, serial connection objects are identified to obtain serial connection transformation objects; Based on the serial transformation object, to-do tasks are generated and sent to the corresponding downstream business system to be transformed, so that developers of the downstream business system to be transformed can perform upstream and downstream collaborative transformation based on the to-do tasks.

2. The method according to claim 1, characterized in that: The data warehouse transformation project includes several transformation projects, and the step of identifying the serial connection objects according to the data warehouse transformation projects to obtain the serial connection transformation objects includes: Identifying transformation objects associated with the plurality of transformation projects; The transformation objects associated with the plurality of transformation projects are connected in series to obtain series-connected transformation objects.

3. The method according to claim 1, characterized in that: The step of generating to-do tasks according to the serial transformation object comprises: According to the serial transformation object, an impact analysis is performed on the downstream business system corresponding to the upstream business system through field-level blood relationship to obtain an impact analysis result; Determine the downstream business system to be transformed based on the impact analysis result; According to the series transformation object, a to-do task of the downstream business system to be transformed is generated.

4. The method according to claim 1, characterized in that: After the step of generating pending tasks according to the series transformation object and sending them to the corresponding downstream business system to be transformed, the method further includes: Monitor whether the upstream business system has a new downstream business system connected; If there is a newly connected downstream business system in the upstream business system, a to-do task of the newly connected downstream business system is generated according to the series transformation object and sent to the newly connected downstream business system.

5. The method according to claim 1, characterized in that: After the step of generating pending tasks according to the series transformation object and sending them to the corresponding downstream business system to be transformed, the method further includes: Monitoring the processing status of the pending tasks; If the processing status of the pending task is modified, determining that the downstream business system to be modified is a modified downstream business system; Reading the transformation content of the to-do task, performing a series connection process on the series connection transformation object and the transformation content, and obtaining a series connection transformation object after the transformation; Performing an impact analysis based on the transformed serial transformation object to determine the affected downstream business system of the transformed downstream business system; According to the transformed serial transformation object, a to-do task is generated and sent to the affected downstream business system.

6. The method according to any one of claims 1 to 5, characterized in that: The transformation project includes at least one or more information tables including a project information table, a transformation object table and a transformation object detailed design table. The transformation object detailed design table includes at least a table name before transformation, a field name before transformation, a transformation plan, a table name after transformation and one or more field attributes in the field name after transformation. The series transformation object includes at least one transformation object detailed design table before series processing and at least one series transformation object detailed design table after series processing.

7. A business system transformation device, characterized in that: The device comprises: The project receiving module is used to receive data warehouse transformation projects for upstream business systems; A series connection identification module, used to identify series connection objects according to the data warehouse transformation project to obtain series connection transformation objects; The collaborative transformation module is used to generate pending tasks according to the serial transformation objects and send them to the corresponding downstream business systems to be transformed, so that the developers of the downstream business systems to be transformed can perform upstream and downstream collaborative transformation according to the pending tasks.

8. A business system transformation device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the business system transformation method according to any one of claims 1 to 6.

9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the business system transformation method according to any one of claims 1 to 6 are implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the business system transformation method according to any one of claims 1 to 6 are implemented.

Images