Enterprise architecture construction method and device

Abstract

The invention discloses an enterprise architecture construction method and device, and relates to the technical field of computers. The computing device obtains the probability of the incidence relation between the first framework and the second framework based on a rule matching system; and the computing device displays a second interface containing the enterprise architecture based on the probability that the association relationship exists between the first architecture and the second architecture. Thus, the computing device displays a second interface including the enterprise architecture according to the rule matching system. Multiple times of communication are avoided, and the efficiency of constructing the enterprise architecture is improved. According to the method and the device, multiple communication is not needed, the influence of the difference of the business levels of workers on the constructed enterprise architecture is reduced, a guarantee is provided for the accuracy of the constructed enterprise architecture, and the requirements on the workers are reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, and particularly relates to a construction method and device of enterprise architecture. BACKGROUND

[0002] Enterprise architecture (EA) can be used to describe the relationship between various elements constituting an enterprise. The construction elements of the enterprise architecture can include: business architecture, information architecture, application architecture, technology architecture, and the association relationship among the business architecture, the information architecture, and the application architecture. Generally, the enterprise architecture can be constructed by the following process: (1) using different construction teams to construct the business architecture, the information architecture, the application architecture, and the technology architecture in the enterprise architecture. (2) the construction personnel of the enterprise architecture communicates with the enterprise constructing the enterprise architecture for multiple times to obtain the association relationship among the business architecture, the information architecture, and the application architecture. (3) constructing the enterprise architecture according to the business architecture, the information architecture, the application architecture, the technology architecture, and the association relationship among the business architecture, the information architecture, and the application architecture.

[0003] Using the above process to construct the enterprise architecture, the construction personnel of the enterprise architecture needs to communicate with the enterprise constructing the enterprise architecture for multiple times, which affects the construction efficiency of the enterprise architecture. SUMMARY

[0004] The present application provides a construction method and device of enterprise architecture, which is used to solve the problem that the construction of the enterprise architecture needs multiple communications, which affects the construction efficiency of the enterprise architecture.

[0005] In a first aspect, the present application provides a method for constructing an enterprise architecture. The method can be executed by a computing device, a computing device cluster including a plurality of computing devices, a component of a computing device such as a processor, a chip or a chip system of a computing device, or a logic module or software capable of implementing all or part of the functions of a computing device. Taking the execution by a computing device as an example, the method for constructing an enterprise architecture provided in the first aspect includes: displaying an initialization interface by the computing device. The initialization interface includes an architecture construction entry. The computing device displays a first interface in response to the operation of the entry by a user. The first interface includes: a business architecture, an information architecture, and an application architecture. The computing device processes the business architecture, the information architecture, and the application architecture based on a rule matching system in response to the operation of the first interface by a user, to obtain a probability that there is an association relationship between a first architecture and a second architecture. The first architecture is the business architecture, the information architecture, or the application architecture, the second architecture is the business architecture, the information architecture, or the application architecture, and the first architecture and the second architecture are different. The computing device displays a second interface according to the probability that there is an association relationship between the first architecture and the second architecture. The second interface includes an enterprise architecture, and the enterprise architecture includes an enterprise business architecture, an enterprise information architecture, an enterprise application architecture, and an association relationship between the enterprise business architecture, the enterprise information architecture, and the enterprise application architecture.

[0006] In the first aspect of the present application, the computing device obtains the probability that there is an association relationship between the first architecture and the second architecture based on the rule matching system. And the computing device displays the second interface including the enterprise architecture based on the probability that there is an association relationship between the first architecture and the second architecture. In this way, the computing device displays the second interface including the enterprise architecture according to the rule matching system. This avoids multiple communications and improves the efficiency of constructing the enterprise architecture. Without multiple communications, the influence of the difference in the business level of the staff on the enterprise architecture constructed is reduced, the accuracy of the enterprise architecture constructed is ensured, and the requirements for the staff are reduced.

[0007] In a possible implementation, the computing device obtains the probability of the existence of the association relationship between the first element in the first architecture and the second element in the second architecture based on the rule matching system processing the business architecture, the information architecture and the application architecture, including: the computing device obtains the probability of the existence of the association relationship between the first element in the first architecture and the second element in the second architecture based on the rule matching system processing the business architecture, the information architecture and the application architecture. The first element is one of the elements included in the first architecture, and the second element is one of the elements included in the second architecture. The association relationship between the first architecture and the second architecture is represented by the probability of the existence of the association relationship between the first element and the second element. In this way, the computing device obtains the probability of the existence of the association relationship between the first element of the first architecture and the second element of the second architecture, and obtains the probability of the existence of the association relationship between the architectures according to the probability of the existence of the association relationship between the elements of the architectures, thereby providing a guarantee for the accuracy of the constructed enterprise architecture.

[0008] In another possible implementation, the computing device obtains the probability of the existence of the association relationship between the first element in the first architecture and the second element in the second architecture based on the rule matching system processing the business architecture, the information architecture and the application architecture, including: the computing device obtains the first probability of the existence of the association relationship between the first element and the second element based on the general matching rule in the rule matching system processing the business architecture, the information architecture and the application architecture. The general matching rule includes one or more of the following: a name matching rule and a person in charge matching rule. The name matching rule is used to obtain the matching degree between the element names of the elements included in different architectures, and the person in charge matching rule is used to obtain the matching degree between the persons in charge corresponding to the elements included in different architectures.

[0009] In another possible implementation, the computing device obtains the probability of the existence of the association relationship between the first element in the first architecture and the second element in the second architecture based on the rule matching system processing the business architecture, the information architecture and the application architecture, including: the computing device obtains the second probability of the existence of the association relationship between the first element and the second element based on the specific matching rule in the rule matching system processing the business architecture, the information architecture and the application architecture. The specific matching rule includes an attribute matching rule. The attribute matching rule is used to obtain the matching degree between the attributes of the elements included in different architectures.

[0010] In a possible implementation, the computing device obtains the probability that the first element in the first architecture and the second element in the second architecture have the association relationship based on the rule matching system processing the business architecture, the information architecture, and the application architecture, including: the computing device obtains the first probability that the first element and the second element have the association relationship based on the computing device processing the business architecture, the information architecture, and the application architecture based on a general matching rule in the rule matching system. The general matching rule includes one or more of the following: a name matching rule and a responsibility person matching rule. The name matching rule is used to obtain a matching degree between element names of elements included in different architectures, and the responsibility person matching rule is used to obtain a matching degree between responsibility persons corresponding to elements included in different architectures. The computing device obtains the second probability that the first element and the second element have the association relationship based on the computing device processing the business architecture, the information architecture, and the application architecture based on a specific matching rule in the rule matching system. The specific matching rule includes an attribute matching rule, which is used to obtain a matching degree between attributes of elements included in different architectures.

[0011] In a possible implementation, the association relationship between the first architecture and the second architecture includes: the probability that the first element in the first architecture and the second element in the second architecture have the association relationship satisfies a first condition or a second condition. The first condition includes that any one of the first probability and the second probability is greater than or equal to a first probability threshold. The second condition includes that the first probability is less than the first probability threshold and greater than or equal to a second probability threshold, and the second probability is less than the first probability threshold and greater than or equal to a third probability threshold. In this way, the computing device uses multiple conditions to determine whether the elements between the architectures have the association relationship, which guarantees the accuracy of the obtained association relationship, and further guarantees the accuracy of the constructed enterprise architecture.

[0012] In a possible implementation, the enterprise architecture includes: the association relationship between the first element in the first architecture and one element in the second architecture. Alternatively, the enterprise architecture includes: the association relationship between the first element in the first architecture and multiple elements in the second architecture.

[0013] In a possible implementation, the second interface further includes: the probability that the first architecture and the second architecture have the association relationship. The probability is used to indicate a numerical value of the possibility of the association relationship. In this way, the user can intuitively obtain the probability that the first architecture and the second architecture have the association relationship, which improves the credibility of the constructed enterprise architecture.

[0014] In another possible implementation, the computing device displays the first interface in response to the user's operation on the entry, including: the computing device displays an architecture input window in response to the user's operation on the entry; and the computing device displays the business architecture, the information architecture, and the application architecture in the first interface in response to the user's input operation on the architecture input window. The computing device supports the user to input the architecture by using the architecture input window, and thus the friendliness and flexibility of the interaction are improved.

[0015] In a second aspect, the present application provides a device for constructing an enterprise architecture. The device includes various modules for performing the method in the first aspect or any possible design of the first aspect.

[0016] In a third aspect, the present application provides a processor. The processor includes an interface circuit and a control circuit, the interface circuit is used for the user's operation on the first interface, and the control circuit cooperates with the interface circuit to implement the operation steps of the method in the first aspect or any possible design of the first aspect.

[0017] In a fourth aspect, the present application provides a computing device cluster. The computing device cluster includes at least one computing device, and each computing device includes 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, so that the computing device cluster performs the functions implemented by the method for constructing an enterprise architecture in the first aspect or any possible design of the first aspect.

[0018] In a fifth aspect, the present application provides a computer-readable storage medium, including: computer program instructions; when the computer program instructions run in the computing device cluster, the computing device cluster performs the functions implemented by the method for constructing an enterprise architecture in the first aspect or any possible design of the first aspect.

[0019] In a sixth aspect, the present application provides a computer program product, when the computer program product runs on the computing device cluster, the computing device cluster performs the functions implemented by the method for constructing an enterprise architecture in the first aspect or any possible design of the first aspect.

[0020] The advantages of the above second aspect to sixth aspect can refer to the description of the first aspect or any possible implementation of the first aspect, and will not be described here. On the basis of the implementation manner provided by the above aspects, the present application can be further combined to provide more implementation manners. BRIEF DESCRIPTION OF DRAWINGS

[0021] Figure 1 The architecture schematic diagram of the enterprise architecture construction system provided by the present application is shown in the figure;

[0022] Figure 2 The structure schematic diagram of a chip provided by the present application is shown in the figure;

[0023] Figure 3 A flowchart illustrating the first enterprise architecture construction method provided in this application;

[0024] Figure 4A A schematic diagram illustrating the first possible business architecture, information architecture, and application architecture provided for this application;

[0025] Figure 4B A schematic diagram illustrating the second business architecture, information architecture, and application architecture provided for this application;

[0026] Figure 4C A schematic diagram illustrating the third business architecture, information architecture, and application architecture provided for this application;

[0027] Figure 5 An example diagram of an enterprise architecture provided for this application;

[0028] Figure 6 A schematic diagram of a device for constructing an enterprise architecture provided in this application;

[0029] Figure 7 This application provides a schematic diagram of the structure of a computing device cluster;

[0030] Figure 8 This is a schematic diagram of the connection between computing devices provided in this application. Detailed Implementation

[0031] To ensure clarity and conciseness in the description of the following embodiments, a brief introduction to the relevant terms is given first.

[0032] 1. Enterprise Structure

[0033] Enterprise architecture (EA) describes the elements that make up an enterprise and the relationships between them. Enterprise architecture can include: Business Architecture (BA), Information Architecture (IA), Application Architecture (AA), and Technology Architecture.

[0034] 2. Business Architecture

[0035] Business architecture: A structured representation of business operations. Business architecture describes how an enterprise uses key business elements to achieve its strategic intentions and goals. The elements of business architecture include: value stream, business capabilities, business processes, activity capabilities, and value stream stages, as shown in Table 1 below. Among these, value stream, business capabilities, activity capabilities, and value stream stages are the key elements of enterprise architecture.

[0036] 3. Information Architecture

[0037] Information Architecture can refer to a set of specifications describing various information required by an enterprise in business operation and management decision-making and the relationship between the various information in a structured manner. In some possible cases, Information Architecture can also be referred to as Data Architecture. Elements of Information Architecture include business objects, logical entities, as shown in Table 1 below. Among them, the business object is a key element of Information Architecture.

[0038] 4. Application Architecture

[0039] Application Architecture is used to describe the application functions supporting Business Architecture and processing the data defined by Information Architecture. Elements of Application Architecture include applications implementing Enterprise Architecture, and application services constituting the applications, as shown in Table 1 below. Among them, the applications implementing Enterprise Architecture and the application services constituting the applications are key elements of Application Architecture.

[0040] 5. Technology Architecture

[0041] Technology Architecture can refer to hardware or software components obtained by an enterprise. Elements of Technology Architecture include technology components and technology services.

[0042] Table 1. Examples of elements of Enterprise Architecture

[0043] Serial number Architecture name Element 1 Business architecture Value stream, business capability, business process, activity capability, value stream stage 2 Information architecture Business object, logical entity 3 Application architecture Application implementing enterprise architecture, multiple application services constituting application 4 Technology architecture Technology component, technology service

[0044] The above briefly introduces related terms that can be involved in the present application. The following briefly introduces related technologies involved in the present application.

[0045] Generally, the following process can be used to build an enterprise architecture. First, use multiple teams to model each architecture included in the enterprise architecture to obtain a model corresponding to each architecture. Second, the modeling teams communicate with the enterprise building the enterprise architecture multiple times to obtain the association relationship between each architecture. Finally, build the enterprise architecture according to the model of each architecture and the association relationship between each architecture.

[0046] Using the above process to build an enterprise architecture can have the following problems.

[0047] (1) The association relationship between each architecture can be obtained only after multiple communications, which affects the efficiency of building the enterprise architecture and the workload of multiple communications.

[0048] (2) The association relationship between each architecture determined by communication can be inaccurate due to the limitation of the communication skills and professional ability of the modeling team, which affects the enterprise architecture obtained.

[0049] Based on this, the application provides a construction method of enterprise architecture. The computing device obtains a probability that there is an association relationship between the first architecture and the second architecture based on a rule matching system. And the computing device displays a second interface containing the enterprise architecture based on the probability that there is an association relationship between the first architecture and the second architecture. In this way, the computing device displays the second interface containing the enterprise architecture according to the rule matching system. This avoids multiple communications and improves the efficiency of constructing the enterprise architecture. Without multiple communications, the influence of the difference in the business level of the staff on the enterprise architecture constructed is reduced, the accuracy of the enterprise architecture constructed is ensured, and the requirements on the staff are reduced.

[0050] The construction method of enterprise architecture provided by the application can be applied to a construction system of enterprise architecture. Figure 1 The architecture of the construction system of enterprise architecture provided by the application is shown in the following figure. Figure 1 As shown in the figure, the construction system of enterprise architecture 100 includes a computing device 110. The computing device 110 can be a common computer device, such as a personal computer, a tablet computer, a server with an external display device, etc. The computing device 110 can receive input data (such as the operation of the user on the architecture construction entry included in the initialization interface, the operation of the user on the first interface), process the business architecture, the information architecture and the application architecture based on a rule matching system, and obtain and output the result (such as the enterprise architecture). In some possible examples, the computing device 110 can also display a second interface containing the enterprise architecture.

[0051] The computing device 110 includes a communication interface 114, a processor 111, a memory 112 and a bus 116. The communication interface 114 is used to communicate with the devices located outside the computing device 110. For example, the user inputs data to the computing device 110 through the communication interface 114 to construct the enterprise architecture. The communication interface can be an input / output (I / O) interface.

[0052] The processor 111 is the operation and control core of the computing device 110, which can include a central processing unit (CPU), a specific integrated circuit, other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and the like. In practical applications, the computing device 110 can also include multiple processors. The processor 111 can include one or more processor cores. The processor 111 is installed with an operating system and other software programs, so that the processor 111 can access the memory 112 and various peripheral component interconnect express (PCIe) devices.

[0053] The processor 111 is connected to the memory 112 through a bus 116. The memory 112 is the main memory of the computing device 110. The bus 116 can be a double data rate (DDR) bus or other types of buses. The memory 112 is usually used to store various running software in the operating system and the like. In order to improve the access speed of the processor 111, the memory 112 needs to have the advantage of fast access speed. In traditional computer devices, dynamic random access memory (DRAM) is usually used as the memory 112. In addition to DRAM, the memory 112 can also be other random access memories, such as static random access memory (SRAM) and the like. In addition, the memory 112 can also be a read only memory (ROM). For read only memories, for example, programmable read only memories (PROM), erasable programmable read only memories (EPROM), and the like. The present embodiment does not limit the number and type of the memory 112.

[0054] In some possible scenarios, the computing device 110 may also include a display 118. The display 118 may display an initialization interface, and in response to user operations on the architecture construction entry point in the initialization interface, display a first interface, etc. The display 118 may be a liquid crystal display (LCD), etc.

[0055] In some possible scenarios, in order to persistently store data (such as business architecture, information architecture, and application architecture), the enterprise architecture building system 100 also includes a data storage system 113, which may be located outside the computing device 110 (e.g., Figure 1 As shown, the data storage system 113 exchanges data with the computing device 110 via a network. Optionally, the data storage system 113 can also be located inside the host, such as the data storage system 113 exchanging data with the processor 111 via the bus 116. In this case, the data storage system 113 manifests as a hard disk.

[0056] In some possible scenarios, the enterprise architecture building system 100 may also include a client device 120. In this case, the user uses the client device 120 to send the business architecture, information architecture, and application architecture to the computing device 110. The client device 120 is a terminal device, including but not limited to personal computers, servers, mobile phones, tablets, or smart cars.

[0057] For example, Figure 1 The processor 111 in the middle can be implemented through a chip, such as Figure 2 As shown, Figure 2 This is a schematic diagram of the structure of a chip provided in this application. For example, the chip 200 includes a core 201, a CPU 202, a system buffer 203, an input / output (I / O) device 205, and a DDR 206.

[0058] The CPU 202 is used to accept tasks (such as compression tasks, decompression tasks, enterprise architecture building tasks, etc.) and call core 201 to execute the task. When chip 200 has multiple cores 201, the CPU 202 is also used for scheduling tasks. For example, the CPU 202 can be implemented by an ARM processor, which is small in size, low in power consumption, uses a 34-bit reduced instruction set, and has simple and flexible addressing. Of course, in some implementations, the CPU 202 can also be implemented by other processors.

[0059] Core 201 provides the computing power required for building enterprise architecture. In one optional configuration, Core 201 includes a load / store unit (LSU), cube computing units, scalar computing units, vector computing units, and buffers. The LSU loads data to be processed and stores processed data. It also manages read / write operations between different buffers within the core and performs format conversions. The cube computing unit provides the core computing power for matrix multiplication. The scalar computing unit is a single-instruction single-data (SISD) processor, processing only one data item (typically an integer or floating-point number) at a time. The vector computing unit, also known as an array processor, is a processor capable of directly manipulating an array or vector for computation. The number of buffers may be one or more. For example, this buffer primarily refers to the level 1 cache (L1 buffer). The buffer is used to temporarily store data that the core 201 needs to use repeatedly, thereby reducing read / write operations from the bus. Additionally, the implementation of certain data format conversion functions also requires the source data to be located in the buffer. In this embodiment, because the buffer is located in the core, the distance between the cube computing unit in the core and the storage area where the data is located is reduced, decreasing the cube computing unit's access to the DDR 206, thereby reducing data access latency and core data processing latency.

[0060] System buffer 203 mainly refers to the secondary cache, which is used to temporarily store input data, intermediate results or final results that have passed through the chip.

[0061] DDR 206 is an off-chip memory that can be replaced by high-bandwidth memory (HBM) or other off-chip memory. Located between the chip and external memory, DDR 206 overcomes the access speed limitations of shared memory read / write operations in computing resource sharing.

[0062] The I / O devices 205 included in chip 200 refer to the hardware that performs data transmission, or devices that interface with the I / O interface. Common I / O devices include network cards, printers, keyboards, and mice. All external storage devices can also be used as I / O devices, such as hard drives, floppy disks, and optical discs.

[0063] Core 201, CPU 202, system buffer 203, I / O devices 205, and DDR 206 are connected via a bus. The bus may include a pathway for transmitting information between the aforementioned components (such as CPU 202 and system buffer 203). In addition to a data bus, the bus may also include a power bus, control bus, and status signal bus. However, for clarity, the bus may be a PCIe bus, or an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a compute express link (CXL), a cache coherent interconnect for accelerators (CCIX), etc. For example, core 201 can access these I / O devices 205 via the PCIe bus. Core 201 is connected to system buffer 203 via the DDR bus. Here, different system buffers 203 may use different data buses to communicate with core 201; therefore, the DDR bus can also be replaced with other types of data buses. This embodiment does not limit the bus type.

[0064] For example, after CPU 202 loads the data (such as business architecture, information architecture, and application architecture) to be processed by the enterprise architecture building task into DDR 206, the LSU in core 201 reads (loads) the data from DDR 206, processes the multiple components, and obtains the processing result (such as the enterprise architecture). After obtaining the processing result, the LSU then loads (stores) the processing result into DDR 206, and sends it to the data storage system 113 for persistent storage via the network interface card.

[0065] It is understood that the structures illustrated in this embodiment do not constitute a specific limitation on the computing device or chip. In other embodiments, the computing device and chip may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0066] The following is combined with Figure 1 and Figure 2 The content shown provides a detailed explanation of the enterprise architecture construction method provided in this application.

[0067] Figure 3This is a flowchart illustrating the first enterprise architecture construction method provided in this application. This enterprise architecture construction method can be executed by a computing device, a computing device cluster, or components of the computing device (such as the computing device's processor, chip, or chip system), and can also be implemented by a logic module or software. When this enterprise architecture construction method is executed by a computing device, the computing device can be... Figure 1 The computing device 110 and client device 120 are shown. For the hardware implementation of the computing device, please refer to the foregoing. Figure 1 The description of that will not be repeated here. Where the construction method of this enterprise architecture is executed by a component of a computing device, that computing device component can be... Figure 2 The chip shown is an example. For details on the chip's hardware implementation, please refer to the preceding text. Figure 2 The description of this will not be repeated here. In some optional examples, the method for constructing this enterprise architecture can also be executed by other computing devices; the hardware implementation of the computing devices can be found in the foregoing. Figure 1 and Figure 2 The description of that will not be repeated here.

[0068] This explanation uses the enterprise architecture construction method provided in this embodiment, executed by a computing device, as an example. Figure 3 As shown, the enterprise architecture construction method provided in this embodiment includes the following steps S310 to S340.

[0069] S310, the computing device displays the initialization interface.

[0070] The initialization interface includes an architecture building entry point. This entry point can refer to controls displayed on the initialization interface that instruct the user to build the enterprise architecture. These controls can be button controls, text box controls, etc. Controls can include text, images, or combinations thereof, and this application does not limit this. For example, the initialization interface displays a first button, which includes the option to "Build Enterprise Architecture". In this case, the user triggers the first button to display the first interface.

[0071] In some possible scenarios, after the user presses the first button, the computing device may also display a login screen. The login screen is used to receive user input such as username and password.

[0072] S320, the computing device responds to the user's operation on the entry point and displays the first interface.

[0073] The first interface includes: business architecture, information architecture, and application architecture.

[0074] Depending on the needs of the actual application, the business architecture, information architecture, and application architecture in the first interface can be either user-inputted or preset, which will be explained below.

[0075] In scenario 1, the business architecture, information architecture, and application architecture displayed on the first interface are input by the user.

[0076] In this case, the following methods ① and ② can be used to obtain the business architecture, information architecture, and application architecture.

[0077] ① The computing device responds to the user's operation on the entry point by displaying the architecture input window.

[0078] User actions on the entry point can include clicking, double-clicking, swiping, etc., which are not limited in this application. The architecture input window can be used to receive user-inputted architectures, such as business architecture, information architecture, application architecture, etc. For example, if the architecture construction entry point included in the initialization interface is a button, the computing device can respond to the user's click operation on the button by displaying the architecture input window to receive the user's input of business architecture, information architecture, and application architecture.

[0079] ② The computing device responds to the user's input operation on the architecture input window and displays the business architecture, information architecture, and application architecture on the first interface.

[0080] The computing device can receive user input operations on the architecture input window, and display the business architecture, information architecture, and application architecture on the first interface based on the input operations.

[0081] The computing device allows users to enter business architecture, information architecture, and application architecture in the architecture input window in multiple ways. Examples of two possible methods are given below.

[0082] Example 1: The computing device allows users to directly input business architecture, information architecture, and application architecture in the architecture input window.

[0083] In this scenario, the computing device allows users to directly input the elements included in the business architecture, information architecture, and application architecture within the architecture input window. The computing device supports multiple methods for users to input the elements of each architecture. For example, the computing device allows users to select controls to input the elements in the input window. Alternatively, the computing device allows users to input the elements in text format. Depending on the needs of the actual application, the computing device can also be configured to support other methods for users to input the elements of each architecture, such as allowing users to drag and drop graphical icons to input the elements, etc., which is not limited in this application.

[0084] Example 2: The computing device allows users to import files containing the elements included in each architecture in the architecture input window.

[0085] The files can be text files, such as txt, word, or excel files; image files, such as jpg or jpeg files; or audio files, such as mp3 or mp4 files. This application does not limit the scope of the file storage. The computing device supports users in importing files containing elements of each architecture using various methods. For example, the computing device supports users importing files containing elements of each architecture using other electronic devices (such as hard drives, flash drives, etc.). Furthermore, the computing device supports users receiving files containing elements of each architecture sent by other electronic devices (such as laptops, etc.) via a network. Depending on the needs of the actual application, the computing device can also be configured to support users importing elements of each architecture using other methods; this application does not limit the scope of the application.

[0086] After obtaining the elements included in each architecture, the computing device can represent each architecture in a variety of ways. Examples of two possible methods are given below.

[0087] Example 1: The computing device does not change the way the elements of each architecture are displayed, and directly displays each architecture in the first interface according to the display method. Figure 4A A schematic diagram illustrating the first possible business architecture, information architecture, and application architecture provided for this application, as shown below. Figure 4A As shown, the computing device obtains the elements of each architecture input by the user using drag-and-drop controls, and the computing device can directly display the elements of each architecture drawn by the user using drag-and-drop controls on the first interface. Figure 4B A schematic diagram illustrating the second business architecture, information architecture, and application architecture provided in this application, such as... Figure 4B As shown, the computing device obtains the elements of each architecture as input by the user in text form, and the computing device can directly display the elements of each architecture in text form on the first interface.

[0088] Example 2: The computing device changes the display method of each element of each architecture obtained, obtains the changed display method, and displays each architecture in the first interface according to the changed display method. Figure 4C The diagram illustrating the third business architecture, information architecture, and application architecture provided for this application is as follows: Figure 4C As shown, the computing device displays the elements of each architecture in text format. In this case, the computing device can obtain the architecture diagram of each architecture based on the elements of each architecture and display the elements of each architecture in the form of an architecture diagram on the first interface.

[0089] The above provides examples of two possible ways for computing devices to represent various architectures. Depending on the needs of actual applications, computing devices may also use other methods to represent various architectures, which this application does not limit.

[0090] In scenario 2, the business architecture, information architecture, and application architecture in the first interface are preset.

[0091] In this scenario, the computing device supports storing the various elements of the business architecture, information architecture, and application architecture in the computing device before receiving operations on the entry points included in the initialization interface, according to actual needs.

[0092] The above section, with examples, explained how computing devices support user input of various architectures and how these architectures are displayed on the first interface. The following section describes how to obtain business architecture, information architecture, and application architecture.

[0093] Typically, modeling can be used to identify the elements included in the business architecture, information architecture, and application architecture of an enterprise architecture. Specifically, the modeling process can be divided into multiple steps, obtaining the output of each step. Based on the output of each step, the elements included in the business architecture, information architecture, application architecture, and technical architecture of the enterprise architecture are obtained, and the modeling steps and their corresponding outputs are summarized in Table 2 below.

[0094] Table 2. Examples of modeling steps and outputs for each step.

[0095]

[0096] The above, combined with Table 2, outlines the typical modeling steps and the outputs of each step. For more details on the above process, please refer to the explanation of common techniques; they will not be repeated here.

[0097] After obtaining the outputs of each modeling step, Tables 1 and 2 can be used to determine the possible relationships between the elements included in each of the business architecture, information architecture, and application architecture, as well as the possible relationships between the elements included in any two of these architectures. For example, in the business architecture, the value stream is supported by business capabilities and business processes, and business processes are supported by business capabilities and realized by the value stream. Similarly, between the business architecture and information architecture, the applications in the application architecture correspond to the business objects in the business architecture, and the applications are realized by the business processes in the business architecture. The computing device can execute the following S330 to obtain the relationships between the elements included in each of the business architecture, information architecture, and application architecture.

[0098] S330, the computing device responds to the user's operation on the first interface, and processes the business architecture, information architecture, and application architecture based on the rule matching system to obtain the probability that there is a correlation between the first architecture and the second architecture.

[0099] The first architecture is either a business architecture, information architecture, or application architecture, while the second architecture is either a business architecture, information architecture, or application architecture. The first architecture and the second architecture are different.

[0100] The computing device can obtain the probability of a relationship between the elements included in the business architecture, information architecture, and application architecture based on a rule matching system, according to the business architecture, information architecture, and application architecture displayed on the first interface. Specifically, the computing device can process the business architecture, information architecture, and application architecture displayed on the first interface based on a rule matching system to obtain the probability of a relationship between a first element in the first architecture and a second element in the second architecture. Here, the first element is one of the elements included in the first architecture, and the second element is one of the elements included in the second architecture. The relationship between the first architecture and the second architecture is represented by the probability of a relationship between the first element and the second element. The probability is a numerical value indicating the likelihood of a relationship. This value can be in percentage form, decimal form, or fraction form; this application does not limit this. The following explanation uses a percentage form as an example to illustrate the enterprise architecture construction method provided by this application.

[0101] The probability of a relationship between the first element and the second element includes at least one of a first probability and a second probability. The first probability is the probability of a relationship between the first element and the second element calculated according to general matching rules in the rule matching system. General matching rules include one or more of the following: name matching rules and responsible person matching rules. Name matching rules are used to obtain the degree of matching between the names of elements included in different architectures, and responsible person matching rules are used to obtain the degree of matching between the responsible persons corresponding to the elements included in different architectures. The second probability is the probability of a relationship between the first element and the second element calculated according to specific matching rules in the rule matching system. Specific matching rules include: attribute matching rules, which are used to obtain the degree of matching between the attributes of elements included in different architectures.

[0102] A rule matching system may include one or more rules. Depending on the number of rules included in the rule matching system, the computing device may obtain the probability of a relationship between the elements included in the business architecture, the elements included in the information architecture, and the elements included in the application architecture in different ways. These will be explained separately below.

[0103] Scenario 1: The rule matching system includes one rule.

[0104] In this scenario, the computing device can use a rule (such as a general matching rule or a specific matching rule) included in the rule matching system to obtain the probability that there is a correlation between the elements included in the business architecture, the elements included in the information architecture, and the elements included in the application architecture.

[0105] (1) The rule matching system includes general matching rules.

[0106] In this scenario, the computing device processes the business architecture, information architecture, and application architecture based on general matching rules in the rule matching system, calculating a first probability that there is a relationship between the first element and the second element. For example, the computing device uses general matching rules to obtain a probability 1 that there is a relationship between element 11 of the business architecture and element 21 of the information architecture.

[0107] Depending on the specific application requirements, a general matching rule can include one or more sub-rules. For example, a general matching rule can include at least one of a name matching rule and a responsible person matching rule. A name matching rule is used to determine the degree of matching between the names of elements within different architectures. A responsible person matching rule is used to determine the degree of matching between the responsible persons corresponding to the elements within different architectures.

[0108] The following example uses general matching rules, including name matching rules and responsible person matching rules, to illustrate the process by which a computing device obtains the probability that there is a correlation between the first architecture and the second architecture.

[0109] Example a: General matching rules include name matching rules.

[0110] Typically, name matching rules determine a relationship between elements in two architectures if their names are similar. For example, a first architecture includes a first element, and a second architecture includes a second element. If the names of the first and second elements are similar, then a relationship can be considered between the first element of the first architecture and the second element of the second architecture. For instance, in a first domain, the name of the business object element in the information architecture is "Line Table Plan," and the name of the business capability element in the business architecture is "Line Table Plan Management." In this case, the probability that there is a relationship between the business object in the information architecture and the business capability in the business architecture is 1. Furthermore, if the element names of the first and second elements express the same narrative concept or semantics, then the element names of the first and second elements can be considered similar.

[0111] Example b: The general matching rules include the responsible person matching rules.

[0112] Typically, the first element of a first architecture has one or more responsible persons. The responsible person for an element can be the person who handles or implements the element. The responsible person matching rule can refer to determining the relationship between elements when they share the same responsible person. For example, application element 1, application service element 2, business capability element 3, and process element 4 of an application architecture share the same responsible person, and that responsible person is A. In this case, it can be considered that there is a relationship between application element 1, application service element 2, business capability element 3, and process element 4.

[0113] The above examples a and b illustrate the two sub-rules that a general matching rule may include (i.e., name matching rule and responsible person matching rule). Depending on the needs of the actual application, the general matching rule may include fewer (e.g., name matching rule or responsible person matching rule) or more sub-rules (e.g., name matching rule, responsible person matching rule and other sub-rules). Other sub-rules may be other sub-rules determined according to the needs of the actual application, and this application does not limit them.

[0114] When a general matching rule includes multiple sub-rules, the computing device can use these sub-rules to obtain multiple probabilities of relationships between elements included in the business architecture, elements included in the information architecture, and elements included in the application architecture. The computing device performs a weighted calculation on these multiple probabilities to obtain a weighted result. The computing device uses this weighted result as the first probability of relationships between elements included in the business architecture, elements included in the information architecture, and elements included in the application architecture obtained using the general matching rule.

[0115] For example, the computing device uses the name matching rule in the general matching rules to calculate the probability 11 that there is a relationship between element 11 in the business architecture and element 21 in the information architecture. The computing device uses the responsible person matching rule in the general matching rules to calculate the probability 12 that there is a relationship between element 11 in the business architecture and element 21 in the information architecture. The computing device then performs a weighted calculation on probabilities 11 and 12 to obtain a weighted result, and uses this weighted result as the probability 1 that there is a relationship between element 11 and element 21 obtained using the general matching rules.

[0116] When a computing device performs a weighted calculation on multiple probabilities obtained using multiple sub-rules to arrive at the probability obtained using a general matching rule, the computing device can set different weights for different probabilities according to the needs of the actual application. For example, the computing device can set a weight coefficient of 0.7 for the probability calculated using the name matching rule and a weight coefficient of 0.3 for the probability calculated using the responsible person matching rule, and so on. When the general matching rule includes more sub-rules, such as sub-rules 1 to 3, the computing device can set weight coefficients for probabilities 11 to 13. Here, probability 11 is the probability that the computing device obtains a relationship between element 11 of architecture 1 and element 21 of architecture 2 using sub-rule 1; probability 21 is the probability that the computing device obtains a relationship between element 11 of architecture 1 and element 21 of architecture 2 using sub-rule 2; and probability 31 is the probability that the computing device obtains a relationship between element 11 of architecture 1 and element 21 of architecture 2 using sub-rule 3.

[0117] (2) The rule matching system includes specific matching rules.

[0118] In this scenario, the computing device processes the business architecture, information architecture, and application architecture based on specific matching rules in the rule matching system, calculating a second probability that a relationship exists between the first element and the second element. For example, the computing device uses specific matching rules to obtain a probability 2 that a relationship exists between element 11 of the business architecture and element 21 of the information architecture.

[0119] Depending on the needs of practical applications, a specific matching rule can include one or more sub-rules. For example, specific matching rules include attribute matching rules, etc. Attribute matching rules are used to obtain the degree of matching between the attributes of elements included in different architectures. Specifically, computing devices can use the key attributes of elements included in the business architecture, application architecture, and information architecture in their respective processes to perform keyword matching to obtain the degree of matching between the attributes of elements included in different architectures. Key attributes of elements in a process refer to attributes that can be used to determine the element's process; keywords for key attributes can refer to words that describe the narrative concepts or semantics of the key attributes. See Table 3 below.

[0120] Table 3 Examples of specific matching rules

[0121]

[0122] The computing device can use the matching rules in Table 3 to perform keyword matching on the first element of the first architecture and the second element of the second architecture to obtain the degree of matching between the first element of the first architecture and the second element of the second architecture.

[0123] The following example illustrates the process by which a computing device obtains the degree of matching between the first element of the first architecture and the second element of the second architecture, assuming that the computing device adopts the matching rules in Table 3, and the first architecture is the business architecture, and the second architectures are the business architecture, information architecture, and application architecture.

[0124] Example a: The first architecture is the business architecture, and the first element is the value stream; the second architecture is the business architecture, and the second element is business capabilities. In this case, the computing device can determine the degree of matching between the first and second elements using the following process.

[0125] The value proposition of the computing device's value stream acquisition includes keywords 11 to 1n. Keywords 11 to 1n can also be referred to as the first category of keywords. Keywords 21 to 2m are the metrics for the computing device's acquisition of business capabilities, and keywords 31 to 3i are the responsibility levels for acquiring business capabilities. Keywords 21 to 2m and keywords 31 to 3i can also be referred to as the second category of keywords. The computing device then matches each keyword in the first category and each keyword in the second category to determine the degree of matching between the value stream of the business architecture and the business capabilities of the business architecture.

[0126] Computing devices can use the proportion of matching keywords among all keywords to determine the degree of matching between the value stream and business capabilities of the business architecture. For example, the value proposition of the value stream might include 10 keywords, the metrics for business capabilities might include 3 keywords, and the responsibility levels for business capabilities might include 4 keywords. If 3 out of the 10 keywords in the value proposition match the 3 keywords in the metrics, and 4 out of the 10 keywords in the value proposition match the 4 keywords in the responsibility levels, the degree of matching between the value stream and business capabilities can be considered 100%. If 2 out of the 10 keywords in the value proposition match the 2 keywords in the metrics, and 4 out of the 10 keywords in the value proposition match the 4 keywords in the responsibility levels, the degree of matching between the value stream and business capabilities can be considered 85.7% (6 / 7).

[0127] Example b: The first architecture is the business architecture, and the first element is the business process; the second architecture is the information architecture, and the second element is the business object. In this case, the computing device can determine the degree of matching between the first and second elements using the following process.

[0128] Taking a passenger boarding a plane at an airport as an example, the input to the business process can be the passenger's origin, and the output can be the passenger's destination. The description of the business process can refer to the optimal path (e.g., path 1 to path n) between the passenger's origin and destination. The description of the business object can be the passenger boarding the plane at the airport. In this scenario, the computing device can obtain a first type of keyword based on the passenger's origin, destination, and the optimal path between them. The computing device can also obtain a second type of keyword based on the origin, destination, and path corresponding to the passenger boarding the plane at the airport. Finally, the computing device matches the first and second types of keywords to determine the degree of matching between the business process and the business object.

[0129] Example c: The first architecture is the business architecture, and the first element is the business process; the second architecture is the application architecture, and the second element is the application. In this case, the computing device can determine the degree of matching between the first and second elements using the following process.

[0130] Continuing with the example of a passenger boarding a plane at an airport, the computing device can obtain the first type of keywords using the method described in Example b above, which will not be repeated here. The computing device then obtains keywords related to the application's service type, reliability level, and description, resulting in the second type of keywords. Finally, the computing device matches each keyword in the first type with each keyword in the second type to determine the degree of matching between the first and second elements.

[0131] Scenario 2: The rule matching system includes multiple rules.

[0132] In this scenario, the computing device can utilize multiple rules (such as general matching rules and specific matching rules) included in the rule matching system to obtain multiple probabilities of relationships between elements included in the business architecture, elements included in the information architecture, and elements included in the application architecture. Specifically, the computing device processes the business architecture, information architecture, and application architecture based on the general matching rules in the rule matching system to calculate a first probability of a relationship between a first element and a second element. The computing device also processes the business architecture, information architecture, and application architecture based on the specific matching rules in the rule matching system to calculate a second probability of a relationship between the first element and the second element. For example, the computing device obtains probability 1 of a relationship between element 11 of the business architecture and element 21 of the information architecture using general matching rules, and probability 2 of a relationship between element 11 of the business architecture and element 21 of the information architecture using specific matching rules. For details on the process by which the computing device obtains the first and second probabilities, please refer to the relevant explanations above; they will not be repeated here.

[0133] The preceding text, in conjunction with the table, describes the process by which a computing device obtains the probability of relationships between different architectures when the rule matching system includes one or more rules. After obtaining the probability of relationships between elements using the rule matching system, the computing device can use these relationships to generate rules to determine whether relationships exist between the elements. For a detailed description, please refer to S340 below.

[0134] S340, the computing device displays a second interface based on the probability that there is a correlation between the first architecture and the second architecture.

[0135] The second interface includes the enterprise architecture, which comprises the enterprise business architecture, enterprise information architecture, enterprise application architecture, and the relationships between these three architectures.

[0136] S340 may include the following ① to ③.

[0137] ① The computing device generates rules based on the relationship and determines whether there is a relationship between the first element of the first architecture and the second element of the second architecture, according to the probability that there is a relationship between the first architecture and the second architecture.

[0138] Depending on the number of rules included in the rule matching system, the conditions included in the rules for generating association relationships also differ, as does the process by which the computing device determines the relationship between the first element and the second element. These will be described separately below.

[0139] For example, when the rule matching system includes general matching rules, the association generation rule may include a condition. This condition may be a first probability threshold. For instance, when the rule matching system includes general matching rules, the probability that the computing device determines a relationship exists between a first element of a first architecture and a second element of a second architecture based on the general matching rules is a first probability. If the first probability is greater than or equal to the first probability threshold, the computing device determines that a relationship exists between the first element and the second element. Depending on the needs of the actual application, different percentage values ​​can be set for the first probability threshold, such as setting it to 80%.

[0140] For example, when a rule-matching system includes specific matching rules, the association generation rule may include a condition. This condition could be a second probability threshold. For instance, when the rule-matching system includes specific matching rules, the probability that the computing device determines a relationship exists between a first element of a first architecture and a second element of a second architecture based on the specific matching rules is the second probability. If the second probability is greater than or equal to the second probability threshold, the computing device determines that a relationship exists between the first element and the second element. Depending on the needs of the actual application, different percentage values ​​can be set for the second probability threshold, such as setting it to 60%.

[0141] For example, in a rule-matching system that includes general matching rules and specific matching rules, the association generation rule can include two conditions (such as a first condition or a second condition). The computing device can use the general matching rules to obtain the probability that there is an association between the first element and the second element as a first probability, and the computing device can use the specific matching rules to obtain the probability that there is an association between the first element and the second element as a second probability. The computing device determines that there is an association between the first element and the second element if the first probability and the second probability satisfy either the first condition or the second condition (as shown in Table 4 below). The first condition includes: either the first probability or the second probability is greater than or equal to a first probability threshold. The second condition includes: the first probability is less than the first probability threshold but greater than or equal to the second probability threshold, and the second probability is less than the first probability threshold but greater than or equal to a third probability threshold. Depending on the needs of the actual application, the first probability threshold, the second probability threshold, and the third probability threshold can take different values. For example, the first probability threshold can be 80%, the second probability threshold can be 60%, and the third probability threshold can be 60%.

[0142] Table 4 Examples of Determining the Generation of Associations

[0143]

[0144] In Table 4, the first probability is the probability that the first element of the first architecture obtained by the computing device using a general matching rule is related to the second element of the second architecture. The second probability is the probability that the first element of the first architecture obtained by the computing device using a specific matching rule is related to the second element of the second architecture.

[0145] The preceding text, using the example of probabilities expressed as percentages, explained the process by which a computing device determines the relationships between architectures based on association rules. When probabilities are expressed in other forms, the probability threshold can also be expressed in a form corresponding to the probabilities. In this case, the computing device can still use the method described above to determine the relationships between architectures. For example, if probabilities are expressed as decimals, the probability threshold can also be expressed as a decimal. In this case, the computing device can also use the method described above to determine the relationships between architectures, and this application does not limit this approach.

[0146] ②If there is a relationship between the first element of the first architecture and the second element of the second architecture, the computing device generates the enterprise architecture based on the relationship.

[0147] In this case, if there is a relationship between the first element of the first architecture and the second element of the second architecture, then the enterprise architecture generated by the computing device includes the relationship between the first element and the second element.

[0148] ③ The computing device displays a second interface based on the generated enterprise architecture.

[0149] The second interface includes the enterprise architecture. The enterprise architecture includes business architecture, information architecture, and application architecture, and the relationships between the elements included in the business architecture, information architecture, and application architecture.

[0150] In some possible scenarios, the second interface may also include the probability that there is a correlation between the first architecture and the second architecture. Figure 5 An example diagram of an enterprise architecture provided for this application, such as Figure 5 As shown, the computing device determines that element 11 in the business architecture and element 21 in the information structure are related. In this case, the enterprise architecture generated by the computing device includes the relationship between element 11 and element 21, and the probability 1 that there is a relationship between element 11 and element 21.

[0151] In some possible scenarios, the probability that there is a correlation between the first architecture and the second architecture included in the second interface can be a probability directly calculated by the computing device based on the rule matching system.

[0152] For example, a first probability and a second probability. In this case, the computing device can display, on a second interface, the probabilities of a relationship between the first element and the second element as the first probability and the second probability.

[0153] In some other possible scenarios, the probability that there is a correlation between the first architecture and the second architecture included in the second interface can be the probability obtained by the computing device after processing the probability calculated by the rule-based matching system.

[0154] For example, the computing device may use the weighted result of a weighted calculation of the first probability and the second probability as the probability that there is a relationship between the first architecture and the second architecture. In this case, the computing device can display the probability that there is a relationship between the first element and the second element as the weighted result of the first probability and the second probability on the second interface.

[0155] The preceding text uses the example of a computing device determining a relationship between a first element in the first architecture and an element (such as a second element) in the second architecture to illustrate the enterprise architecture construction method provided in this application. In some possible cases, relationships may also exist between the first element in the first architecture and multiple elements (such as the second element and the third element) in the second architecture, as shown in Table 5 below.

[0156] Table 5 Examples of relationships between architectures

[0157] First architecture Second architecture Element of first architecture Element of second architecture Correlation relationship Business architecture Business architecture Business capability Business process n:n Business architecture Business architecture Value stream Business capability 1：n Business architecture Business architecture Value stream stage Business process 1：n Business architecture Information architecture Business capability Business object 1：n Business architecture Information architecture Business process Business object 1：n Business architecture Application architecture Business capability Application 1：n Business architecture Application architecture Business process Application n:n Business architecture Application architecture Business service Application service n:n Application architecture Information architecture Application Business object 1：n

[0158] The first element mentioned above can be one of all the elements included in the first architecture, or it can be one of the key elements included in the first architecture. The second element can be one of all the elements included in the second architecture, or it can be one of the key elements included in the second architecture. The third element can be one of all the elements included in the second architecture, or it can be one of the key elements included in the second architecture. This application does not limit this.

[0159] In this embodiment, the computing device uses a rule-matching system to obtain the probability that a relationship exists between the first architecture and the second architecture. Based on this probability, the computing device displays a second interface containing the enterprise architecture. Thus, the computing device displays the second interface containing the enterprise architecture according to the rule-matching system. This avoids multiple communications and improves the efficiency of building the enterprise architecture. Eliminating the need for multiple communications reduces the impact of differences in staff skill levels on the resulting enterprise architecture, ensuring its accuracy and lowering the requirements for staff.

[0160] It is understood that, in order to achieve the functions in the above embodiments, the computing device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and method steps described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0161] The above text combines Figures 1 to 5 This document describes in detail the method for constructing an enterprise architecture according to this embodiment. The following will combine... Figure 6 This describes the apparatus for building an enterprise architecture according to this embodiment.

[0162] Figure 6 A structural schematic diagram of an enterprise architecture construction device provided in this application, such as... Figure 6As shown, the enterprise architecture construction device 600 includes a display module 610 and a processing module 620. The display module 610 is used to display an initialization interface. The initialization interface includes an architecture construction entry point. The processing module 620 is used to display a first interface using the display module 610 in response to user operations on the entry point. The first interface includes a business architecture, an information architecture, and an application architecture. The processing module 620 is also used to process the business architecture, information architecture, and application architecture based on a rule matching system in response to user operations on the first interface, obtaining the probability of a correlation between the first architecture and a second architecture. The first architecture is a business architecture, information architecture, or application architecture, and the second architecture is also a business architecture, information architecture, or application architecture; the first architecture and the second architecture are different. The processing module 620 is also used to display a second interface using the display module 610 based on the probability of a correlation between the first architecture and the second architecture. The second interface includes an enterprise architecture, which includes an enterprise business architecture, an enterprise information architecture, an enterprise application architecture, and the correlation between these three architectures.

[0163] In some possible scenarios, processing module 620 is specifically used to: process the business architecture, information architecture, and application architecture based on the rule matching system to obtain the probability that there is a correlation between a first element in the first architecture and a second element in the second architecture. Here, the first element is one of the elements included in the first architecture, and the second element is one of the elements included in the second architecture. The correlation between the first architecture and the second architecture is represented by the probability that the first element and the second element are correlated.

[0164] In some possible scenarios, the probability of a relationship between the first element and the second element includes: a first probability and a second probability. The first probability is the probability of a relationship between the first element and the second element calculated according to the general matching rules in the rule matching system. The general matching rules include one or more of the following: name matching rules and responsible person matching rules. Name matching rules are used to obtain the degree of matching between the names of elements included in different architectures, and responsible person matching rules are used to obtain the degree of matching between the responsible persons corresponding to the elements included in different architectures. The second probability is the probability of a relationship between the first element and the second element calculated according to specific matching rules in the rule matching system. Specific matching rules include: attribute matching rules. Attribute matching rules are used to obtain the degree of matching between the attributes of elements included in different architectures.

[0165] In some possible scenarios, the processing module 620 is specifically used to: process the business architecture, information architecture, and application architecture based on the general matching rules in the rule matching system, and calculate the first probability that there is a correlation between the first element and the second element. The general matching rules include one or more of the following: name matching rules and responsible person matching rules. The name matching rules are used to obtain the degree of matching between the names of elements included in different architectures, and the responsible person matching rules are used to obtain the degree of matching between the responsible persons corresponding to the elements included in different architectures.

[0166] In some possible scenarios, the processing module 620 is specifically used to: process the business architecture, information architecture, and application architecture based on specific matching rules in the rule matching system, and calculate a second probability that there is a correlation between the first element and the second element. The specific matching rules include: attribute matching rules, which are used to obtain the degree of matching between the attributes of the elements included in different architectures.

[0167] In some possible scenarios, processing module 620 is specifically used to: process the business architecture, information architecture, and application architecture based on general matching rules in the rule matching system, and calculate a first probability that there is a relationship between the first element and the second element. The general matching rules include one or more of the following: name matching rules and responsible person matching rules. The name matching rules are used to obtain the degree of matching between the names of elements included in different architectures, and the responsible person matching rules are used to obtain the degree of matching between the responsible persons corresponding to the elements included in different architectures. Processing module 620 is also specifically used to: process the business architecture, information architecture, and application architecture based on specific matching rules in the rule matching system, and calculate a second probability that there is a relationship between the first element and the second element. The specific matching rules include: attribute matching rules, which are used to obtain the degree of matching between the attributes of elements included in different architectures.

[0168] In some possible scenarios, the relationship between the first architecture and the second architecture includes: the probability that there is a relationship between the first element of the first architecture and the second element of the second architecture satisfies either a first condition or a second condition. The first condition includes: either the first probability or the second probability is greater than or equal to a first probability threshold. The second condition includes: the first probability is less than the first probability threshold but greater than or equal to the second probability threshold, and the second probability is less than the first probability threshold but greater than or equal to a third probability threshold.

[0169] In some possible scenarios, enterprise architecture includes: relationships between a first element in a first architecture and an element in a second architecture. Alternatively, relationships between a first element in a first architecture and multiple elements in a second architecture.

[0170] In some possible scenarios, the second interface may also include: the probability that a relationship exists between the first architecture and the second architecture. The probability is a numerical value indicating the likelihood of a relationship existing.

[0171] For more details on the display module 610 and the processing module 620, please refer to the above description of the enterprise architecture construction method, which will not be repeated here.

[0172] When the enterprise architecture building apparatus 600 corresponds to the steps performed by the computing device in the enterprise architecture building method described in the embodiments of this application, the above and other operations and / or functions of each module in the enterprise architecture building apparatus 600 are respectively for implementing the method flow performed by the computing device in the foregoing figures.

[0173] It is worth noting that if the above-mentioned enterprise architecture building devices are implemented through software modules, for example, the software modules can be provided to users through a cloud service subscription model, and users can choose different subscription levels according to their needs; or, for example, the software modules can also provide enterprise-level customized services with professional domain customization, interface personalization and extended functions according to the needs of users or enterprises.

[0174] In addition, the enterprise architecture building device 600 provided in this application can also be made into a value-added service and provided to users, which is not limited in this application.

[0175] The enterprise architecture building apparatus in this application embodiment can also be implemented in hardware, such as a computing device, chip, or processor. For details on the specific implementation of the computing device, please refer to... Figure 1 For a description of the chip and processor's specific implementation, please refer to [link / reference]. Figure 2 The description of that will not be repeated here.

[0176] The method steps in this embodiment can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a computing device. Of course, the processor and storage medium can also exist as discrete components in a network device or terminal device.

[0177] This application also provides a computing device cluster. The computing device cluster includes at least one computing device, which may be a server with a display. In some embodiments, the computing device may also be a terminal device such as a desktop computer, laptop computer, or smartphone.

[0178] like Figure 7 As shown, Figure 7 This application provides a schematic diagram of a computing device cluster, which includes at least one computing device 110. The memory 112 of one or more computing devices 110 in the computing device cluster may store the same instructions for executing methods for building enterprise architectures.

[0179] In some possible implementations, the memory 112 of one or more computing devices 110 in the computing device cluster may also store partial instructions for executing the enterprise architecture construction method. In other words, a combination of one or more computing devices 110 can jointly execute instructions for executing the enterprise architecture construction method.

[0180] It should be noted that the memory 112 in different computing devices 110 within the computing device cluster can store different instructions, each used to execute a portion of the computing device's functions. That is, the instructions stored in the memory 112 of different computing devices 110 can implement the functions of one or more modules in the display module 610 and processing module 620.

[0181] In some possible implementations, one or more computing devices in a computing device cluster can be connected via a network. This network can be a wide area network (WAN) or a local area network (LAN). Figure 8 One possible implementation is shown. For example... Figure 8 As shown, Figure 8 This application provides a schematic diagram of a connection between computing devices, where two computing devices 110A and 110B are connected via a network. Specifically, they are connected to the network through communication interfaces in each computing device. In this possible implementation, the instructions stored in the memory 112 of computing device 110A can implement the functions implemented by the display module 610. Simultaneously, the instructions stored in the memory 112 of computing device 110B can implement the functions implemented by the processing module 620.

[0182] This application also provides a computer program product containing instructions. The computer program product may be a software or program product containing instructions capable of running on a computing device or 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 a method for building an enterprise architecture.

[0183] 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 that includes one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive). The computer-readable storage medium includes instructions that instruct the computing device to perform a method for constructing an enterprise architecture.

[0184] This application also provides a chip. The chip includes an interface circuit and a control circuit. The interface circuit is used to obtain a build request for an enterprise architecture, and the control circuit is used to implement the functions of the computing device in the enterprise architecture build method.

[0185] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video disc (DVD); or it can be a semiconductor medium, such as a solid-state drive (SSD).

[0186] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for constructing an enterprise architecture, characterized in that, The method includes: The initialization interface is displayed; the initialization interface includes an architecture construction entry point; In response to the user's operation on the entry point, a first interface is displayed; the first interface includes: business architecture, information architecture, and application architecture; In response to the user's operation on the first interface, the business architecture, the information architecture, and the application architecture are processed based on the rule matching system to obtain the probability that there is a correlation between the first architecture and the second architecture; Wherein, the first architecture is the business architecture, the information architecture, or the application architecture, and the second architecture is the business architecture, the information architecture, or the application architecture, and the first architecture and the second architecture are different; Based on the probability of a correlation between the first architecture and the second architecture, a second interface is displayed; the second interface includes an enterprise architecture, which includes an enterprise business architecture, an enterprise information architecture, an enterprise application architecture, and the correlation between the enterprise business architecture, the enterprise information architecture, and the enterprise application architecture.

2. The method according to claim 1, characterized in that, The rule-based matching system processes the business architecture, the information architecture, and the application architecture to obtain the probability that there is a correlation between the first architecture and the second architecture, including: Based on the rule matching system, the business architecture, the information architecture, and the application architecture are processed to obtain the probability that there is a correlation between the first element in the first architecture and the second element in the second architecture; Wherein, the first element is one of the elements included in the first architecture, the second element is one of the elements included in the second architecture, and the relationship between the first architecture and the second architecture is represented by the probability that the first element and the second element have a relationship.

3. The method according to claim 2, characterized in that, The process of processing the business architecture, information architecture, and application architecture based on the rule matching system to obtain the probability that there is a correlation between a first element in the first architecture and a second element in the second architecture includes: Based on the general matching rules in the rule matching system, the business architecture, the information architecture, and the application architecture are processed to calculate the first probability that there is a correlation between the first element and the second element; The general matching rules include one or more of the following: name matching rules and responsible person matching rules. The name matching rules are used to obtain the degree of matching between the element names of elements included in different architectures, and the responsible person matching rules are used to obtain the degree of matching between the responsible persons corresponding to the elements included in different architectures.

4. The method according to claim 2, characterized in that, The process of processing the business architecture, information architecture, and application architecture based on the rule matching system to obtain the probability that there is a correlation between a first element in the first architecture and a second element in the second architecture includes: Based on specific matching rules in the rule matching system, the business architecture, the information architecture, and the application architecture are processed to calculate a second probability that there is a correlation between the first element and the second element; The specific matching rules include: attribute matching rules, which are used to obtain the degree of matching between the attributes of the elements included in different architectures.

5. The method according to claim 2, characterized in that, The process of processing the business architecture, information architecture, and application architecture based on the rule matching system to obtain the probability that there is a correlation between a first element in the first architecture and a second element in the second architecture includes: Based on the general matching rules in the rule matching system, the business architecture, the information architecture, and the application architecture are processed to calculate the first probability that there is a correlation between the first element and the second element; The general matching rules include one or more of the following: name matching rules and responsible person matching rules. The name matching rules are used to obtain the degree of matching between the element names of the elements included in different architectures, and the responsible person matching rules are used to obtain the degree of matching between the responsible persons corresponding to the elements included in different architectures. And based on specific matching rules in the rule matching system, the business architecture, the information architecture, and the application architecture are processed to calculate a second probability that there is a correlation between the first element and the second element; The specific matching rules include: attribute matching rules, which are used to obtain the degree of matching between the attributes of the elements included in different architectures.

6. The method according to any one of claims 3-5, characterized in that, The relationships between the first architecture and the second architecture include: The probability that there is a correlation between the first element and the second element satisfies either the first condition or the second condition; The first condition includes: either the first probability or the second probability is greater than or equal to a first probability threshold; the second condition includes: the first probability is less than the first probability threshold and greater than or equal to a second probability threshold, and the second probability is less than the first probability threshold and greater than or equal to a third probability threshold.

7. The method according to any one of claims 1-6, characterized in that, The enterprise architecture includes: The relationship between a first element in the first architecture and an element in the second architecture; Alternatively, the association between a first element in the first architecture and multiple elements in the second architecture.

8. The method according to any one of claims 1-7, characterized in that, The second interface also includes: a probability that there is an association between the first architecture and the second architecture, the probability being used to indicate a numerical value of the likelihood of an association.

9. An enterprise architecture building device, characterized in that, The device includes: The display module is used to: display an initialization interface; the initialization interface includes an architecture construction entry point; The processing module is configured to: respond to a user's operation on the entry point and display a first interface using the display module; the first interface includes: business architecture, information architecture, and application architecture; The processing module is further configured to: respond to the user's operation on the first interface, process the business architecture, the information architecture, and the application architecture based on the rule matching system, and obtain the probability that there is a correlation between the first architecture and the second architecture; Wherein, the first architecture is the business architecture, the information architecture, or the application architecture, and the second architecture is the business architecture, the information architecture, or the application architecture, and the first architecture and the second architecture are different; The processing module is further configured to: display a second interface using the display module based on the probability that there is an association between the first architecture and the second architecture; the second interface includes an enterprise architecture, which includes an enterprise business architecture, an enterprise information architecture, and an enterprise application architecture, as well as the association between the enterprise business architecture, the enterprise information architecture, and the enterprise application architecture.

10. The apparatus according to claim 9, characterized in that, The processing module is specifically used to: process the business architecture, the information architecture, and the application architecture based on the rule matching system to obtain the probability that there is a correlation between the first element in the first architecture and the second element in the second architecture; Wherein, the first element is one of the elements included in the first architecture, the second element is one of the elements included in the second architecture, and the relationship between the first architecture and the second architecture is represented by the probability that the first element and the second element have a relationship.

11. The apparatus according to claim 10, characterized in that, The processing module is specifically used to: process the business architecture, the information architecture, and the application architecture based on the general matching rules in the rule matching system, and calculate the first probability that there is a correlation between the first element and the second element; The general matching rules include one or more of the following: name matching rules and responsible person matching rules. The name matching rules are used to obtain the degree of matching between the element names of elements included in different architectures, and the responsible person matching rules are used to obtain the degree of matching between the responsible persons corresponding to the elements included in different architectures.

12. The apparatus according to claim 10, characterized in that, The processing module is specifically used to: process the business architecture, the information architecture, and the application architecture based on specific matching rules in the rule matching system, and calculate a second probability that there is a correlation between the first element and the second element; The specific matching rules include: attribute matching rules, which are used to obtain the degree of matching between the attributes of the elements included in different architectures.

13. The apparatus according to claim 10, characterized in that, The processing module is specifically used to: process the business architecture, the information architecture, and the application architecture based on the general matching rules in the rule matching system, and calculate the first probability that there is a correlation between the first element and the second element; The general matching rules include one or more of the following: name matching rules and responsible person matching rules. The name matching rules are used to obtain the degree of matching between the element names of the elements included in different architectures, and the responsible person matching rules are used to obtain the degree of matching between the responsible persons corresponding to the elements included in different architectures. The processing module is further specifically used to: process the business architecture, the information architecture, and the application architecture based on specific matching rules in the rule matching system, and calculate a second probability that there is a correlation between the first element and the second element; The specific matching rules include: attribute matching rules, which are used to obtain the degree of matching between the attributes of the elements included in different architectures.

14. The apparatus according to any one of claims 11-13, characterized in that, The relationships between the first architecture and the second architecture include: The probability that there is a correlation between the first element of the first architecture and the second element of the second architecture satisfies either the first condition or the second condition. The first condition includes: either the first probability or the second probability is greater than or equal to a first probability threshold; the second condition includes: the first probability is less than the first probability threshold and greater than or equal to a second probability threshold, and the second probability is less than the first probability threshold and greater than or equal to a third probability threshold.

15. A processor, characterized in that, It includes an interface circuit and a control circuit; the interface circuit is used to acquire user operations on the first interface and to cooperate with the control circuit to execute the method of any one of claims 1-8.

16. A computing device cluster, characterized in that, It includes at least one computing device, each computing device including a processor and a memory, the memory storing program code, and when the processor executes the program code, the processor is used to perform the method of any one of claims 1-8.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer instructions; when the computer instructions are executed in a computing device, the computing device performs the method of any one of claims 1-8.

18. A computer program product, characterized in that, When the computer program product is run in a computing device, the computing device performs the method of any one of claims 1-8.

Images