Structured management method for sensitive service architecture system
Through the five-layer structured standard model and automated acquisition method, the management of sensitive business system architecture is solved, and the management efficiency and consistency problems are achieved, and the full life cycle management and performance improvement is achieved.
Patent Information
- Application Number
- CN202411033599.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-30
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2044-07-30
AI Technical Summary
The sensitive business system architecture lacks structured management, ledger records, visual management and design and operational consistency management in the management process, resulting in low management efficiency, insufficient stability and security.
A five-layer structured standard model is adopted, and configuration items are managed in combination with automation and manual collection methods, and ledger record standards and visual verification standards are formulated, and a comparison mechanism between design and operating conditions is established to ensure the consistency of the architecture.
It realizes the full life cycle management of the sensitive business system architecture, meets the needs of different roles, and improves the stability, security and performance of the system.
Smart Images

Figure CN119025074A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of software technology, and in particular to a structured management method for an agile business architecture system. Background Art
[0002] Financial enterprises generally have steady-state businesses based on traditional technology stacks and agile businesses based on microservice technology. Rapidly increasing business needs are basically for agile businesses. During the construction of the architecture management of agile business systems, there are the following problems:
[0003] First, there is a lack of structured management capabilities for agile business system architecture. Currently, there are large differences in the management of agile business system architecture among various enterprises, and there is no relatively unified standard. Some enterprises divide the agile system architecture based on domain models, but the granularity of the division and the element information vary greatly; some enterprises manage the agile system architecture based on the management ideas of the stable business system architecture, resulting in the inability to reflect the characteristics and advantages of the agile business system architecture.
[0004] Second, there is a lack of record-keeping capabilities for agile business system architectures. Currently, there are several problems with the record-keeping of agile business system architectures in enterprises: (1) Agile system architectures are rarely managed and recorded according to the design state and the operation state; (2) There is a lack of structured recording methods for the management and recording of agile system architectures, and most of them are recorded in documents; (3) There is a lack of effective management of the versions of agile system architectures, and changes in the versions of system architectures cannot be tracked well.
[0005] The third is the lack of visualization capabilities for agile business system architectures. According to the survey, due to management and technical reasons, few companies have implemented visualization of agile business system architectures. However, architecture visualization is very important for architects, developers, security personnel, and operation and maintenance personnel, such as architecture evolution, change correlation impact analysis, and security attack event location.
[0006] Fourth, there is a lack of a comparison mechanism between the design state and the running state of the agile business system architecture. In actual production, due to lack of management, the running state architecture of a business system often undergoes significant changes from the initial design state after multiple changes, but the design state architecture is not updated synchronously or for some reasons, the actual online architecture of some business systems is indeed different from the design state architecture. If these differences between the design state and the running state are not discovered and adjusted in a timely manner, it will bring hidden dangers to the business system. For example, a business system that was initially positioned at a lower level, with the iteration of changes, changes to a system that has a greater impact on production business. If this situation cannot be identified quickly and accurately, the supporting resource guarantee cannot keep up, which is likely to cause production accidents. Summary of the invention
[0007] In view of the above technical problems, the present invention provides a structured management method for an agile business architecture system, which aims to solve the problems of lack of structured management of the agile business system architecture, lack of ledger records of the agile business system architecture, lack of visual management of the agile business system architecture, and lack of consistency management of the design state and operation state of the agile business system architecture in the current management process of the agile business system architecture, and realizes the structured management, ledger records, visual verification and architecture consistency management of the agile business system architecture.
[0008] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by the practice of the present disclosure.
[0009] According to one aspect of the present invention, a method for structured management of an agile business architecture system is disclosed, the method comprising:
[0010] According to the determined hierarchical type of the business architecture system, a design state architecture is formed, wherein the design state architecture includes demand finalization, architecture design, software design, development, and testing, wherein the architecture design includes domain division, component division, interface definition, and data flow design, and the business architecture system formed based on the design state architecture is deployed and maintained to form an operation state architecture;
[0011] When designing the design state architecture, a structured standard model is designed. The standard model adopts a five-layer structure, which includes system, subsystem, application, service, computing node in order, and defines the configuration items of each layer. When planning the standard model, its model instance, access logic architecture, computing node information, and the creation, modification and deletion process of the model instance are planned;
[0012] When the running state architecture is executed, an automated collection method is used in combination with a manual collection method to manage the configuration items involved in the service and computing nodes;
[0013] Formulate the ledger record standards for the design state architecture and the running state architecture, including formulating the principles and management specifications to be followed for ledger record, wherein the management specifications include the ledger templates and version management requirements for the design state architecture and the running state architecture;
[0014] Establish visual verification standards for the system architecture, including setting the visualization target object, determining the data acquisition path, designing visualization elements, setting visualization target object element information, selecting visualization tools, realizing dynamic and interactive display, and using the design state architecture version as the baseline version and the running state architecture version as the running version, and formulating a timed comparison mechanism between the baseline version and the running version. If the comparison finds that the version information is inconsistent, generate a version difference work order and execute processing.
[0015] Furthermore, when constructing and managing the design state, the following operations are performed:
[0016] Requirements analysis, where the requirements analyzed include one or more of business requirements, user requirements, system requirements definition, functional requirements, non-functional requirements, security requirements, technical requirements, data requirements, integration requirements, testability requirements, change management requirements, priorities, and dependencies;
[0017] Architectural design, including: the relationships between systems, subsystems, and applications;
[0018] Interface definition, including: defining the interaction interface between different components or services;
[0019] Technology selection, including: choosing the corresponding technology stack and tools for development.
[0020] Furthermore, when constructing and managing the running state, the following operations are performed:
[0021] Deployment environment, deploying the designed software components into the production environment. The operational architecture includes the access architecture and the deployment architecture. The access architecture represents the access relationship between components within the business system, and the deployment architecture represents how the business system architecture is deployed in the environment.
[0022] Configuration parameters: configure system parameters according to the needs of the operating environment;
[0023] Monitoring and optimization: Based on visual monitoring of the operating status of business systems, performance optimization and troubleshooting are carried out.
[0024] Furthermore, the configuration items of the system include: system name, system code, service catalog and SLA, system person in charge, system importance level, system business positioning, system scope and boundaries, business system architecture requirements, service life cycle, information security requirements, business continuity, resource management, and security level; the configuration items of the subsystem include: subsystem name, subsystem code, system person in charge, system importance level, subsystem function and SLA, information security requirements, performance baseline, monitoring baseline, service window, maintenance strategy and window, user and authority management, testing strategy, and change management requirements; the configuration items of the application include the name of the application, the code of the application, the person in charge of the application, application function and service description, application environment configuration, application security strategy, application performance indicators, application monitoring indicators, fault handling strategy, application release method, application version, and application technology stack; the configuration items of the service include: service name, person in charge, IP, port, service interface, calling service, and called service; the configuration items of the computing node include: node name, IP, person in charge, operating system, configuration, environment, type, and service process.
[0025] Furthermore, in the standard model, the system, the subsystem, the application, the service and the computing node have the following association relationship:
[0026] The system includes several subsystems, the subsystems include several applications, the applications include several services, and the services include several computing nodes;
[0027] One subsystem can only belong to one system, and one application belongs to one subsystem;
[0028] The SLA of the system affects the SLA of the subsystem;
[0029] The importance level of the system affects the importance level of the subsystem;
[0030] The system's architectural design principles affect the subsystem's demand access principles, technology stack usage principles, data call principles, and permission control principles;
[0031] The information security requirements of the system affect the security requirements and controls of the subsystems;
[0032] The business continuity plan of the system affects the service windows, maintenance strategies and windows, and quality assurance and testing of the subsystems described;
[0033] The change management requirements of the subsystem affect the release mode of the application, application version management and version release history;
[0034] The performance baseline of the subsystem affects the performance indicators of the application;
[0035] The monitoring baseline of the subsystem affects the monitoring indicators of the application.
[0036] Furthermore, the specific planning process of the design state architecture diagram includes:
[0037] In combination with the positioning of the business system, planning is performed from five levels: the system, the subsystem, the application, the service, and the computing node;
[0038] In the planning process of the five levels, for the models at the five levels, determine the new model instances that need to be created and the existing model instances that need to be reused;
[0039] After determining the model instance, the required computing node information is calculated, and the computing node information includes the type, configuration and quantity of the computing nodes;
[0040] The access logic is planned, and the access logic includes network partitions, request access links, and data links. The access logic can be represented in the computing node information to form the design state architecture diagram.
[0041] Furthermore, the configuration items involved in the running state in the management service and computing node, the automatic collection method and the manual collection method adopted include:
[0042] By obtaining network link information from the operating system, the access relationship between computing nodes is calculated. At the same time, the relationship between computing nodes and services in the CMDB is combined to calculate the calling relationship between services, and then the calling relationship between applications, between subsystems, and between systems is calculated.
[0043] By obtaining the call information between interfaces from APM and combining it with the relationship between interfaces and applications in CMDB, the call relationship between interfaces between applications can be calculated. At the same time, based on the characteristics of APM, the running path of each business request in the system architecture can be calculated.
[0044] The call relationship between the application and the database or storage service is calculated by combining the link relationship between the computing node and the database or storage service collected in the OS with the relationship between the computing node and the service in the CMDB.
[0045] Through the service query interface provided by the message middleware and the association between the middleware, applications and consumers recorded in the CMDB, the access relationship between applications interacting through the message middleware is calculated;
[0046] The file mount point service information collected in the OS is combined with the relationship between computing nodes and applications in the CMDB to calculate the access relationship between several applications that interact through the file mount service.
[0047] By connecting to the data service platform or component, the computing nodes that interact with data through the data service are obtained, and the applications that interact through the data service platform are calculated based on the relationship between the computing nodes and applications recorded in the CMDB.
[0048] By connecting to the CDC data synchronization tool, we can obtain which databases have data synchronization tasks, and combine the relationship between databases and applications recorded in the CMDB to calculate the access relationship between applications based on database data synchronization tasks.
[0049] Furthermore, the principles followed by the ledger records include:
[0050] Clarify the objects and scope of the records. The objects of the records include relevant instances of systems, subsystems, applications, services, and computing nodes. The scope of the records includes the configuration items and their associations of the systems, subsystems, applications, services, and computing nodes:
[0051] Standardize the record content and format. The configuration items that need to be recorded in the system, subsystem, application, service and computing node should be entered in the preset format, and the relationship between related instances should be associated.
[0052] Standardize the recording process, and provide supporting process support when recording the creation, modification, and deletion of systems, subsystems, applications, services, and computing node instances in the ledger;
[0053] The unified standardization of ledger carriers requires the establishment of a unified electronic tool for ledger records;
[0054] To facilitate query and analysis, multiple methods of querying and analyzing records in the ledger need to be provided;
[0055] Security and confidentiality: The access, recording, and modification of the ledger are accompanied by corresponding security measures, which include at least one of role authority division, secondary access authentication, and data encryption storage.
[0056] Furthermore, the indicator items of the ledger template in the design state include:
[0057] Initial version information, system, subsystem, application, service, computing node, version number, release date, requirement ID, developer, functional description, compatibility information, performance indicators, technology stack information, system architecture topology, physical architecture topology, deployment guide, rollback plan, monitoring and maintenance, test and verification results, and other instructions;
[0058] The version management requirements of the ledger template in the design state include the following settings:
[0059] Initialize version specifications, define version control system, set version change process, standardize architecture topology, version change tracking mechanism, backup and archive.
[0060] Furthermore, the indicator items of the account template in the running state include:
[0061] Associated design state version number, system, subsystem, application, service, computing node, version number, latest update time, system architecture topology, physical architecture topology;
[0062] The version management requirements for the running state include:
[0063] Implement a role-based access control model to control the configuration permissions and data collection permissions of automated collection tools, ensuring that only authorized users can operate and maintain the tools;
[0064] After the application version is released, the relevant service instance and computing node information is automatically collected and compared with the design state architecture;
[0065] Regularly collect service instances and computing nodes of business systems through scheduled tasks to obtain the latest runtime configuration information;
[0066] Properly configure tools that continuously collect runtime information and monitor their operating status to ensure that the tools are functioning properly;
[0067] Analyze and adjust automated collection methods that affect business system stability and performance;
[0068] A running state architecture version change process is established in the process management system. When the design state architecture is inconsistent with the running state architecture, the design state architecture is used as the basis for version change and update.
[0069] The technical solution disclosed in this disclosure has the following beneficial effects:
[0070] Through this method, the entire life cycle of the agile business system architecture is managed. On the one hand, the different demands of different roles for the management of the agile business system architecture are met, such as root cause analysis, architecture evolution, and correlation impact analysis. On the other hand, by managing the consistency between the design state and the operating state of the agile business system architecture, the handle for managing the business system is increased, which helps to improve the stability, security, and performance of the agile business system. BRIEF DESCRIPTION OF THE DRAWINGS
[0071] Figure 1 It is a flowchart of a structured management method of an agile business architecture system in an embodiment of this specification;
[0072] Figure 2It is a framework diagram of the design state and the operation state in the embodiments of this specification;
[0073] Figure 3 It is a correlation diagram of the five-layer model in the embodiment of this specification;
[0074] Figure 4 Create a flow chart for the examples in the embodiments of this specification;
[0075] Figure 5 This is a flowchart of example changes in the embodiments of this specification;
[0076] Figure 6 The flowchart is deleted for the example in the embodiments of this specification;
[0077] Figure 7 A flowchart of the design state architecture version change in the embodiment of this specification;
[0078] Figure 8 This is a flowchart of the running state architecture version change in the embodiment of this specification;
[0079] Fig. 9 This is a flowchart of processing when there are version differences in the embodiments of this specification. DETAILED DESCRIPTION
[0080] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as being limited to the examples set forth herein; on the contrary, these embodiments are provided so that the present disclosure will be more comprehensive and complete, and the concepts of the example embodiments are fully conveyed to those skilled in the art. The described features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure may be practiced while omitting one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other cases, known technical solutions are not shown or described in detail to avoid obscuring various aspects of the present disclosure.
[0081] In addition, the accompanying drawings are only schematic illustrations of the present disclosure. The same reference numerals in the figures represent the same or similar parts, and thus their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities, which do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.
[0082] like Figure 1 As shown, the embodiment of this specification provides a method for structured management of an agile business architecture system. The method may specifically include the following steps S101 to S107:
[0083] In step S101, a design state architecture is formed according to the determined hierarchical type of the business architecture system. The design state architecture includes demand finalization, architecture design, software design, development, and testing. The architecture design includes domain division, component division, interface definition, and data flow design. The business architecture system formed based on the design state architecture is deployed and operated to form an operating state architecture.
[0084] Among them, Figure 2 As shown in the figure, the structured management specification of agile business system architecture aims to establish a standard system to better describe the digital architecture of an agile business system. The overall framework must be centered on the architecture lifecycle perspective, with project establishment, architecture design, development, and testing as the content of the design phase, and deployment and operation and maintenance as the content of the operation phase, so that it has the following principles:
[0085] Achieve full life cycle management: Based on the full life cycle process, starting from product business needs, the design state architecture is delivered to the production environment, thereby building the operation state architecture;
[0086] Build views for different roles: Build architectural features from the perspectives of business personnel, architects, developers, testers, and operation and maintenance personnel;
[0087] Matching the model with the IT architecture: Look at the relationship between resources and services from the perspective of the business system to generate application architecture, deployment architecture, operation architecture, etc.
[0088] In step S102, when designing the design state architecture, a structured standard model is designed. The standard model adopts a five-layer structure, which includes system, subsystem, application, service, and computing node in order, and defines the configuration items of each layer. When planning the standard model, its model instance, access logic architecture, computing node information, and creation, modification and deletion processes of the model instance are planned.
[0089] Among them, the design state architecture refers to the design and planning of the structure and components of the software system by architects and development teams during the software development process. The architecture at this stage focuses on the overall design of the system architecture, including the division of domains, the division of components, the definition of interfaces, the design of data flows, etc. The design state architecture needs to complete the definition of metadata models such as systems, subsystems, and applications (service units), and clarify the architecture type, architecture hierarchy, and the logical relationship between services. The key activities included in the design state architecture are: demand analysis, the analyzed requirements include one or more of business requirements, user requirements, system requirements definition, functional requirements, non-functional requirements, security requirements, technical requirements, data requirements, integration requirements, testability requirements, change management requirements, priorities, and dependencies; architecture design, including: the relationship between systems, subsystems, and applications; interface definition, including: defining the interaction interface between different components or services; technology selection, including: selecting the corresponding technology stack and tools for development.
[0090] The operational architecture refers to the deployment and operation of a system, which requires the preparation of deployment resources, cluster environment, and architecture visualization. The operational architecture can also play a role in some operation and maintenance scenarios, such as emergency switching, fault location, health status check, capacity expansion / reduction, capacity forecasting, etc.; the key activities it includes are: Deployment: deploying the designed software components to the production environment. The operational architecture includes access architecture and deployment architecture. The access architecture expresses the access relationship between the components within an agile business system; the deployment architecture indicates how the agile business system architecture is deployed in the environment; configuration: configure system parameters according to the needs of the operating environment; monitoring and optimization: monitor the system operating status, perform performance optimization and troubleshooting.
[0091] In summary, the relationship between the design state and the running state is: Complementarity: The design state architecture provides a blueprint and guidance for the running state architecture, while the running state architecture is the specific implementation and verification of the design state architecture. Iteration: During the software development process, the design state architecture and the running state architecture will gradually evolve iteratively according to changes in business requirements. Among them, the design state architecture focuses more on static architecture design principles, focusing on designing according to management requirements, while the running state architecture focuses more on the dynamic behavior and performance of the system, focusing on the discovery of the live network running architecture in the production environment.
[0092] Among them, in the design state, the structured standard model of the agile business system architecture can be used as a management handle through the five-layer architecture model of system, subsystem, application, service and computing node. Specifically, the system refers to a comprehensive whole, including several subsystems, which work together to support specific business goals or missions; the subsystem is a component of the system, usually responsible for a part of the system's functions or business processes; the application refers to a set of resources within the subsystem, which are bound to specific infrastructure resources and provide specific business functions or services for the subsystem; the service is a set of software processes under the application, and the business functions are realized through the operation of these processes; the computing node is the infrastructure that carries the service and provides computing power for the service, generally including cloud hosts, physical machines and containers. It can be seen that each of the five layers has different responsibilities and functions, and needs corresponding configuration management items (CI) and model relationships, and corresponding management standards are required to ensure its effective operation and maintenance.
[0093] The configuration items of the system include: system name, system code, service catalog and SLA, system person in charge, system importance level, system business positioning, system scope and boundary, business system architecture requirements, service life cycle, information security requirements, business continuity, resource management, and security level; the configuration items of the subsystem include: subsystem name, subsystem code, system person in charge, system importance level, subsystem function and SLA, information security requirements, performance baseline, monitoring baseline, service window, maintenance strategy and window, user and authority management, testing strategy, and change management requirements; the configuration items of the application include the name of the application, the code of the application, the person in charge of the application, application function and service description, application environment configuration, application security strategy, application performance indicators, application monitoring indicators, fault handling strategy, application release method, application version, and application technology stack; the configuration items of the service include: service name, person in charge, IP, port, service interface, calling service, and called service; the configuration items of the computing node include: node name, IP, person in charge, operating system, configuration, environment, type, and service process.
[0094] like Figure 3 As shown, in the standard model, the system, the subsystem, the application, the service and the computing node have the following association relationship:
[0095] The system includes several subsystems, each of which includes several applications, each of which includes several services, and each of which includes several computing nodes; one subsystem can only belong to one system, and one application belongs to one subsystem; the SLA of the system affects the SLA of the subsystem; the importance level of the system affects the importance level of the subsystem; the architectural design principles of the system affect the demand access principles, technology stack usage principles, data call principles, and authority control principles of the subsystem; the information security requirements of the system affect the security requirements and control of the subsystem; the business continuity plan of the system affects the service window, maintenance strategy and window, and quality assurance and testing of the subsystem; the change management requirements of the subsystem affect the release method, application version management, and version release history of the application; the performance baseline of the subsystem affects the performance indicators of the application; the monitoring baseline of the subsystem affects the monitoring indicators of the application.
[0096] Among them, the specific planning process of the design state architecture diagram includes: combining the positioning of the business system, planning from five levels: the system, the subsystem, the application, the service and the computing node; in the planning process of the five levels, for the models of the five levels, determining the model instances that need to be newly created and the existing model instances that need to be reused; after determining the model instance, calculating the required computing node information, the computing node information includes the type, configuration and number of computing nodes; planning the access logic, the access logic includes network partitioning, request access links, and data links, and the access logic can be represented in the computing node information to form the design state architecture diagram.
[0097] And, the creation process of establishing a model instance is as follows Figure 4 As shown, the change process is as follows Figure 5 As shown, the deletion process is as follows Figure 6 shown.
[0098] In step S103, the running state architecture adopts an automated collection method and combines a manual collection method to manage the configuration items involved in the service and computing node when executing;
[0099] Among them, the configuration items involved in the running state in the management service and computing node, the automatic collection method and the manual collection method adopted, include: calculating the access relationship between computing nodes through the network link information obtained from the operating system, and combining the relationship between computing nodes and services in the CMDB to calculate the calling relationship between services, and then calculating the calling relationship between applications, between subsystems and subsystems, and between systems; calculating the calling relationship between interfaces between applications through the call information between interfaces obtained from APM, and combining the relationship between interfaces and applications in CMDB, and calculating the running path of each business request in the system architecture based on the characteristics of APM; calculating the link relationship between computing nodes and databases or storage services collected in the OS, and combining the relationship between computing nodes and services in CMDB, so as to calculate the relationship between applications and databases or storage services. The calling relationship between services; through the service query interface provided by the message middleware, combined with the association relationship between the middleware and the application and the consumer recorded in the CMDB, the access relationship between the applications that interact through the message middleware is calculated; through the file mount point service information collected in the OS, combined with the relationship between the computing node and the application in the CMDB, the access relationship between several applications that interact through the file mount service is calculated; by connecting to the data service platform or component, the computing nodes that interact with data through the data service are obtained, and combined with the relationship between the computing node and the application recorded in the CMDB, the applications that interact through the data service platform are calculated; by connecting to the CDC data synchronization tool, which databases have data synchronization tasks are obtained, and combined with the relationship between the database and the application recorded in the CMDB, the access relationship between applications based on the database data synchronization task is calculated.
[0100] In step S104, the ledger record standards for the design state architecture and the operation state architecture are formulated, including formulating principles and management specifications to be followed in the ledger record, and the management specifications include the ledger templates and version management requirements of the design state architecture and the operation state architecture.
[0101] Among them, ledger records are a systematic and standardized record management method, which records relevant information and data in detail for specific objects or matters according to certain standards and processes. This method helps to improve management efficiency, improve data accuracy and completeness, enhance data traceability, strengthen risk control, promote compliance, facilitate data tracking and in-depth data analysis, facilitate knowledge sharing and inheritance, and support continuous improvement and enhance transparency.
[0102] The principles followed by the ledger record include: clarifying the record object and scope, the record object includes the relevant instances of the system, subsystem, application, service, and computing node, and the record scope includes the configuration items and associated relationships of the system, subsystem, application, service, and computing node; standardizing the record content and format, entering the configuration item content that needs to be recorded in the system, subsystem, application, service, and computing node in the ledger according to the preset format, and the relationship between the related instances needs to be associated; standardizing the record process, and the creation, modification, and deletion of the system, subsystem, application, service, and computing node instances that need to be recorded in the ledger In addition, supporting process support should be provided; unified standardization of ledger carriers requires the establishment of unified electronic tools for ledger records; convenience of query and analysis requires the provision of multiple methods for querying and analyzing ledger records; security and confidentiality, the access, recording, and modification of ledgers require corresponding security measures, which include at least one of role authority division, secondary access authentication, and data encryption storage; regulatory compliance, when conducting ledger records, it is also necessary to comply with relevant laws and regulations to ensure the legality of record acquisition and preservation; record retention requirements specify the retention period of ledger records to meet possible query and audit needs.
[0103] In addition, version records need to be managed in a standardized manner. Since the architecture itself is also a digital asset and can be versioned, the agile business system architecture version management can refer to the business system code version management model, but the two are different. On the one hand, it needs to manage and track changes at the system architecture design level, that is, the design state architecture version iteration management. On the other hand, it needs to obtain the actual deployment architecture and access architecture of the business system during runtime through automatic collection, that is, the operation state architecture version iteration management.
[0104] Therefore, the indicator items of the ledger template in the design state include: initial version information, system, subsystem, application, service, computing node, version number, release date, requirement ID, developer, functional description, compatibility information, performance indicators, technology stack information, system architecture topology, physical architecture topology, deployment guide, rollback plan, monitoring and maintenance, test and verification results, and other instructions. Among them, each indicator item is explained as follows: Initial version information: record the initialization version number and time of the system; system: the system involved; subsystem: the subsystem involved; application: the application involved; service: the service information involved; computing node: the computing node information involved; version number: a unique identifier used to distinguish different architecture versions; release date: record the date when the version architecture is officially released; requirement ID: the business requirement ID corresponding to the version; developer: information about the personnel involved in the development of this version; functional description: describe the new functions included in this version architecture, the optimization and deletion of the original functions, and how these changes improve the performance, security or other key attributes of the system; compatibility information: describe the compatibility of the new version architecture with the previous version and other system components, including forward compatibility and incompatible content; performance indicators: provide performance benchmark test results, such as response time, throughput, resource consumption, etc., to evaluate the performance of the new version; technology Stack information: technical architecture information of this version, including but not limited to development language, development framework, component type, database type, middleware type, data dictionary, main algorithms, dependent peripheral systems, etc.; System architecture topology: system architecture topology diagram of this version, including but not limited to system, subsystem, application and service node description, access relationship, hierarchical structure, etc.; Physical architecture topology: the physical architecture topology diagram of this version shall reflect the physical deployment topology of this version and the changes compared with the previous version; Deployment guide: provide the steps and requirements for deploying the new version of the architecture, including environment configuration, data migration, system upgrade, etc.; Rollback plan: design a rollback plan so that it can quickly restore to the state of the previous stable version when problems occur in the deployment of the new version; Monitoring and maintenance: changes in the monitoring and maintenance of the current version of the system architecture; Test and verification results: test report of this version; Other notes: other situations that need to be explained for management and user reference.
[0105] In addition, design-state version control is basically completed by manual operations, and is generally formulated and maintained by architects and development managers, following the principle of "who designs, builds, and maintains". If the design-state architecture needs to be adjusted according to the actual needs of system construction, it needs to be approved before it can be updated. Once updated, a new design-state architecture version will be generated for the system; therefore, the version management requirements for formulating the design-state ledger template include the following settings: initializing version specifications, defining version control systems, setting version change processes, standardizing architecture topology, version change tracking mechanisms, backups, and archiving. Among them, the system architecture initialization version specification: the architecture design prototype passed by the system architecture at the architecture review meeting (which should include but not be limited to the participation of relevant roles in business architecture, system architecture, technical architecture, data architecture and infrastructure) is the design state initialization version of the system architecture; system architecture version system: define a version control system for the architecture design state, which can adopt the mode of major version number and minor version number, and update the version number every time the architecture changes; architecture topology standardization: for the "system architecture topology" and "physical architecture topology" in the design state architecture version ledger model, it is necessary to provide a visual related architecture topology diagram and a document description in a unified format, and subsequent architecture version changes need to be iterated based on the standardized architecture topology information of the previous version; system architecture version change Optimized tracking mechanism: records the differences between each architecture version, the historical minutes of each architecture version decision, including the process of determining the initial version of the system architecture, the specific reasons for the approval or rejection of the architecture version change, the personnel involved in the architecture version review, etc. These records help team members and stakeholders to clearly understand the current status and historical changes of the architecture, thereby improving the transparency of the project and understanding the history of architecture evolution; backup and archiving: regularly back up the system architecture data and related system architecture documents in the ledger to ensure that the specific system architecture version information can be restored in the event of data loss or damage; comply with standards and industry practices: follow industry standards and industry practices to design and maintain the system architecture, do not be unconventional, and ensure the stability and scalability of the system architecture.
[0106] In addition, the relevant process of changing the system design state architecture version is set in the process management system. The triggering reason is that the system manager has a plan to adjust the system architecture; the second is that the design state architecture is inconsistent with the running state architecture, and the running state architecture should be used as the standard. In this case, the work is carried out according to the design state architecture version change process. Figure 7As shown, the system manager submits a system architecture change request through the process management system, including but not limited to the planned change time, change reason, change impact assessment, change plan and steps, change verification method and change rollback plan, etc.; the architecture group discusses the change request and forms a resolution at the regular architecture review meeting (which should include but not be limited to the participation of relevant roles of business architecture, system architecture, technical architecture, data architecture and infrastructure). If the change request is approved, a new architecture version number will be assigned for this architecture version change and updated to the system design state architecture version ledger. If it is not approved, it will be rejected and returned to the system manager; for applications that pass the change request, the business system change process is initiated, and the application form for the design state architecture version adjustment and the new architecture version number are bound; the change of the design state architecture version is implemented through the execution of the business system change process.
[0107] The running state is mainly based on the technical means of automatic discovery to obtain the access architecture and deployment architecture of the business system in the actual operating environment. The running state version also has an internal logic, which is the design state architecture associated with it. This design state architecture is the basis of the running state architecture. Under normal circumstances, the running state architecture of the same version should be consistent with the design state architecture. At the same time, from the perspective of actual production, what supports the actual operation of the business system in the five-layer model are the computing nodes and the service instances deployed on each computing node. The information of these two models can be automatically collected. Therefore, the indicator items of the ledger template of the running state include: the associated design state version number, system, subsystem, application, service, computing node, version number, latest update time, system architecture topology, and physical architecture topology. Among them, the associated design state version number: the design state version information associated with the running state; system: the system involved; subsystem: the subsystem involved; application: the application involved; service: the service information involved (collected in an automated way); computing node: the computing node information involved (collected in an automated way); version number: a unique identifier used to distinguish different architecture versions; latest update time: the latest date when the current version of the architecture was discovered; system architecture topology: the system architecture topology diagram of this version, which is mainly reflected in the actual access architecture (collected in an automated way); physical architecture topology: the physical architecture topology diagram of this version, which is mainly reflected in the actual physical deployment architecture (collected in an automated way).
[0108] The version management requirements for the running state include: implementing a role-based access control model to control the configuration permissions and data collection permissions of the automated collection tools to ensure that only authorized users can operate and maintain the tools; automatically collecting relevant service instance and computing node information after the application version is released and changed, and comparing it with the design state architecture; regularly collecting service instances and computing nodes of the business system through scheduled tasks to obtain the latest runtime configuration information; reasonably configuring tools that continuously collect runtime information, and monitoring their running status to ensure the normal operation of the tools; analyzing and adjusting automated collection methods that affect the stability and performance of the business system; establishing a running state architecture version change process in the process management system. When the design state and the running state architecture are inconsistent, the design state architecture shall be used as the basis for version changes and updates. In addition, the relevant processes for changing the system running state architecture version are as follows: Figure 8 shown.
[0109] In step S105, a visual verification standard for the system architecture is established, including setting a visualization target object, determining a data acquisition path, designing visualization elements, setting visualization target object element information, selecting visualization tools, realizing dynamic and interactive display, and using the version of the design state architecture as the baseline version and the version of the running state architecture as the running version, formulating a timed comparison mechanism between the baseline version and the running version, and if the comparison finds that the version information is inconsistent, generating a version difference work order and executing processing.
[0110] Visualization of the agile business system architecture is a technology that presents the components and workflows of the business system in a graphical way. It makes complex and abstract system architecture information intuitive and easy to understand and analyze. Especially for agile business systems, microservice architecture is often used for design and development, referring to the five-layer model of system, subsystem, application, service and computing node. Compared with the monolithic model of the steady-state business system, the architecture of the agile business system can be more intuitively presented after being visualized. The access relationship, hierarchical structure and business data flow of each service between and within each business system can be presented.
[0111] Among them, the explanation for step S105 is as follows: Determine the target object for visualization: There are many objects involved in the agile business system architecture, and the current agile business systems in the securities and fund industry are mostly developed in a microservice manner. Instances of the five-layer model of system, subsystem, application, service and computing node can be determined as the visualization target object; Data acquisition: Architecture visualization is essentially a running architecture display, so the data required for visualization can be obtained from the running architecture data information. If there are omissions, they can be supplemented manually; Design visualization elements: Design intuitive graphic elements to represent the relationship between visualization target objects, such as using different shapes, colors and lines; Visualization target object element information: name, function, level, capacity indicator, performance indicator, health status, upstream target object, downstream target object, etc.; Select appropriate visualization tools: Select appropriate visualization tools or platforms according to needs. These tools and platforms can provide visualization objects and topology views that need to be displayed in the agile business system architecture; Realize dynamic and interactive display: Provide dynamically updated visualization displays and support user interaction, such as zooming, panning, filtering and in-depth viewing of details.
[0112] In the design state architecture and running state architecture comparison specification, the design state architecture version mainly describes the architecture information of the business system from the management perspective, and the system topology diagram and physical deployment diagram reflect the expected service request access relationship and computing node deployment status when the business system is designed. Therefore, the design state business system architecture version is also the baseline version that meets the management requirements and architecture design. The running state architecture version is mainly based on the technical means of automatic discovery, which obtains the access architecture and deployment architecture in the actual operating environment, and obtains the service request access relationship and computing node deployment status when the business system is actually running. Therefore, the running state business system architecture version is the running version. Generally speaking, in the process of architecture design and management of enterprise organizations, the running state architecture of the same version of the business system should be consistent with the design state architecture without deviation. However, in actual situations, the running version collected in the running state may be inconsistent with the baseline version of the design state. At this time, it is necessary to analyze the running state architecture and the design state architecture of the same version number. A timed comparison mechanism should be set up during the low business peak period (such as the second half of the night every day), and the running state system architecture should be scanned regularly and compared with the design state version architecture information recorded in the ledger. When it is found that the version information of the design state architecture and the running state architecture of the business system is inconsistent, the process platform will automatically generate a work order for the difference between the design state and running state architecture versions.
[0113] In the case of version differences, such as Fig. 9 As shown, the following situations are handled:
[0114] Case 1: The design state architecture is accurate, but the running state architecture is actually implemented because the system manager did not initiate the architecture change management process for some reason. Routine daily changes may indeed cause changes in the system architecture. This situation is difficult to detect and is also a great harm to the system architecture, resulting in a deviation between the two. The running state architecture needs to be adjusted in time to keep it consistent with the design state architecture, and the system development manager needs to explain the reasons for the deviation between the two, summarize the experience, and achieve closed-loop management;
[0115] Case 2: The design state architecture is not considered comprehensively during the design process, and some designs are omitted or deviated. In this case, the design state architecture needs to be based on the running state architecture and adjusted in a timely manner, that is, the baseline version should be corrected through the running version, and the evaluators involved in the relevant architecture design state need to summarize their experience and realize closed-loop management.
[0116] It can be seen that in step S107, through the visual verification of the architecture, the mutual verification of the design state architecture and the running state architecture can, on the one hand, ensure that the running state architecture actually implemented in the business system conforms to the baseline version of the design state architecture, and on the other hand, ensure that the design state architecture of the business system is more accurate under the verification of the running state architecture, so as to provide a reference for the implementation of more high-value scenarios based on the trusted design state architecture.
[0117] From the above implementation modes, it can be seen that the present invention realizes the management of the entire life cycle of the agile business system architecture. On the one hand, it realizes the different demands of different roles for the management of the agile business system architecture, such as root cause analysis, architecture evolution, correlation impact analysis, etc.; on the other hand, by managing the consistency between the design state and the running state of the agile business system architecture, it increases the grip for managing the business system, which helps to improve the stability, security and performance of the agile business system.
[0118] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary technical means in the art that are not disclosed in the present disclosure. The specification and embodiments are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the claims.
Claims
1. A structured management method for an agile business architecture system, characterized in that: The method comprises: According to the determined hierarchical type of the business architecture system, a design state architecture is formed, wherein the design state architecture includes demand finalization, architecture design, software design, development, and testing, wherein the architecture design includes domain division, component division, interface definition, and data flow design, and the business architecture system formed based on the design state architecture is deployed and maintained to form an operation state architecture; When designing the design state architecture, a structured standard model is designed. The standard model adopts a five-layer structure, which includes system, subsystem, application, service, computing node in order, and defines the configuration items of each layer. When planning the standard model, its model instance, access logic architecture, computing node information, and the creation, modification and deletion process of the model instance are planned; When the running state architecture is executed, an automated collection method is used in combination with a manual collection method to manage the configuration items involved in the service and computing nodes; Formulate the ledger record standards for the design state architecture and the running state architecture, including formulating the principles and management specifications to be followed for ledger record, wherein the management specifications include the ledger templates and version management requirements for the design state architecture and the running state architecture; Establish visual verification standards for the system architecture, including setting the visualization target object, determining the data acquisition path, designing visualization elements, setting visualization target object element information, selecting visualization tools, realizing dynamic and interactive display, and using the design state architecture version as the baseline version and the running state architecture version as the running version, and formulating a timed comparison mechanism between the baseline version and the running version. If the comparison finds that the version information is inconsistent, generate a version difference work order and execute processing.
2. A method for structured management of an agile business architecture system according to claim 1, characterized in that: When building and managing the design state, the following operations are performed: Requirements analysis, where the requirements analyzed include one or more of business requirements, user requirements, system requirements definition, functional requirements, non-functional requirements, security requirements, technical requirements, data requirements, integration requirements, testability requirements, change management requirements, priorities, and dependencies; Architectural design, including: the relationships between systems, subsystems, and applications; Interface definition, including: defining the interaction interface between different components or services; Technology selection, including: choosing the corresponding technology stack and tools for development.
3. The method for structured management of an agile business architecture system according to claim 1, characterized in that: When building and managing the runtime, the following operations are performed: Deployment environment, deploying the designed software components into the production environment. The operational architecture includes the access architecture and the deployment architecture. The access architecture represents the access relationship between components within the business system, and the deployment architecture represents how the business system architecture is deployed in the environment. Configuration parameters: configure system parameters according to the needs of the operating environment; Monitoring and optimization: Based on visual monitoring of the operating status of business systems, performance optimization and troubleshooting are carried out.
4. The method for structured management of an agile business architecture system according to claim 1, characterized in that: The configuration items of the system include: system name, system code, service catalog and SLA, system person in charge, system importance level, system business positioning, system scope and boundary, business system architecture requirements, service life cycle, information security requirements, business continuity, resource management, and security level; the configuration items of the subsystem include: subsystem name, subsystem code, system person in charge, system importance level, subsystem function and SLA, information security requirements, performance baseline, monitoring baseline, service window, maintenance strategy and window, user and authority management, testing strategy, and change management requirements; the configuration items of the application include the name of the application, the code of the application, the person in charge of the application, application function and service description, application environment configuration, application security strategy, application performance indicators, application monitoring indicators, fault handling strategy, application release method, application version, and application technology stack; the configuration items of the service include: service name, person in charge, IP, port, service interface, calling service, and called service; the configuration items of the computing node include: node name, IP, person in charge, operating system, configuration, environment, type, and service process.
5. The method for structured management of an agile business architecture system according to claim 1, characterized in that: In the standard model, the system, the subsystem, the application, the service and the computing node have the following association relationship: The system includes several subsystems, the subsystems include several applications, the applications include several services, and the services include several computing nodes; One subsystem can only belong to one system, and one application belongs to one subsystem; The SLA of the system affects the SLA of the subsystem; The importance level of the system affects the importance level of the subsystem; The system's architectural design principles affect the subsystem's demand access principles, technology stack usage principles, data call principles, and permission control principles; The information security requirements of the system affect the security requirements and controls of the subsystems; The business continuity plan of the system affects the service windows, maintenance strategies and windows, and quality assurance and testing of the subsystems described; The change management requirements of the subsystem affect the release mode of the application, application version management and version release history; The performance baseline of the subsystem affects the performance indicators of the application; The monitoring baseline of the subsystem affects the monitoring indicators of the application.
6. The method for structured management of an agile business architecture system according to claim 1, characterized in that: The specific planning process of the design state architecture diagram includes: In combination with the positioning of the business system, planning is performed from five levels: the system, the subsystem, the application, the service, and the computing node; In the planning process of the five levels, for the models at the five levels, determine the new model instances that need to be created and the existing model instances that need to be reused; After determining the model instance, the required computing node information is calculated, and the computing node information includes the type, configuration and quantity of the computing nodes; The access logic is planned, and the access logic includes network partitions, request access links, and data links. The access logic can be represented in the computing node information to form the design state architecture diagram.
7. The method for structured management of an agile business architecture system according to claim 1, characterized in that: The configuration items involved in the running state in the management service and computing node, and the automatic collection method and manual collection method adopted include: By obtaining network link information from the operating system, the access relationship between computing nodes is calculated. At the same time, the relationship between computing nodes and services in the CMDB is combined to calculate the calling relationship between services, and then the calling relationship between applications, between subsystems, and between systems is calculated. By obtaining the call information between interfaces from APM and combining it with the relationship between interfaces and applications in CMDB, the call relationship between interfaces between applications can be calculated. At the same time, based on the characteristics of APM, the running path of each business request in the system architecture can be calculated. The call relationship between the application and the database or storage service is calculated by combining the link relationship between the computing node and the database or storage service collected in the OS with the relationship between the computing node and the service in the CMDB. Through the service query interface provided by the message middleware and the association between the middleware, applications and consumers recorded in the CMDB, the access relationship between applications interacting through the message middleware is calculated; The file mount point service information collected in the OS is combined with the relationship between computing nodes and applications in the CMDB to calculate the access relationship between several applications that interact through the file mount service. By connecting to the data service platform or component, the computing nodes that interact with data through the data service are obtained, and the applications that interact through the data service platform are calculated based on the relationship between the computing nodes and applications recorded in the CMDB. By connecting to the CDC data synchronization tool, we can obtain which databases have data synchronization tasks, and combine the relationship between databases and applications recorded in the CMDB to calculate the access relationship between applications based on database data synchronization tasks.
8. The method for structured management of an agile business architecture system according to claim 1, characterized in that: The principles followed by the ledger records include: Clarify the objects and scope of the records. The objects of the records include relevant instances of systems, subsystems, applications, services, and computing nodes. The scope of the records includes the configuration items and their associations of the systems, subsystems, applications, services, and computing nodes: Standardize the record content and format. The configuration items that need to be recorded in the system, subsystem, application, service and computing node should be entered in the preset format, and the relationship between related instances should be associated. Standardize the recording process, and provide supporting process support when recording the creation, modification, and deletion of systems, subsystems, applications, services, and computing node instances in the ledger; The unified standardization of ledger carriers requires the establishment of a unified electronic tool for ledger records; To facilitate query and analysis, multiple methods of querying and analyzing records in the ledger need to be provided; Security and confidentiality: The access, recording, and modification of the ledger are accompanied by corresponding security measures, which include at least one of role authority division, secondary access authentication, and data encryption storage.
9. The method for structured management of an agile business architecture system according to claim 1, characterized in that: The indicator items of the account template in the design state include: Initial version information, system, subsystem, application, service, computing node, version number, release date, requirement ID, developer, functional description, compatibility information, performance indicators, technology stack information, system architecture topology, physical architecture topology, deployment guide, rollback plan, monitoring and maintenance, test and verification results, and other instructions; The version management requirements of the ledger template in the design state include the following settings: Initialize version specifications, define version control system, set version change process, standardize architecture topology, version change tracking mechanism, backup and archive.
10. The method for structured management of an agile business architecture system according to claim 1, characterized in that: The indicator items of the account template in the running state include: Associated design state version number, system, subsystem, application, service, computing node, version number, latest update time, system architecture topology, physical architecture topology; The version management requirements for the running state include: Implement a role-based access control model to control the configuration permissions and data collection permissions of automated collection tools, ensuring that only authorized users can operate and maintain the tools; After the application version is released, the relevant service instance and computing node information is automatically collected and compared with the design state architecture; Regularly collect service instances and computing nodes of business systems through scheduled tasks to obtain the latest runtime configuration information; Properly configure tools that continuously collect runtime information and monitor their operating status to ensure that the tools are functioning properly; Analyze and adjust automated collection methods that affect business system stability and performance; A running state architecture version change process is established in the process management system. When the design state architecture is inconsistent with the running state architecture, the design state architecture is used as the basis for version change and update.
Citation Information
Patent Citations
Online management system of data model
CN112380189A
Construction method for integrated collaborative management platform of digital shipyard
CN116757634A
System for realizing multi-level architecture asset maintenance and guaranteeing architecture design and system operation state consistency
CN117992023A
Software deployment architecture management method and related device
WO2024040930A1
Cited By
Intelligent data processing and collaboration architecture integrating data, table and account space
CN119416756A
