Enterprise interface generation method and related device

Abstract

The invention discloses an enterprise interface generation method and a related device, and relates to the technical field of enterprise informatization. Comprising the steps of obtaining enterprise architecture assets based on an architecture meta-model; setting a plurality of services under the target element of the enterprise architecture asset, and setting a plurality of interfaces under the services; service numbers are distributed to the services according to a preset rule, and interface numbers are distributed to the interfaces; and describing the interface based on the self-defined attribute information to obtain the enterprise interface. A unique number generated according to a preset rule is allocated to a service and an interface, so that clear definition of a relationship between architecture elements is ensured; the interface is described in combination with self-defined attribute information, the information dimension of the interface is enriched, and subsequent accurate retrieval and efficient management of the interface are facilitated; therefore, the method provided by the invention can improve the management efficiency and traceability of enterprise architecture assets, and can ensure that the corresponding relationship between architecture elements is accurate; the problems of unreasonable interface design and redundant functions in the prior art can be solved.

Description

Technical Field

[0001] The present application relates to the field of enterprise information technology, and in particular to an enterprise interface generation method and related devices. Background Art

[0002] With the development of distributed architecture technology, enterprises are facing the challenges of a surge in the number of system interfaces and complex interactions. Current interface management focuses on lifecycle and operating status, ignoring source control, resulting in problems such as unreasonable interface design and functional redundancy. How to reasonably design the interfaces (also called enterprise interfaces) in various systems of enterprises in distributed architecture systems, such as human resource management systems and financial management systems, has become one of the technical problems that need to be solved in the field of enterprise information technology. Summary of the invention

[0003] Based on the above problems, the present application provides an enterprise interface generation method, which can reasonably design the interfaces in the enterprise system in a distributed architecture system, realize the control of the interfaces from the source, and thereby reduce the functional redundancy of the interfaces.

[0004] The embodiments of the present application disclose the following technical solutions:

[0005] The first aspect of the present application provides an enterprise interface generation method, comprising:

[0006] Based on the architecture metamodel, an enterprise architecture asset is obtained; the elements and numbers in the enterprise architecture asset correspond one to one; the numbers corresponding to the elements are generated according to a preset rule; the preset rule indicates that the number of the child element includes the number of the parent element; the child element and the parent element are two elements in the enterprise architecture asset that have a containment relationship; the parent element contains the child element;

[0007] Setting a plurality of services under the target element of the enterprise architecture asset, and setting a plurality of interfaces under the service; and assigning a service number to the service and an interface number to the interface according to the preset rule; the target element is a system component in the application architecture asset in the enterprise architecture asset;

[0008] The interface is described based on the customized attribute information to obtain an enterprise interface.

[0009] In an optional implementation, the enterprise architecture assets include business architecture assets, data architecture assets and application architecture assets; wherein,

[0010] The business functions in the business architecture assets are associated with the conceptual data models in the data architecture assets; the business functions in the business architecture assets are corresponding to the function numbers in the application architecture assets.

[0011] In an optional implementation, the business functions in the business architecture asset are associated with the conceptual data model in the data architecture asset, specifically:

[0012] The business functions in the business architecture assets are associated with the conceptual data models in the data architecture assets through business objects.

[0013] In an optional implementation, the custom attributes include interface name, interface protocol, interface path, interface status, interface consumer and interface performance parameters; the interface status includes online, paused and offline; the interface consumer includes system component number and / or system component name.

[0014] In an optional implementation, the method further includes:

[0015] The operating status of the plurality of enterprise interfaces is displayed through the application system management platform; the operating status includes the interface status, calling frequency, calling time and interface performance.

[0016] In an optional implementation, displaying the operation status of the plurality of enterprise interfaces through the application system management platform includes:

[0017] Obtaining the running status of a target enterprise interface through an enterprise business application; the target enterprise interface is an enterprise interface registered in the enterprise business application among the plurality of enterprise interfaces; the enterprise business application includes but is not limited to a SOFA business application and a TCS business application;

[0018] The operating status of the target enterprise interface among the plurality of enterprise interfaces is displayed through the application system management platform.

[0019] In an optional implementation, the method further includes:

[0020] Displaying an interface asset map on an application system management platform; Displaying an interface asset map on an application system management platform; The interface asset map indicates the association relationship between the elements in the enterprise architecture assets and the interface.

[0021] A second aspect of the present application provides an enterprise interface generation device, including:

[0022] An enterprise architecture asset generation module, used to obtain enterprise architecture assets based on an architecture metamodel; the elements in the enterprise architecture assets correspond to the numbers one by one; the numbers corresponding to the elements are generated according to a preset rule; the preset rule indicates that the number of the child element includes the number of the parent element; the child element and the parent element are two elements in the enterprise architecture assets that have a containment relationship; the parent element contains the child element;

[0023] A service interface setting module, used to set a plurality of services under the target element of the enterprise architecture asset, and set a plurality of interfaces under the service; assign service numbers to the services and interface numbers to the interfaces according to the preset rules; the target element is a system component in the application architecture asset in the enterprise architecture asset;

[0024] The enterprise interface production module is used to describe the interface based on user-defined attribute information to obtain the enterprise interface.

[0025] A third aspect of the present application provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the steps of the method introduced in any implementation manner of the first aspect are implemented.

[0026] A fourth aspect of the present application provides an electronic device, including:

[0027] a memory having a computer program stored thereon;

[0028] A processor is used to execute the computer program in the memory to implement the steps of the method introduced in any implementation manner of the first aspect.

[0029] Compared with the prior art, this application has the following beneficial effects:

[0030] The present application discloses a method for generating an enterprise interface, including: obtaining an enterprise architecture asset based on an architecture metamodel; setting multiple services under a target element of the enterprise architecture asset, and setting multiple interfaces under the service; assigning a service number to the service and an interface number to the interface according to a preset rule; describing the interface based on user-defined attribute information to obtain an enterprise interface. In the present application, the numbers corresponding to the elements are generated according to preset rules; the preset rules indicate that the number of the child element includes the number of the parent element.

[0031] By assigning unique numbers generated according to preset rules to services and interfaces, and embedding the parent element number in the child element number, a clear definition of the relationship between architectural elements is ensured; the interface is described in detail in combination with custom attribute information, which enriches the information dimension of the interface and facilitates subsequent accurate retrieval and efficient management of the interface; therefore, the enterprise interface generated by the method disclosed in this application can significantly improve the management efficiency and traceability of enterprise architecture assets, ensure the accuracy of the correspondence between architectural elements, and lay a solid foundation for the digital transformation and business innovation of the enterprise. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0033] Figure 1 A flowchart of a method for generating an enterprise interface provided in an embodiment of the present application;

[0034] Figure 2 A schematic diagram of the structure of an architecture meta-model provided in an embodiment of the present application;

[0035] Figure 3 A schematic diagram of an enterprise architecture asset provided in an embodiment of the present application;

[0036] Figure 4 A schematic diagram of an interface of a system application management platform provided in an embodiment of the present application;

[0037] Figure 5 A schematic diagram of the structure of an enterprise interface generation device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0038] With the development of distributed architecture technology, the number of enterprise systems is increasing. For example, enterprises generally have multiple systems such as human resource management systems and financial management systems. Each system includes a large number of interfaces, which makes the interaction between systems extremely complex. How to reasonably control the interfaces in the system is one of the technical problems that need to be solved in the field of enterprise information technology.

[0039] Currently, the industry's interface management methods usually focus on the management of interface lifecycle and operating status, while ignoring the control of interface resources. As a result, problems such as unreasonable interface definition or design, and similar or repeated interface functions in different systems have occurred, leading to a waste of development resources and, in serious cases, posing hidden dangers to production safety.

[0040] To solve the above problems, the present application discloses a method for generating an enterprise interface, including: obtaining enterprise architecture assets based on an architecture metamodel; setting multiple services under a target element of the enterprise architecture asset, and setting multiple interfaces under the service; assigning service numbers to services and interface numbers to interfaces according to preset rules; describing the interface based on user-defined attribute information to obtain an enterprise interface. In the present application, the numbers corresponding to the elements are generated according to preset rules; the preset rules indicate that the numbers of the child elements include the numbers of the parent elements.

[0041] By assigning unique numbers generated according to preset rules to services and interfaces, and embedding the parent element number in the child element number, a clear definition of the relationship between architectural elements is ensured; the interface is described in detail in combination with custom attribute information, which enriches the information dimension of the interface and facilitates subsequent accurate retrieval and efficient management of the interface; therefore, the enterprise interface generated by the method disclosed in this application can significantly improve the management efficiency and traceability of enterprise architecture assets, ensure the accuracy of the correspondence between architectural elements, and lay a solid foundation for the digital transformation and business innovation of the enterprise.

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

[0043] Figure 1 A flowchart of a method for generating an enterprise interface provided in an embodiment of the present application. Figure 1 As shown, the enterprise interface generation method disclosed in this application includes:

[0044] S101, based on the architecture metamodel, obtain enterprise architecture assets.

[0045] The architectural metamodel is an important tool in the architectural design and development process. It is used to define the basic elements of the model in a specific domain, the relationships between elements, or the representation of relationships. It is a model representation or model definition with a higher degree of abstraction than the model.

[0046] Figure 2 A schematic diagram of the structure of an architecture metamodel provided in an embodiment of the present application. Figure 2 As shown, the architecture metamodel includes business architecture related elements, application architecture related elements, data architecture related elements, technical architecture related elements and architecture relationships. Figure 2 The middle (a) area represents the logical structure of the business architecture. Figure 2 The middle (b) area represents the logical structure of the application architecture. Figure 2 The middle (c) area represents the logical structure of the data architecture. Figure 2 The middle (d) area represents the logical structure of the technical architecture (also called the "infrastructure architecture"). Figure 2 The relationship elements involved include: composition / inclusion, aggregation, execution / assignment, realization, connection point, etc.

[0047] Combination Figure 2As shown in area (a), the elements in the business architecture involve business domains, value streams, business processes, and business functions.

[0048] The business domain represents the "vertical" structure for building a unified view of enterprise capabilities. It is a higher-level business area formed by combining them according to their business relevance. For example, the business domain of the insurance industry is usually divided into product domain, marketing and sales domain, customer domain, operation domain, risk domain, etc.

[0049] The value stream represents the "horizontal" structure of building enterprise capabilities within a certain business domain. It is a collection of end-to-end value-added activities that create value contributions for stakeholders (users and customers). It also usually refers to a collection of business capabilities that support the business operations of the enterprise. For example, the value stream in the insurance field includes contract underwriting, preservation, reinsurance, renewal, claims settlement, etc.

[0050] A business process refers to a business activity completed by a business organization driven by a single business goal. Business processes support multi-level nesting: such as higher-level end-to-end processes, cross-functional processes, and lower-level sub-processes; for example, the underwriting business process includes: automatic underwriting, manual underwriting, and underwriting problem handling.

[0051] Business functions refer to business tasks that realize a specific business scenario. Business functions usually correspond to task nodes in business processes, which are a collection of a series of business operations completed by a role or system; for example, the manual underwriting business process consists of business functions such as task application and allocation, underwriting processing, underwriting review, and underwriting re-examination.

[0052] Combination Figure 2 As shown in area (a), the elements in the application architecture involve application domains, systems, system components, and modules.

[0053] Application domain refers to the construction and management characteristics of the application. For example, the application domain of the insurance industry is divided into product domain, marketing and high-level application domain based on the degree of business coupling.

[0054] A system is a logical entity that is composed of multiple closely related system components that carry a certain type of business value. For example, a system includes an underwriting system, an insurance underwriting system, a human resources system, and a financial system.

[0055] System components refer to a collection of modules that achieve a specific set of business goals; they are independently deployable, reusable, and replaceable. For example, the underwriting system is composed of the underwriting management system component and the underwriting processing system component.

[0056] A module is a logical collection of a set of functional underwriting processing system component packages that achieve a specific business goal; it has the characteristics of high cohesion and low coupling. For example, manual underwriting module and problem case processing module.

[0057] Combination Figure 2 As shown in area (c), the elements in the data architecture involve logical data entities, physical data entities and attributes.

[0058] Logical data entity refers to a data model that describes data entities, attributes, and relationships between data entities. For example, the logical data entity representing a car includes attributes such as vehicle type, usage nature, brand and model, as well as the relationship between the insured entity.

[0059] A physical data entity refers to the physical implementation of a conceptual data entity or a logical data entity in a database; it includes detailed information such as table names, column names, and column data types.

[0060] Attributes are used to represent the characteristics of objects in the real world; they are used to describe the properties, characteristics and relationships of data entities in the data architecture. For example, the conceptual data entity of a car logo contains vehicle type, brand model, etc., which are attributes; the primary key and foreign key of a logical data entity are attributes; the creation time and creator of a physical data entity table are attributes.

[0061] Combination Figure 2 As shown in area (d), the elements in the technical architecture include the definition of deployment groups, deployment units, and nodes.

[0062] A deployment group is a group of resources that provide the same operating environment, including load balancing, network, and storage resources. Resources within the group are managed in a unified manner.

[0063] A deployment unit is a collection of system components that can be deployed together. System components can be combined into deployment units based on factors such as dependencies and performance. A deployment unit can be deployed to the smallest physical unit that a deployment group can deploy.

[0064] A node refers to a terminal of a network system or a junction of multiple network lines. Nodes are divided into two categories: "transfer nodes" and "access nodes". The function of a "transfer node" is to support network connections, and it transfers and transmits information through the network; an "access node" is the source and destination of information exchange. Among them, access nodes include network ports of system components, virtual machines, and containers. Transfer nodes include various network ports and deployment groups of switches, gateways, routers, and firewall devices.

[0065] In obtaining Figure 2 After obtaining the meta-architecture model in the system, the enterprise's architecture assets can be sorted out to obtain enterprise architecture assets. Figure 3 A schematic diagram of an enterprise architecture asset provided in an embodiment of the present application. Figure 3 As shown, the enterprise architecture assets disclosed in this application include: business architecture assets (enterprise-level business architecture assets), architecture assets (enterprise-level application architecture assets) and application architecture assets (enterprise-level data architecture assets).

[0066] Figure 3 The business architecture assets shown in include business domain, value stream, business process and business function; enterprise application architecture assets include application domain, application system, system component, module number and function number; enterprise data architecture assets include data domain, data subject, conceptual data model and logical data model. For an introduction to related elements, refer to Figure 2 The description of the corresponding text in will not be repeated here.

[0067] Combination Figure 3 As shown, the elements and numbers in the enterprise architecture asset correspond one to one. The number corresponding to each element in the enterprise architecture asset is generated according to a preset rule; the preset rule indicates that the number of the child element includes the number of the parent element.

[0068] In this application, child elements and parent elements are two elements in an enterprise architecture asset that have a containment relationship; the parent element contains the child element. For example, Figure 3 The business domain is the parent element and the value stream is the child element. For another example, Figure 3 The system component is the parent element, and the encoding module and service encoding are both child elements.

[0069] Combination Figure 3 As shown, the business functions in the business architecture assets in the enterprise architecture assets are associated with the conceptual data models in the data architecture assets through business objects; the business functions in the business architecture assets correspond to the function numbers in the application architecture assets.

[0070] Understandably, Figure 3 The business object in the business function is the object to be processed; and the various operations processed by the business object correspond to Figure 3 The function number.

[0071] S102, setting a plurality of services under the target element of the enterprise architecture asset, and setting a plurality of interfaces under the services; and assigning service numbers to the services and interface numbers to the interfaces according to the preset rules.

[0072] The preset rule in this application means that the number of the child element includes the number of the parent element, that is, the number of the next-level element in the enterprise architecture asset includes the number of the previous-level element.

[0073] The target element in this application is the system component in the application architecture asset in the enterprise architecture asset. After obtaining the application architecture asset, you can set up multiple services under the system component under the application architecture asset according to the actual use requirements in the work, and set up multiple interfaces under each service. Then, according to the preset rules, assign service codes to services and assign interface codes to interfaces; so that there is a strong logical relationship between the service number, interface number and system component number.

[0074] For example, Figure 3 The service number included in the system component (number A-01-01-01) is A-01-01-01-S-01; the interface number included in the service number (A-01-01-01-S-01) is A-01-01-01-S-01-1-01.

[0075] From the above introduction, we can see that the numbering of the upper-level elements is embedded in the numbering of the lower-level elements, which greatly enhances the hierarchy and correlation between architectural elements, making it possible to clearly identify the subordination and dependency relationships between elements when managing and tracking architectural assets, thereby improving the maintainability and traceability of the architecture.

[0076] S103, describing the interface based on the customized attribute information to obtain an enterprise interface.

[0077] The customized attribute information in this application includes but is not limited to: interface number, interface name, interface protocol, interface path, interface description, interface status, interface consumer and interface performance parameters; interface status includes online, paused and offline; interface consumer includes system component number and / or system component name.

[0078] In an optional implementation, after obtaining a large number of interfaces according to the method disclosed in this application, the operating status of the interface can be displayed on the application system management platform. The operating status in this application includes the interface status (online, paused and offline), call frequency and call time (response time) and interface performance.

[0079] Figure 4 A schematic diagram of an interface of a system application management platform provided in an embodiment of the present application. Figure 4 As shown, after a large number of interfaces are generated, if the interface to be used (i.e., the target enterprise interface in this application) is applied through the enterprise business, that is, Figure 4The SOFA (Scalable Open Financial Architecture) business application, TCS (Tencent Cloud-native Suite) business application or any non-TCS / SOFA business application in the system is registered in the corresponding enterprise business application; the enterprise business application is connected to the system management platform for communication; the system management platform can collect information on the target enterprise interface registered on each enterprise business application, that is, the system management platform can obtain the operating status of the target enterprise interface through the enterprise business application; and then display the operating status of the target enterprise interface through the application system management platform.

[0080] Combination Figure 4 As shown in the figure, there are three major sections on the application system management platform, namely unified management of service catalog (management of target enterprise interface registration information), service lifecycle (process) management (management of target enterprise interface lifecycle) and system association management (i.e. the association between target enterprise application interface and each element in enterprise architecture assets). Unified management of service catalog is further divided into dynamic collection and analysis of service information and service document management; service lifecycle (process) management is further divided into service application, service listing, service release, service change, service docking and service delisting. Among them, dynamic collection and analysis of service information can collect the interface status, call frequency and response time parameters of the target enterprise interface; by comparing the scheduled parameters with the preset enterprise interface parameters (maximum call frequency and longest response time), etc., the enterprise's interface performance can be corrected.

[0081] Furthermore, the interface asset map can be displayed on the application system management platform. Figure 4 A schematic diagram of an interface asset map provided in an embodiment of the present application. Figure 4 As shown, the interface asset map indicates the association relationship between elements and interfaces in the enterprise architecture assets. Figure 4 The interface production information refers to the call frequency, call volume and response time; the interface management information includes interface number, interface name, interface protocol, interface description, interface path, status (online, paused, offline), interface consumer (system component number, system component name) and interface performance.

[0082] Based on the architecture metamodel, structured enterprise architecture assets can be generated. Each element in the enterprise architecture asset allows users to customize its attributes and attribute values, providing a high degree of flexibility and customization. More importantly, the relevant information of "service-interface" can be structured and easily read in the corresponding architecture element attributes and attribute values. This design makes the management and use of architecture information more efficient and accurate.

[0083] Traditional enterprise interface governance and management often focus on the interface life cycle and operation status management. The control of the source of the enterprise interface is often ignored. It is impossible to judge the rationality of the interface definition or design, whether the interface functions are similar or repeated, etc., resulting in repeated development, waste of resources, and increased operation and maintenance costs. The technical solution in this application is based on the overall design of business architecture-application architecture-data architecture, and then to the specific interface design, and unified rules and standards, so that the interface can be traced back to the business, service, and data used, making the interface design more reasonable, avoiding repeated development of similar interfaces, and improving the interface utilization rate. It can be quickly accessed and used, improving development efficiency, and further improving the interface management level.

[0084] Compared with the traditional interface management method, this application adopts the application system management platform to display the operating status of the interface; by realizing closed-loop management of the interface between the design state, management state, and operation state, the aggregation and unification of interface information is ensured; the consistency, integrity and observability of interface information are improved, and it also plays an important role in multiple scenarios such as active-active deployment, disaster recovery management, and resource optimization.

[0085] In summary, the present application discloses a method for generating an enterprise interface, including: obtaining an enterprise architecture asset based on an architecture metamodel; setting multiple services under a target element of the enterprise architecture asset, and setting multiple interfaces under the service; assigning a service number to the service and an interface number to the interface according to a preset rule; describing the interface based on custom attribute information to obtain an enterprise interface. In the present application, the numbers corresponding to the elements are generated according to preset rules; the preset rules indicate that the number of the child element includes the number of the parent element.

[0086] By assigning unique numbers generated according to preset rules to services and interfaces, and embedding the parent element number in the child element number, a clear definition of the relationship between architectural elements is ensured; the interface is described in detail in combination with custom attribute information, which enriches the information dimension of the interface and facilitates subsequent accurate retrieval and efficient management of the interface; therefore, the enterprise interface generated by the method disclosed in this application can significantly improve the management efficiency and traceability of enterprise architecture assets, and can ensure the accuracy of the correspondence between architectural elements.

[0087] Based on the enterprise interface generation method disclosed in the aforementioned embodiment, the present application also discloses an enterprise interface generation device. Figure 5 This is a schematic diagram of the structure of an enterprise interface generation device provided in an embodiment of the present application. Figure 5 As shown, the enterprise interface generation device 500 in the present application includes:

[0088] The enterprise architecture asset generation module 501 is used to obtain an enterprise architecture asset based on an architecture metamodel; the elements and numbers in the enterprise architecture asset correspond one to one; the numbers corresponding to the elements are generated according to a preset rule; the preset rule indicates that the number of the child element includes the number of the parent element; the child element and the parent element are two elements in the enterprise architecture asset that have a containment relationship; the parent element contains the child element;

[0089] The service interface setting module 502 is used to set a plurality of services under the target element of the enterprise architecture asset, and set a plurality of interfaces under the service; assign service numbers to the services and assign interface numbers to the interfaces according to the preset rules; the target element is a system component in the application architecture asset in the enterprise architecture asset;

[0090] The enterprise interface production module 503 is used to describe the interface based on the user-defined attribute information to obtain the enterprise interface.

[0091] In an optional implementation, the enterprise interface generating device 500 further includes:

[0092] The display module is used to display the operating status of multiple enterprise interfaces through the application system management platform; the operating status includes interface status, call frequency and call time and interface performance.

[0093] In an optional implementation, the display module includes:

[0094] A status acquisition unit, used to obtain the running status of a target enterprise interface through an enterprise business application; the target enterprise interface is an enterprise interface registered in the enterprise business application among the plurality of enterprise interfaces; the enterprise business application includes but is not limited to a SOFA business application and a TCS business application;

[0095] The status display unit is used to display the operating status of the target enterprise interface among the multiple enterprise interfaces through the application system management platform.

[0096] In an optional implementation, the display module further includes:

[0097] The asset map display unit is used to display the interface asset map on the application system management platform; the interface asset map indicates the association relationship between the elements in the enterprise architecture assets and the interface.

[0098] Based on the enterprise interface generation method and device provided in the aforementioned embodiments, the present application also provides a computer-readable storage medium, on which a computer program is stored, which, when executed by a processor, implements some or all of the steps in the aforementioned enterprise interface generation method.

[0099] Based on the enterprise interface generation method and device provided in the above embodiments, the present application further provides an electronic device, including:

[0100] a memory having a computer program stored thereon;

[0101] The processor is used to execute the computer program in the memory to implement part or all of the steps in the enterprise interface generation method provided in the above embodiment.

[0102] It should be noted that each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. The device embodiment described above is merely schematic, in which the unit described as a separate component may or may not be physically separated, and the component prompted as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative work.

[0103] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for generating an enterprise interface, characterized in that: The method comprises: Based on the architecture metamodel, an enterprise architecture asset is obtained; the elements and numbers in the enterprise architecture asset correspond one to one; the numbers corresponding to the elements are generated according to a preset rule; the preset rule indicates that the number of the child element includes the number of the parent element; the child element and the parent element are two elements in the enterprise architecture asset that have a containment relationship; the parent element contains the child element; Setting a plurality of services under the target element of the enterprise architecture asset, and setting a plurality of interfaces under the service; and assigning a service number to the service and an interface number to the interface according to the preset rule; the target element is a system component in the application architecture asset in the enterprise architecture asset; The interface is described based on the customized attribute information to obtain an enterprise interface.

2. The method according to claim 1, characterized in that The enterprise architecture assets include business architecture assets, data architecture assets and application architecture assets; among which, The business functions in the business architecture assets are associated with the conceptual data models in the data architecture assets; the business functions in the business architecture assets are corresponding to the function numbers in the application architecture assets.

3. The method according to claim 2, characterized in that The business functions in the business architecture assets are associated with the conceptual data models in the data architecture assets, specifically: The business functions in the business architecture assets are associated with the conceptual data models in the data architecture assets through business objects.

4. The method according to claim 1, characterized in that The custom attributes include interface name, interface protocol, interface path, interface status, interface consumer and interface performance parameters; the interface status includes online, paused and offline; the interface consumer includes system component number and / or system component name.

5. The method according to any one of claims 1 to 4, characterized in that: Also includes: Displaying the operating status of the plurality of enterprise interfaces through the application system management platform; The operating status includes interface status, call frequency and call time and interface performance.

6. The method according to claim 5, characterized in that The operating status of the plurality of enterprise interfaces is displayed through the application system management platform, including: Obtaining the running status of a target enterprise interface through an enterprise business application; the target enterprise interface is an enterprise interface registered in the enterprise business application among the plurality of enterprise interfaces; the enterprise business application includes but is not limited to a SOFA business application and a TCS business application; The operating status of the target enterprise interface among the plurality of enterprise interfaces is displayed through the application system management platform.

7. The method according to any one of claims 1 to 4, characterized in that Also includes: Display interface asset map on the application system management platform; The interface asset map indicates association relationships between elements in the enterprise architecture asset and the interface.

8. An enterprise interface generation device, characterized in that: The device comprises: An enterprise architecture asset generation module, used to obtain enterprise architecture assets based on an architecture metamodel; the elements in the enterprise architecture assets correspond to the numbers one by one; the numbers corresponding to the elements are generated according to a preset rule; the preset rule indicates that the number of the child element includes the number of the parent element; the child element and the parent element are two elements in the enterprise architecture assets that have a containment relationship; the parent element contains the child element; A service interface setting module, used to set a plurality of services under the target element of the enterprise architecture asset, and set a plurality of interfaces under the service; assign service numbers to the services and interface numbers to the interfaces according to the preset rules; the target element is a system component in the application architecture asset in the enterprise architecture asset; The enterprise interface production module is used to describe the interface based on user-defined attribute information to obtain the enterprise interface.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the method described in any one of claims 1 to 7 are implemented.

10. An electronic device, characterized in that: include: a memory having a computer program stored thereon; A processor, configured to execute the computer program in the memory to implement the steps of the method according to any one of claims 1 to 7.

Images