JP2004213488A - Data consistency checking device and data consistency checking method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a data consistency checking device wherein new creation, modification, or addition of a checking condition of data used for a data checking program is easily conducted even by a person who does not have expertise, and recheck after error correction of the data is conducted in a short period of time. <P>SOLUTION: In a checking condition creating part 16, a checking condition logical formula, which corresponds to a checking condition to check the error of soft data of a switching equipment or the like and which is used when a data checking program 30 of the soft data is generated, is created by combining an operator and a function of a symbol with a data name of the soft data. Each checking condition logical formula can be created by combination of simple symbols. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a data consistency check device and a data consistency check method for checking whether there is an error in software data for controlling and operating hardware such as a communication system including a large number of elements.
[0002]
[Prior art]
An exchange is hardware controlled by a computer, and requires software data to operate. There are two types of software data, system data and station data.
Since the system data is a system program for controlling and operating the exchange, it is common data for the same type of exchange. On the other hand, the office data is data defining hardware configuration information in the local exchange, network information between the exchanges, and the like. The office data must be set individually (uniquely) for each exchange. The system program acquires the information of the office data and operates the exchange.
[0003]
The station data will be described in more detail. There are two types of station data: NW (Network) data and NE (Network E1 element) data. The NW data is data commonly used by the exchanges, and typical examples include data commonly used by all the exchanges, such as the names of exchanges and charging information in the network. On the other hand, NE data includes data defining hardware information and the like of each exchange, such as data indicating the hardware mounting state such as the number of CPUs installed in the own exchange and the number of lines held.
[0004]
The NW data and the NE data are defined for each setting purpose, and are described in a text file format. These are called definition fields. Station data is a collection of definition fields.
By the way, in the third generation mobile phone system, this network is configured by an exchange called MMS (Mobile Multimedia Switch). There are 41 types of NW data and 84 types of NE data that are actually used in the MMS. Depending on the definition, there are some definitions that contain data of thousands of records in one definition, so it is necessary to set data of about 20,000 records in total per exchange.
[0005]
The station data is created by the facility design system. In a facility design system, a GUI (Graphic User Interface) is provided instead of directly inputting a value of a definition in a text image, so that a definition in which similar data is input can be input from the same screen. In addition, by preparing a screen of a system device frame image, a device has been devised so that the value of the definition field can be easily input.
[0006]
In addition, the facility design system is provided with a function of checking the consistency of the input value in addition to the function of supporting the input of station data. If erroneous office data is input to the exchange, an error occurs in the exchange or, in the worst case, the exchange does not operate, so that these are prevented beforehand.
[0007]
There are three types of station data consistency checks: entry value check, item-to-item check, and definition-to-definition check. The entry value check checks the value of each item in the definition. The item-to-item check checks a value between items in the definition. The definition-to-definition check is for checking a value that extends between definition fields.
[0008]
The function of performing these checks is made by a C language program. When the station data check conditions are changed or added in accordance with the change or addition of the station data, the programmer changes the program, compiles again, and implements the program. Each of the above checks is performed on the entire station data by the installed program.
[0009]
However, in this data consistency check device, when the data check condition is changed or added, the data check program must be changed and compiled each time, so that the data check can be easily performed. In addition, there is a disadvantage that the program cannot be changed unless a person with specialized knowledge can change the program.
[0010]
As an apparatus capable of solving such a defect, there is, for example, an input check method described in Patent Document 1. In the device of this patent document 1, the check content for each input item is patterned (check pattern), set in a check pattern file in advance, and arbitrarily defining which check pattern to use in the screen control file. In this way, when the check specification (check condition) of each input item is changed, processing is performed by changing the definition or the check pattern without changing the program itself.
[0011]
[Patent Document 1]
JP-A-6-274389 (refer to FIG. 1).
[0012]
[Problems to be solved by the invention]
However, in the method of Patent Document 1, since the check pattern defined in accordance with the change of the data check condition is set in advance, there is a check pattern corresponding to the changed or added data check condition. If not, a new check pattern must be created or the check pattern must be changed and used. For this reason, there is a problem that the check pattern can be changed or added only by a person having specialized knowledge.
[0013]
Also, when checking data consistency with a check program after changing or adding a check pattern, it is necessary to check the entire data. Even if it is corrected and rechecked, the entire check must be performed instead of only the error part. Therefore, there is a problem that it takes time to recheck the data.
[0014]
The present invention has been made in view of such a problem, and new creation, change, or addition of data check conditions used in a data check program can be easily performed even by those who do not have expert knowledge. It is another object of the present invention to provide a data consistency check device and a data consistency check method capable of performing a recheck after correcting an error in data in a short time.
[0015]
[Means for Solving the Problems]
In order to achieve the above object, a data consistency check device according to claim 1 of the present invention converts software data for controlling and operating hardware of an equipment system including a large number of elements into an error of the software data. In a data consistency check device for checking whether there is no error according to a check condition for checking, a first database for storing the soft data for each data name, and a logical expression for the check condition A second database storing an operator and a function that are symbols to be represented by: and a corresponding data name is read from the first database in accordance with an input instruction for expressing the check condition by a logical expression; After reading the corresponding operator and function from the second database, the data name, the operator and Creating means for creating a check condition logical expression corresponding to each of the check conditions by combining the functions; and a third means for storing the individual check condition logical expressions created by the create means in association with unique information. Database, analysis means for analyzing the syntax of the check condition logical expression stored in the third database, and a program in which the basic part for checking the soft data is determined in advance by the analysis result of the analysis means. Is used as a parameter to generate a check program for checking the error of the soft data, and a check means for checking the error of the soft data according to the check program.
[0016]
According to this configuration, the check condition logical expression corresponding to the check condition for checking for an error in the soft data and used when generating the check program for the soft data is represented by a symbol in the data name of the soft data. Since it is created by combining operators and functions, a check condition logical expression can be created by a simple combination of symbols.
[0017]
According to a second aspect of the present invention, in the data consistency check apparatus according to the first aspect, the creating unit is configured to, based on the input instruction for changing the check condition logical expression, read the corresponding check condition logical expression from the third database. After the reading, the check condition logical expression is changed.
According to this configuration, the check condition logical expression can be arbitrarily changed after being created.
[0018]
The data consistency check device according to claim 3 of the present invention is the data consistency check device according to claim 1 or 2, wherein the creating means uses the check condition logical expression stored in the third database to create a new check condition logical device. It is characterized by creating an expression.
According to this configuration, the check condition logical expression once created can be used, so that the check condition logical expression can be efficiently created.
[0019]
According to a fourth aspect of the present invention, there is provided a data consistency check device according to any one of the first to third aspects, wherein a check state indicating a good or bad check result by the check means is associated with the unique information. Management means for describing in a table by means of a table, and acquisition means for acquiring only a check condition logical expression of unique information whose check state indicates a failure described in the table from the third database and outputting the formula to the analysis means. It is characterized by having.
[0020]
According to this configuration, the corresponding soft data can be checked using only the check condition logical expression for checking the soft data whose check result is defective.
According to a fifth aspect of the present invention, in the data consistency check device according to the fourth aspect, the management unit may be configured to determine whether the check condition logical expression stored in the third database is changed or the check condition logical expression is changed. When the expression is newly stored, a check state indicating that the check by the corresponding check condition logical expression has not been completed is described in the table in association with the unique information of the check condition logical expression, and the Means for acquiring from the third database only a check condition logical expression of unique information indicating that the check state described in the table indicates the failure or the unfinished at least one, and outputs the check condition logical expression to the analysis means. Features.
[0021]
According to this configuration, when the check condition logical expression is changed, added, or newly created, the corresponding soft data can be checked using only the corresponding check condition logical expression.
The data consistency check device according to claim 6 of the present invention is the data consistency check device according to any one of claims 1 to 5, wherein the facility system is an exchange, and the software data is data for controlling and operating the exchange. It is characterized by being.
[0022]
According to this configuration, the same effect can be obtained in the exchange as above.
A data consistency check method according to a seventh aspect of the present invention is a method for checking software data for controlling and operating hardware of an equipment system including a large number of elements for checking an error in the software data. In a data consistency check method for checking whether there is no error according to a condition, a first database for storing the soft data for each data name, and a symbol for expressing the check condition by a logical expression And a symbol for expressing the check condition in a logical expression in the data name of the soft data in accordance with an input command for expressing the check condition in a logical expression. Check condition theory corresponding to each of the check conditions by combining operators and functions A creating step of creating an expression, a storing step of storing each check condition logical expression created by the creating means in a database in association with unique information, and a syntax of the check condition logical expression stored in the database. An analysis step for analyzing, and a check program for checking an error in the soft data by using the analysis result obtained in the analysis step as a parameter in a program in which a basic part for checking the software data is predetermined. It is characterized by comprising a generating step of generating and a checking step of checking an error of the soft data according to the check program.
[0023]
According to this method, a check condition logical expression corresponding to a check condition for checking an error of the soft data and used when generating a check program for the soft data is represented by a symbol in the data name of the soft data. Since it can be created by combining operators and functions, it is possible to create a check condition logical expression with a simple combination of symbols.
[0024]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
(Embodiment)
FIG. 1 is a block diagram showing a configuration of a data consistency check device according to an embodiment of the present invention.
[0025]
The data consistency check device 10 shown in FIG. 1 checks the consistency of software data (hereinafter, referred to as data) for controlling and operating the exchange, and includes a data storage database 12 to be checked, an operator A function storage database 14, a check condition creation unit 16, a keyboard 18, a check condition storage database 20, a check condition acquisition management unit 24 having a check state management table 22, a syntax analysis unit 28 having a syntax analysis program 26, , A program generation unit 32 for generating the data check program 30, a data check unit 34, a check result output control unit 36, a check result storage unit 38, and a display unit 40.
[0026]
The check target data storage database 12 stores various data to be checked for each data name. For example, the contents described in the A-HUB definition document 51 and the B-HUB definition document 52 which are the specifications of the station data as shown in FIG. 2 are stored as data.
Further, as other specifications relating to the station data, a station data specification 53 shown in FIG. 3 and a specification (FIG. 4) in which the conditions of the entry value check, the item-to-item check, and the definition-to-definition check shown in FIG. Hereinafter, referred to as a check condition specification) 54.
[0027]
The office data specification 53 is a document indicating the configuration of the office data and the check conditions. For example, it is described that the condition of the entry value of the TGN of item number 1 must be within the range of 2048 to 4095, and if a value of 2000 is input, it must be detected as an error. . Only the station data specification 53 can express only the condition of the entry value check. Therefore, the document such as the check condition specification 54 also describes the entry condition, the condition between items, and the condition between definitions. The check conditions described in the check condition specification 54 indicate which data is compared and checked, for example, as indicated by arrows Y1 to Y5 in the A-HUB definition document 51 and the B-HUB definition document 52. Part. Arrow Y1 indicates the data part of the entry value check, arrows Y2 and Y3 indicate the data part of the check between items, and arrows Y4 and Y5 indicate the data part of the check between definitions.
[0028]
The operator / function storage database 14 stores an operator such as <,>, =, && and a function. The operator is for constructing a logical expression such as 0 <A <10. As the function, for example, the definition content of the function shown in the specification 56 as shown in FIG. 5 is stored as data. The meaning of the function is described in, for example, NO. The function length (val) of 4 has the meaning of counting and outputting the length of the character string. By combining such functions and operators, it is possible to easily create a logical expression for limiting character strings.
[0029]
The check condition creation unit 16 reads the names (data names), operators, and functions of the data to be checked from the databases 12 and 14 in accordance with an instruction for creating a check condition logical expression executed by operating the keyboard 18, and performs a check. A conditional logical expression is created, a unique check ID is associated with this check conditional logical expression, and stored in the corresponding check type column in the database 20. That is, the check condition logical expression expresses the check condition described in the check condition specification 54 or the like by a logical expression combining an operator and a function.
[0030]
The check condition creation unit 16 reads the corresponding check condition logical expression from the check condition storage database 20 according to the instruction to change the check condition logical expression from the keyboard 18, and then changes the check condition logical expression. Overwrites the original storage area of the database 20. Further, the check condition creation unit 16 can create a new check condition logical expression using the check condition logical expression stored in the check condition storage database 20.
[0031]
The operation of the above command is performed in accordance with the check condition specification sheet 54. When the check condition of the data is changed or added in accordance with the change or addition of the exchange, or when the data is newly created. It is performed when it is done. The addition of the check condition logical expression is executed by being added to the end of the column of the corresponding check type. In other words, it is performed in the image of adding a one-line record.
[0032]
The check condition acquisition management unit 24 acquires the check condition logical expression stored in the check condition storage database 20 according to the check state management table 22, and outputs this to the syntax analysis unit 28.
FIG. 6 shows an example of the contents of the check state management table 22. The check state management table 22 describes a check ID of a check condition logical expression for each unit name of the exchange, and further describes a data check state according to the corresponding check condition logical expression for each check ID. In the column of the check state, "completed" is described when the check result obtained by the data check described later is OK. When the check result is an error, or when the check condition logical expression is changed, added, or newly stored in the check condition storage database 20, "not implemented" is described in the status column of the check ID of the check condition logical expression. It is supposed to be. Further, even when the check target data itself is changed, “not implemented” is described in the check ID status column of the check condition logical expression in which the change has been made. The check condition acquisition management unit 24 describes the “completed” and “not implemented”.
[0033]
That is, when acquiring the check condition logical expression, the check condition acquisition management unit 24 acquires only the check condition logical expression of the check ID described as “unexecuted” in the check state management table 22, and analyzes this. Output to the unit 28. In addition, when acquiring the check condition logical expression, the check condition acquisition management unit 24 specifies one of the conditions of the entry value check, the check between items, and the check between definitions in the check type column of the check condition storage database 20, It is also possible to acquire all check condition logical expressions associated with the specified check condition.
[0034]
The syntax analysis unit 28 analyzes the syntax of the check condition logical expression input from the check condition acquisition management unit 24 according to the syntax analysis program 26, and outputs the analysis result to the program generation unit 32. The analysis is performed by recognizing operator and function definitions.
The program generation unit 32 generates the data check program 30 by using the analysis result input from the syntax analysis unit 28 as a parameter in a program whose basic part for checking data is predetermined. That is, the data check program 30 reflects the analysis result.
[0035]
The data check unit 34 checks whether there is any error in the check target data stored in the check target data storage database 12 according to the data check program 30, and outputs the check result to the check result output control unit 36. Is what you do. However, the check target data in the database 12 is searched by the data name recognized by the syntax analysis in the program 30.
[0036]
The check result output control unit 36 stores the contents of the check result from the data check unit 34 in the check result storage unit 38, displays the contents on the display unit 40, and outputs the check result to the check condition acquisition management unit 24. is there. At this time, the check condition acquisition management unit 24 updates the check status of the check status management table 22 according to the check result.
[0037]
Also, under the display control of the check result output control unit 36, an error list 58 indicating the contents of the check result is displayed on the display unit 40, for example, as shown in FIG. In the error list 58, the check type is “3” indicating an error in the inter-definition check, the number of errors is “2”, and further, the content of each error is shown.
[0038]
The data consistency check process performed by the data consistency check device 10 having such a configuration will be described with reference to FIG.
However, as an initial state, it is assumed that all the check conditions of the station data are newly created with the new installation of the exchange.
In this case, in step S1, an instruction for creating a check condition logical expression for all station data of the newly installed exchange is sequentially input by operating the keyboard 18. In response to the input command, in step S2, the check condition creation unit 16 reads the data name of the check target from the check target data storage database 12, and also reads the operator and function from the operator / function storage database 14. Is read.
[0039]
Thereafter, as shown in step S3, in the check condition creation unit 16, the read data name is defined by an operator and a function according to the input command, thereby creating a check condition logical expression. The created check condition logical expression is stored in the corresponding check type column of the check condition storage database 20 after being associated with the check ID.
[0040]
By the processing in step S3, for example, as shown in the check condition storage database 20 in FIG. 1, 0 <CLST. Of the check condition logical expression in which the check ID OPCT_A001 is associated with the entry value check column. A <100 is stored, OPCT_B001 (CLST.A> CLST.B) is stored in the check box between items, and OPCT_C001 is stored in the check column between definitions (CLST.A = OPCT). .B) & (CLST.B = OPCT.B) are stored. However, although a part of the check condition logical expression is described in each check column on the drawing, it is assumed that there are many other check condition logical expressions.
[0041]
When the check condition logical expression is stored, as shown in step S4, in the check condition acquisition management unit 24, the stored check state of the check condition logical expression is associated with the corresponding check ID and the check state management table is stored. 22.
Then, in step S5, the check condition management table 22 is referred to by the check condition acquisition management unit 24, and it is determined whether or not the check state includes “unexecuted”. Here, since it is assumed that all the check condition logical expressions are newly created, the check states associated with all the check IDs are “not performed”.
[0042]
Therefore, in step S6, all check condition logical expressions are obtained from the check condition storage database 20, and output to the syntax analysis unit 28.
In the syntax analysis section 28, as shown in step S7, the syntax analysis program 26 performs syntax analysis of all the check condition logical expressions, and outputs the analysis result to the program generation section 32.
[0043]
In step S8, the data generation program 30 is generated in the program generation unit 32 according to the analysis result. Then, as shown in step S9, the data check unit 34 checks whether there is any error in the check target data stored in the check target data storage database 12 according to the generated data check program 30, The check result is output to the check result output control unit 36.
[0044]
In step S10, the check result output control unit 36 stores the contents of the check result in the check result storage unit 38 and displays it on the display unit 40. Further, the check result is output to the check condition acquisition management unit 24.
The check condition acquisition management unit 24 updates the check state of the check state management table 22 according to the check result, as shown in step S4. Here, it is assumed that the check state has been updated as shown in FIG. That is, it is assumed that there is an error in the exchange data corresponding to the check IDs OPCT_B001, C003, and C004. Here, the erroneous data is corrected. With this modification, the check state remains "not performed".
[0045]
After the correction, the check condition acquisition management unit 24 refers to the check state management table 22 in step S5, and determines whether or not the check state includes “unexecuted”. In this case, since there is “unexecuted”, the check condition logical expression associated with the “unexecuted” check ID is acquired from the check condition storage database 20 and output to the syntax analysis program 26 in step S6. You. Then, as described above, the processes of steps S7 to S10 are performed again, and in step S4, the check condition acquisition management unit 24 updates the check state according to the check result. Here, it is assumed that all the check states have been updated to “completed”.
[0046]
After this update, in step S5, the check condition acquisition management unit 24 refers to the check state management table 22 to determine whether or not the check state includes "unexecuted". Since there is no such case, the data consistency check process ends. According to such a data consistency check device 10, software data for controlling and operating the exchange is stored in the check target data storage database 12 for each data name, and the check condition is expressed by a logical expression. The operator and the function, which are symbols for the operation, are stored in the operator / function storage database 14. The check condition creation unit 16 reads the corresponding data name from the database 12 and reads the corresponding operator and function from the database 14 in accordance with the input command for expressing the check condition by a logical expression, and then reads the data name and the operation. A check condition logical expression corresponding to each check condition is created by combining the child and the function. Then, each check condition logical expression is stored in the check condition storage database 20 in association with the check ID.
[0047]
The syntax of the stored check condition logical expression is analyzed by the syntax analyzer 28. The program generation unit 32 generates a data check program 30 for checking data errors by using the above analysis result as a parameter in a program whose basic part for checking data is predetermined. Then, according to the data check program 30, the data check unit 34 checks for an error in the soft data.
[0048]
That is, a check condition logical expression corresponding to a check condition for checking an error of the soft data and used when generating the data check program 30 for the soft data is added to the data name of the soft data by an operator, which is a symbol. And the function are combined, so that a check condition logical expression can be created by a simple combination of symbols. Therefore, new creation, change, or addition of data check conditions used in the data check program 30 can be easily performed even by a person who does not have specialized knowledge.
[0049]
Further, the check condition creation unit 16 reads the relevant check condition logical expression from the check condition storage database 20 in accordance with the input command for changing the check condition logical expression, and then changes the check condition logical expression. After the check condition formula is created, it can be arbitrarily changed.
Further, since the check condition creation unit 16 creates a new check condition logical expression using the check condition logical expression stored in the check condition storage database 20, it is possible to use the check condition logical expression once created. Therefore, a check condition logical expression can be efficiently created.
[0050]
In addition, the check condition acquisition management unit 24 describes a check state indicating “good” in the check result or a check state indicating an error in the check state management table 22 in association with the check ID. Since only the check condition logical expression of the unique information whose check state indicates an error is acquired from the check condition storage database 20 and output to the syntax analysis unit 28, the check for checking the soft data having a bad check result is performed. The corresponding software data can be checked using only the conditional logical expression. Therefore, it is possible to recheck the data after correcting the error in a short time.
[0051]
In addition, the check condition acquisition management unit 24 determines whether the check condition logical expression stored in the check condition storage database 20 is changed or the check condition logical expression is newly stored. A check state indicating that the check has not been performed is described in the check state management table 22 in association with the check ID of the check condition logical expression, and the described check state indicates at least one of a defective state and an unfinished state. Only the check condition logical expression of the unique information is acquired from the check condition storage database 20 and output to the syntax analysis unit 28. Therefore, when the check condition logical expression is changed, added, or newly created, The corresponding soft data can be checked using only the corresponding check condition logical expression. Therefore, data change, addition, and check at the time of new creation can be performed in a short time.
[0052]
【The invention's effect】
As described above, according to the present invention, a check condition logical expression corresponding to a check condition for checking an error of soft data and used when generating a check program of the soft data is added to a data name of the soft data, Since it is created by combining operators and functions that are symbols, a check condition logical expression can be created with a simple combination of symbols. Therefore, there is an effect that new creation, change, or addition of the check condition of the data used in the check program can be easily performed even by a person who does not have specialized knowledge.
[0053]
In addition, a check state indicating “good” or an error indicating a check result is described in a table in association with a check ID, and the check state described in this table is a check condition logical expression of unique information indicating an error. Is obtained from the database and parsed, and a check program is generated, so the software data is checked using only the check condition logical expression for checking the soft data with a bad check result. be able to. Therefore, there is an effect that re-check after data error correction can be performed in a short time.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of a data consistency check device according to an embodiment of the present invention.
FIG. 2 is a diagram showing an A-HUB definition document and a B-HUB definition document which are specifications of station data of an exchange.
FIG. 3 is a diagram showing an office data specification, which is a specification of office data of an exchange.
FIG. 4 is a diagram showing a specification of station data of an exchange, in which each condition of an entry value check, a check between items, and a check between definitions is expressed in text.
FIG. 5 is a diagram showing a specification of a function.
FIG. 6 is a diagram showing a check state management table.
FIG. 7 is a diagram showing an error list describing the contents of a check result.
FIG. 8 is a flowchart for explaining a data consistency check process by the data consistency check device according to the embodiment of the present invention.
[Explanation of symbols]
10 Data consistency check device
12 Data storage database to be checked
14. Operator and function storage database
16 Check condition creation section
18 Keyboard
20 Check condition storage database
22 Check status management table
24 Check condition acquisition management unit
26 Syntax analysis program
28 Syntax Analyzer
30 Data Check Program
32 Program Generator
34 Data Check Section
36 Check result output control unit
38 Check result storage
40 Display

Claims (7)

Data consistency to check if there is any error in software data for controlling and operating hardware of equipment system composed of many elements according to check conditions for checking errors in the software data In the checking device,
A first database storing the soft data for each data name;
A second database that stores operators and functions that are symbols for expressing the check condition by a logical expression;
According to an input command for expressing the check condition by a logical expression, a corresponding data name is read from the first database, and a corresponding operator and function are read from the second database. Creating means for creating a check condition logical expression corresponding to each of the check conditions by combining a child and the function,
A third database that stores the individual check condition logical expressions created by the creating means in association with unique information;
Analysis means for analyzing the syntax of the check condition logical expression stored in the third database;
Generating means for generating a check program for checking an error in the soft data by using the analysis result of the analyzing means as a parameter in a program in which a basic part for checking the soft data is predetermined,
Checking means for checking an error of the soft data in accordance with the check program. 2. The method according to claim 1, wherein the creating unit reads the corresponding check condition logical expression from the third database and changes the check condition logical expression in accordance with an input command for changing the check condition logical expression. 2. A data consistency check device according to claim 1. The data consistency check device according to claim 1, wherein the creating unit creates a new check condition logical expression using the check condition logical expression stored in the third database. Management means for writing a check state indicating good or bad of a check result by the check means in a table in association with the unique information;
An acquisition means for acquiring only a check condition logical expression of unique information indicating a failure in a check state described in the table from the third database and outputting it to the analysis means. 4. The data consistency check device according to any one of 1 to 3. The management means, if the check condition logical expression stored in the third database is changed or the check condition logical expression is newly stored, the check by the corresponding check condition logical expression has not been completed. Is described in the table in association with the unique information of the check condition logical expression,
The acquiring means acquires from the third database only a check condition logical expression of unique information whose check status described in the table indicates the defect or at least one of which is not completed, and outputs it to the analyzing means. 5. The data consistency check device according to claim 4, wherein: 6. The data consistency check device according to claim 1, wherein the facility system is an exchange, and the software data is data for controlling and operating the exchange. Data consistency to check if there is any error in software data for controlling and operating hardware of equipment system composed of many elements according to check conditions for checking errors in the software data In the checking method,
A first database storing the soft data for each data name;
A second database that stores operators and functions that are symbols for expressing the check condition by a logical expression;
In accordance with an input command for expressing the check condition by a logical expression, the data name of the soft data is combined with an operator and a function, which are symbols for expressing the check condition by a logical expression, so that each of the check conditions is A creation step of creating a check condition formula corresponding to
A storage step of storing each check condition logical expression created by the creating means in a database in association with unique information;
An analyzing step of analyzing the syntax of the check condition logical expression stored in the database;
A generation step of generating a check program for checking an error in the soft data by using the analysis result obtained in the analysis step as a parameter for a program in which a basic part for checking the software data is predetermined,
A check step for checking an error of the soft data according to the check program.

Images