Software asset visualization method and device and nonvolatile storage medium

Abstract

The invention discloses a software asset visualization method and device and a nonvolatile storage medium. The method comprises the following steps: collecting a plurality of different types of target information related to software assets; performing three-dimensional display on different types of target information in different areas of the target interface; and obtaining log data of the application program interface corresponding to each software asset in the capability open platform, extracting calling information among the software assets from the log data, constructing a knowledge graph according to the software assets and the calling information among the software assets, and displaying the knowledge graph. According to the method and the device, the technical problem that complicated software asset information is difficult to intuitively display and efficiently manage in related technologies is solved.

Description

Technical Field

[0001] The present application relates to the field of software asset management, and more specifically, to a method and device for visualizing software assets, and a non-volatile storage medium. Background Art

[0002] With the accelerated development of enterprise digital transformation, software assets have become one of the most important assets of enterprises. However, many enterprises do not realize the importance of software asset management, resulting in the inability to fully realize the value of software assets. This paper will explore the importance of software asset management and how to effectively manage software assets through digital visualization methods, and further promote the maximization of software asset value.

[0003] Asset visualization is to collect, process and display information such as the location, status and usage of assets in real time through information technology, so that managers can clearly understand the status of assets, allocate and manage assets in a timely manner, improve the efficiency and accuracy of asset management, reduce costs and enhance the competitiveness of enterprises. Compared with tangible asset management, the management and visualization of intangible assets such as software systems are more difficult:

[0004] Software assets have no physical form and are highly specialized and complex. Their definition and identification require professional knowledge and skills to ensure that assets can be correctly classified and measured. The amount of data involved in software assets is large and diverse, including multiple dimensions such as technological innovation, market potential, user experience, and capability output. The collection, processing, and analysis of these data require highly specialized technical and tool support, and there is also the problem of difficulty in obtaining data. In the asset visualization process, the display of software assets is not intuitive, and different departments and perspectives (such as marketing, finance, IT operations, security, etc.) focus on different points, making coordination difficult.

[0005] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0006] The present application provides a method and device for visualizing software assets, and a non-volatile storage medium, so as to at least solve the technical problem that related technologies are difficult to intuitively display and efficiently manage complex software asset information.

[0007] According to one aspect of the present application, a method for visualizing software assets is provided, including: collecting multiple different types of target information related to software assets, wherein the target information includes at least two of the following: attribute information, construction project information, architecture information, user group information, function information, capability exposure information, cloud resource information, data asset information, indicator information, and technological innovation information of the software assets; performing three-dimensional display of different types of target information in different areas of a target interface; obtaining log data of an application program interface corresponding to each software asset in a capability exposure platform, extracting call information between software assets from the log data, constructing a knowledge graph based on the software assets and the call information between software assets, and displaying the knowledge graph.

[0008] Optionally, the attribute information of the software asset includes at least one of the following: identification information of the software asset, coding information of the software asset, construction time information of the software asset, classification information of the software asset, associated object information of the software asset, and investment model information of the software asset; the construction project information includes at least one of the following: identification information of the construction project, identification information of the work breakdown structure WBS of the construction project, investment amount information, construction time information, issuance time information, closing time information, project status information, and engineering management object information of the construction project; the architecture information includes at least one of the following: business architecture diagram, functional architecture diagram, data architecture diagram, network architecture diagram, and system architecture diagram; the user group information includes at least one of the following: user role information, user quantity information, quantity information of active users within a preset time period, and ranking information of the quantity information of active users within a preset time period; the software asset function information includes at least one of the following: identification information of the function module in the software asset, coding information of the function module, level information of the function module, description information of the function module, attribute information of the function module, question information of the function module The information on capability exposure includes at least one of the following: identification information of the capabilities provided and called by the software assets, coding information of the capabilities, provision information of the capabilities, calling information of the capabilities, provision object information of the capabilities, calling object information of the capabilities, access method information of the capabilities, calling volume information of the capabilities, called volume information of the capabilities, and online time information of the capabilities; the information on cloud resources includes at least one of the following: resource deployment diagram, resource name information, resource type information, resource identification information, resource usage information, and resource utilization rate information; the information on data assets includes at least one of the following: data asset directory information, data asset coding information, data asset format information, data asset storage cycle information, and data asset confidentiality level information; the information on indicators includes at least one of the following: indicator name information, indicator coding information, indicator data caliber information, indicator value information, and indicator statistical time information; the information on technological innovation includes at least one of the following: promotion income information, patent information, paper publication information, enterprise or industry standard information, and innovation award information.

[0009] Optionally, multiple different types of target information related to software assets are collected, including: responding to a first preset instruction to call a first preset interface, accessing the engineering construction system through the first preset interface, and collecting construction project information in the engineering construction system; responding to a second preset instruction to call a second preset interface, accessing the log center system through the second preset interface, and collecting software asset function information in the accessed log center system; responding to a third preset instruction to call a third preset interface, accessing the data governance center through the third preset interface, and collecting data asset information in the data governance center; responding to a fourth preset instruction to call a fourth preset interface, accessing the docking capability opening platform through the fourth preset interface, and collecting capability opening information in the docking capability opening platform; responding to a fifth preset instruction to call a fifth preset interface, accessing the cloud management platform through the fifth preset interface, and collecting cloud resource information in the cloud management platform.

[0010] Optionally, different types of target information are displayed in three dimensions in different areas of the target interface, including: displaying multiple first-level menus in a first preset area in the target interface, and displaying the number of second-level menus included in each first-level menu, wherein the first-level menu at least includes: attribute information of software assets, and the second-level menu at least includes: construction project information, architecture information, and user group information; in response to a click operation on the first-level menu, jumping to a second-level menu list, wherein the second-level menu list includes multiple second-level menus, and each second-level menu displays the user of the second-level menu and the number of visits within a preset time period; displaying first-level function modules and second-level function modules in a second preset area in the target interface, and displaying the function introduction of the first-level function module in response to a click operation on the first-level function module. The first-level function module at least includes: attribute information of the software asset; the second-level function module at least includes: construction project information, architecture information, and user group information; the target number of capabilities provided and called by the software asset is displayed in the third preset area in the target interface, and in response to a click operation on the target number, the capability exposure information of each capability is displayed; the indicator information of the software asset is displayed in the fourth preset area in the target interface, and in response to a click operation on the target indicator, the indicator information corresponding to the target indicator is displayed; the data asset information is displayed in the fifth preset area in the target interface; and the cloud resource information is displayed in the sixth preset area in the target interface.

[0011] Optionally, call information between software assets is extracted from the log data, and a knowledge graph is constructed based on the software assets and the call information between software assets, and the knowledge graph is displayed, including: performing data cleaning on the log data to remove invalid data and duplicate data, analyzing the log data after the data cleaning process, and extracting call information between software assets, wherein the call information includes: call direction, call type, name of the call interface, and call volume, and the call direction includes: calling and being called; using software assets as nodes and call information as edges to construct a knowledge graph; converting the node and edge data in the knowledge graph into a target format readable by a visualization tool, and using the visualization tool to display the knowledge graph.

[0012] Optionally, the method also includes: dividing the target information according to multiple preset dimensions to obtain multiple division results, wherein the multiple preset dimensions include at least two of the following: the total amount of software assets, the life cycle of software assets, the number of software assets under different business categories, the ranking of software assets by user activity rate, the ranking of software assets by annual investment amount, and the ranking of software assets by value assessment. The life cycle of software assets includes: planning period, construction period, maturity period, evolution period, and offline period; and using a preset dashboard to display the multiple division results.

[0013] Optionally, after collecting a plurality of different types of target information related to software assets, the method further includes: receiving asset coding information of the software assets, receiving labels of the software assets input by different target objects; and classifying the target information according to different classification rules.

[0014] According to another aspect of the present application, a software asset visualization device is also provided, including: a collection module for collecting multiple different types of target information related to software assets, wherein the target information includes at least two of the following: attribute information, construction project information, architecture information, user group information, function information, capability exposure information, cloud resource information, data asset information, indicator information, and technological innovation information of the software assets; a first display module for three-dimensionally displaying different types of target information in different areas of the target interface; a second display module for obtaining log data of the application program interface corresponding to each software asset in the capability exposure platform, extracting call information between software assets in the log data, constructing a knowledge graph based on the software assets and the call information between software assets, and displaying the knowledge graph.

[0015] According to another aspect of the present application, a non-volatile storage medium is provided, the storage medium including a stored program, wherein when the program is run, the device where the storage medium is located is controlled to execute the above software asset visualization method.

[0016] According to another aspect of the present application, an electronic device is provided, including: a memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the above method for visualizing software assets is executed when the program is run.

[0017] According to yet another aspect of the present application, a computer program is provided, wherein when the computer program is executed by a processor, the above method for visualizing software assets is implemented.

[0018] According to another aspect of the present application, a computer program product is provided, which includes a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the above method for visualizing software assets is implemented.

[0019] In the present application, a plurality of different types of target information related to software assets are collected, wherein the target information includes at least two of the following: attribute information, construction project information, architecture information, user group information, function information, capability exposure information, cloud resource information, data asset information, indicator information, and technological innovation information of the software assets; different types of target information are displayed in three dimensions in different areas of the target interface; log data of the application program interface corresponding to each software asset is obtained in the capability exposure platform, call information between software assets is extracted from the log data, and a knowledge graph is constructed according to the software assets and the call information between software assets, and the knowledge graph is displayed in a manner to achieve the purpose of intuitively displaying and efficiently managing software asset information, thereby realizing the technical effect of improving the utilization rate of software assets, and further solving the technical problem that related technologies are difficult to intuitively display and efficiently manage complex software asset information. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0021] Figure 1 is a flow chart of a method for visualizing software assets according to an embodiment of the present application;

[0022] Figure 2 is a user view of a software asset according to an embodiment of the present application;

[0023] Figure 3 It is a software asset relationship diagram constructed using a knowledge graph according to an embodiment of the present application;

[0024] Figure 4 is a structural diagram of a software asset visualization device according to an embodiment of the present application;

[0025] Figure 5 It is a hardware structure block diagram of a computer terminal according to a method for visualizing software assets in an embodiment of the present application. DETAILED DESCRIPTION

[0026] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0027] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0028] According to an embodiment of the present application, a method embodiment of a method for visualizing software assets is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0029] Figure 1 is a flowchart of a method for visualizing software assets according to an embodiment of the present application, such as Figure 1 As shown, the method comprises the following steps:

[0030] Step S102, collecting multiple different types of target information related to software assets, wherein the target information includes at least two of the following: attribute information of software assets, construction project information, architecture information, user group information, function information, capability exposure information, cloud resource information, data asset information, indicator information, and technology innovation information.

[0031] Specifically, the software asset management model automatically or semi-automatically collects information from multiple dimensions, collects and sorts out the software system asset information, performs asset inventory, and connects to engineering construction systems, log systems, capability exposure platforms, big data lakes and other data sources to obtain the following information: basic software information, construction project information, architecture information, user group information, function information, capability exposure information, cloud resource information, data asset information, core indicator information, and technological innovation information.

[0032] Among them, the attribute information of software assets is collected through the software asset management platform or manually input, and the basic information of each software asset is collected, including but not limited to the software name, unique number, key stakeholders (such as business manager, system manager, operation and maintenance manager, developer), etc. The construction project information is automatically captured by connecting to the enterprise's engineering management system, including but not limited to the project name, WBS number, investment amount, construction year, issuance and closing time, project status, etc. The architecture information uses IT architecture tools or manual drawing to collect the business architecture, functional architecture, data architecture, network architecture, system architecture and other information of the software system, and displays the software architecture in a graphical way. User group information obtains the main user group information of the software through the software usage log or user management system, including but not limited to user roles, number of users, monthly active number and its ranking. Functional information extracts the usage of functional modules from the software's log center system, including but not limited to function introduction, operation instructions, usage, etc. The capability exposure information obtains the software capability exposure and call information by connecting to the enterprise's capability exposure platform, including but not limited to capability name, coding, access method, call volume, etc. Cloud resource information collects cloud resource information required for software operation through the cloud management platform, such as the usage and utilization of operating systems, containers, middleware, databases, servers, etc. Data asset information obtains data asset information generated during software operation from the data governance center, including but not limited to data format, storage cycle, confidentiality level, etc. Indicator information is used to evaluate the value of software and collect core indicator information of software, such as service quality, efficiency improvement, business support capabilities, etc. Technological innovation information is collected from internal or external systems of the enterprise, including but not limited to software invention patents, paper publications, enterprise / industry standards, innovation awards and other information.

[0033] Step S104: three-dimensionally display different types of target information in different areas of the target interface.

[0034] Specifically, the collected software asset information is displayed in three dimensions on the target interface using three-dimensional modeling technology to enhance the intuitiveness and comprehensibility of the information. The software is given a unique software asset code and included in the software asset list for unified management. The software is classified according to the software asset catalog, and the software assets are labeled with public tags based on business needs and management requirements, and user tags are labeled based on the user's personal preferences.

[0035] To achieve the above steps, the three-dimensional display platform is used to ensure that different types of software asset information can be carried, and different display areas are set according to different display requirements (such as user view, manager view). Among them, the entry layer information of the software assets, such as the software name, the number of first-level menus and second-level menus, is displayed in the central area of ​​the three-dimensional view. Users can click to enter more detailed functional module information. The functional architecture and capability exposure information of the software are displayed in a certain area of ​​the three-dimensional view, and the functional modules and capability call relationships are displayed through intuitive icons and links. The core indicators, data assets and cloud resource usage are displayed in other areas of the three-dimensional view, and dynamic dashboards or charts are used to represent the real-time status of various indicators and resources.

[0036] Step S106, obtaining the log data of the application program interface corresponding to each software asset in the capability opening platform, extracting the call information between software assets in the log data, constructing a knowledge graph based on the software assets and the call information between software assets, and displaying the knowledge graph.

[0037] Specifically, data mining algorithms are used to extract call information between software assets from log data, including which software calls which capabilities, call frequency, etc. The extracted call information is constructed into a node relationship graph using a knowledge graph construction tool, with each software asset and capability exposure information as a node and the call relationship as an edge, to form an intuitive software asset relationship graph. On the software asset visualization interface, a separate area is set up to display the knowledge graph of software assets, which graphically displays the interconnected relationships between software assets.

[0038] According to the above steps, in the present application, multiple different types of target information related to software assets are collected, wherein the target information includes at least two of the following: attribute information, construction project information, architecture information, user group information, function information, capability exposure information, cloud resource information, data asset information, indicator information, and technological innovation information of the software assets; different types of target information are displayed in three dimensions in different areas of the target interface; log data of the application program interface corresponding to each software asset is obtained in the capability exposure platform, call information between software assets is extracted from the log data, and a knowledge graph is constructed according to the software assets and the call information between software assets, and the knowledge graph is displayed in a manner to achieve the purpose of intuitively displaying and efficiently managing software asset information, thereby realizing the technical effect of improving the utilization rate of software assets.

[0039] The following Figure 1 The steps shown are exemplary and explanatory.

[0040] According to some optional embodiments of the present application, the attribute information of the software asset includes at least one of the following: identification information of the software asset, coding information of the software asset, construction time information of the software asset, classification information of the software asset, associated object information of the software asset, and investment model information of the software asset; the construction project information includes at least one of the following: identification information of the construction project, identification information of the work breakdown structure WBS of the construction project, investment amount information, construction time information, issuance time information, closing time information, project status information, and engineering management object information of the construction project; the architecture information includes at least one of the following: business architecture diagram, functional architecture diagram, data architecture diagram, network architecture diagram, and system architecture diagram; the user group information includes at least one of the following: user role information, user quantity information, quantity information of active users within a preset time length, and ranking information of the quantity information of active users within a preset time length; the software asset function information includes at least one of the following: identification information of the function module in the software asset, coding information of the function module, level information of the function module, description information of the function module, attribute information of the function module, Question and answer information of functional modules, operation guidance information of functional modules, and information on the number of users using functional modules; capability exposure information includes at least one of the following: identification information of capabilities provided and called by software assets, coding information of capabilities, provision information of capabilities, calling information of capabilities, provision object information of capabilities, calling object information of capabilities, access method information of capabilities, calling volume information of capabilities, called volume information of capabilities, and online time information of capabilities; cloud resource information includes at least one of the following: resource deployment diagram, resource name information, resource type information, resource identification information, resource usage information, and resource utilization information; data asset information includes at least one of the following: data asset directory information, data asset coding information, data asset format information, data asset storage cycle information, and data asset confidentiality level information; indicator information includes at least one of the following: indicator name information, indicator coding information, indicator data caliber information, indicator value information, and indicator statistical time information; technological innovation information includes at least one of the following: promotion income information, patent information, paper publication information, enterprise or industry standard information, and innovation award information.

[0041] In the above embodiment, by investigating and analyzing the entire life cycle of various software assets from planning, construction, operation and maintenance to offline, it is found that the main elements of software assets include basic asset information, construction project information, architecture information, user group information, function information, capability exposure information, cloud resource information, data asset information, core indicator information, and technology innovation information, and a software asset management model is formulated. As shown in Table 1, it specifically includes the following 10 dimensions:

[0042] Table 1

[0043]

[0044] Among them, the basic information of software assets is used to distinguish different software product information, mainly including software name, software unique number, key stakeholders (business manager, system manager, operation and maintenance manager, developer). As shown in Table 2:

[0045] Table 2

[0046]

[0047] For example, the specific software asset information is:

[0048] Software Asset Name CRM System Software asset unique code IT-BSS-001 Software asset construction time 2018 Professional classification Business Operations Investment Model capital

[0049] The construction project information is the software construction projects over the years, which is used to understand the software investment and value estimation, including the construction project name, construction project WBS number, investment amount, construction year, issuance time, closing time, and project status, as shown in Table 3:

[0050] Table 3

[0051] Secondary indicators Secondary indicator description Construction project name Display the history of software projects or the names of ongoing projects Construction Project WBS Number Display the WBS number of the software project history or the project in progress Investment Amount Display the history of software projects or the current investment amount of projects under construction Construction Year Display the history of software projects or the current project construction year of the projects under construction Release time Display the software project history or the current project release time of the project under construction Closing time Display the history of software projects or the closing time of current projects under construction Project Status Display the project status of software project history or current projects under construction Construction project manager Show the history of software projects or current project managers of ongoing projects

[0052] For example, the information of a specific construction project is:

[0053] WBS Number Construction project name Construction Year Investment Amount Project Status GC001 2021 CRM Project 2021 XX million Closed GC002 2022 CRM Project 2022 XX million Acceptance GC003 2023 CRM Project 2023 XX million Completed GC004 2024 CRM Project 2024 XX million Completed

[0054] Architectural information refers to the business architecture, functional architecture, data architecture, network architecture, system architecture and other architectural information of the software system. It shows the structure and composition of the software system from different perspectives, helping users, developers and project managers to better understand and design the software system, as shown in Table 4:

[0055] Secondary indicators Secondary indicator description Business architecture diagram Demonstrate the business processes, key activities and business requirements implemented by the software system Functional architecture diagram Demonstrate the functional system of the software system and the relationship between modules, including the planning of existing functions and future functions Data architecture diagram Show the flow of data in the software system, storage location, and the relationship between data to facilitate data management and governance Network architecture diagram Demonstrate the physical relationship between the hardware components required by the software system and the distribution of components on the processing nodes System architecture diagram Present a high-level view of the software system, including interactions between systems and interfaces with external systems

[0056] User group information is the main user group of the software, including user roles, number of users, and monthly active users. It is ranked according to the number of active users to help project managers better understand the user group activity rate of the software system, as shown in Table 5:

[0057] Table 5

[0058] Secondary indicators Secondary indicator description Role Name Describe the main role types and names of the software Number of users Describe the number of registered users of the software system (the more users there are, the more valuable the system is) Monthly active users Describe the recent number of monthly active users of the software system Daily active users Describe the recent number of daily active users of the software system Daily Ranking Display software system ranking by daily active users Monthly Ranking Display software systems ranking by number of monthly active users

[0059] For example, the information of a specific user group is:

[0060] Role Name Salesperson Number of users 3236 Monthly active users 2564 Daily active users 2130 Daily Ranking 1

[0061] Functional information includes the software's functional introduction, functional features, operation guide information, usage, including usage records, satisfaction, etc. It is crucial for users to understand the software's functions, usage methods, and usage, as shown in Table 6:

[0062] Table 6

[0063]

[0064] For example, a specific function information is:

[0065] Function module number Function module name Number of users IT-BSS-001-001 Customer Inquiry 2134 IT-BSS-001-002 Business acceptance 1201 IT-BSS-001-003 Fee Inquiry 1657 IT-BSS-001-004 Shopping cart query 2346

[0066] Capability exposure information refers to the capability exposure and capability call information of the software, including capability code, capability information, capability access method, capability call / access volume, which helps users understand the peripheral relationship of the software system and helps project managers evaluate the openness of the software system and the external call effect, as shown in Table 7:

[0067] Table 7

[0068] Secondary indicators Secondary indicator description Capability Name The capability name registered or used by the software system comes from the capability opening platform Capability Coding The capability code registered or used by the software system comes from the capability opening platform Capability provision or call The software system uses this capability to provide or call Capability Provider The software system uses the provider of this capability Capability Caller The software system uses the caller of this capability Capability access method The software system uses the access methods of this capability, including https, H5, SDK, OpenAPI, etc. Capacity call volume The number of calls that the software system uses this capability Capacity Called The software system outputs the number of calls to this capability. Capability launch time The registration or call start time of the software system comes from the capability opening platform

[0069] Cloud resource information is used to describe the cloud computing environment required to run the software system, mainly including the usage and utilization of various cloud resources such as operating system, container / virtual machine / physical machine, middleware, and database, as shown in Table 8:

[0070] Table 8

[0071] Data asset information is used to describe the data generated by the software during the operation process that has core value and can be stored, managed and analyzed, such as customer information, order information, network element information, equipment information, etc., as shown in Table 9:

[0072] Table 9

[0073] Secondary indicators Secondary indicator description Data asset catalog Display the catalog category to which the data asset belongs Data asset encoding Display the data asset code Data asset format Display the data format of the data asset, including: structured, non-structured (text, image, file), etc. Data asset storage cycle Display the storage period of the data asset Data asset confidentiality level Display the confidentiality level of the data asset, which is divided into: public information, internal information, important information, and core information

[0074] The core indicator information is used to reflect the core value of the software, usually including service quality and efficiency improvement, economic benefit improvement, business support capability improvement, system processing capability improvement, etc. According to the different characteristics of the software system, different characteristic capability indicators are selected / set, as shown in Table 10:

[0075] Table 10

[0076]

[0077] Technological innovation information includes the technological innovation-related content generated by the software, including external promotion effects, invention patents, enterprise / industry standards, innovation awards, etc., as shown in Table 11:

[0078] Table 11

[0079] Secondary indicators Secondary indicator description External promotion effect Display the number of external promotion cases of the software asset and the revenue brought by the promotion Invention Patent Demonstrate the invention patent of the software asset Paper publication Paper publications showcasing the software asset Enterprise / Industry Standards Demonstrate corporate / industry standards for the software asset Innovation Awards Showcase the innovation awards the software asset has received

[0080] By constructing the above-mentioned software asset management model, specific definition standards and unified management requirements and suggestions are provided for software asset management. In the process of software asset visualization and value assessment, appropriate adjustments can be made based on the model according to the actual situation of each software system to meet the expansion and extension of future technical and business needs.

[0081] According to other optional embodiments of the present application, collecting various different types of target information related to software assets can be achieved by the following methods: responding to a first preset instruction to call a first preset interface, accessing the engineering construction system through the first preset interface, and collecting construction project information in the engineering construction system; responding to a second preset instruction to call a second preset interface, accessing the log center system through the second preset interface, and collecting software asset function information in the accessed log center system; responding to a third preset instruction to call a third preset interface, accessing the data governance center through the third preset interface, and collecting data asset information in the data governance center; responding to a fourth preset instruction to call a fourth preset interface, accessing the docking capability opening platform through the fourth preset interface, and collecting capability opening information in the docking capability opening platform; responding to a fifth preset instruction to call a fifth preset interface, accessing the cloud management platform through the fifth preset interface, and collecting cloud resource information in the cloud management platform.

[0082] Specifically, when the first preset instruction is received, the system communicates with the engineering construction system through the first preset interface, which is a pre-defined data exchange channel for obtaining construction project information. After the interface is called, the engineering construction system returns the construction project information related to the software asset, including project name, WBS number, investment amount, construction year, issuance and closing time, project status, etc. The system parses and stores the received information to ensure the accuracy and completeness of the data for subsequent management and analysis.

[0083] When the second preset instruction is received, the system is connected to the log center system through the second preset interface, and a request is first sent to the log center system to obtain the real-time and historical log data of the software assets, including the access records and usage of the functional modules. The log center system then responds to the request and returns the relevant functional usage data through the second preset interface. The received functional data is analyzed and sorted, and key indicators such as the frequency of use of the functional modules and user satisfaction are extracted to provide a basis for standardized management and optimization of functions.

[0084] When the third preset instruction is received, the third preset interface is called to send a request to the data governance center to obtain information such as the data structure, storage location, and data volume of the software asset. After receiving the request, the data governance center returns specific information about the data asset through the interface, including the format, storage period, and confidentiality level of the data. The returned data is processed and integrated into the software asset management model to form a complete description of the software data asset.

[0085] When the fourth preset instruction is received, the capability opening platform is interacted with by calling the fourth preset interface, and a request is sent to the capability opening platform to request the capability information of the software asset registered or called through the platform, including the capability name, code, provider / caller, access method, call amount, etc. The capability opening platform responds to the request and returns all capability information related to the software asset through the fourth preset interface. The received capability data is processed to generate a capability call relationship diagram, which is convenient for subsequent visualization analysis of the interconnection between software assets.

[0086] After receiving the fifth preset instruction, a request is sent to the cloud management platform through the fifth preset interface to obtain the cloud resource usage of the software asset, such as the usage and utilization of the operating system, container, middleware, database, etc. The cloud management platform responds to the request and returns the cloud resource details of the software asset through the interface, including resource name, type, usage, utilization, etc. The cloud resource data is received and processed, and integrated into the software asset management model to form a comprehensive view of the software asset cloud resource usage.

[0087] Through the above specific implementation methods, various key information of software assets can be automatically collected from multiple external systems according to preset instructions, providing a solid foundation for subsequent software asset management, visualization and value assessment. This not only improves the efficiency of information collection, but also ensures the accuracy and real-time nature of data, providing strong support for the effective management of software assets and corporate decision-making.

[0088] In some optional embodiments of the present application, three-dimensional display of different types of target information in different areas of the target interface can be achieved by the following method: display multiple first-level menus in a first preset area in the target interface, and display the number of second-level menus included in each first-level menu, wherein the first-level menu at least includes: attribute information of software assets, and the second-level menu at least includes: construction project information, architecture information, and user group information; in response to a click operation on the first-level menu, jump to the second-level menu list, wherein the second-level menu list includes multiple second-level menus, and each second-level menu displays the user of the second-level menu and the number of visits within a preset time period; display the first-level function module and the second-level function module in the second preset area in the target interface, and display the first-level function module in response to a click operation on the first-level function module. The function introduction information and operation guide information in the function module are displayed in response to a click operation on the secondary function module, wherein the primary function module at least includes: attribute information of the software asset; the secondary function module at least includes: construction project information, architecture information, and user group information; the target number of capabilities provided and called by the software asset is displayed in the third preset area within the target interface, and in response to a click operation on the target number, the capability exposure information of each capability is displayed; the indicator information of the software asset is displayed in the fourth preset area within the target interface, and in response to a click operation on the target indicator, the indicator information corresponding to the target indicator is displayed; the data asset information is displayed in the fifth preset area within the target interface; and the cloud resource information is displayed in the sixth preset area within the target interface.

[0089] In the above embodiment, multiple first-level menus are displayed in the first preset area (e.g., the top of the page or the navigation bar) of the target interface (e.g., the homepage of the software asset management platform), and each menu represents a basic attribute classification of a software asset, such as "software assets", "construction projects", "architecture information", "user groups", etc. Under each first-level menu, the number of second-level menus included is displayed by a small icon or a number. For example, "9" is displayed under the "software assets" menu to indicate that there are 9 second-level menus. When the user clicks on a first-level menu, the system will jump to the corresponding second-level menu list page, which lists all the second-level menus. Each menu is followed by the user (e.g., business manager, system administrator, etc.) and the number of visits within a preset time period (e.g., "daily visits", "monthly visits").

[0090] The second preset area of ​​the target interface (such as the middle of the page) displays the first-level functional modules, such as "property information of software assets", and the next-level second-level functional modules, such as "construction project information", "architecture information", and "user group information". Among them, the first-level functional modules are used for overview. When the user clicks on the first-level functional module, the system displays the function introduction and operation instructions under the module, such as the definition, management process, scope of use and other information of software assets. When the user clicks on the second-level functional module, the system displays more detailed function introduction and operation instructions, such as the project background, goals, stage results, etc. of the construction project information, or the specific architecture diagram and design documents of the architecture information.

[0091] The total number of capabilities provided and called by the software asset is displayed in the third preset area of ​​the target interface (such as the sidebar of the page). For example, the number "9" indicates that there are 9 capabilities provided or called. When the user clicks on the number, the system will jump to the capability exposure information page to display the specific information of each capability, including capability name, code, provision / calling method, call volume, online time, etc.

[0092] The fourth preset area of ​​the target interface displays the core indicator information of software assets, such as "service quality and efficiency improvement", "social and economic benefit improvement" and other indicators. When the user clicks on an indicator, the system displays a detailed description of the indicator, including the indicator name, code, data caliber, current value and statistical time.

[0093] The fifth preset area is used to display key information such as the data asset directory, data format, storage period, confidentiality level, etc. of the software assets. Users can view a detailed description of each data asset, such as the source, purpose, and processing method of the data.

[0094] The sixth preset area is used to display the cloud resources required by software assets, such as the usage and utilization of operating systems, containers, middleware, and databases. Users can view the real-time status of cloud resources, including the usage of CPU, memory, hard disk and other resources.

[0095] Through the above specific implementation methods, the software asset management platform can provide users with intuitive and comprehensive software asset information. Whether it is the overall overview of software assets or the usage details of specific functions, capabilities and resources, users can obtain detailed information through simple clicks, which greatly improves the efficiency and transparency of software asset management.

[0096] As some optional embodiments of the present application, extracting call information between software assets in log data, constructing a knowledge graph based on software assets and the call information between software assets, and displaying the knowledge graph can be achieved by the following method: performing data cleaning processing on the log data to remove invalid data and duplicate data, analyzing the log data after the data cleaning processing, extracting call information between software assets, wherein the call information includes: call direction, call type, name of the call interface and call amount, and the call direction includes: calling and being called; using software assets as nodes and call information as edges to construct a knowledge graph; converting the node and edge data in the knowledge graph into a target format readable by a visualization tool, and using the visualization tool to display the knowledge graph.

[0097] In the above embodiment, the data processing module pre-processes the log data, including removing invalid data in the log, such as those records that are not related to software asset calls, and identifying and deleting duplicate data to ensure the accuracy of subsequent analysis. The cleaning process also includes repairing or deleting format errors, missing value processing, and standardizing data formats to ensure the consistency and integrity of all log data. The cleaned log data is then sent to the data analysis module, where the analysis module identifies the direction of each call (whether it is calling or being called), the type of call (such as API call, data request, etc.), the name of the calling interface, and the amount of calls within a certain time range. Then use data mining algorithms, including statistical analysis, pattern recognition, association rule learning, etc., to deeply understand the interactive relationship between software assets.

[0098] According to the call information extracted in the above steps, the data analysis module identifies the software assets as nodes in the graph, and the call information is used as the edge between the nodes to construct a knowledge graph. Among them, each node will contain the unique identification and basic information of the software asset, and the edge will be associated with the call direction, call type, name of the call interface, and call volume. The constructed knowledge graph data needs to be converted into a format that can be read and parsed by visualization tools, such as JSON, XML, or a specific graph description language. After the data is converted, the knowledge graph is displayed using visualization tools (such as D3.js, Gephi, or specialized graph visualization software). When visualizing, nodes and edges will be presented as graphic elements, and users can explore the relationship between software assets through an interactive interface, such as zooming in, zooming out, highlighting nodes, and other operations to more intuitively understand the call network of software assets.

[0099] Through the above steps, the software asset visualization method of this application can automatically mine and construct the call relationship map between software assets from the log data of the capability opening platform, providing a clear perspective for software asset managers to understand how software assets interact with each other in actual operation, thereby conducting more effective IT governance and resource optimization. The display of the knowledge map not only enhances the intuitiveness of the information, but also provides a tool for analyzing the software asset call pattern, which helps to identify key software assets and potential optimization points.

[0100] In some optional embodiments of the present application, the following steps are also included: dividing the target information according to multiple preset dimensions to obtain multiple division results, wherein the multiple preset dimensions include at least two of the following: the total amount of software assets, the life cycle of software assets, the number of software assets under different business categories, the ranking of software assets by user activity rate, the ranking of software assets by annual investment amount, and the ranking of software assets by value assessment. The life cycle of software assets includes: planning period, construction period, maturity period, evolution period, and offline period; and using a preset dashboard to display the multiple division results.

[0101] Specifically, first, the overall information of software assets is divided according to multiple preset dimensions to generate analysis results under different dimensions. For example, all software assets are classified according to their life cycle stages (planning period, construction period, maturity period, evolution period, and offline period) to obtain the number of software assets in each stage. Similarly, software assets can be divided according to business categories (such as business operation, management support, IT operation, big data AI), and the number of software assets under different business categories can be counted. It is also possible to analyze the user activity of software assets, rank them according to the monthly active number or daily active number, and identify the most popular or most active software assets. For the annual investment amount of software assets, analyze its investment scale and sort it to identify the software assets with the most or least resource investment. Finally, based on the value assessment of software assets, such as technological innovation, business contribution, user experience and other dimensions, the software assets are comprehensively ranked.

[0102] Then use the preset dashboard to display the analysis results. One or more preset dashboards can be developed or configured to intuitively display the results of multiple dimensions of software asset management. Each dashboard can be designed for one or more dimensions. In the dashboard, use charts, lists, progress bars and other forms to display the total amount of software assets, the distribution of software assets in each life cycle stage, the number of software assets under different business categories, the ranking of active users, the ranking of investment amounts, the ranking of value assessments and other information. For example, a pie chart can be used to display the distribution ratio of software assets in each life cycle stage, a bar chart or bar chart can be used to display the number of software assets under different business categories, and a scatter plot or heat map can be used to intuitively display the ranking of software assets by user activity rate. In addition, the data in the dashboard should be updated in real time to ensure that managers can obtain the latest software asset management status. The dashboard provides interactive functions, allowing managers to view specific software asset information under a certain dimension in more detail by clicking, dragging and other operations. For example, clicking the pie chart area of ​​the "Construction Period" stage can jump to the list page of all software assets in that stage.

[0103] Through the above specific implementation methods, the present application can provide managers with a comprehensive and intuitive software asset management view, making the distribution, status, value and other information of software assets clear at a glance, which helps enterprises make more effective software asset management decisions and optimizations.

[0104] As other optional embodiments of the present application, after collecting various types of target information related to software assets, it can also be implemented by the following methods: receiving asset coding information of software assets, receiving labels of software assets input by different target objects; and classifying and processing the target information according to different classification rules.

[0105] Specifically, a special receiving module is designed to collect asset coding information of software assets. The coding information is automatically assigned by the software asset management system, or manually entered by the administrator when the software asset is entered. The receiving module can be a form interface that requires the user to enter the software asset code, or an API interface that allows an external system or script to automatically submit the coding information. The coding information of each software asset will be stored in a database as the basic data for subsequent classification and management.

[0106] An easy-to-use tag input function is also provided, allowing different target objects (such as business users, system administrators, developers, etc.) to add tags to software assets. Tag input can be achieved through a searchable drop-down menu, which is pre-filled with public tags and allows users to customize their own user tags. The received tag information is also recorded in the database and associated with the software asset's encoding information for subsequent classification and query.

[0107] A flexible classification rule engine can also be provided, which can automatically classify software assets according to preset classification rules. Classification rules can be based on different dimensions, such as business classification, frequency of use, investment model, etc. Specifically, for business classification, the system can automatically classify software assets into "business operation category", "management support category", "IT operation category", "big data AI category", etc. according to their business purposes. For frequency of use, software assets can be divided according to the number of daily active users or monthly active users to identify software assets with high and low usage frequencies. For investment models, the system can divide software assets into "cost model", "capital model" and "self-developed model" to reflect the financial and development background of different software assets. The results of the classification process will be stored in the database, and classification reports can be generated or used to build software asset views from different perspectives.

[0108] According to the above steps, take a CRM (customer relationship management) software system in an enterprise as an example, whose asset coding information is "IT / SCN-0009". Its different business users, such as the sales department and the customer service department, can add public tags such as "customer service category" to the CRM system, while the system administrator or developer adds user tags such as "internal use" and "integration capability". The system classifies the CRM system as "business operation category" according to preset classification rules, such as business classification, and can classify it as "highly active software" according to its monthly active user number. All classification results will be displayed on the dashboard or management interface for users of different roles to view and use. For example, business users may pay more attention to the use of "customer service category" software assets, while the finance department may be more concerned about the return on investment of "capital model" and "cost model" software assets.

[0109] Through the above specific implementation methods, the present invention can effectively receive and manage the coding information and tags of software assets, realize multi-dimensional classification of software assets, and provide strong support for the management and decision-making of software assets.

[0110] Figure 2 is a user view of a software asset according to an embodiment of the present application, which adopts a three-dimensional modeling form to achieve a visual overview of the software asset, such as Figure 2 As shown in the figure, six preset areas are used to comprehensively display the information of a software asset. These areas correspond to different dimensions of the software asset:

[0111] The entry layer area is used to display the first-level menu items in the software system and the number of second-level menus under them, helping users quickly locate various functional modules. There is a number next to each first-level menu, indicating the number of second-level menu items contained in the menu. Clicking the menu can jump to the detailed second-level menu list, which shows the user of each menu and the number of visits within the preset time.

[0112] The functional layer area is used to display the important functional modules of the software assets, including the primary functional modules and the more detailed secondary functional modules. The information in this area responds to the click operation on the primary menu of the entry layer. Users can view the detailed description of the functional modules, such as the functional introduction and operation guide, to further understand and master the functional characteristics of the software.

[0113] The capability layer area is used to display the number of capabilities provided or called by software assets. By clicking the number displayed in this area, users can jump to the capability exposure information page, which lists in detail the capabilities called or output by the software system through the capability exposure platform, including capability name, code, provision / calling method, call volume, and online time.

[0114] The indicator layer area is used to display the core evaluation indicators of software assets. When a user clicks on an indicator, this area will display the specific information of the indicator, such as the indicator name, code, data collection method, data collection caliber, and the latest indicator value. At the same time, users can view the historical statistics of the indicator to evaluate the operating status and value of the software assets.

[0115] The data layer area is used to provide data asset information and data architecture diagrams of software assets. Users can query detailed information about each data asset in this area, such as the data structure, storage location, data volume, and data confidentiality level, to understand the data composition and management of software assets.

[0116] The resource layer area is used to display the cloud resource information required for the operation of software assets, such as the usage of operating systems, containers, virtual machines, physical machines, middleware, and databases. It includes the resource name, type, unique identifier, usage, and utilization rate, etc., to help users monitor and manage the use of cloud resources.

[0117] Through the six preset areas in the figure, users can obtain comprehensive information from various dimensions of software assets (entry, function, capability, indicator, data, resource), so as to better understand and utilize software assets and improve the efficiency and value of software assets. The three-dimensional modeling form makes this information more intuitive, enhancing user experience and data insight.

[0118] Figure 3 is a software asset relationship diagram constructed using a knowledge graph according to an embodiment of the present application, such as Figure 3 As shown in the figure, the interconnection links between multiple software assets are intuitively displayed. Specifically, the calling relationship and interface integration between software assets are clearly depicted through the graphical representation of nodes and edges:

[0119] Figure 3Each node in the graph represents a software asset, including CRM systems, e-commerce portals, customer service portals, customer service portals, operation and maintenance portals, billing systems, activation systems, resource systems, network management systems, etc. Edges are lines connecting different nodes, which are used to represent the call relationship between software assets. The direction of the edge clearly indicates the direction of the call, that is, which system is the caller and which system is the callee. The width or color coding of the edge can indicate the frequency or importance of the call, helping users quickly identify key system interactions. At the junction of the node and the edge, the details of the call information are displayed, including the direction of the call (calling or being called), the type of call (such as API call, data request, etc.), the name of the calling interface, and the number of calls within a certain time range.

[0120] Through the display of the knowledge graph, an intuitive visual representation is provided for the complex calling relationships between software assets, which makes it easier for IT managers and developers to quickly understand the interconnection of software assets within the enterprise. This is crucial for understanding the integration complexity of software assets and discovering potential integration problems or optimization points.

[0121] Figure 4 is a structural diagram of a software asset visualization device according to an embodiment of the present application, such as Figure 4 As shown, the device comprises:

[0122] The collection module 40 is used to collect multiple different types of target information related to software assets, wherein the target information includes at least two of the following: attribute information of software assets, construction project information, architecture information, user group information, function information, capability exposure information, cloud resource information, data asset information, indicator information, and technological innovation information.

[0123] The first display module 42 is used to perform three-dimensional display of different types of target information in different areas of the target interface.

[0124] The second display module 44 is used to obtain the log data of the application program interface corresponding to each software asset in the capability exposure platform, extract the call information between software assets in the log data, build a knowledge graph based on the software assets and the call information between software assets, and display the knowledge graph.

[0125] Optionally, the attribute information of the software asset includes at least one of the following: identification information of the software asset, coding information of the software asset, construction time information of the software asset, classification information of the software asset, associated object information of the software asset, and investment model information of the software asset; the construction project information includes at least one of the following: identification information of the construction project, identification information of the work breakdown structure WBS of the construction project, investment amount information, construction time information, issuance time information, closing time information, project status information, and engineering management object information of the construction project; the architecture information includes at least one of the following: business architecture diagram, functional architecture diagram, data architecture diagram, network architecture diagram, and system architecture diagram; the user group information includes at least one of the following: user role information, user quantity information, quantity information of active users within a preset time period, and ranking information of the quantity information of active users within a preset time period; the software asset function information includes at least one of the following: identification information of the function module in the software asset, coding information of the function module, level information of the function module, description information of the function module, attribute information of the function module, question information of the function module The information on capability exposure includes at least one of the following: identification information of the capabilities provided and called by the software assets, coding information of the capabilities, provision information of the capabilities, calling information of the capabilities, provision object information of the capabilities, calling object information of the capabilities, access method information of the capabilities, calling volume information of the capabilities, called volume information of the capabilities, and online time information of the capabilities; the information on cloud resources includes at least one of the following: resource deployment diagram, resource name information, resource type information, resource identification information, resource usage information, and resource utilization rate information; the information on data assets includes at least one of the following: data asset directory information, data asset coding information, data asset format information, data asset storage cycle information, and data asset confidentiality level information; the information on indicators includes at least one of the following: indicator name information, indicator coding information, indicator data caliber information, indicator value information, and indicator statistical time information; the information on technological innovation includes at least one of the following: promotion income information, patent information, paper publication information, enterprise or industry standard information, and innovation award information.

[0126] Optionally, the collection module 40 is also used to perform the following steps: respond to a first preset instruction to call a first preset interface, access the engineering construction system through the first preset interface, and collect construction project information in the engineering construction system; respond to a second preset instruction to call a second preset interface, access the log center system through the second preset interface, and collect software asset function information in the accessed log center system; respond to a third preset instruction to call a third preset interface, access the data governance center through the third preset interface, and collect data asset information in the data governance center; respond to a fourth preset instruction to call a fourth preset interface, access the docking capability open platform through the fourth preset interface, and collect capability open information in the docking capability open platform; respond to a fifth preset instruction to call a fifth preset interface, access the cloud management platform through the fifth preset interface, and collect cloud resource information in the cloud management platform.

[0127] Optionally, the first display module 42 is also used to perform the following steps: display multiple first-level menus in a first preset area within the target interface, and display the number of second-level menus included in each first-level menu, wherein the first-level menu at least includes: attribute information of software assets, and the second-level menu at least includes: construction project information, architecture information, and user group information; in response to a click operation on the first-level menu, jump to the second-level menu list, wherein the second-level menu list includes multiple second-level menus, and each second-level menu displays the user objects of the second-level menu and the number of visits within a preset time period; display the first-level function modules and the second-level function modules in the second preset area within the target interface, and in response to a click operation on the first-level function module, display the function introduction information and operation information in the first-level function module Guidance information, in response to a click operation on the secondary function module, displays the function introduction information and operation guidance information in the secondary function module, wherein the primary function module at least includes: attribute information of the software asset; the secondary function module at least includes: construction project information, architecture information, and user group information; displays the target number of capabilities provided and called by the software asset in the third preset area within the target interface, and displays the capability exposure information of each capability in response to a click operation on the target number; displays the indicator information of the software asset in the fourth preset area within the target interface, and displays the indicator information corresponding to the target indicator in response to a click operation on the target indicator; displays the data asset information in the fifth preset area within the target interface; and displays the cloud resource information in the sixth preset area within the target interface.

[0128] Optionally, the second display module 44 is also used to perform the following steps: perform data cleaning processing on the log data to remove invalid data and duplicate data, analyze the log data after data cleaning processing, and extract call information between software assets, wherein the call information includes: call direction, call type, name of the call interface and call amount, and the call direction includes: calling and being called; use software assets as nodes and call information as edges to construct a knowledge graph; convert the node and edge data in the knowledge graph into a target format readable by visualization tools, and use visualization tools to display the knowledge graph.

[0129] Optionally, the software asset visualization device is also used to perform the following steps: divide the target information according to multiple preset dimensions to obtain multiple division results, wherein the multiple preset dimensions include at least two of the following: the total amount of software assets, the life cycle of software assets, the number of software assets under different business categories, the ranking of software assets by user activity rate, the ranking of software assets by annual investment amount, and the ranking of software assets by value assessment. The life cycle of software assets includes: planning period, construction period, maturity period, evolution period, and offline; use a preset dashboard to display the multiple division results.

[0130] Optionally, after collecting various types of target information related to software assets, the software asset visualization device is also used to perform the following steps: receiving asset coding information of software assets, receiving labels of software assets input by different target objects; and classifying the target information according to different classification rules.

[0131] It should be noted that the above Figure 4 The modules in the embodiment may be program modules (e.g., a set of program instructions for implementing a specific function) or hardware modules. For the latter, they may be expressed in the following forms, but are not limited thereto: the expression form of the above modules is a processor, or the functions of the above modules are implemented by a processor.

[0132] It should be noted that Figure 4 The preferred implementation of the illustrated embodiment can be found in Figure 1 The relevant description of the illustrated embodiment will not be repeated here.

[0133] Figure 5 The hardware structure block diagram of a computer terminal for implementing a method for visualizing software assets is shown. Figure 5As shown, the computer terminal 50 may include one or more (502a, 502b, ..., 502n are used to illustrate) processors 502 (the processor 502 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 504 for storing data, and a transmission module 506 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the BUS bus), a network interface, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 5 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 5 More or fewer components as shown, or with Figure 5 Different configurations shown.

[0134] It should be noted that the one or more processors 502 and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 50. As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

[0135] The memory 504 can be used to store software programs and modules of application software, such as program instructions / data storage devices corresponding to the method for visualizing software assets in the embodiment of the present application. The processor 502 executes various functional applications and data processing by running the software programs and modules stored in the memory 504, that is, realizing the method for visualizing software assets described above. The memory 504 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 504 may further include a memory remotely arranged relative to the processor 502, and these remote memories may be connected to the computer terminal 50 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0136] The transmission module 506 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 50. In one example, the transmission module 506 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission module 506 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0137] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 50 .

[0138] It should be noted that, in some optional embodiments, the above Figure 5 The computer terminal shown may include hardware elements (including circuits), software elements (including computer code stored on a computer-readable medium), or a combination of hardware elements and software elements. It should be noted that Figure 5 This is merely one example of a particular embodiment and is intended to illustrate the types of components that may be present in the computer terminal described above.

[0139] It should be noted that Figure 5 The computer terminal shown is used to execute Figure 1 The visualization method of the software assets shown in the figure, therefore the relevant explanations and instructions in the execution method of the above commands are also applicable to the electronic device and will not be repeated here.

[0140] The embodiment of the present application further provides a non-volatile storage medium, which includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the above software asset visualization method.

[0141] A program for a non-volatile storage medium to perform the following functions: collecting multiple different types of target information related to software assets, wherein the target information includes at least two of the following: attribute information, construction project information, architecture information, user group information, function information, capability exposure information, cloud resource information, data asset information, indicator information, and technological innovation information of the software assets; performing three-dimensional display of different types of target information in different areas of a target interface; obtaining log data of an application program interface corresponding to each software asset in a capability exposure platform, extracting call information between software assets from the log data, constructing a knowledge graph based on the software assets and the call information between software assets, and displaying the knowledge graph.

[0142] An embodiment of the present application further provides an electronic device, including: a memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the above software asset visualization method is executed when the program is run.

[0143] The processor is used to run a program that performs the following functions: collecting multiple different types of target information related to software assets, where the target information includes at least two of the following: attribute information, construction project information, architecture information, user group information, function information, capability exposure information, cloud resource information, data asset information, indicator information, and technological innovation information of the software assets; performing three-dimensional display of different types of target information in different areas of the target interface; obtaining log data of the application program interface corresponding to each software asset in the capability exposure platform, extracting call information between software assets from the log data, constructing a knowledge graph based on the software assets and the call information between software assets, and displaying the knowledge graph.

[0144] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0145] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0146] In the above-mentioned embodiments of the present application, the collected information is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary protection measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0147] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0148] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0149] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0150] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0151] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for visualizing software assets, characterized in that: include: Collecting multiple different types of target information related to software assets, wherein the target information includes at least two of the following: attribute information, construction project information, architecture information, user group information, function information, capability exposure information, cloud resource information, data asset information, indicator information, and technology innovation information of software assets; Displaying different types of target information in three dimensions in different areas of the target interface; The log data of the application program interface corresponding to each software asset is obtained in the capability exposure platform, the call information between the software assets is extracted from the log data, a knowledge graph is constructed according to the software assets and the call information between the software assets, and the knowledge graph is displayed.

2. The method according to claim 1, characterized in that The attribute information of the software asset includes at least one of the following: identification information of the software asset, coding information of the software asset, construction time information of the software asset, classification information of the software asset, associated object information of the software asset, and investment model information of the software asset; The construction project information includes at least one of the following: identification information of the construction project, identification information of the work breakdown structure WBS of the construction project, investment amount information, construction time information, release time information, closing time information, project status information, and construction project engineering management object information; The architecture information includes at least one of the following: a business architecture diagram, a functional architecture diagram, a data architecture diagram, a network architecture diagram, and a system architecture diagram; The user group information includes at least one of the following: user role information, user quantity information, quantity information of active users within a preset time period, and ranking information of quantity information of active users within the preset time period; The software asset function information includes at least one of the following: identification information of a function module in the software asset, coding information of the function module, level information of the function module, description information of the function module, attribute information of the function module, question and answer information of the function module, operation guide information of the function module, and information on the number of users using the function module; The capability exposure information includes at least one of the following: identification information of the capability provided and called by the software asset, encoding information of the capability, provision information of the capability, calling information of the capability, provision object information of the capability, calling object information of the capability, access mode information of the capability, calling volume information of the capability, called volume information of the capability, and online time information of the capability; The cloud resource information includes at least one of the following: resource deployment diagram, resource name information, resource type information, resource identification information, resource usage information, and resource utilization rate information; The data asset information includes at least one of the following: data asset directory information, data asset encoding information, data asset format information, data asset storage cycle information, and data asset confidentiality level information; The indicator information includes at least one of the following: indicator name information, indicator code information, indicator data caliber information, indicator value information, and indicator statistical time information; The technological innovation information includes at least one of the following: promotion income information, patent information, paper publication information, enterprise or industry standard information, and innovation award information.

3. The method according to claim 2, characterized in that Collects multiple different types of targeted information related to software assets, including: In response to a first preset instruction, a first preset interface is called, an engineering construction system is accessed through the first preset interface, and the construction project information is collected in the engineering construction system; In response to a second preset instruction, a second preset interface is called, a log center system is accessed through the second preset interface, and the software asset function information is collected in the access log center system; In response to a third preset instruction, a third preset interface is called, a data governance center is accessed through the third preset interface, and the data asset information is collected in the data governance center; In response to a fourth preset instruction, a fourth preset interface is called, a connection capability exposure platform is accessed through the fourth preset interface, and the capability exposure information is collected in the connection capability exposure platform; In response to the fifth preset instruction, the fifth preset interface is called, the cloud management platform is accessed through the fifth preset interface, and the cloud resource information is collected in the cloud management platform.

4. The method according to claim 1, characterized in that: Different types of target information are displayed in three dimensions in different areas of the target interface, including: Displaying a plurality of first-level menus in a first preset area in the target interface, and displaying the number of second-level menus included in each first-level menu, wherein the first-level menu includes at least: attribute information of the software asset, and the second-level menu includes at least: the construction project information, the architecture information, and the user group information; In response to a click operation on the primary menu, jump to a secondary menu list, wherein the secondary menu list includes a plurality of secondary menus, each of which displays a user of the secondary menu and a number of visits within a preset time period; Displaying the primary function module and the secondary function module in the second preset area of ​​the target interface, and in response to a click operation on the primary function module, displaying the function introduction information and operation guide information in the primary function module, and in response to a click operation on the secondary function module, displaying the function introduction information and operation guide information in the secondary function module, wherein the primary function module at least includes: the attribute information of the software asset; the secondary function module at least includes: the construction project information, the architecture information, and the user group information; Displaying the target number of capabilities provided and called by the software asset in a third preset area in the target interface, and displaying the capability exposure information of each capability in response to a click operation on the target number; Displaying the indicator information of the software asset in a fourth preset area in the target interface, and displaying the indicator information corresponding to the target indicator in response to a click operation on the target indicator; Displaying the data asset information in a fifth preset area in the target interface; The cloud resource information is displayed in a sixth preset area within the target interface.

5. The method according to claim 1, characterized in that: Extracting the call information between the software assets from the log data, constructing a knowledge graph based on the software assets and the call information between the software assets, and displaying the knowledge graph, including: Performing data cleaning on the log data to remove invalid data and duplicate data, analyzing the log data after data cleaning, and extracting call information between the software assets, wherein the call information includes: call direction, call type, name of the call interface and call amount, and the call direction includes: call and called; Taking the software assets as nodes and the call information as edges, a knowledge graph is constructed; The node and edge data in the knowledge graph are converted into a target format readable by a visualization tool, and the knowledge graph is displayed using the visualization tool.

6. The method according to claim 1, characterized in that The method further comprises: The target information is divided according to a plurality of preset dimensions to obtain a plurality of division results, wherein the plurality of preset dimensions include at least two of the following: the total amount of software assets, the life cycle of software assets, the number of software assets under different business categories, the ranking of software assets by user activity rate, the ranking of software assets by annual investment amount, and the ranking of software assets by value assessment, and the life cycle of software assets includes: planning period, construction period, maturity period, evolution period, and offline period; A plurality of the segmentation results are displayed using a preset dashboard.

7. The method according to claim 1, characterized in that After collecting a plurality of different types of target information related to the software assets, the method further includes: receiving asset coding information of the software assets, receiving labels of the software assets input by different target objects; and classifying the target information according to different classification rules.

8. A software asset visualization device, characterized in that: include: A collection module, used to collect multiple different types of target information related to software assets, wherein the target information includes at least two of the following: attribute information, construction project information, architecture information, user group information, function information, capability exposure information, cloud resource information, data asset information, indicator information, and technology innovation information of software assets; A first display module is used to display different types of target information in three dimensions in different areas of the target interface; The second display module is used to obtain log data of the application program interface corresponding to each software asset in the capability exposure platform, extract call information between the software assets from the log data, build a knowledge graph based on the software assets and the call information between the software assets, and display the knowledge graph.

9. A non-volatile storage medium, characterized in that: The non-volatile storage medium includes a stored program, wherein when the program is executed, the device where the non-volatile storage medium is located is controlled to execute the method for visualizing software assets according to any one of claims 1 to 7.

10. An electronic device, characterized in that: include: A memory and a processor, wherein the processor is used to run a program stored in the memory, wherein the program executes the software asset visualization method according to any one of claims 1 to 7 when running.

11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method for visualizing software assets according to any one of claims 1 to 7 is implemented.

Images