A method and system for developing custom software through CAE simulation of APPs

Abstract

The application discloses a kind of methods and systems for developing custom software by CAE simulation APP, belong to software development technical field.The method includes: determining the parameters required by design engineer in each simulation App in target industry, to generate the part unit corresponding to each simulation App;Using test case, the correctness of the metadata in each simulation App corresponding part unit is checked, to build the part unit library corresponding to the target industry;Using the functional requirements of industry-specific software and part unit library, part unit screening is carried out to combine part units;The combined part unit is packed as industry-specific software.The application can reduce the development workload and cost (i.e. manpower and time) of industry-specific software, the development speed of industry-specific software is fast, the efficiency of developing industry software is high, and the data transmission and interaction between each simulation App in the development process of industry-specific software are guaranteed.

Description

Technical Field

[0001] This invention belongs to the field of software development technology, and in particular relates to a method and system for developing customized software through CAE simulation APP. Background Technology

[0002] CAE (Computer Aided Engineering) technology is playing an increasingly important role in industry. In industries such as aerospace, transportation, energy and chemical engineering, and power electronics, CAE simulation is gradually replacing physical testing and becoming a major method and means of verifying designs.

[0003] Existing CAE simulation software includes general-purpose CAE software, industry-specific CAE software, and simulation applications. General-purpose CAE software contains various models, functions, and numerical calculations for solving problems in different industries and fields. Therefore, general-purpose CAE software is becoming increasingly complex and cumbersome to use, requiring a very high level of technical expertise from simulation engineers.

[0004] Industry-specific CAE software only includes simulation models and functions used in a specific industry or field. It is only applicable to the needs of a specific industry or field, has a single function, is easy to use, and is more in line with the usage habits of industry engineers. However, there are many industries, the development workload is huge, and it is not flexible enough.

[0005] Existing simulation apps, or "application-based" simulation software, allow design engineers to focus on product design parameters rather than simulation settings and operating software. Their development has been rapid, with tens of thousands, even hundreds of thousands, of simulation apps available for different physical models. However, current simulation apps are still merely highly customized and packaged versions of CAE simulation software—simplified "CAE" software. They lack data transmission and interaction between different simulation apps, have limited functionality, and their data is closed. Summary of the Invention

[0006] One of the objectives of this invention is to provide a method for developing customized software using CAE simulation apps. This method can reduce the workload and cost (i.e., manpower and time) of developing industry-specific software, accelerate the development speed of industry-specific software, increase the efficiency of developing industry-specific software, and ensure data transmission and interaction between various simulation apps during the development process of industry-specific software.

[0007] The second objective of this invention is to provide a system for developing customized software through CAE simulation APP.

[0008] To achieve one of the above objectives, the present invention employs the following technical solution:

[0009] A method for developing custom software using a CAE simulation app, the method comprising the following steps:

[0010] Step S1: Determine the parameters required by the design engineers in each simulation app in the target industry to generate the part unit corresponding to each simulation app;

[0011] Step S2: Using test cases, perform a correctness check on the metadata in the part unit corresponding to each simulation App in order to build the part unit library corresponding to the target industry;

[0012] Step S3: Utilize the functional requirements and component library of industry-specific software to filter component units and combine them.

[0013] Step S4: Package the assembled part units into industry-specific software.

[0014] Furthermore, in step S1, the specific process of determining the parameters required by design engineers in each simulation app within the target industry includes:

[0015] Step S111: Extract input parameters for each simulation app in the target industry;

[0016] Step S112: Identify the extracted input parameters to determine the parameters required by the design engineer in each simulation application;

[0017] In step S112, the parameters required by the design engineer include geometric parameters, process parameters, boundary conditions, and post-processing requirements.

[0018] Furthermore, in step S1, the specific process of generating the part unit corresponding to each simulation App includes:

[0019] Step S121: Use the parameters required by the design engineer in each simulation app as the user interaction interface;

[0020] Step S122: Standardize the input and output interfaces of each simulation application;

[0021] Step S123: Using the simulation purpose of each simulation app, determine the metadata of the part unit corresponding to each simulation app;

[0022] In step S123, the metadata includes a simulation function description, a parameter mapping table between the parameters required by the design engineer and the parameters of the simulation application, and the dependencies between various part units;

[0023] Step S124: Using the user interaction interface, the standardized input / output interface, and the metadata corresponding to each simulation App, the simulation App is converted into its corresponding part unit through scripts or automated tools.

[0024] Furthermore, in step S3, the specific process of screening part units includes:

[0025] Step S311: Decompose the functional requirements of the industry-specific software to determine the sub-tasks corresponding to each functional requirement;

[0026] Step S312: Using the keywords of each functional requirement, perform keyword matching between each subtask and the part unit library to determine the part unit that meets the functional requirements of each subtask.

[0027] Step S313: Perform metadata filtering on the part units that meet the functional requirements of each subtask.

[0028] Furthermore, in step S3, the specific process of assembling the component units includes:

[0029] Step S321: Using the connection relationships between the filtered component units, generate a component unit combination logic diagram to determine the input-output dependencies between component units;

[0030] Step S322: Perform consistency checks and adjustments on the parameters of the part units with input-output dependencies in sequence.

[0031] To achieve the second objective mentioned above, the present invention employs the following technical solution:

[0032] A system for developing custom software using a CAE simulation app, the system comprising:

[0033] The generation module is used to determine the parameters required by the design engineers in each simulation app in the target industry, so as to generate the part unit corresponding to each simulation app;

[0034] The inspection module is used to perform correctness checks on the metadata in the part unit corresponding to each simulation App using test cases, so as to build the part unit library corresponding to the target industry;

[0035] The filtering module is used to filter parts units based on the functional requirements of industry-specific software and the parts unit library, so as to combine parts units.

[0036] The packaging module is used to package the assembled part units into industry-specific software.

[0037] Furthermore, the generation module includes:

[0038] The extraction submodule is used to extract input parameters for each simulation app in the target industry;

[0039] The identification submodule is used to identify the extracted input parameters in order to determine the parameters required by the design engineer in each simulation application;

[0040] The parameters required by the design engineer include geometric parameters, process parameters, boundary conditions, and post-processing requirements.

[0041] Furthermore, the generation module also includes:

[0042] As a submodule, it is used to provide the parameters required by the design engineers in each simulation app as the user interaction interface;

[0043] The standardization processing submodule is used to standardize the input and output interfaces of each simulation application.

[0044] The determination submodule is used to determine the metadata of the part unit corresponding to each simulation app by utilizing the simulation purpose of each simulation app;

[0045] The metadata includes a simulation function description, a parameter mapping table between the parameters required by the design engineer and the parameters of the simulation app, and the dependencies between various part units.

[0046] The conversion submodule is used to convert the simulation app into its corresponding part unit by using the user interaction interface, the standardized input / output interface, and the metadata of the part unit corresponding to each simulation app, through scripts or automated tools.

[0047] Furthermore, the filtering module includes:

[0048] Decompose submodules, which are used to decompose the functional requirements of industry-specific software to determine the subtasks corresponding to each functional requirement;

[0049] The keyword matching submodule is used to match the keywords of each functional requirement with the part unit library to determine the part unit that meets the functional requirements of each subtask.

[0050] The filtering submodule is used to filter metadata for part units that meet the functional requirements of each subtask.

[0051] Furthermore, the filtering module also includes:

[0052] The generation submodule is used to generate a component unit combinational logic diagram by utilizing the connection relationships between the filtered component units, so as to determine the input-output dependencies between component units.

[0053] The adjustment submodule is used to sequentially perform consistency checks and adjustments on the parameters of part units with input-output dependencies.

[0054] In summary, the solution proposed in this invention has the following technical effects:

[0055] This invention generates part units corresponding to each simulation app based on the parameters required by design engineers in each simulation app within the target industry. It then uses the metadata of these part units to check for correctness, retaining only qualified part units for each simulation app. This process removes irrational (i.e., incomplete or conflicting metadata) part units from the same industry within the part unit library. This reduces the computational load of part unit selection and combination, lowers the development workload and cost (i.e., manpower and time) of industry-specific software, accelerates the development speed of industry-specific software, significantly improves the efficiency of industry software development, and ensures data transmission and interaction between various simulation apps during the development process of industry-specific software. Attached Figure Description

[0056] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0057] Figure 1 This is a schematic diagram of a method for developing customized software using a CAE simulation app according to an embodiment of the present invention. Detailed Implementation

[0058] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0059] This embodiment provides a method for developing customized software using a CAE simulation application, such as... Figure 1 As shown, the method includes the following steps:

[0060] Step S1: Determine the parameters required by the design engineers in each simulation app in the target industry to generate the corresponding part unit for each simulation app.

[0061] This embodiment utilizes general-purpose simulation software, such as Comsol and Simdroid, to provide tools for no-code / low-code app development. The simulation process is encapsulated to quickly generate a large number of simulation apps for different industries and add them to a simulation app library. For example, simulation apps for the automotive industry include suspension mechanics simulation apps, suspension vibration modal simulation apps, wheel hub statics simulation apps, and tire dynamics apps developed using structural mechanics simulation software.

[0062] In this embodiment, each industry corresponds to at least one simulation application. The input parameters for each simulation application include parameters required by the design engineer and parameters required by the simulation engineer. Parameters required by the design engineer include geometric parameters (such as dimensions and shape), process parameters (such as temperature and pressure), boundary conditions, and post-processing requirement parameters (post-processing requirement parameters typically refer to a series of parameter settings or configurations required to complete a specific post-processing task in data analysis, signal processing, or other engineering computation fields, such as statistical indicators). Parameters required by the simulation engineer include mesh generation algorithm parameters, solver setting parameters, and numerical computation detail parameters.

[0063] This embodiment can use a rule engine or machine learning model to determine the parameters required by the design engineer in the input parameters of the simulation app.

[0064] In summary, the specific process for determining the parameters required by design engineers in each simulation app within the target industry, as described in this embodiment, includes:

[0065] Step S111: Extract input parameters for each simulation app in the target industry;

[0066] Step S112: Identify the extracted input parameters to determine the parameters required by the design engineer in each simulation application.

[0067] This embodiment completely hides the parameters needed by simulation engineers in the simulation app, retaining only the parameters needed by design engineers as the user interaction interface. The input and output interfaces of the simulation app are standardized (e.g., JSON format) to ensure compatibility with other part units and facilitate encapsulation. The specific process of generating the part unit corresponding to each simulation app includes:

[0068] Step S121: Use the parameters required by the design engineer in each simulation app as the user interaction interface;

[0069] Step S122: Standardize the input and output interfaces of each simulation application;

[0070] Step S123: Using the simulation purpose of each simulation app, determine the metadata of the part unit corresponding to each simulation app;

[0071] The metadata in this embodiment includes simulation function descriptions (referring to the simulation purpose of the part unit, such as heat conduction analysis and stress analysis), parameter mapping tables between the parameters required by the design engineer and the parameters of the simulation application (referring to the correspondence between the parameters required by the design engineer and the parameters of the simulation application), and dependencies between various part units (i.e., the association between part units, such as geometric topology connections and physical field coupling).

[0072] Step S124: Using the user interaction interface, the standardized input / output interface, and the metadata of the part unit corresponding to each simulation App, the simulation App is converted into its corresponding part unit through scripts or automated tools.

[0073] Step S2: Use test cases to check the correctness of the metadata in the part unit corresponding to each simulation App in order to build the part unit library corresponding to the target industry.

[0074] This embodiment verifies the consistency between the output results and the simulation application by running independent test cases of the part unit, that is, checking the correctness of the metadata of the part unit (i.e., whether the metadata is complete and conflict-free).

[0075] This embodiment stores component units by category, such as by industry (e.g., aerospace, energy and chemical) and physical field (e.g., thermodynamics, fluid mechanics), and maintains a version number for each component unit, recording modification history (e.g., parameter adjustment, algorithm optimization).

[0076] Step S3: Utilize the functional requirements and component library of industry-specific software to screen component units and combine them.

[0077] This embodiment decomposes the functional requirements of industry-specific software (such as the thermal-structural coupling analysis of a certain automotive component) into multiple sub-tasks (such as heat conduction analysis and stress analysis). Part elements that meet the requirements of the sub-tasks are selected from the part element library through keyword matching (such as heat conduction and stress) and metadata filtering (such as industry tags and physics field tags).

[0078] In summary, the specific process of selecting part units in this embodiment includes:

[0079] Step S311: Decompose the functional requirements of the industry-specific software to determine the sub-tasks corresponding to each functional requirement;

[0080] Step S312: Using the keywords of each functional requirement, perform keyword matching between each subtask and the part unit library to determine the part unit that meets the functional requirements of each subtask.

[0081] Step S313: Perform metadata filtering on the part units that meet the functional requirements of each subtask.

[0082] This embodiment generates a component unit combination logic diagram (such as a flowchart or UML diagram) by using the connection relationships between component units (such as data flow direction and physical field coupling rules) to determine the input-output dependencies of each component unit.

[0083] Check for parameter conflicts between connected component units (i.e., consistency checks, such as inconsistent boundary conditions or units). Then, adjust the parameters (such as unit conversion and boundary condition interpolation) using an automatic calibration tool.

[0084] In summary, the specific process of assembling the component units in this embodiment includes:

[0085] Step S321: Using the connection relationships between the filtered component units, generate a component unit combination logic diagram to determine the input-output dependencies between component units;

[0086] Step S322: Perform consistency checks and adjustments on the parameters of the part units with input-output dependencies in sequence.

[0087] For example, there are input-output dependencies such as geometry and force relationships between the "part unit corresponding to the wheel hub statics simulation APP" and the "part unit corresponding to the tire dynamics simulation APP". The parameters of these two part units are sequentially checked and adjusted for consistency to meet the requirements of data stream transmission.

[0088] Step S4: Package the assembled part units into industry-specific software.

[0089] The industry-specific software in this embodiment includes a user interface (UI) that displays only the parameters needed by the design engineer and hides the parameters needed by the engineer, i.e., simulation details), a core logic module (used to call the standardized interface of the part unit and perform simulation according to combinational logic), and a data management module (used to store simulation results and support visualization, such as cloud maps and statistical reports).

[0090] This embodiment accelerates repetitive calculations (such as caching simulation results with the same parameters) through caching technology. It also parallelizes independent calculation tasks for multiple component elements (such as parallelizing heat conduction and stress analysis).

[0091] For example, by using scripts, the assembled component units can be packaged sequentially to form a dedicated simulation software for automotive chassis systems. This dedicated simulation software for automotive chassis systems covers the functions of all the component units used and can simulate the chassis system.

[0092] This embodiment generates part units corresponding to each simulation app based on the parameters required by the design engineers in each simulation app in the target industry. It uses the correctness check of the metadata of the part units to retain the part units corresponding to qualified simulation apps, and removes unreasonable part units (i.e., incomplete or conflicting metadata) in the same industry from the part unit library. This reduces the amount of calculation required for part unit screening and combination, reduces the development workload and cost (i.e. manpower and time) of industry-specific software, accelerates the development speed of industry-specific software, greatly improves the efficiency of developing industry-specific software, and ensures the data transmission and interaction between various simulation apps during the development process of industry-specific software.

[0093] The above embodiments can be implemented using the technical solutions given in the following embodiments:

[0094] A system for developing custom software using a CAE simulation app, the system comprising:

[0095] The generation module is used to determine the parameters required by the design engineers in each simulation app in the target industry, so as to generate the part unit corresponding to each simulation app;

[0096] The inspection module is used to perform correctness checks on the metadata in the part unit corresponding to each simulation App using test cases, so as to build the part unit library corresponding to the target industry;

[0097] The filtering module is used to filter parts units based on the functional requirements of industry-specific software and the parts unit library, so as to combine parts units.

[0098] The packaging module is used to package the assembled part units into industry-specific software.

[0099] Furthermore, the generation module includes:

[0100] The extraction submodule is used to extract input parameters for each simulation app in the target industry;

[0101] The identification submodule is used to identify the extracted input parameters in order to determine the parameters required by the design engineer in each simulation application;

[0102] The parameters required by the design engineer include geometric parameters, process parameters, boundary conditions, and post-processing requirements.

[0103] Furthermore, the generation module also includes:

[0104] As a submodule, it is used to provide the parameters required by the design engineers in each simulation app as the user interaction interface;

[0105] The standardization processing submodule is used to standardize the input and output interfaces of each simulation application.

[0106] The determination submodule is used to determine the metadata of the part unit corresponding to each simulation app by utilizing the simulation purpose of each simulation app;

[0107] The metadata includes a simulation function description, a parameter mapping table between the parameters required by the design engineer and the parameters of the simulation app, and the dependencies between various part units.

[0108] The conversion submodule is used to convert the simulation app into its corresponding part unit by using the user interaction interface, the standardized input / output interface, and the metadata of the part unit corresponding to each simulation app, through scripts or automated tools.

[0109] Furthermore, the filtering module includes:

[0110] Decompose submodules, which are used to decompose the functional requirements of industry-specific software to determine the subtasks corresponding to each functional requirement;

[0111] The keyword matching submodule is used to match the keywords of each functional requirement with the part unit library to determine the part unit that meets the functional requirements of each subtask.

[0112] The filtering submodule is used to filter metadata for part units that meet the functional requirements of each subtask.

[0113] Furthermore, the filtering module also includes:

[0114] The generation submodule is used to generate a component unit combinational logic diagram by utilizing the connection relationships between the filtered component units, so as to determine the input-output dependencies between component units.

[0115] The adjustment submodule is used to sequentially perform consistency checks and adjustments on the parameters of part units with input-output dependencies.

[0116] The principles, formulas, and parameter definitions involved in the above embodiments are all applicable and will not be repeated here.

[0117] The above embodiments merely illustrate several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A method of developing custom software for an APP through CAE simulation, characterized by, The method comprises the following steps: Step S1, determining parameters required by a design engineer in each simulation App in a target industry to generate a part unit corresponding to each simulation App; Step S2, using a test case to check the correctness of metadata in the part unit corresponding to each simulation App to construct a part unit library corresponding to the target industry; The metadata comprises simulation function description, parameter mapping table between parameters required by a design engineer and simulation App parameters, and dependency relationship between part units; Step S3, using function requirements of industry-specific software and the part unit library to perform part unit screening to combine part units; In the step S3, the specific process of part unit screening comprises: Step S311, decomposing function requirements of the industry-specific software to determine subtasks corresponding to each function requirement; Step S312, using keywords of each function requirement to match keywords between each subtask and the part unit library to determine part units meeting function requirements of each subtask; Step S313, filtering metadata of the part units meeting function requirements of each subtask; In the step S3, the specific process of part unit combination comprises: Step S321, using connection relationship between the screened part units to generate a part unit combination logic diagram to determine input-output dependency relationship between part units; Step S322, sequentially performing consistency check and adjustment on parameters of the part units with input-output dependency relationship; Step S4, packaging the combined part units as industry-specific software.

2. The method of claim 1, wherein, In the step S1, the specific process of determining parameters required by a design engineer in each simulation App in a target industry comprises: Step S111, extracting input parameters of each simulation App in the target industry; Step S112, identifying the extracted input parameters to determine parameters required by a design engineer in each simulation App; In the step S112, the parameters required by a design engineer comprise geometric parameters, process parameter boundary conditions and post-processing requirement parameters.

3. The method of claim 2, wherein, In the step S1, the specific process of generating a part unit corresponding to each simulation App comprises: Step S121, taking parameters required by a design engineer in each simulation App as a user interactive interface; Step S122, standardizing input-output interfaces of each simulation App; Step S123, using a simulation purpose of each simulation App to determine metadata of the part unit corresponding to each simulation App; Step S124, using the user interactive interface, the standardized input-output interface and the metadata of the part unit corresponding to each simulation App, converting the simulation App into a part unit corresponding thereto through a script or an automatic tool.

4. A system for developing customized software through CAE simulation of APPs, characterized by, The system comprises: A generating module for determining parameters required by a design engineer in each simulation App in a target industry to generate a part unit corresponding to each simulation App; The inspection module is configured to check the correctness of the metadata in each part unit corresponding to each simulation App by using a test case, so as to construct a part unit library corresponding to the target industry; The metadata includes simulation function description, parameter mapping table between parameters required by a design engineer and simulation App parameters, and dependency relationship between part units; The screening module is configured to screen part units by using the functional requirements of the industry-specific software and the part unit library, so as to combine part units; The screening module includes: The decomposition submodule is configured to decompose the functional requirements of the industry-specific software, so as to determine subtasks corresponding to each functional requirement; The keyword matching submodule is configured to match keywords of each functional requirement with the part unit library, so as to determine part units meeting the functional requirements of each subtask; The filtering submodule is configured to filter the metadata of the part units meeting the functional requirements of each subtask; The screening module further includes: The generation submodule is configured to generate a part unit combination logic diagram by using the connection relationship between the screened part units, so as to determine the input-output dependency relationship between the part units; The adjustment submodule is configured to sequentially perform consistency check and adjustment on the parameters of the part units with the input-output dependency relationship; The packaging module is configured to package the combined part units into the industry-specific software.

5. The system of claim 4, wherein, The generation module includes: The extraction submodule is configured to extract input parameters of each simulation App in the target industry; The identification submodule is configured to identify the extracted input parameters, so as to determine parameters required by a design engineer in each simulation App; The parameters required by the design engineer include geometric parameters, process parameters, boundary conditions, and post-processing requirement parameters.

6. The system of claim 5, wherein, The generation module further includes: The submodule is configured to take the parameters required by the design engineer in each simulation App as a user interactive interface; The standardization processing submodule is configured to standardize the input-output interfaces of each simulation App; The determination submodule is configured to determine the metadata of the part unit corresponding to each simulation App by using the simulation purpose of each simulation App; The conversion submodule is configured to convert the simulation App into the part unit corresponding thereto by using the user interactive interface, the standardized input-output interface, and the metadata of the part unit corresponding to each simulation App through a script or an automatic tool.

Images