Data dictionary management system and method for embedded system control software

Abstract

This invention relates to a data dictionary management system for embedded system control software, comprising: a unified data dictionary module for storing the overall data dictionary; a data dictionary retrieval and extraction module for extracting data definition information; a similar data reference definition module for extracting data definition information about newly added data; a submodule data dictionary automatic generation module for extracting submodule data directories; a data dictionary merging and verification module for merging data definition information into the overall data dictionary; and a data flow parsing module for analyzing the data flow of conflicting data, setting evaluation schemes, and outputting conflict reports. This invention also relates to a data dictionary management method, comprising the steps of: extracting submodule data directories; extracting data definition information; generating submodule data dictionaries; merging submodule data dictionaries into the overall data dictionary; and updating the overall data dictionary. This invention achieves fully automated data dictionary maintenance and eliminates redundant items.

Description

Technical Field

[0001] This invention relates to the field of embedded system control software technology, and more specifically to a data dictionary management system and method for embedded system control software. Background Technology

[0002] An embedded system data dictionary is a directory that records application metadata definitions. It defines and describes data items, data structures, data flows, data storage, and processing logic. Its purpose is to provide detailed descriptions of each element in the data flow diagram. Data dictionaries are used for modeling and code writing. In short, a data dictionary is a collection of information describing data; it is a collection of definitions for all data elements used in the system.

[0003] Current technologies for managing digital dictionaries largely rely on manual maintenance of data dictionary documents. This involves directly editing or retrieving data table structure information from the database using query statements, then copying it into a document for storage. Furthermore, a unified data dictionary is often not used; instead, the data dictionary is distributed across various component modules and maintained separately. During database construction, modifications to the data model and maintenance operations such as adding and deleting data are frequent.

[0004] The shortcomings of existing technology are:

[0005] 1. Because manual management usually cannot change and maintain the data dictionary in a timely manner, and complex control system software often contains thousands of functional modules, it is easy to cause different definitions of variables in different modules;

[0006] 2. Manual management can lead to different definitions of variables in different modules, which can further cause software integration failures, resulting in a waste of manpower and time. In addition, the manual maintenance of the data dictionary is itself time-consuming and labor-intensive.

[0007] To address the technical challenges of manual management, a very small number of data dictionary maintenance techniques currently employ computers to achieve partial automation. A typical example is Chinese invention patent application number CN201610270564.6, entitled "A Method and System for Managing a Data Dictionary," which discloses the following technical solution:

[0008] A data dictionary management method, applied to multi-task system development, includes: providing an initial data dictionary baseline; defining new development tasks using the latest version of the data dictionary baseline, and maintaining the basic data dictionary under the development task during development; comparing the basic data dictionary of the completed development task with the basic data dictionaries of other ongoing development tasks and the latest version of the data dictionary baseline to obtain parallel task difference analysis results and baseline difference analysis results compared to the basic data dictionary of the completed development task; adding the parallel task difference analysis results to the basic data dictionary under the corresponding ongoing development task; adding the baseline difference analysis results to the latest version of the data dictionary baseline, and publishing the updated version of the data dictionary baseline.

[0009] A baseline describes one or more configuration items and the related entities that constitute those items. In this invention, the data dictionary baseline is a verified and confirmed data dictionary that provides a stable foundation for the project development process. At the beginning of system development, an initial data dictionary baseline is provided to lay the groundwork for upcoming tasks. This initial baseline is continuously updated and released as a higher version during subsequent development. The initial baseline can be obtained through data table import or page maintenance. Then, new development tasks are defined using the latest version of the data dictionary baseline, and the basic data dictionary for each task is maintained during development. Development tasks can be multiple tasks running simultaneously or a single task, all based on the latest version of the data dictionary baseline. At the beginning of the project, development work is based on the initial data dictionary baseline. After the project has progressed for a period, if an updated version of the data dictionary baseline is released, development work is based on that latest version. After defining the development task with the latest version of the data dictionary baseline, during the development process, it is also necessary to maintain the basic data dictionary under each development task. The basic data dictionary is the data dictionary information added to the development task during the development process.

[0010] Maintenance can be performed through batch import of data tables or via page input. This includes aspects such as basic data table information, data table structure information, data table keys, data table indexes, and batch maintenance of the data dictionary. Depending on the specific user dimension during development, maintenance operations may include creating, editing, deleting, and restoring relevant information in these data tables. Next, the basic data dictionary of the completed development task is compared with the basic data dictionary of other ongoing development tasks and the latest version of the data dictionary baseline to obtain parallel task difference analysis results and baseline difference analysis results compared to the basic data dictionary of the completed development task.

[0011] A data dictionary management method further includes: obtaining a test data dictionary in a test environment and performing a difference analysis between the test data dictionary and the data dictionary baseline.

[0012] The steps to obtain the test data dictionary in the test environment include: generating the test data dictionary from the latest version of the data dictionary baseline and the basic data dictionary of the development task.

[0013] A data dictionary management method further includes: querying the baseline of the data dictionary for each version and / or the basic data dictionary for development tasks.

[0014] After obtaining the baseline difference analysis results, the process also includes: generating a data dictionary (DDL) deployment script from the baseline difference analysis results.

[0015] A data dictionary management system includes: a data dictionary baseline initialization unit for providing an initial data dictionary baseline; a development task establishment unit for defining new development tasks using the latest version of the data dictionary baseline; a basic data dictionary maintenance unit for maintaining the basic data dictionary under the development task during development; a first difference analysis unit for comparing the basic data dictionary of the completed development task with the basic data dictionaries of other ongoing development tasks and the latest version of the data dictionary baseline to obtain parallel task difference analysis results and baseline difference analysis results compared to the basic data dictionary of the completed development task; a basic data dictionary update unit for adding the parallel task difference analysis results to the basic data dictionary under the corresponding ongoing development task; and a baseline update unit for adding the baseline difference analysis results to the latest version of the data dictionary baseline and publishing the updated version of the data dictionary baseline.

[0016] The data dictionary management system also includes: a test data dictionary establishment unit, used to obtain the test data dictionary in the test environment; and a second difference analysis unit, used to perform difference analysis between the test data dictionary and the data dictionary baseline.

[0017] In the test data dictionary creation unit, the test data dictionary is generated from the latest version of the data dictionary baseline and the basic data dictionary of the development task.

[0018] The data dictionary management system also includes a query unit for querying the baseline of each version of the data dictionary and / or the basic data dictionary for development tasks.

[0019] The data dictionary management system also includes a DDL deployment script generation unit, which is used to generate data dictionary DDL deployment scripts from the baseline difference analysis results.

[0020] Updating the data dictionary baseline and releasing new versions of the data dictionary baseline, and adding the baseline difference analysis results to the latest version of the data dictionary baseline, ensures that the data dictionary is updated and released in a timely manner. This allows subsequent development tasks to use the latest data dictionary baseline as ground data, effectively manages the data dictionary in project development, and improves project development efficiency.

[0021] For the steps described above, providing an initial data dictionary baseline is usually done only once for initializing and laying the groundwork for the data dictionary. After that, for each development task, all the steps mentioned above except for providing the initial data dictionary baseline are performed during the development process. This effectively manages the basic data dictionary of the development task and the system's data dictionary baseline during the development process until the system development is completed.

[0022] While the technical solution provided in patent CN201610270564.6 offers a method for managing data dictionaries for different versions and development branches, it still suffers from the following technical defects:

[0023] 1. Because the comparison of differences between data dictionaries only generates analysis reports and does not perform automated merging, and the existing data dictionary information is not used as a reference for automated definition when adding new data, the management efficiency is very low.

[0024] 2. Because there is no automated merging process, redundant items will increase exponentially with the increase of running time, causing the efficiency of data retrieval to drop sharply in the later stages, until the system can no longer run and crashes. Summary of the Invention

[0025] To address the aforementioned problems, this invention provides a data dictionary management system and method for embedded system control software. Its purpose is to achieve fully automated data dictionary maintenance, eliminating the various drawbacks of manual management; preventing redundant items from occurring, thus preventing system slowdown or even crash.

[0026] To solve the above problems, the technical solution provided by the present invention is as follows:

[0027] A data dictionary management system for embedded system control software includes the following components:

[0028] A unified data dictionary module is used to store the overall data dictionary; the overall data dictionary contains data definition information.

[0029] The data dictionary retrieval and extraction module is used to automatically extract the data definition information of the data already existing in the total database.

[0030] The same type of data reference definition module is used to automatically extract the data definition information about the new data and transmit it to the staff for manual review and confirmation.

[0031] The submodule data dictionary automatic generation module is used to extract the submodule data directory about submodule data.

[0032] The data dictionary merging and verification module is used to automatically merge the data definition information about the submodule data into the total data dictionary;

[0033] The data flow parsing module is used to analyze the data flow of conflicting data in this management system when the data of the sub-module conflicts with the total data dictionary, set an evaluation scheme, automatically determine whether to incorporate the conflicting data into the total data dictionary, and output a conflict report for manual review by staff.

[0034] Preferably, the submodule data includes existing data in the overall database and the newly added data.

[0035] Preferably, this management system will also automatically merge the existing data in the total database with the newly added data, and then automatically generate a submodule data dictionary for submodule testing.

[0036] Preferably, the submodule data dictionary includes data definition information about the data already existing in the total database and data definition information about the newly added data.

[0037] A method for managing a data dictionary for embedded system control software, utilizing a data dictionary management system for embedded system control software, includes the following steps:

[0038] S100. Extract the current submodule data directory regarding the submodule data;

[0039] S200. Extract the data definition information regarding the submodule data;

[0040] S300. Automatically generate the data dictionary for the submodule;

[0041] S400. Merge the submodule data dictionary into the overall data dictionary;

[0042] S500. Update the total data dictionary;

[0043] S600. End the execution flow of this data dictionary management method.

[0044] Preferably, extracting the data definition information about the submodule data in S200 specifically includes the following steps:

[0045] S210. Determine the type of data in the submodule;

[0046] S220. Based on the judgment result, perform the following operations:

[0047] If the data in the submodule is data that already exists in the total database, then execute S240;

[0048] If the submodule data is the newly added data, then execute S230;

[0049] S230. Based on data that already exists in the overall database and is of the same type as the data in the submodule, perform an analogy definition to obtain the data definition information; then execute S300;

[0050] S240. Extract the data definition information about the submodule data for recording into the data dictionary; then execute S300.

[0051] Preferably, updating the total data dictionary in S500 specifically includes the following steps:

[0052] S510. Determine whether the submodule data conflicts with the total data dictionary;

[0053] S520. Based on the judgment result, perform the following operations:

[0054] If the submodule data conflicts with the total data dictionary, then execute S530;

[0055] If the submodule data does not conflict with the total data dictionary, then execute S550;

[0056] S530. Analyze the data flow of the conflicting data in this management system and set the evaluation scheme; then execute S540;

[0057] S540. Output the conflict report for manual review by staff; then execute S600;

[0058] S550. Update the total data dictionary; then execute S600.

[0059] Preferably, S530, analyzing the conflict data in the data flow of this management system and setting the evaluation scheme, further includes the following steps:

[0060] S531. Automatically determine whether to incorporate the conflicting data into the overall data dictionary;

[0061] S532. Based on the judgment result, perform the following operations:

[0062] If it is determined that the conflicting data should be incorporated into the total data dictionary, then the conflicting data is incorporated into the total data dictionary; then S540 is executed;

[0063] If it is determined that the conflicting data should not be incorporated into the total data dictionary, then S540 is executed directly.

[0064] Preferably, in S100, the submodule data dictionary automatic generation module is also used to extract the model variable data list; the model variable data list includes a list of variable names contained in the submodule data dictionary automatic generation module.

[0065] Preferably, the data in the overall data dictionary are named according to a naming rule that proceeds from the largest to the smallest classification range.

[0066] Compared with the prior art, the present invention has the following advantages:

[0067] 1. Because this invention uses a unified data dictionary to form a unified data dictionary, and automatically references and generates new data definition information by referencing existing data in the updates of each design branch, it can achieve fully automatic data dictionary maintenance, thus eliminating the various drawbacks of manual management;

[0068] 2. Because this invention automatically compares data differences and automatically updates the unified data dictionary database according to the merging strategy, it eliminates the occurrence of redundant items and will not cause the system to slow down or even crash. Attached Figure Description

[0069] Figure 1 This is a schematic diagram of the system structure according to a specific embodiment of the present invention;

[0070] Figure 2 This is a schematic diagram of the method flow of a specific embodiment of the present invention. Detailed Implementation

[0071] The present invention will be further illustrated below with reference to specific embodiments. It should be understood that these embodiments are for illustrative purposes only and are not intended to limit the scope of the invention. After reading the present invention, any modifications of the present invention in various equivalent forms by those skilled in the art will fall within the scope defined by the appended claims.

[0072] like Figure 1 As shown, the data dictionary management system for embedded system control software includes the following components:

[0073] The unified data dictionary module stores the overall data dictionary, which contains data definition information.

[0074] The data dictionary retrieval and extraction module is used to automatically extract data definition information that already exists in the total database.

[0075] The similar data reference definition module is used to automatically extract data definition information about new data and send it to staff for manual review and confirmation.

[0076] The submodule data dictionary automatic generation module is used to extract the submodule data directory about the submodule data.

[0077] In this specific embodiment, the submodule data includes existing data in the overall database and newly added data.

[0078] In this specific embodiment, the management system will also automatically merge the existing data and newly added data in the total database, and then automatically generate a submodule data dictionary for submodule testing.

[0079] In this specific embodiment, the submodule data dictionary contains data definition information about data already existing in the main database and data definition information about newly added data.

[0080] The data dictionary merging and verification module is used to automatically incorporate data definition information about submodule data into the overall data dictionary.

[0081] The data flow parsing module is used to analyze the data flow of conflicting data in this management system when data from a submodule conflicts with the overall data dictionary, set an evaluation scheme, automatically determine whether to incorporate the conflicting data into the overall data dictionary, and output a conflict report for manual review by staff.

[0082] like Figure 2 As shown, the present invention also includes a data dictionary management method for embedded system control software using a data dictionary management system for embedded system control software, comprising the following steps:

[0083] S100. Extract the current submodule data directory related to submodule data.

[0084] In this specific embodiment, in S100, the submodule data dictionary automatic generation module is also used to extract the model variable data list; the model variable data list includes a list of variable names contained in the submodule data dictionary automatic generation module.

[0085] This specific embodiment takes a particular sub-functional module of a vehicle control system as an example: After the control system completes the design of this sub-functional module, if Simulink is used to complete the logic modeling, the sub-module data dictionary is used to automatically generate the Simulink model variable data list N_list, which contains a list of variable names contained in this module.

[0086] S200. Extract data definition information about the submodule data.

[0087] In this specific embodiment, S200 extracts data definition information about submodule data, which specifically includes the following steps:

[0088] S210. Determine the type of data in the submodule.

[0089] S220. Based on the judgment result, perform the following operations:

[0090] If the data in the submodule is data that already exists in the main database, then execute S240.

[0091] If the submodule data is newly added data, then execute S230.

[0092] S230. Based on the data that already exists in the main database and is of the same type as the submodule data, perform analogy definition to obtain data definition information; then execute S300.

[0093] S240. Extract the data definition information about the submodule data for recording into the data dictionary; then execute S300.

[0094] In this specific embodiment, S200 specifically performs the following: compares the total data dictionary A and divides the submodule data into two categories. One category is the data that already exists in the total database A, which is the list EXIST_VAR_list_1 containing the overlapping variables in the total database A and N_list. The other category is the data newly added to this module, which is the list UNEXIST_VAR_list_1.

[0095] S300. Automatically generate submodule data dictionaries.

[0096] In this specific embodiment, S300 specifically performs the following: for the data in the list EVAR_XIST_VAR_list_1, the data dictionary retrieval and extraction module automatically extracts the definition information from the total data dictionary A to obtain the existing data dictionary subset EXIST_VAR_DIC; for the newly added data list UN_EXIST_VAR_list_1, the same type of data reference definition module is used.

[0097] S400. Merge the submodule data dictionary into the total data dictionary.

[0098] In this specific embodiment, the data in the general data dictionary are named according to the naming rule of classification range from large to small.

[0099] It should be noted that specific naming rules are used to categorize the data. For example, in the variable AIR_TEMP_EGRV_VAR_xVAR_x_M, AIR represents the module category to which the variable belongs, TEMP represents temperature, EGRV represents EGR valve related variables, M represents the measured quantity, and x represents the letter related to the specific definition of the variable. This narrows down the scope, finds the definitions of variables in the same category as a reference, automatically generates the definition of new data, and then manually reviews and confirms it to obtain the data dictionary consisting of the new data.

[0100] UN_EXIST_VAR_DIC.

[0101] In this specific embodiment, S400 specifically performs the following: automatically merges EVAR_XIST_VAR_DIC and UN_EVAR_XIST_VAR_DIC to generate a submodule data dictionary CHILD_VAR_DIC, which can be used for model testing and code generation, etc.

[0102] S500. Update the total data dictionary.

[0103] In this specific embodiment, updating the total data dictionary in S500 includes the following steps:

[0104] S510. Determine if there is a conflict between the submodule data and the overall data dictionary.

[0105] S520. Based on the judgment result, perform the following operations:

[0106] If the submodule data conflicts with the overall data dictionary, then execute S530.

[0107] If the submodule data does not conflict with the overall data dictionary, then execute S550.

[0108] S530. Analyze the data flow of conflicting data in this management system and set an evaluation scheme; then execute S540.

[0109] In this specific embodiment, S530, which analyzes the data flow of conflicting data in this management system and sets an evaluation scheme, also includes the following steps:

[0110] S531. Automatically determine whether to incorporate conflicting data into the overall data dictionary.

[0111] S532. Based on the judgment result, perform the following operations:

[0112] If it is determined that conflicting data should be incorporated into the total data dictionary, then the conflicting data should be incorporated into the total data dictionary; then execute S540.

[0113] If it is determined that conflicting data should not be included in the total data dictionary, then S540 is executed directly.

[0114] S540. Output a conflict report for manual review by staff; then execute S600.

[0115] In this specific embodiment, the following detailed conflict resolution strategies are also provided, with a total of 5 examples covering 5 possible specific situations:

[0116] Case 1: For example, if VAR_x is the output of the current submodule, but no other module references VAR_x as input, and no other module outputs VAR_x, then the VAR_x data definition information in CHILD_VAR_DIC will automatically overwrite the VAR_x definition information in the total data dictionary A.

[0117] Case 2: If VAR_x is an output in the current submodule and is used as an input by other modules, and no other module outputs VAR_x, then the VAR_x data definition information in CHILD_VAR_DIC should not be overwritten with the VAR_x definition information in the total data dictionary A.

[0118] Case 3: If VAR_x is an output in the current submodule and other modules also output VAR_x, then the VAR_x data definition information in CHILD_VAR_DIC will not be overwritten with the VAR_x definition information in the total data dictionary A, and an error message will be reported.

[0119] Case 4: If VAR_x is the input in the current submodule but no other module outputs it, then the VAR_x data definition information in CHILD_VAR_DIC will not be overwritten with the VAR_x definition information in the total data dictionary A. The system will automatically determine that the naming is incorrect and report an error message.

[0120] Case 5: If VAR_x is an input in the current submodule and other modules output VAR_x, then refuse to overwrite the VAR_x definition information in the total data dictionary A with the VAR_x data definition information in CHILD_VAR_DIC.

[0121] S550. Update the total data dictionary; then execute S600.

[0122] In this specific embodiment, S500 specifically performs the following: using the data dictionary merging and verification module to automatically merge the submodule data dictionary CHILD_VAR_DIC into the total data dictionary A; when data VAR_x in the submodule CHILD_VAR_DIC conflicts with data in the total data dictionary A, the data flow parsing module analyzes the data flow of the conflicting data VAR_x in the system, sets an evaluation scheme, automatically determines whether it covers the data definition in A, and outputs a conflict report for manual review after the automatic judgment is completed.

[0123] S600. End the execution flow of this data dictionary management method.

[0124] In the above detailed description, various features are combined together in a single embodiment to simplify this disclosure. This approach to disclosure should not be construed as reflecting an intention that embodiments of the claimed subject matter require more features than are explicitly stated in each claim. Rather, as reflected in the appended claims, the invention is presented with fewer features than all of the features of the single disclosed embodiment. Therefore, the appended claims are hereby explicitly incorporated into the detailed description, wherein each claim stands alone as a preferred embodiment of the invention.

[0125] The disclosed embodiments have been described above to enable any person skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the spirit and scope of this disclosure. Therefore, this disclosure is not limited to the embodiments given herein, but is consistent with the broadest scope of the principles and novel features disclosed in this application.

[0126] The foregoing description includes examples of one or more embodiments. It is certainly impossible to describe all possible combinations of components or methods in order to describe the above embodiments, but those skilled in the art will recognize that further combinations and arrangements of the various embodiments are possible. Therefore, the embodiments described herein are intended to cover all such changes, modifications, and variations that fall within the scope of the appended claims. Furthermore, the term "comprising" as used in the specification or claims is interpreted in a manner similar to the term "including," as interpreted when used as a conjunction in the claims. Additionally, the use of any term "or" in the specification of the claims is intended to mean "non-exclusive or."

[0127] The specific implementation methods described above further illustrate the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above description is only a specific implementation method of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A data dictionary management system for embedded system control software, characterized in that: Includes the following parts: A unified data dictionary module is used to store the overall data dictionary; the overall data dictionary contains data definition information. The data dictionary retrieval and extraction module is used to automatically extract the data definition information of the data already existing in the total database. The same type of data reference definition module is used to automatically extract the data definition information about the new data and transmit it to the staff for manual review and confirmation. The submodule data dictionary automatic generation module is used to extract the submodule data directory about submodule data. The data dictionary merging and verification module is used to automatically merge the data definition information about the submodule data into the total data dictionary; The data flow parsing module is used to analyze the data flow of conflicting data in this management system when the data of the submodule conflicts with the total data dictionary, set an evaluation scheme, automatically determine whether to incorporate the conflicting data into the total data dictionary, and output a conflict report for manual review by staff.

2. The data dictionary management system for embedded system control software according to claim 1, characterized in that: The submodule data includes existing data in the main database and the newly added data.

3. The data dictionary management system for embedded system control software according to claim 2, characterized in that: This management system will also automatically merge the existing data in the main database with the newly added data, and then automatically generate a submodule data dictionary for submodule testing.

4. The data dictionary management system for embedded system control software according to claim 3, characterized in that: The submodule data dictionary contains data definition information about the data already existing in the main database and data definition information about the newly added data.

5. A data dictionary management method for embedded system control software using the data dictionary management system for embedded system control software as described in claim 4, characterized in that: Includes the following steps: S100. Extract the current submodule data directory regarding the submodule data; S200. Extract the data definition information regarding the submodule data; S300. Automatically generate the data dictionary for the submodule; S400. Merge the submodule data dictionary into the overall data dictionary; S500. Update the total data dictionary; S600. End the execution flow of this data dictionary management method.

6. The data dictionary management method for embedded system control software according to claim 5, characterized in that: S200 extracts the data definition information about the submodule data, specifically including the following steps: S210. Determine the type of data in the submodule; S220. Based on the judgment result, perform the following operations: If the data in the submodule is data that already exists in the total database, then execute S240; If the submodule data is the newly added data, then execute S230; S230. Based on data that already exists in the overall database and is of the same type as the data in the submodule, perform an analogy definition to obtain the data definition information; then execute S300; S240. Extract the data definition information about the submodule data for recording into the data dictionary; then execute S300.

7. The data dictionary management method for embedded system control software according to claim 6, characterized in that: Updating the total data dictionary in S500 specifically includes the following steps: S510. Determine whether the submodule data conflicts with the total data dictionary; S520. Based on the judgment result, perform the following operations: If the submodule data conflicts with the total data dictionary, then execute S530; If the submodule data does not conflict with the total data dictionary, then execute S550; S530. Analyze the data flow of the conflicting data in this management system and set the evaluation scheme; then execute S540; S540. Output the conflict report for manual review by staff; then execute S600; S550. Update the total data dictionary; then execute S600.

8. The data dictionary management method for embedded system control software according to claim 7, characterized in that: S530 analyzes the conflicting data in the data flow of this management system and sets the evaluation scheme, and also includes the following steps: S531. Automatically determine whether to incorporate the conflicting data into the overall data dictionary; S532. Based on the judgment result, perform the following operations: If it is determined that the conflicting data should be incorporated into the total data dictionary, then the conflicting data is incorporated into the total data dictionary; then S540 is executed; If it is determined that the conflicting data should not be incorporated into the total data dictionary, then S540 is executed directly.

9. The data dictionary management method for embedded system control software according to any one of claims 5 to 8, characterized in that: In S100, the submodule data dictionary automatic generation module is also used to extract the model variable data list; the model variable data list contains a list of variable names included in the submodule data dictionary automatic generation module.

10. The data dictionary management method for embedded system control software according to claim 9, characterized in that: The data in the overall data dictionary are named according to a naming rule that proceeds from the largest to the smallest category.

Images