Application system evaluation and result query method and device, equipment and storage medium

Abstract

The invention provides an evaluation and result query method and device of an application system, equipment and a storage medium, and relates to the technical field of cloud services. The evaluation method of the application system comprises the following steps: obtaining an evaluation rule tree of the application system; wherein the evaluation rule tree comprises evaluation nodes respectively corresponding to a plurality of evaluation dimensions of the application system and topological relations among the evaluation nodes; traversing each evaluation node according to a topological relation among the evaluation nodes in the evaluation rule tree, and determining a corresponding node evaluation result according to a node evaluation rule of each evaluation node; and determining a system evaluation result of the application system according to the node evaluation result of the at least one evaluation node. According to the technical scheme provided by the embodiment of the invention, the application system can be subjected to multi-dimensional evaluation, and a user can conveniently and comprehensively measure the architecture maturity level of the application system, so that architecture review, control, management, governance or optimization and the like can be performed in a targeted manner.

Description

Technical Field

[0001] The present application relates to the field of cloud service technology, and in particular to an application system evaluation and result query method, device, equipment and storage medium. Background Art

[0002] With the rapid development of cloud computing technology and the advancement of digital transformation, many business (also called service) departments use cloud architecture to deploy cloud application systems (also called business systems or service systems) or migrate traditional application systems to the cloud. Users expect to be able to evaluate the overall architecture of cloud application systems, but there is currently a lack of evaluation solutions for the overall architecture of cloud application systems. Summary of the invention

[0003] The embodiments of the present application provide an application system evaluation and result query method, apparatus, device and storage medium to implement architecture evaluation or measurement of the application system.

[0004] In a first aspect, an embodiment of the present application provides an evaluation method for an application system, comprising: obtaining an evaluation rule tree for the application system; wherein the evaluation rule tree comprises evaluation nodes corresponding to multiple evaluation dimensions of the application system and a topological relationship between each evaluation node; traversing each evaluation node according to the topological relationship between each evaluation node in the evaluation rule tree, and determining the corresponding node evaluation results according to the node evaluation rules of each evaluation node; and determining a system evaluation result of the application system according to the node evaluation result of at least one evaluation node.

[0005] In the second aspect, an embodiment of the present application provides an evaluation result query method for an application system, comprising: determining the application system to be queried; displaying a system evaluation result tree of the application system; wherein the system evaluation result tree includes node evaluation results of each evaluation node and the topological relationship between each evaluation node; each evaluation node corresponds one-to-one to each evaluation dimension of the application system.

[0006] In a third aspect, an embodiment of the present application provides an evaluation device for an application system, comprising: an evaluation rule tree acquisition unit, used to acquire an evaluation rule tree for an application system; wherein the evaluation rule tree comprises evaluation nodes corresponding to a plurality of evaluation dimensions of the application system and a topological relationship between each evaluation node; a node evaluation result determination unit, used to traverse each evaluation node according to the topological relationship between each evaluation node in the evaluation rule tree, and determine the corresponding node evaluation results according to the node evaluation rules of each evaluation node; and a system evaluation result determination unit, used to determine the system evaluation result of the application system according to the node evaluation result of at least one evaluation node.

[0007] In a fourth aspect, an embodiment of the present application provides an evaluation result query device for an application system, comprising: an application system determination unit, used to determine the application system to be queried; a system evaluation result tree display unit, used to obtain a system evaluation result tree of the application system; wherein the system evaluation result tree includes node evaluation results of each evaluation node and the topological relationship between each evaluation node; each evaluation node corresponds one-to-one to each evaluation dimension of the application system.

[0008] In a fifth aspect, an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory, wherein the processor implements the method described in any one of the embodiments of the present application when executing the computer program.

[0009] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the method described in any one of the embodiments of the present application is implemented.

[0010] According to the evaluation method of the application system in the embodiment of the present application, by mapping the evaluation dimension (which can also be understood as the measurement dimension) into the evaluation node, an evaluation rule tree is configured for the application system, wherein the evaluation rule tree includes the evaluation nodes corresponding to the multiple evaluation dimensions of the application system and the topological relationship between the evaluation nodes, each evaluation node is configured with the evaluation rules under the corresponding evaluation dimension, and then each evaluation node can be traversed according to the topological relationship, and the node evaluation result of each evaluation node can be determined according to the evaluation rules of each evaluation node, and then the system evaluation result of the application system is determined, thereby performing a multi-dimensional evaluation of the application system, which is convenient for users to comprehensively measure the architectural maturity level of the application system, so as to carry out architecture review control, management, governance or optimization in a targeted manner.

[0011] Furthermore, the system evaluation results can be displayed in a tree-like form, i.e., a system evaluation result tree, in which the scoring results corresponding to each evaluation dimension are displayed according to the corresponding topological relationship, thereby intuitively displaying the global architectural maturity level of the application system and the aspects that need to be governed and improved (evaluation dimensions or measurement dimensions).

[0012] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In the accompanying drawings, unless otherwise specified, the same reference numerals throughout the multiple drawings represent the same or similar parts or elements. These drawings are not necessarily drawn to scale. It should be understood that these drawings only depict some embodiments according to the present application and should not be regarded as limiting the scope of the present application.

[0014] Figure 1 A schematic diagram of an application scenario of the evaluation solution of the application system provided in this application;

[0015] Figure 2 A schematic diagram of an exemplary structure of a data model and a metadata storage instance of an evaluation scheme for an application system provided in this application;

[0016] Figure 3 This is a flow chart of an evaluation method for an application system according to Embodiment 1 of the present application;

[0017] Figure 4 A schematic diagram of the structure of an evaluation rule tree of an evaluation method for an application system in Embodiment 1 of the present application;

[0018] Figure 5 A schematic diagram of the structure of a system evaluation result tree of the evaluation method of the application system in the first embodiment of the present application;

[0019] Figure 6 This is an application example diagram of the evaluation method of the application system in Embodiment 1 of the present application;

[0020] Figure 7 This is an example diagram of the application of the rule module of the evaluation method of the application system in the first embodiment of the present application;

[0021] Figure 8 This is a flow chart of an evaluation method for an application system in Embodiment 2 of the present application;

[0022] Fig. 9 This is a structural block diagram of an evaluation device of an application system in Embodiment 3 of the present application;

[0023] Fig.10 This is a structural block diagram of an evaluation result query device of an application system in Embodiment 4 of the present application;

[0024] Fig.11 A block diagram of an electronic device used to implement an embodiment of the present application. DETAILED DESCRIPTION

[0025] In the following, only some exemplary embodiments are briefly described. As those skilled in the art will appreciate, the described embodiments may be modified in various ways without departing from the concept or scope of the present application. Therefore, the drawings and descriptions are considered to be exemplary in nature and not restrictive.

[0026] To facilitate understanding of the technical solutions of the embodiments of the present application, the following describes the related technologies of the embodiments of the present application. The following related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.

[0027] Application Scenario

[0028] With the rapid development of cloud computing technology and the advancement of digital transformation, many business units or service departments use cloud architecture to deploy cloud application systems or migrate traditional application systems to the cloud. Users expect to be able to evaluate cloud application systems, such as comprehensively evaluating and measuring the maturity level of cloud application system architecture, so that users can conduct architecture review, control, management, governance or optimization in a targeted manner. Among them, application systems can also be called business systems or service systems.

[0029] The embodiment of the present application aims to provide an evaluation scheme for an application system, by configuring an evaluation rule tree for the application system to be evaluated, the evaluation rule tree includes evaluation nodes corresponding to multiple evaluation dimensions of the application system and the topological relationship between the evaluation nodes, traversing each evaluation node, and then evaluating from multiple evaluation dimensions respectively, and obtaining corresponding node evaluation results; further, based on the node evaluation results, the system evaluation results of the application system can be determined.

[0030] Based on the evaluation scheme of the embodiments of the present application, the cloud application system can be evaluated, and the non-cloud application system can be evaluated. The newly deployed application system can also be evaluated. The application embodiment of the present application is not limited to this.

[0031] Figure 1 A schematic diagram of an application scenario of the evaluation scheme of the application system provided in this application. Figure 1 As shown, the application system to be evaluated is such as a service system, a business system, a database system, etc. The embodiment of the present application does not specifically limit the type or architecture of the application system. Among them, the architecture of the application system can also be called IT architecture.

[0032] Exemplarily, the architecture of the application system may include several applications, such as logical applications and physical applications. Among them, the logical application can be understood as the logical design of the application system architecture, and the physical application is the actual application or instance, that is, the business data or service data generated by the actual application. Therefore, logical applications and physical applications usually have a one-to-one mapping relationship. Therefore, in the embodiment of the present application, the evaluation of the application system is mainly to evaluate the maturity of the architecture of the application system, so that users can conduct architecture review, control, management, governance or optimization of the application system in a targeted manner.

[0033] In order to deploy an application system, multiple information technology (IT) resources are required, such as computing resources, storage resources, and network resources. Therefore, for users, the IT resources used to deploy their application systems can also be called IT assets, including but not limited to servers, databases, containers, images, block storage, security groups, elastic network cards, middleware, etc. IT asset metadata describes the entire IT architecture of the application system and is the data source for evaluating the maturity of the application system.

[0034] The configuration management database is used to store IT asset metadata and system evaluation results of the application system. Exemplarily, various metadata of the application system can be stored as a metadata storage instance according to a preset data model. Figure 2 An exemplary structural diagram of a data model and a metadata storage instance is shown. Figure 2 As shown, the storage structure of the metadata storage instance, i.e., the data model, may include identification information, attribute fields, and topological relationships with other data models (including association relationships and association types). Therefore, the metadata storage instance obtained after the IT asset metadata (i.e., the IT asset instance data after the application system is implemented) is stored according to the data model also includes identification information, attribute fields, and topological relationships with the metadata storage instance (including association relationships and association types).

[0035] Among them, the identification information of the data model defines the same type of IT assets in a standard format, such as business or service, application, host or server, database, etc.; correspondingly, the identification information of the metadata storage instance defines the same type of IT asset metadata instance in a standard format, such as identifying the instance as a certain business or service, a certain application, a certain host or server, a certain database, etc.

[0036] The attribute fields of a data model define all the attribute information of a data model. Taking the data model of application-type IT assets as an example, the attribute fields of the data model may include application name, application type, etc. Correspondingly, the attribute fields of the metadata storage instance include various attribute information of the instance, such as the application name, application type and other attribute information of the order application.

[0037] The topological relationship of the data model includes association relationship and association type, where the association relationship defines the relationship between any two data models, for example, a business or service can "include" multiple applications, and an application can "depend on" a database, etc. Accordingly, the topological relationship between data models is used to constrain the topological relationship between metadata storage instances. For example, the order system is "deployed" on two cloud servers and "depends on" a relational database (RDS). "Include", "depend on", and "deploy" are association types. After defining these topological relationships, the entire IT architecture of the application system can be visualized in a mesh. Where N represents the number, such as the number of metadata storage instances or the number of other associated data models or metadata storage instances.

[0038] Exemplarily, the metadata storage instance corresponds to version information, which is used to record changes in IT asset metadata. If the IT asset metadata changes, a new version of the metadata storage instance will be generated. The configuration management database is also used to store metadata version files, recording the version information of each metadata storage instance. Based on the metadata version file, the historical changes of the IT architecture of the application system can be traced.

[0039] like Figure 1 As shown, the evaluation device of the application system can be used to execute the evaluation method of the embodiment of the present application, which includes performing a multi-dimensional evaluation on the application system based on the evaluation rule tree corresponding to the application system, and then obtaining a system evaluation result of the application system. Among them, the evaluation rule tree includes evaluation nodes corresponding to multiple evaluation dimensions of the application system and the topological relationship between each evaluation node. Each evaluation node is configured with an evaluation rule under the corresponding evaluation dimension, and then each evaluation node can be traversed according to the topological relationship, and the node evaluation result of each evaluation node is determined according to the evaluation rule of each evaluation node, and then the system evaluation result of the application system is determined.

[0040] Exemplarily, the system evaluation results of the application system can be stored in the configuration management database for user query. The system evaluation results of the application system correspond to version information for recording changes in the system evaluation results, so as to facilitate tracing historical snapshots or changes in the IT architecture evaluation results of the application system.

[0041] Based on the evaluation scheme of the embodiment of the present application, a comprehensive multi-dimensional and multi-level evaluation can be performed on the application system, thereby facilitating users to conduct architecture review, control, management, governance or optimization in a targeted manner.

[0042] Exemplarily, the evaluation device of the application system can be in the form of a hardware device (such as a server, terminal device) or a hardware chip with data processing functions, such as a CPU, a graphics processor (Graphics Processing, GPU), a field programmable gate array (Field Programmable Gate Array, FPGA), a network processor (Neural-network Processing Unit, NPU), an AI accelerator card or a data processor (Data Processing Unit, DPU), etc.; it can also be an application, service, instance, a functional module in the form of software, a virtual machine (Virtual Machine, VM), a container or a cloud server, etc.; or it can also be a combination of software and hardware.

[0043] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose or edit authorization or rejection.

[0044] The following is a detailed description of the technical solution of the present application and how the technical solution of the present application solves the aforementioned technical problems with specific embodiments. Among them, Embodiment 1 mainly introduces an evaluation method for an application system, and Embodiment 2 mainly introduces an evaluation result query method for an application system. It should be noted that the several specific embodiments listed can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

[0045] Embodiment 1

[0046] Figure 3 A flow chart of an evaluation method for an application system according to an embodiment of the present application is shown. The evaluation method for an application system can be applied to an evaluation device for an application system. Figure 3 As shown, the evaluation method of the application system includes:

[0047] Step S301: Obtain an evaluation rule tree of the application system; wherein the evaluation rule tree includes evaluation nodes corresponding to multiple evaluation dimensions of the application system and topological relationships between the evaluation nodes.

[0048] The application system is the application system to be evaluated, such as a service system, a business system, a database system, etc. In the embodiment of the present application, the application system to be evaluated can be a cloud application system or a non-cloud application system, a newly deployed application system or an application system that has been deployed in the past, and the embodiment of the present application does not limit this.

[0049] For example, the IT architecture of an application system can usually be measured or evaluated from many aspects. One aspect is an evaluation dimension, which can also be called a measurement dimension, which is used to characterize a factor for evaluating or measuring the application system. The evaluation dimension can be preset according to the specific type of the application system to be evaluated, such as application availability, application performance, observability, etc., and then the evaluation rule tree can be configured for the application system according to multiple evaluation dimensions.

[0050] The evaluation rule tree includes evaluation nodes corresponding to multiple evaluation dimensions of the application system and the topological relationship between each evaluation node. Each evaluation node corresponds to an evaluation dimension, and an evaluation dimension may be divided into multiple evaluation sub-dimensions. For example, the evaluation dimension of observability can be divided into infrastructure monitoring, application monitoring, business monitoring and other evaluation dimensions for evaluation or measurement. Therefore, the evaluation rule tree can also be called an evaluation dimension tree or a measurement dimension tree. In the tree structure, an evaluation node corresponds to a tree node, that is, an evaluation dimension corresponds to a tree node, which can be a root node, a parent node or a leaf node, and the topological relationship between evaluation dimensions, such as multiple evaluation sub-dimensions contained in an evaluation dimension, can be mapped to the topological relationship between evaluation nodes.

[0051] For example, Figure 4 FIG. 1 is a schematic diagram showing the structure of an evaluation rule tree of an application system to be evaluated. Figure 4 As shown, in the evaluation rule tree, each tree node represents an evaluation node, corresponding to an evaluation dimension. Specifically, the root node represents the application system to be evaluated, for example, it can be represented by the name or identification information of the application system. The parent node includes the evaluation nodes corresponding to the evaluation dimension 5, the evaluation dimension 7 and the evaluation dimension 5-1. The leaf node includes the evaluation nodes corresponding to the evaluation dimension 1, the evaluation dimension 2, the evaluation dimension 3, the evaluation dimension 4, the evaluation dimension 5-1-1, the evaluation dimension 5-1-2, the evaluation dimension 5-2, the evaluation dimension 5-3, the evaluation dimension 6, the evaluation dimension 7-1, the evaluation dimension 7-2 and the evaluation dimension 7-3. Therefore, the evaluation rule tree not only includes each evaluation node, but also can represent the topological relationship between each evaluation dimension, that is, the topological relationship between each evaluation node.

[0052] Exemplarily, each evaluation node defines the dimension name, dimension identifier, parent dimension and other information of the evaluation dimension corresponding to it, thereby forming an evaluation rule tree. The dimension name is the name of the evaluation node, that is, the name of the evaluation dimension; the dimension identifier is used to query the corresponding evaluation node in the evaluation rule tree; the parent dimension information is used to declare the parent node information of the evaluation node, including which parent node of the current evaluation node is, such as for the evaluation node of evaluation dimension 5-1, the parent dimension information of the evaluation node is the evaluation node information of evaluation dimension 5. The root node does not have a parent dimension. Based on this feature, the root node in the evaluation rule tree can be queried, and then the evaluation rule tree of the corresponding application system can be queried.

[0053] Furthermore, each evaluation node corresponds to a node evaluation rule. For example, the node evaluation rule of a parent node can be all the child nodes of the parent node and the weight of each child node in the parent node. The scoring result (also called the scoring result) of each child node and the weight in the parent node are weighted and summarized to obtain the scoring result of the node, which is used as the node evaluation result of the parent node.

[0054] Another example: the evaluation rules of a leaf node may include metadata configuration information, metadata conversion rules, and scoring rules. Among them, the metadata configuration information is the configuration information of the data source on which the leaf node evaluation depends, such as the identification information and attribute fields of the metadata storage instance. Based on the metadata configuration information of the leaf node, the metadata of the application system can be called for evaluation or measurement calculation. The metadata conversion rules are used to perform data conversion on the called metadata, such as secondary cleaning and conversion. The scoring rules define the scorer applicable to the evaluation dimension corresponding to the leaf node, which is used to score the data conversion results of the metadata, obtain the scoring result of the leaf node, and serve as the node evaluation result of the leaf node.

[0055] Step S302: traverse each evaluation node according to the topological relationship between each evaluation node in the evaluation rule tree, and determine the corresponding node evaluation result according to the node evaluation rule of each evaluation node.

[0056] Exemplarily, the evaluation rule tree of the application system may have multiple versions, and for the application system to be evaluated, the latest version of the evaluation rule tree corresponding to it may be obtained. The evaluation rule tree is recursively traversed using a depth-first traversal algorithm, and then each evaluation node may be traversed according to the topological relationship between the evaluation nodes, and the node evaluation result of each evaluation node may be determined based on the node evaluation rule of each evaluation node.

[0057] For example: if it is a parent node, the scoring results of each child node of the parent node and the weighted summary in the parent node are used to obtain the node evaluation result of the parent node. Another example: if it is a leaf node, based on the metadata configuration information of the leaf node, the corresponding metadata of the application system is called, and the called metadata is converted, and then based on the scorer applicable to the leaf node, the data conversion result of the metadata is scored to obtain the node evaluation result of the leaf node.

[0058] Step S303: Determine a system evaluation result of the application system according to the node evaluation result of at least one evaluation node.

[0059] For example, based on the evaluation rule tree of the application system, the node evaluation results under each evaluation dimension can be obtained, including the node evaluation results of the root node, such as the scoring results. The node evaluation results of the root node can be used as the system evaluation results of the application system. In another example, the system evaluation results can be displayed in a tree-like result, that is, a system evaluation result tree. The system evaluation result tree includes the node evaluation results of each evaluation node and the topological relationship between each evaluation node, that is, the node evaluation results corresponding to each evaluation dimension and the topological relationship between each evaluation dimension, such as Figure 5 shown.

[0060] According to the evaluation method of the application system in the embodiment of the present application, the evaluation dimensions are mapped into evaluation nodes, and then an evaluation rule tree is configured for the application system, wherein the evaluation rule tree includes evaluation nodes corresponding to multiple evaluation dimensions of the application system and the topological relationship between each evaluation node, and each evaluation node is configured with an evaluation rule under the corresponding evaluation dimension, and then each evaluation node can be traversed according to the topological relationship, and the node evaluation result of each evaluation node can be determined according to the evaluation rules of each evaluation node, and then the system evaluation result of the application system can be determined, thereby performing a multi-dimensional evaluation of the application system, which is convenient for users to comprehensively measure the architectural maturity level of the application system, so as to carry out architectural review control, management, governance or optimization in a targeted manner.

[0061] In one embodiment, in step S302, each evaluation node is traversed according to the topological relationship between each evaluation node in the evaluation rule tree, and the corresponding node evaluation results are determined according to the node evaluation rules of each evaluation node, including: traversing each evaluation node according to the topological relationship; in response to the evaluation node being a leaf node, determining the scoring result of the leaf node as the node evaluation result of the leaf node based on the leaf node evaluation rule of the leaf node; wherein the leaf node evaluation rule includes metadata configuration information, metadata conversion rules and scoring rules.

[0062] Evaluation nodes include leaf nodes, such as Figure 4 and Figure 5The evaluation dimensions of the leaf nodes represent the most fine-grained measurement dimensions. Therefore, by configuring detailed evaluation rules, it is convenient to score or grade the leaf nodes.

[0063] Specifically, the node rules of the leaf node are the leaf node evaluation rules, including metadata configuration information, metadata conversion rules and scoring rules. Among them, the metadata configuration information is the configuration information of the data source on which the leaf node evaluation depends, such as the identification information and attribute fields of the data model. Based on the metadata configuration information of the leaf node, the metadata of the application system can be called for evaluation or measurement calculation. The metadata conversion rules are used to perform data conversion on the called metadata, such as secondary cleaning and conversion. The scoring rules define the scorer applicable to the evaluation dimension corresponding to the leaf node, which is used to score the data conversion results of the metadata, obtain the scoring result of the leaf node, and serve as the node evaluation result of the leaf node.

[0064] Exemplarily, the metadata conversion rule may be a simple mathematical calculation expression, such as an arithmetic expression or a logical expression. The metadata conversion rule may be a custom script, such as a complex data conversion function may be written according to a standard interface, and by calling the script, complex data conversion may be implemented, which is used for more complex secondary data conversion scenarios. The scoring rule may be an enumeration scoring method, a Boolean expression scoring method, or other custom scoring method, which is not limited in the embodiments of the present application.

[0065] Among them, the enumeration scoring method is to enumerate the corresponding scores for the data conversion results of the metadata. Taking the evaluation dimension or measurement dimension of the service level as an example, if it is a cloud component, it will get 1 point; if it is an open source component, it will get 0.5 points; and so on. The Boolean expression scoring method is to set a Boolean expression and use the Boolean expression to judge and score the data conversion results of the metadata. Custom scoring methods such as setting a data calculation expression and using the data calculation expression to calculate the data conversion results of the metadata to obtain a scoring result.

[0066] In one embodiment, based on the leaf node evaluation rule of the leaf node, the scoring result of the leaf node is determined as the node evaluation result of the leaf node, including: based on the metadata configuration information, calling at least one metadata of the application system; performing data conversion on at least one metadata according to the metadata conversion rule; using the scoring rule, scoring the data conversion result of at least one metadata to obtain the scoring result of the leaf node.

[0067] Exemplarily, by parsing the node evaluation rules of the leaf node, metadata configuration information, metadata conversion rules and scoring rules can be obtained. The metadata configuration information includes target identification information and target attribute fields, so that the corresponding target metadata storage instance can be determined, such as determining the target metadata storage instance corresponding to the target identification information from multiple metadata storage instances of the application system; calling the data corresponding to the target attribute field from the target metadata storage instance to obtain at least one metadata. Furthermore, the obtained metadata is converted according to the metadata conversion rules of the leaf node, and then the data conversion result is scored according to the scoring rules of the leaf node, thereby obtaining the scoring result of the leaf node.

[0068] In an example, for a certain leaf node, the rule type of the scoring rule, that is, the type of the scorer, is obtained by parsing the node evaluation rule of the leaf node; the target identification information is "APPLICATION"; the target association relationship and the target association type are "'relationWithApp':'IS'", that is, the metadata storage instance to be called is the actual metadata of the application "APPLICATION", rather than the metadata of the cloud server on which it depends; the target attribute fields are "configCenterWay" and "configCenter", that is, the metadata of the "configCenterWay" field and the metadata of the "configCenter" field need to be called; the scoring rule is: if {configCenterWay}>2&&configCenter==1, the score is 1; if ${configCenterWay}<=2&&${configCenter}=1, the score is 0.5.

[0069] In this way, different node evaluation rules can be adapted according to actual needs and evaluation dimensions, including configuring metadata, data conversion rules and scoring rules suitable for the evaluation dimension corresponding to the leaf node, and then scoring the most fine-grained evaluation nodes.

[0070] In one embodiment, in step S302, each evaluation node is traversed according to the topological relationship between each evaluation node in the evaluation rule tree, and the corresponding node evaluation results are determined according to the node evaluation rules of each evaluation node, including: traversing each evaluation node according to the topological relationship; in response to the evaluation node being a parent node, based on the scoring results of each child node of the parent node and the weight of each child node in the parent node, determining the scoring result of the parent node as the node evaluation result of the parent node.

[0071] Evaluation nodes include parent nodes, i.e. non-leaf nodes, such as Figure 4 and Figure 5 The evaluation node corresponding to the evaluation dimension 5, evaluation dimension 7 and evaluation dimension 5-1 in is the parent node. For the parent node, the scoring result of the current parent node can be calculated based on the score of each child node of the parent node and the weight configured for the child node in the parent node, that is, the node evaluation result of the current parent node. In this way, the parent dimension information can be configured for the evaluation dimension (evaluation sub-dimension) corresponding to each child node, including which parent node of the current evaluation node is and the corresponding weight, thereby determining the node evaluation result under the evaluation dimension of each parent node.

[0072] In one embodiment, the evaluation node includes a root node, and determining a system evaluation result of the application system according to a node evaluation result of at least one evaluation node includes: using the node evaluation result of the root node as the system evaluation result of the application system.

[0073] As mentioned above, the root node does not have a parent dimension. Based on this feature, the root node in the evaluation rule tree can be queried, and then the corresponding node evaluation result can be queried, such as Figure 5 As shown in the figure, the node evaluation result of the root node can represent the system evaluation result of the corresponding application system, that is, 90 points. In this way, the overall score (system evaluation result) of the application system can be easily and quickly queried based on the root node.

[0074] In one embodiment, a system evaluation result of an application system is determined based on a node evaluation result of at least one evaluation node, including: generating a system evaluation result tree of the application system according to the topological relationship between each evaluation node and the node evaluation result of each evaluation node; wherein the system evaluation result tree includes the node evaluation results of each evaluation node and the topological relationship between each evaluation node.

[0075] That is to say, the system evaluation results can be displayed in a tree-like form, i.e., the system evaluation result tree, such as Figure 5 As shown, the scoring results corresponding to each evaluation dimension are displayed according to the corresponding topological relationship, so as to intuitively display the global architecture maturity level of the application system and the aspects that need to be governed and improved (evaluation dimensions or measurement dimensions).

[0076] In one embodiment, the method of the embodiment of the present application may also include: storing various metadata of the application system as a metadata storage instance according to a preset data model; wherein the data model includes identification information, attribute fields, and topological relationships with other metadata storage instances.

[0077] Among them, the metadata of the application system is stored as a metadata storage instance, and the data model is the storage structure of the metadata storage instance. Figure 2As shown, the storage structure of the metadata storage instance, i.e., the data model, may include identification information, attribute fields, and topological relationships with other data models (including association relationships and association types). Therefore, the metadata storage instance obtained after the IT asset metadata (i.e., the IT asset instance data after the application system is implemented) is stored according to the data model also includes identification information, attribute fields, and topological relationships with the metadata storage instance (including association relationships and association types).

[0078] Among them, the identification information of the data model defines the same type of IT assets in a standard format, such as business or service, application, host or server, database, etc.; correspondingly, the identification information of the metadata storage instance defines the same type of IT asset metadata instance in a standard format, such as identifying the instance as a certain business or service, a certain application, a certain host or server, a certain database, etc.

[0079] The attribute fields of a data model define all the attribute information of a data model. Taking the data model of application-type IT assets as an example, the attribute fields of the data model may include application name, application type, etc. Correspondingly, the attribute fields of the metadata storage instance include various attribute information of the instance, such as the application name, application type and other attribute information of the order application.

[0080] The topological relationship of the data model includes association relationship and association type. The association relationship defines the relationship between any two data models. For example, a business or service can "include" multiple applications, and an application can "depend on" a database. Accordingly, the topological relationship between data models is used to constrain the topological relationship between metadata storage instances. For example, the order system is "deployed" on two cloud servers and "depends on" an RDS. "Include", "depend on", and "deploy" are association types. After defining these topological relationships, the entire IT architecture of the application system can be displayed in a network-like visualization.

[0081] Combine the following Figure 6 and Figure 7 An application example of the evaluation scheme of the application system in combination with the embodiment of the present application. Figure 6As shown, the data module, such as the Configuration Management Database (CMDB), is responsible for the storage of IT asset metadata and evaluation results. Among them, according to the preset data model, the metadata of the application system can be stored as a metadata storage instance, so that at the macro level, the entire IT architecture of the application system can be displayed through a network visualization, and it serves as the source data input of the architecture maturity measurement module. The measurement results calculated by the measurement module, that is, the system evaluation results of the application system, are stored in the CMDB for user query. Exemplarily, both the metadata storage instance and the system evaluation results correspond to version information, that is, the data version, which is used to record the changes in IT asset metadata and system evaluation results, so as to facilitate the tracing of historical snapshots / changes of the IT architecture of the application system and historical snapshots / changes of the system evaluation results.

[0082] The system evaluation results of each application system can be stored in the CMDB in the form of a system evaluation result tree, which is convenient for users to query the system evaluation results of a certain application system. The specific storage data of the system evaluation result tree includes: the name of the evaluation dimension (evaluation node), the measurement object (i.e., the application system to be evaluated) and its version, the node scoring result, the parent node (the root node has no parent node), the version of the system evaluation result and other key information.

[0083] The rule model is used to configure the evaluation rule tree, that is, the evaluation rules of each application system (i.e., evaluation dimensions or measurement dimensions) are configured in a tree structure of an N-layer tree, and for each tree node (i.e., evaluation node), the corresponding node evaluation rule is configured for it. Specifically, each evaluation node defines the dimension name, dimension identifier, parent dimension and other information of the evaluation dimension corresponding to it. Among them, the dimension name is the name of the evaluation node, that is, the name of the evaluation dimension; the dimension identifier is used to query the corresponding evaluation node in the evaluation rule tree; the parent dimension information is used to declare the information of the parent node of the evaluation node, including which is the parent node of the current evaluation node.

[0084] Each evaluation node corresponds to a node evaluation rule. For example, the node evaluation rule of the parent node (non-leaf node dimension) can be all the child nodes of the parent node and the weight of each child node in the parent node. The scoring result (also called the scoring result) of each child node and the weight in the parent node are weighted and summarized to obtain the scoring result of the node, and used as the node evaluation result of the parent node. For another example, the evaluation rule of the leaf node dimension can include metadata configuration information (depending on the data source, that is, the metadata that needs to be called), metadata conversion rules and scoring rules (scoring methods corresponding to the scorer). Among them, the metadata configuration information is the configuration information of the data source on which the leaf node evaluation depends, such as the identification information and attribute fields of the metadata storage instance. Based on the metadata configuration information of the leaf node, the metadata of the application system can be called for evaluation or measurement calculation. The metadata conversion rule is used to perform data conversion on the called metadata, such as secondary cleaning and conversion. The scoring rule defines the scorer applicable to the evaluation dimension corresponding to the leaf node, which is used to score the data conversion result of the metadata, obtain the scoring result of the leaf node, and use it as the node evaluation result of the leaf node.

[0085] The measurement module is used to perform evaluation or measurement calculation of an application system, including: rule parsing, such as parsing the evaluation rule tree of the application, recursively traversing each evaluation node on the evaluation rule tree using a depth-first traversal algorithm, and solving the node evaluation rules of each evaluation node, performing data conversion and measurement calculation, obtaining the node evaluation results of each evaluation node, and then obtaining the score of the application system under each evaluation dimension.

[0086] Based on the evaluation scheme of the embodiment of the present application, a comprehensive multi-dimensional and multi-level evaluation can be performed on the application system, thereby facilitating users to conduct architecture review, control, management, governance or optimization in a targeted manner.

[0087] Embodiment 2

[0088] An embodiment of the present application provides a method for querying application system evaluation results, wherein at least part of the technical solutions and corresponding technical effects of Embodiment 1 can be referenced to the embodiments of the present application. Figure 8 A flow chart of an evaluation method for an application system according to an embodiment of the present application is shown. The evaluation method for an application system can be applied to an evaluation device for an application system. Figure 4 As shown, the evaluation method of the application system includes:

[0089] Step S801: Determine the application system to be queried;

[0090] Step S802: Display the system evaluation result tree of the application system; wherein the system evaluation result tree includes the node evaluation result of each evaluation node and the topological relationship between each evaluation node; each evaluation node corresponds to each evaluation dimension of the application system one by one.

[0091] Exemplarily, referring to the first embodiment, the system evaluation results of each application system can be stored in the form of a system evaluation result tree. The specific storage data of the system evaluation result tree includes: the name of the evaluation dimension (evaluation node), the measurement object (i.e., the application system to be queried) and version, the node scoring result, the parent node (the root node has no parent node), the version of the system evaluation result, and other key information. Since the root node does not have a parent dimension, the root node in the system evaluation result tree can be queried based on this feature, and then the system evaluation result corresponding to the application system can be queried.

[0092] Furthermore, the system evaluation results can be displayed in a tree-like form, i.e., a system evaluation result tree, in which the scoring results corresponding to each evaluation dimension are displayed according to the corresponding topological relationship, such as Figure 5 As shown, it can intuitively show the global architecture maturity level of the application system and the aspects that need governance and improvement (assessment dimensions or measurement dimensions)

[0093] In one embodiment, the application system corresponds to an evaluation rule tree, which includes evaluation nodes corresponding to multiple evaluation dimensions of the application system and topological relationships between the evaluation nodes, and the node evaluation results of the evaluation nodes are determined based on the node evaluation rules of the evaluation nodes. For details, please refer to Example 1, which will not be repeated here.

[0094] Embodiment 3

[0095] Corresponding to the application scenario provided in the embodiment of the present application and the method of the first embodiment, the embodiment of the present application also provides an evaluation device for an application system. Fig. 9 As shown, the evaluation device of the application system may include: an evaluation rule tree acquisition unit 901, used to obtain an evaluation rule tree of the application system; wherein the evaluation rule tree includes evaluation nodes corresponding to multiple evaluation dimensions of the application system and the topological relationship between each evaluation node; a node evaluation result determination unit 902, used to traverse each evaluation node according to the topological relationship between each evaluation node in the evaluation rule tree, and determine the corresponding node evaluation result according to the node evaluation rule of each evaluation node; a system evaluation result determination unit 903, used to determine the system evaluation result of the application system according to the node evaluation result of at least one evaluation node.

[0096] In one embodiment, the node evaluation result determination unit 902 is specifically used to: traverse each evaluation node according to the topological relationship; in response to the evaluation node being a leaf node, determine the scoring result of the leaf node as the node evaluation result of the leaf node based on the leaf node evaluation rule of the leaf node; wherein the leaf node evaluation rule includes metadata configuration information, metadata conversion rules and scoring rules.

[0097] In one embodiment, the node evaluation result determination unit 902 is specifically used to: call at least one metadata of the application system based on the metadata configuration information; perform data conversion on the at least one metadata according to the metadata conversion rule; and score the data conversion result of the at least one metadata using the scoring rule to obtain the scoring result of the leaf node.

[0098] In one embodiment, the node evaluation result determination unit 902 is specifically used to: traverse each evaluation node according to the topological relationship; in response to the evaluation node being a parent node, based on the scoring results of each child node of the parent node and the weight of each child node in the parent node, determine the scoring result of the parent node as the node evaluation result of the parent node.

[0099] In one implementation, the evaluation node includes a root node, and the system evaluation result determination unit 903 is specifically configured to: use the node evaluation result of the root node as the system evaluation result of the application system.

[0100] In one embodiment, the system evaluation result determination unit 903 is specifically used to: generate a system evaluation result tree of the application system according to the topological relationship between each evaluation node and the node evaluation result of each evaluation node; wherein the system evaluation result tree includes the node evaluation results of each evaluation node and the topological relationship between each evaluation node.

[0101] In one embodiment, the metadata configuration information includes target identification information and target attribute fields, and the node evaluation result determination unit 902 is specifically used to: determine the target metadata storage instance corresponding to the target identification information from multiple metadata storage instances of the application system; call the data corresponding to the target attribute field from the target metadata storage instance to obtain the at least one metadata.

[0102] In one embodiment, the evaluation device of the application system also includes a storage unit, which is specifically used to store various metadata of the application system as a metadata storage instance according to a preset data model; wherein the data model includes identification information, attribute fields, and topological relationships with other metadata storage instances.

[0103] The functions of each module in each device in the embodiments of the present application can be found in the corresponding description in the above method, and have corresponding beneficial effects, which will not be repeated here.

[0104] Embodiment 4

[0105] Corresponding to the application scenario provided in the embodiment of the present application and the method of the second embodiment, the embodiment of the present application also provides an evaluation result query device for an application system. Fig.10 As shown, the evaluation result query device of the application system may include: an application system determination unit 1001, used to determine the application system to be queried; a system evaluation result tree display unit 1002, used to obtain the system evaluation result tree of the application system; wherein, the system evaluation result tree includes the node evaluation results of each evaluation node and the topological relationship between each evaluation node; each evaluation node corresponds one-to-one to each evaluation dimension of the application system.

[0106] In one embodiment, the application system corresponds to an evaluation rule tree, which includes evaluation nodes corresponding to multiple evaluation dimensions of the application system and the topological relationship between the evaluation nodes, and the node evaluation results of the evaluation nodes are determined based on the node evaluation rules of the evaluation nodes.

[0107] The functions of each module in each device in the embodiments of the present application can be found in the corresponding description in the above method, and have corresponding beneficial effects, which will not be repeated here.

[0108] Embodiment 5

[0109] Fig.11 is a block diagram of an electronic device used to implement an embodiment of the present application. Fig.11 As shown, the electronic device includes: a memory 1101 and a processor 1102. The memory 1101 stores a computer program that can be run on the processor 1102. When the processor 1102 executes the computer program, the method in the above embodiment is implemented. The number of the memory 1101 and the processor 1102 can be one or more.

[0110] The electronic device also includes:

[0111] The communication interface 1103 is used to communicate with external devices and perform data exchange transmission.

[0112] If the memory 1101, the processor 1102 and the communication interface 1103 are implemented independently, the memory 1101, the processor 1102 and the communication interface 1103 can be connected to each other through a bus and communicate with each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.11 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0113] Optionally, in a specific implementation, if the memory 1101, the processor 1102 and the communication interface 1103 are integrated on a chip, the memory 1101, the processor 1102 and the communication interface 1103 can communicate with each other through an internal interface.

[0114] An embodiment of the present application provides a computer-readable storage medium storing a computer program, which implements the method provided in the embodiment of the present application when the program is executed by a processor.

[0115] An embodiment of the present application also provides a chip, which includes a processor for calling and executing instructions stored in the memory from the memory, so that a communication device equipped with the chip executes the method provided by the embodiment of the present application.

[0116] An embodiment of the present application also provides a chip, including: an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected via an internal connection path, and the processor is used to execute the code in the memory. When the code is executed, the processor is used to execute the method provided in the embodiment of the application.

[0117] It should be understood that the processor may be a CPU, or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), FPGAs or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor, etc. It is worth noting that the processor may be a processor supporting the Advanced RISC Machines (ARM) architecture.

[0118] Further, optionally, the above-mentioned memory may include a read-only memory and a random access memory. The memory may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory may include a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may include a random access memory (RAM), which is used as an external cache. By way of exemplary but not limiting description, many forms of RAM are available. For example, static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct memory bus random access memory (DR RAM).

[0119] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium.

[0120] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example" or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine different embodiments or examples described in this specification and the features of different embodiments or examples, unless they are contradictory.

[0121] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0122] Any process or method described in the flow chart or otherwise described herein can be understood as a module, fragment or portion of a code representing one or more executable instructions for implementing the steps of a specific logical function or process. And the scope of the preferred embodiment of the present application includes other implementations, in which the functions may not be performed in the order shown or discussed, including in a substantially simultaneous manner or in a reverse order according to the functions involved.

[0123] The logic and / or steps described in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, which can be specifically implemented in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or used in combination with these instruction execution systems, devices or apparatuses.

[0124] It should be understood that the various parts of the present application can be implemented with hardware, software, firmware or a combination thereof. In the above embodiments, multiple steps or methods can be implemented with software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the above embodiment method can be completed by instructing the relevant hardware through a program, which can be stored in a computer-readable storage medium, and when the program is executed, it includes one of the steps of the method embodiment or a combination thereof.

[0125] In addition, each functional unit in each embodiment of the present application can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into one module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of a software functional module. If the above-mentioned integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. The storage medium can be a read-only memory, a disk or an optical disk, etc.

[0126] The above is only an exemplary embodiment of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various changes or substitutions within the technical scope recorded in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A method for evaluating an application system, comprising: Obtaining an evaluation rule tree of the application system; wherein the evaluation rule tree includes evaluation nodes corresponding to multiple evaluation dimensions of the application system and topological relationships between the evaluation nodes; According to the topological relationship between the evaluation nodes in the evaluation rule tree, each evaluation node is traversed, and the corresponding node evaluation results are determined according to the node evaluation rules of each evaluation node; A system evaluation result of the application system is determined according to a node evaluation result of at least one evaluation node.

2. The method according to claim 1, wherein: According to the topological relationship between the evaluation nodes in the evaluation rule tree, each evaluation node is traversed, and the corresponding node evaluation results are determined according to the node evaluation rules of each evaluation node, including: Traversing each evaluation node according to the topological relationship; In response to the evaluation node being a leaf node, based on the leaf node evaluation rule of the leaf node, the scoring result of the leaf node is determined as the node evaluation result of the leaf node; wherein the leaf node evaluation rule includes metadata configuration information, metadata conversion rules and scoring rules.

3. The method according to claim 2, wherein: Based on the leaf node evaluation rule of the leaf node, determining the scoring result of the leaf node as the node evaluation result of the leaf node includes: Based on the metadata configuration information, calling at least one metadata of the application system; According to the metadata conversion rule, performing data conversion on the at least one metadata; The data conversion result of the at least one metadata is scored using the scoring rule to obtain a scoring result of the leaf node.

4. The method according to claim 1, wherein: According to the topological relationship between the evaluation nodes in the evaluation rule tree, each evaluation node is traversed, and the corresponding node evaluation results are determined according to the node evaluation rules of each evaluation node, including: Traversing each evaluation node according to the topological relationship; In response to the evaluation node being a parent node, based on the scoring results of each child node of the parent node and the weight of each child node in the parent node, the scoring result of the parent node is determined as the node evaluation result of the parent node.

5. The method according to any one of claims 1 to 4, wherein: The evaluation node includes a root node, and according to the node evaluation result of at least one evaluation node, a system evaluation result of the application system is determined, including: The node evaluation result of the root node is used as the system evaluation result of the application system.

6. The method according to any one of claims 1 to 4, wherein: Determining a system evaluation result of the application system according to a node evaluation result of at least one evaluation node includes: According to the topological relationship between each evaluation node and the node evaluation result of each evaluation node, a system evaluation result tree of the application system is generated; wherein the system evaluation result tree includes the node evaluation result of each evaluation node and the topological relationship between each evaluation node.

7. The method according to claim 3, wherein: The metadata configuration information includes target identification information and target attribute fields. Based on the metadata configuration information, calling at least one metadata of the application system includes: Determining a target metadata storage instance corresponding to the target identification information from a plurality of metadata storage instances of the application system; The data corresponding to the target attribute field is retrieved from the target metadata storage instance to obtain the at least one metadata.

8. The method according to claim 1 or 7, further comprising: According to a preset data model, each metadata of the application system is stored as a metadata storage instance; wherein the data model includes identification information, attribute fields, and topological relationships with other metadata storage instances.

9. A method for querying evaluation results of an application system, comprising: Determine the application system to be queried; Display the system evaluation result tree of the application system; wherein the system evaluation result tree includes the node evaluation results of each evaluation node and the topological relationship between each evaluation node; each evaluation node corresponds to each evaluation dimension of the application system one by one.

10. The method according to claim 9, wherein: The application system corresponds to an evaluation rule tree, which includes evaluation nodes corresponding to multiple evaluation dimensions of the application system and topological relationships between the evaluation nodes. The node evaluation results of the evaluation nodes are determined based on the node evaluation rules of the evaluation nodes.

11. An evaluation device for an application system, comprising: An evaluation rule tree acquisition unit, used to acquire an evaluation rule tree of an application system; wherein the evaluation rule tree includes evaluation nodes corresponding to a plurality of evaluation dimensions of the application system and a topological relationship between the evaluation nodes; A node evaluation result determination unit, used to traverse each evaluation node according to the topological relationship between each evaluation node in the evaluation rule tree, and determine the corresponding node evaluation result according to the node evaluation rule of each evaluation node; The system evaluation result determining unit is used to determine the system evaluation result of the application system according to the node evaluation result of at least one evaluation node.

12. An evaluation result query device for an application system, comprising: An application system determination unit, used to determine the application system to be queried; The system evaluation result tree display unit is used to display the system evaluation result tree of the application system; wherein the system evaluation result tree includes the node evaluation results of each evaluation node and the topological relationship between each evaluation node; each evaluation node corresponds one-to-one to each evaluation dimension of the application system.

13. An electronic device comprising a memory, a processor and a computer program stored in the memory, wherein the processor implements the method according to any one of claims 1 to 10 when executing the computer program.

14. A computer-readable storage medium, wherein a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the method according to any one of claims 1 to 10 is implemented.

Images