Industrial software adaptation method and system and electronic equipment

Abstract

The invention provides an industry software adaptation method and system and electronic equipment, and relates to the technical field of industrial software, the method comprises the following steps: through a dynamic metadata engine, analyzing according to metadata configuration of a target industry to obtain a field exclusive mode, service logic configuration, a storage mode and data operation logic configuration of target industry software; according to the field exclusive mode, the service logic configuration, the storage mode and the data operation logic configuration, respectively obtaining a front-end display layer, a server field logic layer and a field exclusive persistent layer of the target industry software; and according to the front-end display layer, the server domain logic layer and the domain exclusive persistent layer, obtaining an adaptive architecture of the target industry software. Full-stack linkage of the front end, the server side and the persistent layer of the multi-industry software is achieved through the dynamic metadata engine based on metadata configuration of the target industry, and the industry software adaptation efficiency and stability are remarkably improved.

Description

Technical Field

[0001] This invention relates to the field of industrial software technology, and more specifically, to an industry software adaptation method, system, and electronic device. Background Technology

[0002] In industrial software applications, the requirements for industrial software vary significantly across different industries (such as chemical and pharmaceutical). Therefore, the same software needs to be adapted before it can be applied to different industries. Currently, traditional industrial software development typically adopts a model of different software versions for different industries, implementing industry-specific functions within the same software through hard coding.

[0003] While hard-coded modes can meet the basic functional requirements of a single industry to a certain extent, they require modifications to the code layer of industrial software to meet the requirements of each industry when adapting products to multiple industries. This results in a long adaptation cycle and seriously affects the adaptation efficiency. In addition, code modifications can easily cause software compatibility issues, leading to the risk of production interruption. Summary of the Invention

[0004] The problem addressed by this invention is how to improve the adaptability and stability of industrial software across multiple industries.

[0005] To address the above problems, this invention provides an industry software adaptation method, system, and electronic device.

[0006] In a first aspect, the present invention provides an industry software adaptation method, comprising: The dynamic metadata engine parses the metadata configuration of the target industry to obtain the domain-specific mode, service logic configuration, storage mode, and data operation logic configuration of the target industry software. The front-end presentation layer of the target industry software is obtained by parsing and rendering according to the domain-specific mode. Logical adaptation is performed based on the service logic configuration to obtain the server-side domain logic layer of the target industry software. Based on the storage mode and the data operation logic configuration, a domain-specific persistence layer for the target industry software is obtained. The adaptation architecture of the target industry software is obtained based on the front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer.

[0007] Optionally, the step involves parsing the target industry's metadata configuration using a dynamic metadata engine to obtain the target industry's domain-specific mode, service logic configuration, storage mode, and data operation logic configuration, including: The domain requirements of the target industry are determined by using a dynamic metadata engine based on the metadata configuration of the target industry. Based on the requirements of the aforementioned domain, determine the domain-specific attributes of the target industry; Based on the domain-specific attributes combined with preset basic general attributes, the domain-specific mode of the target industry software is generated.

[0008] Optionally, the step involves parsing the target industry's metadata configuration using a dynamic metadata engine to obtain the target industry's domain-specific mode, service logic configuration, storage mode, and data operation logic configuration, including: The domain requirements of the target industry are determined by using a dynamic metadata engine based on the metadata configuration of the target industry. Based on the requirements of the aforementioned domain, determine the domain-specific attributes of the target industry; Based on the standard model fields and basic logic of the preset standard model, the basic model data of the target industry is determined; Based on the domain-specific attributes of the target industry, the basic model data is expanded with domain fields to obtain domain-specific model metadata for the target industry; The service logic configuration is obtained by mapping the domain-specific model metadata.

[0009] Optionally, the step involves parsing the target industry's metadata configuration using a dynamic metadata engine to obtain the target industry's domain-specific mode, service logic configuration, storage mode, and data operation logic configuration, including: The domain requirements of the target industry are determined by using a dynamic metadata engine based on the metadata configuration of the target industry. Based on the requirements of the aforementioned field, determine the data storage characteristics and data processing requirements of the target industry; Based on the preset general storage structure and combined with the data storage characteristics, the extended storage fields and association rules for the target industry are determined; Based on the extended storage field and the association rule, the storage mode of the target industry software is determined; The data operation logic configuration is obtained based on the storage mode and the data processing requirements.

[0010] Optionally, the step of parsing and rendering according to the domain-specific mode to obtain the front-end presentation layer of the target industry software includes: Based on the domain-specific mode, determine the component type definition, display attribute parameters, data binding rules, and industry-compliant rendering logic of the target industry software; Based on the component type, define and load industry-specific components; Configure the layout and style of the exclusive component according to the display attribute parameters, establish the association between the exclusive component and the server interface based on the data binding rules, and inject the industry compliance rendering logic into the exclusive component to obtain the configured exclusive component. The configured dedicated components are then adapted and rendered for the terminal to obtain the front-end presentation layer of the target industry software.

[0011] Optionally, the step of performing logical adaptation based on the service logic configuration to obtain the server-side domain logic layer of the target industry software includes: Based on the service logic configuration, extract the domain-specific business rules and general service interface definitions for the target industry; Based on a pre-defined standard service framework, load basic service logic; The domain-specific business rules are integrated into the basic service logic, and the server-side interface adapted to front-end calls is configured according to the general service interface definition to generate the server-side domain logic layer of the target industry software.

[0012] Optionally, the step of designing and configuring the domain-specific persistence layer of the target industry software based on the storage mode and the data operation logic configuration includes: Based on the storage mode, determine the standard table structure, extended table structure, and inter-table association rules for the target industry; Based on the standard table structure, the extended table structure, and the inter-table association rules, create a data storage table for the target industry; Based on the data operation logic configuration, determine the data read / write strategy, transaction processing mechanism, and data consistency verification rules for the target industry; By embedding the data read / write strategy, the transaction processing mechanism, and the data consistency verification rules into the operation logic of the data storage table, the domain-specific persistence layer of the target industry software is obtained.

[0013] Optionally, obtaining the adaptation architecture of the target industry software based on the front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer includes: The front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer are service orchestrated to obtain inter-layer call links and data flow paths; The dynamic metadata engine is used to perform consistency verification on the inter-layer call chain and the data flow path; Once the verification is successful, the front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer are encapsulated to generate the adaptation architecture for the target industry software.

[0014] Secondly, the present invention provides an industry software adaptation system, comprising: The metadata parsing unit is used to parse the target industry's metadata configuration through the dynamic metadata engine to obtain the target industry's domain-specific mode, service logic configuration, storage mode, and data operation logic configuration. The rendering unit is used to parse and render according to the domain-specific mode to obtain the front-end display layer of the target industry software. An adaptation unit is used to perform logical adaptation based on the service logic configuration to obtain the server-side domain logic layer of the target industry software. A configuration unit is used to design and configure the target industry software based on the storage mode and the data operation logic configuration to obtain the domain-specific persistence layer of the target industry software. An integration unit is used to obtain the adaptation architecture of the target industry software based on the front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer.

[0015] Thirdly, the present invention provides an electronic device, comprising: a processor and a memory, wherein the memory is used to store a computer program; When the computer program is loaded by the processor, it causes the processor to execute the industry software adaptation method described above.

[0016] The industry software adaptation method, system, and electronic device of this invention parses the target industry's metadata configuration using a dynamic metadata engine to obtain domain-specific modes, service logic configurations, storage modes, and data operation logic configurations. This avoids the tedious operation of modifying core code for different industries under traditional hard-coding methods. Leveraging the dynamic configuration characteristics of metadata, it quickly adapts to the specific needs of the target industry, such as risk management in the chemical industry or compliance requirements in the pharmaceutical industry, significantly shortening the adaptation cycle and reducing development costs. The front-end presentation layer is obtained through parsing and rendering based on the domain-specific mode, enabling front-end components to accurately match the scenario characteristics of the target industry while ensuring the compliance of the front-end display and multi-terminal adaptability, thus improving the user interaction experience. Based on the service logic... The configuration generates a server-side domain logic layer through logical adaptation. This layer achieves precise alignment between the server and the target industry's business rules by reusing standard logic and enhancing industry-specific logic, avoiding logical redundancy and system stability issues. A domain-specific persistence layer is designed based on storage patterns and data operation logic, enabling the construction of a storage structure tailored to the target industry's data characteristics. This ensures data storage consistency and traceability, meeting the core needs of industry data management. Finally, by integrating the front-end presentation layer, server-side domain logic layer, and domain-specific persistence layer to form an adaptation architecture, the full-stack linkage of the front-end, server, and persistence layers is achieved. This ensures that each layer collaboratively adapts to the target industry's needs, significantly improving the efficiency, stability, and scalability of industry software adaptation. Attached Figure Description

[0017] Figure 1 This is a flowchart illustrating the industry software adaptation method in an embodiment of the present invention. Figure 2 This is a flowchart illustrating the construction process of the domain-specific pattern in this embodiment of the invention. Figure 3 This is a schematic diagram of the parsing and rendering process based on the domain-specific mode in an embodiment of the present invention; Figure 4 This is a schematic diagram of the structure of the industry software adaptation system in an embodiment of the present invention. Detailed Implementation

[0018] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Although some embodiments of the present invention are shown in the drawings, it should be understood that the present invention can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present invention. It should be understood that the accompanying drawings and embodiments of the present invention are for illustrative purposes only and are not intended to limit the scope of protection of the present invention.

[0019] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.

[0020] The term "comprising" and its variations as used herein are open-ended, meaning "including but not limited to"; the term "based on" means "at least partially based on"; the term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments"; and the term "optionally" means "optional embodiments". Definitions of other terms will be given in the following description. It should be noted that the concepts of "first," "second," etc., mentioned in this invention are used only to distinguish different devices, modules, or units, and are not intended to limit the order of functions performed by these devices, modules, or units or their interdependencies.

[0021] It should be noted that the terms "a" and "a plurality of" used in this invention are illustrative rather than restrictive. Those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0022] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data used for analysis, data stored, data displayed, etc.) and signals involved in this application are all authorized by the user or fully authorized by all parties. The collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0023] Combination Figure 1 As shown in the figure, an industry software adaptation method provided by an embodiment of the present invention includes: The dynamic metadata engine parses the metadata configuration of the target industry to obtain the domain-specific mode, service logic configuration, storage mode, and data operation logic configuration of the target industry software.

[0024] Specifically, this invention uses a dynamic metadata engine as the execution entity, breaking through the technical bottleneck of strong coupling between industry and code in traditional software development. By parsing the metadata configuration of the target industry, it transforms abstract industry requirements into concrete configuration information that can directly drive the construction of each level of the software, such as domain-specific patterns and service logic configurations. The dynamic metadata engine can respond to different industry requirements without modifying the core software architecture. It establishes a mapping relationship between industry requirements and software implementation by using metadata as an intermediary between the target industry and industry software, providing standardized and scalable input for accurate adaptation at subsequent levels.

[0025] The front-end presentation layer of the target industry software is obtained by parsing and rendering according to the domain-specific mode.

[0026] Specifically, the parsing and rendering are based directly on domain-specific patterns. Unlike traditional front-end development where a single component can adapt to multiple industries, this approach uses domain-specific patterns to ensure that the selection, layout, and functionality of front-end components closely align with the target industry's scenario characteristics and interaction requirements. This eliminates the need for developers to manually write large amounts of industry-specific front-end code. Instead, the industry rules inherent in the domain-specific patterns automatically complete component matching and rendering logic configuration. This ensures a high degree of fit between the front-end display and the target industry's business scenario, while avoiding redundant development and development of front-end code during cross-industry adaptation, significantly improving front-end development efficiency and adaptation accuracy.

[0027] Logical adaptation is performed based on the service logic configuration to obtain the server-side domain logic layer of the target industry software.

[0028] Specifically, service logic configuration is used as the benchmark for logic adaptation. Through targeted parsing and adaptation of service logic configuration, precise matching between server-side logic and target industry business rules is achieved. In this process, the service logic configuration carries the target industry's exclusive business logic and process specifications. By interpreting it, the server can automatically integrate basic logic with industry-specific logic, achieving cross-industry logic adaptation without refactoring the core server architecture. This ensures rapid response of server-side logic to industry needs and improves the maintainability and scalability of the server system.

[0029] Based on the storage mode and the data operation logic configuration, a domain-specific persistence layer for the target industry software is designed and configured to obtain the desired layer.

[0030] Specifically, the design and configuration are based on both storage mode and data operation logic, enabling the data storage solution to precisely match the data characteristics and operational norms of the target industry, such as data types, relationships, and read / write frequencies. The storage mode clarifies the data storage structure that meets industry needs, while the data operation logic configuration defines core operational rules such as data read / write and transaction processing. The combination of these two aspects allows the persistence layer to achieve efficient storage, secure operation, and reliable management of industry-specific data. The configuration can be adjusted to adapt to the data needs of different industries, ensuring the integrity and traceability of industry data.

[0031] The adaptation architecture of the target industry software is obtained based on the front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer.

[0032] Specifically, by organically integrating the front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer, a three-layer collaborative target industry software adaptation architecture is constructed. This differs from the traditional software architecture where each layer is developed independently and lacks collaboration, achieving a high degree of collaboration and adaptation loop driven by metadata across all layers. During the integration process, each layer achieves data flow and functional linkage based on unified metadata-derived logic. Front-end interaction requirements can be accurately translated into data operation commands through server-side logic, and the data status of the persistence layer can be fed back to the front-end display in real time through the server, forming a complete chain. This ensures both the independence of functions at each software layer and achieves cross-layer collaborative adaptation capabilities, enabling the software to quickly respond to target industry needs as a whole.

[0033] The industry software adaptation method of this invention parses the target industry's metadata configuration using a dynamic metadata engine to obtain domain-specific modes, service logic configurations, storage modes, and data operation logic configurations. This avoids the tedious operation of modifying core code for different industries under traditional hard-coding methods. Leveraging the dynamic configuration characteristics of metadata, it quickly adapts to the specific needs of the target industry, such as risk management in the chemical industry or compliance requirements in the pharmaceutical industry, significantly shortening the adaptation cycle and reducing development costs. The front-end presentation layer is obtained through parsing and rendering based on the domain-specific mode, enabling front-end components to accurately match the scenario characteristics of the target industry, while ensuring the compliance of the front-end display and multi-terminal adaptability, thus improving the user interaction experience. Based on the service logic configuration... The logic adaptation generates a server-side domain logic layer, which achieves precise alignment between the server and the target industry's business rules through standard logic reuse and industry-specific logic enhancement, avoiding logic redundancy and system stability issues. Based on storage patterns and data operation logic configuration, a domain-specific persistence layer is designed, enabling the construction of a storage structure tailored to the target industry's data characteristics, ensuring data storage consistency and traceability, and meeting the core needs of industry data management. Finally, by integrating the front-end presentation layer, server-side domain logic layer, and domain-specific persistence layer to form an adaptation architecture, full-stack linkage between the front-end, server, and persistence layers is achieved, ensuring that each layer collaboratively adapts to the target industry's needs, significantly improving the efficiency, stability, and scalability of industry software adaptation.

[0034] Optionally, the step involves parsing the target industry's metadata configuration using a dynamic metadata engine to obtain the target industry's domain-specific mode, service logic configuration, storage mode, and data operation logic configuration, including: The domain requirements of the target industry are determined by using a dynamic metadata engine based on the metadata configuration of the target industry. Based on the requirements of the aforementioned domain, determine the domain-specific attributes of the target industry; Based on the domain-specific attributes combined with preset basic general attributes, the domain-specific mode of the target industry software is generated.

[0035] Specifically, firstly, the dynamic metadata engine identifies the core domain needs of the target industry by parsing the preset industry identifiers, compliance standard association information, and scenario keywords in the target industry's metadata configuration. For example, in the chemical industry, this might be high-frequency data monitoring and hazardous materials risk management requirements, or in the pharmaceutical industry, it might be GMP compliance forms and audit trail requirements. Secondly, based on the identified domain needs, domain-specific attributes are extracted from the metadata configuration. These attributes are extracted using mapping rules between domain needs and domain-specific attributes. For example, in the chemical industry, exclusive attributes such as reaction temperature thresholds, hazardous material levels, and DCS interface protocols are extracted; in the pharmaceutical industry, exclusive attributes such as cleanroom levels, raw material traceability IDs, and GMP audit rule IDs are extracted, ensuring that the attributes directly match the industry needs. Finally, using the JSON-formatted schema specification as the technical carrier, the extracted domain-specific attributes are structurally integrated with preset basic general attributes (including basic attributes such as field names and data types, display attributes such as component types and styles, and data attributes such as data sources and interface protocols). By defining a unified metadata field format and constraint rules, a domain-specific pattern containing industry-specific characteristics is generated, achieving an organic combination of general attribute reuse and domain attribute customization, fully covering all configuration information required for front-end rendering. In a preferred embodiment of the present invention, combined with Figure 2 As shown, the process first defines the requirements for extending metadata in JSON format. Then, it analyzes the domain requirements and selects specific domains (such as chemical, pharmaceutical, or other industries). For chemical industries, it adds domain attributes such as warning range; for pharmaceutical industries, it adds domain attributes such as GMP level; and for other industries, it adds corresponding domain attributes. After that, it integrates common basic attributes, including display attributes such as component type and style, basic attributes such as field name and type, data attributes such as data source and interface protocol, and domain attributes such as industry-specific fields. Based on this, it generates a customized schema specification, outputs a domain-specific schema, and finally applies it to the actual business system.

[0036] In this embodiment of the invention, the dynamic metadata-driven attribute extraction and fusion mechanism avoids the repetitive development of front-end components in traditional solutions, enabling domain-specific modes to directly support the dynamic rendering of industry-specific UIs. This not only improves the efficiency of multi-industry adaptation but also ensures the precise alignment of front-end display with industry compliance standards and guarantees the maintainability and scalability of metadata.

[0037] Optionally, the step involves parsing the target industry's metadata configuration using a dynamic metadata engine to obtain the target industry's domain-specific mode, service logic configuration, storage mode, and data operation logic configuration, including: The domain requirements of the target industry are determined by using a dynamic metadata engine based on the metadata configuration of the target industry. Based on the requirements of the aforementioned domain, determine the domain-specific attributes of the target industry; Based on the standard model fields and basic logic of the preset standard model, the basic model data of the target industry is determined; Based on the domain-specific attributes of the target industry, the basic model data is expanded with domain fields to obtain domain-specific model metadata for the target industry; The service logic configuration is obtained by mapping the domain-specific model metadata.

[0038] Specifically, the dynamic metadata engine first parses information such as industry identifiers and business scenario keywords in the target industry metadata configuration to accurately determine domain requirements; then, it extracts domain-specific attributes based on these requirements; next, it retrieves a preset standard model, which contains general business fields and basic processing logic, such as data validation and access control, to determine the basic model data; subsequently, it uses a field expansion algorithm to embed domain-specific attributes as extended fields into the basic model data, forming domain-specific model metadata. For example, based on a general equipment management model, it adds a hazardous materials level field for chemicals and a cleanroom level field for pharmaceuticals; finally, through model mapping technology, such as JSON Schema-based field mapping rules, it transforms the domain-specific model metadata into server-side executable service logic configuration. This configuration includes industry-specific business rules and general service interface definitions, such as over-temperature interlock logic for chemicals and batch traceability generation logic for pharmaceuticals, thereby achieving precise adaptation between server-side logic and target industry requirements. In a preferred embodiment of the present invention, when it is necessary to extend from the standard model to the chemical / pharmaceutical field, an inheritance and addition pattern is adopted to ensure the reuse of general logic and the enhancement of domain characteristics. First, for the inheritance of the standard model, the industry extension model automatically inherits all fields and basic logic of the standard model (such as batch number field, general data storage logic); for the addition of domain fields, exclusive fields are added according to industry needs (such as adding clean area level or audit ID for pharmaceuticals, and adding temperature threshold or hazardous material ID for chemicals); for the rule association configuration, domain compliance rules are bound to the extension fields (such as associating pharmaceutical fields with GMP verification rules, and chemical fields with hazardous material level determination rules); for the binding of equipment interfaces, the chemical model is associated with DCS / PLC equipment interfaces, and the pharmaceutical model is associated with LIMS interfaces.

[0039] In this embodiment of the invention, the combination of standard model reuse and domain field extension not only ensures the development efficiency of server-side logic, but also achieves the precise embedding of industry-specific business rules. This solves the problems of logic redundancy and insufficient customization when traditional server-side cross-industry adaptation is performed. At the same time, the automated generation method based on model mapping significantly reduces the error rate of manual coding and improves the accuracy and maintainability of server-side logic adaptation.

[0040] Optionally, the step involves parsing the target industry's metadata configuration using a dynamic metadata engine to obtain the target industry's domain-specific mode, service logic configuration, storage mode, and data operation logic configuration, including: The domain requirements of the target industry are determined by using a dynamic metadata engine based on the metadata configuration of the target industry. Based on the requirements of the aforementioned field, determine the data storage characteristics and data processing requirements of the target industry; Based on the preset general storage structure and combined with the data storage characteristics, the extended storage fields and association rules for the target industry are determined; Based on the extended storage field and the association rule, the storage mode of the target industry software is determined; The data operation logic configuration is obtained based on the storage mode and the data processing requirements.

[0041] Specifically, the dynamic metadata engine first parses information such as industry identifiers and business scenarios in the target industry metadata configuration to determine domain requirements; then, based on these requirements, it extracts data storage characteristics and data processing requirements; subsequently, it retrieves a preset general storage structure, combines data storage characteristics, and uses field extension and table association design techniques to determine extended storage fields and inter-table association rules, thereby generating a storage model; finally, based on the storage model and data processing requirements, it obtains the data operation logic configuration through rule mapping technology. This configuration includes data read / write strategies, transaction processing mechanisms, and consistency verification rules, achieving precise adaptation between the storage layer and the target industry's data management needs. In a preferred embodiment of the present invention, when the dynamic metadata engine parses its metadata configuration, it first determines the domain requirement as traceability and immutability of batch data through pharma industry identifiers and batch lifecycle management scenarios; then it extracts data storage characteristics (versioned storage, chained association) and data processing requirements (audit log generation, data anti-tampering verification); subsequently, it calls the general storage structure, adds extended storage fields such as batch version number and previous batch ID in combination with storage characteristics, and designs inter-table association rules for batch table, audit log table, and raw material traceability table to generate a storage mode; finally, based on the storage mode and processing requirements, it generates data operation logic configuration that includes rules such as automatically generating version number and audit log when batch data is written and verifying the integrity of data chained association when querying.

[0042] In this embodiment of the invention, by using the technical means of reusing general storage structures and extending industry-specific fields, the repetitive workload of storage layer development is reduced, and the high degree of fit between the storage solution and the data characteristics of the target industry is ensured. This solves the problems of low storage efficiency and non-standard data management when traditional storage layers are adapted across industries. At the same time, the automated generation method of data operation logic improves the scalability and operation and maintenance efficiency of the storage layer, and ensures the integrity and traceability of industry data.

[0043] Optionally, the step of parsing and rendering according to the domain-specific mode to obtain the front-end presentation layer of the target industry software includes: Based on the domain-specific mode, determine the component type definition, display attribute parameters, data binding rules, and industry-compliant rendering logic of the target industry software; Based on the component type, define and load industry-specific components; Configure the layout and style of the exclusive component according to the display attribute parameters, establish the association between the exclusive component and the server interface based on the data binding rules, and inject the industry compliance rendering logic into the exclusive component to obtain the configured exclusive component. The configured dedicated components are then adapted and rendered for the terminal to obtain the front-end presentation layer of the target industry software.

[0044] Specifically, firstly, based on JSON Schema parsing technology, the domain-specific schema is structured and parsed to extract component type definitions, display attribute parameters, data binding rules, and industry-compliant rendering logic, ensuring that the parsing results cover all dimensions of front-end rendering requirements. Secondly, a component library dynamic loading technology is adopted to call matching components from a pre-set industry-specific component library based on the parsed component type definitions, avoiding redundant loading of general components. Next, component configuration is completed through a CSS style engine and interface adaptation tools, that is, adjusting the component layout and visual style according to display attribute parameters, establishing the association between the component and the server interface based on data binding rules, and embedding industry-compliant rendering logic into the component interaction process using logic implantation technology to form a configured exclusive component. Finally, responsive rendering technology is used to automatically adjust the component resolution and layout structure according to the terminal type, call the front-end rendering engine to generate an HTML page, and finally obtain a front-end display layer that conforms to the target industry scenario. The entire process does not require manual writing of a large amount of customized code, realizing configuration-driven front-end adaptation. In a preferred embodiment of the present invention, combined with Figure 3 As shown, the schema is loaded according to the user's domain and terminal type, and metadata processing and parsing are performed. On the one hand, component type matching and initialization are completed. Based on the type field of the schema, domain-specific component libraries are matched and real-time data interfaces are bound (such as rule processing logic injection, HTTP protocol calling programs for medical data, etc.). On the other hand, field attributes, compliance rules and page information are parsed and component instances are initialized (such as range, time range). Subsequently, multi-terminal adaptation rendering is performed, the rendering engine is called to generate HTML pages, the component layout is adjusted according to terminalType, and finally the front-end presentation layer of the target industry software is obtained.

[0045] In this embodiment of the invention, by combining configuration drivers with technical tools, the cost of front-end adaptation is significantly reduced, ensuring that front-end components are highly compatible with industry scenarios and compliance standards. At the same time, the real-time performance and accuracy of front-end display are improved through the automated configuration of data binding and compliance logic, further ensuring operational efficiency and compliance in industrial scenarios.

[0046] Optionally, the step of performing logical adaptation based on the service logic configuration to obtain the server-side domain logic layer of the target industry software includes: Based on the service logic configuration, extract the domain-specific business rules and general service interface definitions for the target industry; Based on a pre-defined standard service framework, load basic service logic; The domain-specific business rules are integrated into the basic service logic, and the server-side interface adapted to front-end calls is configured according to the general service interface definition to generate the server-side domain logic layer of the target industry software.

[0047] Specifically, firstly, configuration parsing technology is used to extract the target industry's domain-specific business rules and general service interface definitions from the service logic configuration. The domain-specific business rules cover over-temperature interlock rules for chemicals and batch traceability rules for pharmaceuticals. The general service interface definitions include interface protocols, parameter formats, and return value specifications. Next, service framework loading technology is used to load basic service logic based on a preset standard service framework. This logic includes modules for general data validation, access control, and log management. Simultaneously, a standard service layer is loaded to implement the general logic, which includes basic operations for adding, modifying, and querying data, as well as general field validation. This standard service layer provides abstract methods for industry extension. Then, through business rule injection technology, the domain-specific business rules are integrated into the basic service logic in a plug-in format. Over-temperature interlock rules for chemicals are embedded into the equipment monitoring service class using custom annotations. Batch traceability rules for pharmaceuticals are integrated into the data operation process through AOP aspect technology. The industry service layer inherits from the standard service class, overrides abstract methods to implement domain-specific logic, and can also supplement new logic through "enhancement methods," such as GMP for pharmaceuticals. Audit log generation and chemical reaction alert triggering are implemented. Based on dynamic rule loading technology, compliance rules are retrieved from a dynamic metadata engine. These rules include pharmaceutical GMP verification rules and chemical hazard level determination rules, which are executed in real-time without modifying service code. A control layer isolation architecture with a standard entry point and industry entry points is adopted. The standard control layer provides a general interface to handle cross-industry common requests, while the industry control layer configures an independent entry point for each domain and divides interface paths according to domain and scenario. For example, the pharmaceutical domain interface paths are: / api / pharma / batch / save, / api / pharma / gmp / audit, / api / pharma / trace / query; and the chemical domain interface paths are: / api / chemical / reactor / save, / api / chemical / alarm / query, / api / chemical / hazard / manage. Simultaneously, routing rules are configured through Spring Cloud Gateway to distribute requests to the corresponding industry control layer based on the X-Industry field in the request header, supporting 15+ [entities / entities]. The system operates in parallel across sub-domains with routing and forwarding latency ≤50ms. Finally, based on the general service interface definition, the system uses an interface configuration tool to configure the server-side interface adapted to the front-end call, specifying the HTTP method, path, request parameters, and response format of the interface. Swagger UI can be used as the interface configuration tool. Ultimately, the system generates the server-side domain logic layer of the target industry software. The entire process achieves precise alignment between the server-side logic and the target industry requirements through modular integration and configuration management, without requiring a reconstruction of the core server-side architecture.

[0048] In this embodiment of the invention, by reusing the standard service framework and integrating business rules into a plug-in manner, the development efficiency and system stability of the server-side logic are ensured, the precise implementation of industry-specific business rules is achieved, and the standardized configuration of general service interfaces also improves the efficiency of front-end and back-end collaborative development, ensuring that the server-side logic can quickly respond to the interactive needs of the front-end presentation layer.

[0049] Optionally, the step of designing and configuring the domain-specific persistence layer of the target industry software based on the storage mode and the data operation logic configuration includes: Based on the storage mode, determine the standard table structure, extended table structure, and inter-table association rules for the target industry; Based on the standard table structure, the extended table structure, and the inter-table association rules, create a data storage table for the target industry; Based on the data operation logic configuration, determine the data read / write strategy, transaction processing mechanism, and data consistency verification rules for the target industry; By embedding the data read / write strategy, the transaction processing mechanism, and the data consistency verification rules into the operation logic of the data storage table, the domain-specific persistence layer of the target industry software is obtained.

[0050] Specifically, firstly, based on the storage model, metadata parsing technology is used to determine the standard table structure, extended table structure, and inter-table association rules for the target industry. A multi-table storage model is designed based on the model-table correspondence principle, which corely includes two types of table structures: standard tables and industry extended tables. Standard tables store cross-domain common fields (such as production batch number, equipment number, creation time, and whether it has been deleted), and all industries share the same standard table structure to ensure consistency of common data. Industry extended tables store domain-specific fields (such as cleanroom level in pharmaceuticals and reaction temperature thresholds in chemicals), with table names in the format of standard table name_industry identifier_ext, and are associated with the standard table through the main table ID. Then, [further steps are taken]. Using database modeling tools, data storage tables for the target industry are created based on the established standard table structure, extended table structure, and inter-table relationship rules. The data type, length, and constraints of each field are defined. Then, based on the configured data operation logic, and considering the data characteristics of the chemical and pharmaceutical fields (high-frequency time series, compliance traceability), optimized database query and update logic is determined using configuration parsing technology. This clarifies the data read / write strategy and transaction processing mechanism: the database query adopts a "standard table left join extended table + traceability table join" pattern, supporting the extension of only a portion of the standard model without modifying the existing query logic. Simultaneously, the industry field is used to filter data by industry. According to the data, database updates follow a standard table → extended table update order. Atomicity of transactions is guaranteed through Spring declarative transactions or a distributed transaction manager (such as Seata). Specifically, when saving pharmaceutical batches, a transaction with isolation level REPEATABLE READ and a timeout of 90 seconds is first initiated. The data is then inserted sequentially into the standard table `production_standard` (batch number, equipment ID, and other common fields) and the extended table `production_pharma_ext` (cleanliness zone level, raw material traceability ID, and other pharmaceutical fields). If any step fails, a rollback is performed; if all steps succeed, the transaction is committed. When saving chemical reaction data, a transaction with a timeout of 60 seconds is initiated to accommodate high-frequency data writing. The data is then inserted sequentially into the standard table `production_standard` (batch number, reactor equipment ID) and the extended table `production_chemical_ext` (reaction temperature, pH value, hazardous material ID). If the amount of time-series data is too large, a batch commit + transaction compensation mechanism is used. Finally, database triggers, stored procedures, or ORM framework interceptor technology are used to embed the determined data read / write strategy, transaction processing mechanism, and data consistency verification rules into the operation logic of the data storage table, resulting in the domain-specific persistence layer of the target industry software. In a preferred embodiment of the present invention, the standard table in the medical field is shown in Table 1, and the extended table is shown in Table 2.

[0051] Table 1. Common Fields in Standard Tables for the Medical Field

[0052] Table 2. Specific fields for the medical field extension table

[0053] In this embodiment of the invention, by reusing storage structures and automatically embedding operation rules, the complexity and workload of storage layer development are reduced, while ensuring that data storage and operation comply with the data characteristics and management standards of the target industry.

[0054] Optionally, obtaining the adaptation architecture of the target industry software based on the front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer includes: The front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer are service orchestrated to obtain inter-layer call links and data flow paths; The dynamic metadata engine is used to perform consistency verification on the inter-layer call chain and the data flow path; Once the verification is successful, the front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer are encapsulated to generate the adaptation architecture for the target industry software.

[0055] Specifically, firstly, service orchestration technology is used to collaboratively integrate the front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer: For the front-end and server, based on the data binding rules of the front-end components and the server-side interface definitions, a call chain is constructed for front-end component requests to server-side interface responses; for the server and persistence layer, combining the data operation requirements of the server-side business logic with the table structure and operation rules of the persistence layer, the data flow path for server-side data instructions to store / query data in the persistence layer is planned, ensuring that the links and paths between the three layers cover all business scenarios. Secondly, through the validation module of the dynamic metadata engine, a rule matching algorithm is used to perform consistency verification on the inter-layer call chain and data flow path: verifying the consistency of the format of front-end request parameters and server-side interface parameters, the compatibility of server-side data operation instructions and persistence layer table structures, and the compliance of the entire chain. If the verification fails, specific mismatch items are returned, supporting targeted adjustments. Finally, using architecture encapsulation technology, the verified three-layer modules and inter-layer interaction rules are encapsulated into independent adaptive architecture units. During the encapsulation process, the configuration entry of the dynamic metadata engine is embedded, which supports rapid updates of the architecture through metadata adjustments when industry requirements change, without the need to reconstruct the core modules, ultimately forming a target industry software adaptation architecture that can be directly deployed.

[0056] In this embodiment of the invention, a standardized service orchestration and verification mechanism ensures the coordinated operation of the three-layer modules. The verification function of the dynamic metadata engine reduces the error rate of architecture integration and improves the stability of the adapted architecture. At the same time, the reserved metadata configuration entry provides flexible adjustment space for subsequent cross-industry expansion or demand iteration, further reducing the architecture maintenance cost.

[0057] Combination Figure 4 As shown, another embodiment of the present invention provides an industry software adaptation system, comprising: The metadata parsing unit is used to parse the target industry's metadata configuration through the dynamic metadata engine to obtain the target industry's domain-specific mode, service logic configuration, storage mode, and data operation logic configuration. The rendering unit is used to parse and render according to the domain-specific mode to obtain the front-end display layer of the target industry software. An adaptation unit is used to perform logical adaptation based on the service logic configuration to obtain the server-side domain logic layer of the target industry software. A configuration unit is used to design and configure the target industry software based on the storage mode and the data operation logic configuration to obtain the domain-specific persistence layer of the target industry software. An integration unit is used to obtain the adaptation architecture of the target industry software based on the front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer.

[0058] The industry software adaptation system of the present invention has the same advantages over the prior art as the above-mentioned industry software adaptation method, and will not be repeated here.

[0059] Another embodiment of the present invention provides an electronic device, comprising: a processor and a memory, wherein the memory is used to store a computer program; When the computer program is loaded by the processor, it causes the processor to execute the industry software adaptation method described above.

[0060] The electronic device of the present invention has the same advantages over the prior art as the aforementioned industry software adaptation method over the prior art, and will not be repeated here.

[0061] While the present invention has been disclosed above, its scope of protection is not limited thereto. Those skilled in the art can make various changes and modifications without departing from the spirit and scope of the present invention, and all such changes and modifications will fall within the scope of protection of the present invention.

Claims

1. An industry software adaptation method, characterized in that, include: The dynamic metadata engine parses the metadata configuration of the target industry to obtain the domain-specific mode, service logic configuration, storage mode, and data operation logic configuration of the target industry software. The front-end presentation layer of the target industry software is obtained by parsing and rendering according to the domain-specific mode. Logical adaptation is performed based on the service logic configuration to obtain the server-side domain logic layer of the target industry software. Based on the storage mode and the data operation logic configuration, a domain-specific persistence layer for the target industry software is obtained. The adaptation architecture of the target industry software is obtained based on the front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer.

2. The industry software adaptation method according to claim 1, characterized in that, The process involves using a dynamic metadata engine to parse the target industry's metadata configuration, thereby obtaining the target industry's domain-specific mode, service logic configuration, storage mode, and data operation logic configuration, including: The domain requirements of the target industry are determined by using a dynamic metadata engine based on the metadata configuration of the target industry. Based on the requirements of the aforementioned domain, determine the domain-specific attributes of the target industry; Based on the domain-specific attributes combined with preset basic general attributes, the domain-specific mode of the target industry software is generated.

3. The industry software adaptation method according to claim 1, characterized in that, The process involves using a dynamic metadata engine to parse the target industry's metadata configuration, thereby obtaining the target industry's domain-specific mode, service logic configuration, storage mode, and data operation logic configuration, including: The domain requirements of the target industry are determined by using a dynamic metadata engine based on the metadata configuration of the target industry. Based on the requirements of the aforementioned domain, determine the domain-specific attributes of the target industry; Based on the standard model fields and basic logic of the preset standard model, the basic model data of the target industry is determined; Based on the domain-specific attributes of the target industry, the basic model data is expanded with domain fields to obtain domain-specific model metadata for the target industry; The service logic configuration is obtained by mapping the domain-specific model metadata.

4. The industry software adaptation method according to claim 1, characterized in that, The process involves using a dynamic metadata engine to parse the target industry's metadata configuration, thereby obtaining the target industry's domain-specific mode, service logic configuration, storage mode, and data operation logic configuration, including: The domain requirements of the target industry are determined by using a dynamic metadata engine based on the metadata configuration of the target industry. Based on the requirements of the aforementioned field, determine the data storage characteristics and data processing requirements of the target industry; Based on the preset general storage structure and combined with the data storage characteristics, the extended storage fields and association rules for the target industry are determined; Based on the extended storage field and the association rule, the storage mode of the target industry software is determined; The data operation logic configuration is obtained based on the storage mode and the data processing requirements.

5. The industry software adaptation method according to claim 1, characterized in that, The step of parsing and rendering according to the domain-specific pattern to obtain the front-end presentation layer of the target industry software includes: Based on the domain-specific mode, determine the component type definition, display attribute parameters, data binding rules, and industry-compliant rendering logic of the target industry software; Based on the component type, define and load industry-specific components; Configure the layout and style of the exclusive component according to the display attribute parameters, establish the association between the exclusive component and the server interface based on the data binding rules, and inject the industry compliance rendering logic into the exclusive component to obtain the configured exclusive component. The configured dedicated components are then adapted and rendered for the terminal to obtain the front-end presentation layer of the target industry software.

6. The industry software adaptation method according to claim 1, characterized in that, The step of performing logical adaptation based on the service logic configuration to obtain the server-side domain logic layer of the target industry software includes: Based on the service logic configuration, extract the domain-specific business rules and general service interface definitions for the target industry; Based on a pre-defined standard service framework, load basic service logic; The domain-specific business rules are integrated into the basic service logic, and the server-side interface adapted to front-end calls is configured according to the general service interface definition to generate the server-side domain logic layer of the target industry software.

7. The industry software adaptation method according to claim 1, characterized in that, The process of designing and configuring the domain-specific persistence layer of the target industry software based on the storage mode and the data operation logic configuration includes: Based on the storage mode, determine the standard table structure, extended table structure, and inter-table association rules for the target industry; Based on the standard table structure, the extended table structure, and the inter-table association rules, create a data storage table for the target industry; Based on the data operation logic configuration, determine the data read / write strategy, transaction processing mechanism, and data consistency verification rules for the target industry; By embedding the data read / write strategy, the transaction processing mechanism, and the data consistency verification rules into the operation logic of the data storage table, the domain-specific persistence layer of the target industry software is obtained.

8. The industry software adaptation method according to claim 1, characterized in that, The step of obtaining the adaptation architecture of the target industry software based on the front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer includes: The front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer are service orchestrated to obtain inter-layer call links and data flow paths; The dynamic metadata engine is used to perform consistency verification on the inter-layer call chain and the data flow path; Once the verification is successful, the front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer are encapsulated to generate the adaptation architecture for the target industry software.

9. An industry software adaptation system, characterized in that, include: The metadata parsing unit is used to parse the target industry's metadata configuration through the dynamic metadata engine to obtain the target industry's domain-specific mode, service logic configuration, storage mode, and data operation logic configuration. The rendering unit is used to parse and render according to the domain-specific mode to obtain the front-end display layer of the target industry software. An adaptation unit is used to perform logical adaptation based on the service logic configuration to obtain the server-side domain logic layer of the target industry software. A configuration unit is used to design and configure the target industry software based on the storage mode and the data operation logic configuration to obtain the domain-specific persistence layer of the target industry software. An integration unit is used to obtain the adaptation architecture of the target industry software based on the front-end presentation layer, the server-side domain logic layer, and the domain-specific persistence layer.

10. An electronic device, characterized in that, include: Processor and memory, the memory being used to store computer programs; When the computer program is loaded by the processor, it causes the processor to execute the industry software adaptation method as described in any one of claims 1-8.

Images