Research and development data management methods, devices, equipment and media

Abstract

The present disclosure provides a method for managing R&D data, which can be applied to the fields of information security technology and the technology of the Internet of Things. The method for managing R&D data includes: verifying the query plan corresponding to the R&D data; executing the logical instance of the completed version according to the query plan that has passed the verification operation; and generating a data snapshot corresponding to the execution result generated by the execution operation, so as to realize the management of R&D data through the data snapshot. Therefore, it is possible to further improve the management efficiency of R&D data, while improving the accuracy of R&D data, and ensuring the accurate review of milestone data within a specific time point. In addition, the present disclosure also provides a R&D data management device, an electronic device, and a computer-readable storage medium.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a research and development data management method, device, equipment and medium. Background Art

[0002] For technology-based enterprises, R&D is the soul of their survival and development, and is a data source for internal management activities. In the context of industrial informatization, more and more technology companies are using information platforms to optimize their own R&D models to enhance their market competitiveness from the inside out. In the R&D process, R&D data, as an important part of product data, its integrity and correctness will seriously affect the quality and efficiency of a new product throughout its life cycle. Grasping the main characteristics of R&D data is the key prerequisite for the successful implementation of R&D data management. Summary of the invention

[0003] 1. Technical issues to be resolved

[0004] In order to solve at least one of the technical problems existing in R&D data management in the prior art, the present disclosure provides a R&D data management method, device, equipment and medium.

[0005] (II) Technical solution

[0006] One aspect of the present disclosure provides a method for managing R&D data, which includes: verifying a query plan corresponding to the R&D data; executing an operation on a logical instance of a completed version according to the query plan that has passed the verification operation; and generating a data snapshot corresponding to an execution result generated by the execution operation, so as to manage the R&D data through the data snapshot.

[0007] According to an embodiment of the present disclosure, in the verification operation of the query plan corresponding to the R&D data, it includes: determining that the preset database meets the preset execution range according to the query logic corresponding to the R&D data; determining that there is no execution conflict in the query plan; and verifying and executing the logic instance corresponding to the query logic.

[0008] According to an embodiment of the present disclosure, in determining whether a preset database satisfies a preset execution scope according to the query logic corresponding to the R&D data, it includes: determining input source information related to the query plan registered in the preset database; and when it is judged that the input source information corresponds to the preset execution scope, determining that the preset database satisfies the preset execution scope.

[0009] According to an embodiment of the present disclosure, determining that a query plan has no execution conflict includes: obtaining a query plan input in a platform management page; and determining that the query plan has no execution conflict when it is determined that the query plan does not correspond to a preset conflict event.

[0010] According to an embodiment of the present disclosure, in verifying and executing the logic instance corresponding to the query logic, it includes: writing the query logic as a logic instance; and verifying and executing the logic instance according to the execution plan input in the platform management page.

[0011] According to an embodiment of the present disclosure, the verification and execution of the logic instance corresponding to the query logic also includes: recording the verification execution parameters in the verification execution process; determining that the verification operation of the query plan is feasible according to the verification execution parameters; executing the version of the logic instance according to the preset version plan, and configuring the query plan with feasible verification operation into the preset database.

[0012] According to an embodiment of the present disclosure, in executing an operation on a logic instance of a completed version according to a query plan that has passed a verification operation, it includes: instantiating the logic instance according to the query plan; and executing an execution result formed by the instantiation process.

[0013] According to an embodiment of the present disclosure, in the process of instantiating a logical instance according to a query plan, it includes: initializing task execution information of the query plan; queuing the logical instance that has triggered a preset plan task according to the task execution information; and instantiating the logical instance in the queue waiting process according to the available currently idle resources.

[0014] According to an embodiment of the present disclosure, the execution result formed by executing the instantiation process includes: tracking the performance consumption parameters during the execution of the execution result; and determining that the execution process is normal based on the performance consumption parameters.

[0015] According to an embodiment of the present disclosure, generating a data snapshot corresponding to an execution result generated by an execution operation includes: performing a persistence operation on the execution result according to preset configuration information; generating a data snapshot of the persistence operation, the data snapshot having a multi-dimensional index.

[0016] According to an embodiment of the present disclosure, in implementing management of R&D data through data snapshots, the steps include: determining a customized query condition for the R&D data; and performing retrieval on the data snapshot according to the customized query condition.

[0017] According to an embodiment of the present disclosure, performing retrieval on a data snapshot according to a customized query condition includes: performing retrieval on the data snapshot in a memory cache by requesting parsing information according to the customized query condition.

[0018] According to an embodiment of the present disclosure, in performing retrieval on a data snapshot according to customized query conditions, it also includes: in the process of executing the retrieval, when the data snapshot hits the memory cache, the R&D data corresponding to the data snapshot is sorted and supplemented to realize the management of the R&D data; when the execution of the data snapshot does not hit the memory cache, the R&D data corresponding to the data snapshot is obtained from a preset database, and the R&D data is cached.

[0019] Another aspect of the present disclosure provides a research and development data management device, which includes a plan verification module, an instance execution module and a snapshot generation module. The plan verification module is used to verify the query plan corresponding to the research and development data; the instance execution module is used to execute the logical instance of the completed version according to the query plan that has passed the verification operation; and the snapshot generation module is used to generate a data snapshot corresponding to the execution result generated by the execution operation, so as to realize the management of the research and development data through the data snapshot.

[0020] Another aspect of the present disclosure provides an electronic device, including one or more processors and a memory; the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method of the embodiment of the present disclosure.

[0021] Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the method of the embodiment of the present disclosure when executed.

[0022] Another aspect of the present disclosure provides a computer program, wherein the computer program includes computer executable instructions, and the instructions are used to implement the method of the embodiment of the present disclosure when executed.

[0023] (III) Beneficial effects

[0024] The present disclosure provides a method for managing R&D data, which includes: verifying the query plan corresponding to the R&D data; executing the logical instance of the completed version according to the query plan that has passed the verification operation; and generating a data snapshot corresponding to the execution result generated by the execution operation, so as to manage the R&D data through the data snapshot. Therefore, the management efficiency of R&D data can be further improved, while the accuracy of R&D data can be improved, and the accurate review of milestone data within a specific time point is guaranteed. In addition, the present disclosure also provides a R&D data management device, an electronic device, and a computer-readable storage medium. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] For a more complete understanding of the present disclosure and its advantages, reference will now be made to the following description taken in conjunction with the accompanying drawings, in which:

[0026] Figure 1 An exemplary system architecture to which the R&D data management method according to an embodiment of the present disclosure can be applied is schematically shown;

[0027] Figure 2 A flowchart of a research and development data management method according to an embodiment of the present disclosure is schematically shown;

[0028] Figure 3 An application scenario diagram of a research and development data management method according to an embodiment of the present disclosure is schematically shown;

[0029] Figure 4 Another application scenario diagram of the R&D data management method according to an embodiment of the present disclosure is schematically shown;

[0030] Figure 5 Another application scenario diagram of the R&D data management method according to an embodiment of the present disclosure is schematically shown;

[0031] Figure 6 Another application scenario diagram of the R&D data management method according to an embodiment of the present disclosure is schematically shown;

[0032] Figure 7 The exemplary architecture of the R&D data management device according to an embodiment of the present disclosure is schematically shown;

[0033] Figure 8 A block diagram of an electronic device according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0034] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0035] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "include", "comprising", etc. used herein indicate the existence of the above-mentioned features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0036] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0037] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0038] Some block diagrams and / or flow charts are shown in the accompanying drawings. It should be understood that some boxes or combinations thereof in the block diagrams and / or flow charts can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that these instructions can create a device for implementing the functions / operations described in these block diagrams and / or flow charts when executed by the processor. The technology of the present disclosure can be implemented in the form of hardware and / or software (including firmware, microcode, etc.). In addition, the technology of the present disclosure can take the form of a computer program product on a computer-readable storage medium storing instructions, which can be used by an instruction execution system or used in conjunction with an instruction execution system.

[0039] In the existing technology, the industry currently manages data in the R&D process mainly by combining real-time data collection to generate reports with manual analysis. The R&D data is mined through real-time queries of various R&D management systems, code hosting platforms and other background databases. R&D managers need to execute batch scripts or SQL script queries at specific time points to obtain the required milestone data (such as basic project information, version arrangements, code submission status, test case submission and execution status, R&D defect rate, risk information, etc.), so as to achieve the purpose of evaluating, monitoring and continuously improving the R&D process. For data management methods involving multiple different R&D management systems and code hosting platforms, manual data fitting is still required, and specific milestone data further needs to be manually backed up offline. The management of R&D data is heavily dependent on human management, with low data accuracy and low management efficiency, and it is also impossible to review milestone data within a specific time point.

[0040] In order to solve at least one of the technical problems existing in the R&D data management process in the prior art, improve the management efficiency of R&D data, and at the same time improve the accuracy of R&D data, and ensure the accurate review of milestone data within a specific time point, the present disclosure provides a R&D data management method, device, equipment and medium.

[0041] It should be noted that the R&D data management method and device of the embodiments of the present disclosure can be applied to the fields of information security technology and the Internet of Things technology, and can also be applied to any field other than the fields of information security technology and the Internet of Things technology, such as the financial services field. The application field of the R&D data management method and device of the embodiments of the present disclosure is not specifically limited.

[0042] Figure 1 An exemplary system architecture to which the R&D data management method according to an embodiment of the present disclosure can be applied is schematically shown.

[0043] It should be noted that Figure 1 What is shown are merely application examples to which the embodiments of the present disclosure can be applied, in order to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the R&D data management method of the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios.

[0044] like Figure 1 As shown, the system architecture 100 according to this embodiment may include a data request system 110, and a server system 120 that establishes data communication with the data request system 110, wherein the server system includes servers M, 121, 122, 123, 124, and 125 that establish a research and development data management channel with the data request system 110, wherein server M is a primary access server that can obtain instruction information from users. Servers 121, 122, 123, 124, and 125 are secondary access servers, and the data request system 110 and servers M, 121, 122, 123, 124, and 125 can be implemented based on an internal cloud network server C. Alternatively, when the primary server M among the servers M, 121, 122, 123, 124, and 125 is a network server, that is, relative to the intranet of other terminal devices 111, 112, 113, 114, and 115, the primary server M of the server system 120 can be located in an external network. At this time, the cloud network server C is used as a medium for providing communication links between other terminal devices 111, 112, 113, 114 and 115. The R&D data management channel between the server system 120 and the multiple terminal devices can be implemented through various communication connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0045] It should be noted that, according to the embodiment of the present disclosure, the servers 121, 122, 123, 124 and 125 can be interconnected without encryption.

[0046] Users can use terminal devices 111, 112, 113, 114 and 115 to interact with the server system 120 to receive or send messages, etc., to achieve R&D data management or processing, specifically involving access to the database in the main server M in the server system. For example, the terminal device 111 sends business data to the terminal device 112. After receiving the data request from the terminal device 111, the server system 120 will forward the corresponding business data and encrypt the business data under specific needs, so that the business data that finally reaches the terminal device 112 is secure. Various communication client applications can be installed on the terminal devices 111, 112, 113, 114 and 115, such as management applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).

[0047] The terminal devices 111 , 112 , 113 , 114 and 115 may be various electronic devices having display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and various application servers.

[0048] The server system 120 may include various types of firewalls that provide various services, such as a filtering firewall (only an example) that provides support for websites browsed by users using terminal devices 111, 112, 113, 114, and 115. The filtering firewall may analyze and process received data such as user requests, and analyze based on the address of the data source and the flag features such as the protocol type to determine whether the request can pass, thereby filtering or blocking unsafe factors.

[0049] It should be noted that the R&D data management method provided in the embodiment of the present disclosure can generally be executed by the server system 120. Accordingly, the R&D data management device provided in the embodiment of the present disclosure can generally be set in the server system 120. The R&D data management method provided in the embodiment of the present disclosure can also be executed by other server systems 120 that are different from the server system 120 and can communicate with the terminal devices 111, 112, 113, 114 and 115 and / or the server system 120. Accordingly, the R&D data management device provided in the embodiment of the present disclosure can also be set in other server systems that are different from the server system 120 and can communicate with the terminal devices 111, 112, 113, 114 and 115 and / or the server system 120.

[0050] It should be understood that Figure 1 The number of terminal devices and servers in the embodiment is only for illustration. Any number of terminal devices and servers may be provided according to implementation requirements.

[0051] The following combination Figure 2-Figure 8 , a research and development data management method, a research and development data management device, an electronic device and a computer-readable storage medium provided by an embodiment of the present disclosure are further described in detail.

[0052] Figure 2 The flowchart of the R&D data management method according to an embodiment of the present disclosure is schematically shown.

[0053] like Figure 2 As shown, one aspect of the present disclosure provides a research and development data management method, which includes steps S201-S203.

[0054] In step S201, a verification operation is performed on the query plan corresponding to the R&D data;

[0055] In step S202, according to the query plan that has passed the verification operation, an execution operation is performed on the logical instance of the completed version production; and

[0056] In step S203, a data snapshot corresponding to the execution result generated by the execution operation is generated, so as to manage the research and development data through the data snapshot.

[0057] Figure 3 An application scenario diagram of a research and development data management method according to an embodiment of the present disclosure is schematically shown.

[0058] like Figure 3 As shown, the R&D management work of R&D personnel is described and modeled according to the business needs of the business demand side, and the data mining logic and query plan required for data collection and analysis are formulated, and compiled into business needs for submission, such as steps S301-S302. The query plan is the preferred data request method for the R&D data rows required for access processing queries, that is, the query plan corresponds to the data request method for R&D data.

[0059] Furthermore, by receiving the R&D tasks formed by the business requirements, feasibility analysis, function and program design and design review are carried out, and the R&D tasks of the business requirements that have passed the review are arranged with a version plan to enter the development coding process, such as steps S303-S305. Among them, the design review plan determined by the R&D tasks of the business requirements that have passed the review needs to be confirmed by the business demand party, such as step S306.

[0060] The process of developing the coding for the above version plan involves the writing of data mining logic, such as step S307. Based on the data mining logic, the corresponding data mining query logic can be defined to form a data mining logic module, and the above query plan can be verified accordingly, such as steps S308-S309. Among them, the verification operation of the query plan in step S309 includes but is not limited to the analysis and avoidance of execution plan time conflicts, the analysis and optimization of system performance pressure, the optimization of cross-platform data synchronization and data consistency, and other verification processes.

[0061] When the query plan verification operation is passed, the query logic of the version plan is executed to form a logical instance, and the query plan is configured to the platform database, such as step S308. Further, the logical instance (which can be understood as data mining logic) is executed according to the query plan of the version to form an execution result, such as step S310.

[0062] When the execution result is processed by the data snapshot algorithm, a corresponding data snapshot can be formed, and the data snapshot result corresponding to the R&D data can be cached in high-speed memory, such as step S311. Therefore, in response to the R&D data management request of the business demander, the real-time execution result can be directly sent to the business demander (such as a terminal device) for real-time display and viewing of the data mining results, such as step S312. It is also possible to directly obtain the corresponding data snapshot by accessing the data mining snapshot result in high-speed memory after the execution operation. Therefore, on the basis of real-time data mining, by adding a data snapshot mechanism, the query results and reports of real-time mining can be specified by configuring expressions to specify the snapshot cycle and number of times, and the query results and reports of specific functions can be serialized in a common format in a WYSIWYG manner for rapid access, thereby improving the hit efficiency by caching the serialized results, supporting the retrospective analysis of historical snapshot data, allowing the use of path expressions to compare the snapshot data content field by field and obtain a difference analysis report, and the public architecture maintains high cohesion and low coupling, providing a time-based general processing container.

[0063] Therefore, R&D personnel can complete R&D work by writing corresponding sub-examples to achieve data acquisition, data visualization and complete sub-example registration. The development cost of each daily and weekly report item is maintained at a low level, which greatly reduces the difficulty and workload of R&D personnel. In addition, with the help of the snapshot system itself, historical execution data can be used for performance self-assessment and monitoring alarms. It can adapt to the execution process deviation caused by the accumulation of data volume without generating false alarms. It can log abnormal tasks and allow retries according to the configuration. It can also alarm the bottleneck failures that affect the task chain through the internal email system.

[0064] That is, with the help of the above-mentioned method of the embodiment of the present disclosure, the management efficiency of R&D data can be effectively improved, and at the same time, the accuracy of R&D data can be improved, ensuring the accurate review of milestone data within a specific time point, while also greatly saving labor costs, making the R&D data mining process easier to manage and control, and this method can effectively improve the automation and intelligence level of the entire R&D data mining to further improve management efficiency.

[0065] Figure 4 Another application scenario diagram of the R&D data management method according to an embodiment of the present disclosure is schematically shown.

[0066] like Figure 2-Figure 4 As shown, according to an embodiment of the present disclosure, in step S201, the query plan corresponding to the R&D data is verified, including:

[0067] Determine that the preset database meets the preset execution scope according to the query logic corresponding to the R&D data;

[0068] Verify that query plans do not have execution conflicts; and

[0069] Verify and execute the logic instance corresponding to the query logic.

[0070] According to the functions and program design completed in the aforementioned steps S305-S306, the data mining logic (which can be understood as query logic) and the query plan are split into two parts, so as to implement the data mining logic execution process through code writing, such as step S401.

[0071] First, it is necessary to determine whether the registration information of the preset database meets the preset execution scope of the query logic based on the functions corresponding to the R&D data and the query logic of the program design. Among them, the preset database is the above-mentioned platform database of the embodiment of the present disclosure, which serves as the data storage module of the embodiment of the present disclosure to realize data access. The registration information is the input source information related to the above-mentioned query plan stored in the above-mentioned preset database. In addition, the preset execution scope is the corresponding relationship between the input source information and the above-mentioned query logic. When the execution data in the query logic has corresponding parameters with the input source information, it is confirmed that it meets the preset execution scope, otherwise it does not meet the preset execution scope.

[0072] An execution conflict is a conflict between the plan execution parameters in the query plan and the corresponding fixed parameters of the platform database. For example, if the execution time in the plan execution parameters is A, but the execution time of the corresponding fixed parameters is also A, then there is no execution conflict in the query plan. On the contrary, if the execution time of the fixed parameters is not A, there will be an execution conflict in the query plan.

[0073] If the instance corresponding to the query logic is to be verified and executed, the query plan must not have any execution conflicts, and the preset database determined by the query logic must meet the preset execution range, thereby ensuring the accuracy of the verification operation of the entire query plan and providing a more efficient verification process for the verification operation.

[0074] like Figure 2-Figure 4 As shown, according to an embodiment of the present disclosure, determining that a preset database satisfies a preset execution range according to the query logic corresponding to the R&D data includes:

[0075] Determine input source information related to the query plan registered in a preset database;

[0076] When it is determined that the input source information corresponds to the preset execution range, it is determined that the preset database satisfies the preset execution range.

[0077] The input source information includes specific information such as table information, cross-platform database information, and file information related to the query plan registered with the preset database. According to the information registered in the preset database, the input source information related to the query plan can be queried and obtained. When the execution data in the query logic has corresponding parameters with the input source information, it is confirmed that it meets the preset execution scope, otherwise it does not meet the preset execution scope, that is, the integrated database of the current platform meets or does not meet the preset execution scope, such as steps S402-S403.

[0078] like Figure 2-Figure 4 As shown, according to an embodiment of the present disclosure, determining that a query plan does not have an execution conflict includes:

[0079] Get the query plan entered in the platform management page;

[0080] When it is determined that the query plan does not correspond to the preset conflict event, it is determined that the query plan does not have an execution conflict.

[0081] The platform management page is a visual input module of the system platform where the preset database is located, so that R&D personnel can input query plans related to functions and program design, such as step S404. When the query plan does not correspond to the preset conflict event, it is determined that the query plan does not have an execution conflict. The preset conflict event is an event in which the corresponding plan execution parameters in the above query plan and the corresponding fixed parameters of the platform database have a conflicting relationship, such as an event in which the execution time of the plan and the execution time of the fixed parameters do not correspond, and the query plan has an execution conflict, such as step S405.

[0082] like Figure 2-Figure 4 As shown, according to an embodiment of the present disclosure, in the process of verifying and executing the logic instance corresponding to the query logic, it includes:

[0083] Write query logic as logical instances;

[0084] Verify and execute the logical instance according to the execution plan entered in the platform management page.

[0085] When there is no execution conflict in the query plan and the preset database determined by the query logic meets the preset execution range, the query logic is written to form a logic instance, and then the logic instance is verified and executed according to the execution plan entered in the background management page, such as step S406.

[0086] like Figure 2-Figure 4 As shown, according to an embodiment of the present disclosure, in the process of verifying and executing the logic instance corresponding to the query logic, it also includes:

[0087] Record the verification execution parameters during the verification execution process;

[0088] Determining that the verification operation of the query plan is feasible according to the verification execution parameters;

[0089] Execute version production on the logical instance according to the preset version plan, and configure the query plan for verifying the feasibility of the operation into the preset database.

[0090] In step S406, it is also necessary to further record the verification execution parameters generated during the verification execution operation of the logic instance, and the verification execution parameters include the execution time of the verification execution according to the execution plan and the corresponding system performance information.

[0091] The verification execution parameters are used to determine whether the verification operation of the query plan is feasible. Specifically, the query logic writing, query plan verification, and logic instance verification operations are performed without any system performance issues or abnormal or normal execution times. If an abnormality occurs, it is not feasible. If everything is normal, it is feasible, as shown in step S407.

[0092] When it is determined that the above verification operation is feasible, it means that the verification operation of the above query plan has passed the verification. Even if there is a situation where the logic instance corresponding to the query plan still needs to further optimize the logic, scheduling, etc., the version can be put into production for the logical instance according to the preset version plan, and the query plan with feasible verification operation can be configured into the preset database, such as step S408. The preset version plan is a version production plan method related to the above query plan.

[0093] In this way, the data correctness of the query planning process and the efficiency of the query planning operation can be guaranteed, data processing delays can be avoided, and it is conducive to the efficient operation of R&D data management.

[0094] like Figure 2-Figure 4As shown, according to an embodiment of the present disclosure, in step S202, according to the query plan that has passed the verification operation, the logical instance of the completed version production is executed, including:

[0095] Instantiate the logical instance according to the query plan;

[0096] The execution result formed by executing the instantiation process.

[0097] The corresponding logical instance of the completed version production and query plan configuration is executed. The execution process specifically involves the instantiation of the logical instance, in order to convert the logical instance into the execution result of the complete instance. By performing an execution operation on the execution result generated by the instantiation, the execution of the logical instance is completed accordingly. In this way, the execution process of the logical instance can be realized, and the logical instance can be effectively converted into a complete instance through the instantiation operation, thereby ensuring the accuracy of the data.

[0098] Figure 5 Another application scenario diagram of the R&D data management method according to an embodiment of the present disclosure is schematically shown.

[0099] like Figure 2-Figure 5 As shown, according to an embodiment of the present disclosure, in instantiating a logical instance according to a query plan, the process includes:

[0100] Initialize the task execution information of the query plan;

[0101] According to the task execution information, the logical instance that triggers the preset scheduled task is queued for waiting;

[0102] Instantiate the logic instance in the queue waiting process according to the available current idle resource queue.

[0103] The task execution information of the read registered planned task (which can be understood as a query plan) is initialized, wherein the task execution information includes the execution scenes, specified time, range, etc. involved in the query plan. The multi-task manager can directly call the query plan and query logic after initialization, such as steps S501-S502.

[0104] When it is determined that there is a preset scheduled task that needs to be triggered, a queue operation is performed on the logical instance that has the preset scheduled task according to the task execution information such as the specified time, session, and range, and the instance is added to the task execution queue and waits for processing, such as steps S503-S504. The preset scheduled task is a data mining event of R&D data related to the above query plan and query logic, which can be provided by the business demander.

[0105] When the logic instance enters the task execution queue, the queue status is updated at the same time, and the update information is fed back to the multi-task manager. The multi-task manager evaluates the update information to confirm whether there are corresponding idle resources to perform operations on the newly added logic instance. After the multi-task manager determines the number of idle resources in the current system, it schedules the idle resources and determines that the idle resources are available. The idle resources are configured to instantiate the logic instance, that is, instantiate the planned task logic, as shown in steps S504-S502-S506-S505. Among them, the current idle resources include the number of available connections in the connection pool, the processor load, etc.

[0106] like Figure 2-Figure 5 As shown, according to an embodiment of the present disclosure, the execution result formed by executing the instantiation process includes:

[0107] Track the performance consumption parameters during the execution of the execution results;

[0108] According to the performance consumption parameters, it is determined that the execution process is normal.

[0109] During the instantiation operation of the execution result, it is necessary to track and monitor the performance consumption generated during the execution of the planned task. The performance consumption parameters involved include CPU consumption index, memory occupancy, task execution time and other specific parameters related to the overall performance of the system, such as step S507.

[0110] When the performance consumption parameter does not have an abnormal value, it is determined that the execution process has no abnormality. When it has an abnormal value, it is determined that the execution process has an abnormality, as shown in step S508. When it is abnormal, the execution status update can be triggered to perform on-site cleaning and restoration. If there is no abnormality, it is determined that the execution process of the execution result is correct, so as to ensure the validity of the data when processing the data snapshot in the next step.

[0111] like Figure 2-Figure 5 As shown, according to an embodiment of the present disclosure, in step S203, generating a data snapshot corresponding to the execution result generated by the execution operation includes:

[0112] Perform persistence operations on the execution results according to the preset configuration information;

[0113] Generate a data snapshot for persistence operations. The data snapshot has a multi-dimensional index.

[0114] The preset configuration information is configuration data that is formed based on the data snapshot mechanism or algorithm logic to facilitate persistence processing. According to the preset configuration information, the persistence operation is realized by encoding the execution result into a general description language or a structured storage language, and the corresponding data snapshot is generated through the persistence operation, such as instantiating the execution result through the persistence encoder in steps S509-S510 to form a data snapshot in the form of JSON / XML, etc., and configuring it to the above-mentioned non-relational preset database. Among them, the system will generate a multi-dimensional data snapshot query index based on dimensional information such as keywords, tags, and execution time, so as to facilitate the query and retrieval of historical data in the later stage, so as to support the retrospective analysis of historical snapshot data.

[0115] Figure 6 Another application scenario diagram of the R&D data management method according to an embodiment of the present disclosure is schematically shown.

[0116] like Figure 2-Figure 6 As shown, according to an embodiment of the present disclosure, in implementing the management of R&D data through data snapshots, the following steps are included:

[0117] Determine customized query conditions for R&D data;

[0118] Retrieve data snapshots based on customized query criteria.

[0119] According to the business needs of R&D management, customized query conditions are used to query R&D data in the platform page component. The customized query conditions include retrieval index parameters such as time and date range and tag information of historical data snapshots, which are used to realize retrieval of indexed data snapshot data, such as step S601.

[0120] like Figure 2-Figure 6 As shown, according to an embodiment of the present disclosure, performing retrieval on a data snapshot according to a customized query condition includes:

[0121] Based on custom query conditions, data snapshots are retrieved from the in-memory cache by requesting parsed information.

[0122] According to the customized query condition, the generated data snapshot can be retrieved by using the historical index tag information and the corresponding time range, depending on the parsing result of the business request provided by the business demander, to query the data snapshot data of the registered scheduled task information, as shown in step S602. The request parsing information is the parsing content of the business request provided by the business demander.

[0123] Therefore, the retrieval query of historical snapshot data can be directly realized, which is convenient and efficient, and the data retrieval query is more accurate.

[0124] like Figure 2-Figure 6As shown, according to an embodiment of the present disclosure, performing retrieval on a data snapshot according to a customized query condition also includes:

[0125] During the retrieval process, when the data snapshot hits the memory cache, the R&D data corresponding to the data snapshot is sorted and supplemented to achieve R&D data management;

[0126] When the execution data snapshot does not hit the memory cache, the R&D data corresponding to the data snapshot is obtained from the preset database and the R&D data is cached.

[0127] In the specific data snapshot retrieval query process, when the data snapshot hits the memory cache, that is, whether the memory cache has the data snapshot to be retrieved, the R&D data corresponding to the data snapshot is sorted and supplemented to realize the management of the R&D data, such as steps S603-S606.

[0128] On the contrary, when the above data snapshot is retrieved through customized query conditions, the retrieval of historical data content is realized, and when it is determined that the data snapshot does not hit the memory cache, that is, the memory cache does not have the data snapshot to be retrieved, the persistent data will be retrieved from the preset non-relational platform database, and the data snapshots accessed within the past set time will be read and stored in the memory cache, and the data will be decoded and supplemented according to the high-speed memory cache, such as steps S604-S606. Therefore, the system access efficiency is further optimized.

[0129] It should be noted that after the data is decoded and supplemented, the mined R&D data can be visualized in the foreground, such as step S507.

[0130] Among them, if there are specific changes in the R&D data management work and the query plan needs to be adjusted, the query plan needs to be modified and re-specified, and the configured query plan will take effect immediately and be executed according to the new query plan from the next cycle. The execution result is regenerated into a data snapshot, such as step S315, which will not be repeated here.

[0131] Based on the above detailed description of the management method of R&D data in the embodiment of the present disclosure, another specific embodiment is further supplemented to further explain as follows:

[0132] According to the original requirements provided by the business demand side, it is necessary to monitor the overdue status of test issues on a daily basis. The query logic for this business requirement is: query the unclosed-loop test issues of the day according to the current system date and aggregate and count the data by the development department to which they belong, mark the overdue issues and sort them according to the number of overdue issues. Email notifications are sent to departments with overdue issues and copies are sent to the department leaders. The query plan is to be conducted twice a day at 0:00 and 12:00, but email notifications are only sent at 0:00 for the overdue status of the previous day.

[0133] Obtain specific requirements through demand review. First, compile specific SQL or file analysis logic modules as Java programs based on query logic and inherit the execution logic parent class (the parent class contains logic such as exception handling and process control and realizes communication with the multi-task management module). After that, upload the corresponding Java code file to the platform on the background management page, and the platform will compile Java into Class for loading through real-time compilation. By receiving the execution plan task expressions entered at 0:00 and 12:00 every day on the background management page, the system will continuously execute the 0:00 and 12:00 sessions in order of the number of executions, ignoring the execution interval, and record the performance overhead during the execution, giving complete execution record data.

[0134] By analyzing the execution record data, we can get the feasibility results of the requirements. For the requirements that do not meet the execution conditions, we will return them to the business demand party for re-involvement. For those that can be adjusted by adjusting the execution times and scope, we will give specific adjustment suggestions. For the requirements that have passed the verification, we can formally submit the written Java code to the version library and bring it out to production with the next patch, and configure the execution plan to the production database.

[0135] After production, the platform will initialize the multi-task manager by reading the execution plan configured in the database during initialization. The multi-task manager will instantiate the execution logic and put it into the execution queue multiple times at 0:00 and 12:00 every day. The multi-task manager will monitor the available resources (such as the remaining database connection pool, processor load, etc.) and take out and execute the planned tasks from the queue when available, and send notification emails according to the execution session conditions (only the 0:00 session). Moreover, if there are exceptions in the execution of the planned tasks, the exception information will be recorded and the multi-task manager will be notified. If the execution is successful, a specific encoder will be instantiated to encode the execution results. The encoding results are usually JSON or XML and stored in a non-relational database for persistence.

[0136] When business personnel query through the page according to specific management needs, the platform queries the memory cache according to the scheduled task ID and query conditions (time and date range, development department ID, historical data tags, etc.) requested by the user. If the memory cache does not hit, the snapshot is obtained by querying the non-relational database and decoded, and then placed in the memory cache. The decoded data is visualized in the foreground through JS. The display content includes the departments that currently have overdue problems, the number and proportion of overdue problems, and is sorted according to the number of overdue problems.

[0137] Therefore, according to the above-mentioned management method of R&D data of the embodiment of the present disclosure and its specific embodiment, it can be seen that the above-mentioned method of the embodiment of the present disclosure can realize a R&D data mining system based on data snapshots. In order to meet the daily and weekly work requirements of R&D management, a data snapshot mechanism is added on the basis of real-time data mining. The query results and reports of real-time mining can be used to formulate snapshot cycles and times by configuring expressions. The query results and reports of specific functions are serialized in a common format in a WYSIWYG manner for fast access. The hit efficiency is improved by caching and indexing the serialized results. Retrospective analysis of historical snapshot data is supported. Path expressions are allowed to be used to compare the snapshot content field by field and obtain a difference analysis report. The public architecture maintains high cohesion and low coupling, and provides an event-based general processing container. R&D personnel can complete development by writing corresponding sub-examples to achieve data acquisition, data visualization and complete sub-example registration. The development cost of each daily and weekly report item is maintained at a low level, which greatly reduces the difficulty and workload of R&D personnel to get started. The snapshot system itself uses historical execution data for performance self-assessment and monitoring alarms. It can adapt to execution process deviations caused by data accumulation without generating false alarms. It logs tasks with abnormal execution and allows retries based on configuration. It also issues alarms through the internal email system for bottleneck failures that affect the task chain.

[0138] Figure 7 The exemplary architecture of the R&D data management device according to an embodiment of the present disclosure is schematically shown.

[0139] like Figure 7 As shown, another aspect of the present disclosure provides a research and development data management device 700, which includes a plan verification module 710, an instance execution module 720 and a snapshot generation module 730. The plan verification module 710 is used to perform a verification operation on a query plan corresponding to the research and development data; the instance execution module 720 is used to perform an execution operation on a logical instance of a completed version production according to the query plan that has passed the verification operation; and the snapshot generation module 730 is used to generate a data snapshot corresponding to the execution result generated by the execution operation, so as to realize the management of the research and development data through the data snapshot.

[0140] It should be noted that the implementation method of the R&D data management device part is similar to the implementation method of the R&D data management method part, and the technical effects achieved are also similar, which will not be repeated here.

[0141] Figure 8 A block diagram of an electronic device according to an embodiment of the present disclosure is schematically shown.

[0142] Another aspect of the present disclosure provides an electronic device, comprising one or more processors and a memory; the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the R&D data management method of an embodiment of the present disclosure.

[0143] Figure 8 A block diagram of an electronic device according to an embodiment of the present disclosure is schematically shown. Figure 8 The electronic 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 disclosure.

[0144] like Figure 8 As shown, the computer system 800 according to the embodiment of the present disclosure includes a processor 801, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 802 or the program loaded from the storage part 808 to the random access memory (RAM) 803. The processor 801 may include, for example, a general-purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (for example, an application-specific integrated circuit (ASIC)), etc. The processor 801 may also include an onboard memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flow according to the embodiment of the present disclosure.

[0145] In RAM 803, various programs and data required for the operation of system 800 are stored. Processor 801, ROM 802 and RAM 803 are connected to each other through bus 804. Processor 801 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 802 and / or RAM 803. It should be noted that the program can also be stored in one or more memories other than ROM 802 and RAM 803. Processor 801 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0146] According to an embodiment of the present disclosure, the system 800 may further include an input / output (I / O) interface 805, which is also connected to the bus 804. The system 800 may further include one or more of the following components connected to the I / O interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, a modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 808 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed, so that a computer program read therefrom is installed into the storage section 808 as needed.

[0147] According to an embodiment of the present disclosure, the method flow according to an embodiment of the present disclosure can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program contains a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 809, and / or installed from the removable medium 811. When the computer program is executed by the processor 801, the above-mentioned functions defined in the system of the embodiment of the present disclosure are executed. According to an embodiment of the present disclosure, the system, equipment, device, module, unit, etc. described above can be implemented by a computer program module.

[0148] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the R&D data management method according to the embodiment of the present disclosure is implemented.

[0149] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: 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), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 802 and / or RAM 803 described above and / or one or more memories other than ROM 802 and RAM 803.

[0150] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, 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 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 or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0151] Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the R&D data management method of the embodiment of the present disclosure when executed.

[0152] Specifically, the computer-readable storage medium may be included in the device / apparatus / system described in the above embodiment; or it may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the R&D data management method according to the embodiment of the present disclosure is implemented.

[0153] Alternatively, the computer-readable storage medium may be included in the device / apparatus / system described in the above embodiment; or it may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the R&D data management method according to the embodiment of the present disclosure is implemented.

[0154] Another aspect of the present disclosure provides a computer program, which includes computer executable instructions. When the instructions are executed, they are used to implement the research and development data management method of the embodiment of the present disclosure.

[0155] So far, the embodiments of the present disclosure have been described in detail with reference to the accompanying drawings.

[0156] The flow charts 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 disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a 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 or flow chart, and the combination of the boxes in the block diagram or flow chart 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.

[0157] It will be appreciated by those skilled in the art that, although the present disclosure has been shown and described with reference to specific exemplary embodiments of the present disclosure, it will be appreciated by those skilled in the art that, without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents, various changes in form and detail may be made to the present disclosure. Therefore, the scope of the present disclosure should not be limited to the above-described embodiments, but should be determined not only by the appended claims, but also by the equivalents of the appended claims.

[0158] The specific embodiments described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for managing R&D data, wherein: include: Performing a verification operation on the query plan corresponding to the R&D data; According to the query plan that has passed the verification operation, an execution operation is performed on the logical instance of the completed version production; as well as Generate a data snapshot corresponding to the execution result generated by the execution operation, so as to manage the research and development data through the data snapshot; The operation of verifying the query plan corresponding to the R&D data includes: determining that a preset database satisfies a preset execution range according to the query logic corresponding to the R&D data; determining that there is no execution conflict in the query plan; and verifying and executing the logic instance corresponding to the query logic; The verification and execution of the logic instance corresponding to the query logic includes: writing the query logic as the logic instance; and verifying and executing the logic instance according to the execution plan input in the platform management page.

2. The method according to claim 1, wherein: In the step of determining that a preset database satisfies a preset execution range according to the query logic corresponding to the research and development data, the step includes: Determining input source information related to the query plan registered in the preset database; When it is determined that the input source information corresponds to the preset execution range, it is determined that the preset database satisfies the preset execution range.

3. The method according to claim 1, wherein: The step of determining that the query plan does not have an execution conflict includes: Get the query plan entered in the platform management page; When it is determined that the query plan does not correspond to a preset conflict event, it is determined that the query plan does not have an execution conflict.

4. The method according to claim 1, wherein: In the verifying and executing the logic instance corresponding to the query logic, it also includes: Recording verification execution parameters during the verification execution process; Determining, according to the verification execution parameters, that the verification operation of the query plan is feasible; The version is put into production on the logic instance according to a preset version plan, and a query plan for verifying the feasibility of the operation is configured into the preset database.

5. The method according to claim 1, wherein: In executing the operation on the logical instance of the completed version production according to the query plan that has passed the verification operation, the following steps are included: Instantiating the logical instance according to the query plan; The execution result formed by executing the instantiation process.

6. The method according to claim 5, wherein: Instantiating the logic instance according to the query plan includes: Initialize task execution information of the query plan; According to the task execution information, the logic instance that triggers the preset planned task is queued for waiting; The logic instance in the queue waiting process is instantiated according to available currently idle resources.

7. The method according to claim 5, wherein: The execution result formed by executing the instantiation process includes: Tracking performance consumption parameters during the execution of the execution result; According to the performance consumption parameter, it is determined that the execution process is normal.

8. The method according to claim 1, wherein: The generating of a data snapshot corresponding to the execution result generated by the execution operation includes: Performing a persistence operation on the execution result according to preset configuration information; A data snapshot of the persistence operation is generated, wherein the data snapshot has a multi-dimensional index.

9. The method according to claim 1, wherein: In the managing the R&D data by using the data snapshot, it includes: Determining customized query conditions for the R&D data; The data snapshot is retrieved according to the customized query condition.

10. The method according to claim 9, wherein: In performing retrieval on the data snapshot according to the customized query condition, the method includes: According to the customized query condition, the data snapshot is retrieved in the memory cache by requesting parsed information.

11. The method according to claim 10, wherein: In the performing retrieval on the data snapshot according to the customized query condition, it also includes: In the process of executing the search, when the data snapshot hits the memory cache, the research and development data corresponding to the data snapshot is sorted and supplemented to achieve the management of the research and development data; When the execution data snapshot does not hit the memory cache, the research and development data corresponding to the data snapshot is obtained from a preset database, and the research and development data is cached.

12. A research and development data management device, wherein: include: A plan verification module, used to verify the query plan corresponding to the R&D data; An instance execution module, configured to execute an operation on a logical instance of a completed version according to a query plan that has passed the verification operation; and A snapshot generation module, used to generate a data snapshot corresponding to the execution result generated by the execution operation, so as to manage the research and development data through the data snapshot; The plan verification module is further used to determine that the preset database meets the preset execution range according to the query logic corresponding to the R&D data; determine that there is no execution conflict in the query plan; and verify and execute the logic instance corresponding to the query logic; The plan verification module is also used to write the query logic into the logic instance; and verify and execute the logic instance according to the execution plan input in the platform management page.

13. An electronic device comprising: one or more processors; a memory for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 11.

14. A computer-readable storage medium storing computer-executable instructions, wherein the instructions are used to implement the method according to any one of claims 1 to 11 when executed.

15. A computer program, comprising computer executable instructions, which are used to implement the method according to any one of claims 1 to 11 when executed.

Images