Central architecture diagram construction method and architecture diagram construction system

Abstract

The present application provides a central architecture diagram construction method and an architecture diagram construction system. The method can be applied to an architecture diagram construction system, thereby generating a central architecture diagram having a better visualization effect. Specifically, the architecture diagram construction system acquires a plurality of pieces of entity information and a relationship among the plurality of pieces of entity information, and then determines first entity information, wherein the first entity information is one of the plurality of pieces of entity information. Then, the architecture diagram construction system constructs a central architecture diagram on the basis of the first entity information and the relationship among the plurality of pieces of entity information, and displays the central architecture diagram, wherein a central node in the central architecture diagram is used for indicating the first entity information, the central architecture diagram further comprises a plurality of annular layers taking the central node as the center, each annular layer comprises at least one node, and nodes of different annular layers have different relationships with the central node.

Description

Methods and systems for constructing central architecture diagrams

[0001] This application claims priority to Chinese Patent Application No. 202311329839.5, filed on October 12, 2023, with the China National Intellectual Property Administration, entitled “Method for Constructing a Central Architecture Diagram and System for Constructing an Architecture Diagram”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of computer technology, and in particular to a method and system for constructing a central architecture diagram. Background Technology

[0003] Architecture diagrams can show users entity information (e.g., business processes) and the relationships between entities. However, the more entities there are, and the more complex the relationships between them, the more nodes and edges there will be in the architecture diagram. This can easily lead to the stacking and intersection of edges, causing more visual clutter for the user.

[0004] Summary of the Invention

[0005] This application provides a method and system for constructing a central architecture diagram, which can generate a central architecture diagram with superior visualization effects.

[0006] Firstly, this application provides a method for constructing a central architecture diagram. This method can be applied to an architecture diagram construction system. Specifically, the architecture diagram construction system acquires multiple entity information and the relationships between these entity information, then determines a first entity information, which is one of the aforementioned multiple entity information. Subsequently, the architecture diagram construction system constructs a central architecture diagram based on the first entity information and the relationships between the multiple entity information, and displays the central architecture diagram. The central node in the central architecture diagram indicates the first entity information. The central architecture diagram also includes multiple ring layers centered on the central node, each ring layer including at least one node, and the nodes in different ring layers have different relationships with the central node.

[0007] The central architecture diagram constructed by the technical solution provided in this application offers users another perspective on observing entity information. The node corresponding to the entity information that the user wants to observe is taken as the central node, and the nodes corresponding to other entity information are arranged in multiple ring layers with the central node as the center. This makes it easier for users to observe the relationship between the entity information indicated by the central node and other entity information.

[0008] In one possible implementation of the first aspect, after acquiring information about multiple entities and the relationships between them, the architecture diagram construction system further constructs and displays a global architecture diagram based on this information. Each node in the global architecture diagram indicates one of the multiple entities. The architecture diagram construction system determines the first entity by receiving information generated when a user clicks on a first node in the global architecture diagram, and then determining the first entity corresponding to that first node based on that information. Through this implementation, the architecture diagram construction system can construct a central architecture diagram according to the user's needs, allowing the user to focus on the entity information they wish to observe.

[0009] In one possible implementation of the first aspect, the architecture diagram construction system constructs a central architecture diagram based on the first entity information and the relationships between multiple entity information. This includes: the architecture diagram construction system determining the hierarchy of multiple entity information based on the hierarchical relationships between nodes in the global architecture diagram; then, based on the hierarchy of the multiple entity information, determining the arrangement of nodes in multiple ring layers, wherein nodes in the same ring layer indicate the same hierarchy of entity information, and nodes in different ring layers indicate different hierarchical levels of entity information. Afterwards, the architecture diagram construction system constructs the central architecture diagram based on the arrangement of nodes in the multiple ring layers.

[0010] Through the above implementation, users can observe the relationship between the first entity information and entity information at different levels from the perspective of entity information hierarchy. In addition, it also makes it convenient for users to expand (or collapse) nodes according to the entity information hierarchy in order to observe the entity information below (or above) the entity information indicated by the expanded (or collapsed) node.

[0011] In one possible implementation of the first aspect, the central architecture diagram is an enterprise process architecture diagram, which is used to represent the relationships between enterprise processes.

[0012] In one possible implementation of the first aspect, the architecture diagram building system further receives user input of an operation to expand any node in the first annular layer of the central architecture diagram, wherein the node is used to indicate second entity information among multiple entity information, the second entity information being associated with one or more lower-level entity information. Subsequently, the architecture diagram building system updates the central architecture diagram according to the operation of expanding the node and displays the updated central architecture diagram, wherein the updated central architecture diagram hides the node, and the updated central architecture diagram includes a second annular layer, the second annular layer including one or more child nodes associated with the node, the child nodes associated with the node indicating entity information below the second entity information.

[0013] Using the above implementation method, users can expand any node in the ring layer of the central architecture diagram according to their needs to observe the lower-level entity information associated with the entity information indicated by the expanded node.

[0014] In one possible implementation of the first aspect, the architecture diagram building system receives user input of any node in the first annular layer of the expanded central architecture diagram, including: the architecture diagram building system receives user input of selecting the node and moving it to the area where the second annular layer of the central architecture diagram is located.

[0015] In one possible implementation of the first aspect, the architecture diagram building system also receives user input to change the central node, updates the central architecture diagram based on the aforementioned operation, and displays the updated central architecture diagram. The updated central architecture diagram includes the new central node and nodes in multiple ring layers centered on the new central node. Thus, the user can observe any node as the central node according to their needs.

[0016] In one possible implementation of the first aspect, the architecture diagram building system receives a user input to change the central node, including: the architecture diagram building system receiving an operation from the user to select any node in the third ring layer of the central architecture diagram and move it to the area where the original central node was located. Alternatively, the architecture diagram building system receives an operation from the user to select a replaceable node and move it to the area where the original central node was located, wherein the replaceable node is a node displayed in the central architecture diagram when the architecture diagram building system detects an operation acting on the original central node.

[0017] In one possible implementation of the first aspect, the architecture diagram building system further receives a user-input operation to collapse a second node in the fourth ring layer of the central architecture diagram, wherein the second node is used to indicate third entity information among multiple entity information. Subsequently, the architecture diagram building system updates the central architecture diagram according to the aforementioned operation of collapsing the second node and displays the updated central architecture diagram, wherein the updated central architecture diagram hides the second node and / or the third node in the fourth ring layer, the third node being used to indicate fourth entity information among multiple entity information, and the updated central architecture diagram also includes a fifth ring layer, the fifth ring layer including the fourth node, and the lower-level entity information associated with the entity information indicated by the fourth node includes both the third and fourth entity information.

[0018] Using the above implementation method, users can collapse any one or more nodes in the ring layer of the central architecture diagram as needed to observe the upper-level entity information associated with the entity information indicated by the collapsed node.

[0019] In one possible implementation of the first aspect, the architecture graph building system receives user input of an operation to collapse a second node in the fourth ring layer of the central architecture graph, including: the architecture graph building system receiving an operation from the user to select the second node and move it to the area where the fifth ring layer is located.

[0020] In one possible implementation of the first aspect, the central architecture graph also includes edges between the central node and the nodes of the ring layer, wherein the edges indicate the relationships between the entity information indicated by the nodes at both ends of the edge. It should be understood that when the central architecture graph does not include edges between the nodes of the ring layer, the user can more intuitively observe the relationships between the first entity information and other entity information.

[0021] In one possible implementation of the first aspect, the central architecture diagram includes a hierarchy of entity information indicated by any node, thereby facilitating user observation of the entity information hierarchy. Alternatively, nodes in the ring layer connected to the central node in the central architecture diagram are represented using different primitives than nodes in other ring layers, thereby highlighting the nodes in the ring layer connected to the central node and facilitating user observation of entity information related to the first entity information.

[0022] Secondly, this application provides a method for displaying a central architecture diagram. This method can be applied to an architecture diagram display system. Specifically, the architecture diagram display system displays a central architecture diagram, wherein a central node in the central architecture diagram is used to indicate first entity information. The central architecture diagram also includes multiple ring layers centered on the central node, each ring layer including at least one node. The architecture diagram display system also receives an operation from a user to move a first node from the first ring layer of the central architecture diagram to the area of ​​a second ring layer, wherein the first node is used to indicate second entity information. Subsequently, based on the user's operation on the first node, the architecture diagram display system hides the first node and displays a second node associated with the first node in the second ring layer, wherein the second node is used to indicate third entity information, and the third entity information is associated with the second entity information.

[0023] In one possible implementation of the second aspect, the second node is a child node of the first node, and the third entity information is the lower-level entity information of the second entity information. Alternatively, the second node is the parent node of the first node, and the third entity information is the upper-level entity information of the second entity information.

[0024] In one possible implementation of the second aspect, the architecture diagram display system further receives an operation from the user selecting a third node in the third ring layer of the central architecture diagram and moving it to the area where the central node is located, wherein the third node is used to indicate fourth entity information. Subsequently, based on the user's operation on the third node, the architecture diagram display system displays a new central node and nodes in multiple ring layers centered on the new central node, wherein the new central node is the third node.

[0025] In one possible implementation of the second aspect, the architecture diagram shows that the system also receives user actions on the central node, and displays replaceable nodes based on these actions, where the replaceable nodes are used to indicate the fifth entity information. Subsequently, the architecture diagram shows that the system receives user actions to select a replaceable node and move it to the area where the central node is located. Based on the user's actions on the replaceable node, a new central node and nodes in multiple ring layers centered on the new central node are displayed, where the new central node is the replaceable node.

[0026] In one possible implementation of the second aspect, the central architecture diagram is an enterprise process architecture diagram, which is used to represent the relationships between enterprise processes.

[0027] In one possible implementation of the second aspect, before displaying the central architecture diagram, the architecture diagram display system also acquires a global architecture diagram, which includes multiple nodes, each indicating an entity. Then, based on the hierarchical relationships between nodes in the global architecture diagram, the system determines the hierarchy of the entity information indicated by these nodes. Next, based on the hierarchy of the entity information, the architecture diagram display system determines the arrangement of nodes in multiple ring layers, where nodes in the same ring layer indicate the same hierarchy of entity information, and nodes in different ring layers indicate different hierarchical levels of entity information. Finally, based on the arrangement of nodes in the multiple ring layers, the architecture diagram display system constructs the central architecture diagram.

[0028] Thirdly, this application provides an architecture diagram construction system. The system includes an acquisition module, a layout module, and a visualization module. The acquisition module is used to acquire information about multiple entities and the relationships between them. The layout module is used to determine first entity information and, based on the first entity information and the relationships between the multiple entity information, construct a central architecture diagram, wherein the first entity information is one of the aforementioned multiple entity information. The visualization module is used to display the central architecture diagram, wherein the central node in the central architecture diagram indicates the first entity information, and the central architecture diagram also includes multiple ring layers centered on the central node, each ring layer including at least one node, and the nodes in different ring layers have different relationships with the central node.

[0029] In one possible implementation of the third aspect, the layout module is further configured to construct a global architecture diagram based on multiple entity information and the relationships between them, wherein each node in the global architecture diagram indicates one of the multiple entity information. The visualization module is also configured to display the global architecture diagram. The layout module is configured to receive information generated by the user clicking on the first node in the global architecture diagram and determine the first entity information corresponding to the first node based on this information.

[0030] In one possible implementation of the third aspect, the layout module is used to determine the hierarchy of multiple entity information based on the hierarchical relationship between nodes in the global architecture diagram; determine the arrangement of nodes in multiple ring layers based on the hierarchy of multiple entity information, wherein nodes in the same ring layer indicate the same hierarchy of entity information, and nodes in different ring layers indicate different hierarchical levels of entity information; and construct a central architecture diagram based on the arrangement of nodes in multiple ring layers.

[0031] In one possible implementation of the third aspect, the central architecture diagram is an enterprise process architecture diagram, which is used to represent the relationships between enterprise processes.

[0032] In one possible implementation of the third aspect, the architecture diagram construction system further includes an interaction module. The interaction module receives user input regarding an operation on any node in the first annular layer of the expanded central architecture diagram, where the node indicates second entity information among multiple entity information, and the second entity information is associated with one or more lower-level entity information. The layout module is also used to update the central architecture diagram based on the operation of expanding the node. The visualization module is further used to display the updated central architecture diagram, where the updated central architecture diagram hides the node, and the updated central architecture diagram includes a second annular layer, which includes one or more child nodes associated with the node, and the child nodes associated with the node indicate entity information below the second entity information.

[0033] In one possible implementation of the third aspect, the interaction module is used to receive the operation of the user selecting any node in the first ring layer and moving to the area where the second ring layer of the central architecture diagram is located.

[0034] In one possible implementation of the third aspect, the interaction module is further configured to receive user input for a change of the central node. The layout module is further configured to update the central architecture diagram based on the aforementioned change of the central node operation. The visualization module is further configured to display the updated central architecture diagram, wherein the updated central architecture diagram includes the new central node and nodes in multiple ring layers centered on the new central node.

[0035] In one possible implementation of the third aspect, the interaction module is used to receive an operation from the user selecting any node in the third ring layer of the central architecture diagram and moving it to the area where the original central node was located. Alternatively, it can receive an operation from the user selecting a replaceable node and moving it to the area where the original central node was located, wherein the replaceable node is a node displayed in the central architecture diagram when an operation acting on the original central node is detected.

[0036] In one possible implementation of the third aspect, the interaction module is further configured to receive user input of an operation to collapse a second node in the fourth ring layer of the central architecture diagram, wherein the second node is used to indicate third entity information among multiple entity information. The layout module is further configured to update the central architecture diagram according to the aforementioned operation of collapsing the second node. The visualization module is further configured to display the updated central architecture diagram, wherein the updated central architecture diagram hides the second node and / or the third node in the fourth ring layer, the third node being used to indicate fourth entity information among multiple entity information, and the updated central architecture diagram also includes a fifth ring layer, the fifth ring layer including the fourth node, and the lower-level entity information associated with the entity information indicated by the fourth node includes both the third and fourth entity information.

[0037] In one possible implementation of the third aspect, the interaction module is used to receive the user's operation of selecting the second node and moving it to the area where the fifth ring layer is located.

[0038] In one possible implementation of the third aspect, the central architecture diagram also includes edges between the central node and the nodes of the ring layer, wherein the edges indicate the relationship between the entity information indicated by the nodes at both ends of the edges.

[0039] In one possible implementation of the third aspect, the central architecture diagram includes a hierarchy of entity information indicated by any node. Alternatively, nodes in the ring layer connected to the central node in the central architecture diagram use different primitive representations than nodes in other ring layers.

[0040] Fourthly, this application provides an architecture diagram display system. The system includes a visualization module and an interaction module. The visualization module displays a central architecture diagram, wherein a central node in the central architecture diagram indicates first entity information. The central architecture diagram also includes multiple ring-shaped layers centered on the central node, each ring-shaped layer including at least one node. The interaction module receives an operation from a user to move a first node from the first ring-shaped layer of the central architecture diagram to the area of ​​a second ring-shaped layer, wherein the first node indicates second entity information. The visualization module is also used to hide the first node based on the user's operation on the first node, and to display a second node associated with the first node in the second ring-shaped layer, wherein the second node indicates third entity information, and the third entity information is associated with the second entity information.

[0041] In one possible implementation of the fourth aspect, the second node is a child node of the first node, and the third entity information is the lower-level entity information of the second entity information. Alternatively, the second node is the parent node of the first node, and the third entity information is the upper-level entity information of the second entity information.

[0042] In one possible implementation of the fourth aspect, the interaction module is further configured to receive an operation from the user selecting a third node in the third ring layer of the central architecture diagram and moving it to the area where the central node is located, wherein the third node is used to indicate the fourth entity information. The visualization module is further configured to display a new central node and nodes in multiple ring layers centered on the new central node, based on the user's operation on the third node, wherein the new central node is the third node.

[0043] In one possible implementation of the fourth aspect, the interaction module is further configured to receive user actions on the central node. The visualization module is further configured to display replaceable nodes based on the action, wherein the replaceable nodes are used to indicate the fifth entity information. The interaction module is further configured to receive user actions to select a replaceable node and move it to the area where the central node is located. The visualization module is further configured to display a new central node and nodes in multiple ring layers centered on the new central node, wherein the new central node is the replaceable node, based on the user's action on the replaceable node.

[0044] In one possible implementation of the fourth aspect, the central architecture diagram is an enterprise process architecture diagram, which is used to represent the relationships between enterprise processes.

[0045] In one possible implementation of the fourth aspect, the architecture diagram display system further includes a layout module. The layout module is used to obtain a global architecture diagram, which includes multiple nodes, each node indicating an entity. The layout module is also used to determine the hierarchy of the multiple entity information indicated by the nodes based on the hierarchical relationship between the nodes in the global architecture diagram; and to determine the arrangement of nodes in multiple ring layers based on the hierarchy of the multiple entity information, wherein nodes in the same ring layer indicate the same hierarchy of entity information, and nodes in different ring layers indicate different hierarchical levels of entity information. The layout module is also used to construct the central architecture diagram based on the arrangement of nodes in the multiple ring layers.

[0046] Fifthly, this application provides a computing device. The computing device includes a processor and a memory. The processor is used to execute instructions stored in the memory to implement some or all of the methods described in the first aspect and any implementation thereof, and the second aspect and any implementation thereof.

[0047] Sixthly, this application provides a computing device cluster. The computing device cluster includes at least one computing device, each computing device including a processor and a memory. The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, causing the computing device cluster to perform some or all of the methods described in the first aspect and any implementation thereof, and the second aspect and any implementation thereof.

[0048] In a seventh aspect, this application provides a computer program product. This computer program product may be a software or program product containing instructions that can run on a computing device or be stored on any available medium. When the computer program product runs on a computing device or a cluster of computing devices, it causes the computing device or the cluster of computing devices to perform some or all of the methods described in the first aspect and any implementation thereof, and the second aspect and any implementation thereof.

[0049] Eighthly, this application provides a computer-readable storage medium. The computer storage medium includes computer program instructions that, when executed by a computing device or cluster of computing devices, cause the computing device or cluster of computing devices to perform some or all of the methods described in the first aspect and any implementation thereof, and the second aspect and any implementation thereof. Attached Figure Description

[0050] Figure 1 is a schematic diagram of an architecture diagram construction system provided in an embodiment of this application;

[0051] Figure 2 is a schematic diagram of an application scenario provided by an embodiment of this application;

[0052] Figures 3A-3I are schematic diagrams of a user interface provided in an embodiment of this application;

[0053] Figure 4 is a schematic diagram of a method for constructing an architecture diagram according to an embodiment of this application;

[0054] Figure 5 is a schematic diagram of an architecture display system provided in an embodiment of this application;

[0055] Figure 6 is a schematic diagram of the structure of a computing device provided in an embodiment of this application;

[0056] Figure 7 is a schematic diagram of the structure of a computing device cluster provided in an embodiment of this application;

[0057] Figure 8 is a schematic diagram of another computing device cluster provided in an embodiment of this application. Detailed Implementation

[0058] The technical solution provided in this application will now be described with reference to the accompanying drawings.

[0059] An architecture diagram is a topological structure composed of multiple nodes and at least one edge. Each node in an architecture diagram represents an entity, and the edges indicate the relationships between the entities represented by the nodes at either end of the edge. Therefore, an architecture diagram can present entities and their relationships to the user. However, traditional architecture diagrams suffer from information flattening; they present all entities and their relationships to the user. The more entities and the more complex their relationships, the more nodes and edges appear in the diagram, resulting in poor overall visualization. This is especially problematic when users want to focus on a single node; numerous irrelevant nodes and edges can create significant visual clutter.

[0060] For example, in enterprise management and operations, an architecture diagram (also known as an "enterprise process architecture diagram") can be used to present enterprise processes and the relationships between them to users, facilitating their understanding, management, and maintenance of these processes. An enterprise process refers to a set of standardized business operation rules and mechanisms within an enterprise. In an enterprise process architecture diagram, each node indicates a process architecture, and each edge indicates the integration relationship between the process architectures at both ends of the edge. A process architecture is a structured overall framework for enterprise processes, describing the classification, hierarchy, boundaries, scope, input / output relationships, etc., reflecting the enterprise's operating model and business characteristics. Furthermore, large process architectures can be further subdivided to form multiple lower-level process architectures; that is, one process architecture can be associated with multiple lower-level process architectures. Therefore, enterprises typically have a large number of low-level process architectures, and the relationships between these low-level process architectures are highly complex. Consequently, the enterprise process architecture diagram includes a large number of nodes and edges. In this situation, when users want to focus on a single enterprise process, the architecture diagram also displays a large number of unrelated enterprise processes and their relationships, causing significant visual interference for the user's observation.

[0061] To address the aforementioned issues, this application provides an architecture diagram construction system. The architecture diagram constructed by this system presents entity information and the relationships between them to the user in a "star trail" format. Specifically, the node corresponding to the entity information the user focuses on is located at the center of the diagram, with nodes corresponding to other entities arranged around this central node. This allows the user to easily use a single entity as the focal point to understand its relationships with other entities. To distinguish it from traditional architecture diagrams, the architecture diagram constructed using this system will be referred to as the central architecture diagram.

[0062] Figure 1 shows a schematic diagram of an architecture diagram building system provided in an embodiment of this application. It should be understood that Figure 1 is merely an exemplary illustration of one way to divide the structure of an architecture diagram building system. In practical applications, the structure of an architecture diagram building system can also be divided in other ways, and this embodiment does not impose specific limitations. As shown in Figure 1, the architecture diagram building system 100 includes an acquisition module 101, a layout module 102, and a visualization module 103. Optionally, the architecture diagram building system 100 may further include an interaction module 104.

[0063] The acquisition module 101 is used to acquire information about multiple entities and the relationships between them. Specifically, the acquisition module 101 can acquire information about multiple entities and the relationships between them from a database, or it can acquire information about multiple entities and the relationships between them based on user input (e.g., an administrator user). Entity information can be related to entities with hierarchical information, such as information related to process architecture (e.g., process architecture code and name), information related to organizational units (e.g., department name), information related to directories (e.g., directory code and name), etc. The relationships between entity information can include integration relationships between entity information. The acquisition module 101 is also used to send the acquired information about multiple entities and the relationships between them to the layout module 102.

[0064] The layout module 102 is used to determine the first entity information, which is one of multiple entity information. The layout module 102 is also used to construct a central architecture diagram based on the first entity information and the relationships between the multiple entity information. The central architecture diagram includes a central node that indicates the first entity information. The central architecture diagram also includes multiple ring layers centered on the central node, each ring layer including at least one node, with different relationships between nodes in different ring layers and the central node. The layout module 102 is also used to send the constructed central architecture diagram to the visualization module 103.

[0065] Optionally, the layout module 102 is further configured to construct a global architecture diagram based on multiple entity information and the relationships between them, and send the constructed global architecture diagram to the visualization module 103. Each node in the global architecture diagram indicates one of the aforementioned multiple entity information. Therefore, the layout module 102 can determine the first entity information in the following way: the layout module 102 receives information generated by the user clicking on the first node in the global architecture diagram, and determines the first entity information corresponding to the first node based on this information.

[0066] Optionally, nodes in the same ring layer in the central architecture diagram indicate the same level of entity information, while nodes in different ring layers indicate different levels of entity information.

[0067] Optionally, the central architecture diagram also includes edges between the central node and the nodes in the ring layer, which are used to indicate the relationship between the entity information indicated by the nodes at both ends of the edge.

[0068] The visualization module 103 is used to display the central architecture diagram constructed by the layout module 102. It should be understood that, as can be seen from the aforementioned functions of the layout module 102, the central architecture diagram constructed by this module highlights the central node, thereby making it easier for users to focus on the entity information indicated by the central node.

[0069] Optionally, the visualization module 103 is also used to display the global architecture diagram constructed by the layout module 102, so that the user can view the global architecture diagram and click on the first node in the global architecture diagram. Accordingly, the layout module 102 can receive the information generated by the user clicking on the first node.

[0070] Optionally, the visualization module 103 is also used to optimize the central architecture diagram constructed by the layout module 102 to improve the visual effect of the central architecture diagram. For example, displaying a hierarchy of one or more indicated entity information nodes. Another example is using different primitive representations for nodes in the ring layer connected to the central node compared to nodes in other ring layers.

[0071] In some embodiments, the architecture diagram building system 100 may also include an interaction module 104.

[0072] The interaction module 104 receives user input regarding operations on the central architecture diagram and sends these operations to the layout module 102. Correspondingly, the layout module 102 updates the central architecture diagram based on the user's operations and sends the updated diagram to the visualization module 103. The visualization module 103 then displays the updated central architecture diagram.

[0073] Optionally, the current central architecture diagram includes node a, which is any node in the ring layer a, and node a indicates the second entity information among the aforementioned multiple entity information. Then, the interaction module 104 can receive the user's input to expand node a, and then send the operation to the layout module 102. The layout module 102 updates the central architecture diagram according to the operation to expand node a, and then sends the updated central architecture diagram to the visualization module 103. The visualization module 103 displays the updated central architecture diagram. Compared to the original central architecture diagram, the updated central architecture diagram hides node a and displays the child nodes associated with node a on the ring layer b, wherein the child nodes associated with node a indicate the lower-level entity information associated with the second entity information. When node a in the original central architecture diagram is connected to the central node by an edge, the updated central architecture diagram also hides the edge between node a and the central node, and displays the edge between the child nodes associated with node a and the central node.

[0074] Optionally, the current central architecture diagram includes node d, which is any node in the ring layer c. Node d indicates the third entity information among the aforementioned multiple entity information. Then, the interaction module 104 can also receive a user input to collapse node d, and then send the operation to the layout module 102. The layout module 102 updates the central architecture diagram according to the operation to collapse node d, and then sends the updated central architecture diagram to the visualization module 103. The visualization module 103 displays the updated central architecture diagram. Compared to the original central architecture diagram, the updated central architecture diagram hides node d and / or node s in the ring layer c, and displays the parent node associated with node d in the ring layer d. The parent node associated with node d is the same as the parent node of node s. Node s indicates the fourth entity information among the aforementioned multiple entity information. The lower-level entity information associated with the entity information indicated by the parent node associated with node d includes both the third and fourth entity information.

[0075] Optionally, the interaction module 104 can also receive user input to change the central node, and then send the operation to the layout module 102. The layout module 102 updates the central architecture diagram according to the operation, and then sends the updated central architecture diagram to the visualization module 103. The visualization module 103 displays the updated central architecture diagram. Compared to the original central architecture diagram, the updated central architecture diagram shows the new central node and the nodes in multiple ring layers centered on the new central node.

[0076] Therefore, it can be seen that the architecture diagram construction system 100 provided in this application embodiment can support users to expand or collapse any node in the ring layer of the central architecture diagram, that is, users can flexibly define the level of detail of the entity information displayed in the central architecture diagram according to their needs. In addition, the architecture diagram construction system 100 provided in this application embodiment also supports using any node as the central node, that is, users can focus on any entity information according to their needs.

[0077] Optionally, the interaction module 104 is also used to receive information generated by the user clicking the first node in the global architecture diagram and send the information to the layout module 102, so that the layout module 102 can determine the first entity information based on the above information.

[0078] In this embodiment of the application, the architecture diagram construction system 100 can be a software system, a hardware device, or a combination of a software system and a hardware device.

[0079] When the architecture diagram building system 100 is a software system, it can be deployed in a data center within a cloud environment. For example, it can be a cloud service provided by a cloud service provider. Specifically, the architecture diagram building system 100 can be deployed independently on a single computing instance within the cloud environment's data center, or distributed across multiple computing instances within the same data center. These computing instances include servers, virtual machines, and containers. As shown in Figure 2, the architecture diagram building system 100 is deployed in a cloud environment's data center and abstracted as a cloud service by the cloud service provider. Administrators can log in to the cloud platform via a client webpage, select and purchase the cloud service corresponding to the architecture diagram building system 100, and after successful purchase, provide the system with information on multiple entities and the relationships between them. When ordinary users want to view the architecture diagram, they log in to the cloud platform via a local client webpage and operate the architecture diagram building system 100 to generate, optimize, and display the optimized central architecture diagram. Furthermore, ordinary users can expand or collapse any node in the circular line of the central architecture diagram to view the lower or upper level entity information associated with the entity information indicated by the expanded or collapsed node. Alternatively, ordinary users can change the central node in the central architecture diagram to use other nodes as the center of observation for exploration.

[0080] The architecture diagram building system 100 can also be deployed on terminal computing devices. For example, the architecture diagram building system 100 is source code or components that can run on one or more terminal computing devices. Terminal computing devices include terminal servers, desktop computers, smartphones, laptops, tablets, etc. In one possible deployment method, the acquisition module 101 and layout module 102 in the architecture diagram building system 100 are deployed on a backend server, and the visualization module 103 and interaction module 104 are deployed on a frontend server. For the user, when the user wants to view the architecture diagram, the backend server constructs a central architecture diagram based on the obtained multiple entity information and the relationships between the multiple entity information, and returns the constructed central architecture diagram to the frontend server. Then, the frontend server optimizes the central architecture diagram and presents the optimized central architecture diagram to the user. In addition, the user can also expand or collapse any node in the ring layer of the central architecture diagram through the frontend server, or change the central node of the central architecture diagram. The backend server updates the central architecture diagram according to the above interactive operations, and then the frontend server presents the updated central architecture diagram to the user.

[0081] The architecture diagram building system 100 can also be deployed in a distributed manner in different environments, including terminal computing devices and data centers in cloud environments. For example, the acquisition module 101 and layout module 102 of the architecture diagram building system 100 are deployed in a data center in a cloud environment, while the visualization module 103 and interaction module 104 are deployed on terminal computing devices.

[0082] The following description of the architecture diagram construction system 100, based on the scenarios depicted in Figures 3A-3I, is from the user's perspective.

[0083] This embodiment uses an enterprise process architecture diagram as an example. Through the enterprise process architecture diagram, users can understand the relationship between enterprise processes, such as the hierarchy, classification and boundaries / scope of enterprise processes, as well as the integration relationship between enterprise processes (such as the input / output relationship between enterprise processes).

[0084] As shown in Figure 3A, the architecture diagram building system 100 provides a user interface, which includes a toolbar, a directory bar, and a display bar. The toolbar includes editing tools for the architecture diagram, such as undo, redo, refresh, favorite, and download buttons. The directory bar displays relevant information about enterprise processes, specifically including the code, name, and hierarchy information of the corresponding process architecture. For example, the process architecture information displayed in the directory bar shown in Figure 3A includes: code 1.0, name "Integrated Product Development"; code 2.0, name "Management Finance"; code 3.0, name "Management Business Change and Information Technology (Management BT&IT)"; code 4.0, name "Channel Sales"; code 5.0, name "Carrier Business CRM," etc. The display bar is used to show the user the central architecture diagram.

[0085] When a user sequentially opens "2.0 Management Finance" and "2.5 Management Pricing" in the directory bar, the architecture diagram building system 100 detects the operation on the directory bar and, in response, displays the global architecture diagram in the display bar. The global architecture diagram includes nodes 1.0, 3.0 to 5.0, 2.1 to 2.7, and the child nodes associated with node 2.5 (i.e., nodes 2.5.1 to 2.5.6), as well as the edges between these nodes. Node 1.0 indicates a process architecture coded as 1.0 and named "Integrated Product Development"; node 3.0 indicates a process architecture coded as 3.0 and named "Managing BT&IT"; node 4.0 indicates a process architecture coded as 4.0 and named "Channel Sales"; and so on, with each node in the global architecture diagram indicating a process architecture. The edges in the global architecture diagram indicate the integration relationships between the process architectures indicated by the nodes at both ends of the edge; the integration relationships between the process architectures indicated by each edge are not described in detail here. Users can observe the process architecture under "Manage Pricing" (e.g., "Manage Business Model and Pricing Planning", "Manage Product Pricing") and the relationship between these process architectures and other process architectures (e.g., "Integrate Product Development", "Manage Plan Budget Forecasting").

[0086] As shown in Figure 3B, when a user wants to focus on "Management Pricing Review and Forecasting," the user can select the "Open Central Exploration Mode" option for node 2.5.5 in the global architecture diagram shown in Figure 3A. Correspondingly, the architecture diagram building system 100 detects the operation performed on node 2.5.5 and, in response, displays the central architecture diagram in the display bar. As can be seen from the figure, the central node of the central architecture diagram is node 2.5.5, and the other nodes are arranged in three ring-shaped layers centered on node 2.5.5, according to the hierarchical structure of the process architecture indicated by the nodes (L1, L2, L3 shown in the figure). The central architecture diagram also includes the edges connecting node 2.5.5, namely the edges between node 2.5.5 and node 5.0, node 2.5.5 and node 2.1, node 2.5.5 and node 2.7, node 2.5.5 and node 2.5.1, node 2.5.5 and node 2.5.2, node 2.5.5 and node 2.5.3, and node 2.5.5 and node 2.5.4. Compared to the global architecture diagram shown in Figure 3A, the central architecture diagram shown in Figure 3B provides users with another perspective on "managed pricing review and prediction," making it easier for users to focus on "managed pricing review and prediction" based on the central architecture diagram.

[0087] As shown in Figure 3C, when a user wants to further explore the relationship between "Management Pricing Review and Forecasting" and "Management Plan Budget Forecasting," the user can select node 2.1 in the middle ring layer of the central architecture diagram and move it to the outer ring layer. Correspondingly, the architecture diagram building system 100 detects the operation on node 2.1, updates the central architecture diagram, and displays the updated central architecture diagram in the display bar. As can be seen from the figure, the updated central architecture diagram adds nodes 2.1.1 to 2.1.3, and the edge between nodes 2.1.2 and 2.5.5, while hiding node 2.6 and the edge between node 2.6 and 2.5.5. Therefore, based on the updated central architecture diagram, the user can observe that the process architecture under "Management Plan Budget Forecasting" includes "Management Budget Generation," "Management Budget Execution," and "Management Business Planning," and that only "Management Budget Execution" and "Management Pricing Review and Forecasting" have an integration relationship, along with details of this integration relationship.

[0088] As shown in Figure 3D, when a user wants to focus on "Managing Product Pricing," they can select node 2.5.2 in the outer ring layer of the central architecture diagram and move it to the area where node 2.5.5 is located. Correspondingly, the architecture diagram building system 100 detects the operation on node 2.5.2, updates the central architecture diagram, and displays the updated central architecture diagram in the display bar. As can be seen from the figure, the central node of the updated central architecture diagram is node 2.5.2, and the other nodes are arranged in three ring layers around node 2.5.2. The updated central architecture diagram also includes the edges connected to node 2.5.2, namely the edge between node 2.5.2 and node 2.2, the edge between node 2.5.2 and node 2.1.1, the edge between node 2.5.2 and node 2.5.1, the edge between node 2.5.2 and node 2.5.4, and the edge between node 2.5.2 and node 2.5.5. This central architecture diagram provides the user with another perspective on "Managing Product Pricing," making it easier for the user to focus on this aspect.

[0089] In addition, as shown in Figure 3E, when a user wants to focus on "Managing Product Pricing," they can hover the mouse over node 2.5.5 in the central architecture diagram. Accordingly, the architecture diagram building system 100 detects the operation on node 2.5.5 and, in response, displays the nodes corresponding to the L3 level process architecture near node 2.5.5 (shown as nodes 2.5.1 and 2.5.2 in the figure). Then, as shown in Figure 3F, the user selects node 2.5.2 near node 2.5.5 and moves it to the area where node 2.5.5 is located. Correspondingly, the architecture diagram building system 100 detects the operation on node 2.5.2, updates the central architecture diagram, and displays the updated central architecture diagram in the display bar. As can be seen from the figure, the central node of the updated central architecture diagram is node 2.5.2, and the other nodes are arranged in three ring layers around node 2.5.2. The updated central architecture diagram also includes the edges connecting node 2.5.2, namely the edges between nodes 2.5.2 and 2.2, between nodes 2.5.2 and 2.1.1, between nodes 2.5.2 and 2.5.1, between nodes 2.5.2 and 2.5.4, and between nodes 2.5.2 and 2.5.5. This central architecture diagram provides users with an alternative perspective on "managing product pricing," allowing them to focus on this aspect.

[0090] As shown in Figure 3E, when a user hovers the mouse over node 2.5.5 in the central architecture diagram, the architecture diagram building system 100 displays nodes corresponding to the L3 level process architecture near node 2.5.5. As shown in Figure 3G, when a user wants to display nodes corresponding to the L1 level process architecture near node 2.5.5, the user can click the "Up" button above node 2.5.5 and set the level to "L1". Correspondingly, the architecture diagram building system 100 detects this operation and, in response, displays nodes corresponding to the L1 level process architecture near node 2.5.5 (shown as nodes 1.0 and 2.0 in the figure). When a user wants to focus on "Management Finance", as shown in Figure 3H, the user selects node 2.0 and moves it to the area where node 2.5.5 is located. Correspondingly, the architecture diagram building system 100 detects the operation performed on node 2.0, updates the central architecture diagram, and displays the updated central architecture diagram in the display bar. As shown in the diagram, the central node of the updated central architecture is node 2.0, with other nodes arranged around it. The updated central architecture also includes edges on node 2.0, such as the edges between node 2.0 and node 1.0, node 2.0 and node 3.0, node 2.0 and node 4.0, and node 2.0 and node 5.0. This central architecture provides users with an alternative perspective on "managing finances," allowing them to focus on this aspect.

[0091] As shown in Figure 3I, when a user wants to view the upper-level process architecture of "Management Budget Generation," the user can select node 2.1.1 in the outer ring layer of the central architecture diagram and move it to the middle ring layer. Correspondingly, the architecture diagram building system 100 detects the operation on node 2.1.1, updates the central architecture diagram in response, and displays the updated central architecture diagram in the display bar. As can be seen from the figure, the updated central architecture diagram adds node 2.1 and the edge between node 2.1 and node 2.5.2, while hiding the edges between nodes 2.1.1 and 2.1.3, and between node 2.1.1 and node 2.5.2. Based on the updated central architecture diagram, the user can observe that the upper-level process architecture of "Management Budget Generation," "Management Budget Execution," and "Management Business Planning" is "Management Plan Budget Forecasting," and the integration relationship between "Management Plan Budget Forecasting" and "Management Product Pricing."

[0092] It should be understood that, for ease of displaying the architecture diagram, the user interface shown in Figures 3B-3I hides the directory bar. It should also be understood that Figures 3A-3I merely illustrate one application scenario of the architecture diagram building system 100. In practical applications, the architecture diagram building system 100 can also be applied to various other scenarios. For example, the central architecture diagram built by the architecture diagram building system 100 can also be an organizational chart to present the organizational structure and functional relationships of an enterprise to users. As another example, the central architecture diagram built by the architecture diagram building system 100 can also be an architecture diagram of a network directory to present the network directory to users, facilitating their search and browsing of the information they need.

[0093] The following description, in conjunction with the flowchart of the architecture diagram generation method shown in Figure 4, further describes the functions of the architecture diagram construction system 100.

[0094] S101: Architecture diagram construction system 100 obtains information on multiple entities and the relationships between them.

[0095] The description of entity information and the relationships between entity information can be found in the previous text and will not be repeated here.

[0096] Specifically, the architecture diagram construction system 100 can obtain information on multiple entities and the relationships between them in any of the following ways:

[0097] Method 1: Architecture Diagram Construction System 100 obtains information on multiple entities and the relationships between them from the database.

[0098] Specifically, the database stores information about multiple entities and the relationships between them. The architecture diagram building system 100 can access this database to obtain information about multiple entities and the relationships between them.

[0099] Method 2: Architecture Diagram Construction System 100 receives user (e.g., administrator user) input operations and obtains multiple entity information and the relationships between multiple entity information based on the user input operations.

[0100] Specifically, the architecture diagram building system 100 provides access interfaces, such as application programming interfaces (APIs) and graphical user interfaces (GUIs). Users can upload file packages to the architecture diagram building system 100 through these interfaces. These file packages contain information on multiple entities and the relationships between them. Upon receiving the uploaded file package, the architecture diagram building system 100 can parse it to obtain the information on the entities and the relationships between them. Furthermore, users can also use these access interfaces to create information on multiple entities and the relationships between them on the architecture diagram building system 100, enabling the system to access and obtain this information.

[0101] S102: Architecture diagram construction system 100 constructs a central architecture diagram based on information about multiple entities and the relationships between them.

[0102] Specifically, the architecture diagram construction system 100 determines first entity information, which is one of multiple entity information. Then, the architecture diagram construction system 100 constructs a central architecture diagram based on the first entity information and the relationships between the multiple entity information. The central architecture diagram includes a central node, which is used to indicate the first entity information. The central architecture diagram also includes multiple ring layers centered on the central node. Each ring layer includes at least one node, and the nodes in different ring layers have different relationships with the central node.

[0103] Alternatively, the ring layer can have various shapes, such as circles, ellipses, triangles, squares, pentagons, etc. For example, in the central architecture diagram shown in Figure 3B above, the ring layer is circular.

[0104] Optionally, the central architecture diagram also includes edges connecting the central nodes, which indicate the relationships between the entity information indicated by the nodes at both ends of the edge. It should be understood that when the central architecture diagram does not include edges between the nodes of the ring layer, users can more intuitively observe the relationships between the entity information indicated by the central node and other entity information.

[0105] In some embodiments, the first entity information may be user-specified. Specifically, after acquiring multiple entity information and the relationships between them, the architecture graph construction system 100 constructs and displays a global architecture graph. The global architecture graph includes multiple nodes and multiple edges. Each node in the global architecture graph indicates one of the aforementioned entity information, and the edges in the global architecture graph indicate the relationships between the entity information indicated by the nodes at both ends of the edge. Then, the architecture graph construction system 100 receives information generated by the user clicking on the first node in the global architecture graph, and then determines the first entity information corresponding to the first node based on this information.

[0106] The first entity information can also be dynamically determined by the architecture diagram building system 100 based on the actual situation. For example, the architecture diagram building system 100 may randomly select the first entity information from multiple entity information.

[0107] In some embodiments, the global architecture diagram includes hierarchical relationships between nodes. For example, in the global architecture diagram described in Figure 3A above, nodes 1.0, 3.0 to 5.0 are nodes at the same level, nodes 2.1 to 2.5 are nodes at the same level, nodes 2.5.1 to 2.5.6 are nodes at the same level, and nodes 2.5.1 to 2.5.6 are child nodes of node 2.5. Therefore, the architecture diagram construction system 100 constructs a central architecture diagram based on the first entity information and the relationships between the first entity information, including: the architecture diagram construction system 100 determines the hierarchy of the aforementioned multiple entity information based on the hierarchical relationships between nodes in the global architecture diagram, and then determines the arrangement of nodes in multiple ring layers based on the hierarchy of the aforementioned multiple entity information. Afterwards, the architecture diagram construction system 100 constructs a central architecture diagram based on the arrangement of nodes in the multiple ring layers. In this central architecture diagram, nodes in the same ring layer indicate the same level of entity information, and nodes in different ring layers indicate different levels of entity information. Accordingly, the different relationships between nodes in different ring layers and the central node may include: the relationship between the hierarchy of entity information indicated by nodes in different ring layers and the hierarchy of the first entity information is different.

[0108] Optionally, the entity information indicated by nodes in the first ring layer is at a lower level than the entity information indicated by nodes in the second ring layer. The first ring layer is farther from the central node than the second ring layer. For example, in the central architecture diagram shown in Figure 3B above, the entity information indicated by nodes in the outer ring layer is at level L3, the entity information indicated by nodes in the middle ring layer is at level L2, and the entity information indicated by nodes in the inner ring layer is at level L1. It should be understood that when a user observes the first entity information indicated by the central node, they may need to expand the entity information related to the first entity information. This will cause the ring layer containing the lower-level nodes to add nodes corresponding to the expanded entity information, while the ring layer containing the higher-level nodes will hide the nodes corresponding to the expanded entity information. By placing the ring layer containing the lower-level nodes on the outer side and the ring layer containing the higher-level nodes on the inner side, the arrangement of nodes in the central architecture diagram can be made more reasonable and aesthetically pleasing.

[0109] In some embodiments, the architecture diagram construction system 100 determines the arrangement of nodes in multiple ring layers based on the hierarchy of multiple entity information, including: the architecture diagram construction system 100 determines the number of nodes in each ring layer based on the hierarchy of multiple entity information, and then determines the arrangement of nodes in each ring layer based on the number of nodes in each ring layer. Optionally, to improve the visual effect of the central architecture diagram, the nodes in the ring layers can be evenly arranged in the corresponding ring layers.

[0110] Since a ring layer may include multiple nodes, these nodes may include nodes connected to the central node or nodes not connected to the central node. To facilitate users' exploration of the relationship between the entity information indicated by the central node and other entity information, nodes connected to the central node and nodes not connected to the central node can be represented using primitives of different sizes. For simplicity, the size of the primitive corresponding to the node will be referred to as the node size below. As an example, the size of the ring layer node connected to the central node is larger than the size of the ring layer node not connected to the central node. For example, in the architecture diagram shown in Figure 3B above, node 2.1 is connected to the central node (i.e., node 2.5.5), node 2.2 is not connected to the central node, and the size of node 2.1 is larger than the size of node 2.2. Therefore, the architecture diagram construction system 100 determines the arrangement of nodes in the ring layer based on the number of nodes in the ring layer, including: the architecture diagram construction system 100 determines the arrangement of nodes in the ring layer based on the number and size of nodes in the ring layer.

[0111] For example, taking Figure 3B above as an example, this describes how the architecture diagram construction system 100 constructs the central architecture diagram shown in Figure 3B.

[0112] The architecture diagram construction system 100 receives a user's click on node 2.5.1 in the global architecture diagram and selects the option to "open the central exploration mode." Based on this operation, the system determines the first entity information indicated by node 2.5.1, and then determines the central node of the central architecture diagram as the node used to indicate the first entity information. The architecture diagram construction system 100 also determines the hierarchy of the entity information indicated by the nodes in the global architecture diagram based on the hierarchical relationship between the nodes. Specifically, the entity information indicated by nodes 1.0 and nodes 3.0 to 5.0 in the global architecture diagram has the same hierarchy, which is L1 shown in Figure 3B; the entity information indicated by nodes 2.1 to 2.7 has the same hierarchy, which is L2 shown in Figure 3B; the entity information indicated by nodes 2.5.1 to 2.5.6 has the same hierarchy, which is L3 shown in Figure 3B; and L1 is higher than L2, and L2 is higher than L3. Subsequently, the architecture diagram construction system determines that the central architecture diagram includes three ring layers based on the hierarchy of entity information indicated by the nodes in the global architecture diagram. The first ring layer includes nodes 1.0 and 3.0 to 5.0; the second ring layer includes nodes 2.1 to 2.4, 2.6, and 2.7; and the third ring layer includes nodes 2.5.1 to 2.5.4 and 2.5.6. The arrangement of the above three ring layers is the first ring layer, the second ring layer, and the third ring layer in sequence.

[0113] For the nodes in the first ring layer, since this layer includes 4 nodes, and the entity information indicated by node 5.0 among these 4 nodes has an integration relationship with the entity information indicated by the central node (i.e., node 2.5.5), the size of node 5.0 is larger than the size of the other 3 nodes. Based on this, nodes 1.0, 3.0 to 5.0 can be evenly arranged on the first ring layer. For the nodes in the second ring layer, since this layer includes 6 nodes, and the entity information indicated by nodes 2.1 and 2.7 among these 6 nodes has an integration relationship with the entity information indicated by the central node, the size of nodes 2.1 and 2.7 is larger than the size of the other 4 nodes. Based on this, nodes 2.1 to 2.4, 2.6, and 2.7 can be evenly arranged on the second ring layer. For the nodes in the third ring layer, since this layer includes 5 nodes, and the entity information indicated by nodes 2.5.1 to 2.5.4 among these 5 nodes has an integration relationship with the entity information indicated by the central node, the size of node 2.5.6 is smaller than the size of the other 4 nodes. Based on this, nodes 2.5.1 to 2.5.4 and node 2.5.6 can be evenly arranged on the third ring layer. The specific arrangement of nodes in the above three ring layers can be seen in the central architecture diagram shown in Figure 3B. It should be understood that the arrangement of nodes in each ring layer in the central architecture diagram shown in Figure 3B is only an example. In practical applications, other arrangements are also possible; for example, the positions of nodes 1.0 and 5.0 in the first ring layer can be interchanged.

[0114] S103: Architecture Diagram Construction System 100 Display Center Architecture Diagram.

[0115] To further improve the visualization of the central architecture diagram, the architecture diagram construction system 100 may also perform the following steps (i.e., S104) before executing S103 above.

[0116] S104: Architecture diagram construction system 100 optimization center architecture diagram.

[0117] Specifically, the architecture diagram building system 100 can optimize the central architecture diagram through any one or more of the following steps:

[0118] Step 1: Architecture Diagram Construction System 100 determines the position of the endpoint of the edge on the corresponding node based on the relative positions of the nodes at both ends of the edge.

[0119] Since the central node of the central architecture graph may be connected to multiple nodes in the ring layer, meaning the central node may have multiple edges connected to it, these edges may intersect and overlap. To reduce the intersection and overlap of edges in the central architecture graph, the architecture graph construction system 100 can determine the position of the endpoints of the edges between the central node and the nodes in the ring layer it connects to on the corresponding nodes. For example, in the central architecture graph shown in Figure 3B above, the central node (i.e., node 2.5.5) is connected to 7 nodes in the ring layer, and there is no intersection or overlap between these 7 edges.

[0120] Step 2: The architecture diagram construction system 100 configures different primitives for the nodes of the ring layer connected to the central node and the nodes of other ring layers. These different primitives include primitives of different sizes, primitives of different colors, primitives of different shapes, etc. For example, in the central architecture diagram shown in Figure 3B above, the size of the nodes of the ring layer connected to the central node (i.e., node 2.5.5) (e.g., node 5.0 and node 2.1) is larger than the size of the nodes of other ring layers.

[0121] Step 3: The architecture diagram construction system 100 displays the hierarchy of entity information indicated by any one or more nodes in the central architecture diagram, so that users can easily understand the hierarchy of entity information indicated by each node in the central architecture diagram. For example, in the central architecture diagram shown in Figure 3B above, the hierarchy of entity information indicated by the central node (i.e., node 2.5.5) is displayed above it (i.e., L3 in the figure), the hierarchy of entity information indicated by the nodes of that layer is displayed near the inner ring layer (i.e., L1 in the figure), the hierarchy of entity information indicated by the nodes of that layer is displayed near the middle ring layer (i.e., L2 in the figure), and the hierarchy of entity information indicated by the nodes of that layer is displayed near the outer ring layer (i.e., L3 in the figure).

[0122] Step 4: The architecture diagram building system 100 sets the position of the central node to the middle position of the canvas.

[0123] The canvas refers to the display area of ​​the central architecture diagram. It should be understood that when the central node is located in the middle of the canvas, since the nodes in the ring layer are arranged around the central node, this step can make the entire central architecture diagram located in the middle area of ​​the canvas, thereby improving the visual effect of the central architecture diagram.

[0124] Step 5: The architecture diagram construction system 100 configures the start or end point of any one or more edges in the central architecture diagram as different graphical elements. These different graphical elements include elements with different colors, shapes, and sizes. For example, for a unidirectional edge in the architecture diagram, the start point can be represented by a circle, and the end point by an arrow.

[0125] Step 6: Architecture Diagram Construction System 100 displays the identifiers of any one or more nodes in the central architecture diagram.

[0126] The node identifier includes the code and / or name of the corresponding entity information. For example, in the central architecture diagram shown in Figure 3B above, the node identifier includes the name and code of the process architecture.

[0127] Step 7: The architecture diagram construction system 100 configures the central node and the nodes in the ring layer as different primitives. These different primitives include primitives of different sizes, primitives of different colors, and primitives of different shapes. For example, in the central architecture diagram shown in Figure 3B above, the size of the central node is larger than the size of the nodes in the ring layer.

[0128] Step 8: The architecture diagram construction system 100 configures the nodes in different ring layers of the central architecture diagram as different primitives, including primitives of different sizes, primitives of different colors, primitives of different shapes, etc.

[0129] Step 9: The architecture diagram construction system 100 configures the edges between the central node and the nodes in different ring layers as different line segments, including line segments with different colors or different thicknesses.

[0130] After viewing the central architecture diagram displayed by the architecture diagram building system 100, users may still need to manipulate the central architecture diagram. For example, they may expand a node in the central architecture diagram to view the lower-level entity information associated with the entity information indicated by the expanded node. Or, they may collapse a node in the central architecture diagram to view the upper-level entity information associated with the entity information indicated by the collapsed node. Furthermore, they may change the central node of the central architecture diagram as needed to focus on the entity information indicated by the new central node. Therefore, after executing S103 above, the architecture diagram building system 100 may also execute the following steps (i.e., S105):

[0131] S105: In response to user input, the architecture diagram building system 100 updates the central architecture diagram and displays the updated central architecture diagram.

[0132] This step is described below using the following three scenarios:

[0133] Scenario 1: The user input operation is node a in the ring layer a of the expanded central architecture diagram.

[0134] Specifically, the architecture diagram building system 100 receives user input to expand node a, then updates the central architecture diagram based on the operation of expanding node a, and then displays the updated central architecture diagram. It should be understood that this embodiment does not limit the operation by which the user expands node a. For example, it could be selecting node a and moving it to ring layer b, where the entity information indicated by the node in ring layer a is at a higher level than the entity information indicated by the node in ring layer b. Another example is selecting relevant options for expanding node a in the user interface, or filling in relevant information for expanding node a in the user interface.

[0135] In some embodiments, node a is any node in ring layer a, and node a indicates the second entity information among the aforementioned plurality of entity information, the second entity information being associated with one or more lower-level entity information. Then, the architecture graph construction system 100 updates the central architecture graph according to the aforementioned operation of expanding node a, including: the architecture graph construction system 100 hides node a in ring layer a, and displays the child nodes associated with node a in ring layer b, wherein the child nodes associated with node a indicate the entity information below the second entity information. Additionally, when node a is connected to the central node by an edge, the architecture graph construction system 100 also hides the edge between node a and the central node, and displays the edge between the child nodes associated with node a and the central node. It should be understood that the updated central architecture graph may include one or more child nodes associated with node a. When the graph includes one child node associated with node a, that child node indicates one entity information below the second entity information. When the graph includes multiple child nodes associated with node a, each of the multiple child nodes indicates one entity information below the second entity information.

[0136] In some embodiments, the architecture graph construction system 100 displays child nodes associated with node a in a ring layer b, including: the architecture graph construction system 100 determines the arrangement of child nodes associated with node a based on the number of child nodes associated with node a, and then displays the child nodes associated with node a in the ring layer b. More specifically, the architecture graph construction system 100 determines the size of the child nodes associated with node a based on the relationship between the entity information indicated by the child nodes associated with node a and the first entity information, and then determines the arrangement of the child nodes associated with node a based on the number and size of the child nodes associated with node a, thereby displaying the child nodes associated with node a on the ring layer b.

[0137] Optionally, the ring layer b also includes node b, wherein the number of nodes b can be one or more. The architecture graph construction system 100 also adjusts the position of node b in the ring layer b so that node b is not obscured by the child nodes associated with node a when the updated central architecture graph is displayed. In some embodiments, node b can be a node affected by the above-described expansion operation, that is, after the child nodes associated with node a are displayed in the ring layer b, if the position of node b is not adjusted, node b will be obscured by the child nodes associated with node a. Specifically, the architecture graph construction system 100 can adjust the position of node b in the following way: the architecture graph construction system 100 adjusts the position of node b according to the position of the child nodes associated with node a.

[0138] Optionally, the ring layer a includes nodes c, where the number of nodes c can be one or more. The architecture diagram construction system 100 also adjusts the position of nodes c in the ring layer a to make the arrangement of nodes in the ring layer a reasonable and aesthetically pleasing when the updated central architecture diagram is displayed. In some embodiments, node c can be a node affected by the above-described expansion operation; that is, after hiding node a in the ring layer a, if the position of node c is not adjusted, the spacing between node c and its adjacent nodes will be large, thus affecting the visual effect of the architecture diagram. In a specific implementation, the architecture diagram construction system 100 can adjust the position of node c in the following way: the architecture diagram construction system 100 adjusts the position of node c according to the position of node a in the original central architecture diagram.

[0139] For example, taking the central architecture diagram shown in Figure 3C above as an example, this describes how the architecture diagram building system 100 updates the central architecture diagram based on user input of node expansion operations. As shown in Figure 3C, when the architecture diagram building system 100 detects the user input of expanding node 2.1 (i.e., selecting node 2.1 and moving it to the outer ring layer), in response to this operation, the architecture diagram building system 100 hides node 2.1 in the middle ring layer, as well as the edge between node 2.1 and node 2.5.5, and displays the child nodes of node 2.6 (i.e., nodes 2.1.1 to 2.1.3), as well as the edge between node 2.1.2 and node 2.5.5 in the outer ring layer. The architecture diagram building system 100 also adjusts the arrangement of nodes in the middle and outer ring layers accordingly, so that the nodes in these two ring layers are evenly distributed.

[0140] Scenario 2: The user input is to collapse node d in the ring layer c of the central architecture diagram.

[0141] Specifically, the architecture diagram construction system 100 receives a user input to collapse node d, then updates the central architecture diagram based on the collapse operation, and finally displays the updated central architecture diagram. It should be understood that this embodiment does not limit the operation by which the user collapses node d. For example, it could be by selecting node d and moving it to ring layer d, where the entity information indicated by the node in ring layer d is at a higher level than the entity information indicated by the node in ring layer c. Another example is selecting relevant options for collapsing node d in the user interface, or filling in relevant information for collapsing node d in the user interface.

[0142] In some embodiments, the architecture graph construction system 100 updates the central architecture graph according to the above-described operation of collapsing node d, including: the architecture graph construction system 100 hides node d and / or node s in the ring layer c, and displays the parent and child points of node d in the ring layer d, wherein node d indicates the third entity information among the plurality of entity information, node s indicates the fourth entity information among the plurality of entity information, the parent node associated with node d and the parent node associated with node s are the same node, and the lower-level entity information associated with the entity information indicated by the parent node associated with node d includes the third entity information and the fourth entity information. Additionally, when node d is connected to the central node through an edge, the architecture graph construction system 100 also hides the edge between node d and the central node, and displays the edge between the parent node associated with node d and the central node.

[0143] In some embodiments, the architecture graph construction system 100 displays the parent node associated with node d in a ring layer d, including: the architecture graph construction system 100 determines the arrangement of nodes d, and then displays nodes d in the ring layer d. More specifically, the architecture graph construction system 100 determines the size of node d based on the relationship between the entity information indicated by node d and the entity information indicated by the center node, and then determines the arrangement of nodes d based on the size of node d, thereby displaying nodes d in the ring layer d.

[0144] Optionally, the ring layer d also includes nodes e, where the number of nodes e can be one or more. The architecture graph construction system 100 also adjusts the position of nodes e in the ring layer d so that when the updated central architecture graph is displayed, node e is not obscured by the parent node associated with node d. In some embodiments, node e may be a node affected by the above-described collapse operation, that is, after the parent node associated with node d is displayed in the ring layer d, if the position of node e is not adjusted, node e will be obscured by the parent node associated with node d. Specifically, the architecture graph construction system 100 can adjust the position of node e in the following way: the architecture graph construction system 100 adjusts the position of node e according to the position of the parent node associated with node d.

[0145] Optionally, the ring layer c also includes nodes f, where the number of nodes f can be one or more. The architecture graph construction system 100 also adjusts the position of nodes f in the ring layer c to make the node arrangement in the ring layer c reasonable and aesthetically pleasing when the updated central architecture graph is displayed. In some embodiments, node f can be a node affected by the above-mentioned collapse operation, that is, after hiding nodes d and / or s in the ring layer c, if the position of node f is not adjusted, the spacing between node f and its adjacent nodes will be large, thereby affecting the visual effect of the central architecture graph. In a specific implementation, the architecture graph construction system 100 can adjust the position of node f in the following way: the architecture graph construction system 100 adjusts the position of node f according to the position of nodes d and / or s in the original central architecture graph.

[0146] For example, taking the central architecture diagram shown in Figure 3I above as an example, this describes how the architecture diagram building system 100 updates the central architecture diagram based on the user's input of collapsing a node. As shown in Figure 3I, when the architecture diagram building system 100 detects the user's input of collapsing node 2.1.1 (i.e., selecting node 2.1.1 and moving it to the middle ring layer), in response to this operation, the architecture diagram building system 100 hides nodes 2.1.1 to 2.1.3 in the outer ring layer, as well as the edge between node 2.1.1 and node 2.5.2, and displays the parent node of node 2.1.1 (i.e., node 2.1) and the edge between node 2.1 and node 2.5.2 in the middle ring layer. The architecture diagram building system 100 also adjusts the arrangement of nodes in the middle and outer ring layers accordingly, so that the nodes in these two ring layers are evenly distributed.

[0147] Scenario 3: The user input is to change the central node in the central architecture diagram.

[0148] Specifically, the architecture diagram building system 100 receives user input indicating a change of the central node, updates the central architecture diagram based on this change, and then displays the updated central architecture diagram. The updated central architecture diagram includes the new central node and nodes in multiple ring layers centered on the new central node. The updated central architecture diagram also includes edges between the new central node and the nodes in the ring layers.

[0149] In some embodiments, users can change the central node in the central architecture diagram using any one or more of the following methods:

[0150] Method 1: The user selects node m in the annular layer m and moves it to the area where the original center node was located. The area where the original center node was located includes the original center node's position and its surrounding area. For example, in Figure 3D above, the user selects node 2.5.2 in the outer annular layer and moves it to the position of the center node (i.e., node 2.5.5), thereby replacing the original center node with node 2.5.2.

[0151] Method 2: The user selects a replaceable section and moves it to the area where the original central node is located. The replaceable section can be a node displayed in the central architecture diagram when the architecture diagram building system 100 detects the user's operation on the original central node.

[0152] Optionally, the user's actions on the original central node can be varied. For example, the user can click on the original central node, or the user can hover the mouse over the original central node (as shown in Figure 3E above, after the user hovers the mouse over node 2.5.5, the architecture diagram building system 100 will display nodes 2.5.1 and 2.5.2 near node 2.5.5). This embodiment of the application does not limit this.

[0153] Optionally, the number of replaceable nodes can be one or more, and the replaceable nodes can be located near the original central node. To facilitate user observation of replaceable nodes, the architecture diagram construction system 100 can configure different primitives for replaceable nodes and other nodes (including the original central node and nodes in the ring layer). For example, replaceable nodes can be represented using primitives in a rotated state, while other nodes can be represented using primitives in a stationary state. Alternatively, replaceable nodes and other nodes can be represented using primitives with different colors, sizes, or shapes. Taking the central architecture diagram shown in Figure 3E above as an example, the replaceable nodes (i.e., nodes 2.5.1 and 2.5.2) are located near the original central node (i.e., node 2.5.5), and the color and size of the replaceable nodes are different from those of the original central node and the nodes in the ring layer.

[0154] Optionally, replaceable nodes can indicate entity information already indicated by nodes in the central architecture diagram. For example, the entity information indicated by the two replaceable nodes shown in Figure 3E corresponds to the entity information indicated by nodes 2.5.1 and 2.5.2 in the outer ring layer of the diagram. Replaceable nodes can also indicate entity information indicated by nodes not shown in the central architecture diagram. For example, the replaceable nodes shown in Figure 3G include node 2.0, which is not displayed in the central architecture diagram. In this way, users can flexibly select entity information to explore.

[0155] Optionally, replaceable nodes can be specified by the user based on the hierarchy indicated by the entity information. As an example, the central architecture diagram includes hierarchy up / down buttons. When the user hovers the mouse over the original central node, the replaceable nodes displayed in the central architecture diagram are at the same hierarchy as the entity information indicated by the original central node. For example, in Figure 3E above, the replaceable nodes in the central architecture diagram (i.e., nodes 2.5.1 and 2.5.2) are at the same hierarchy as the original central node (i.e., node 2.5.5), both being L3. When the user clicks the hierarchy up / down buttons, the hierarchy of the entity information indicated by the replaceable nodes displayed in the central architecture diagram differs from the hierarchy indicated by the original central node. For example, in Figure 3G above, by clicking the hierarchy up button, the user makes the replaceable nodes displayed in the central architecture diagram the nodes corresponding to the entity information at hierarchy L1 (i.e., nodes 1.0 and 2.0 in the diagram).

[0156] It should be understood that in practical applications, users can also achieve the purpose of changing the central node through other operations. For example, users can select relevant options for changing the central node in the user interface, or fill in relevant information for changing the central node in the user interface. This application embodiment does not limit this.

[0157] In some embodiments, the architecture diagram construction system 100 updates the central architecture diagram based on the operation of changing the central node, including: the architecture diagram construction system 100 determines a new central node and nodes in multiple ring layers centered on the new central node, then determines the arrangement of the aforementioned nodes, and obtains the updated central architecture diagram based on the arrangement of the aforementioned nodes. The position of the new central node is the same as the position of the original central node, and other nodes are arranged in at least one ring layer centered on the new central node. It should be understood that, for simplicity, this step does not describe in detail how the architecture diagram construction system 100 determines the arrangement of nodes in the ring layers of the updated central architecture diagram; for details, please refer to the relevant steps in S102 above.

[0158] Optionally, since the technical solution provided in this application embodiment is to provide users with another perspective for observing the entity information indicated by the central node, the nodes of the ring layer in the updated central architecture diagram can be determined by the architecture diagram building system 100 based on the new central node. For example, they can include nodes corresponding to entity information that has an integration relationship with the entity information indicated by the new central node.

[0159] In conjunction with the architecture diagram construction system 100 shown in Figure 1 above, the acquisition module 101, layout module 102, visualization module 103, and interaction module 104 work together to implement the steps performed by the architecture diagram construction system 100 in the method embodiment described in Figure 4 above. Specifically, the acquisition module 101 is used to execute S101. The layout module 102 is used to execute one or more of the following steps: the steps related to updating the central architecture diagram in S102 and S105. The visualization module 103 is used to execute one or more of the following steps: the steps related to displaying the updated central architecture diagram in S103, S104, and S105. The interaction module 104 is used for one or more of the following steps: receiving the user's click operation on the first node in the global architecture diagram in S102, and receiving the user's input operation on the central architecture diagram in S105.

[0160] This application embodiment also provides an architecture diagram display system. As shown in FIG5, the architecture diagram display system 200 includes a visualization module 201 and an interaction module 202. Optionally, the architecture diagram display system 200 further includes a layout module 203. Specifically, the visualization module 201 is used to perform one or more of the following steps: S103, S104, and the steps related to displaying the updated central architecture diagram in S105. The interaction module 202 is used to perform one or more of the following steps: receiving the user's click operation on the first node in the global architecture diagram in S102, and receiving the user's input operation on the central architecture diagram in S105. The layout module 203 is used to perform one or more of the following steps: the steps related to updating the central architecture diagram in S102 and S105.

[0161] In this embodiment of the application, the architecture diagram shows that system 200 can be a software system, a hardware device, or a combination of a software system and a hardware device.

[0162] When the architecture diagram display system 200 is a software system, it can be deployed in a data center within a cloud environment. For example, the architecture diagram display system 200 may be a cloud service provided by a cloud service provider. Specifically, the architecture diagram display system 200 can be deployed independently on a single computing instance within a cloud environment's data center, or distributed across multiple computing instances within the same cloud environment's data center. These computing instances include servers, virtual machines, and containers.

[0163] The architecture diagram display system 200 can also be deployed on terminal computing devices. For example, the architecture diagram display system 200 is source code or a component that can run on one or more terminal computing devices. In one possible deployment, the visualization module 201 and the interaction module 202 in the architecture diagram display system 200 are deployed on a front-end server, and the layout module 203 is deployed on a back-end server.

[0164] The architecture diagram display system 200 can also be deployed in a distributed manner in different environments, including terminal computing devices and data centers in cloud environments. For example, the visualization module 201 and the interaction module 202 of the architecture diagram display system 200 are deployed on terminal computing devices, while the layout module 203 is deployed in data centers in cloud environments.

[0165] This application also provides a computing device. This computing device can be a terminal computing device or a server in a data center within a cloud environment. As shown in FIG6, the computing device 300 includes a bus 301, a processor 302, a memory 303, and a communication interface 304. The processor 302, the memory 303, and the communication interface 304 communicate with each other via the bus 301.

[0166] Bus 301 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, only one line is used in Figure 6, but this does not mean that the computing device 300 has only one bus or one type of bus. Bus 301 can include pathways for transmitting information between various components of the computing device 300 (e.g., processor 302, memory 303, and communication interface 304).

[0167] Processor 302 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0168] Memory 303 may include volatile memory, such as random access memory (RAM). Memory 303 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0169] The memory 303 stores executable program code. The processor 302 executes the executable program code stored in the memory 303 to perform some or all of the steps in S101-S105 above. That is to say, the memory 303 stores program code for implementing the functions of the architecture diagram construction system 100 (including the acquisition module 101, the layout module 102, the visualization module 103, and the interaction module 104) and / or the architecture diagram display system 200 (including the visualization module 201, the interaction module 202, and the layout module 203).

[0170] The communication interface 304 uses transceiver modules such as, but not limited to, network interface cards and transceivers to enable communication between the computing device 300 and other devices or communication networks. For example, the computing device 300 displays a central architecture diagram to the user through the communication interface 304.

[0171] This application also provides a computing device cluster. The computing device cluster includes multiple computing devices, which may include one or more of the following: terminal computing devices, servers in a cloud environment's data center. As shown in Figure 7, the computing device cluster 400 includes multiple computing devices 300. These multiple computing devices 300 can be connected via a network (e.g., a wide area network or a local area network).

[0172] The memory 303 of multiple computing devices 300 in the computing device cluster 400 may store the same program code for executing some or all of the steps in S101-S105. Alternatively, the memory 303 of multiple computing devices 300 in the computing device cluster 400 may each store partial program code for executing some or all of the steps in S101-S105, that is, the combination of multiple computing devices 300 jointly executes some or all of the steps in S101-S105.

[0173] It should be understood that this application embodiment does not specifically limit which module in the architecture diagram building system 100 and / or architecture diagram display system 200 is deployed on which computing device 300. In practical applications, the deployment can be adaptively made according to the computing power or specific needs of the computing device 300. Taking the architecture diagram building system 100 as an example, considering how to present a central architecture diagram with better visualization effects to users (e.g., smooth interaction, timely page response, etc.), this application embodiment provides the deployment method shown in Figure 8. As shown in Figure 8, the computing device cluster 400 includes computing device 300A and computing device 300B. Computing device 300A and computing device 300B are connected through a network, specifically through the communication interface in each computing device. The memory 303 in computing device 300A stores instructions for implementing the functions of the acquisition module 101 and the layout module 102, and the memory 303 in computing device 300B stores instructions for implementing the functions of the visualization module 103 and the interaction module 104.

[0174] This application also provides a computer program product containing instructions. The computer program product may be a software or program product containing instructions that can run on a computing device or be stored on any available medium. When the computer program product is run on at least one computing device, it causes the at least one computing device to perform the central architecture diagram construction method described above.

[0175] This application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computing device can store, or a data storage device such as a data center containing one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital versatile discs, DVDs), semiconductor media (e.g., SSDs), etc. The computer-readable storage medium includes instructions that instruct the computing device to execute the method for constructing the central architecture diagram described above.

[0176] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of this application.

Claims

1. A method for constructing a central architecture diagram, characterized in that, The method includes: Obtain information on multiple entities and the relationships between them; Determine the first entity information, which is one of the plurality of entity information; Based on the relationship between the first entity information and the multiple entity information, a central architecture diagram is constructed; The central architecture diagram is shown, wherein the central node in the central architecture diagram is used to indicate the first entity information, and the central architecture diagram also includes multiple ring layers centered on the central node, each ring layer including at least one node, and the nodes of different ring layers have different relationships with the central node.

2. The method according to claim 1, characterized in that, After acquiring information about multiple entities and the relationships between them, the method further includes: Based on the multiple entity information and the relationships between the multiple entity information, a global architecture diagram is constructed and displayed, wherein each node in the global architecture diagram indicates one of the multiple entity information; The step of determining the first entity information includes: receiving information generated by a user clicking on a first node in the global architecture diagram, and determining the first entity information corresponding to the first node based on the information.

3. The method according to claim 2, characterized in that, The step of constructing a central architecture diagram based on the relationship between the first entity information and the plurality of entity information includes: The hierarchy of the multiple entity information is determined based on the hierarchical relationship between nodes in the global architecture diagram; Based on the hierarchy of the multiple entity information, the arrangement of the nodes of the multiple ring layers is determined, wherein the nodes of the same ring layer indicate the same hierarchy of entity information, and the nodes of different ring layers indicate different hierarchical levels of entity information. The central architecture diagram is constructed based on the arrangement of the nodes of the multiple ring layers.

4. The method according to any one of claims 1 to 3, characterized in that, The central architecture diagram is an enterprise process architecture diagram, which is used to represent the relationships between enterprise processes.

5. The method according to claim 3, characterized in that, The method further includes: The user input is received to expand any node in the first ring layer of the central architecture diagram. The any node is used to indicate the second entity information among the multiple entity information. The second entity information is associated with one or more lower-level entity information. The central architecture diagram is updated according to the operation of expanding any node, and the updated central architecture diagram is displayed. The updated central architecture diagram hides any node, and the updated central architecture diagram includes a second ring layer. The second ring layer includes one or more child nodes associated with any node. The child nodes associated with any node indicate the entity information below the second entity information.

6. The method according to claim 5, characterized in that, The operation of receiving the user input to expand any node in the first ring layer of the central architecture diagram includes: The system receives the user's operation of selecting any node and moving it to the area where the second ring layer is located.

7. The method according to claim 3, characterized in that, The method further includes: Receive the user's input to change the central node; The central architecture diagram is updated according to the operation of replacing the central node, and the updated central architecture diagram is displayed. The updated central architecture diagram includes the new central node and nodes in multiple ring layers centered on the new central node.

8. The method according to claim 7, characterized in that, The operation of receiving user input to change the central node includes: The system receives the user's operation of selecting any node in the third ring layer of the central architecture diagram and moving it to the area where the original central node was located; or, The system receives the user's operation of selecting a replaceable node and moving it to the area where the original central node is located. The replaceable node is the node displayed in the central architecture diagram when the operation acting on the original central node is detected.

9. The method according to claim 3, characterized in that, The method further includes: The user input is received to collapse the second node in the fourth ring layer of the central architecture diagram, where the second node is used to indicate the third entity information among the multiple entity information. The central architecture diagram is updated according to the operation of collapsing the second node, and the updated central architecture diagram is displayed. The updated central architecture diagram hides the second node and / or the third node in the fourth ring layer. The third node is used to indicate the fourth entity information in the plurality of entity information. The updated central architecture diagram also includes a fifth ring layer. The fifth ring layer includes the fourth node. The lower-level entity information associated with the entity information indicated by the fourth node includes the third entity information and the fourth entity information.

10. The method according to claim 9, characterized in that, The operation of receiving the user input to collapse the second node in the fourth ring layer of the central architecture diagram includes: The system receives the user's operation of selecting the second node and moving it to the area where the fifth ring layer is located.

11. The method according to any one of claims 1 to 10, characterized in that, The central architecture diagram also includes edges between the central node and the nodes of the ring layer, wherein the edges indicate the relationship between the entity information indicated by the nodes at both ends of the edges.

12. The method according to any one of claims 1 to 11, characterized in that, The central architecture diagram includes a hierarchy of entity information indicated by any node; or, In the central architecture diagram, the nodes of the ring layer connected to the central node are represented using different primitives than the nodes of other ring layers.

13. A method for displaying a central architecture diagram, characterized in that, The method includes: The diagram shows a central architecture, wherein the central node in the central architecture is used to indicate first entity information, and the central architecture also includes multiple ring layers centered on the central node, each ring layer including at least one node; The system receives an operation from a user to move a first node in the first ring layer of the central architecture diagram to the area where the second ring layer is located, wherein the first node is used to indicate second entity information; Based on the user's operation on the first node, the first node is hidden, and a second node associated with the first node is displayed in the second ring layer, wherein the second node is used to indicate third entity information, and the third entity information is associated with the second entity information.

14. The method according to claim 13, characterized in that, The second node is a child node of the first node, and the third entity information is the entity information of the lower level of the second entity information; or, The second node is the parent node of the first node, and the third entity information is the entity information above the second entity information.

15. The method according to claim 13 or 14, characterized in that, The method further includes: The system receives the user's operation of selecting a third node in the third ring layer of the central architecture diagram and moving it to the area where the central node is located, wherein the third node is used to indicate fourth entity information; Based on the user's operation on the third node, a new central node and nodes in multiple ring layers centered on the new central node are displayed, wherein the new central node is the third node.

16. The method according to claim 13 or 14, characterized in that, The method further includes: Receive the user's operation on the central node; Based on the user's operation on the central node, a replaceable node is displayed, which is used to indicate the fifth entity information; Receive the user's operation of selecting the replaceable node and moving it to the area where the central node is located; Based on the user's operation on the replaceable node, a new central node and nodes in multiple ring layers centered on the new central node are displayed, where the new central node is the replaceable node.

17. The method according to any one of claims 14 to 16, characterized in that, The central architecture diagram is an enterprise process architecture diagram, which is used to represent the relationships between enterprise processes.

18. The method according to any one of claims 14 to 17, characterized in that, Prior to the aforementioned exhibition center architecture diagram, the method further includes: Obtain a global architecture diagram, wherein the global architecture diagram includes multiple nodes, and each node is used to indicate entity information; Based on the hierarchical relationship between nodes in the global architecture diagram, the hierarchy of the multiple entity information indicated by the multiple nodes is determined; Based on the hierarchy of the multiple entity information, the arrangement of the nodes of the multiple ring layers is determined, wherein the nodes of the same ring layer indicate the same hierarchy of entity information, and the nodes of different ring layers indicate different hierarchical levels of entity information. The central architecture diagram is constructed based on the arrangement of the nodes of the multiple ring layers.

19. An architecture diagram construction system, characterized in that, The system includes: The acquisition module is used to acquire information about multiple entities and the relationships between the multiple entity information. The layout module is used to determine the first entity information and construct a central architecture diagram based on the relationship between the first entity information and the plurality of entity information, wherein the first entity information is one of the plurality of entity information; A visualization module is used to display the central architecture diagram, wherein the central node in the central architecture diagram is used to indicate the first entity information, and the central architecture diagram also includes multiple ring layers centered on the central node, each ring layer including at least one node, and the nodes of different ring layers have different relationships with the central node.

20. The system according to claim 19, characterized in that, The layout module is further configured to construct a global architecture diagram based on the plurality of entity information and the relationship between the plurality of entity information, wherein each node in the global architecture diagram indicates one of the plurality of entity information. The visualization module is also used to display the global architecture diagram; The layout module is used to receive information generated by the user clicking on the first node in the global architecture diagram, and determine the first entity information corresponding to the first node based on the information.

21. The system according to claim 20, characterized in that, The layout module is used to determine the hierarchy of the multiple entity information based on the hierarchical relationship between nodes in the global architecture diagram; determine the arrangement of nodes in the multiple ring layers based on the hierarchy of the multiple entity information, wherein nodes in the same ring layer indicate the same hierarchy of entity information, and nodes in different ring layers indicate different hierarchical levels of entity information; and construct the central architecture diagram based on the arrangement of nodes in the multiple ring layers.

22. The system according to any one of claims 19 to 21, characterized in that, The central architecture diagram is an enterprise process architecture diagram, which is used to represent the relationships between enterprise processes.

23. The system according to claim 21, characterized in that, The system also includes an interaction module. The interaction module is used to receive the user's input to expand any node in the first ring layer of the central architecture diagram. The any node is used to indicate the second entity information among the multiple entity information. The second entity information is associated with one or more lower-level entity information. The layout module is also used to update the central architecture diagram based on the operation of expanding any node; The visualization module is also used to display the updated central architecture diagram, which hides any of the nodes, and the updated central architecture diagram includes a second ring layer, which includes one or more child nodes associated with any of the nodes, and the child nodes associated with any of the nodes indicate the entity information below the second entity information.

24. The system according to claim 23, characterized in that, The interaction module is used to receive the user's operation of selecting any node and moving it to the area where the second ring layer of the central architecture diagram is located.

25. The system according to claim 21, characterized in that, The system also includes an interaction module. The interaction module is used to receive the user's input to change the central node; The layout module is also used to update the central architecture diagram based on the operation of changing the central node; The visualization module is also used to display the updated central architecture diagram, which includes a new central node and nodes in multiple ring layers centered on the new central node.

26. The system according to claim 25, characterized in that, The interaction module is used to receive the user's operation of selecting any node in the third ring layer of the central architecture diagram and moving it to the area where the original central node is located; or, to receive the user's operation of selecting a replaceable node and moving it to the area where the original central node is located, wherein the replaceable node is a node displayed in the central architecture diagram when an operation acting on the original central node is detected.

27. The system according to claim 21, characterized in that, The system also includes an interaction module. The interaction module is used to receive the user's input to collapse the second node in the fourth ring layer of the central architecture diagram, and the second node is used to indicate the third entity information among the multiple entity information. The layout module is also used to update the central architecture diagram according to the operation of collapsing the second node; The visualization module is also used to display the updated central architecture diagram, which hides the second node and / or the third node in the fourth ring layer. The third node is used to indicate the fourth entity information among the multiple entity information. The updated central architecture diagram also includes a fifth ring layer, which includes the fourth node. The lower-level entity information associated with the entity information indicated by the fourth node includes the third entity information and the fourth entity information.

28. The system according to claim 27, characterized in that, The interaction module is used to receive the user's operation of selecting the second node and moving it to the area where the fifth ring layer is located.

29. The system according to any one of claims 19 to 28, characterized in that, The central architecture diagram also includes edges between the central node and the nodes of the ring layer, wherein the edges indicate the relationship between the entity information indicated by the nodes at both ends of the edges.

30. The system according to any one of claims 19 to 29, characterized in that, The central architecture diagram includes a hierarchy of entity information indicated by any node; or, In the central architecture diagram, the nodes of the ring layer connected to the central node are represented using different primitives than the nodes of other ring layers.

31. An architecture diagram display system, characterized in that, The system includes: A visualization module is used to display a central architecture diagram, wherein the central node in the central architecture diagram is used to indicate first entity information, and the central architecture diagram also includes multiple ring layers centered on the central node, each ring layer including at least one node; An interaction module is used to receive an operation from a user to move a first node in the first ring layer of the central architecture diagram to the area where the second ring layer is located, wherein the first node is used to indicate second entity information; The visualization module is further configured to hide the first node and display a second node associated with the first node in the second ring layer based on the user's operation on the first node, wherein the second node is used to indicate third entity information, and the third entity information is associated with the second entity information.

32. The system according to claim 31, characterized in that, The second node is a child node of the first node, and the third entity information is the entity information of the lower level of the second entity information; or, The second node is the parent node of the first node, and the third entity information is the entity information above the second entity information.

33. The system according to claim 31 or 32, characterized in that, The interaction module is also used to receive the user's operation of selecting a third node in the third ring layer of the central architecture diagram and moving it to the area where the central node is located, wherein the third node is used to indicate fourth entity information; The visualization module is also used to display a new central node and nodes in multiple ring layers centered on the new central node, based on the user's operation on the third node, wherein the new central node is the third node.

34. The system according to claim 31 or 32, characterized in that, The interaction module is also used to receive the user's operation on the central node; The visualization module is also used to display replaceable nodes based on the user's operation on the central node, and the replaceable nodes are used to indicate the fifth entity information; The interaction module is also used to receive the user's operation of selecting the replaceable node and moving it to the area where the central node is located; The visualization module is also used to display a new central node and nodes in multiple ring layers centered on the new central node, based on the user's operation on the replaceable node, wherein the new central node is the replaceable node.

35. The system according to any one of claims 31 to 34, characterized in that, The central architecture diagram is an enterprise process architecture diagram, which is used to represent the relationships between enterprise processes.

36. The system according to any one of claims 31 to 35, characterized in that, The system also includes a layout module. The layout module is used to obtain a global architecture diagram, wherein the global architecture diagram includes multiple nodes, each node indicating an entity information; determine the hierarchy of the multiple entity information indicated by the multiple nodes according to the hierarchical relationship between the nodes in the global architecture diagram; determine the arrangement of the nodes of the multiple ring layers according to the hierarchy of the multiple entity information, wherein the entity information indicated by the nodes of the same ring layer is at the same level, and the entity information indicated by the nodes of different ring layers is at different levels; and construct the central architecture diagram according to the arrangement of the nodes of the multiple ring layers.

37. A computing device, characterized in that, It includes a processor and a memory, the processor executing instructions stored in the memory to implement the method as claimed in any one of claims 1 to 18.

38. A computer-readable storage medium, characterized in that, It includes computer program instructions that, when executed by a computing device, cause the computing device to perform the method as described in any one of claims 1 to 18.

Images