JP4852872B2 - Fare determination program confirmation device, fare determination program confirmation method, and confirmation program - Google Patents

Description

  This invention is incorporated in automatic ticket gates, payment machines, etc. installed at railway stations and other transportation facilities, and when ticket data such as tickets and commuter passes are given as input data, The present invention relates to a fare determination program confirmation device for confirming a fare determination program for outputting (generating) fare data including items, a fare determination program confirmation method, and a fare determination program confirmation program.

  2. Description of the Related Art Conventionally, a fare determination program is stored in a storage means such as a ROM in an automatic ticket gate, a checkout machine, and the like installed at a transportation station such as a railway. As is well known, an automatic ticket gate is a device that restricts users who do not have the proper ticket from entering or leaving the station, and the checkout machine is a boarding device that is carried by the train, etc. This is a device that allows a user who is not a proper ticket to participate in a ticket from the station premises to use the ticket he / she has before participating in the station yard. The fare determination program is a program that generates fare data for the ticket data when the ticket data is given as input data. There are tickets, commuter passes, prepaid tickets, and so on. In the ticket, item data such as the ticket amount and issuing station are stored as ticket data, and in the commuter pass, data on items such as the valid period, the period where the period can be used, and the starting station of the section of use is the ticket data. In the prepaid ticket, data of items such as the valid period, the remaining prepaid amount, the starting station of the use section, and the like are stored as boarding ticket data. In addition, the data concerning the start station of the use section memorize | stored in the said commuter pass and the said prepaid ticket are written at the time of entrance. In addition, the fare data includes data on items such as a boarding fee for use of the use section and a settlement amount that is insufficient for the boarding fee.

  Automatic ticket gates and checkout machines read the ticket data stored in the inserted ticket when a user entering the station enters the ticket, and give this ticket data as input to the fare determination program Based on the fare data for this ticket data generated by this fare determination program, it is determined whether it is a ticket that needs to be settled before entry, and if it is necessary to settle, Traffic adjustments (automatic ticket gates) and check-in (accounting machine) for the entered tickets.

  This fare determination program must be updated each time a fare revision is made. In addition, when the fare determination program is updated, it is necessary to confirm whether or not the fare determination program operates according to the specifications before the updated fare determination program is incorporated into an automatic ticket checker or a checkout machine.

  In addition, test data (ticket data) is transmitted from the host computer to the automatic ticket checker incorporating the updated fare determination program, and the test data transmitted from the automatic ticket checker is input to the fare determination program as input data. A fare determination program test is performed to obtain fare data generated by the fare determination program. The automatic ticket checker transmits to the host computer the test result in this test, the comparison result comparing the test result with the expected result transmitted from the host computer together with the test data, and the like. Then, the operator checks information such as test results and comparison results sent from the automatic ticket checker on the host computer, and the test results that there was a difference (difference) between the test results and the expected results. It has been proposed to analyze the cause of data one by one (see Patent Document 1).

Note that the prediction result is assumed that the operator will obtain the test result for each test data.
JP 2001-194683 A

  However, in the configuration of the above-described Patent Document 1, an operator has to create an expected result for each ticket data, and this operation takes time and effort. Moreover, the cause of the difference between the workers must be analyzed one by one, and this analysis also takes time and effort.

  Moreover, recently, the calculation of fares has become complicated due to mutual entry between electric railway companies and payment using multiple types of tickets (such as tickets, commuter passes, and prepaid cards). For this reason, in order to fully confirm the operation of the fare determination program, a large amount of test data must be used. Settlement using tickets and commuter passes, connections between railway companies, etc. complicate calculations.

  On the other hand, considering the burden on the worker and the work time required for the operation check of the fare determination program, the limit of test data used for the operation check is about tens of thousands. Therefore, even if the operation of the fare determination program is sufficiently confirmed, it is complicated to use the ticket and commuter pass as described above after connecting the fare determination program or when connecting between electric railway companies. In rare cases, a fare calculation program error was discovered, causing trouble for users, and so on.

  The object of the present invention is to sufficiently confirm the operation of the fare determination program by improving the generation efficiency of the predicted result for comparison with the test result of the fare determination program and the analysis efficiency of the cause of the difference in the comparison result. The present invention provides a fare determination program confirmation device, a fare determination program confirmation method, and a confirmation program.

  The fare determination program confirmation device of the present invention has the following configuration in order to solve the above problems.

Fare determination program verification device of this invention, and the test tickets generating means for generating a plurality of ticket data for the test,
When the ticket data generated by the test ticket generating means is given as input data, a fare determination program for generating first fare data for the ticket data, and a specification different from the fare determination program Control means for executing a simulation program for generating second fare data for the ticket data when the ticket data generated by the test ticket generating means is given as input data;
For each of the ticket data, the first fare data generated by the control means and the second fare data are matched to extract a difference, and for each extracted difference, the degree of importance is set. A determination means for determining which of the plurality of defined ranks corresponds to the difference,
For each ticket data, based on the determination result of the determination means, a totaling means for generating total data in which the number of extracted differences is totaled according to the rank of importance,
For each of the ticket data, an output means for outputting the number of differences according to rank of importance based on the aggregate data generated by the aggregate means;
Filtering means for performing a filtering process for searching for ticket data that is presumed to have the same cause of the difference extracted by the determination means .

  In this configuration, test ticket data is generated by the test ticket generating means. This test ticket data includes data on items such as a ticket face amount, issuance station, use section, and periodical section that can be stored in the ticket. The ticket amount is the amount such as a ticket, and the issuing station is the station where the ticket was purchased. The use section is a section between the station and the station where the ticket amount can be boarded, and the regular useable section is a section between the station and the station where the commuter pass can be boarded and exited freely. The test ticket generating means also generates test ticket data combining a plurality of types of tickets such as tickets, commuter passes, and prepaid tickets. For example, test ticket data combining a ticket and a commuter pass is generated. Furthermore, ticket data for transferring a railway between different railway companies is generated. In this way, test ticket data for various cases assumed by the test ticket generating means is generated.

  Further, a fare determination program is executed by the control means. This fare determination program generates first fare data as output when the ticket data generated by the test ticket generation means is given as input data.

  Further, a simulation program is executed by the control means. In the simulation program, when the ticket data generated by the test ticket generating means is given as input data, second fare data is generated as output.

  This simulation program is created under different conditions from the fare determination program. In other words, the simulation program is a program in which the specifications of the fare determination program are lowered. The simulation program is created so as to satisfy some standard specifications of the fare determination program, but is created without considering the detailed specifications of the fare determination program. Therefore, the simulation program can suppress the development period and development cost more than the fare determination program. The different conditions mentioned here mean that the specifications are different.

  Further, as will be described later, in the test of the fare determination program, the first fare data generated by the fare determination program is matched with the second fare data generated by the simulation program, so that the fare determination program It is preferable to have different developers create the simulation program. This is because if both programs are developed by the same developer, there is a high possibility that the same error exists in both programs.

  The first fare data and the second fare data include data of items such as a settlement amount, a determination amount, a ticket amount, a settlement start station, and a determination result. The ticket amount is the amount of the ticket, and the determination amount is the boarding fee in the usage zone. The payment amount is a shortage amount that is insufficient with respect to the determination amount in the usage section, and the availability determination result is a result of determining whether the adjustment is necessary from the payment amount or the like.

Further, the determination means matches the first fare data and the second fare data for each ticket data and extracts a difference. Specifically, all items that do not match are extracted from items such as the settlement amount, judgment amount, ticket amount, settlement origin station, and availability judgment result included in the first fare data and the second fare data. . Also, the importance rank is determined for each of the items included in the first fare data and the second fare data. There are multiple importance ranks. The determination means determines the rank of importance corresponding to each extracted difference. The tabulation unit generates tabulation data in which the number of cases is tabulated according to importance ranks for the differences extracted by the determination unit for each ticket data. For example, when the rank of importance is A, B, and C (the order of importance is A, B, and C), the counting means calculates the number of differences corresponding to rank A, rank Total data is generated by counting the number of differences corresponding to B and the number of differences corresponding to rank C. The output means outputs this aggregated data. Further, the filtering means searches for ticket data presumed that the cause of the difference extracted by the determination means is the same.

In this way , test ticket data is automatically generated by the test ticket generation means, so there is no need for the operator to create test ticket data as in the prior art, and the burden on the operator is eliminated. The In addition, since the second fare data corresponding to the predicted result to be compared with the first fare data as the test result of the fare determination program is automatically generated by executing the simulation program, the worker can There is no need to create second fare data, and the burden on the operator is eliminated. Therefore , the generation efficiency of the second fare data can be improved.

In addition , for each ticket data, because it outputs the aggregated data that totaled the number of differences according to the rank of importance, for example, when analyzing the cause preferentially for the difference where the rank of importance is high, It is possible to easily find ticket data having a difference with a high importance rank, and to proceed with an analysis of the cause of the difference with a high importance rank. Thereby, the analysis efficiency of the cause about a difference can be improved. Furthermore, it is possible to easily check the ticket data in which a difference is caused by the same cause.
In addition, if the cause of the difference has been analyzed for any of the ticket data that is presumed that the cause of the difference is the same, the filtering means may obtain the difference obtained by the analysis. It is preferable to provide a configuration in which classification data indicating the type of cause of the dot is given. In this way, it is possible to improve the analysis efficiency for a plurality of ticket data for which differences are caused by the same cause.
In addition, when multiple routes occur between the departure station and the arrival station, the fare determination program generates first fare data for each route, and the simulation program generates second fare data for each route, What is necessary is just to match a 1st fare data and said 2nd fare data for every path | route, and to extract a difference.

  Since the generation efficiency of the second fare data and the analysis efficiency of the cause of the difference can be improved, the number of ticket data to be used can be increased more than before.

  In addition, test ticket data for multiple types of tickets is also automatically generated, so it is output to the output means after sufficiently performing a test assuming that multiple types of tickets are used. The collected data can be confirmed and analyzed.

Also, the output means may output a video signal for displaying the aggregated data to the display unit.

If comprised in this way, since total data will be displayed on a display , if total data will be produced | generated, an operator can confirm immediately. Thereby, the burden on the operator can be reduced.

In addition, the first of fare data and the second of fare data is, look at including an item in the settlement amount for the ticket data given as input, the differences according to the settlement amount, corresponding to the highest rank importance it may be a difference of.

Ma違doctor of fine calculation amount, so that the inconvenience to the user. In other words, the wrong amount is the biggest factor that reduces the trust of users.

Therefore, only for the test ticket data for which the difference corresponding to the rank with the highest importance has occurred, by analyzing the cause of the difference, the payment amount that most reduces the trust of the user is wrong. Analyze the cause.

  According to the present invention, by automatically generating test ticket data using the test ticket generating means, it is not necessary for an operator to create test ticket data as in the prior art. The burden can be eliminated. In addition, the second fare data corresponding to the predicted result to be compared with the first fare data that is the test result of the fare determination program is automatically generated by executing the simulation program. The operator does not need to create the second fare data, and the burden on the worker can be eliminated. Thereby, the generation efficiency of the second fare data can be improved.

  Furthermore, when outputting the aggregated data in which the number of differences for each ticket data is aggregated according to the importance using the output means, for example, when the operator analyzes the cause preferentially for the differences of great importance In addition, it is not necessary to check whether the output difference is a difference having a high importance level, and the analysis work can be started immediately. Thereby, the analysis efficiency of the cause about a difference can be improved.

  In addition, by automatically generating test ticket data for multiple types of tickets, it is possible to perform a test that assumes that multiple types of tickets will be used, and then output the aggregated data. Can be confirmed and analyzed.

  Hereinafter, a fare determination program confirmation device according to an embodiment of the present invention will be described.

  FIG. 1 is a block diagram showing a configuration of a fare determination program confirmation device 1 according to an embodiment of the present invention. The fare determination program confirmation device 1 of the present embodiment is a personal computer (PC) in which a test ticket generation program, a fare determination program, a simulation program, and a confirmation program are installed.

  The fare determination program confirmation device 1 is used when confirming the operation of the fare determination program, and includes a control unit 11, an HDD (hard disk) 12, an output unit 13, an operation unit 14, and the like.

  The control unit 11 controls the operation of the apparatus main body. The HDD 12 stores a confirmation program, a test ticket generation program, a fare determination program, a simulation program, and the like. The output unit 13 converts a signal such as data into a format corresponding to the connected output device, and transmits the signal to the output device. In the present embodiment, a display device 13a is connected as an output device. The display device 13 a is, for example, a liquid crystal display device, and displays data received from the output unit 13. An output device such as a printer may be connected.

  The operation unit 14 includes a known input device such as a keyboard and a mouse (not shown), and accepts an input operation by a user.

  The test ticket generation program generates test ticket data for a plurality of types of tickets such as tickets, commuter passes, and prepaid tickets. The ticket data is data stored in the ticket. This test ticket data includes data on items such as a ticket face amount, issuance station, use section, and periodical section that can be stored in the ticket. The ticket amount is the amount such as a ticket, and the issuing station is the station where the ticket was purchased. The use section is a section between the station and the station where the ticket amount can be boarded, and the regular useable section is a section between the station and the station where the commuter pass can be boarded and exited freely.

  The test ticket generation program outputs test ticket data for various assumed cases. For example, there are cases where a ticket and a commuter pass are used together, or a train between different railway companies is connected with one ticket. Note that the test ticket data generated by the test ticket generation program includes descending station data indicating the station from which the train got off. The descending station data is not included in normal ticket data stored in tickets, commuter passes, and the like.

  The fare determination program is a program for generating first fare data for the ticket data when the ticket data is given as input data.

  The simulation program is a program for generating second fare data for the ticket data when the ticket data is given as input data. The second fare data is an expected result that is assumed to be generated as the first fare data from the test ticket data.

  The simulation program is created under different conditions from the fare determination program. In other words, it is a program that lowers the specifications of the fare determination program. The simulation program is created so as to satisfy some standard specifications of the fare determination program, but is created without considering the detailed specifications of the fare determination program. Therefore, the simulation program can suppress the development period and development cost more than the fare determination program. The different conditions mentioned here mean that the specifications are different.

  Further, as will be described later, in the test of the fare determination program, the first fare data generated by the fare determination program is matched with the second fare data generated by the simulation program, so that the fare determination program It is preferable to have different developers create the simulation program. This is because if both programs are developed by the same developer, there is a high possibility that the same error exists in both programs. In the simulation program of the present embodiment, only standard specifications of the fare determination program are implemented.

  The first fare data and the second fare data include data of items such as a settlement amount, a determination amount, a ticket amount, a settlement start station, and a determination result. The ticket amount is the amount of the ticket, and the determination amount is the boarding fee in the usage zone. The settlement amount is a shortage amount that is insufficient with respect to the determination amount in the usage section, and the availability determination result is a result of determining whether the user needs to settle from the settlement amount or the like.

  The fare determination program is a program that is actually incorporated into an automatic ticket checker, a checkout machine, and the like, and the simulation program is a program used to check the operation of the fare determination program.

  The confirmation program receives the first fare data and the second fare data when the first fare data and the second fare data obtained by execution of the ticket generation program, the fare determination program, and the simulation program are given as inputs. Differences are extracted by matching the fare data, and aggregate data is generated by counting the number of differences for each ticket data according to importance, and displayed on the display device 13a.

  FIG. 2 is a flowchart showing the operation procedure of the fare determination program confirmation device 1, that is, the confirmation procedure of the fare determination program of the confirmation program.

  When the execution start input is received by the operation unit 14, the control unit 11 reads the confirmation program from the HDD 12 and executes it.

  Thereafter, when an input for starting the confirmation process of the fare determination program is received by the operation unit 14, the control unit 11 reads and executes the test ticket generation program from the HDD 12 as shown in FIG. 2 (S1). Specifically, test ticket data is generated and output to a ticket data file, and the ticket data file is stored in the HDD 12. In this embodiment, millions of ticket data are generated. The ticket data is generated by a procedure as shown in FIGS. 3A and 3B, for example.

  FIG. 3A is a flowchart showing a processing procedure for generating ticket data for a two-line communication commuter pass between a company A, which is a railway company, and a company B, a railway company different from the company A. First, the control unit 11 acquires the station code of the company A station stored in advance from the HDD 12 as departure station data so that all stations of the company A station are departure stations (S51). Next, the station code of the B company station, which is stored in advance as the destination station data from the HDD 12 so as to make all the stations of the B company station as the destination station, is acquired (S52).

  Thereafter, departure station arrival station data combining all station codes of departure station and arrival station is generated (S53). Next, all-line route information and the like stored in advance in the HDD 12 are read out, and route data of all routes that can arrive at the arrival station from the departure station is obtained for each departure station arrival station data (S54).

  Next, the data constituting the ticket data such as the obtained route data and departure station arrival station data is converted into encoded information (S55), and the train ticket data of all combinations of departure station and arrival station are generated.

  This boarding ticket data is boarding ticket data of a commuter pass (A company station B company station 2 line communication commuter pass) in which a station of company A station and a station of company B station can be used regularly.

  Thereafter, all the ticket data is output to a ticket data file and stored in the HDD 12 (S56).

  FIG. 3B is a flowchart showing a processing procedure for generating ticket data of a two-line contact ordinary ticket between a company A, which is a railway company, and a company B, a railway company different from the company A. . The control unit 11 acquires the station code of the A company station stored in advance from the HDD 12 as the departure station data so that all the stations of the A company station are the departure stations (S61). Next, the station codes of the communication stations of the A company station and the B company station which are stored in advance as HDD communication station data for all the communication stations of the A company station and the B company station are acquired from the HDD 12 (S62). Departure station contact station data combining all station codes with the contact station is generated (S63).

  Next, data for calculating the number of districts, all-line route information, etc. stored in advance from the HDD 12 are read, and for each departure station contact station data, district number data is obtained as the number of districts between the departure station and the contact station. For each station contact station data, route data of all possible routes that can arrive at the contact station from the departure station is acquired (S64). Also, the number of usable wards stored in advance is read from the HDD 12, and the number of wards available from the contact station to the B company bureau is subtracted from the number of available wards from the contact station to the company B. Obtained as station use ward number data (S65).

Next, the data constituting the ticket data such as the acquired route data and the number of districts data is converted into encoded information (S66), and the ticket data of all combinations from the departure station to the contact station is generated. This ticket data is a single ticket (A company B company B line 2) used when using from the A company station to the B company station via the A company / B company station. The ticket data stored in the contact ordinary ticket).

  Thereafter, all the ticket data are output to the above-described ticket data file and stored in the HDD 12 (S67).

Other ticket data mentioned above, Hatsueki and a and ticket data ticket that can be used in a section of the generated A company station by the combination of all the stations of the company A station destination station, generated test for In addition, boarding ticket data obtained by adding boarding station data with the station selected at random as the boarding station and boarding station data with the station selected at random as the boarding station is generated. The ticket data to which the boarding station data and the descending station data are added assumes a case where payment is required after getting over the station.

  Note that the test ticket data is often generated by combining various data such as the departure station, and thus the ticket data having a pattern similar to the front and back is often continuous.

  The control unit 11 and the test ticket generation program correspond to the test ticket generation means of the present invention.

  After generating test ticket data in S1, a fare determination program is read from the HDD 12 and executed (S2). Specifically, the ticket data is read from the HDD 12, and first fare data is generated for each ticket data. Thereafter, all the first fare data is output to the first fare data file and stored in the HDD 12.

  Next, the simulation program is read from the HDD 12 and executed (S3). Specifically, the ticket data is read from the HDD 12, and second fare data is generated for each ticket data. Thereafter, all the second fare data is output to the second fare data file and stored in the HDD 12.

  After the simulation program is executed in S3, a totaling / analysis process for performing comparison and the like based on the difference between the first fare data and the second fare data is executed (S4). Specifically, as shown in FIG. 4, the first fare data file and the second fare data file are read from the HDD 12 (S71), and the data of each item of both fare data is compared for each ticket data. A point is extracted (S72). In the present embodiment, differences are extracted only for the items of the adjustment fee, determination fee, ticket surface fee, adjustment start station, and availability determination result. Note that differences may be extracted not only for the data of the above items but also for data of other items.

  Next, the importance of the extracted difference is determined (S73). In the present embodiment, the importance is divided into three ranks A to C in descending order, and it is determined which rank the extracted difference corresponds to. Rank A corresponds to the difference in the settlement fee, Rank B corresponds to the difference in the judgment fee, the difference in the ticket surface fee, Rank C corresponds to the difference in the determination result of admissibility, and the difference in the settlement origin station. The control unit 11 corresponds to the determination unit of the present invention.

  Thereafter, aggregate data is generated by summing up the number of differences by rank for each ticket data, output to an aggregate data file, and stored in the HDD 12 (S74). In the total data, classification data (initial value 0: cause unanalyzed) is assigned for each difference. The classification data indicates the type of cause of the difference. Note that the control unit 11 corresponds to a counting unit of the present invention.

  Next, the filter condition is read from the HDD 12 (S75). Further, ticket data that has a difference corresponding to rank A and matches the filter condition is filtered (S76).

  The filter condition indicates that the ticket data having the difference whose cause has already been analyzed is filtered, and that the ticket data that is considered to have a difference due to the same cause is automatically of the same cause type. This is a search condition for searching for ticket data to be updated by adding classification data. In S76, the classification data included in the filter condition is added to the total data corresponding to the ticket data extracted by filtering and updated. The filter condition is input by the user via the operation unit 14.

  Next, it is determined whether or not there is ticket data having a difference corresponding to an unanalyzed rank A (S77). Specifically, it is determined whether or not there is ticket data whose classification data has an initial value of 0. In S77, when it is determined that there is no ticket data having a difference corresponding to the rank A that has not been analyzed, the analysis process is terminated and the execution of the confirmation program is terminated. In the present embodiment, it is determined whether or not there is ticket data having a difference whose cause corresponds to an unanalyzed A rank only for the lowest price route data described later.

  On the other hand, if it is determined in S77 that there is ticket data having a difference corresponding to rank A whose cause has not been analyzed for the cheapest route data, the ticket data having a difference of rank A in the cheapest route data. The ticket data number is selected and, for example, detailed information about the ticket data corresponding to the selected ticket data number is displayed on the display device 13a in the format shown in FIG. 5 (S78). The ticket data number is a unique number assigned to each ticket data, and associates the ticket data with the total data. The area P shows the total data of the ticket data as shown in FIG. 6 and displays the ticket data number and the number of differences between the ranks (A to C) in order from the left column.

  The area Q displays detailed information on the total data of the single ticket data selected in the area P as shown in FIG. In order from the left column, the route data number, each fare data item name to be compared, second fare data, first fare data, each item rank, comparison result (match or mismatch), and classification data are displayed. is doing.

  FIG. 7 displays the detailed information of the ticket data number 92 indicated by the alternate long and short dash line in FIG.

  As shown in FIG. 7, a route data number is assigned to each route data so as to distinguish data such as differences for each route data because a plurality of routes may occur between the departure station and the arrival station. Number. In addition, fare data is displayed for each route data. Of the plurality of route data, the lowest price route data that is the route data with the lowest settlement fee is displayed in the first line. For example, for the ticket data shown in FIG. 7, the route data of route data No. 1 with the lowest settlement fee among the route data of route data Nos. 1 to 3 is displayed as the lowest price route data on the first line. Yes.

  The region R displays analysis information such as classification data that is an analysis result. Analysis information such as classification data is registered in a host computer (not shown), and information is received via a communication means (not shown) when displayed. The area S displays detailed information of the single ticket data selected in the area P. The area T displays detailed information of the first fare data of the single ticket data selected in the area P. The area U displays the detailed information of the second fare data of the single ticket data selected in the area P.

  As a result, the operator can check the aggregated data immediately after generation, so that the burden on the operator can be reduced. Moreover, since total data, ticket data, etc. are displayed on one screen, it is easy for an operator to analyze the cause of the difference.

  In this embodiment, in S78, only the ticket data having a difference of rank A in the cheapest route data is selected and detailed information is displayed on the display device 13a. However, the present invention is not limited to this, and all routes are not limited to this. Detailed information may be displayed for ticket data having a difference of rank A for the data.

  After displaying on the display device 13a in S78, it is determined whether or not an input for interrupting the analysis process has been received by the operation unit 14 (S79). If it is determined that an input for interrupting has been received, the analysis process is terminated (suspended). To finish the execution of the confirmation program.

  If it is determined in S79 that no interruption input has been received, it is determined whether or not the filtering execution start input has been received by the operation unit 14 (S80), and until the filtering execution start input is received. The processes of S79 and S80 are repeated.

During this time, the worker analyzes the cause of the difference in the settlement fee for the ticket data displayed in the area P one by one. In the present embodiment, only the difference in the most important settlement fee in the lowest price route data is analyzed. When the wrong settlement amount of money, because the would bother to the user. In other words, the wrong amount is the biggest factor that reduces the trust of users.

  In addition, although the filtering process of S76 and S81 in this embodiment is performed only about the difference of the adjustment fee in the cheapest route data, it is not limited to this.

  When the cause of the difference is clarified, the operator inputs information such as a value used for classification data and other phenomenon names about the cause in the region R via the operation unit 14. When the input is accepted, information such as classification data is transmitted to a host computer (not shown) and registered. If classification data for the same cause has already been registered, it is not registered.

  At this time, if the search conditions for the ticket data having the same cause difference are clear, the operator inputs the setting of the filter condition. For example, if there is a defective part in the fare determination program, it is considered that there is a difference in the settlement fee due to this problem for the ticket data under the condition for executing this defective part. Therefore, the operator inputs the ticket data search condition and the classification data indicating the cause as the filter condition.

Further, for example, as shown in FIG. 6, the ticket data numbers 104 to 115 of the ticket data are considered to have different points due to the same cause because the number of different points in each rank is the same. . This is because the test ticket data is data generated by combining various kinds of information, and therefore, the ticket data having a similar pattern often continues. Therefore, the operator specifies, in the search conditions for ticket data as a filter condition, data that is identified as the cause of the difference in common with the ticket data numbers 104 to 115, and classification data of the cause corresponding to this Enter. Thereby, by analyzing the cause of the difference in one ticket data, the cause can be analyzed for the difference in other ticket data. Moreover, by setting the filter condition and executing the filtering process in S76 and S82 described below, the same classification data is automatically assigned and updated for the ticket data having a difference due to the same cause. can do.

  On the other hand, if the search condition for the ticket data having the same cause difference cannot be specified, the operator can enter the value of the classification data via the operation unit 14 in the column of the classification data of the settlement fee in the lowest price route data in the region Q. Enter.

  In addition, when an operator inputs a filter execution start via the operation unit 14 after newly inputting a filter condition by an analysis operation, the following processing is performed.

  In S78, when the control unit 11 determines that the input for starting the filtering is accepted, the filter condition is read from the HDD 12 (S81) and the difference corresponding to the A rank is determined in the same manner as the processes of S75 and S76 described above. Passage ticket data that has and satisfies the filter condition is filtered (S82). Further, in S82, the classification data included in the filter condition is added to the total data corresponding to the ticket data extracted by filtering, and updated. Thereafter, the process returns to S77.

  As described above, the worker proceeds with the above analysis work, updates the value of the classification data for the difference of rank A, or performs the filtering of S76, 81 to update the value of the classification data, so that the lowest price is obtained. When the classification data for the difference of rank A in the route data has a value indicating the cause type other than the initial value 0, the control unit 11 determines in S77 that the analysis of the cause of the difference of rank A has been completed. , The process ends.

  Although not shown, when the analysis work is started again in the case where the process is interrupted in S79, the operator inputs the start of execution of the confirmation program via the operation unit 14, and then the aggregation / analysis process The process is restarted from S75 in FIG. 4 by inputting the restart of execution and selecting the total data storage file of the total data.

  As described above, since the fare determination program confirmation device 1 of the present invention automatically generates test ticket data, it is not necessary for an operator to create test ticket data as in the prior art. The burden on the worker can be eliminated. In addition, since the second fare data corresponding to the predicted result that is the comparison target of the first fare data, which is the test result of the fare determination program, is automatically generated, the worker can use the second fare as in the past. There is no need to create data, and the burden on the operator can be eliminated. Thereby, the generation efficiency of the second fare data can be improved.

  Furthermore, since the display device 13a displays aggregated data in which the number of differences for each ticket data is aggregated according to importance, for example, when an operator preferentially analyzes the cause of differences with high importance In addition, it is not necessary to check whether the output difference is a difference having a high importance level, and the analysis work can be started immediately. Thereby, the analysis efficiency of the cause about a difference can be improved.

  In addition, test ticket data for multiple types of tickets is automatically generated, so the output is calculated after sufficient testing is performed assuming that multiple types of tickets are used. Data can be confirmed and analyzed.

  In addition, in S76 and S82, by filtering the ticket data having a difference corresponding to the rank A, it is possible to preferentially analyze from the difference having a high importance. In addition, by filtering the ticket data that matches the filter condition, it is not necessary for the operator to analyze the difference between the ticket data having the same cause, and the analysis efficiency can be improved. Furthermore, in order to confirm the operation of the fare determination program that has been corrected for defects again, the confirmation data is not required to be analyzed even when the confirmation program is executed and the confirmation program processing shown in FIG. 2 is executed again. Is not displayed, the analysis efficiency of the cause of the difference can be improved.

  In this embodiment, a program such as a confirmation program is stored in the HDD 12, but the present invention is not particularly limited to this, and may be stored in a recording medium such as a RAM built in the main body.

It is a block diagram which shows the structure of the fare determination program confirmation apparatus which concerns on embodiment of this invention. It is a flowchart which shows the operation | movement procedure of the fare determination program confirmation apparatus. It is a flowchart which shows the process sequence which produces | generates the ticket data of the fare determination program confirmation apparatus. It is a flowchart which shows the process sequence which performs the totaling / analysis process of the fare determination program confirmation apparatus. It is explanatory drawing which shows the display screen of the display apparatus with which the fare determination program confirmation apparatus was equipped. It is explanatory drawing which expanded a part of display screen of the display apparatus with which the fare determination program confirmation apparatus was equipped. It is explanatory drawing which expanded a part of display screen of the display apparatus with which the fare determination program confirmation apparatus was equipped.

Explanation of symbols

1-Fare determination program confirmation device 11-Control unit 12-HDD (hard disk)
13-output unit 13a-display device

Claims (7)

Test ticket generating means for generating a plurality of test ticket data for testing;
When the ticket data generated by the test ticket generating means is given as input data, a fare determination program for generating first fare data for the ticket data, and a specification different from the fare determination program Control means for executing a simulation program for generating second fare data for the ticket data when the ticket data generated by the test ticket generating means is given as input data;
For each of the ticket data, the first fare data generated by the control means and the second fare data are matched to extract a difference, and for each extracted difference, the degree of importance is set. A determination means for determining which of the plurality of defined ranks corresponds to the difference,
For each ticket data, based on the determination result of the determination means, a totaling means for generating total data in which the number of extracted differences is totaled according to the rank of importance,
For each of the ticket data, an output means for outputting the number of differences according to rank of importance based on the aggregate data generated by the aggregate means;
A fare determination program confirmation device comprising: filtering means for performing a filtering process for searching for ticket data presumed to have the same cause of the difference extracted by the determination means . If the cause of the difference has been analyzed for any of the ticket data that is estimated to have the same cause of the difference being found, the filtering means is obtained by the analysis. imparting classification data indicating the type of cause of differences occurs, fare determination program checking apparatus according to claim 1. When a plurality of routes are generated between the departure station and the arrival station, the control means generates the first fare data for each route, and the simulation program generates a second fare for each route. The fare determination program confirmation device according to claim 1 or 2 , which generates data. It said output means includes means for outputting a video signal for displaying the summary data to the display unit, the fare determination program verification device according to any one 請 Motomeko 1-3 of. The first fare data and the second fare data include an item of a settlement amount for the ticket data given as input,
The fare determination program confirmation device according to any one of claims 1 to 4, wherein the determination unit determines that the difference related to the settlement amount is a difference corresponding to a rank having the highest importance. A method for confirming a fare determination program for confirming a fare determination program for generating first fare data for the ticket data when the ticket data is given as input data,
Computer
A test ticket generation step for generating a plurality of test ticket data for testing;
When the ticket data generated by the test ticket generation step is given as input data, the fare determination program generates first fare data for the ticket data and is different from the fare determination program. A fare data generation step for generating second fare data for the ticket data in a simulation program created in the specifications;
For each of the ticket data, the first fare data generated in the fare data generation step and the second fare data are matched to extract a difference, and for each extracted difference, the degree of importance is large. A determination step for determining which of the plurality of ranks that define the difference corresponds to;
For each of the ticket data, based on the determination result of the determination step, a tabulation step for generating tabulated data in which the number of extracted differences is tabulated according to the rank of importance,
For each of the ticket data, an output step for outputting the number of differences according to rank of importance based on the aggregate data generated by the aggregate step;
A filtering step for performing a filtering process for searching for ticket data presumed to have the same cause of the difference extracted by the determination step;
How to check the fare determination program that executes A confirmation program for confirming a fare determination program for generating first fare data for the ticket data when the ticket data is given as input data,
A test ticket generation step for generating a plurality of test ticket data for testing;
When the ticket data generated by the test ticket generation step is given as input data, the fare determination program generates first fare data for the ticket data and is different from the fare determination program. A fare data generation step for generating second fare data for the ticket data in a simulation program created in the specifications;
For each of the ticket data, the first fare data generated in the fare data generation step and the second fare data are matched to extract a difference, and for each extracted difference, the degree of importance is large. A determination step for determining which of the plurality of ranks that define the difference corresponds to;
For each of the ticket data, based on the determination result of the determination step, a tabulation step for generating tabulated data in which the number of extracted differences is tabulated according to the rank of importance,
For each of the ticket data, an output step for outputting the number of differences according to rank of importance based on the aggregate data generated by the aggregate step;
A filtering step for performing a filtering process for searching for ticket data presumed to have the same cause of the difference extracted by the determination step;
A confirmation program that causes a computer to execute.

Images