Developing resource migration analysis method, device, storage medium and product

Abstract

This application provides a development resource migration analysis method, device, storage medium, and product. It is applied in the field of software development technology. The specific implementation scheme is as follows: Obtain the migration analysis results corresponding to the target migration package; determine the basic information of the target migration package and the business group information of each development resource under each migration attribute in the target migration package from the migration analysis results; obtain the business group information of the target migration package from the basic information of the target migration package; compare the business group information of the target migration package with the business group information of each development resource; if it is determined that the business group information of a certain development resource is inconsistent with the business group information of the target migration package, then highlight the relevant information of that development resource; send the highlighted development resource information to the development user terminal so that the development user terminal can highlight the relevant development resource information.

Description

Technical Field

[0001] The embodiments of the present invention relate to the field of software development, and in particular to a method, device, storage medium and product for development resource migration analysis. Background Technology

[0002] With the advent of the digital age, the trend towards online, data-driven, intelligent, and open financial services has become increasingly important. Banks are actively researching how to transform to a distributed architecture; however, most banks still retain their core applications on mainframe systems. Therefore, the stability and security of core applications running on mainframe systems remain paramount, and the correctness of the development resource versions for core applications is of utmost importance.

[0003] When developers are developing development resources, they typically use multiple databases in the Mainframe Resource Repository (MRE) to store the programs corresponding to each version of the development resources. Version integration is achieved through migration operations between versions until a production version is created. Before each migration operation, the development resources need to be packaged into a migration package, which is then analyzed to obtain migration analysis results. Redundant development resources are removed from the migration analysis results before the migration operation is performed.

[0004] Currently, when removing redundant development resources from migration analysis results, developers manually filter and remove them through the MRE operation terminal. This is time-consuming and labor-intensive, and developers often fail to completely remove development resources that do not need to be migrated, which can easily lead to omissions and errors. Summary of the Invention

[0005] This invention provides a development resource migration analysis method, device, storage medium, and product to solve the technical problem in the prior art that removing redundant development resources from migration analysis results is time-consuming, labor-intensive, and prone to omissions and errors.

[0006] In a first aspect, embodiments of the present invention provide a development resource migration analysis method, comprising:

[0007] Obtain the migration analysis results corresponding to the target migration package; the target migration package is a migration package from the first development resource version to the second development resource version; the migration package includes multiple development resources;

[0008] The basic information of the target migration package and the business group information of the development resources under each migration attribute in the target migration package are determined from the migration analysis results.

[0009] Obtain the business group information to which the target migration package belongs from the basic information of the target migration package;

[0010] Compare the business group information to which the target migration package belongs with the business group information to which each development resource belongs;

[0011] If it is determined that the business group information of a certain development resource is inconsistent with the business group information of the target migration package, then the relevant information of the development resource will be highlighted.

[0012] The highlighted development resource information is sent to the development user terminal so that the development user terminal can highlight the development resource information, and the development user can filter out the development resources to be migrated in the PCOM operation terminal based on the highlighted development resource information.

[0013] Secondly, embodiments of the present invention provide a development resource migration analysis device, comprising:

[0014] The first acquisition module is used to acquire the migration analysis results corresponding to the target migration package; the target migration package is a migration package from a first development resource version to a second development resource version; the migration package includes multiple development resources;

[0015] The determination module is used to determine the basic information of the target migration package and the business group information of the development resources under each migration attribute in the target migration package from the migration analysis results;

[0016] The second acquisition module is used to acquire the business group information to which the target migration package belongs from the basic information of the target migration package;

[0017] The comparison module is used to compare the business group information of the target migration package with the business group information of each development resource.

[0018] The highlighting module is used to highlight the relevant information of a development resource if it is determined that the business group information of a certain development resource is inconsistent with the business group information of the target migration package.

[0019] The sending module is used to send the highlighted development resource information to the development user terminal, so that the development user terminal can highlight the development resource information and the development user can filter out the development resources to be migrated in the PCOM operation terminal based on the highlighted development resource information.

[0020] Thirdly, embodiments of the present invention provide an electronic device, including: at least one processor, a memory, and a transceiver;

[0021] The processor, the memory, and the transceiver circuit are interconnected;

[0022] The memory stores computer-executed instructions; the transceiver is used for sending and receiving data.

[0023] The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the method as described in the first aspect.

[0024] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method described in the first aspect.

[0025] Fifthly, embodiments of the present invention provide a computer program product, including a computer program that, when executed by a processor, implements the method described in the first aspect.

[0026] The development resource migration analysis method, device, storage medium, and product provided in this invention involve obtaining the migration analysis results corresponding to a target migration package; the target migration package is a migration package from a first development resource version to a second development resource version; the migration package includes multiple development resources; determining the basic information of the target migration package and the business group information of each development resource under each migration attribute in the target migration package from the migration analysis results; obtaining the business group information of the target migration package from the basic information of the target migration package; comparing the business group information of the target migration package with the business group information of each development resource; if it is determined that the business group information of a certain development resource is inconsistent with the business group information of the target migration package, then highlighting the relevant information of that development resource; sending the highlighted relevant information of the development resource to the development user terminal so that the development user terminal highlights the relevant information of the development resource, and the development user selects the development resources to be migrated in the PCOM operation terminal based on the highlighted relevant information of the development resource. After determining the business group information of the target migration package and the business group information of each development resource through the migration analysis results, development resources that do not belong to the same business group as the target migration package are summarized, highlighted, and sent to the development user terminal. The development user can then selectively view the corresponding development resources based on the highlighted information and determine whether they need to be removed. This effectively assists the development user in removing development resources that do not belong to the same business group as the target migration package, eliminating the need to sift through a large number of development resources in the PCOM operation terminal. Therefore, it improves the efficiency of removing development resources that do not need to be migrated and effectively avoids omissions and errors. Attached Figure Description

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

[0028] Figure 1 This is a diagram illustrating the MRE version management process;

[0029] Figure 2 This is a network architecture diagram that can implement the development resource migration analysis method of the embodiments of the present invention;

[0030] Figure 3 This is a flowchart illustrating a development resource migration analysis method provided in an embodiment of the present invention;

[0031] Figure 4 This is a flowchart illustrating a development resource migration analysis method provided in another embodiment of the present invention;

[0032] Figure 5 This is a flowchart illustrating a development resource migration analysis method provided in another embodiment of the present invention;

[0033] Figure 6 This is a schematic diagram of the structure of a development resource migration analysis device provided in an embodiment of the present invention;

[0034] Figure 7 This is a schematic diagram of the structure of an electronic device used to implement the development resource migration analysis method of the present invention.

[0035] Figure 8 This is a block diagram of an electronic device used to implement the development resource migration analysis method of this invention.

[0036] The accompanying drawings have illustrated specific embodiments of this disclosure, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this disclosure to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0037] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0038] First, the terms used in the embodiments of this invention will be explained:

[0039] Mainframe system: This is a type of high-end server system, which is an integrated solution of large hardware platform and operating system. It has powerful transaction processing capabilities and extremely high availability. The online transaction processing capacity is generally in the range of millions to tens of millions, and the availability is as high as 99.999%. It is an irreplaceable operating platform for large-scale mission-critical applications in the financial field, e-commerce and other fields.

[0040] Version management: The process of tracking software components or configuration information and the different versions of systems that use these components. Version management also includes ensuring that changes made by different developers do not affect each other.

[0041] MRE: A resource repository for a bank's mainframe program. It is a crucial foundational software infrastructure for the core system, from design and development to deployment. The MRE stores the program and version information corresponding to the development resources in the form of database tables.

[0042] RULE: The development language for bank mainframe programs. Through configuration, the Rule language can be compiled into executable files in other languages. For example, the backend Rule can be compiled into the mainframe COBOL language and deployed on the mainframe, while the frontend Rule can be compiled into the C# language and deployed on the teller's end.

[0043] PCOM: The operating terminal for the MRE repository, which allows developers to perform operations such as program migration and compilation.

[0044] Migration analysis: A crucial step in the MRE migration process, including creating migration packages, analysis, and removing non-production-ready programs. Through migration analysis, the MRE informs developers of the differences between the upstream and downstream repositories in the content being migrated, specifically identifying which changes remain unchanged and which are added, updated, or deleted as the downstream repository is migrated to the upstream repository.

[0045] In order to clearly understand the technical solution of this application, the solutions of the prior art will be described in detail.

[0046] When developers develop development resources, they typically use multiple databases within the Main Program Resource Repository (MRE) to store the programs corresponding to different versions of the development resources. Therefore, MRE version management is based on these databases. MRE version management distinguishes versions using the Version field in the database tables, and version integration is achieved through migration operations until a production version is formed. The MRE database consists of a Development Version Repository (V repository) and a Production Version Repository (P repository). The V repository comprises two versions: V1 and V2. Similarly, the P repository comprises two versions: P2 and P3. After developers complete coding on V1, creating the program for version V1 development resources, they migrate from V1 to V2, then from V2 to P2, and finally from P2 to P3, forming the final production version. Before migrating development resources to P3, each migration requires creating a migration package, performing migration analysis on the package to remove redundant development resources, and finally completing the migration operation. Figure 1 As shown, taking the MRE of a bank's mainframe system as an example, it includes loan operations, deposit operations, and accounting operations. For each business type, each migration requires first creating a migration package, then performing migration analysis on the migration package and removing redundant development resources, and finally completing the migration operation.

[0047] During the migration analysis, a list of development resources to be migrated will be obtained. Currently, when removing redundant development resources from the list, the list of development resources to be migrated will be displayed in the PCOM operation terminal. Developers will then manually select which development resources need to be migrated and which do not, and remove the programs that do not need to be migrated.

[0048] However, since the number of development resources displayed per page in the PCOM interface is limited, when the migration package involves changes to many development resources or changes to a specific underlying development resource, the MRE impact analysis mechanism will identify tens of thousands of development resources to be migrated. This requires developers to flip through dozens, hundreds, or even thousands of pages to confirm whether all development resources need to be removed. Therefore, this manual screening method is time-consuming and labor-intensive, and developers often fail to completely remove development resources that do not need to be migrated, leading to omissions and errors.

[0049] Therefore, when faced with the technical problems of existing technologies, the inventors, through creative research, discovered that when developers manually remove development resources, they mainly remove those whose business group is inconsistent with the business group of the target migration package. To effectively assist developers in removing development resources that are inconsistent with the target migration package's business group, these resources can be summarized and highlighted. The information related to these highlighted resources can then be sent to the developer's terminal, allowing the developer to filter out the development resources to be migrated in the PCOM operating terminal based on this information.

[0050] When identifying development resources that do not belong to the same business group as the target migration package, the basic information of the target migration package and the business group information of the development resources under each migration attribute in the target migration package can be determined from the migration analysis results corresponding to the target migration package. The business group information of the target migration package in the basic information of the target migration package can be obtained, and the business group information of the target migration package can be compared with the business group information of each development resource to identify the development resources that do not belong to the same business group as the target migration package.

[0051] Therefore, based on the above-mentioned inventive discovery, the inventors proposed the technical solution of the embodiments of the present invention. The network architecture of the development resource migration analysis method provided by the embodiments of the present invention will be described below.

[0052] Figure 2 This is a network architecture diagram that can implement the development resource migration analysis method of the embodiments of the present invention, such as... Figure 2 As shown, the network structure includes: a host program resource library (MRE) 1, an electronic device 2, a development user terminal 3, a PCOM operation terminal 4, and a migration request device 5. The electronic device 2 is communicatively connected to the host program resource library (MRE) 1, the development user terminal 3, and the migration request device 5. The PCOM operation terminal 4 is communicatively connected to the host program resource library (MRE) 1.

[0053] Specifically, in one application scenario, a developer wants to migrate a target migration package from a downstream development resource version to an upstream development resource version. The downstream development resource version's migration package is stored in the host application resource library MRE 1. The host application resource library MRE 1 performs migration analysis on the target migration package to obtain the migration analysis results. The electronic device retrieves the migration analysis results corresponding to the target migration package from the host application resource library MRE 1. Using the development resource migration analysis method provided in this embodiment, development resource-related information that is inconsistent with the business group information of the target migration package is identified and highlighted. This highlighted development resource-related information is then sent to the developer's terminal. The developer filters the development resources to be migrated in the PCOM operation terminal based on the highlighted development resource-related information. The developer submits a migration application request through the migration application device. The electronic device detects whether the developer has submitted a candidate exclusion development resource table corresponding to the highlighted development resource-related information through the migration application device. If it is determined that a candidate exclusion development resource table has been submitted, the migration application device is controlled to allow the application request to be sent to the review user client. The reviewing user uses the PCOM operation terminal to migrate the upstream development resource version migration package corresponding to the selected development resources to be migrated to the upstream development resource version database of host program resource library MRE 1.

[0054] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0055] Example 1

[0056] Figure 3 This is a flowchart illustrating a development resource migration analysis method provided in an embodiment of the present invention, as shown below. Figure 3 As shown, the execution subject of the development resource migration analysis method provided in this embodiment is a development resource migration analysis device. This development resource migration analysis device is located in an electronic device. Therefore, the development resource migration analysis method provided in this embodiment includes the following steps:

[0057] Step 201: Obtain the migration analysis results corresponding to the target migration package.

[0058] The target migration package is the migration package for migrating from a downstream development resource version to an upstream development resource version. For example, if the downstream development resource version is V1, then the upstream development resource version is V2. Furthermore, if the downstream development resource version is V2, then the upstream development resource version is P2. And if the downstream development resource version is P2, then the upstream development resource version is P3.

[0059] The migration package includes multiple development resources. These include the main development resource and other development resources associated with it. These development resources exist in the form of programs.

[0060] In this embodiment, the electronic device communicates with the MRE resource library of the host program and sends a migration result retrieval request to the MRE resource library of the host program. The migration result retrieval request may include the identification information of the target migration package, so that the MRE resource library of the host program can obtain the migration analysis result corresponding to the target migration package according to the identification information of the target migration package, and send the migration analysis result corresponding to the target migration package to the electronic device.

[0061] Step 202: Determine the basic information of the target migration package and the business group information of the development resources under each migration attribute in the target migration package from the migration analysis results.

[0062] In this embodiment, the migration analysis results include the differences between upstream and downstream version development resources. This includes differences in the main development resources, as well as differences in other development resources that are related to the main development resources.

[0063] Differences in the main development resource and other development resources that are related to the main development resource may include: differences in addition, updates, or deletions.

[0064] Specifically, in this embodiment, since the migration analysis results to be analyzed are stored in the MRE resource library of the host program in the form of a table structure in the database, the relevant table structure of the migration analysis results can be parsed to determine each field stored in the relevant table structure of the migration analysis results, and the basic information of the target migration package and the business group information of the development resources under each migration attribute in the target migration package can be determined based on each field.

[0065] The basic information of the target migration package may include: the target migration package name, the target migration package identification information, the business group to which the target migration package belongs, and the migration record table, etc.

[0066] The migration attributes corresponding to the target migration package may include any one or more of the following attributes: Create, Update, and Delete.

[0067] In this embodiment, the business group information to which the development resources belong will vary depending on the application scenario of the host program's MRE resource library. For example, if the host program's MRE resource library is applied to a bank's host system, the business group information to which the development resources belong may include any one or more of the following business groups: loan business, deposit business, accounting business, etc.

[0068] Step 203: Obtain the business group information to which the target migration package belongs from the basic information of the target migration package.

[0069] In this embodiment, the basic information of the target migration package is parsed to extract the business group information to which the target migration package belongs. For example, in a bank's mainframe system, the business group information to which the target migration package belongs can be any of the following business group information: loan business, deposit business, or accounting business.

[0070] Step 204: Compare the business group information of the target migration package with the business group information of each development resource.

[0071] In this embodiment, the business group information of each development resource is compared one by one with the business group information of the target migration package. It is determined whether the business group information of each development resource matches the business group information of the target migration package. If the business group information of a development resource matches the business group information of the target migration package, it means that the development resource needs to be migrated to the upstream development resource version. If the business group information of a development resource does not match the business group information of the target migration package, it means that there is a high probability that the development resource does not need to be migrated to the upstream development resource version. Further judgment by the development user is required to determine whether migration to the upstream development resource version is necessary.

[0072] Step 205: If it is determined that the business group information of a certain development resource is inconsistent with the business group information of the target migration package, then the relevant information of the development resource is highlighted.

[0073] In this embodiment, if it is determined that the business group information of at least one development resource is inconsistent with the business group information of the target migration package, it indicates that at least one development resource is highly likely not to need to be migrated to the upstream development resource version. To enable developers to efficiently obtain relevant information about these development resources, the relevant information of at least one development resource is highlighted.

[0074] Understandably, if it is determined that the business group information of at least one development resource is consistent with the business group information of the target migration package, then the relevant information of at least one development resource will be displayed normally.

[0075] The method of highlighting is not limited. For example, the font color of development resource information may be more prominent than that of the display page, or the background of development resource information may be filled with a highlight color.

[0076] Step 206: Send the highlighted development resource information to the development user terminal so that the development user terminal can highlight the development resource information and the development user can filter out the development resources to be migrated in the PCOM operation terminal based on the highlighted development resource information.

[0077] In this embodiment, highlighted development resource information can be sent to the developer user terminal via instant messaging, SMS, or other means. After the developer user opens the terminal, this development resource information is highlighted. Using this highlighted information as a reference, the developer user uses the PCOM operation terminal to remove development resources that do not need to be migrated to the upstream development resource version, while retaining the development resources to be migrated.

[0078] Specifically, developers can enter the highlighted development resource name into the search command in the PCOM terminal to find detailed information about the resource and determine whether it needs to be removed. If removal is necessary, the Toggle command is used to perform the removal operation.

[0079] The development resource migration analysis method provided in this embodiment obtains the migration analysis results corresponding to the target migration package. The target migration package is a migration package that migrates from a downstream development resource version to an upstream development resource version. The migration package includes multiple development resources. The basic information of the target migration package and the business group information of each development resource under each migration attribute in the target migration package are determined from the migration analysis results. The business group information of the target migration package is obtained from the basic information of the target migration package. The business group information of the target migration package is compared with the business group information of each development resource. If it is determined that the business group information of a certain development resource is inconsistent with the business group information of the target migration package, the relevant information of that development resource is highlighted. The highlighted development resource information is sent to the development user terminal so that the development user terminal can highlight the relevant development resource information, and the development user can filter the development resources to be migrated in the PCOM operation terminal based on the highlighted development resource information. Since the business group information of the target migration package and the business group information of each development resource are determined through the migration analysis results, the development resources that are inconsistent with the business group of the target migration package are summarized, highlighted, and sent to the development user terminal. Developers can use the highlighted development resource information to view the corresponding development resources in a targeted manner and determine whether they need to be removed. This effectively assists developers in removing development resources that are inconsistent with the business group to which the target migration package belongs, eliminating the need to browse through a large number of development resources in the PCOM operation terminal. Therefore, it improves the efficiency of removing development resources that do not need to be migrated and effectively avoids omissions and errors.

[0080] Figure 4 This is a flowchart illustrating a development resource migration analysis method provided in another embodiment of the present invention. Figure 4 As shown, the development resource migration analysis method provided in this embodiment is a further refinement of step 202 based on the development resource migration analysis method provided in the embodiment, and also includes other steps. Therefore, the development resource migration analysis method provided in this embodiment includes the following steps:

[0081] Step 301: Obtain the migration analysis results corresponding to the target migration package; the target migration package is a migration package for migrating from the downstream development resource version to the upstream development resource version; the migration package includes multiple development resources.

[0082] Optionally, in this embodiment, the downstream development resource version is the pre-production version (i.e., P2 version), and the upstream development resource version is the production version (i.e., P3 version).

[0083] Step 302: Parse the relevant table structure of the migration analysis results to obtain the basic information fields of the target migration package, the name field of each development resource, the migration attribute field, and the business group field.

[0084] It should be noted that steps 302-303 are an optional implementation of step 202 in Embodiment 1.

[0085] Specifically, in this embodiment, the migration analysis results are stored in the MRE resource library of the host program, and are stored in a table structure similar to that in a database. Therefore, the relevant table structure is parsed to obtain the fields in the relevant table structure, and from each field, the basic information related to the target migration package, the name field of each development resource, the migration attribute field, and the business group field are obtained.

[0086] The fields related to the basic information of the target migration package may include: the field corresponding to the target migration package name, the field corresponding to the target migration package identifier, the field corresponding to the business group to which the target migration package belongs, and the corresponding fields in the migration record table.

[0087] It should be noted that the basic information fields of the target migration package can be stored in the development resource overview table corresponding to the target migration package. The name field of the development resource can be stored in the development resource list corresponding to the target migration package. The migration attribute field and business group field can be stored in the development resource details file.

[0088] Understandably, other fields for obtaining the target migration package's development resources can be extracted from the relevant table structure of the migration analysis results. These fields may include the development resource type field and entity field. These other fields can then be stored in the development resource details file.

[0089] Step 303: Determine the basic information of the target migration package from the fields related to the basic information of the target migration package, and determine the business group information of the development resource under each migration attribute based on the name field, migration attribute field and business group field of each development resource.

[0090] Specifically, as shown in Table 1, this table illustrates the basic information of the target migration package. In Table 1, "Migration Package Name" is the name of the target migration package. "Migration Package ID" is the identifier for the target migration package. "Migration Package Group" is the business group to which the target migration package belongs.

[0091] The migration package record table, which contains basic information about the target migration package, may include the time of the migration analysis, the number of unchanged development resources in the migration analysis results, and the number of changed development resources. Specifically, the number of changed development resources includes newly added development resources, updated development resources, and deleted development resources. For example, in the basic information of the target migration package in Table 1, the number of unchanged development resources is 16,180, of which 4,172 are related to the main development resource, and the number of other development resources associated with the main development resource is 12,008. Changed development resources include updated development resources and newly added development resources. Specifically, the number of updated development resources is 323, of which 318 are related to the main development resource, and the number of other development resources associated with the main development resource is 5. The number of newly added development resources is 83, of which 9 are related to the main development resource, and the number of other development resources associated with the main development resource is 74.

[0092] Table 1: A schematic table of basic information for the target migration package

[0093]

[0094] As an optional implementation, in this embodiment, step 303, determining the business group information of each development resource under each migration attribute based on the name field, migration attribute field, and business group field of each development resource, includes the following steps:

[0095] Step 3031: Classify each development resource according to its migration attribute based on the name field and migration attribute field of each development resource.

[0096] In this embodiment, the name field of each development resource can be obtained from the development resource list corresponding to the target migration package. The migration attribute field of each development resource can be obtained from the development resource details file. The development resources are then categorized according to their migration attributes. If the migration attribute fields corresponding to development resources in the target migration package include add, update, and delete fields, then the categorization of development resources according to migration attributes includes development resources with add attributes, development resources with update attributes, and development resources with delete attributes.

[0097] Step 3032: Determine the development resource name field and the corresponding business group field under each migration attribute, so as to determine the business group information to which the development resource belongs under each migration attribute.

[0098] In this embodiment, the field of the business group information of each development resource is obtained from the development resource details file. Then, the field of the business group information of each development resource is associated with the corresponding development resource name field to determine the development resource name field and the corresponding business group field under each migration attribute. The field of the business group information associated with the development resource name field under each migration attribute is determined as the business group information of the development resource under each migration attribute.

[0099] Step 304: Store the development resource name field and the corresponding business group field under each migration attribute into the corresponding candidate removal development resource table.

[0100] In this embodiment, the development resource name field and its associated business group field under the newly added attribute are stored in the newly added candidate development resource removal table. The development resource name field and its associated business group field under the updated attribute are stored in the updated candidate development resource removal table. The development resource name field and its associated business group field under the deleted attribute are stored in the deleted candidate development resource removal table. Furthermore, to centrally highlight the name field and associated business group field of development resources that are inconsistent with the business group information of the target migration package, the development resource name field and associated business group field in each candidate development resource removal table can be sorted according to the business group field.

[0101] Each development resource name field and its corresponding business group field are located in the same row of the corresponding candidate development resource removal table.

[0102] Understandably, in order to facilitate developers in initially screening development resources that do not need to be migrated based on the development resource information in the candidate removal development resource table, each candidate removal development resource table may also include the type field and entity field corresponding to the development resource.

[0103] Table 2: Schematic Table of Candidate Removal Development Resources

[0104] LONGNAME TYPE ENTITY PROJECT AMT_FEE Field Entity DM00 COD_AR_RLN Field Entity DM00 COD_FEE_BUS_CLS Field Entity DM00 COD_FEE_TR_TYP Field Entity DM00 COD_FEE_TYP Field Entity DM00 IND_ACTG_DREC_1 Field Entity DM00 IND_INBNK Field Entity DM00 IND_TR_PROC_STS Field Entity DM00 NUM_ADDR Field Entity DM00 NUM_SEQ_DTAL Field Entity DM00 NUM_SEQ_SUB_ACC Field Entity DM00 THIB_AG_ARCH_QRY_CTR Rule Entity ARCH_ THIB_AG_GC_QRY_CTR Rule Entity GZ00 THIB_AG_GC_SETL_SCH_CTR Rule Entity GZ00 THIB_AG_RVOK_MQRY_CTR Rule Entity GZ00

[0105] For example, Table 2 is a candidate elimination table for development resources. As shown in Table 2, “LONGNAME” is the development resource name field, “TYPE” is the type field, “ENTITY” is the entity field, and PROJECT is the business group field.

[0106] Step 305: Obtain the business group information to which the target migration package belongs from the basic information of the target migration package.

[0107] For example, in Table 1, the business group information of the target migration package in the basic information of the target migration package is "GZ00".

[0108] Step 306: Compare the business group information of the target migration package with the business group information of each development resource.

[0109] In this embodiment, the implementation of steps 305-306 is similar to that of steps 203-204 in embodiment one, and will not be described in detail here.

[0110] Step 307: If it is determined that the business group information of a certain development resource is inconsistent with the business group information of the target migration package, then the relevant information of the development resource is highlighted.

[0111] In this embodiment, if it is determined that the business group information of a certain development resource is inconsistent with the business group information of the target migration package, the name field of the development resource and the corresponding business group field are highlighted in the corresponding candidate removal development resource table.

[0112] For example, as shown in Table 2, after comparing the business group information of each development resource with the business group information of the target migration package, if the business group information of the development resource is “DM00” and “ARCH_” and is inconsistent with the business group information of the target migration package “GZ00”, then the inconsistent development resource name field and the corresponding business group field will be highlighted in the corresponding candidate elimination development resource table. The associated type field and entity field can also be highlighted.

[0113] It should be noted that in Table 2, the first 12 development resource-related information items are displayed in bold to indicate that the development resource-related information is highlighted.

[0114] Step 308: Send the highlighted development resource information to the development user terminal so that the development user terminal can highlight the development resource information and the development user can filter out the development resources to be migrated in the PCOM operation terminal based on the highlighted development resource information.

[0115] Optionally, in this embodiment, sending the highlighted development resource information to the development user terminal includes:

[0116] The candidate removal development resource table is sent to the development user terminal. The candidate removal development resource table includes development resource information that is highlighted and development resource information that is not highlighted. The development resource information that is not highlighted is development resource information that is consistent with the business group information to which the target migration package belongs.

[0117] For example, as shown in Table 2, non-bold display of development resource-related information indicates that it is not highlighted. Therefore, the non-bold development resource-related information is consistent with the business group information to which the target migration package belongs.

[0118] The development resource migration analysis method provided in this embodiment, after determining the development resource name field and corresponding business group field under each migration attribute, and thus determining the business group information to which the development resource belongs under each migration attribute, stores the development resource name field and corresponding business group field under each migration attribute in the corresponding candidate removal development resource table. Each development resource name field and corresponding business group field is located in the same row of the corresponding candidate removal development resource table. The candidate removal development resource table is sent to the development user terminal. The candidate removal development resource table includes highlighted development resource related information and non-highlighted development resource related information. The non-highlighted development resource related information is development resource related information consistent with the business group information to which the target migration package belongs. This allows development users to more clearly see development resource related information that is inconsistent with the business group to which the target migration package belongs, and also to see development resource related information that is consistent with the business group to which the target migration package belongs, thereby further improving the removal efficiency of development resources that do not need to be migrated.

[0119] Example 3

[0120] Currently, when removing redundant development resources from migration analysis results, developers manually filter and remove them through the MRE operation terminal. This method is prone to being overlooked by developers with insufficient business skills, even when the migration analysis result list is small, ultimately leading to the inclusion of non-production development resources in the production environment. Therefore, this embodiment of the invention establishes a mandatory enforcement mechanism, requiring that developers must have already performed the removal action through the highlighted development resource information before successfully submitting a migration request. Therefore, this embodiment of the invention also includes the following technical solutions.

[0121] Figure 5 This is a flowchart illustrating a development resource migration analysis method provided in another embodiment of the present invention, as shown below. Figure 5 As shown, the development resource migration analysis method provided in this embodiment, based on the development resource migration analysis method provided in any of the above embodiments, further includes the following steps after sending the highlighted development resource-related information to the development user terminal:

[0122] Step 401: Monitor whether the development user has submitted a migration request through the application to migrate the device.

[0123] In this embodiment, the developer uses at least one candidate elimination development resource table obtained by classifying electronic devices as a reference, filters out the development resources to be migrated in the PCOM operation terminal, eliminates the development resources that do not need to be migrated, and submits a migration application request by applying for migration device.

[0124] Specifically, users can enter the relevant information of the target migration package in the operation interface for applying to migrate the equipment, and then click the submit component to submit the migration application request. The relevant information of the target migration package may include: the identification information of the target migration package, the version of downstream development resources, the version of upstream development resources, and at least one candidate exclusion development resource table, etc.

[0125] In this embodiment, the electronic device monitors the device requesting migration by communicating with it, and in turn monitors the migration request submitted by the development user.

[0126] Step 402: If it is determined that the developer user submitted a migration request through the application for device migration, then check whether the developer user submitted a candidate removal development resource form through the application for device migration.

[0127] In this embodiment, if a migration request is detected, it is detected whether the developer has submitted the candidate removal development resource form to the migration request device before clicking the submit component. Based on the detection result, the migration request device is controlled to send out the migration request.

[0128] Step 403: If it is determined that the candidate removal development resource form has not been submitted, then control the application migration device to prevent it from sending the migration application request to the review user client.

[0129] Step 404: If it is confirmed that a candidate removal development resource form has been submitted, then control the application migration device to allow the application request to be sent to the review user client.

[0130] Specifically, in this embodiment, if it is determined that no candidate removal development resource table has been submitted, it indicates that the developer user is highly likely not using the candidate removal development resource table as a reference to remove development resources that do not need to be migrated. In this case, the migration request device is controlled to prevent the migration request from being sent to the reviewing user's client. The migration request device can also display a prompt message on the developer user's corresponding client to remind the developer user to use the candidate removal development resource table as a reference when removing development resources that do not need to be migrated. If it is determined that a candidate removal development resource table has been submitted, it indicates that the developer user has viewed the candidate removal development resource table and used it as a reference to remove development resources that do not need to be migrated. In this case, the migration request device is controlled to allow the request to be sent to the reviewing user's client.

[0131] It should be noted that after receiving a migration request, the reviewing user client can send a response confirming the migration request's approval to the development user client if the review is successful. Furthermore, the reviewing user will use the PCOM terminal to migrate the target migration package corresponding to the selected development resources to be migrated to the upstream development resource version database of the host application repository (MRE).

[0132] The development resource migration analysis method provided in this embodiment monitors whether development users submit migration request requests through the migration application device. If it is confirmed that a development user has submitted a migration request request through the migration application device, it checks whether the development user has submitted a candidate removal list of development resources through the migration application device. If it is confirmed that no candidate removal list of development resources has been submitted, it controls the migration application device to prevent the migration request from being sent to the reviewing user's client. If it is confirmed that a candidate removal list of development resources has been submitted, it controls the migration application device to allow the request to be sent to the reviewing user's client. This method can remind development users to remove development resources that do not need to be migrated when they submit migration request requests. Only after removing development resources that do not need to be migrated with reference to the candidate removal list of development resources can the migration request request be successfully submitted. This avoids the problem of non-production development resources being brought into the production environment due to developers neglecting the migration analysis and removal actions.

[0133] Example 4

[0134] Figure 6 This is a schematic diagram of the structure of a development resource migration analysis device provided in an embodiment of the present invention, as shown below. Figure 6 As shown, the development resource migration analysis device 50 provided in this embodiment includes: a first acquisition module 51, a determination module 52, a second acquisition module 53, a comparison module 54, a highlight display module 55, and a sending module 56.

[0135] The system comprises the following modules: First Acquisition Module 51, which acquires the migration analysis results corresponding to the target migration package; the target migration package is a migration package from a first development resource version to a second development resource version; the migration package includes multiple development resources. Determination Module 52, which determines the basic information of the target migration package and the business group information of each development resource under each migration attribute in the target migration package from the migration analysis results. Second Acquisition Module 53, which acquires the business group information of the target migration package from its basic information. Comparison Module 54, which compares the business group information of the target migration package with the business group information of each development resource. Highlighting Module 55, which highlights the relevant information of a development resource if it is determined that the business group information of a certain development resource is inconsistent with the business group information of the target migration package. Sending Module 56, which sends the highlighted development resource information to the development user terminal, so that the development user terminal can highlight the relevant development resource information and the development user can filter the development resources to be migrated in the PCOM operation terminal based on the highlighted development resource information.

[0136] The development resource migration analysis device provided in this embodiment can perform... Figure 3 The technical solution of the method embodiment shown has the same implementation principle and technical effect as... Figure 3 The methods and embodiments shown are similar and will not be described in detail here.

[0137] Optionally, module 52 is defined, specifically for:

[0138] The relevant table structure of the migration analysis results is parsed to obtain the basic information fields of the target migration package, the name field, migration attribute field, and business group field of each development resource; the basic information of the target migration package is determined from the fields related to the basic information of the target migration package, and the business group information of the development resource under each migration attribute is determined according to the name field, migration attribute field, and business group field of each development resource.

[0139] Optionally, module 52, when determining the business group information of each development resource under each migration attribute based on the name field, migration attribute field, and business group field of each development resource, is specifically used for:

[0140] Based on the name field and migration attribute field of each development resource, the development resources are classified according to their migration attributes; the name field and corresponding business group field of each development resource under each migration attribute are determined to determine the business group information to which the development resource under each migration attribute belongs.

[0141] Optionally, it may also include: a storage module.

[0142] The storage module is used to store the development resource name field and the corresponding business group field under each migration attribute into the corresponding candidate removal development resource table; each development resource name field and the corresponding business group field are located in the same row of the corresponding candidate removal development resource table.

[0143] Optionally, the highlighting module 55 is specifically used to highlight the development resource name field and the corresponding business group field in the corresponding candidate exclusion development resource table.

[0144] Accordingly, the sending module 56 is specifically used to send the candidate removal development resource table to the development user terminal. The candidate removal development resource table includes development resource related information that is highlighted and development resource related information that is not highlighted. The development resource related information that is not highlighted is development resource related information that is consistent with the business group information to which the target migration package belongs.

[0145] Optionally, it may also include: a monitoring module, a detection module, and a control module.

[0146] The system includes several modules: a monitoring module to monitor whether developers submit migration requests via the device migration application; a detection module to check whether, if a developer submits a migration request via the device migration application, they have also submitted a candidate removal form for development resources; and a control module to prevent the device migration application from sending the request to the reviewing user's client if no candidate removal form has been submitted, and to allow the request to be sent to the reviewing user's client if a candidate removal form has been submitted.

[0147] Optionally, the downstream development resource version is the pre-production version, and the upstream development resource version is the production version.

[0148] The development resource migration analysis device provided in this embodiment can perform... Figures 4-5 The technical solution of the method embodiment shown has the same implementation principle and technical effect as... Figures 4-5 The methods and embodiments shown are similar and will not be described in detail here.

[0149] Example 5

[0150] Figure 7 This is a schematic diagram of the structure of an electronic device used to implement the development resource migration analysis method of this invention. Figure 7 As shown, the electronic device 60 provided in this embodiment includes at least one processor 62, a memory 61, and a transceiver 63.

[0151] The processor 62, memory 61, and transceiver 63 are interconnected.

[0152] The memory 61 stores computer-executed instructions. The transceiver 63 is used for sending and receiving data.

[0153] At least one processor 62 executes computer execution instructions stored in memory, causing the at least one processor to perform the method provided in any one of Embodiments 1 to 3.

[0154] Example 6

[0155] Figure 8 This is a block diagram of an electronic device used to implement the development resource migration analysis method of this invention, such as... Figure 8 As shown, the electronic device can be a computer, a messaging device, a tablet, a server, a server cluster, etc.

[0156] Electronic device 700 may include one or more of the following components: processing component 702, memory 704, power supply component 706, input / output (I / O) interface 712, sensor component 714, and communication component 716.

[0157] Processing component 702 typically controls the overall operation of electronic device 700, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 702 may include one or more processors 720 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 702 may include one or more modules to facilitate interaction between processing component 702 and other components.

[0158] Memory 704 is configured to store various types of data to support the operation of electronic device 700. Examples of this data include instructions for any application or method operating on electronic device 700, contact data, phonebook data, messages, pictures, videos, etc. Memory 704 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0159] Power supply component 706 provides power to various components of electronic device 700. Power supply component 706 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to electronic device 700.

[0160] I / O interface 712 provides an interface between processing component 702 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0161] Sensor assembly 714 includes one or more sensors for providing state assessments of various aspects of electronic device 700. For example, sensor assembly 714 may detect the on / off state of electronic device 700, the relative positioning of components such as the display and keypad of electronic device 700, changes in position of electronic device 700 or a component of electronic device 700, the presence or absence of user contact with electronic device 700, orientation or acceleration / deceleration of electronic device 700, and temperature changes of electronic device 700. Sensor assembly 714 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 714 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 714 may also include an accelerometer, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0162] Communication component 716 is configured to facilitate wired or wireless communication between electronic device 700 and other devices. Electronic device 700 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 716 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 716 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0163] In an exemplary embodiment, the electronic device 700 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0164] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 704 including instructions, which can be executed by a processor 720 of an electronic device 700 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0165] A non-transitory computer-readable storage medium, wherein when the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is able to perform the method provided in any one of the embodiments 1 to 3 described above.

[0166] In an exemplary embodiment, a computer program product is also provided, including a computer program that is executed by a processor using the method provided in any one of the embodiments 1 to 3 described above.

[0167] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0168] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A method for analyzing the migration of development resources, characterized in that, include: Obtain the migration analysis results corresponding to the target migration package; The target migration package is a migration package that migrates from a downstream development resource version to an upstream development resource version. The migration package includes multiple development resources, which exist in the form of programs. The relevant table structure of the migration analysis results is parsed to obtain the basic information fields of the target migration package, including the name field, migration attribute field, and business group field of each development resource; The basic information of the target migration package is determined from the fields related to the basic information of the target migration package, and each development resource is classified according to its migration attribute based on the name field and migration attribute field of each development resource. Determine the development resource name field and the corresponding business group field under each migration attribute to determine the business group information to which the development resource belongs under each migration attribute; Obtain the business group information to which the target migration package belongs from the basic information of the target migration package; Compare the business group information to which the target migration package belongs with the business group information to which each development resource belongs; If it is determined that the business group information of a certain development resource is inconsistent with the business group information of the target migration package, then the relevant information of the development resource will be highlighted. The highlighted development resource information is sent to the development user terminal so that the development user terminal can highlight the development resource information, and the development user can filter out the development resources to be migrated in the PCOM operation terminal based on the highlighted development resource information.

2. The method according to claim 1, characterized in that, After determining the development resource name field and the corresponding business group field under each migration attribute to determine the business group information to which the development resource belongs under each migration attribute, the process further includes: Store the development resource name field and the corresponding business group field under each migration attribute into the corresponding candidate development resource removal table; each development resource name field and the corresponding business group field are located in the same row of the corresponding candidate development resource removal table.

3. The method according to claim 2, characterized in that, The step of highlighting the relevant information of the development resources includes: The development resource name field and its corresponding business group field are highlighted in the corresponding candidate removal development resource table; Sending the highlighted development resource information to the development user terminal includes: The candidate removal development resource table is sent to the development user terminal. The candidate removal development resource table includes development resource information that is highlighted and development resource information that is not highlighted. The development resource information that is not highlighted is development resource information that is consistent with the business group information to which the target migration package belongs.

4. The method according to any one of claims 1-3, characterized in that, After sending the highlighted development resource information to the development user terminal, the process also includes: Monitor whether the development user submits a migration request through the device migration application process; If it is determined that the developer user submitted a migration request through the application to migrate the device, then check whether the developer user submitted a candidate removal development resource form through the application to migrate the device. If it is determined that the candidate removal development resource form has not been submitted, then the control device applying for migration shall be prohibited from sending the migration application request to the review user client; If it is confirmed that a candidate removal development resource form has been submitted, the control application migration device is allowed to send the migration application request to the review user client.

5. The method according to any one of claims 1-3, characterized in that, The downstream development resource version is the pre-production version, and the upstream development resource version is the production version.

6. A development resource migration analysis device, characterized in that, include: The first acquisition module is used to acquire the migration analysis results corresponding to the target migration package; The target migration package is a migration package for migrating from the first development resource version to the second development resource version; The migration package includes multiple development resources, which exist in the form of programs. The determination module is used to parse the relevant table structure of the migration analysis results to obtain the basic information related fields of the target migration package, the name field, migration attribute field and business group field of each development resource; The basic information of the target migration package is determined from the fields related to the basic information of the target migration package, and each development resource is classified according to its migration attribute based on the name field and migration attribute field of each development resource. Determine the development resource name field and the corresponding business group field under each migration attribute to determine the business group information to which the development resource belongs under each migration attribute; The second acquisition module is used to acquire the business group information to which the target migration package belongs from the basic information of the target migration package; The comparison module is used to compare the business group information of the target migration package with the business group information of each development resource. The highlighting module is used to highlight the relevant information of a development resource if it is determined that the business group information of a certain development resource is inconsistent with the business group information of the target migration package. The sending module is used to send the highlighted development resource information to the development user terminal, so that the development user terminal can highlight the development resource information and the development user can filter out the development resources to be migrated in the PCOM operation terminal based on the highlighted development resource information.

7. An electronic device, characterized in that, include: At least one processor, memory, and transceiver; The processor, the memory, and the transceiver circuit are interconnected; The memory stores computer-executed instructions; The transceiver is used to send and receive data; The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the method as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-5.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-5.

Images