Architecture as service system and method based on TOGAF standard

Abstract

The invention relates to the technical field of enterprise services, in particular to an architecture-as-a-service system and method based on the TOGAF standard, and the method comprises the steps: receiving enterprise architecture data information inputted by a user based on a technical architecture through an architecture-as-a-service platform composed of a business architecture, a system architecture and the technical architecture, graphic data are assembled based on the enterprise architecture data information; based on the system architecture, generating view data according to the graphic data and a graphic layout algorithm, and judging whether the generated view data is a process implementation graph or not; and based on the business architecture, when the generated view data is a process implementation graph, performing quadratic programming by using a graph layout algorithm to generate new view data, and generating an architecture view from the new view data by using a graph editor. Therefore, the problems that an existing enterprise architecture implementation scheme is low in level coverage rate, a modeling tool is difficult to adapt to a complex enterprise environment, unified information management is lacked, and the connection degree of the enterprise architecture and landing implementation is low are solved.

Description

Technical Field

[0001] This application relates to the technical field of enterprise services, and particularly to an architecture as a service system and method based on the TOGAF standard. Background Art

[0002] Digital transformation requires systematic top-level design and blueprint planning to ensure the effective coordination between various technologies and businesses. The methodology of enterprise architecture planning can provide clear guidance for this process, enabling enterprises to better adapt to market changes and technological developments during the transformation process. When implementing technology empowerment, strengthening the digital technology platform is the foundation, which includes improving data infrastructure and cloud computing capabilities. At the same time, enhancing independent technology capabilities is the long-term goal to ensure the technical independence and competitiveness of enterprises. Additionally, improving the technical tool ecosystem can enhance the overall technical operation and management capabilities by introducing and integrating various technical tools. To effectively implement the top-level strategy to specific business goals, enterprises need to establish a complete set of management tools and information architecture. This full-link architecture information should cover all aspects such as requirements analysis, system design, and technical implementation to ensure the implementation of various strategic goals. Finally, by building comprehensive technology management tools, enterprises can manage their panoramic system architecture, ensuring the integration and connectivity of system architecture information. This management can empower the IT team, making it more efficient and scientific in technical decision-making, system architecture design, and technical architecture governance, thus supporting the sustainable development and innovation of enterprises.

[0003] Currently, not many enterprises at home and abroad have truly implemented enterprise architecture, and its functions are not perfect. Moreover, during the implementation of enterprise architecture, architecture views are often drawn based on foreign traditional drawing software such as Visio and open-source modeling software such as Archi. The architecture is graph-driven rather than model-driven, and architecture planning is often disjointed from implementation, making it difficult to ensure architecture freshness.

[0004] In summary, the existing enterprise architecture solutions have the following problems:

[0005] 1. Hierarchical coverage

[0006] Current situation: Mainly concentrated at the solution level, less involved in the enterprise-level panoramic architecture.

[0007] Impact: Restricts the cross-departmental and cross-system collaborative working ability, affecting the overall strategic planning.

[0008] 2. Modeling tool selection

[0009] Current situation: Relies on traditional drawing software (such as Visio) for modeling, graph-driven rather than model-driven.

[0010] Challenge: These tools have limitations in maintaining the consistency of architecture documents and are difficult to adapt to complex enterprise environments.

[0011] 3. Information management method

[0012] Current situation: The architecture information applied is stored dispersedly and lacks unified management.

[0013] Problem: It is difficult to ensure the integrity and consistency of data, increasing the difficulty of management and maintenance.

[0014] 4. Connection with the project implementation process

[0015] Current situation: Enterprise architecture planning is often disconnected from the project implementation process and fails to be embedded in the whole life process of the project for control.

[0016] Consequence: There are often some inconsistencies between the enterprise architecture and the actual implementation, and it is difficult to ensure the freshness of the architecture. Summary of the invention

[0017] This application provides an architecture as a service system and method based on the TOGAF standard to solve problems such as low hierarchical coverage rate of existing enterprise architecture implementation solutions, difficulty of modeling tools in adapting to complex enterprise environments, lack of unified information management, and low connection degree between enterprise architecture and actual implementation.

[0018] The first aspect of the embodiments of this application provides an architecture as a service system based on the TOGAF standard, including: an architecture as a service platform composed of a business architecture, a system architecture, and a technology architecture. Among them, based on the technology architecture, enterprise architecture data information entered by a user is received, and graphic data is assembled based on the enterprise architecture data information; based on the system architecture, view data is generated according to the graphic data and a graphic layout algorithm, and it is judged whether the generated view data is a process implementation diagram; based on the business architecture, when the generated view data is the process implementation diagram, the graphic layout algorithm is used for secondary planning to generate new view data, and the new view data is used by a graphic editor to generate an architecture view.

[0019] Optionally, the business architecture is used to determine the enterprise strategic goals, organizational structure, business functions, and business processes, and perform governance activities based on the enterprise strategic goals to generate value streams, capability maps, and business processes, and contribute driving forces, goals, initiatives, and business metrics; the system architecture includes an application architecture and a data architecture, the application architecture is used to input and output to generate the data architecture, and the technology architecture is used to support the implementation of the system architecture; based on the organizational structure, business functions, and business processes in the business architecture, and according to the data architecture, drive the application architecture to plan the functions of the application system; at the same time, based on the business processes in the business architecture, and according to the data storage and processing requirements in the data architecture and the characteristics of the application system in the application architecture, determine the technology selection of the technology architecture.

[0020] Optionally, the organizational structure is also used to create an infrastructure map according to the basic network infrastructure data of the enterprise; input the business process diagram, process implementation diagram, application interaction diagram, and technology architecture diagram based on the infrastructure map; create a motivation view, value stream view, capability map, technology, and product standards based on the business process diagram, the process implementation diagram, the application interaction diagram, and the technology architecture diagram.

[0021] Optionally, the application interaction diagram includes a function structure diagram, a data model diagram, and an application deployment diagram.

[0022] Optionally, the data architecture consists of multiple data objects.

[0023] Optionally, the technology architecture includes technology standards, product standards, system deployment architecture, and infrastructure architecture.

[0024] Optionally, the above-mentioned architecture-as-a-service system based on the TOGAF standard further includes: a project management platform for business interaction and project interaction with the architecture-as-a-service platform; an intelligent gateway for governing and analyzing the gateway configuration information and gateway monitoring information of the architecture-as-a-service platform; a monitoring platform for monitoring the operation and maintenance events of the project management platform.

[0025] Optionally, the project management platform includes: a requirements management module for sending business requirements to the architecture-as-a-service platform; a project management module for reviewing the project construction plan, project deployment plan, and basic software and hardware configuration according to the business requirements, and feeding back the deployment information to the architecture-as-a-service platform.

[0026] Optionally, the architecture-as-a-service platform is built based on the Open Group Architecture Framework TOGAF and the Archimate modeling language.

[0027] The second aspect of the present application provides an architecture-as-a-service method based on the TOGAF standard, including: receiving the enterprise architecture data information input by the user, and assembling it into graphic data based on the enterprise architecture data information; based on the graphic data, using a graphic layout algorithm to generate view data, and determining whether the generated view data is a process implementation diagram; if the generated view data is the process implementation diagram, using the graphic layout algorithm to perform secondary planning to generate new view data, and using a graphic editor to generate an architecture view from the new view data.

[0028] In the above implementation, based on the technical architecture, receive the enterprise architecture data information input by the user, and assemble it into graphic data based on the enterprise architecture data information. Based on the system architecture, generate view data according to the graphic data and the graphic layout algorithm, and determine whether the generated view data is a process implementation diagram. Based on the business architecture, when the generated view data is a process implementation diagram, use the graphic layout algorithm to perform secondary planning to generate new view data, and use a graphic editor to generate an architecture view from the new view data. Thus, the problems of low hierarchical coverage rate of the existing enterprise architecture implementation solutions, difficulty of the modeling tool in adapting to complex enterprise environments, lack of unified information management, and low degree of connection between enterprise architecture and implementation are solved. The enterprise architecture is transformed from fragmented graphics into an integrated model, effectively realizing digital architecture, constructing a panoramic view of the enterprise architecture, providing support for the entire life cycle of architecture management, realizing the deep integration of enterprise architecture governance and information project management processes, comprehensively sorting out the architecture of the existing system, and at the same time conducting architecture control over the newly added system to achieve continuous update and maintenance of the architecture, and finally realizing the digital innovation of the enterprise architecture.

[0029] Additional aspects and advantages of the present application will be given in part in the following description, become apparent in part from the following description, or be learned through the practice of the present application. Brief Description of the Drawings

[0030] The above and / or additional aspects and advantages of the present application will become apparent and be readily understood from the following description of the embodiments in conjunction with the drawings, where:

[0031] Figure 1 It is a schematic diagram of an architecture-as-a-service system based on the TOGAF standard according to an embodiment of the present application;

[0032] Figure 2 It is a schematic diagram of the automatic graphic planning implementation according to an embodiment of the present application;

[0033] Figure 3 It is a schematic diagram of the structure of the architecture-as-a-service platform according to an embodiment of the present application;

[0034] Figure 4Schematic diagram of an organizational structure according to an embodiment of the present application;

[0035] Figure 5 Interaction schematic diagram according to an embodiment of the present application;

[0036] Figure 6 Schematic diagram of an integrated project management platform according to an embodiment of the present application;

[0037] Figure 7 Example diagram of an architecture - as - a - service method based on the TOGAF standard according to an embodiment of the present application. Detailed implementation manners

[0038] The embodiments of the present application will be described in detail below. Examples of the embodiments are shown in the accompanying drawings, where the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described by referring to the accompanying drawings are exemplary and are intended to explain the present application, and should not be construed as a limitation to the present application.

[0039] The following describes the architecture - as - a - service system and method based on the TOGAF standard according to the embodiments of the present application. Aiming at the problems mentioned in the above - mentioned background technology, such as the low hierarchical coverage rate of the existing enterprise architecture implementation solutions, the difficulty of modeling tools to adapt to complex enterprise environments, the lack of unified information management, and the low degree of connection between enterprise architecture and implementation, the present application provides an architecture - as - a - service system based on the TOGAF standard. In this system, based on the technical architecture, it receives the enterprise architecture data information input by the user and assembles it into graphic data; based on the system architecture, it generates view data according to the graphic data and the graphic layout algorithm, and determines whether the generated view data is a process implementation diagram; based on the business architecture, when the generated view data is a process implementation diagram, it uses the graphic layout algorithm for secondary planning to generate new view data, and uses the graphic editor to generate an architecture view from the new view data. Thus, it solves the problems such as the low hierarchical coverage rate of the existing enterprise architecture implementation solutions, the difficulty of modeling tools to adapt to complex enterprise environments, the lack of unified information management, and the low degree of connection between enterprise architecture and implementation. It supports the top - level design of enterprise architecture with the international architecture standard TOGAF methodology and Archimate modeling language. The enterprise architecture is model - driven, and the element relationship path is automatically planned through the graphic layout algorithm. The graphics that originally needed to be painstakingly hand - drawn can automatically plan the path and dynamically generate views according to the data input by the user in this system. The average time for technical managers to update and submit system architecture artifacts (including business, function, application, deployment, etc.) has been shortened from the original 5 days to 1.5 days, and the one - time passing rate of architecture artifacts exceeds 90%; architecture consistency guarantee: when a certain architecture element changes, the references to this element in different systems and different architecture views will be automatically updated, so the consistency of the architecture views can be automatically maintained; the architecture - as - a - service platform is not only an architecture modeling tool, but also empowers technology governance. It provides standardized APIs to achieve deep integration with the IT tool ecosystem and management processes, maximizing the technical value of architecture assets. The control and governance of the technical architecture strengthen the foundation of configuration management, realize full - process digitization, and the system service monitoring achieves deep visualization.

[0040] Specifically, Figure 1 It is a block diagram of an architecture - as - a - service system based on the TOGAF standard provided by the embodiments of the present application.

[0041] As Figure 1 shown, the architecture - as - a - service system 10 based on the TOGAF standard includes an architecture - as - a - service platform composed of a business architecture 100, a system architecture 200, and a technical architecture 300, where,

[0042] Based on the technology architecture 300, receive the enterprise architecture data information input by the user, store the enterprise architecture data information, and assemble it into graphic data; based on the system architecture 200, generate view data according to the graphic data and the graphic layout algorithm, and determine whether the generated view data is a process implementation diagram; based on the business architecture 100, when the generated view data is a process implementation diagram, use the graphic layout algorithm for secondary planning to generate new view data, and use the graphic editor to generate an architecture view from the new view data.

[0043] Specifically, as Figure 2 shown, the technology architecture 300 is used to receive the enterprise architecture data information input by the user and assemble it into graphic data based on the enterprise architecture data information. The system architecture 200 is used to generate view data based on the graphic data using the graphic layout algorithm and determine whether the generated view data is a process implementation diagram. The business architecture 100 is used to, if the generated view data is a process implementation diagram, use the graphic layout algorithm for secondary planning to generate new view data, and use the graphic editor to generate an architecture view from the new view data.

[0044] Optionally, in some embodiments, the business architecture 100 is used to determine the enterprise strategic goals, organizational structure, business functions, and business processes, and perform governance activities based on the enterprise strategic goals to generate value streams, capability maps, and business processes, and contribute drivers, goals, initiatives, and business metrics; the system architecture 200 includes an application architecture and a data architecture, the application architecture is used to input and output to generate the data architecture, and the technology architecture 300 is used to support the implementation of the system architecture 200; based on the organizational structure, business functions, and business processes in the business architecture 100, and according to the data architecture, drive the application architecture to plan the functions of the application system; at the same time, based on the business processes in the business architecture 100, and according to the data storage and processing requirements in the data architecture and the characteristics of the application system in the application architecture, determine the technology selection of the technology architecture 300.

[0045] Optionally, in some embodiments, the organizational structure is further used to create an infrastructure diagram according to the enterprise's basic network infrastructure data; input a business process diagram, a process implementation diagram, an application interaction diagram, and a technology architecture diagram based on the infrastructure diagram; create a motivation view, a value stream view, a capability map, and technology and product standards based on the business process diagram, the process implementation diagram, the application interaction diagram, and the technology architecture diagram.

[0046] Optionally, in some embodiments, the application interaction diagram includes a function structure diagram, a data model diagram, and an application deployment diagram.

[0047] Optionally, in some embodiments, the data architecture consists of multiple data objects.

[0048] Optionally, in some embodiments, the technology architecture 300 includes technology standards, product standards, system deployment architecture, and infrastructure architecture.

[0049] Optionally, in some embodiments, the above-mentioned architecture-as-a-service system 10 based on the TOGAF standard further includes: a project management platform for business interaction and project interaction with the architecture-as-a-service platform; an intelligent gateway for governing and analyzing the gateway configuration information and gateway monitoring information of the architecture-as-a-service platform; and a monitoring platform for monitoring the operation and maintenance events of the project management platform.

[0050] Optionally, in some embodiments, the project management platform includes: a requirements management module for sending business requirements to the architecture-as-a-service platform; and a project management module for reviewing the project construction plan, project deployment plan, and basic software and hardware configuration according to the business requirements, and feeding back the deployment information to the architecture-as-a-service platform.

[0051] Optionally, in some embodiments, the architecture-as-a-service platform is built based on the Open Group Architecture Framework (TOGAF) and the Archimate modeling language.

[0052] Specifically, the embodiments of the present application are based on the TOGAF methodology and the Archimate modeling language. From the enterprise architecture to the solution architecture, different stakeholders can collaborate on the platform, and the architecture views at different levels and from different perspectives that they are concerned about can be modeled, queried, updated, traced, and visualized on the architecture-as-a-service platform, as Figure 3 shown.

[0053] The business architecture 100 has three support layers: the decision-making layer, the management layer, and the execution layer. The three support layers perform governance activities based on the enterprise strategic goals, generate value streams, capability maps, and business processes, and contribute driving forces, goals, initiatives, and business metrics.

[0054] The business architecture 100 needs to be supported and implemented by the system architecture 200. The system architecture 200 is divided into an application architecture and a data architecture. The application architecture consists of a top-level architecture, applications, and services. The application architecture inputs and outputs to generate the data architecture, and the data architecture consists of data objects. The system architecture 200 needs to be supported and implemented by the technology architecture 300. The technology architecture 300 is divided into technology standards, product standards, system deployment architecture, and infrastructure architecture.

[0055] The business architecture 100 defines key elements such as the enterprise's strategic goals, business processes, organizational structure, and business functions. These business requirements drive the design of the data architecture. The business function and business process requirements in the business architecture 100, combined with the data requirements in the data architecture, jointly drive the application architecture to plan the functions of application systems. The business requirements (such as performance requirements, availability requirements, etc.) in the business architecture 100, the data storage and processing requirements (such as data volume, data read / write frequency, etc.) in the data architecture, and the application system characteristics (such as the concurrent processing ability of the application, response time requirements, etc.) in the application architecture jointly guide the technology architecture 300 in technology selection.

[0056] The architecture-as-a-service platform supports the online construction of model-driven enterprise architectures in the standard enterprise architecture modeling language Archimate, including 16 artifacts and 3 catalog lists for the business architecture 100, application architecture, data architecture, and technology architecture 300.

[0057] Among them, the 16 artifacts include business architecture, capability map, value stream, organization chart, business process diagram, process implementation diagram, motivation view, application architecture, system topology diagram, application interaction diagram, service interaction diagram, application implementation diagram, functional structure diagram, deployment diagram, infrastructure diagram, data architecture (transactional), conceptual data model, data flow view, technology architecture, and technology architecture view; the 3 catalog lists include application list, service list, and application interaction list.

[0058] Enterprise architects use the platform to create motivation views, value stream views, capability maps, technology, and product standards. Solution architects enter the business process diagrams, process implementation diagrams, application interaction diagrams, functional structure diagrams, data model diagrams, and application deployment diagrams of the system. Infrastructure architects use the platform to create infrastructure diagrams, as specifically Figure 4 shown.

[0059] All the graphics in the embodiments of this application are data-driven. When using this system, architects only need to create system nodes and architecture elements under the planned directory structure according to the system catalog. The system will automatically draw architecture views according to the graphic layering algorithm. Different from traditional enterprise architecture solutions that draw graphic elements, each architecture view is dynamically generated, and the interaction information between systems is also dynamically maintained and generated. When the interaction information between systems changes, only the interaction information data needs to be modified, and the graphics will automatically change and be displayed. The interaction diagram is as Figure 5 shown.

[0060] Traditional deployment diagrams are all drawn by solution architects and infrastructure architects using visio drawing tools based on the company's infrastructure. When the basic network changes or the deployment changes, it is necessary to find the original diagram and modify it using local tools. Especially when the infrastructure changes, a large number of application system deployment diagrams need to be modified. The deployment diagrams of this solution are automatically generated based on the basic network infrastructure data and deployment data. First, the infrastructure architect enters the basic network infrastructure data of the company to generate the basic network infrastructure deployment diagram. The solution architect enters the system deployment data, and the deployment diagram will be automatically generated according to the data. In this way, the data is maintained separately and the diagram is automatically generated, reducing the maintenance cost of the deployment diagram.

[0061] For enterprises with complex business processes and intricate application architectures, the process implementation diagram is one of the most useful architecture views, revealing which underlying application services support the business processes. Due to the complexity of this view, it is often difficult to clearly draw and display in general software, while on the platform, operations such as design, update, query, zoom, perspective, and link jump can be conveniently performed. This view is also where the architecture as a service platform creates an implementation relationship based on the existing business architecture 100 data and application architecture data to complete the automatic drawing of the process implementation diagram, dynamically displaying the enterprise's system architecture 200 information.

[0062] For the enterprise architecture, the architecture as a service platform cannot be an information island. By integrating with the project management platform and embedding it into the project process of the information management platform, full-process architecture control is carried out from project requirements, project establishment, to implementation, deployment, go-live, and acceptance. The project management platform integrated by the project management platform, architecture as a service platform, intelligent gateway, and monitoring platform is as Figure 6 shown.

[0063] It can be understood that the requirements management module sends business requirements to the architecture as a service platform. The project management module conducts reviews on the project construction plan, project deployment plan, and basic software and hardware configuration according to the business requirements, and feeds back the deployment information to the architecture as a service platform. The specific steps are as follows:

[0064] 1. When the business architect conducts requirements analysis, use the architecture as a service platform to create a business process diagram.

[0065] 2. When the system architect conducts system solution design, use the architecture as a service platform to create system interaction diagrams, function structure diagrams, application deployment diagrams, and data model diagrams.

[0066] 3. When creating a project in the project management platform and conducting a project plan review, submit the outputs of the architecture as a service platform for architecture review.

[0067] 4. When creating a deployment plan in the project management platform, submit the deployment diagram of the architecture as a service platform for review.

[0068] 5. When configuring the software and hardware on the project management platform, submit the service catalog of the Architecture as a Service platform.

[0069] 6. After the deployment is completed, the deployment information is fed back on the project management platform and synchronized to the architecture as a service platform.

[0070] 7. The Infrastructure as a Service platform integrates intelligent gateways to manage and analyze the gateway configuration information and gateway monitoring information of the Infrastructure as a Service platform.

[0071] 8. The architecture-as-a-service platform integrates the monitoring platform to conduct key analysis of operation and maintenance events, conduct link monitoring of important operation and maintenance events of the project management system, and assist in architecture sorting.

[0072] In summary, the embodiments of the present application can complete the architecture combing and modeling of the business process diagrams, interaction diagrams, process implementation diagrams, functional structure diagrams, deployment diagrams, and service catalogs of all enterprise systems, and can complete the construction of the enterprise's top-level strategic goals, motivation views, value streams, and capability maps. For new systems, by embedding the platform into the information project management platform process, the incremental system construction plan, requirement specification review, deployment plan approval, and online plan approval processes are associated with the system architecture view, and the system architecture is managed and controlled during the project. After using this solution, the system architecture product delivery time, architecture asset update frequency, and architecture review pass rate are greatly improved.

[0073] Therefore, the embodiments of the present application effectively solve the following key problems:

[0074] (1) Unified architecture modeling standards

[0075] Based on TOGAF methodology and Archimate modeling language, and combined with the company's specific needs, a set of unified architecture modeling standards has been developed. The architecture design of this application adopts a model-driven approach rather than a traditional graphic-driven approach, which transforms the enterprise architecture from a segmented graphic into an integrated model, effectively realizing digital architecture. Through the model-driven approach, any changes to the architecture elements can be automatically reflected in all related views, eliminating the difficulty of maintaining different views when drawing traditional architecture diagrams. Figure 1 The problem of consistency.

[0076] (2) Construction of digital platform

[0077] By building a model-driven digital architecture management platform, we can manage enterprise architecture assets in a unified manner. Through the establishment of the architecture-as-a-service platform and the comprehensive review of the enterprise architecture, we have successfully built a panoramic view of the enterprise architecture and provided support for the full cycle of architecture management.

[0078] (3) IT operation process reengineering

[0079] Collaborate with other IT tool systems, build a core system around architecture assets, and achieve deep integration of enterprise architecture governance and informatization project management processes. The platform supports various IT aspects in the form of URL links or standard API services, making it the intelligent core and driving force of digital IT management, ensuring the compliance of each system architecture, and effectively embedding into the entire life cycle process of informatization project management.

[0080] (4) Architecture sorting and governance

[0081] Based on the new platform, a comprehensive architecture sorting of existing systems is carried out, and at the same time, architecture control is carried out on newly added systems to achieve continuous update and maintenance of the architecture, and ultimately realize the digital innovation of the enterprise architecture.

[0082] The architecture as a service system based on the TOGAF standard proposed according to the embodiments of the present application receives the enterprise architecture data information input by users based on the technical architecture, and assembles it into graphic data; based on the system architecture, generates view data according to the graphic data and graphic layout algorithm, and determines whether the generated view data is a process implementation diagram; based on the business architecture, when the generated view data is a process implementation diagram, uses the graphic layout algorithm for secondary planning to generate new view data, and generates an architecture view with the new view data using a graphic editor. Thus, the problems of low hierarchical coverage rate of existing enterprise architecture implementation solutions, difficulty of modeling tools in adapting to complex enterprise environments, lack of unified information management, and low connection degree between enterprise architecture and implementation are solved, enabling the enterprise architecture to transform from fragmented graphics into an integrated model, effectively realizing digital architecture, constructing a panoramic view of the enterprise architecture, providing support for the entire life cycle of architecture management, achieving deep integration of enterprise architecture governance and informatization project management processes, carrying out a comprehensive architecture sorting of existing systems, and at the same time, carrying out architecture control on newly added systems to achieve continuous update and maintenance of the architecture, and ultimately realizing the digital innovation of the enterprise architecture.

[0083] Secondly, the architecture as a service method based on the TOGAF standard proposed according to the embodiments of the present application is described with reference to the accompanying drawings.

[0084] Figure 7 It is a schematic diagram of the architecture as a service method based on the TOGAF standard of the embodiments of the present application.

[0085] As Figure 7 shown, the architecture as a service method based on the TOGAF standard includes:

[0086] In step S701, the enterprise architecture data information entered by the user is received and assembled into graphic data based on the enterprise architecture data information.

[0087] In step S702, based on the graphic data, view data is generated using a graphic layout algorithm, and it is determined whether the generated view data is a process implementation diagram.

[0088] In step S703, if the generated view data is a process implementation diagram, then a secondary planning is performed using the graphic layout algorithm to generate new view data, and the new view data is used by a graphic editor to generate an architecture view.

[0089] It should be noted that the foregoing explanation of the architecture-as-a-service system embodiment based on the TOGAF standard also applies to the architecture-as-a-service method based on the TOGAF standard of this embodiment, and will not be elaborated here.

[0090] According to the architecture-as-a-service method based on the TOGAF standard proposed in the embodiments of the present application, the enterprise architecture data information entered by the user is received, assembled into graphic data based on the enterprise architecture data information, view data is generated using a graphic layout algorithm based on the graphic data, and it is determined whether the generated view data is a process implementation diagram. If the generated view data is a process implementation diagram, then a secondary planning is performed using the graphic layout algorithm to generate new view data, and the new view data is used by a graphic editor to generate an architecture view.

[0091] In the description of this specification, the descriptions with reference to terms such as "one embodiment", "some embodiments", "example", "specific example", or "some examples" mean that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in any one or N embodiments or examples in a suitable manner. In addition, without contradiction, those skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0092] In addition, the terms "first" and "second" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first" and "second" can explicitly or implicitly include at least one of the features. In the description of the present application, the meaning of "N" is at least two, such as two, three, etc., unless otherwise specifically defined.

[0093] Any process or method description represented in a flowchart or otherwise described herein can be understood to represent a module, segment, or portion of code including one or more executable instructions for implementing a customized logical function or process. The scope of the preferred embodiments of the present application includes additional implementations where functions may be executed not in the order shown or discussed, including in a substantially simultaneous manner according to the functions involved or in a reverse order, which should be understood by those skilled in the art to which the embodiments of the present application pertain.

[0094] Logic and / or steps represented in a flowchart or otherwise described herein, for example, can be considered a sequenced list of executable instructions for implementing a logical function and can be embodied in any computer program product for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, a system including a processor, or other systems that can fetch and execute instructions from the instruction execution system, apparatus, or device. For the purposes of this specification, a "computer program product" can be any device that can contain, store, communicate, propagate, or transport a program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer program product include the following: an electrical connection unit (electronic device) having one or more wirings, a portable computer diskette (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer program product can even be paper or other suitable medium on which the program can be printed, as the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpretation, or otherwise appropriate processing as necessary, and then stored in a computer memory.

[0095] It should be understood that various parts of the present application can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, the N steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or a combination of the following techniques known in the art can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays (PGAs), field programmable gate arrays (FPGAs), etc.

[0096] Those of ordinary skill in the art can understand that all or part of the steps carried out in implementing the above-described embodiment methods can be completed by instructing relevant hardware through a program, and the program can be stored in a computer program product. When the program is executed, it includes one or a combination of the steps of the method embodiment.

[0097] In addition, each functional unit in various embodiments of the present application can be integrated in a processing module, can exist physically alone for each unit, or two or more units can be integrated in a module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of a software functional module. When the above-mentioned integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer program product.

[0098] The above-mentioned computer program product can be a read-only memory, a magnetic disk, an optical disc, etc. Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present application. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present application.

Claims

1. An architecture as a service system based on the TOGAF standard, characterized in that: include: The architecture-as-a-service platform consists of business architecture, system architecture and technical architecture, among which: Based on the technical architecture, receiving enterprise architecture data information entered by a user, and assembling into graphic data based on the enterprise architecture data information; Based on the system architecture, generating view data according to the graphic data and the graphic layout algorithm, and determining whether the generated view data is a process implementation diagram; Based on the business architecture, when the generated view data is the process implementation diagram, the graphic layout algorithm is used to perform secondary planning to generate new view data, and the new view data is used to generate an architecture view using a graphic editor.

2. The TOGAF-based architecture as a service system according to claim 1, characterized in that: The business architecture is used to determine the enterprise's strategic goals, organizational structure, business functions and business processes, and to perform governance activities based on the enterprise's strategic goals, generate value streams, capability maps and business processes, and contribute drivers, goals, initiatives and business indicators; The system architecture includes an application architecture and a data architecture, wherein the application architecture is used to input and output the data architecture, and the technical architecture is used to support the implementation of the system architecture; Based on the organizational structure, business functions and business processes in the business architecture, and according to the data architecture, the application architecture plans the application system functions; at the same time, based on the business processes in the business architecture, and according to the data storage and processing requirements in the data architecture and the application system characteristics in the application architecture, the technology selection of the technical architecture is determined.

3. The TOGAF-based architecture as a service system according to claim 2, characterized in that: The organizational structure is also used to: Creating an infrastructure map based on the enterprise's network infrastructure data; Entering business process diagrams, process implementation diagrams, application interaction diagrams, and technical architecture diagrams based on the infrastructure diagram; A motivation view, a value stream view, a capability map, technology and product standards are created based on the business process diagram, the process implementation diagram, the application interaction diagram and the technical architecture diagram.

4. The TOGAF-based architecture as a service system according to claim 3, characterized in that: The application interaction diagram includes a functional structure diagram, a data model diagram and an application deployment diagram.

5. The TOGAF-based architecture as a service system according to claim 1, characterized in that: The data architecture consists of multiple data objects.

6. The TOGAF-based architecture as a service system according to claim 1, characterized in that: The technical architecture includes technical standards, product standards, system deployment architecture and infrastructure architecture.

7. The TOGAF-based architecture as a service system according to claim 1, characterized in that: Also includes: A project management platform, used for business interaction and project interaction with the architecture as a service platform; An intelligent gateway, used to manage and analyze gateway configuration information and gateway monitoring information of the architecture as a service platform; A monitoring platform is used to monitor the operation and maintenance events of the project management platform.

8. The TOGAF-based architecture as a service system according to claim 7, characterized in that: The project management platform includes: A demand management module, used for sending business requirements to the architecture as a service platform; The project management module is used to review the project construction plan, project deployment plan, and basic software and hardware configuration according to the business needs, and feed back the deployment information to the architecture as a service platform.

9. The TOGAF-based architecture as a service system according to claim 1, characterized in that: The architecture-as-a-service platform is constructed based on the Open Group Architecture Framework TOGAF and the Archimate modeling language.

10. An architecture as a service method based on the TOGAF standard, characterized in that: Using the TOGAF standard-based architecture as a service system as described in any one of claims 1 to 9, the method includes: Receiving enterprise architecture data information entered by a user, and assembling into graphic data based on the enterprise architecture data information; Based on the graphic data, generating view data using a graphic layout algorithm, and determining whether the generated view data is a process implementation diagram; If the generated view data is the process implementation diagram, the graph layout algorithm is used to perform secondary programming to generate new view data, and the new view data is used to generate an architecture view using a graph editor.

Images