A document verification file generation method and system

Abstract

The application discloses a document verification file generation method and system, which is used for document verification of a TACS system and runs on a TACS security platform. The document verification file generation method comprises the following steps: acquiring a latest data framework file published by the TACS security platform; constructing a plurality of verification items according to the data framework file; automatically generating a verification file according to all the verification items, and comparing the generated verification file with an original verification file to quickly determine an upgrade verification range. The application can automatically identify and construct a plurality of verification items, so that the verification items are acquired more quickly and accurately, and the verification speed of a document to be verified is improved.

Description

Technical Field

[0001] This invention relates to the field of rail transit technology, and in particular to a document verification file generation method and system. Background Technology

[0002] The TACS (Train Autonomous Control System) is a next-generation product for urban rail transit signaling systems. Compared with the traditional CBTC (Communication Based Train Control System), it has advantages such as higher operational efficiency, fewer devices, and lower cost. As a next-generation product, verification during the design phase is a crucial activity in the project's implementation and validation, playing a vital role in ensuring the quality of the system design.

[0003] The primary purpose of verification activities during the design phase is to verify the correctness of the design documents and whether they meet the platform's design rules and constraints. In the TACS project, the PrPD (Project Parameter Description) document is the most critical design document, and its verification plays a decisive role in the quality of the system data. The PrPD document mainly contains four parts: PrPD_Infrastructure, PrPD_Rollingstock, PrPD_U500Settings, and PrPD_Services. These four design documents are used to define the physical or logical information, vehicle parameters, general settings, and train operation paths in the TACS project, respectively. Therefore, during the TACS project design phase, the verification of all four PrPD documents must be completed without any serious remaining issues before system data creation can proceed.

[0004] In the existing technology, the verification steps of PrPD documents are as follows: (1) Based on the parameter path diagram of the U500DataModelwithoutpublished.xsd file published by the platform baseline, all parameters and parameter paths are manually listed as verification items; (2) Based on all verification items, the project PrPD document is manually checked to ensure that all parameters required in the .xsd file are fully defined, the parameter definitions comply with the platform rules, and the parameter values ​​have source definitions. It can be seen that the current verification activities of PrPD documents are completely done manually. Due to the thousands of verification items in the xsd file and the deep hierarchy of parameter paths, the verification activities of PrPD documents have problems such as large workload, low efficiency, and easy omission of items. Summary of the Invention

[0005] The purpose of this invention is to provide a document verification file generation method and system that can automatically identify and construct several verification items, making the acquisition of verification items and the generation of verification files faster and more accurate, thereby improving the verification speed of documents to be verified.

[0006] To achieve the above objectives, the present invention is implemented through the following technical solution:

[0007] A method for generating a document verification file, used for document verification in a TACS system, wherein the TACS system runs on a TACS security platform; the method for generating the document verification file includes:

[0008] Obtain the latest data framework file released by the TACS security platform;

[0009] Construct several validation items based on the data framework file;

[0010] Generate a verification file based on all the aforementioned verification items; and

[0011] The generated verification file is compared with the original verification file to determine the scope of the upgrade verification.

[0012] Optionally, the data framework file is an XSD file.

[0013] Optionally, before performing the step of constructing several validation items based on the data framework file, the method further includes: opening the data framework file in text format to obtain the data framework text.

[0014] Optionally, the step of constructing several validation items based on the data framework file includes:

[0015] Search the element name field in the data frame text, and use the value of the first element name field found as the name of the starting level of a parameter path;

[0016] The composite type segment in the data framework text is searched according to the first preset search criteria to obtain the element name field in the composite type segment and use its value as the name of the intermediate level of the parameter path.

[0017] The data framework text is searched according to the second preset search criteria to obtain the attribute name field in the composite type segment and use its value as the name of the final level of the parameter path; and

[0018] A parameter path is constructed based on the starting level name, the intermediate level name, and the ending level name of the parameter path, and each parameter path is a verification item.

[0019] Optionally, the intermediate levels of the parameter path include several sub-levels, and the starting level is the level preceding the first sub-level in the intermediate level, and the last sub-level in the intermediate level is the level preceding the ending level.

[0020] Optionally, the first preset search conditions include a first search start position, a first search end position, and a first search content; and the first search start position is: composite type name = the name of the previous level, the first search end position is the last line of the composite type segment, and the first search content is the element name field; and the last line of each composite type segment is the same.

[0021] Optionally, the step of searching for composite type segments in the data frame text according to the first preset search criteria includes:

[0022] The starting position of the first search is obtained based on the name of the previous level;

[0023] The first search content is searched between the first search start position and the first search end position. If the element name field is found, a level is added to the corresponding parameter path, and the value of the searched element name field is used as the name of the added level; and the added level is a sub-level in the intermediate level.

[0024] Optionally, the step of searching for composite type segments in the data framework text according to the first preset search conditions further includes: if no element name field is found, the name of the previous level is taken as the last sub-level of the intermediate level.

[0025] Optionally, the second preset search conditions include a second search start position, a second search end position, and a second search content; and the second search start position is: composite type name = the name of the previous level, the second search end position is the last line of the composite type segment, and the second search content is the attribute name field.

[0026] Optionally, the step of searching for composite type segments in the data frame text according to the second preset search criteria includes:

[0027] The second search starting position is obtained based on the name of the last sub-level in the intermediate level of the parameter path;

[0028] The second search content is searched between the second search start position and the second search end position, and the value of the searched attribute name field is used as the name of the end level.

[0029] On the other hand, the present invention also provides a document verification file generation system for document verification in a TACS system, wherein the TACS system runs on a TACS security platform; the document verification file generation system includes:

[0030] The data framework file acquisition module is used to acquire the latest data framework file released by the TACS security platform.

[0031] A verification item generation module, connected to the data framework file acquisition module, is used to construct several verification items based on the data framework file.

[0032] A verification file generation module, connected to the verification item generation module, is used to generate a verification file based on all the verification items; and

[0033] The comparison module is connected to the verification file generation module and compares the generated verification file with the original verification file to determine the scope of the upgrade verification.

[0034] Optionally, the data framework file is an XSD file.

[0035] Optionally, the document verification file generation system further includes: a text acquisition module, which is connected to the data framework file acquisition module and the verification item generation module respectively, for opening the data framework file in text form to obtain the data framework text.

[0036] Optionally, the verification item generation module is specifically used to search for the element name field in the data frame text, so as to use the value of the first element name field found as the name of the starting level of a parameter path;

[0037] The composite type segment in the data framework text is searched according to the first preset search criteria to obtain the element name field in the composite type segment and use its value as the name of the intermediate level of the parameter path.

[0038] The data framework text is searched according to the second preset search criteria to obtain the attribute name field in the composite type segment and use its value as the name of the final level of the parameter path; and

[0039] A parameter path is constructed based on the starting level name, the intermediate level name, and the ending level name of the parameter path, and each parameter path is a verification item.

[0040] Optionally, the intermediate levels of the parameter path include several sub-levels, and the starting level is the level preceding the first sub-level in the intermediate level, and the last sub-level in the intermediate level is the level preceding the ending level.

[0041] Optionally, the first preset search conditions include a first search start position, a first search end position, and a first search content; and the first search start position is: composite type name = the name of the previous level, the first search end position is the last line of the composite type segment, and the first search content is the element name field; and the last line of each composite type segment is the same.

[0042] Optionally, when the verification item generation module searches for composite type segments in the data frame text according to the first preset search conditions,

[0043] The starting position of the first search is obtained based on the name of the previous level;

[0044] The first search content is searched between the first search start position and the first search end position. If the element name field is found, a level is added to the corresponding parameter path, and the value of the searched element name field is used as the name of the added level; and the added level is a sub-level in the intermediate level.

[0045] Optionally, when the verification item generation module searches for composite type segments in the data framework text according to the first preset search conditions, if no element name field is found, the name of the previous level is used as the last sub-level of the intermediate level.

[0046] Optionally, the second preset search conditions include a second search start position, a second search end position, and a second search content; and the second search start position is: composite type name = the name of the previous level, the second search end position is the last line of the composite type segment, and the second search content is the attribute name field.

[0047] Optionally, when the verification item generation module searches for composite type segments in the data frame text according to the second preset search conditions,

[0048] The second search starting position is obtained based on the name of the last sub-level in the intermediate level of the parameter path;

[0049] The second search content is searched between the second search start position and the second search end position, and the value of the searched attribute name field is used as the name of the end level.

[0050] Compared with the prior art, the present invention has at least one of the following advantages:

[0051] This invention provides a document verification file generation method and system. Based on the latest data framework file released by the TACS security platform, it can automatically identify and construct several verification items, and automatically generate a verification file based on all verification items. The generated verification file is compared with the original verification document to quickly locate the changed verification items, thereby determining the scope of the upgrade verification.

[0052] In this invention, the data framework file can be opened in text form and the data framework text can be obtained, which facilitates the subsequent automatic identification and construction of verification items.

[0053] This invention improves the verification speed of documents by performing a cyclic search on the data framework text and automatically identifying and importing verification items, which is faster and more accurate than the original manual identification and listing of verification items.

[0054] This invention is universal and can be used in all projects that use the TACS platform baseline and the XSD data framework as data input.

[0055] After the TACS platform baseline is upgraded and the data framework file is updated, this invention can quickly identify the changed verification items, thereby quickly determining the scope of the upgrade verification. Attached Figure Description

[0056] Figure 1 This is a flowchart of a document verification file generation method provided in an embodiment of the present invention;

[0057] Figure 2 This is a graphical structure diagram of the data frame file in a document verification file generation method provided by an embodiment of the present invention;

[0058] Figure 3a and Figure 3b This is a text-based structural diagram of a data frame file in a document verification file generation method provided by an embodiment of the present invention;

[0059] Figure 4 This is a logic diagram of a document verification file generation method provided in an embodiment of the present invention. Detailed Implementation

[0060] The following detailed description, in conjunction with the accompanying drawings and specific embodiments, provides a further detailed explanation of the document verification file generation method and system proposed in this invention. The advantages and features of this invention will become clearer from the following description. It should be noted that the drawings are in a very simplified form and use non-precise proportions, used only to facilitate and clearly illustrate the embodiments of this invention. Please refer to the drawings to make the objectives, features, and advantages of this invention more apparent and understandable. It should be understood that the structures, proportions, sizes, etc., depicted in the accompanying drawings are only for illustrative purposes to aid those skilled in the art and are not intended to limit the implementation conditions of this invention. Therefore, they have no substantial technical significance. Any modifications to the structure, changes in proportions, or adjustments to the size, without affecting the effects and objectives achieved by this invention, should still fall within the scope of the technical content disclosed in this invention.

[0061] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0062] Combined with appendix Figures 1 to 4 As shown, this embodiment provides a document verification file generation method for document verification in a TACS system, wherein the TACS system runs on the TACS security platform; the document verification file generation method includes: step S110, obtaining the latest data framework file released by the TACS security platform; step S120, constructing several verification items based on the data framework file; step S130, generating a verification file based on all the verification items; and step S140, comparing the verification file with the original verification file to quickly determine the verification scope of the upgraded verification items.

[0063] Specifically, in this embodiment, during the TACS project implementation process, the TACS security platform baseline will publish the data framework file (e.g., the U500DataModelwithoutpublished.xsd file) for TACS project design and system data creation. The data framework file defines all parameters and parameter paths required by the TACS project and is a crucial input for the verification activities of documents to be verified (e.g., PrPD documents) in the TACS project. More specifically, the data framework file is an xsd file; and the data framework file can have two display formats: graphical and textual; wherein, when the data framework file is opened in graphical form (e.g., ... Figure 2 As shown), it can intuitively display the hierarchical relationship of the path, which is convenient for visual extraction, but it is difficult to read automatically; when the data framework file is opened in text format (such as...), it can intuitively display the hierarchical relationship of the path, which is convenient for visual extraction, but it is difficult to read automatically; Figure 3a and Figure 3b As shown, although the hierarchical relationship cannot be intuitively displayed, the names of different hierarchical paths can be automatically extracted by searching keywords, which is convenient for the subsequent construction of the verification items and the generation of the verification files, but the present invention is not limited thereto.

[0064] Please also refer to Figure 1 , Figure 3a , Figure 3b and Figure 4 Before performing step S120, the method further includes: opening the data frame file in text format to obtain the data frame text.

[0065] Step S120 includes: Step S1201, searching for an element name field in the data frame text, and using the value of the first element name field found as the name of the starting level of a parameter path; Step S1202, searching for composite type segments in the data frame text according to a first preset search condition, to obtain the element name field in the composite type segment and using its value as the name of the intermediate level of the parameter path; Step S1203, searching for composite type segments in the data frame text according to a second preset search condition, to obtain the attribute name field in the composite type segment and using its value as the name of the ending level of the parameter path; and Step S1204, constructing a parameter path based on the starting level name, intermediate level name, and ending level name of the parameter path, wherein each parameter path is a verification item.

[0066] It is understood that the intermediate levels of the parameter path include several sub-levels, which can be respectively denoted as: first sub-level, second sub-level, third sub-level, ..., last sub-level; and the starting level is the level preceding the first sub-level in the intermediate level, and the last sub-level in the intermediate level is the level preceding the ending level.

[0067] Specifically, in this embodiment, in step S1201, the element name field is searched from the beginning in the data framework text, resulting in several ordered search results containing the element name field. The element name field in the first search result can be recorded as the first element name field in the data framework text, and the value of the first element name field can be used as the name of the starting level of the parameter path. For example, as... Figure 3a As shown, the first element name field in the data framework text is: element name = "U500SystemDatabase". U500SystemDatabase can be used as the name of the starting level of the parameter path, but the present invention is not limited thereto.

[0068] Specifically, in this embodiment, in step S1202, the composite type segment can be searched in the data framework text according to the first preset search conditions; the first preset search conditions include a first search start position, a first search end position, and a first search content; and the first search start position is: composite type name = the name of the previous level (i.e., the first line content of the composite type segment), the first search end position is the last line content of the composite type segment, and the first search content is the element name; and the last line content of each composite type segment is the same. The specific steps for searching the composite type segment in the data framework text according to the first preset search conditions include: obtaining the first search start position according to the name of the previous level; searching the first search content between the first search start position and the first search end position; if the element name field is found, adding a level to the corresponding parameter path, and using the value of the searched element name field as the name of the added level; and the added level is a sub-level in the intermediate level; if the element name field is not found, using the name of the previous level as the last sub-level of the intermediate level.

[0069] More specifically, after obtaining the name of the starting level of the parameter path, the name of the starting level can be used as the name of the previous level; then, the first search start position is taken as the name of the starting level (e.g., complexType name = "U500SystemDatabase"), and the first search end position is taken as the last line of the complex type segment (e.g.); the first search content, i.e., the element name field, is searched between the first search start position and the first search end position. If the element name field (which may be one, two, or even more) is found, the parameter path is added to a level, and the value of one of the searched element name fields (e.g., element name = "infrastructure") (e.g., infrastructure) is used as the name of the added level (i.e., the first sub-level in the intermediate level). After obtaining the name of the first level in the intermediate level of the parameter path, the name of the first sub-level in the intermediate level can be used as the name of the previous level. Then, the first search start position is set with the composite type name = the name of the first sub-level in the intermediate level (e.g., complexType name = "infrastructure"), and the first search end position is set with the last line of the composite type segment (e.g., the last line of the composite type segment). The first search content, i.e., the element name field, is searched between the first search start position and the first search end position. If the element name field (which may be one, two, or even more) is found, the parameter path is added to a level, and the value of one of the found element name fields (e.g., element name = "logicalElements") (e.g., logicalElements) is used as the name of the added level (i.e., the second sub-level in the intermediate level). By continuously performing the above search steps to search the composite type segment, after obtaining the nth sub-level in the intermediate level of the parameter path, the name of the nth sub-level in the intermediate level (e.g., notProtectedSupervisedZone) can be used as the name of the previous level. If the element name field is not found between the corresponding first search start position and the first search end position, then the nth sub-level in the intermediate level is used as the last sub-level of the intermediate level. At this time, the name of the intermediate level corresponding to the parameter path is completely obtained, but the present invention is not limited thereto.

[0070] Specifically, in this embodiment, in step S1203, the composite type segment can be searched in the data framework text according to the second preset search conditions; the second preset search conditions include a second search start position, a second search end position, and a second search content; and the second search start position is: composite type name = the name of the previous level, the second search end position is the last line of the composite type segment, and the second search content is the attribute name field. The specific steps for searching the composite type segment in the data framework text according to the second preset search conditions include: obtaining the second search start position according to the name of the last sub-level in the intermediate level of the parameter path; searching the second search content between the second search start position and the second search end position, and using the value of the searched attribute name field as the name of the final level.

[0071] More specifically, after obtaining the name of the intermediate level of the parameter path, the name of the last sub-level in the intermediate level can be used as the name of the previous level. Figure 3b As shown, the second search starts at the name of the last sub-level in the intermediate level (e.g., `complexType name = "notProtectedSupervisedZone"`) and ends at the last line of the composite type segment (e.g., `lastLine`). The search then continues between the second search start and end positions, searching for the second search content, i.e., the `attribute name` field. If the `attribute name` field (which may be one, two, or more) is found, the parameter path is added to a new level, and the value of one of the found `attribute name` fields (e.g., `id`) is used as the name of the added level (i.e., the final level). Optionally, the value of the `attribute name` field includes: `name`, `id`, `value`, `ref`, etc., but this invention is not limited to these.

[0072] Specifically, in this embodiment, in step S1204, a complete parameter path can be constructed based on the starting level name, the intermediate level name, and the ending level name corresponding to the parameter path. The format of the parameter path is: starting level name / first sub-level name in the intermediate level / second sub-level name in the intermediate level / ... / last sub-level name in the intermediate level / ending level name (e.g., U500SystemDatabase / infrastructure / logicalElements / notProtectedSupervisedZones / notProtectedSupervisedZone / id), but the present invention is not limited thereto.

[0073] Specifically, in this embodiment, by repeatedly executing steps S1202 to S1204, several different parameter paths can be obtained. In step S130, each parameter path is automatically included as a verification item in an Excel file, thus obtaining the verification file, which is an Excel file as shown in Table 1, but the present invention is not limited thereto.

[0074] Table 1 Validation Documents (Partial Content Shown)

[0075]

[0076] Furthermore, in this embodiment, if the TACS platform baseline is upgraded and the data framework file is updated, not only can the updated verification file be automatically obtained according to steps S120 and S130, but the verification file before the update can also be obtained according to the data framework file before the update and steps S120 and S130. By comparing the updated verification file with the verification file before the update using existing comparison tools, newly added, changed, and deleted verification items can be quickly identified, and the latest upgraded verification scope can be determined.

[0077] Specifically, in this embodiment, the TACS platform defines a series of rules to define the project in the verification item. Regarding verifying whether the project's PrPD document fully defines all the parameters required in the verification file generated from the data framework file and meets the platform rules, this process relies on human understanding and experience of the rules, and therefore must be manually verified. Furthermore, in addition to meeting the platform rules, the elements defined in the project's PrPD document also include the definitions of some parameters. These parameters need to have a clear source. In this step, all parameters are manually checked to ensure they have a source definition, but this invention is not limited to this.

[0078] On the other hand, this embodiment also provides a document verification file generation system for document verification in a TACS system, wherein the TACS system runs on a TACS security platform. The document verification file generation system includes: a data framework file acquisition module for acquiring the latest data framework file released by the TACS security platform; a verification item generation module connected to the data framework file acquisition module for constructing several verification items based on the data framework file; a verification file generation module connected to the verification item generation module for generating a verification file based on all the verification items; and a comparison module connected to the verification file generation module for comparing the generated verification file with the original verification file to quickly determine the upgraded verification items.

[0079] It is understood that the data framework file is an XSD file. The document verification file generation system further includes a text acquisition module, which is connected to both the data framework file acquisition module and the verification item generation module, and is used to open the data framework file in text format to obtain the data framework text.

[0080] Specifically, in this embodiment, the verification item generation module is specifically used to search for element name fields in the data framework text, and use the value of the first element name field found as the name of the starting level of a parameter path; to search for composite type segments in the data framework text according to a first preset search condition, to obtain element name fields in the composite type segments and use their values ​​as the names of the intermediate levels of the parameter path; to search for composite type segments in the data framework text according to a second preset search condition, to obtain attribute name fields in the composite type segments and use their values ​​as the names of the ending levels of the parameter path; and to construct a parameter path based on the starting level name, intermediate level name, and ending level name of the parameter path, wherein each parameter path is a verification item. More specifically, the intermediate levels of the parameter path include several sub-levels, and the starting level is the level preceding the first sub-level in the intermediate level, and the last sub-level in the intermediate level is the level preceding the ending level, but the present invention is not limited thereto.

[0081] Specifically, in this embodiment, the first preset search condition includes a first search start position, a first search end position, and a first search content; and the first search start position is: composite type name = name of the previous level, the first search end position is the last line of the composite type segment, and the first search content is the element name field; and the last line of each composite type segment is the same. More specifically, when the verification item generation module searches for composite type segments in the data framework text according to the first preset search condition, it obtains the first search start position based on the name of the previous level; it searches for the first search content between the first search start position and the first search end position. If the element name field is found, a level is added to the corresponding parameter path, and the value of the found element name field is used as the name of the added level; and the added level is a sub-level in the intermediate level. In addition, when the verification item generation module searches for composite type segments in the data framework text according to the first preset search condition, if the element name field is not found, the name of the previous level is used as the last sub-level of the intermediate level, but the present invention is not limited thereto.

[0082] Specifically, in this embodiment, the second preset search conditions include a second search start position, a second search end position, and a second search content; and the second search start position is: composite type name = the name of the previous level, the second search end position is the last line of the composite type segment, and the second search content is the attribute name field. More specifically, when the verification item generation module searches for the composite type segment in the data framework text according to the second preset search conditions, it obtains the second search start position based on the name of the last sub-level in the intermediate level of the parameter path; it searches for the second search content between the second search start position and the second search end position, and uses the value of the searched attribute name field as the name of the final level. Optionally, the value of the attribute name field includes: name, id, value, ref, etc., but the present invention is not limited thereto.

[0083] Furthermore, in this embodiment, the document verification file generation system can be an executable program (.exe) implemented using Python. When generating a verification file using the document verification file generation system, the document verification file generation system and the data framework text can be placed in the same path (i.e., the same folder). Then, the document verification file generation system can be run in the cmd command line, and the parameters required by the document verification file generation system can be entered. After the document verification file generation system runs, it will automatically import and generate all verification items and list them in an Excel file, thereby obtaining the verification file.

[0084] In summary, this embodiment provides a method and system for generating document verification files. Based on the data framework file published by the TACS security platform, it can automatically identify and construct several verification items, and automatically generate a verification file based on all verification items. The generated verification file is compared with the original verification document to quickly locate changed verification items, thereby determining the scope of the upgrade verification. In this embodiment, the data framework file can be opened in text format to obtain the data framework text, facilitating subsequent automatic identification and construction of verification items. This embodiment, through iterative searching and automatic identification and import of verification items from the data framework text, is faster and more accurate than the original manual identification and listing of verification items. Furthermore, this embodiment is universal and can be used for all projects using the TACS platform baseline and those using the XSD data framework as data input. Simultaneously, after the TACS platform baseline is upgraded and the data framework file is updated, it can quickly identify changed verification items, thereby quickly determining the scope of the upgrade verification.

[0085] Although the present invention has been described in detail through the preferred embodiments above, it should be understood that the above description should not be considered as a limitation of the present invention. Various modifications and substitutions to the present invention will be apparent to those skilled in the art after reading the above description. Therefore, the scope of protection of the present invention should be defined by the appended claims.

Claims

1. A method for generating document verification files, used for document verification in a TACS system, wherein the TACS system runs on the TACS security platform; characterized in that, The document verification file generation method includes: Obtain the latest data framework file released by the TACS security platform; Construct several validation items based on the data framework file; Generate a verification file based on all the aforementioned verification items; and The generated verification file is compared with the original verification file to determine the scope of the upgrade verification. Before performing the step of constructing several validation items based on the data framework file, the method further includes: opening the data framework file in text format to obtain the data framework text; The steps for constructing several validation items based on the data framework file include: Search the element name field in the data frame text, and use the value of the first element name field found as the name of the starting level of a parameter path; The composite type segment in the data framework text is searched according to the first preset search criteria to obtain the element name field in the composite type segment and use its value as the name of the intermediate level of the parameter path. The data framework text is searched according to the second preset search criteria to obtain the attribute name field in the composite type segment and use its value as the name of the final level of the parameter path; and A parameter path is constructed based on the starting level name, the intermediate level name, and the ending level name of the parameter path, and each parameter path is a verification item.

2. The document verification file generation method as described in claim 1, characterized in that, The data framework file is an xsd file.

3. The document verification file generation method as described in claim 1, characterized in that, The intermediate levels of the parameter path include several sub-levels, and the starting level is the level preceding the first sub-level in the intermediate level, and the last sub-level in the intermediate level is the level preceding the ending level.

4. The document verification file generation method as described in claim 3, characterized in that, The first preset search conditions include a first search start position, a first search end position, and a first search content; and the first search start position is: composite type name = name of the previous level, the first search end position is the last line of the composite type segment, and the first search content is the element name field; and the last line of each composite type segment is the same.

5. The document verification file generation method as described in claim 4, characterized in that, The steps for searching for composite type segments in the data frame text according to the first preset search criteria include: The starting position of the first search is obtained based on the name of the previous level; and The first search content is searched between the first search start position and the first search end position. If the element name field is found, a level is added to the corresponding parameter path, and the value of the searched element name field is used as the name of the added level; and the added level is a sub-level in the intermediate level.

6. The document verification file generation method as described in claim 5, characterized in that, The step of searching for composite type segments in the data framework text according to the first preset search conditions further includes: if no element name field is found, the name of the previous level is taken as the last sub-level of the intermediate level.

7. The document verification file generation method as described in claim 3, characterized in that, The second preset search conditions include a second search start position, a second search end position, and a second search content; and the second search start position is: composite type name = name of the previous level, the second search end position is the last line of the composite type segment, and the second search content is the attribute name field.

8. The document verification file generation method as described in claim 7, characterized in that, The steps for searching for composite type segments in the data frame text according to the second preset search criteria include: The second search starting position is obtained based on the name of the last sub-level in the intermediate level of the parameter path; and The second search content is searched between the second search start position and the second search end position, and the value of the searched attribute name field is used as the name of the end level.

9. A document verification file generation system for document verification in a TACS system, wherein the TACS system runs on a TACS security platform; characterized in that, The document verification file generation system includes: The data framework file acquisition module is used to acquire the latest data framework file released by the TACS security platform. A verification item generation module, connected to the data framework file acquisition module, is used to construct several verification items based on the data framework file. A verification file generation module, connected to the verification item generation module, is used to generate a verification file based on all the verification items; and The comparison module, connected to the verification file generation module, is used to compare the generated verification file with the original verification file to determine the scope of the upgrade verification. It also includes: a text acquisition module, which is connected to the data framework file acquisition module and the verification item generation module respectively, and is used to open the data framework file in text form to obtain the data framework text; The verification item generation module is specifically used to search for the element name field in the data frame text, so as to use the value of the first element name field found as the name of the starting level of a parameter path; The composite type segment in the data framework text is searched according to the first preset search criteria to obtain the element name field in the composite type segment and use its value as the name of the intermediate level of the parameter path. The data framework text is searched according to the second preset search criteria to obtain the attribute name field in the composite type segment and use its value as the name of the final level of the parameter path; and A parameter path is constructed based on the starting level name, the intermediate level name, and the ending level name of the parameter path, and each parameter path is a verification item.

10. The document verification file generation system as described in claim 9, characterized in that, The data framework file is an xsd file.

11. The document verification file generation system as described in claim 9, characterized in that, The intermediate levels of the parameter path include several sub-levels, and the starting level is the level preceding the first sub-level in the intermediate level, and the last sub-level in the intermediate level is the level preceding the ending level.

12. The document verification file generation system as described in claim 11, characterized in that, The first preset search conditions include a first search start position, a first search end position, and a first search content; and the first search start position is: composite type name = name of the previous level, the first search end position is the last line of the composite type segment, and the first search content is the element name field; and the last line of each composite type segment is the same.

13. The document verification file generation system as described in claim 12, characterized in that, When the verification item generation module searches for composite type segments in the data frame text according to the first preset search conditions... The starting position of the first search is obtained based on the name of the previous level; as well as The first search content is searched between the first search start position and the first search end position. If the element name field is found, a level is added to the corresponding parameter path, and the value of the searched element name field is used as the name of the added level; and the added level is a sub-level in the intermediate level.

14. The document verification file generation system as described in claim 13, characterized in that, When the verification item generation module searches for composite type segments in the data framework text according to the first preset search conditions, if no element name field is found, the name of the previous level is used as the last sub-level of the intermediate level.

15. The document verification file generation system as described in claim 11, characterized in that, The second preset search conditions include a second search start position, a second search end position, and a second search content; and the second search start position is: composite type name = name of the previous level, the second search end position is the last line of the composite type segment, and the second search content is the attribute name field.

16. The document verification file generation system as described in claim 15, characterized in that, When the verification item generation module searches for composite type segments in the data frame text according to the second preset search conditions... The second search starting position is obtained based on the name of the last sub-level in the intermediate level of the parameter path; as well as The second search content is searched between the second search start position and the second search end position, and the value of the searched attribute name field is used as the name of the end level.

Images