JP5103338B2 - Electronic file analysis technology - Google Patents

Description

    The present disclosure generally relates to systems and methods for analyzing practical electronic files, and more particularly to electronic file analysis techniques.

    Many software programs are customizable at some level. To easily customize software, many software programs can contain one or more programs so that the software does not need to be compiled and recompiled every time the customization changes. An electronic configuration file is used. This configuration file is formed in a format known by a specific software program. For example, each line of a configuration file includes a key name and a key value. This configuration file is read by the software program. When the software program reads and parses the configuration file, it can look for a specific format. For example, the software program can assume that the key name precedes the key value on every line of the configuration file. If the configuration file described above does not match the format that the software program can read, the software program cannot read the configuration file and the software program is not executed, or The software program can also use default configuration parameters. In either instance, the usefulness of the configuration file will be reduced or eliminated.

    Unfortunately, the format for the electronic configuration file is different for each software program. In an extreme example, each software program requires a different configuration file format. These differences are not important, or the differences may vary greatly.

    The problem with the state of the art, however, is that the electronic configuration file may need to be in a very specific format. If they deviate from a predetermined format, one or more values of the configuration file or all configuration files may not be readable by the software program. This disadvantage can reduce the effectiveness of the configuration file or completely reduce its effectiveness.

    One configuration management system is operable to read one or more electronic configuration files for one or more entire servers. The configuration management system can also check multiple configuration files and perform operations on the configuration files. For example, the configuration management system can check for differences between different configuration files, or can change one or more configuration files. While many standardized configuration file formats are available, there is no requirement in the software industry to standardize configuration files. As a result, when a software program is added to the configuration management system, the user must verify that the software program's configuration file is compatible with the configuration management system. Such work requires the user to interact with the format for one or more configuration files, and requires knowledge of the user.

    In view of the foregoing, it can be understood that there are significant problems and disadvantages associated with current electronic file analysis techniques.

    The present invention discloses a plurality of electronic file analysis techniques.

    In one particular exemplary embodiment, the parsing technique is embodied as an parsing device that includes an input module that reads one or more electronic files; and stores one or more syntactic elements. A conversion module for converting one or more of the one or more syntax elements to parse one or more electronic files read by the input module; and An output module capable of generating one or more normalized electronic files from the one or more analyzed electronic files.

    As another aspect of this embodiment of the present invention, this analysis apparatus is characterized in that the input module, the syntax element module, the conversion module, and the output module are configured to be communicable with each other.

    According to another aspect of this embodiment of the present invention, the analysis apparatus further stores a syntax element storage that stores one or more syntax elements used to analyze one or more analyzed electronic files. It is characterized by having a part.

    As another aspect of this embodiment of the present invention, in the analyzing apparatus, the syntax element is a second one or more converted syntax elements used for analyzing one or more electronic files. It is characterized by being configured to be converted into

    As another aspect of this embodiment of the present invention, in the analyzing apparatus, the syntax element is configured to be converted and applied to the electronic file until a normalized file is formed. It is characterized by.

    In another particular exemplary embodiment, the parsing technique is embodied as a parsing method, the parsing method providing one or more syntax elements; one or more features having one or more features Read a plurality of electronic files; the converted syntax element uses at least one of one or more features included in the one or more electronic files, and the one or more Converting at least one of the one or more syntax elements into a converted syntax element; and one or more of the converted syntax elements to parse the one or more electronic files Are applied to the one or more electronic files; each step is characterized by a feature.

    As another aspect of this embodiment of the present invention, the analysis method further comprises the step of generating one or more normalized files from the one or more analyzed electronic files. It is characterized by that.

    As another aspect of this embodiment of the present invention, the analysis method further includes the one or more converted syntax elements used to analyze the one or more analyzed electronic files. It is characterized by comprising the step of storing.

    In another aspect of this embodiment of the present invention, the parsing method is configured such that the syntax element is converted into a second syntax element used to parse the one or more electronic files. It is characterized by that.

    In another aspect of this embodiment of the present invention, the parsing method is configured such that the syntax element is converted and applied to the electronic file until a normalized file is formed. It is characterized by.

    According to another aspect of this embodiment of the present invention, at least one signal input to at least one carrier, wherein the computer process for performing the method of claim 6 is performed. At least one signal input to at least one carrier for transmitting instructions of a computer program configured to be readable by the at least one processor for instructing the processor It is characterized by that.

    In another aspect of this embodiment of the present invention, instructions are provided to at least one processor that is a carrier readable by at least one processor and that executes a computer process for performing the method of claim 6. And a carrier wave readable by at least one processor for carrying instructions of a computer program configured to be readable by the at least one processor. .

    In another particular exemplary embodiment, the parsing technique is embodied as an parsing system, the parsing system comprising means for preparing one or more syntactic elements; and one having one or more features. Means for reading one or more electronic files; and the converted syntax element uses at least one of one or more features included in the one or more electronic files, Or means for converting at least one of the one or more syntax elements into a plurality of converted syntax elements; and the converted syntax to parse the one or more electronic files Means for applying one or more of the elements to the one or more electronic files.

    According to another aspect of this embodiment of the present invention, the present invention is further characterized by comprising means for generating one or more normalized files from the one or more analyzed electronic files. Yes.

    As another aspect of this embodiment of the present invention, it further comprises means for storing the one or more converted syntax elements used for analyzing the one or more analyzed electronic files. It is characterized by that.

    According to another aspect of this embodiment of the present invention, the syntax element is configured to be converted into a second syntax element used for analyzing the one or more electronic files. Yes.

    Another aspect of this embodiment of the invention is characterized in that the syntax element is transformed and applied to the electronic file until a normalized file is formed.

    The present invention will be disclosed in further detail with reference to the following illustrative examples and the accompanying drawings. In addition, although this invention is demonstrated with reference to an Example, this invention is not the meaning limited to them. In other words, in addition to the contents described in this specification, additional implementations, various modifications, other examples, implementations in other fields, and the like will be apparent to those skilled in the art from the foregoing description and accompanying drawings. Are obvious and all fall within the scope of the disclosure and the claims of the present invention. Also, it should be understood by those skilled in the art that the present invention can be used in these various embodiments.

    FIG. 1 shows a diagram-level overview of the general flow of information to and from the device 101 according to one embodiment of the present disclosure. Device 101 is described in more detail in the following figures, but is operable to read one or more electronic files 110 of a known or unknown type, and may be one or more regular ones. An electronic file 120 can be generated. The normalized electronic file 120 is in a unified format that can be read by other programs or processes. For example, the normalized electronic file 120 may be in the form of an extensive markup language (“XML”) with a predefined document format definition. The device 101 can perform data communication with one or a plurality of syntax element storage units 105. The electronic file 110 in an unknown format does not necessarily need to be in an unknown format for other elements in the system 100 including the device 101 and the syntax element storage unit 105. Rather, the electronic file 110 may be in an unknown format if the format is not obvious. For example, the electronic file 110 is read by the device 101, but when reading the electronic file 110, the format need not be clearly known by the device 101. Thus, even if the format is ultimately known or identified by the device 101, the format of the electronic file 110 may be unknown at the time of input.

    Here, FIG. 2 shows an outline of a diagram level of the file analysis system 200 according to the embodiment of the present invention. The file analysis system 200 can include an input module 210, an output module 220, a conversion module 230, and a syntax element module 240. Each module can communicate with a plurality of other modules. In some embodiments, the one or more modules are included in one physical system, but this is not necessary. In other embodiments, the one or more modules may be located on one or more physical systems, such as one or more computers. The one or more computers and one or more modules on the one or more computers can communicate via a network. The device 101 can include one or more modules, such as an input module 210, an output module 220, a conversion module 230, a syntax element module 240, and the like. Each module is described in further detail below.

    The input module 210 can read one or a plurality of electronic files. The electronic file may be located in the same system as the input module 210 or may be located in another system that can communicate with the input module 210. For example, the input module 210 can generate one or more electronic files or move to a network of storage areas, or the input module 210 can receive one or more electronic files from a remote system. One or a plurality of networks such as the Internet can be used for reading.

    The syntax element module 240 can communicate with the syntax element storage unit 105. The syntax element module 240 can send or receive one or more syntax elements to or from the syntax element storage unit 105. The syntax element storage unit 105 can include one or more syntax elements. The syntax element storage unit 105 may be included in one or a plurality of electronic files, or may be included in one or a plurality of databases. The syntax element module 240 and the syntax element storage unit 105 may operate in the same system, or may be separately disposed on one or more systems, and may be one or more networks or other. You may arrange | position so that communication with this communication apparatus is possible.

    The conversion module 230 may be operable to read one or more of the syntax elements and may be operable to convert one or more of the one or more syntax elements. The transformations performed on one or more syntax elements according to embodiments of the present invention are disclosed in further detail below.

    The output module 220 is operable to generate one or more electronic files. The output module 220 can be placed in the same system as the input module 210 or can be placed in another system so that it can communicate with the input module 210. For example, the output module 220 can generate one or more electronic files or move to a storage area network or other networked file system. Although not limited to these networks, one or a plurality of electronic files on a remote system can be generated or moved including the Internet.

    Here, FIG. 3 shows a flowchart for analyzing an electronic file of a potentially known format according to an embodiment of the present invention. Embodiments according to the present disclosure are described using an electronic configuration file. Although this disclosure can be operated by reading and analyzing one or more electronic configuration files, it is not an essential requirement that the electronic file be a configuration file. Accordingly, the configuration file embodiment used does not limit the present disclosure.

In embodiments of the disclosure, one or more Configurations
A description of Template Language (configuration template language “CTL”) is available. One CTL description corresponds to one configuration file type. In alternative embodiments, the description of one or more CTLs may correspond to one or more configuration file types. For example, one CTL description may be associated with a standard Windows INI configuration file, and another CTL description may be associated with a standard Apache configuration file. . A typical configuration file is shown in Figure 3a. This exemplary configuration file shown in FIG. 3a may include a comment type, a key type, and a key value type.

    First, as shown in step 301, one or more electronic configuration files are read. Next, as shown in step 302, the description of the CTL associated with the electronic configuration file from step 301 is read. A typical CTL description is shown in Figure 3b. This CTL description shown in FIG. 3b relates to the typical configuration file seen in FIG. 3a. This CTL description can use standard notation in the associated configuration file. For example, with respect to the example configuration file and CTL descriptions in FIGS. 3a and 3b, the “/ * EMX_COMMENT * /” line in FIG. 3b appears between “/ *” and “* /”. Indicates that the text is designated as “EMX_COMMENT” for parsing. Furthermore, the “#EMX_COMMENT” line in FIG. 3b indicates that the text associated with the “#” sign is designated as “EMX_COMMENT”.

    Next, as shown in step 304, the description of the CTL associated with the above configuration file is parsed into a specific value or “token”. An exemplary token for the description of the exemplary CTL shown in FIG. 3b is shown in FIG. 3c. A typical glossary associated with these tokens is shown in Figure 3d. A typical “syntax” used to parse the CTL description is shown in FIG. 3e. Apart from the CTL description for each electronic configuration file format, this syntax does not apply to the electronic configuration file itself. In FIG. 3e, for example, this exemplary “syntax” may be a meta-syntax notation in extended Bacchus-Naur notation (“EBNF”). For example, a comment starts with a “#” character and is displayed on a single line. As shown in the exemplary glossary of FIG. 3d, “CM_B” can indicate the beginning of a comment and “CM_E” can indicate the end of a comment. The “CM_B = #, CM_E = NULL” line shown in Figure 3c indicates that the comment begins with a “#” character and ends with a “NULL” character or a character defined as the end of the line in the configuration file. Represents. Similarly, the line “CM_B = / *, CM_E = * /” shown in FIG. 3c indicates that the comment starts with the “/ *” character and ends with “* /”. Similar tokens can also be used to indicate, for example, sections, keys, and values within a single configuration file.

    As shown in step 306, these tokens are stored with the device 101 and can therefore be used to parse a similar configuration file. In this way, steps 302 and 304 are not necessary to parse a configuration file having a format in which the associated CTL description has already been parsed into a token. These tokens can also be used later for “unknown” configuration files.

    As shown in step 308, the token described above may be displayed as a set of one or more syntax elements or syntax symbols. An exemplary syntax element derived from the token shown in FIG. 3c is shown in FIG. 3f. For example, one syntax element is “/ * * /”. This corresponds to the “CM_B = / *, CM_E = * /” line shown in FIG. 3c. The syntax element is stored for future use so that device 101 can parse the unknown configuration file. A syntax element generated by such a method is formed of an element set. For example, one or more syntax elements in a set of syntax elements associated with a given file format is a “section” element, which is a single section of the configuration file. Means where a section begins or ends. One or more other syntax elements in the same set as the set are “comment” elements, meaning where the comment begins or ends. These syntax elements or syntax symbols are used as a starting point for analyzing the subject file to create one or more sets of known syntax elements.

    As shown in step 310, the plurality of tokens created by analyzing the CTL description can be used to analyze the configuration file. Typical tokens created are shown in FIG. 3c, and these tokens can be used to parse the configuration file in a normalized field. This normalization may be in the form of an extensive markup language (“XML”) document with a predefined document type definition. For example, the annotation field shown in the typical configuration file shown in Figure 3a can be used in two different ways (for example, a comment line starting with "#" or a comment line with "/ *" and "* /"). The method of expressing the start point and the end point). Both comment types can be designated as comments if correctly parsed by the token associated with the subject configuration file. These comments are then defined in a normalized way. For example, all comments are normalized to start with a “/ *” character and end with a “* /” character. The method thus uses the CTL description to read one or more types of configuration files, and then one or more normalized types for further use. Generate a configuration file.

    The embodiment thus has the ability to represent the configuration file format with a CTL description created using a typical and intuitive syntax. This configuration format is modeled intuitively using one or more CTL descriptions, which can be used to parse the configuration file. In this embodiment, one embodiment of the present invention can use a CTL description for each configuration file type. If the CTL description does not describe a specific configuration file, the configuration file cannot be parsed correctly using the CTL description. Also, if the CTL description is not available in the configuration file, the configuration file can still be parsed.

    FIG. 4 shows a flowchart for analyzing an electronic file in an unknown format according to the embodiment of the present invention. First, in step 402, a configuration file is read. In step 404, try to parse the configuration file using syntax elements obtained from a known file. In other embodiments, these syntax elements may be supplied beyond obtaining a well-known CTL description associated with a well-known file format. Each available syntax element may be used, or the configuration file may be parsed using a smaller subset of available syntax elements. If the configuration file is parsed by one or more of the available syntax elements, the configuration file is marked as “known” as shown in step 406 and the configuration file is The file can be parsed using its available syntax elements to create a normalized configuration file. If the file format of this configuration file is not already associated with the one or more syntax elements described above, the file format of the configuration file from step 402 will then parse the document. Associated with one or more syntax elements used for the purpose.

    And if the existing syntax element is not used successfully, an alternative set of syntax elements is generated from the one or more syntax elements used in step 404. A method for generating an alternative set of syntax elements is shown in FIG. 5, and steps 408 to 418 are described subsequently.

    Turning now to FIG. 5, a method for converting one or more syntax elements according to an embodiment of the present invention is disclosed. In step 502, a controlled quasi-random intersection operation is performed between a combination of one or more sets of syntax elements. An intersection operation consists of, for example, the step of reducing the one or more syntax elements to smaller parts and combining the smaller parts into one or more syntax elements. . The set of all possible combinations of the original plurality of syntax elements can be reduced by removing one or more of the new syntax elements that do not match the parsing rules. For example, a set of parsing rules is shown in FIG. The application of this parsing rule is designed to reduce the number of syntax elements that can be applied to the configuration file.

    Next, in step 504, the target configuration file is utilized and scanned for repeated character groups. For example, the target configuration file may have a high probability of the “/ *” character set. In that case, higher priority is given to characters and groups of characters including non-alphanumeric characters. This is because these characters mean that a character or group of characters is used as part of the format. A probability distribution can be formed using a scan of the repetitive characters in the target configuration file.

    Next, at step 506, one or more conversion operations are performed on the new syntax symbol. This conversion uses one or more of the one or more characters or character groups obtained in step 504 and converts them to one or more of the new syntax elements generated in step 502. Insert it. That is, the resulting new syntax element set will not be randomly formed, but will be formed using repeated character group scanning of the target configuration file.

    In step 508, a new set of syntax elements is generated using the transformation syntax elements generated in step 506.

    It should be noted that steps 502 to 508 shown in FIG. 5 can be repeated in parallel and executed in parallel. For example, one device performs steps 508 to 508 to generate a first syntax element set for conversion, and another device steps from step 502 to generate a second syntax element set for conversion. 508 may be performed. This process may be performed in parallel by multiple devices, or may be configured such that one device has the ability to generate multiple sets of transformed syntax elements in parallel. Furthermore, each set of translated syntax elements may be applied to one or more configuration files in parallel. For example, a parallel process that generates a set of translated syntax elements may be used for multiple unknown configuration files simultaneously.

    Returning to FIG. 4, an attempt is made to parse the configuration file with the new set of translated syntax elements, as shown in step 412.

    If step 508 is successful and the configuration file is parsed successfully, the configuration file is then marked as “known” and the configuration file uses the available syntax elements. And, as shown in step 410, a normalized configuration file is generated. If the file format is not associated with the one or more syntax elements described above, the file format of the configuration file from step 402 is then used to parse the document. Associated with the converted syntax elements. This new set of translated syntax elements is stored for a plurality of files having the same format as the format of the “known” configuration file at step 402.

    If the configuration file is not parsed using the new set of translated syntax elements generated in step 408, a counter indicating the total number of iterations is incremented, as shown in step 414. . If the number of iterations reaches a predetermined number of times, the file is marked as “unknown” and the configuration file is converted to a syntax element or other source as shown in step 416. Is stored for further analysis using a new set of syntactic elements. Still further, other embodiments may be configured to inform the operator in other ways that an error message has been generated or that the configuration file has not been parsed successfully. If the counter has not reached a predetermined number of times, a new set of translated syntax elements is generated, as shown in step 418. An iteration from step 418 to step 408 is performed to generate one or more new sets of translated syntax elements. In other embodiments, if the configuration file is unsuccessful with the first set of converted syntax elements, the conversion is continued until the configuration file is parsed by the set of converted syntax elements. A plurality of new sets of generated syntax elements may be generated.

    As noted above, it should be noted that the embodiments of the present invention generally include processing of input data and generation of output data. This input data processing and output data generation can be performed by hardware or software. For example, as described above, a specific electronic component may be used in a computer or a similar device or related circuit to perform the function of analyzing the configuration file according to the embodiment of the present invention. . As a further alternative, one or more processors operating according to pre-stored instructions may be configured to perform the function of analyzing a configuration file in accordance with embodiments of the present invention as described above. Good. If this is the case, the instructions are stored on a carrier (eg, a magnetic disk or other storage medium) readable by one or more processors, or the instructions are received by one or more carriers. Sending to one or more processors via one or more signals is within the scope of the present disclosure.

    The scope of the invention is not limited by the specific embodiments described herein. It will be apparent to those skilled in the art from the foregoing description and accompanying drawings that various changes can be made in addition to the contents described in this specification. Accordingly, it is understood that such modifications are also within the scope of the following appended claims. Furthermore, although the present invention has been described herein on the premise of a specific implementation in a specific environment, its usefulness is not limited thereto, and the present invention is useful for any purpose or environment. It can be understood by those skilled in the art. Accordingly, the following claims should be construed broadly in view of the description and the technical spirit of the disclosed invention.

    In order that the present disclosure may be more fully understood, description will be made with reference to the accompanying drawings. Each element of the invention is given a reference number. These drawings should not be construed as limiting the disclosure, but are merely for illustrative purposes.

FIG. 1 shows a system level block diagram according to one embodiment of the present disclosure, which includes an input electronic file and an output electronic file. FIG. 2 shows a system level block diagram according to one embodiment of the disclosed subject matter and shows the actual modules. FIG. 3 shows a flow chart for analyzing an electronic file in a well-known format according to one embodiment of the present disclosure. FIG. 3a shows an exemplary electronic configuration file according to one embodiment of the present disclosure. ; FIG. 3b shows a description of an exemplary configuration template language according to one embodiment of the present disclosure. FIG. 3c shows an exemplary token according to one embodiment of the present disclosure. FIG. 3d shows an exemplary glossary of token definitions according to one embodiment of the present disclosure. FIG. 3e shows one potential syntax list for the description of the configuration template language according to one embodiment of the present disclosure. FIG. 3f shows an exemplary list of potential syntax elements or syntax symbols according to one embodiment of the present disclosure. FIG. 4 shows a flow chart for analyzing an unknown format electronic file according to one embodiment of the present disclosure. FIG. 5 shows a flowchart for converting one or more syntax elements of FIG. 4 according to one embodiment of the present disclosure. FIG. 5a shows an exemplary list of conversion rules according to one embodiment of the present disclosure.

Claims (22)

A device for analyzing electronic files:
An input module for reading one or more electronic files having one or more features ;
A syntax element module for storing one or more syntax elements;
Analyzing one or more electronic files read by the input module using one or more of one or more syntax elements, and if the analysis is not possible, the one or more syntax elements Is converted into a syntax element that uses at least one of one or more features included in the one or more electronic files, and the input module is converted using the converted syntax element. A conversion module for analyzing one or more electronic files read by
An output module capable of generating one or a plurality of normalized electronic file from one or more electronic files before Symbol analysis; and
Electronic file analysis apparatus characterized by having a memory for providing instructions to at least one of coupled to a processor the at least one processor. The input module, the syntax elements module, the converting module, before SL output module and the memory, the electronic file analysis apparatus according to claim 1, characterized in that it is capable of communicating with each. And a syntax element storage unit for storing one or more converted syntax elements used for analyzing the one or more analyzed electronic files. Item 3. The electronic file analysis device according to Item 1.   The syntax element is configured to be converted into a second one or more converted syntax elements used to parse one or more electronic files. The electronic file analysis apparatus described.   The electronic file analysis apparatus according to claim 1, wherein the syntax element is configured to be converted and applied to the electronic file until a normalized file is formed. In an analysis method that analyzes multiple electronic files:
Comprising: providing one or a plurality of syntax elements;
And one or more write-free step reads the electronic file having one or more features;
The read one or more electronic files are analyzed using one or more of one or more syntax elements, and if the analysis is not possible, they are included in the one or more electronic files. Converting at least one of the one or more syntax elements into a syntax element that utilizes at least one of the one or more features to be selected ; and one or more of the converted syntax elements Analyzing the one or more electronic files using:
A method for analyzing an electronic file, comprising: 7. The electronic file analysis method according to claim 6, further comprising the step of generating one or more normalized files from the one or more analyzed electronic files. 7. The electronic file of claim 6, further comprising the step of storing the one or more translated syntax elements used to parse the one or more parsed electronic files. Analysis method.   7. The electronic file analysis method according to claim 6, wherein the syntax element is configured to be converted into a second syntax element used for analyzing the one or more electronic files.   The electronic file analysis method according to claim 6, wherein the syntax element is configured to be converted and applied to the electronic file until a normalized file is formed. 7. A storage medium readable by at least one processor, readable by said at least one processor for instructing at least one processor to execute a computer process for performing the method of claim 6. A storage medium readable by at least one processor for storing instructions of a computer program configured as described above. In a system that analyzes multiple electronic files:
Means for preparing one or more syntax elements;
Means for reading one or more electronic files having one or more features;
The read one or more electronic files are analyzed using one or more of one or more syntax elements, and if the analysis is not possible, they are included in the one or more electronic files. Means for converting at least one of said one or more syntax elements into a syntax element that utilizes at least one of said one or more features; and
One or with a plurality of pre-Symbol transformed syntax elements, means for analyzing the one or more electronic files;
Analysis system for electronic file, characterized in that it comprises and. 13. The electronic file analysis system according to claim 12 , further comprising means for generating one or more normalized files from the one or more analyzed electronic files. 13. The electronic file of claim 12, further comprising means for storing the one or more converted syntax elements used to parse the one or more parsed electronic files. Analysis system. 13. The electronic file analysis system according to claim 12 , wherein the syntax element is configured to be converted into a second syntax element used for analyzing the one or more electronic files. 13. The electronic file analysis system according to claim 12 , wherein the syntax element is converted and applied to the electronic file until a normalized file is formed.   The conversion module for converting at least one of the one or more syntax elements into a new syntax element;
  Performing a cross operation between a combination of one or more sets of syntax elements to generate the one or more new syntax elements;
  Scan one character or group of characters in the one or more electronic files; and
  2. The electronic file analysis apparatus according to claim 1, wherein the one character or character group is inserted into the one or more new syntax elements.   Converting at least one of the one or more syntax elements into a new syntax element;
  Performing a cross operation between a combination of one or more sets of syntax elements to generate the one or more new syntax elements;
  Scanning one or more characters in the one or more electronic files; and
  The electronic file analysis method according to claim 6, further comprising a step of inserting the one character or character group into the one or more new syntax elements.   The converting means for converting at least one of the one or more syntax elements into a new syntax element;
  Performing a cross operation between a combination of one or more sets of syntax elements to generate the one or more new syntax elements;
  Scan one character or group of characters in the one or more electronic files; and
  13. The electronic file analysis system according to claim 12, wherein the one character or character group is inserted into the one or more new syntax elements.   The electronic file analysis apparatus according to claim 1, wherein the one or more electronic files are electronic configuration files used in a software program.   7. The electronic file analysis method according to claim 6, wherein the one or more electronic files are electronic configuration files used in a software program.   The electronic file analysis system according to claim 12, wherein the one or more electronic files are electronic configuration files used in a software program.

Images