JP5941823B2 - Consistency confirmation method and system - Google Patents

Description

  The present invention relates to a technique for confirming consistency of processing contents in two information systems. In particular, the present invention relates to a technology for supporting a test when the information system is shifted from the current system to the new system.

  The test in the construction of the information system is performed by the tester operating the information system based on the check list, confirming the result, and writing it in the check list. In the transition from the current system to the new system, there are cases where the network is switched from the current system to the new system outside business hours, and tests related to surrounding systems and user terminals are performed. These tests are indispensable elements in the construction of an information system, but recently, as the scale of the information system increases, the man-hours required for the test increase, and a test man-hour reduction method is required. In addition, since the test at the time of transition must be performed within a limited time outside the business hours, there is a higher demand for reducing the number of test steps.

  As a technique for reducing the test man-hours, a technique for reducing man-hours required for network switching and setting by transmitting the same request message to the current system and the new system and comparing response messages as in Patent Document 1 It has been known.

JP-A-8-249279

  In Patent Document 1, the tester still needs to perform system operation for testing, check the results, and describe the test results, and there is no man-hour reduction effect for the portion that increases as the system scales up.

  In order to solve the above-described problem, in the present invention, when comparing response messages of two systems, a correspondence table indicating a correspondence relationship between check list items for confirmation of consistency and messages is used. This correspondence table has information (ID, function name, etc.) included in the message, and is created from specifications in the system.

  More specific embodiments of the present invention are as follows. The test result evaluation system is a new test after acquiring the request message of the current system user by packet capture, etc. and performing processing such as correction of the acquisition time in the test at the time of transition from the current system to the new system. Send it to the system. The response message of the current system is also acquired by packet capture or the like, and compared with the response message from the new system.

  Next, a correspondence table listing various types of information is created from the information on the specifications used at the time of system construction. This correspondence table includes some items that match the checklist as key information. By using this correspondence table, the information contained in each message can be converted into key information, and by checking the items that match the key information listed in the check list, which check each message Specify whether the list item is supported. Here, whether or not the message of the current system matches the message of the new system is entered in the check list.

  According to the present invention, it is possible to check the consistency of two information systems including a test in a manner that further reduces the load on the tester.

It is a figure showing the whole information processing system composition in one embodiment of the present invention. It is an example of the information preserve | saved in the message | telegram preservation | save function 1514 in one Embodiment of this invention. It is an example of the information preserve | saved in the comparison result preservation | save function 1515 in one Embodiment of this invention. It is an example of the check list preserve | saved at the check list preservation | save function 1525 in embodiment of this invention. It is an example of the correspondence table preserve | saved at the correspondence table preservation | save function 1526 in one Embodiment of this invention. It is an example of a correspondence table setting file stored in the setting file storage function 1527 in one embodiment of the present invention. It is an example of the setting file for message | telegram specification preserve | saved in the setting file preservation | save function 1527 in one Embodiment of this invention. It is an example of the setting file for message | telegram information extraction preserve | saved at the setting file preservation | save function 1527 in one Embodiment of this invention. It is a flowchart which shows the content of the whole process in one Embodiment of this invention. It is a flowchart at the time of performing evaluation of the test result using the message | telegram comparison result in one Embodiment of this invention, and description to a check list. It is a flowchart of the correspondence table preparation in one Embodiment of this invention. It is a flowchart of the correspondence specification in one Embodiment of this invention.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In addition, this invention is not limited by embodiment described below. In the present embodiment, a test in transition from the current system to the new system will be described as an example.
FIG. 1 is a diagram illustrating a system configuration of the embodiment.
The test result evaluation method and system of this embodiment includes a current system B120, a current system A130, a new system A′140, and a test result evaluation system 150 that are interconnected to the network 110.

The network 110 may be any transmission medium that transmits information to each other, and may be realized by a LAN or the like, for example.
The current system B120 is a computer including a storage unit such as a hard disk drive, a control device, and the like, and has a request message transmission function for transmitting a request message and a response message reception function for receiving a response message.

  The current system A130 and the new system A′140 are computers including a storage unit such as a hard disk drive, a control device, etc., a request message receiving function for receiving a request message, a request message processing function for processing a request message, It has a response message transmission function that transmits a response message.

  The test result evaluation system 150 is a computer including a storage unit such as a hard disk drive, a control device, and the like, and includes a telegram control unit 151 and a test result evaluation unit 152. Each function (unit) shown below can be calculated and processed by a control device (such as a CPU) included in the system according to a program.

  The message control unit 151 is a part that acquires messages from the current system B120, the current system A130, and the new system A′140, and compares response messages, and includes a message acquisition function 1511, a message transmission / reception function 1512, and a message comparison function 1513. , A message storage function 1514 and a comparison result storage function 1515.

  The message acquisition function 1511 acquires a response message and a comparison message between the current system B 120 and the current system A 130 by packet capture or the like, and stores them in the message storage function 1514.

  The message transmission / reception function 1512 reads the request message of the current system B120 from the message storage function 1514, transmits it to the new system A'140, and stores it in the message storage function 1514 as a request message to the new system A '. Also, the response message from the new system A ′ 140 is received and stored in the message storage function 1514.

  The message comparison function 1513 compares the message between the current system B 120 and the current system A 130 stored in the message storage function 1514 and the corresponding message of the new system A ′ 140, and stores the result in the comparison result storage function 1515. To do.

  The message storage function 1514 stores the message received from the message acquisition function 1511. FIG. 2 shows an example of information stored in the message storage function 1514. Reference numeral 201 denotes a source ID column, in which terminal-specific information such as the IP address of the current system B 120 is stored. Reference numeral 202 denotes a message ID column, which stores an ID for identifying a message. Reference numeral 203 denotes a message type column, in which information indicating whether the message is transmitted from the current system or the new system, and information indicating which message is a request or a response is stored. Reference numeral 204 denotes a message body, which is stored as text as it is.

  The comparison result storage function 1515 stores the message comparison result received from the message comparison function 1513. FIG. 3 shows an example of information stored in the comparison result storage function 1515. Reference numeral 301 denotes a source ID column, which stores information unique to the terminal such as the IP address of the current system B120. 302 is a column without a message difference, and stores a message ID 202 of a message that has no difference as a result of comparison. 303 is a column without a message difference, and stores a message ID 202 of a message having a difference as a result of comparison.

  The test result evaluation unit 152 is a part that performs test result determination and description in a check list using messages and comparison results stored in the message control unit 151, and includes a check list creation function 1521 and a correspondence table creation function. 1522, a correspondence specifying function 1523, a test result description function 1524, a check list storage function 1525, a correspondence table storage function 1526, and a setting file storage function 1527.

The check list creation function 1521 reads the check list used for the test and stores it in the check list storage function 1525.
The correspondence table creation function 1522 reads a specification sheet and the like based on the correspondence table setting file stored in the setting file storage function 1527, creates a correspondence table, and stores it in the correspondence table storage function 1526.

  In the correspondence relationship specifying function 1523, a message is extracted from the message storage function 1514 and stored in the message specification setting file stored in the setting file storage function, the message information extraction setting file, and the correspondence table storage function 1526. Use the correspondence table to identify the screen name to which each message corresponds. Further, the result is added to the check list stored in the check list storage function 1525.

  The test result description function 1524 reads the check list from the check list storage function 1525, searches the comparison result storage function 1515 for each message described in the check list, and adds the comparison result to the check list.

  The check list storage function 1525 stores the check list received from the check list creation function 1521. FIG. 4 shows an example of a check list. Reference numeral 401 denotes a test ID column, which stores information for identifying each test. Reference numeral 402 denotes an operation ID column, which stores information for identifying an operation to be performed in each test. One or a plurality of 402 is assigned to each test ID. Reference numeral 403 denotes a confirmation item column, which stores items to be confirmed by the tester for each operation ID. Reference numeral 404 denotes an operation content column, which stores the operation content performed by the tester for each operation ID. Reference numeral 405 denotes a screen transition column, which stores screen transitions expected when the operation content 404 is performed. A message string 406 stores a message ID 202 corresponding to each operation ID. Reference numeral 407 denotes a current / new comparison column, which stores information on whether or not the response message from the current system A 130 matches the response message from the new system A ′ 140 for the message 406. Reference numeral 408 denotes a test result column, which stores a test result for each operation ID or test ID.

  The correspondence table storage function 1526 stores the correspondence table received from the correspondence table creation function 1522. FIG. 5 shows an example of the correspondence table. Reference numeral 501 denotes a screen ID column, which stores the screen ID adopted from the specification or the like. Reference numeral 502 denotes a screen name column, which stores the name of the screen adopted from the specification or the like. Reference numeral 503 denotes a function name, which stores the name of the function adopted from the specification or the like. Reference numeral 504 denotes a function ID column, which stores the function ID adopted from the specification or the like. Reference numeral 505 denotes an API / URL column, which stores APIs and URLs adopted from specifications and the like. Reference numeral 506 denotes a parameter column, which stores parameters adopted from a specification or the like. Here, each column is given a mark indicating whether or not it is unique. In the example of FIG. 5, 501, 502, 503, 504, and 505 are unique, and 506 is not unique.

  The setting file storage function 1527 stores a correspondence table setting file used by the correspondence table creation function 1522, a message specification setting file used by the correspondence relationship specifying function 1523, and a message information extraction setting file. FIG. 6 shows an example of the correspondence table setting file. Reference numeral 601 denotes an input file column, which stores the type of input file used when creating the correspondence table. Reference numeral 602 denotes a use column in the correspondence table, and an item indicating whether or not the input file is already used in the correspondence table is stored for each input file. An item name column 603 stores items to be reflected in the correspondence table for each input file. Reference numeral 604 denotes a position column, which stores position information where information is described in the input file for each item name. Reference numeral 605 denotes a unique column in which information indicating whether each item is unique information is stored. Next, FIG. 7 shows an example of a message specifying setting file. Reference numeral 701 denotes a message type column, in which information indicating the type to which each message is assigned is stored. Reference numeral 702 denotes a search position column, which stores information indicating a position where information is searched from a message in order to specify the type of message. Reference numeral 703 denotes a column of specific information, in which information to be searched at the position specified in 702 is stored in order to specify the type of message.

  Next, FIG. 8 shows an example of a telegram information extraction setting file. Reference numeral 801 denotes a message type column, which stores information indicating the type to which each message is distributed, as in the case of 701. Reference numeral 802 denotes an information name column, in which information indicating the type of information extracted from each type of message is stored. Reference numeral 803 denotes a start position column, in which information indicating the position to be extracted from the electronic message is stored for the information to be extracted indicated by 802. Reference numeral 804 denotes a length column, which stores information indicating the length to be extracted from the position indicated by 803 for the information to be extracted indicated by 802.

Next, processing contents of the system configured as described above will be described.
FIG. 9 shows an overall flow. The message control unit acquires a request message and a response message exchanged between the current system B 120 and the current system A 130, and transmits a request message to the new system A ′ 140. It is a flowchart at the time of receiving a response message and performing message comparison.

The current system B120 transmits a request message to the current system A130. Here, the request message may be created by a tester for a test, or a message transmitted by a normal user may be used (step 901).
The current system A 130 receives the request message from the current system B 120 and performs processing according to the content of the request message (step 902).
Here, the message acquisition function 1511 of the message control unit 151 acquires the request message transmitted from the current system B120 to the current system A130. Although it is desirable to acquire the current system B120 or the current system A130 by using a technique such as packet capture that does not require modification, a method of acquiring the current system B120 or the current system A130 with modification may be adopted (steps). 903).

  The message acquisition function 1511 of the message control unit 151 processes the acquired message into a format as shown in FIG. 2 and stores it in the message storage function 1514. Here, the source IP address in the packet, the ID determined from the source IP address, etc. are described in 201 as the source ID. Also, a message ID 202 is given and described. Further, since the request message is sent from the current system B 120 to the current system A 130, the information is described in the message type 203. The message body is described in 204 (step 904).

The current system A 130 that has completed the processing after receiving the request message in step 902 transmits a response message to the current system B 120 (step 905).
The current system B120 receives the request message from the current system A130 (step 906).

  Here, the message acquisition function 1511 of the message control unit 151 acquires the response message transmitted from the current system A 130 to the current system B 120. Although it is desirable to acquire the current system B120 or the current system A130 by using a technique such as packet capture that does not require modification, a method of acquiring the current system B120 or the current system A130 with modification may be adopted (steps). 907).

  The message acquisition function 1511 of the message control unit 151 processes the acquired message into a format as shown in FIG. 2 and stores it in the message storage function 1514. Here, the ID determined from the transmission destination IP address or the transmission destination IP address in the packet is described in 201 as the transmission source ID. Further, the request message corresponding to the request message is identified from the transmission source ID 201 and the information in the packet, and the same message ID as the request message is described in 202. Further, since the request message is sent from the current system A 130 to the current system B 120, the information is described in the message type 203. The message body is described in 204 (step 904).

  Next, the message transmission / reception function 1512 of the message control unit 151 acquires the request message from the message storage function 1514 and transmits it to the new system A ′ 140. Here, when information specific to the current system B120 such as the transmission source IP address or information specific to the current system A130 such as the transmission destination IP address is described in the main body of the message to be transmitted, the information of the message is not included. In order not to cause matching, information is appropriately rewritten and transmitted. In addition, by rewriting the information of the request message, the new system A ′ can interpret that the request message is transmitted from the current system B120 or the virtual new system B ′, not from the message transmission / reception function 1512, Tests can be performed in near real situations. The message transmitted here is processed into the format shown in FIG. 2 and stored in the message storage function 1514. An ID calculated from a transmission destination IP address or a transmission destination IP address in the packet is described in 201 as a transmission source ID. In addition, the same message ID as the request message of the processing source is described in 202. In addition, for the request message to the new system A ′ 140, the information is described in the message type 203. The message body is described in 204.

  In FIG. 9, the request message is transmitted to the new system A ′ 140 after the request message and the response message are gathered. However, when the request message from the current system B 120 is acquired, the request message is transmitted to the new system A ′ 140. You may perform step 909 to step 912 which are the transmission of a request message | telegram, and the process following it (step 909).

The current system A ′ 140 receives the request message from the message transmission / reception function 1512 and performs processing according to the content of the request message (step 910).
The new system A ′ 130 that has completed the processing after receiving the request message in step 910 transmits a response message to the current system B 120 or the virtual new system B ′. Actually, the transmission destination is the telegram transmission / reception function 1512 (step 911).

  The message transmission / reception function 1512 receives the response message from the new system A ′ 140, processes it into the format shown in FIG. 2, and stores it in the message storage function 1514. Here, the transmission destination IP address in the packet, the ID determined from the transmission destination IP address, etc. are described in 201 as the transmission source ID. Further, the request message corresponding to the request message is identified from the transmission source ID 201 and the information in the packet, and the same message ID as the request message is described in 202. Since the response message is from the new system A ′ 140, the information is described in the message type 203. The message body is described in 204 (step 912).

  When the response message from the current system A130 and the response message from the new system A'140 are collected with the same message ID, the message comparison function 1513 compares the messages and compares them in the format shown in FIG. The result is stored in the result storage function 1515. Here, when the transmission source ID of the response message described in 201 is not described in 301, the transmission source ID 201 of the response message is described in the transmission source ID 301 of FIG. Next, the response messages are compared. If there is no difference between the messages, the message ID is described in 302. If there is a difference between the messages, the message ID is described in 303. Here, it may be set so that no comparison is performed for a specific portion. As a result, it is possible to prevent the test from being hindered by being classified as having a message difference by a portion that does not have a match, such as a source IP address and a destination IP address. Further, the request message may be similarly compared (step 913).

FIG. 10 is a flowchart when the test result evaluation unit 152 performs the evaluation of the test message using the request message, the response message, and the message comparison result acquired by the message control unit 151 and the description in the check list.
The check list creation function 1521 creates a check list for the new system A ′ in the format shown in FIG. 4 and stores it in the check list storage function 1525. In creating the check list, the person in charge of the test may directly input necessary items to the check list creating function 1521, or a list describing necessary items may be read by the check list creating function 1521, or the current system A130. The checklist may be read by the checklist creation function 1521 or may be created by a combination of these methods. In the step 1001, 401, 402, 403, 404, and 405 are described among the items in FIG. 4. Here, the checklist is created and saved in response to the message acquisition and comparison result saving in the message control unit, but this step 1001 may be performed before the test is started (step 1001).

  In the correspondence table creation function 1522, a specification sheet or the like is read based on the correspondence table setting file saved in the setting file saving function 1527 to create a correspondence table in the format shown in FIG. 5 and saved in the correspondence table saving function 1526. To do. The person in charge of the test needs to prepare various setting files in advance, but the system may perform according to the various setting files, or may be manually performed by the person in charge of the test. Here, the correspondence table is created in response to the creation and storage of the check list in step 1001, but this step 1002 may be performed before the start of the test or before the creation of the check list. Good (step 1002).

  FIG. 11 is a detailed flowchart for creating the correspondence table performed in step 1002. In the following description, the present embodiment will be described by taking the case of actually using FIGS. 5 and 6 as an example.

The correspondence table creation function 1522 first reads a screen list (step 1101).
Next, information is extracted from the screen list read in step 1101 according to the correspondence table setting file. Specifically, the information of 604 is read, the columns of the screen list are referenced, the item names are given to the columns by the information of 603, and the information is extracted while maintaining the relationship in each column. Describe in the correspondence table. For example, in this example, the screen ID, the screen name, and the function name are extracted from the screen list, and these pieces of information are described in the correspondence table of FIG. Further, a flag is set in the use column 602 in the correspondence table of the screen list column in the correspondence table setting file to clearly indicate that the screen list has already been used (step 1102).

Next, an input file not flagged in 602 is selected from the correspondence table setting file, and the corresponding input file is read (step 1103).
Next, information is extracted from the input file read in step 1103 according to the correspondence table setting file in the same manner as in step 1102. For example, when the function list is read in this example, the function ID and the function name are extracted. (Step 1104)
Next, in the information extracted in step 1104, it is determined whether or not there is a unique item that matches the item already described in the correspondence table. If the condition is met, the process proceeds to step 1106, where it matches. If not, the process proceeds to step 1108. For example, in this example, the function name is included in both the correspondence table at this point and the information extracted in step 1104, and this information is unique. Step 1105).

  If the condition is met in step 1105, information is described in the correspondence table using the unique item found in step 1105 and matching the correspondence table as a key. For example, in this example, the function ID is described in the correspondence table using the function name as a key (step 1106).

The input file used in step 1106 is flagged in the correspondence table setting file 602 to clearly indicate that it has already been used (step 1107).
Here, it is determined whether or not the end condition is satisfied. If the end condition is satisfied, the creation of the correspondence table is ended. If not, the process returns to step 1103 to continue the processing. As an end condition, at least all input files are used, that is, when the flag 602 is set for all input files and when there is no change in the correspondence table, Other conditions may be added (step 1108).

In creating the correspondence table, the item name and item content are described at the same time. However, only the correspondence table item name is created first using the correspondence table configuration file and then input. You may read the file and fill in the contents of the item.
When the message, the message comparison result, the check list, and the correspondence table are ready, the correspondence specifying function 1523 extracts the message from the message storing function 1514, and is stored in the setting file storing function. And the message information extraction setting file and the correspondence table stored in the correspondence table storage function 1526, the screen name corresponding to each message is specified. The result is added to the column 406 of the check list stored in the check list storage function 1525. When a plurality of electronic messages are associated with the same checklist item, a plurality of electronic messages are associated with the column 406 (step 1003).

FIG. 12 is a detailed flowchart of the correspondence relationship identification performed in step 1003. In the following, the embodiment will be described using the case where the screen name is adopted as key information, using the transmission source ID IP001 of FIG. 2 and FIGS. 7 and 8 as an example.
First, the correspondence specifying function 1523 reads a message from the message storage function 1514. Here, the correspondence is specified from the request message or response message to the new system A ′ 140, but the correspondence may be specified from the request message or response message to the current system A 130 (step 1201).

  Next, the type of the message is specified according to the message specifying setting file. Specifically, the information on the position indicated by the search position 702 of the message specification setting file in FIG. 7 is read from the message, and it is determined whether or not the information matches the information indicated by the specific information 703. If they match, the message type specified in the message type 701 is specified. For example, in this example, since an HTTP character string is found in the first line, which is the search position of HTTP (1), it is classified into the message type of HTTP (1). Further, since the item name Referer was not found, it is not classified into HTTP (2) (step 1202).

  Next, information necessary for specifying the correspondence is extracted from the message according to the message information extraction setting file. Specifically, the message type 801 in the message information extraction setting file in FIG. 8 corresponding to the message type classified in step 1202 is searched, information is extracted according to the start position 803 and the length 804, and the information name 802 is extracted. Give the item name. For example, in this example, a character string “login” is extracted as API / URL information (step 1203).

  Next, it is determined whether or not an item that matches the item name of the information extracted from the message in step 1203 exists in the correspondence table. If there is a matching item, the process proceeds to step 1205. If there is no matching item, the process proceeds to step 1206. For example, in this example, since the item of API / URL also exists in the correspondence table, the process proceeds to step 1205 (step 1204).

  Next, the screen name which is key information is specified based on the information extracted from the message. Specifically, the information extracted from the message in step 1203 is searched from the column of matching items found in step 1204 of the correspondence table, and the screen name of the matching row is the screen name to which the message corresponds. Become. For example, in this example, a character string “login” is searched from the API / URL column, and it becomes clear from the screen name of the matched row that this message corresponds to the login screen (step 1205).

  Next, a message corresponding to the check list is described in the column 406 using the screen name as key information as a key. At this time, the message ID is described in the column 406 for the operation ID corresponding to both the request message and the response message having the same message ID. At this time, a plurality of messages are associated with one operation ID. Also, for a message that does not correspond to any operation ID because the screen name is not found, an item having only a test ID, operation ID, and screen transition is created in the checklist, and the item corresponds to the item. The message ID is described as follows. If there is no matching item in step 1204 or a message whose screen name could not be specified in step 1205, a new item having only a test ID and an operation ID is created in the checklist. The message ID is described so as to correspond (step 1206).

  Here, it is determined whether or not the end condition is satisfied. If the end condition is satisfied, the specification of the message is ended. If not, the process returns to step 1201 to continue the processing. As a termination condition, it is at least necessary that all messages are in the state described in the check list, but other conditions may be added (step 1207).

  After the correspondence between the check list and the message is specified, the test result description function 1524 reads the check list from the check list storage function 1525, and the comparison result from the comparison result storage function 1515 for each message described in the check list. And a match / mismatch of the comparison result is added to the column 407 of the check list. Further, the test result is added to the column 408 in accordance with the comparison result for each operation ID. Note that the description of the test result in 408 can be determined from the comparison result of the message, for example, when the message with the same comparison result and the message with the same comparison result are mixed for the same operation ID. Since it may be difficult, it may be described manually by the person in charge of the test instead of using the test result description function 1524 (step 1004).

  According to the present embodiment described above, it is possible to reduce the man-hours required for test input by a tester, confirmation of results, and description of test results. In addition, since the current system user's message is used, the test is performed with messages of various contents that cannot be assumed by the tester alone, and the quality of the test is improved.

110: Network 120: Current system B
130: Current system A
140: New system A '
150: Test result evaluation system 151: Message control unit 1511: Message acquisition function 1512: Message transmission / reception function 1513: Message comparison function 1514: Message storage function 1515: Comparison result storage function 152: Test result evaluation unit 1521: Check list reading function 1522 : Correspondence table creation function 1523: Correspondence relation specifying function 1524: Test result description function 1525: Check list storage function 1526: Correspondence table storage function 1527: Setting file storage function

Claims (12)

In the consistency check method for checking the consistency in the operation of multiple information systems,
Capturing a request message for a first information system included in the plurality of information systems;
Sending the captured request message to a second information system included in the plurality of information systems;
From each of the first information system and the second information system, receiving an output message for the request message, comparing these output messages,
The result of the comparison, a checklist of items for integrity check, and identified using the correspondence table, the consistency check, characterized in that to check the consistency against the specific been checklist item Method. In the consistency check method according to claim 1,
The consistency check method, wherein the correspondence table is created from the specifications of the second information system. In the consistency check method according to claim 1,
The consistency check is characterized in that the correspondence between the output message and the check list item is specified from the information described in the output message and the information of the specifications of the second system. . In the consistency check method according to any one of claims 1 to 3,
For the consistency check of the results, the consistency verification method characterized by recording in association with a plurality of output message to one checklist item. In the consistency check method according to any one of claims 1 to 4,
Consistency confirmation method characterized by adding other information to the check list when a corresponding check list item cannot be identified for the comparison result of the output message. In the consistency confirmation method according to any one of claims 1 to 5,
A consistency check method characterized by storing message information, a message comparison result, a check list, a correspondence table, and various settings in a storage device. In the consistency confirmation system for confirming consistency in the operation of multiple information systems,
Means for capturing a request message for a first information system included in the plurality of information systems;
Means for transmitting the captured request message to a second information system included in the plurality of information systems;
Means for receiving an output message for the request message from each of the first information system and the second information system and comparing the output messages;
The result of the comparison, and characterized in that it has a checklist item for integrity check, and identified using the correspondence table, and means for confirming the consistency against the specific been checklist item Consistency check system. In the consistency confirmation system according to claim 7,
The consistency check system, wherein the correspondence table is created from the specifications of the second information system. In the consistency confirmation system according to claim 7,
The means for confirming the consistency specifies a correspondence relationship between the output message and the check list item from the information described in the output message and the information of the specifications of the second system. Confirmation system. In the consistency check system according to any one of claims 7 to 9,
The information on check consistency results, integrity confirmation system characterized in that it comprises means for recording in association with a plurality of output message to one checklist item. In the consistency check system according to any one of claims 7 to 10,
A consistency confirmation system, comprising: means for adding other information to the check list when a corresponding check list item cannot be specified for the comparison result of the output message. In the consistency confirmation system according to any one of claims 7 to 11,
A consistency confirmation system comprising means for storing electronic message information, electronic message comparison results, a check list, a correspondence table, and various settings in a storage device.

Images