Enterprise architecture processing method, device, storage medium and electronic device

Abstract

The present invention discloses a method, device, storage medium and electronic device for processing enterprise architecture. Relating to the field of artificial intelligence technology, the method includes: obtaining a service call link and target physical table information of a service in the enterprise architecture; determining the target production operation model of the enterprise architecture through a software asset management system based on the service identifier of the service in the service call link and the target physical table information; determining the target preset model of the enterprise architecture through an architecture asset management system and a software asset management system based on the service identifier of the service in the service call link; comparing the target production operation model with the target preset model, and if the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, generating a service record to be governed for the service call link. The present invention solves the technical problem of using a semi-manual method to identify the consistency between the business model of the enterprise architecture and the computer implementation, resulting in poor identification effect and low consistency maintenance efficiency.

Description

Technical Field

[0001] The present invention relates to the field of financial technology, and in particular to a method, device, storage medium and electronic device for processing enterprise architecture. Background Art

[0002] The banking and financial industry is using enterprise-level architecture methods to streamline and build enterprise-level business processes. This process decomposes enterprise-level strategies into strategic capabilities and embeds them into business models. IT then implements these strategies through operational business models. Some institutions have already completed enterprise-level business architecture construction, and many are also advancing business architecture modeling and achieving phased results. Currently, enterprise-level business architecture modelers are responsible for implementing business modeling results through coding.

[0003] The value of enterprise architecture lies in enabling enterprise-level capability building and reuse, and rapidly launching product innovations. The core is that the task components that carry business capabilities must fully correspond to the IT services that connect to them. This includes the data tables accessed and updated by IT services, and the call relationships between IT services must be consistent with the business architecture modeling results. Only then can IT support flexible assembly while the business utilizes task components for flexible combination and innovation. Currently, a list of the docking results between task components and IT services has been compiled, and some banks have established architectural asset management and control platforms to implement management and control of these assets. However, management and control measures are limited to manual identification. For example, when application architects and business architects confirm the consistency between the business model and IT services, they need to delve into the code implementation level to verify the program logic, the data tables accessed, and the specific operations on the data tables. This is theoretically feasible, but the actual cost is enormous, and it is impossible to invest sufficient resources to ensure the consistency of the business architecture and IT architecture.

[0004] The following problems exist in the relevant technologies: (1) The identification method that does not conform to the principle of consistency between service call relationships and business models is to manually determine whether the service call relationship is consistent with the predecessor and successor relationships of the task components through the services and service call links registered on the software asset management platform. In case of inconsistency, the corresponding service R&D team is manually contacted to confirm the technical transformation plan. (2) The existing identification method that does not conform to the principle of consistency between service implementation and business models is to export a project service and business model docking relationship list report through the architecture asset management system. Through manual report analysis, if there is a service docking with multiple task components, the relevant R&D team is contacted to communicate and confirm the technical transformation plan. (3) The existing identification method that does not conform to the principle of consistency between service access to data tables and task component model access to data entity models is to verify which data tables the code accesses through code inspection and then compare them with the model. If there is inconsistent data access, the relevant R&D team is contacted to communicate and confirm the technical transformation plan.

[0005] Existing identification and analysis technologies rely on report data scattered across various management systems or tools. Problem types are identified through semi-automatic and semi-manual analysis, and technical solutions are then confirmed through offline communication based on the problem type. This results in a low degree of automation, high communication costs, and low efficiency. This long-term trend can lead to a serious misalignment between business models and IT implementation, making them incompatible and unreusable. This necessitates reinvesting resources to rebuild both the business model and IT service implementation, rebuilding the enterprise-level business architecture, and promoting implementation, wasting enterprise resources.

[0006] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0007] Embodiments of the present invention provide a method, device, storage medium, and electronic device for processing an enterprise architecture, so as to at least solve the technical problems of using a semi-manual method to identify the consistency between the business model of the enterprise architecture and the computer implementation, resulting in poor recognition effect and low consistency maintenance efficiency.

[0008] According to one aspect of an embodiment of the present invention, a method for processing an enterprise architecture is provided, comprising: obtaining a service call link and target physical table information of a service in the enterprise architecture, wherein the target physical table information includes at least a physical table accessed when calling a service when implementing a business transaction of the enterprise, the physical table being used to store the business data of the enterprise; determining a target production and operation model of the enterprise architecture through a software asset management system based on a service identifier of the service in the service call link and the target physical table information, wherein the target production and operation model includes at least service call information of the running state of the enterprise architecture; determining a target preset model of the enterprise architecture through an architecture asset management system and a software asset management system based on the service identifier of the service in the service call link, wherein the target preset model is used to determine the consistency between the business model of the enterprise architecture and a computer implementation; comparing the target production and operation model with the target preset model to obtain a comparison result, wherein the comparison result includes at least whether the business model of the enterprise architecture is consistent with the computer implementation; and generating a service record to be governed for the service call link if the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation.

[0009] Furthermore, if the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, after generating the service record to be governed of the service call link, it also includes: based on the service record to be governed, searching for the governance policy corresponding to the service record to be governed in the governance policy library, wherein the service record to be governed includes at least: a service identifier, a rule model identifier of a rule model, and the rule model is used to represent the docking rules between the business architecture of the enterprise architecture and the corresponding computer implementation; based on the governance policy, adjusting the business model and computer implementation of the enterprise architecture.

[0010] Furthermore, based on the service identifier of the service in the service call link and the target physical table information, the target production operation model of the enterprise architecture is determined through the software asset management system, including: based on the service identifier, determining the scenario identifier of the business scenario to which the service call relationship in the service call link belongs through the software asset management system, and based on the scenario identifier, determining the association relationship between the target business model in the enterprise architecture and the service in the service call link; based on the service call link, the association relationship and the target physical table information, determining the target production operation model of the enterprise architecture.

[0011] Furthermore, based on the service identifier of the service in the service call link, the target preset model of the enterprise architecture is determined through the architecture asset management system and the software asset management system, including: based on the service identifier and the business scenario identifier of the service identifier, obtaining the associated business model of the service call link through the architecture asset management system, wherein the associated business model at least includes the association relationship between the business models related to the service identifier; based on the service identifier and the business scenario identifier, determining the target service information of the service in the service call link through the software asset management system, wherein the target service information at least includes: basic service information and service development information; based on the associated business model, the target service information of the service in the service call link and the rule model library, determining the target preset model, wherein the rule model library at least includes the docking rules between the business architecture of the enterprise architecture and the corresponding computer implementation.

[0012] Furthermore, obtaining the service call link and target physical table information of the service in the enterprise architecture includes: marking the target transaction running in the enterprise architecture based on the target identification, and based on the marked target transaction, obtaining the service called by the target transaction in the enterprise architecture, and the physical table accessed when calling each service; obtaining the service subscription information of the service called by the target transaction based on the service registration center of the enterprise architecture; determining the service call link and the target physical table information based on the service called by the target transaction, the physical table accessed when calling each service and the service subscription information.

[0013] Furthermore, if the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, a record of the service to be governed of the service call link is generated based on the comparison result, including: determining the service to be governed of the enterprise architecture based on the comparison result; generating the record of the service to be governed based on the rule model associated with the service to be governed and the service to be governed.

[0014] Furthermore, the target preset model includes at least: task components, services, physical tables, data entities, the association relationship between task components and data entities, the association relationship between task components and services, the association relationship between services and physical tables, and the association relationship between data entities and physical tables.

[0015] According to another aspect of an embodiment of the present invention, a device for processing an enterprise architecture is provided, comprising: an acquisition unit configured to acquire a service call link and target physical table information of a service in the enterprise architecture, wherein the target physical table information includes at least a physical table accessed when a service is called when implementing a business transaction of the enterprise, the physical table being used to store the business data of the enterprise; a first determination unit configured to determine, through a software asset management system, a target production and operation model of the enterprise architecture based on a service identifier of the service in the service call link and the target physical table information, wherein the target production and operation model includes at least service call information of the running state of the enterprise architecture; a second determination unit configured to determine, through an architecture asset management system and a software asset management system, a target preset model of the enterprise architecture based on the service identifier of the service in the service call link, wherein the target preset model is used to determine the consistency between the business model of the enterprise architecture and a computer implementation; a comparison unit configured to compare the target production and operation model with the target preset model to obtain a comparison result, wherein the comparison result includes at least whether the business model of the enterprise architecture is consistent with the computer implementation; and a generation unit configured to generate a service record to be governed for the service call link if the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation.

[0016] Furthermore, the processing device of the enterprise architecture also includes: a search unit, which is used to generate a service record to be governed of the service call link, and then search for the governance policy corresponding to the service record to be governed in the governance policy library based on the service record to be governed if the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation. The governance policy includes at least: a service identifier and a rule model identifier of a rule model, and the rule model is used to represent the docking rules between the business architecture of the enterprise architecture and the corresponding computer implementation; an adjustment unit, which is used to adjust the business model and computer implementation of the enterprise architecture according to the governance policy.

[0017] Furthermore, the first determination unit includes: a first processing sub-unit, used to determine, based on the service identifier, through the software asset management system, the scenario identifier of the business scenario to which the service call relationship in the service call link belongs, and based on the scenario identifier, determine the association relationship between the target business model in the enterprise architecture and the service in the service call link; a first determination sub-unit, used to determine the target production operation model of the enterprise architecture based on the service call link, the association relationship and the target physical table information.

[0018] Furthermore, the second determination unit includes: a first acquisition sub-unit, used to obtain the associated business model of the service call link through the architecture asset management system based on the service identifier and the business scenario identifier of the service identifier, wherein the associated business model at least includes the association relationship between business models related to the service identifier; a second determination sub-unit, used to determine the target service information of the service in the service call link through the software asset management system based on the service identifier and the business scenario identifier, wherein the target service information at least includes: basic service information and service development information; a third determination sub-unit, used to determine the target preset model based on the associated business model, the target service information of the service in the service call link and the rule model library, wherein the rule model library at least includes the business architecture of the enterprise architecture and the corresponding computer-implemented docking rules.

[0019] Furthermore, the acquisition unit includes: a second acquisition subunit, configured to tag a target transaction running in the enterprise architecture based on a target identifier, and based on the tagged target transaction, to acquire, in the enterprise architecture, services called by the target transaction and a physical table accessed when calling each service; a second processing subunit, configured to acquire, based on a service registration center of the enterprise architecture, service subscription information of the service called by the target transaction;

[0020] The fourth determining subunit is configured to determine the service calling link and the target physical table information based on the services called by the target transaction, the physical table accessed when calling each service, and the service subscription information.

[0021] Furthermore, the generation unit includes: a fifth determination subunit, for determining the services to be governed of the enterprise architecture based on the comparison result; and a generation subunit, for generating the service records to be governed based on the rule model associated with the services to be governed and the services to be governed.

[0022] Furthermore, the target preset model includes at least: task components, services, physical tables, data entities, the association relationship between task components and data entities, the association relationship between task components and services, the association relationship between services and physical tables, and the association relationship between data entities and physical tables.

[0023] According to another aspect of an embodiment of the present invention, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the above-mentioned enterprise architecture processing methods by executing the executable instructions.

[0024] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided, which stores a computer program, wherein when the computer program runs, the device where the computer-readable storage medium is located is controlled to execute any one of the above-mentioned enterprise architecture processing methods.

[0025] In the present invention, a service call link and target physical table information of a service in an enterprise architecture are obtained, wherein the target physical table information includes at least the physical table accessed when the service is called when implementing the enterprise's business transaction, and the physical table is used to store the enterprise's business data; based on the service identifier of the service in the service call link and the target physical table information, a target production operation model of the enterprise architecture is determined through a software asset management system, wherein the target production operation model includes at least the service call information of the enterprise architecture's running state; based on the service identifier of the service in the service call link, a target preset model of the enterprise architecture is determined through an architecture asset management system and a software asset management system, wherein the target preset model is used to determine the consistency between the business model of the enterprise architecture and the computer implementation; a comparison result is obtained by comparing the target production operation model with the target preset model, wherein the comparison result includes at least whether the business model of the enterprise architecture is consistent with the computer implementation; if the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, a service record to be governed for the service call link is generated. This solves the technical problem of using a semi-manual method to identify the consistency between the business model of the enterprise architecture and the computer implementation, which has poor identification effect and low consistency maintenance efficiency. In the present invention, the target production operation model of the enterprise architecture operation state is compared with the target preset model to determine the consistency of the business model of the enterprise architecture and the computer implementation, thereby avoiding the use of manual judgment on the consistency of the business model of the enterprise architecture and the computer implementation, thereby achieving the technical effect of improving the efficiency of judging the consistency of the business model of the enterprise architecture and the computer implementation. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0027] Figure 1 is a flowchart of an optional enterprise architecture processing method according to an embodiment of the present invention;

[0028] Figure 2 is a flowchart of an optional implementation process of an enterprise architecture according to an embodiment of the present invention;

[0029] Figure 3 is a flow chart of an optional business model and service consistency identification and governance process according to an embodiment of the present invention;

[0030] Figure 4 is a schematic diagram of an optional method for constructing a preset model according to an embodiment of the present invention;

[0031] Figure 5 is a schematic diagram of an optional service actual operation model according to an embodiment of the present invention;

[0032] Figure 6 is a schematic diagram of a preset model for consistency of association between an optional task component and a data entity and IT implementation according to an embodiment of the present invention;

[0033] Figure 7 is a schematic diagram of a physical table operation model for actual service access according to an optional embodiment of the present invention;

[0034] Figure 8 This is a system architecture diagram of a physical table operation model for an optional service actual access according to an embodiment of the present invention;

[0035] Figure 9 is a schematic diagram of a processing device of an optional enterprise architecture according to an embodiment of the present invention;

[0036] Figure 10 is a schematic diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

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

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

[0039] For the convenience of description, some terms or nouns involved in the present invention are explained below.

[0040] The Continuous Value Enhancement Methodology is an industry-leading enterprise architecture methodology. Through strategic goal decomposition and business modeling methods such as process modeling, entity modeling, and product modeling, it guides enterprises to discover potential value, accurately define value, optimize value processes, rapidly manufacture and deliver value, and create new and high-end value. It is the theoretical foundation for building our enterprise architecture. The Continuous Value Enhancement Methodology primarily includes process modeling, market modeling, and entity modeling.

[0041] Business architecture: guides and defines the details of the business model, translating the vision and strategy into an execution-level business model.

[0042] Business model: used to undertake business architecture, implement business architecture, create enterprise value by using key resources and dynamic capabilities, and plan how the enterprise can make profits and develop sustainably.

[0043] Process model: The business that needs to be performed to achieve the goal, in order to deliver specific services or products to customers. The process is a set of business activities initiated by customers and interacting with customers, and is performed to achieve a certain purpose.

[0044] Business area: The business area is the first-level process. Each business area consists of a set of activities including planning, execution, and supervision. The business area structure reflects the enterprise value creation process.

[0045] Value Stream: The second-level process shows the value stream of a specific business area. It is the process of value creation. The process is a set of activities that interact with customers and participate in the realization of goals in the business area.

[0046] Activity: The third-level process is triggered by events and describes the interaction process with stakeholders in order to fulfill stakeholder needs.

[0047] Steps: The fifth-level process defines the work sequence, responsibilities, and goals for completing a task. The specific steps need to follow the corresponding business rules.

[0048] Business events: These are used to identify customer expectations and verify whether activities support business events. Business events are categorized as internal and external. External events are triggered by external sources, such as customers, regulators, and third parties. Internal events are triggered internally by the bank, such as conditions and time triggers.

[0049] Service: From a business perspective, a service is a business activity that is standardized, has independent and complete business meaning, and can produce specific results. From a technical perspective, a service is a discoverable, callable, reusable, encapsulated software resource. It is a capability for application functions to access each other, and this access capability is explicitly published through standardized service descriptions. The internal technical implementation of a service is transparent to its consumers, and the external implementation can be expressed in the form of standard interfaces, distributed services, services with interfaces, program components, batch processing, etc. The characteristics of services: first, they emphasize business integrity, and second, they adopt standardized definitions and unified management.

[0050] It should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for display and analysis, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties. For example, an interface is set up between this system and the relevant user or organization. Before obtaining relevant information, it is necessary to send an acquisition request to the aforementioned user or organization through the interface, and obtain the relevant information after receiving the consent information fed back by the aforementioned user or organization.

[0051] The present invention will be further described below with reference to various embodiments.

[0052] Example 1

[0053] According to an embodiment of the present invention, a method embodiment of an optional enterprise architecture processing method is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0054] Figure 1 is a flowchart of an optional enterprise architecture processing method according to an embodiment of the present invention. Figure 1 As shown, the method includes the following steps:

[0055] Step S101: Obtain a service call link and target physical table information of a service in an enterprise architecture, wherein the target physical table information at least includes a physical table accessed when a service is called when implementing a business transaction of the enterprise, and the physical table is used to store the business data of the enterprise.

[0056] The above-mentioned service call link can be a service call link composed of services called to conduct business transactions or respond to transaction requests in the enterprise architecture. The above-mentioned target physical table information can be the physical table accessed when calling the service when implementing the business transaction. The above-mentioned physical table can be used to store enterprise production data and obtain enterprise production business data.

[0057] Step S102: Based on the service identifier of the service in the service call link and the target physical table information, the target production operation model of the enterprise architecture is determined through the software asset management system, wherein the target production operation model at least includes the service call information of the enterprise architecture operation state.

[0058] The above-mentioned software asset management system can manage the software assets of the enterprise-level architecture in financial institutions, and may include relevant information of services in the enterprise-level architecture of financial institutions (such as service call relationships, basic service information, development teams, applications) and other information. Based on the service identifier of the service in the service call link and the target physical table information, the target production operation model of the service call link can be obtained.

[0059] The target production operation model may include service call information of the enterprise architecture operation state, and may also include the call relationship between components, the relationship between components and services, and the call relationship between services in the enterprise architecture operation state.

[0060] Step S103: Based on the service identifier of the service in the service call link, the target preset model of the enterprise architecture is determined through the architecture asset management system and the software asset management system, wherein the target preset model is used to determine the consistency between the business model of the enterprise architecture and the computer implementation.

[0061] The above-mentioned target preset model can be compared with the target production operation model in the running state to determine the consistency between the business model of the enterprise architecture and the computer implementation. The above-mentioned target preset model can include the association relationship between components in the business model of the enterprise architecture, and the association relationship between the business model and the corresponding computer software system. That is, the target preset model can be the business architecture planning of the enterprise architecture related to the service call link.

[0062] Step S104 , obtaining a comparison result by comparing the target production operation model with the target preset model, wherein the comparison result at least includes whether the business model of the enterprise architecture is consistent with the computer implementation.

[0063] By comparing the target production operation model in the actual operation state with the target preset model, it is possible to determine whether the business architecture model of the enterprise architecture in the actual operation state is consistent with the planned business architecture or business model, or to determine whether the computer-level implementation of the enterprise architecture is consistent with the business architecture plan or business model.

[0064] Step S105: If the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, a service record to be governed of the service call link is generated.

[0065] In this embodiment, if the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, a record of the service call link to be governed can also be generated based on the comparison result to improve the timely processing of locations in the enterprise architecture where the model and the computing implementation are inconsistent, thereby ensuring consistency between the design and implementation of the enterprise architecture.

[0066] Through the above steps, the target production operation model of the enterprise architecture operation state is compared with the target preset model to determine the consistency between the business model of the enterprise architecture and the computer implementation, avoiding the use of manual judgment on the consistency between the business model of the enterprise architecture and the computer implementation, thereby achieving the technical effect of improving the efficiency of judging the consistency between the business model of the enterprise architecture and the computer implementation, and further solving the technical problems of using a semi-manual method to identify the consistency between the business model of the enterprise architecture and the computer implementation, resulting in poor identification effect and low consistency maintenance efficiency.

[0067] In order to avoid the situation where manual judgment of the consistency between the planning and design of the enterprise architecture and the computer implementation is used, and manual determination of the governance strategy is inefficient, in this embodiment, if the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, then after generating the service record to be governed of the service call link, the following content is also included: based on the service record to be governed, the governance policy corresponding to the service record to be governed is searched in the governance policy library, wherein the service record to be governed includes at least: a service identifier, a rule model identifier of a rule model, and the rule model is used to represent the docking rules between the business architecture of the enterprise architecture and the corresponding computer implementation; based on the governance strategy, the business model and computer implementation of the enterprise architecture are adjusted.

[0068] In this embodiment, if the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, the relevant service will be recorded as a service to be governed. The record must include information such as the rule model ID (corresponding to the above-mentioned rule model identifier) ​​and the service's affiliated R&D team. The affiliated R&D team can be obtained through the association of the service information record. Based on the rule model ID of the service to be governed record, the corresponding governance policy record is found in the governance policy library, and the governance policy ID is updated to the service to be governed record. The governance policy library can be a pre-maintained processing solution for the corresponding rule model library, including problem description, suggestions, and other information.

[0069] Based on the list of services to be governed in the governance records, a suspected governance recommendation record can be generated and sent to the target team's responsible position according to the delivery strategy. The suspected governance recommendation record can include information such as the governance service and service call relationship, corresponding strategy, receiving team, and receiving responsibility position. The delivery strategy can set different receiving positions and delivery frequencies based on different rule models, and emails are sent to the corresponding personnel. This enables rapid determination of the consistency between the enterprise architecture planning and design and computer implementation, thereby improving the efficiency of maintaining the consistency between the enterprise architecture planning and design and computer implementation.

[0070] In order to accurately obtain the architectural model in the running enterprise architecture, in this embodiment, based on the service identification of the service in the service call link and the target physical table information, the target production operation model of the enterprise architecture is determined through the software asset management system, which also includes the following contents: based on the service identification, the scenario identification of the business scenario to which the service call relationship in the service call link belongs is determined through the software asset management system, and based on the scenario identification, the association relationship between the target business model in the enterprise architecture and the service in the service call link is determined; based on the service call link, the association relationship and the target physical table information, the target production operation model of the enterprise architecture is determined.

[0071] In this embodiment, the service design information unit of the enterprise architecture can be used to obtain the business scenario to which the service call relationship in the software asset management system belongs using the service unique ID (i.e., service identifier), and lock the relationship between the business model and service-related information, that is, the call relationship between the two services is subordinate to a unique business scenario ID (the business scenario can be the activity ID in the business model) to support the situation where a service is reused by multiple business scenarios.

[0072] The service design information unit uses the service unique ID and business scenario ID (i.e., scenario identifier) ​​to obtain the associated business models of call link-related services (such as activities, relationships between activities and task components, task components, relationships between task components, data entities, relationships between task components and data entities, relationships between task components and services, relationships between data entities and physical tables, etc.) through the architecture asset management system; obtains service-related information (such as service call relationships, basic service information, development teams, applications) and other information through the software asset management system, and determines the target production operation model of the enterprise architecture based on the service call link, associated relationships and target physical table information, thereby accurately obtaining the architecture model in the running enterprise architecture.

[0073] In order to accurately obtain the planning model of the enterprise architecture related to the service call link, based on the service identifier of the service in the service call link, the target preset model of the enterprise architecture is determined through the architecture asset management system and the software asset management system, including: based on the service identifier and the business scenario identifier of the service identifier, obtaining the associated business model of the service call link through the architecture asset management system, wherein the associated business model at least includes the association relationship between the business models related to the service identifier; based on the service identifier and the business scenario identifier, determining the target service information of the service in the service call link through the software asset management system, wherein the target service information at least includes: basic service information and service development information; based on the associated business model, the target service information of the service in the service call link and the rule model library, determining the target preset model, wherein the rule model library at least includes the docking rules between the business architecture of the enterprise architecture and the corresponding computer implementation.

[0074] In this embodiment, the service design information unit can obtain the service ID in the service call link, the business scenario ID obtained through the software asset return system, and the associated business model of the call link related services obtained through the architecture asset management system (for example: activities, the relationship between activities and task components, task components, the relationship between task components, data entities, the relationship between task components and data entities, the relationship between task components and services, the relationship between data entities and physical tables, etc.); and obtain service-related information, namely target service information (for example, service call relationships, basic service information, development team or service development information, applications), etc. through the software asset management system. Based on the associated business model, the target service information of the service called in the service call link, and the rule model library, the target preset model is determined, achieving the technical effect of accurately obtaining the planning model of the enterprise architecture related to the service call link.

[0075] In order to avoid the inability to accurately obtain the actual call link information in the running enterprise architecture, in this embodiment, obtaining the service call link and target physical table information of the service in the enterprise architecture also includes the following: based on the target identification tag, the target transaction running in the enterprise architecture is marked, and based on the marked target transaction, the service called by the target transaction and the physical table accessed when calling each service are obtained in the enterprise architecture; based on the service registration center of the enterprise architecture, the service subscription information of the service called by the target transaction is obtained; based on the service called by the target transaction, the physical table accessed when calling each service and the service subscription information, the service call link and the target physical table information are determined.

[0076] In this embodiment, the service operation information unit of the enterprise architecture can be used to mark each transaction with a unique Trace ID (corresponding to the target identifier) ​​for the services running on production, track the actual call link of a single transaction request, and the physical table accessed by each called service (the service called by the target transaction) in the middle. Then, through the service registration center, the service and service subscription information is obtained, and the running service call link and the accessed physical table information (corresponding to the above-mentioned target physical table information) are constructed, thereby achieving the technical effect of accurately obtaining the real call link information in the running enterprise architecture.

[0077] In order to avoid the inefficiency of generating records of services to be governed in the enterprise architecture through manual judgment, in this embodiment, if the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, the records of services to be governed in the service call link are generated based on the comparison result. The process of generating records of services to be governed in the service call link also includes the following: determining the services to be governed in the enterprise architecture based on the comparison result; and generating records of services to be governed based on the rule model associated with the services to be governed and the services to be governed.

[0078] In this embodiment, when the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, the relevant service is recorded as a service to be governed, and the record must include the rule model ID (corresponding to the above-mentioned rule model identifier), the service's affiliated R&D team and other information, where the affiliated R&D team can be obtained through the association of the service information record. According to the rule model ID of the service to be governed record, the corresponding governance policy record is found in the governance policy library, and the governance policy ID is updated to the service to be governed record. The governance policy library can be a processing solution for the corresponding rule model library maintained in advance, including problem description, suggestions and other information, achieving the technical effect of providing efficiency in generating the service records to be governed in the enterprise architecture.

[0079] In order to ensure that the business architecture planned for the enterprise architecture is consistent with the corresponding computer implementation, the target preset model at least includes: task components, services, physical tables, data entities, the association relationship between task components and data entities, the association relationship between task components and services, the association relationship between services and physical tables, and the association relationship between data entities and physical tables.

[0080] In this embodiment, the above-mentioned target preset model, the relationship between business models (such as the relationship between task components and data entities), the relationship between business models and IT systems (such as the relationship between task components and services, the relationship between data entities and physical tables), and the relationship between IT systems (such as the relationship between services and physical tables) ensure that the target preset model includes various relationships in the enterprise architecture.

[0081] The present invention will be further described below in conjunction with another optional embodiment.

[0082] Example 2

[0083] This embodiment provides another optional enterprise architecture processing method and system. Through this embodiment, based on existing service information, service call relationships, service access data tables and other information, by building a preset model and the actual operation model, comparing them according to the problem rule model, setting corresponding governance policies for the rule model, and building an integrated solution for automated preservation and governance with consistent design and implementation, while reducing governance costs and improving work efficiency.

[0084] Figure 2 is a flowchart of an optional implementation process of an enterprise architecture according to an embodiment of the present invention, such as Figure 2 As shown, the implementation process of enterprise architecture can include three stages: engineering implementation stage, project requirements compilation stage, and software development stage.

[0085] Figure 3 is a flowchart of an optional business model and service consistency identification and governance process according to an embodiment of the present invention, such as Figure 3 As shown, the specific steps include:

[0086] Step S201, obtain the service call relationship and accessed data table information. For the service running on production, the service operation information unit marks each transaction with a unique Trace ID (corresponding to the target identifier in Example 1), tracks the actual call link of a single request, and the physical table accessed by each called service in the middle, and then obtains the service and service subscription information through the service registration center to construct the running service call link and the accessed physical table information.

[0087] Step S202, lock the architecture assets through the service and service call relationship. The service design information unit uses the service unique ID (corresponding to the service identifier in Example 1) to obtain the business scenario to which the service call relationship belongs in the software asset management system, and locks the relationship between the business model and service-related information, that is, the call relationship between the two services is subordinate to a unique business scenario ID (the business scenario can be the activity ID in the business model) to support the situation where a service is reused by multiple business scenarios.

[0088] Step S203, obtain the business model associated with the relevant service and the association information between business models. The service design information unit uses the service unique ID and business scenario ID (corresponding to the scenario identifier in Example 1) to obtain the associated business model of the call link related service (such as activities, relationships between activities and task components, task components, relationships between task components, data entities, relationships between task components and data entities, relationships between task components and services, relationships between data entities and physical tables, etc.) through the architecture asset management system; obtain service-related information (such as service call relationships, basic service information, development teams, applications) and other information through the software asset management system.

[0089] Step S204, identify the services to be governed and the list of service docking relationships according to the rule model, and the consistency judgment rule model unit acts as an identification engine, through the operation characteristics of the services required in the consistency judgment rule model unit, and the service design information is obtained to form a preset model and incorporate it into the preset model library; the service information, service call link information, and service access data table information obtained from the production operation status are used to generate a production operation model library; after comparing the preset model with the production operation model consistent with the Trace ID, a single service or service operation chain that does not meet the characteristics of the consistency judgment rule model is identified, and the relevant service is recorded as a service to be governed. The record must include the rule model ID (corresponding to the rule model identifier in Example 1), the service's affiliated R&D team and other information, where the affiliated R&D team can be obtained through the association of the service information record. The consistency judgment rule model mentioned in the step is also a key component of this step, that is, the rule model library, which is used to save information such as the service governance rule model characteristics. Different rule models have a globally unique ID number.

[0090] S205: Generate a recommended governance policy based on the governance policy library. Based on the rule model ID of the service to be governed, find the corresponding governance policy record in the governance policy library and update the governance policy ID to the service to be governed. The governance policy library mentioned in this step is a pre-maintained solution for the corresponding rule model library, including information such as problem description and suggestions. A visual strategy diagram and a snapshot of the preset model are saved for comparison.

[0091] S206: Send suspected services to be managed, their service call relationships, and corresponding policies. Based on the list of services to be managed obtained in the previous step, a suspected management recommendation record is generated and sent to the target team's responsible position according to the sending policy. The record must include information such as the management service and service call relationship, corresponding policy, receiving team, and receiving responsibility position. The sending policy can be configured based on different rule models, with different receiving positions and sending frequencies, and emails are sent to the corresponding personnel.

[0092] The following examples illustrate the core functions of steps S204 and S205, including the preset model, operational model, rule model, corresponding governance strategy recommendations, and recommended governance effect diagrams. The specific processing steps are as follows:

[0093] 1. Task Component Consistency

[0094] (1) Define the rule model library in the consistency determination rule model unit. According to management and control requirements, set the rule library for the relationship between assets. This rule library can be flexibly customized according to actual management and control needs and is not limited to the business architecture and IT docking rules stated in this embodiment. The business architecture and IT docking rules are as follows: For example, a task component can be associated with one or more services; the calling relationship between services cannot exceed the relationship between task components. For example, calls within task components are legal, calls that are consistent with the relationship between task components are legal, and any calls that are inconsistent with the above are illegal.

[0095] (2) Figure 4 is a schematic diagram of an optional construction of a preset model according to an embodiment of the present invention, such as Figure 4 The design consistency identification engine unit obtains business model and service-related information from the architecture asset management system and software asset management system to generate a pre-defined model. In this case, the pre-defined model is generated by obtaining the relationships between business models (such as the relationships between task components) and the relationships between business models and IT systems (such as the relationships between task components and services) from the architecture asset management system. This pre-defined model serves as a reference standard for identifying task component consistency.

[0096] (3) Figure 5 FIG. 1 is a schematic diagram of an optional service actual operation model according to an embodiment of the present invention. Figure 5 , design consistency recognition engine unit recognition processing Figure 4 Based on the service operation characteristics recorded, combined with the service information and service call link information obtained in steps S201 and S202, the service actual operation model is generated, and the result is compared with the preset model; according to the rule model library in the consistency judgment rule model unit, for the service records to be governed that cannot be covered by the preset model (for example Figure 5 H, F, G and their calling relationships), find the corresponding governance policy in the governance policy library, and recommend that the development team of the application to which services H, F, and G belong integrate related services based on the visualized strategy graph snapshot and the relationship between the task components and models provided by the system, or increase the relationship between the business model and the service.

[0097] 2. The consistency of the association between task components and data entities and IT implementation.

[0098] (4) Define the rule model library in the consistency determination rule model unit. According to the management and control requirements, set the rule library for the association relationship between assets. This rule library can be flexibly customized according to the actual management and control needs and is not limited to the business architecture and IT docking rules stated in this embodiment. The consistency rules for the association between the task component and the data entity and the IT implementation are as follows: From the data entity associated with the task component, obtain the list of physical tables used by the task component based on the docking assets of the data entity and the physical table; compare the IT service docked with the task component and the list of physical tables actually accessed by the service from holographic monitoring. If the range of the physical table list accessed by the IT service is smaller than the physical table list used by the task component, the IT physical implementation is consistent with the business model.

[0099] (5) Schematic diagram of constructing the preset model Figure 4 The design consistency recognition engine unit scans the asset library based on the rule model library to generate a preset model. In this embodiment, the preset model is generated by obtaining the relationships between business models (such as the relationship between task components and data entities), the relationships between business models and IT systems (such as the relationship between task components and services, and the relationship between data entities and physical tables), and the relationships between IT systems (such as the relationship between services and physical tables) from the architecture asset management system.

[0100] (6) Figure 7 FIG. 1 is a schematic diagram of a physical table operation model for actual service access according to an optional embodiment of the present invention. Figure 7 , design consistency recognition engine unit scanning recognition processing Figure 6 The preset model of the consistency between the association of task components and data entities and IT implementation is used to generate the physical table operation model of the actual service access based on the recorded service operation characteristics, combined with the service information and service call link information obtained in steps S201 and S202 ( Figure 7 ) and compare the results with the preset model. For the service records that cannot be covered by the preset model, find the corresponding governance policy in the governance policy library. It is recommended that the development team of the application to which the service belongs integrate and split the service according to the business model based on the visual strategy diagram snapshot, cancel the access to the relevant physical tables; or supplement and improve the association between the business model and IT, and increase the relationship between the entity and the physical table.

[0101] Figure 8 This is a system architecture diagram of a physical table operation model for an optional service actual access according to an embodiment of the present invention. Figure 8As shown, it includes: business model implementation monitoring system, architecture asset management system, software resource system, as well as service design information unit, service operation information unit, consistency judgment rule model unit, governance strategy unit, design consistency identification engine unit, preset model library, production operation model library, service library to be governed and governance recommendation unit.

[0102] This embodiment provides a general method for identifying consistency between business models and IT services. It can analyze and manage the consistency between IT implementation and business models based on general systems and personalized customized rules. By automatically running and capturing production data, the service call links and service access data table results obtained are fully compared and analyzed with business model assets and business model and IT service docking assets. The consistency between IT implementation and business model is verified with production data. For inconsistencies, a checklist can be generated to help related applications carry out consistency governance, saving a lot of investment in manual consistency verification, solving the problem of consistency verification between business models and IT implementation that has plagued the industry, and achieving continuous and effective preservation of business models and IT implementations.

[0103] The present invention will be further described below in conjunction with another optional embodiment.

[0104] Example 3

[0105] This embodiment provides an optional embodiment of a processing device for an enterprise architecture, and each implementation unit in the processing device corresponds to each implementation step in the first embodiment.

[0106] Figure 9 is a schematic diagram of a processing device of an optional enterprise architecture according to an embodiment of the present invention, such as Figure 9 As shown, the processing device includes: an acquisition unit 91, a first determination unit 92, a second determination unit 93, a comparison unit 94, and a generation unit 95.

[0107] Specifically, the acquisition unit 91 is configured to acquire a service call link and target physical table information of a service in the enterprise architecture, wherein the target physical table information at least includes a physical table accessed when a service is called to implement a business transaction of the enterprise, and the physical table is used to store the business data of the enterprise;

[0108] A first determining unit 92 is configured to determine, through a software asset management system, a target production operation model of the enterprise architecture based on the service identifier of the service in the service call link and the target physical table information, wherein the target production operation model at least includes the service call information of the enterprise architecture operation state;

[0109] A second determining unit 93 is configured to determine a target preset model of the enterprise architecture based on the service identifier of the service in the service call link through the architecture asset management system and the software asset management system, wherein the target preset model is used to determine the consistency between the business model of the enterprise architecture and the computer implementation;

[0110] A comparison unit 94 is configured to compare the target production operation model with the target preset model to obtain a comparison result, wherein the comparison result at least includes whether the business model of the enterprise architecture is consistent with the computer implementation;

[0111] The generating unit 95 is configured to generate a to-be-governed service record of the service call link if the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation.

[0112] In a third embodiment of the present application, an enterprise architecture processing device is provided. An acquisition unit 91 can acquire a service call link and target physical table information of a service in the enterprise architecture. The target physical table information includes at least a physical table accessed when a service is called when implementing a business transaction of the enterprise, and the physical table is used to store the business data of the enterprise. A first determination unit 92 determines a target production and operation model of the enterprise architecture through a software asset management system based on a service identifier of the service in the service call link and the target physical table information. The target production and operation model includes at least service call information of the enterprise architecture in operation. A second determination unit 93 determines a target preset model of the enterprise architecture through an architecture asset management system and a software asset management system based on the service identifier of the service in the service call link. The target preset model is used to determine the consistency between the business model of the enterprise architecture and a computer implementation. A comparison unit 94 compares the target production and operation model with the target preset model to obtain a comparison result. The comparison result includes at least whether the business model of the enterprise architecture is consistent with the computer implementation. If the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, a generation unit 95 generates a service record to be governed for the service call link. This solves the technical problem of using semi-manual methods to identify the consistency between the enterprise architecture's business model and the computer implementation, resulting in poor identification results and low consistency maintenance efficiency. In the present invention, the consistency between the enterprise architecture's business model and the computer implementation is determined by comparing the target production operation model of the enterprise architecture's operating state with the target preset model, avoiding the need for manual judgment of the consistency between the enterprise architecture's business model and the computer implementation, thereby achieving the technical effect of improving the efficiency of judging the consistency between the enterprise architecture's business model and the computer implementation.

[0113] Optionally, in the enterprise architecture processing device provided in Example 3 of the present application, the enterprise architecture processing device also includes: a search unit, which is used to generate a service record to be governed of the service call link, and then search the governance policy corresponding to the service record to be governed in the governance policy library based on the service record to be governed if the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, wherein the service record to be governed includes at least: a service identifier, a rule model identifier of a rule model, and the rule model is used to represent the docking rules between the business architecture of the enterprise architecture and the corresponding computer implementation; an adjustment unit, which is used to adjust the business model and computer implementation of the enterprise architecture based on the governance policy.

[0114] Optionally, in the processing device for the enterprise architecture provided in Example 3 of the present application, the first determination unit includes: a first processing sub-unit, used to determine, based on the service identifier, through the software asset management system, the scenario identifier of the business scenario to which the service call relationship in the service call link belongs, and based on the scenario identifier, determine the association relationship between the target business model in the enterprise architecture and the service in the service call link; the first determination sub-unit, used to determine the target production operation model of the enterprise architecture based on the service call link, the association relationship and the target physical table information.

[0115] Optionally, in the processing device of the enterprise architecture provided in Example 3 of the present application, the second determination unit includes: a first acquisition sub-unit, used to obtain the associated business model of the service call link through the architecture asset management system based on the service identifier and the business scenario identifier of the service identifier, wherein the associated business model at least includes the association relationship between business models related to the service identifier; a second determination sub-unit, used to determine the target service information of the service in the service call link through the software asset management system based on the service identifier and the business scenario identifier, wherein the target service information at least includes: basic service information and service development information; a third determination sub-unit, used to determine the target preset model based on the associated business model, the target service information of the service in the service call link and the rule model library, wherein the rule model library at least includes the business architecture of the enterprise architecture and the corresponding computer-implemented docking rules.

[0116] Optionally, in the processing device of the enterprise architecture provided in Example 3 of the present application, the acquisition unit includes: a second acquisition sub-unit, which is used to mark the target transaction running in the enterprise architecture based on the target identification, and based on the marked target transaction, obtain the service called by the target transaction in the enterprise architecture, and the physical table accessed when calling each service; a second processing sub-unit, which is used to obtain the service subscription information of the service called by the target transaction based on the service registration center of the enterprise architecture; a fourth determination sub-unit, which is used to determine the service call link and the target physical table information based on the service called by the target transaction, the physical table accessed when calling each service, and the service subscription information.

[0117] Optionally, in the processing device for enterprise architecture provided in Example 3 of the present application, the generation unit includes: a fifth determination sub-unit, used to determine the services to be governed of the enterprise architecture based on the comparison results; and a generation sub-unit, used to generate records of services to be governed based on the rule model associated with the services to be governed and the services to be governed.

[0118] Optionally, in the processing device of the enterprise architecture provided in Example 3 of the present application, the target preset model includes at least: task components, services, physical tables, data entities, the association relationship between task components and data entities, the association relationship between task components and services, the association relationship between services and physical tables, and the association relationship between data entities and physical tables.

[0119] The processing device of the above-mentioned enterprise architecture may also include a processor and a memory. The above-mentioned acquisition unit 91, first determination unit 92, second determination unit 93, comparison unit 94, generation unit 95, etc. are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.

[0120] The processor includes a kernel that retrieves corresponding program units from memory. One or more kernels can be provided. By adjusting kernel parameters, the target production operation model of the enterprise architecture's operational state is compared with a target preset model to determine the consistency of the enterprise architecture's business model with its computer implementation. This avoids manual determination of the consistency between the enterprise architecture's business model and its computer implementation, thereby achieving the technical effect of improving the efficiency of determining the consistency between the enterprise architecture's business model and its computer implementation.

[0121] The above-mentioned memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0122] According to another aspect of an embodiment of the present invention, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the above-mentioned enterprise architecture processing methods by executing the executable instructions.

[0123] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided, which stores a computer program, wherein when the computer program runs, the device where the computer-readable storage medium is located is controlled to execute any one of the above-mentioned enterprise architecture processing methods.

[0124] Figure 10is a schematic diagram of an electronic device according to an embodiment of the present invention, such as Figure 10 As shown, an embodiment of the present invention provides an electronic device 100, which includes a processor, a memory, and a program stored in the memory and executable on the processor. When the processor executes the program, any one of the above-mentioned enterprise architecture processing methods is implemented.

[0125] The serial numbers of the above embodiments of the present invention are for description only and do not represent the advantages or disadvantages of the embodiments.

[0126] In the above embodiments of the present invention, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

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

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

[0129] In addition, the functional units in the various embodiments of the present invention may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

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

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

Claims

1. A method for processing enterprise architecture, characterized in that: include: Obtaining a service call link and target physical table information of a service in the enterprise architecture, wherein the target physical table information at least includes a physical table accessed when a service is called when implementing a business transaction of the enterprise, and the physical table is used to store the business data of the enterprise; Based on the service identifier of the service in the service call link and the target physical table information, determining, through a software asset management system, a target production operation model of the enterprise architecture, wherein the target production operation model at least includes service call information of the enterprise architecture operation state; Based on the service identifier of the service in the service call link, determining the target preset model of the enterprise architecture through the architecture asset management system and the software asset management system, wherein the target preset model is used to determine the consistency between the business model of the enterprise architecture and the computer implementation; Comparing the target production operation model with the target preset model to obtain a comparison result, wherein the comparison result at least includes whether the business model of the enterprise architecture is consistent with the computer implementation; If the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, generating a service record to be governed for the service call link; Wherein, based on the service identifier of the service in the service call link, determining the target preset model of the enterprise architecture through the architecture asset management system and the software asset management system includes: Acquiring, based on the service identifier and the business scenario identifier of the service identifier, an associated business model of the service call link through an architecture asset management system, wherein the associated business model at least includes an association relationship between business models related to the service identifier; Determining target service information of the service in the service call link through the software asset management system based on the service identifier and the business scenario identifier, wherein the target service information includes at least basic service information and service development information; Determining the target preset model based on the associated business model, target service information of the service in the service call link, and a rule model library, wherein the rule model library at least includes the business architecture of the enterprise architecture and corresponding computer-implemented docking rules; The method further includes finding corresponding governance policies in a governance policy library for service records to be governed that cannot be covered by a preset rule model according to the rule model library.

2. The processing method according to claim 1, characterized in that If the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, after generating the to-be-governed service record of the service call link, the method further includes: Searching, in accordance with the service record to be governed, a governance policy corresponding to the service record to be governed in a governance policy library, wherein the service record to be governed includes at least: a service identifier and a rule model identifier of a rule model, wherein the rule model is used to represent the business architecture of the enterprise architecture and the corresponding computer-implemented docking rules; Based on the governance policy, the business model and computer implementation of the enterprise architecture are adjusted.

3. The processing method according to claim 1, characterized in that Determining a target production operation model of the enterprise architecture through a software asset management system based on the service identifier of the service in the service call link and the target physical table information includes: Based on the service identifier, determining, through a software asset management system, a scenario identifier of a business scenario to which a service call relationship in the service call link belongs, and based on the scenario identifier, determining an association relationship between a target business model in the enterprise architecture and a service in the service call link; A target production operation model of the enterprise architecture is determined based on the service call link, the association relationship, and the target physical table information.

4. The processing method according to claim 1, characterized in that Obtain the service call link and target physical table information of services in the enterprise architecture, including: Marking a target transaction running in the enterprise architecture based on a target identifier, and obtaining, in the enterprise architecture, services called by the target transaction and physical tables accessed when calling each service based on the marked target transaction; Based on the service registration center of the enterprise architecture, obtaining service subscription information of the service called by the target transaction; The service call link and the target physical table information are determined based on the services called by the target transaction, the physical table accessed when calling each service, and the service subscription information.

5. The processing method according to claim 2, characterized in that: If the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation, a service record to be governed of the service call link is generated, including: Determining the services to be governed of the enterprise architecture according to the comparison result; Generate the service record to be governed according to the rule model associated with the service to be governed and the service to be governed.

6. The processing method according to claim 1, characterized in that The target preset model includes at least: task components, services, physical tables, data entities, the association relationship between task components and data entities, the association relationship between task components and services, the association relationship between services and physical tables, and the association relationship between data entities and physical tables.

7. A processing device for an enterprise architecture, characterized in that: include: an acquisition unit, configured to acquire a service call link and target physical table information of a service in an enterprise architecture, wherein the target physical table information at least includes a physical table accessed when a service is called when implementing a business transaction of the enterprise, and the physical table is used to store the business data of the enterprise; a first determining unit, configured to determine, through a software asset management system, a target production operation model of the enterprise architecture based on a service identifier of the service in the service call link and the target physical table information, wherein the target production operation model at least includes service call information of an operation state of the enterprise architecture; a second determining unit, configured to determine, based on the service identifier of the service in the service call link, a target preset model of the enterprise architecture through the architecture asset management system and the software asset management system, wherein the target preset model is used to determine consistency between a business model of the enterprise architecture and a computer implementation; a comparing unit, configured to compare the target production operation model with the target preset model to obtain a comparison result, wherein the comparison result at least includes whether the business model of the enterprise architecture is consistent with the computer implementation; a generating unit, configured to generate a to-be-governed service record of the service call link if the comparison result indicates that the business model of the enterprise architecture is inconsistent with the computer implementation; The second determining unit is further configured to obtain, through an architecture asset management system, an associated business model of the service call link based on the service identifier and the business scenario identifier of the service identifier, wherein the associated business model at least includes an association relationship between business models related to the service identifier; determine, through the software asset management system, target service information of the service in the service call link based on the service identifier and the business scenario identifier, wherein the target service information at least includes basic service information and service development information; determine the target preset model based on the associated business model, the target service information of the service in the service call link, and a rule model library, wherein the rule model library at least includes docking rules between the business architecture of the enterprise architecture and the corresponding computer implementation; The device is further configured to find corresponding governance policies in a governance policy library for service records to be governed that cannot be covered by a preset rule model according to the rule model library.

8. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein when the computer program is executed, the device where the computer-readable storage medium is located is controlled to execute the enterprise architecture processing method according to any one of claims 1 to 6.

9. An electronic device, characterized in that: The system comprises one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the enterprise architecture processing method according to any one of claims 1 to 6.

Images