Intelligent collaborative management method and system for data interaction information based on modularized architecture

Abstract

The invention discloses an intelligent collaborative management method and system for data interaction information based on a componentized architecture, and relates to the technical field of intelligent management and control of power system outage maintenance plans, and the method comprises the steps: carrying out the first relation division of a page module and a component according to a business demand; performing first collaborative management on the data between the modules and the components, and dividing the levels of the components; dividing the component interaction management first scene, and performing first expansion adjustment on the common component function. According to the intelligent collaborative management method for the data interaction information based on the modularization architecture, the reusability of codes is improved by distinguishing the service components from the public components, the system can be adjusted and the adaptability is improved according to scene requirements through a unified state management mode, unnecessary resource consumption is reduced through the modularization architecture, and the system is convenient to use. And the operation efficiency of the system is improved, and better effects are achieved in the aspects of expandability, maintainability and stability.

Description

Technical Field

[0001] The present invention relates to the technical field of intelligent control of power system outage maintenance plans, and specifically to an intelligent collaborative management method for data interaction information based on a componentized architecture. Background Art

[0002] With the increasing scale of the power system and the deepening development of the modern power market, the management complexity of power grid outage maintenance operations has increased significantly. To meet the business requirements under multi-level dispatching, power grid dispatching agencies at all levels rely on intelligent control platforms to achieve data sharing and collaboration. However, traditional outage maintenance information management models usually use static and manual methods for information transfer and plan management, with low efficiency and prone to errors. In recent years, the application of intelligent systems based on componentized architectures and modular designs in the power field has gradually increased, providing technical support for the real-time sharing and intelligent decision-making of outage maintenance plans. At the same time, auxiliary technologies combining big data and artificial intelligence have gradually improved the efficiency of data interaction and the accuracy of information collaboration. These progress have laid a foundation for the intelligence and high efficiency of outage maintenance operations in multi-level power grids.

[0003] Although the current outage maintenance management platform of the power system has achieved certain results in informatization construction, there are still the following deficiencies: First, the complexity of the data interaction mechanism is high. Existing technologies generally use the method of directly calling data between modules, resulting in too high code coupling degree and significantly increasing the development and maintenance costs. Second, the scalability of the system is poor. When facing new business scenarios or specific requirement adjustments, it often requires reconstructing the logic of existing modules, which is time-consuming and laborious. Third, the data transfer path is not clear, making it difficult to ensure the real-time and accuracy of data between multi-level dispatching. Especially when performing state transfer between multiple modules, information is easily lost or conflicts occur. In addition, existing solutions lack intelligent collaborative strategies for multi-level dispatching outage plans and cannot effectively meet multi-dimensional requirements in a dynamic power grid environment, such as real-time sharing of key equipment information and multi-dimensional plan collaborative optimization. Summary of the Invention

[0004] In view of the above existing problems, the present invention is proposed.

[0005] Therefore, the technical problem solved by the present invention is: The existing outage maintenance plan management method has a complex data interaction mechanism and high code coupling degree, poor system scalability leading to difficult business adjustment, unclear data transfer path prone to information loss, and how to optimize the efficiency of data interaction and state collaborative management under multi-level dispatching.

[0006] To solve the above technical problems, the present invention provides the following technical solutions: An intelligent collaborative management method for data interaction information based on a componentized architecture, including performing a first relationship division on page modules and components according to business requirements; performing a first collaborative management on the data between modules and components, dividing the levels of components; dividing the first scenario of component interaction management, and performing a first extension and adjustment on the functions of common components.

[0007] As a preferred solution of the intelligent collaborative management method for data interaction information based on a componentized architecture according to the present invention, wherein: the performing a first relationship division on page modules and components includes performing a division by combining various aspects of analysis, dividing the page into modules, and dividing components according to the modules.

[0008] As a preferred solution of the intelligent collaborative management method for data interaction information based on a componentized architecture according to the present invention, wherein: the dividing components according to the modules includes dividing components according to module responsibilities, separating business components and common components.

[0009] As a preferred solution of the intelligent collaborative management method for data interaction information based on a componentized architecture according to the present invention, wherein: the performing a first collaborative management on the data between modules and components includes determining the data interaction method between modules, and performing collaborative management according to the linkage interaction between modules.

[0010] As a preferred solution of the intelligent collaborative management method for data interaction information based on a componentized architecture according to the present invention, wherein: the performing a first collaborative management on the data between modules and components further includes analyzing the data interaction linkage between components, and performing collaborative management on the components.

[0011] As a preferred solution of the intelligent collaborative management method for data interaction information based on a componentized architecture according to the present invention, wherein: the dividing the first scenario of component interaction management includes analyzing the usage scenario of application data interaction linkage, and dividing the first scenario of interaction management for the defined levels of components.

[0012] As a preferred solution of the intelligent collaborative management method for data interaction information based on a componentized architecture according to the present invention, wherein: the performing a first extension and adjustment on the functions of common components includes determining and extracting common components, and performing a first extension and adjustment on the functions of common components.

[0013] Another object of the present invention is to provide an intelligent collaborative management system for data interaction information based on a componentized architecture, which can determine the data interaction and state management methods between modules through a collaborative management module, and solves the problems of complex current data interaction mechanisms and high coupling degrees between modules.

[0014] As a preferred solution of the intelligent collaborative management system for data interaction information based on the componentized architecture of the present invention, it includes a relationship division module, a collaborative management module, and a scenario division module; the relationship division module is used to perform a first relationship division on page modules and components according to business requirements; the collaborative management module is used to perform a first collaborative management on the data between modules and components and divide the levels of components; the scenario division module is used to divide the first scenario of component interaction management and perform a first extension and adjustment on the functions of common components.

[0015] A computer device includes a memory and a processor. The memory stores a computer program. It is characterized in that when the processor executes the computer program, the steps of the intelligent collaborative management method for data interaction information based on the componentized architecture are implemented.

[0016] A computer-readable storage medium stores a computer program on it. It is characterized in that when the computer program is executed by a processor, the steps of the intelligent collaborative management method for data interaction information based on the componentized architecture are implemented.

[0017] Advantages of the present invention: The intelligent collaborative management method for data interaction information based on the componentized architecture provided by the present invention avoids code duplication and improves code reusability by distinguishing business components and common components. Due to the componentized design, each module can be developed and extended independently. When adding new functions, there is no need to modify the existing code, reducing the workload of later development and maintenance. The clear division of modules and components makes the data flow clearer, avoiding data synchronization problems caused by mutual dependencies between modules, improving data consistency and stability, avoiding frequent direct data calls in traditional methods, making data transmission between modules more efficient, reducing communication overhead, ensuring the correctness and consistency of data through a unified state management method, avoiding errors caused by out-of-sync data between modules. Different modules only interact through data interfaces, reducing mutual dependencies between modules and making the code clearer and more maintainable. Different component interaction management methods adapt to different business requirements, enabling the system to be adjusted according to scenario requirements and improving adaptability. The reasonable extraction and optimization of common components enable the code to be reused in multiple modules, improving development efficiency. The function extension of common components adopts a plug-in design, enabling new functions to be developed independently and loaded dynamically without modifying the existing code, reducing system maintenance costs. The componentized architecture reduces unnecessary resource consumption and improves the operating efficiency of the system. The intelligent collaborative management strategy reduces redundant calculations during data transmission and improves the accuracy of data processing. Through data-driven optimization, the system's adaptability to different scheduling scenarios is improved, enabling it to complete tasks more efficiently. The present invention achieves better results in terms of scalability, maintainability, and stability. Description of the Drawings

[0018] To more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the accompanying drawings required for the description of the embodiments. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other accompanying drawings can be obtained based on these drawings. Among them:

[0019] Figure 1 It is the overall flowchart of the intelligent collaborative management method for data interaction information based on a componentized architecture provided by the first embodiment of the present invention.

[0020] Figure 2 It is the scenario simulation diagram of the intelligent collaborative management method for data interaction information based on a componentized architecture provided by the first embodiment of the present invention.

[0021] Figure 3 It is the overall module diagram of the intelligent collaborative management system for data interaction information based on a componentized architecture provided by the third embodiment of the present invention. Detailed implementation manners

[0022] To make the above objects, features, and advantages of the present invention more obvious and understandable, the following will make a detailed description of the specific implementation manners of the present invention with reference to the accompanying drawings of the specification. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0023] Embodiment 1

[0024] Referring to Figure 1 - Figure 2 , as an embodiment of the present invention, there is provided an intelligent collaborative management method for data interaction information based on a componentized architecture, including:

[0025] S1: According to business requirements, perform a first relationship division on page modules and components.

[0026] Furthermore, performing a first relationship division on page modules and components includes performing a division by combining various aspects of analysis, dividing the page into modules, and dividing components according to the modules.

[0027] In the embodiments of the present application, the first relationship division is to analyze the business requirements of the maintenance plan system, and perform a division by combining business, page layout, usage, and linkage interaction analysis. The page is divided into a query panel, a table list, and a legend display, and then components are divided according to the modules.

[0028] It should also be noted that by distinguishing business components from common components, code duplication is avoided, code reusability is improved, and the development and maintenance of the system are made more efficient. Due to the component-based design, each module can be developed and extended independently. When adding new functions, there is no need to modify the existing code, greatly reducing the workload of later development and maintenance. The clear division of modules and components makes the data flow clearer, avoiding data synchronization problems caused by mutual dependencies between modules and improving data consistency and stability.

[0029] Furthermore, dividing components according to modules includes dividing components according to module responsibilities and separating business components and common components.

[0030] In the embodiment of the present application, analyze the module functions, divide the components according to the responsibilities, and separate the business components and the common components. The business components are specifically used to process specific business logics, are usually related to specific business domains, and encapsulate the core logics and data displays of specific domains. The table data component of the maintenance plan on the page displays the data related to the maintenance plan, such as plan name, planned quantity, maintenance time, etc. By extracting the table data component of the maintenance plan divided according to business requirements, the accuracy and consistency of the data are ensured, and at the same time, the mutual interference with other business logics is reduced. The legend component for counting the maintenance plan provides statistical charts of the maintenance plan, such as bar charts, line charts, etc. By extracting a dedicated statistical legend component, data analysis of the maintenance plan is performed, and at the same time, the readability of the page and the user experience are improved;

[0031] The common components are the components shared and reused by multiple modules or application programs in system development. These components usually contain general functions and logics and are called and integrated by different parts. The table component of the common components has functions such as column setting, export, double-click editing, sorting, etc. The tables on the system page are all similar components, and the common components can be extracted for business components to call and expand the functions of the common components according to business requirements, improving code reusability, maintainability, and scalability. The query panel function component of the common components provides general query condition input, filtering, resetting, etc. functions. By extracting the common query panel component, the development process of the query function can be simplified, and the development efficiency can be improved. At the same time, when the query logic needs to be adjusted, it only needs to be modified in the common components, which is applicable to all pages in the system that require query functions, such as maintenance plan query, inventory query, etc.

[0032] It should also be noted that by dividing business components and common components, the code can be better organized, reusability can be improved, maintenance costs can be reduced, and the development speed can be accelerated. Business components focus on the logics and data displays of specific business domains, while common components provide general functions and logics to support the sharing and reuse of multiple modules or application programs. This component-based development method helps to build a flexible, scalable, and easy-to-maintain software system.

[0033] In an optional embodiment, the first relationship partitioning can also be based on the gradual deconstruction and integration of the business function domain. Starting from the overall business scenario of the system, combining the characteristics of the data flow and the functional boundaries of the business modules, the design of modules and components is completed through the partitioning strategy of the function domain;

[0034] According to the business logic of the power outage maintenance plan system, the overall functions of the system are divided into several function domains, such as the data acquisition domain, the plan scheduling domain, the status monitoring domain, and the report analysis domain. Each function domain is further subdivided into independent function modules. For example, the data acquisition domain includes a data acquisition entry module and a data verification module, and the plan scheduling domain includes a plan scheduling main module and a plan optimization module, etc. Through the function domain partitioning, the business responsibilities of each module are clarified, and the coupling relationship between modules is reduced globally. Each module is divided into a logic layer and a display layer according to its functional complexity. The logic layer is responsible for processing the core business logic of the module, such as data calculation, rule matching, etc. Each logical function is further split into independent logical units for easy maintenance and expansion. The display layer is responsible for the interface components for interacting with users. Each interface component only focuses on a single display function, such as the display of the plan list, the presentation of the status chart, etc. The logic layer and the display layer are connected through a clear data interface to ensure clear data flow. For the functions or logics shared among multiple modules, common components are extracted. The common components are developed independently of specific modules and are adapted to the call requirements of different modules. After each module realizes the independence of its internal functions within the business domain, they are integrated through a business domain control center to ensure efficient cooperation among the modules within the function domain. The interaction between different function domains is managed through an event mechanism or middleware to avoid direct calls.

[0035] S2: Perform the first collaborative management on the data between modules and components, and partition the levels of the components.

[0036] Furthermore, performing the first collaborative management on the data between modules and components includes determining the data interaction method between modules and performing collaborative management according to the linkage interaction between modules.

[0037] In the embodiment of the present application, the first collaborative management is to determine the data interaction method between each module. If there is linkage data interaction between page modules, the data variables are promoted to the parent module for unified management. If there is no linkage interaction between modules, the data variables are independently defined and stored within their respective modules.

[0038] It should also be noted that the method of the present invention avoids frequent direct data calls in the traditional method, makes data transmission between modules more efficient, reduces communication overhead, ensures the correctness and consistency of data through a unified state management method, and avoids errors caused by data asynchronization between modules. Different modules only interact through data interfaces, reducing the mutual dependence between modules and making the code clearer and more maintainable.

[0039] Furthermore, the first collaborative management of data between modules and components also includes analyzing the data interaction linkage between components and performing collaborative management on the components.

[0040] In the embodiment of the present application, after determining the information management of data interaction between modules, further analyze the data interaction linkage between components. If there is a linkage method between components, promote the data variables to the parent component for unified management. If there is no linkage interaction between components, define data variables inside the components for storage.

[0041] It should also be noted that by dividing the levels of components in the module where the data state is located, the data is both independent and collaboratively managed with each other. By planning the data context, the maintainability, iterability, and scalability of the system are improved.

[0042] In an alternative embodiment, the first collaborative management can also be based on the data management of the subscription and publishing mechanism. An independent event center is established in the system as an intermediary for data interaction between modules. The event center is responsible for listening to data changes from modules and broadcasting notifications to modules that have subscribed to the event. Each module only needs to interact with the event center and does not need to directly communicate with other modules, eliminating the direct dependency relationship between modules;

[0043] When the data state of a certain module changes, the module publishes an event through the event center, attaching the changed data. For example, when the plan scheduling module completes the generation of a new plan, it will publish an event of plan generation completion to the event center and attach the plan data. Other modules subscribe to relevant events according to their own business needs. For example, the status monitoring module subscribes to the event of plan generation completion. When the event is triggered, the status monitoring module will automatically obtain relevant data and execute the corresponding logic;

[0044] The event center acts as the manager of the global data stream. By maintaining the subscription and publishing relationship graph of events, it uniformly records the relationship between all event subscribers and publishers. The flow of data follows the rules of the event center, avoiding unnecessary data coupling between modules. For example, the data acquisition module does not need to directly interact with the report generation module, but transfers data through the event center;

[0045] To avoid conflicts during event handling, all events are divided into different priorities according to business importance and data flow. For example, the state monitoring module has high real-time requirements, and its event priority is set higher than the offline processing requirements of the report generation module. The event center processes the tasks in the event queue in order of priority to ensure the efficient execution of critical business;

[0046] When an error occurs in a module while processing an event, the event center will record the status of the event and attempt to re-trigger it. If the re-trigger fails multiple times, the event center will mark the event as abnormal and notify the relevant module for processing to ensure the robustness of the system;

[0047] Through the subscription mechanism of the event center, the dynamic loading of new modules can be easily achieved. The new module only needs to register the event types it needs to subscribe to with the event center without modifying the logic of the existing modules. For example, when adding a new fault analysis module, it only needs to subscribe to the events of abnormal state detection to complete the integration.

[0048] S3: Divide the first scenario of component interaction management and make the first extension and adjustment to the functions of common components.

[0049] Furthermore, dividing the first scenario of component interaction management includes analyzing the usage scenarios of application data interaction linkage and dividing the first scenario of component hierarchical definition interaction management.

[0050] In the embodiment of the present application, dividing the first scenario of component interaction management is to analyze the usage scenarios of application data interaction linkage. For complex business operation scenarios with multiple linkages, multiple interactions, and multiple levels, based on React's custom Hooks, React's state management method, and state lifting strategy interaction management method, divide the scenario of component hierarchical definition interaction management;

[0051] The state used inside the component does not have cross-component application or linkage situations and only affects the variables inside the component itself. Use Class Components. In Class Components, use this.state to define the state of the component. The state is initialized in the constructor and then updated through the setState method; use functional components and Hooks. In functional components, use the useState Hook to define the state. useState returns an array containing the state and a function to update the state. The state and the function to update the state can be obtained respectively through destructuring assignment;

[0052] When the interface content is complex, it is possible to further abstract the module business, keep the component hierarchy between 2 and 3 levels, and improve the application performance and response speed. If the components are at the sibling level, that is, the state is shared between components, it is recommended to lift the state to the parent component and pass it to the child component through props to avoid deep nesting and ensure clear and efficient state management. Through prop passing, the props value can only be passed unidirectionally. Avoid over-refining the extracted components and avoid deep prop passing. React is a unidirectional data flow. When the state affects each other between the parent and child components, at least 2 props (value, onChange) are required to complete. When this situation crosses component hierarchies, the definition method is complex, but the data flow context is clear. Developers can clearly see the flow of the data state and locate the code block that affects the state update, improving the iterability and scalability of the code.

[0053] When the state used between components spans multiple levels, use useContext to achieve cross-level state transfer and sharing, following the principle of unidirectional data flow. The states of each component do not affect each other and can be changed by the management side, improving the application state management ability. When multiple components in the application need to share certain states, use useContext to create a global state manager. Create a Context object to store the shared state and use useContext in the child components to obtain and update the state. Create a context Context through React.createContext, define the state in a Context Provider, wrap the components that need to access the state in the Provider, and then use useContext in the components that need to access the state to obtain the state value. Facing multi-level and deep state transfer, use useContext to create a global state manager, which is simple and convenient to use, avoiding the performance consumption caused by passing props between multiple layers of components, improving the performance of the components. By lifting the global state to the top-level component and then obtaining it where needed through useContext, the coupling between components can be better decoupled. Through useContext, it can be clearly seen which components share the same global state, facilitating maintenance and management.

[0054] Furthermore, perform the first expansion and adjustment on the functions of common components, including determining the extraction of common components and performing the first expansion and adjustment on the functions of common components.

[0055] In the embodiments of the present application, extracting common components is to improve the reusability of code, reduce the cost of repeated coding, and unify the implementation of similar functions in the project. The first extension adjustment is to analyze the functions of the common components that need to be extended and adjusted, clarify the new functions or adjusted functions that need to be implemented, and modify the code of the common components according to the requirements, including operations such as adding new props, modifying existing logic, and adding styles, to ensure that the modified components still meet the design and function requirements of the project and do not affect the business components that have called the common components. Test the modified common components to ensure that the newly added functions and adjusted functions work properly and do not affect the existing functions. After completing the component development, add the call and test of the corresponding components of the module to the page under the module to complete the development of the system page.

[0056] In an alternative embodiment, the first extension adjustment can also be based on the functional extension and adjustment of the common components of the plug-in architecture. Design a plug-in interface on the basis of the common components to allow new functions to be added to the components or existing functions to be adjusted through plug-ins. The plug-in interface includes functions such as function registration, loading, execution, and unloading. Each plug-in encapsulates an independent functional module and implements a standardized interface with the common components to communicate with the component body. For example, a data table component can support functions such as sorting, column filtering, and exporting through plug-ins.

[0057] Design a plug-in registration center for each common component, which is responsible for managing the registration and association of plug-ins. When a plug-in is loaded, it registers its function type, call method, and applicable components through the registration center. When the common component is initialized, it loads the eligible plug-ins through the plug-in registration center and dynamically loads or unloads the plug-ins according to the requirements at runtime. When the user needs to enable the column filtering function, the table component will load the corresponding plug-in from the registration center and call its interface to implement the function. The dynamic loading of the plug-in is achieved through lazy loading, that is, the plug-in is only loaded when the function is called, reducing the initialization time of the component and the occupation of system resources.

[0058] The plug-in communicates with the common component through a unified event mechanism. When the user selects a sorting rule in the table, the sorting function plug-in sends a sorting event to the table component and attaches sorting parameters. The common component calls the function of the plug-in according to the event content to complete the response to the user's requirements.

[0059] When new functions need to be added to the component, only new plug-ins need to be developed and registered in the plug-in registration center, without modifying the core logic of the component. When existing functions need to be adjusted, it is achieved by updating the plug-in logic. The entire process of the plug-in from loading to unloading is uniformly managed by the registration center, including stages such as initialization, use, and destruction. The status of the plug-in is monitored in real time by the registration center to ensure that its functions are correctly called or released at the appropriate time points.

[0060] It should also be noted that different component interaction management methods are adapted to different business requirements, enabling the system to be adjusted according to scenario requirements, improving adaptability. The reasonable extraction and optimization of common components enable the code to be reused in multiple modules, reducing repetitive development work and improving development efficiency. The functional expansion of common components adopts a plug-in design, enabling new functions to be developed independently and loaded dynamically without modifying the existing code, thereby reducing the system maintenance cost.

[0061] Embodiment 2

[0062] An embodiment of the present invention provides an intelligent collaborative management method for data interaction information based on a componentized architecture. To verify the beneficial effects of the present invention, scientific demonstrations are carried out through economic benefit calculations and simulation experiments.

[0063] The experiment was conducted in a multi-level scheduling environment. The main objective of the experiment was to test the advantages of the method of the present invention in terms of data interaction efficiency, system response speed, data consistency, and maintainability. The experimental environment included a power grid scheduling simulation platform, a data interaction server, a front-end display system, and a database management system. Real power outage plan data was used as input to simulate the operation under actual scheduling scenarios. According to the method of the present invention, the business logic of the power outage maintenance plan was analyzed, and the system was divided into multiple functional modules, including a plan scheduling module, a status monitoring module, a data synchronization module, and a visualization analysis module. Each module was further decomposed into multiple business components and common components to achieve efficient data flow and low coupling between modules. In the experimental implementation stage, power grid scheduling data was first loaded to verify the data transfer between different components. The experiment designed a set of maintenance plans with different time windows and compared the response speed and data consistency of the traditional monolithic architecture and componentized architecture through the system. In the data interaction test, a set of maintenance task data was input into the plan scheduling module using the simulation scheduling platform. The system parsed the data through the componentized architecture and distributed it to other business modules, including the status monitoring module, the data storage module, and the visualization display module, ensuring smooth and non-redundant data. To further evaluate the scalability of the system, a new business requirement - dynamically adjusting the power outage plan - was added to the experiment. Using the method of the present invention, the newly added functional components could be directly connected to the existing system framework without modifying the core code. Only by registering new business components at the module management layer could the functions be added and optimized. In the comparison experiment, the traditional system needed to modify the code of multiple modules and conduct repeated tests, while the method of the present invention only needed to add new components and complete data interaction through module interfaces, greatly reducing the development workload and iteration cycle. In the final stage, the code maintenance costs and data interaction paths under different architectures were compared to verify the advantages of the method of the present invention in reducing code coupling and improving data processing efficiency. After the experimental data was collected, the performance indicators of different component interaction methods were compared, including data transmission rate, status synchronization accuracy rate, system response time, code coupling degree, maintenance cost reduction rate, and system scalability score, ensuring the objectivity and repeatability of the effect of the method of the present invention.

[0064] Through component-based design, the data flow path between different modules becomes clearer, reducing unnecessary coupling and improving data transmission rate and system response speed. Compared with the traditional method that requires manual maintenance of status synchronization, the method of the present invention adopts a hierarchical architecture, making status updates more accurate and avoiding data inconsistency problems caused by redundant calls. The method of the present invention adopts dynamic component management, enabling the addition of new functions without modifying the existing code. Only by adding new business components can the functions be extended. Due to the reduction of code coupling degree, developers can more accurately locate problems when adjusting or optimizing the system, reducing the workload of development iteration and improving the maintainability of the system.

[0065] Example 3

[0066] Reference Figure 3 , an embodiment of the present invention provides an intelligent collaborative management system for data interaction information based on a componentized architecture, including: a relationship division module, a collaborative management module, and a scenario division module.

[0067] Among them, the relationship division module is used to perform a first relationship division on page modules and components according to business requirements; the collaborative management module is used to perform a first collaborative management on the data between modules and components and divide the levels of components; the scenario division module is used to divide the first scenario of component interaction management and perform a first extension and adjustment on the functions of common components.

[0068] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in various embodiments of the present invention. The aforementioned storage medium includes: USB flash drives, mobile hard disks, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), magnetic disks, or optical disks, etc., all kinds of media that can store program codes.

[0069] The logic and / or steps represented in the flowchart or described in other ways herein, for example, can be considered as a definite sequence list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processor, or other systems that can fetch instructions from the instruction execution system, apparatus, or device and execute the instructions), or in combination with these instruction execution systems, apparatus, or devices. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device.

[0070] More specific examples (a non-exhaustive list) of computer-readable media include the following: electrical connections (electronic devices) having one or more wirings, portable computer diskettes (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber devices, and portable compact disc read-only memory (CDROM). Additionally, the computer-readable media can even be paper or other suitable media on which a program can be printed, because the program can be obtained electronically, for example, by optically scanning the paper or other media, then editing, interpreting, or otherwise processing it as appropriate, and then storing it in a computer memory.

[0071] It should be understood that various parts of the present invention can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, multiple 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 well 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 (PGA), field programmable gate arrays (FPGA), etc. It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit them. Although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of the present invention can be modified or equivalently replaced without departing from the spirit and scope of the technical solutions of the present invention, and they should all be covered by the scope of the claims of the present invention.

[0072] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit them. Although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of the present invention can be modified or equivalently replaced without departing from the spirit and scope of the technical solutions of the present invention, and they should all be covered by the scope of the claims of the present invention.

Claims

1. An intelligent collaborative management method for data interaction information based on componentized architecture, characterized in that: include: According to business needs, the page modules and components are divided into first relationships; First, collaboratively manage the data between modules and components and divide the components into hierarchies; The first scenario of component interaction management is divided, and the first expansion adjustment is made to the public component functions.

2. The intelligent collaborative management method for data interaction information based on componentized architecture according to claim 1, characterized in that: The first relationship division of page modules and components includes combining various aspects of analysis and division, dividing the page into modules, and dividing the components according to the modules.

3. The intelligent collaborative management method for data interaction information based on componentized architecture according to claim 2, characterized in that: The dividing of components according to modules includes dividing components according to module responsibilities, and separating business components and public components.

4. The intelligent collaborative management method for data interaction information based on componentized architecture according to claim 3, characterized in that: The first collaborative management of data between modules and components includes determining a data interaction mode between modules and performing collaborative management according to the linkage interaction between modules.

5. The intelligent collaborative management method for data interaction information based on componentized architecture according to claim 3, characterized in that: The first collaborative management of data between modules and components also includes analyzing data interactions between components and collaboratively managing the components.

6. The intelligent collaborative management method for data interaction information based on componentized architecture according to claim 5, characterized in that: The dividing of the first scenario of component interaction management includes analyzing the application data interaction linkage usage scenario and dividing the first scenario of component hierarchical definition interaction management.

7. The intelligent collaborative management method for data interaction information based on componentized architecture according to claim 6, characterized in that: The first expansion adjustment of the common component function includes determining to extract the common component and performing the first expansion adjustment on the common component function.

8. A system using the method for intelligent collaborative management of data interaction information based on component architecture as claimed in any one of claims 1 to 7, characterized in that: Including relationship division module, collaborative management module, and scenario division module; The relationship division module is used to perform a first relationship division on page modules and components according to business requirements; The collaborative management module is used to perform a first collaborative management on data between modules and components and divide the components into hierarchies; The scenario division module is used to divide the first scenario of component interaction management and perform a first expansion adjustment on the public component function.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method for intelligent collaborative management of data interaction information based on a componentized architecture as described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method for intelligent collaborative management of data interaction information based on a componentized architecture described in any one of claims 1 to 7 are implemented.

Images