JP5374405B2 - Model debugging apparatus and model debugging method - Google Patents

Description

  The present invention relates to a model debugging apparatus representing software specifications and a method thereof.

  In recent years, model-driven development has been applied for the purpose of reducing the cost and quality of system development. Model-driven development expresses the traditional design specifications written in natural language in a model format that uses diagrams such as decision tables or state transition diagrams, thereby clarifying the scope of the specifications and improving reusability. Rise. In addition, by automatically generating the source code from the model, it is a development method that saves the trouble of creating the source code that requires language acquisition. Non-Patent Document 1 discloses a development method performed by model driving.

  In the above development method, it is generally necessary to perform two operations for debugging. First, a log output unit is added to the source code generated from the model and executed, and errors are found and corrected on the source code using the log obtained after execution. Thereafter, the model portion corresponding to the corrected portion of the source code is found and the model is corrected. With these two operations, errors in the model and source code can be removed. Patent Document 1 discloses a method of debugging a source code created from a model in a decision table (decision table) format as an example of the debugging.

  As another method different from the model debugging method described above, there is a method of building a model simulator and executing and debugging the model as it is without creating a source code. Patent Document 2 discloses a model debugging method using a model simulator.

Japanese Patent Laid-Open No. 5-100891 Japanese Patent No. 4251964

David S.M. Frankel, “Model Driven Architecture: Applying MDA to Enterprise Computing”, Wiley, January 2003, pp. 11-29. 31-64

  The conventional model debugging method using the source code disclosed in Patent Document 1 requires two corrections for the same contents in the source code and the model, and it takes time and labor for double management. In actual development, the correction of the source code is the center due to the strict development schedule, and the corresponding model is not corrected sufficiently. As a result, there is a discrepancy between the model and the source code, and an accurate model does not exist, which makes it difficult for a person other than the developer to accurately grasp the system specifications. For this reason, in the next and subsequent system development, the design assets of the past cannot be used effectively, and even with the same specifications, there is time and effort to develop from the beginning, and the model that is characteristic of model-driven development is not sufficiently reused. .

  In addition, the model debugging method using the model simulator disclosed in Patent Document 2 does not have the above problem because the model can be directly executed / debugged without using source code. In addition, there is a development cost for preparing simulator data separately from the actual machine. Further, since execution is performed in an environment different from that of the actual machine, there is a possibility that the execution timing in the real-time system cannot be accurately reproduced, and an abnormality may occur on the actual machine even if the simulator is normal.

  SUMMARY OF THE INVENTION An object of the present invention is to provide an apparatus for performing accurate debugging using an actual machine while omitting the trouble of double management of a model and source code at the time of debugging in consideration of the above points.

In order to achieve the above object, the model debugging apparatus according to the present invention satisfies the condition described in the condition part indicating the condition for updating the equipment data, the condition part for updating the equipment data, and the specification of the software accompanying the equipment data update. Model editing means that edits the decision table model that is represented by the correspondence with the definition part that indicates the update contents of the equipment data, and the process that generates the source code from the edited decision table model and updates the equipment data A decision table model including a processing unit for each processing unit, identification information for identifying the processing unit, and source code generation means for adding log processing to output update information of equipment data to the generated source code,
As the source code is executed, the execution log obtained by log processing is read, the decision table model included in the execution log is displayed, the processing unit indicated by the identification information in the decision table model is highlighted, and the equipment data update information And execution result display means for displaying.

  In another desirable aspect of the present invention, the model debugging apparatus includes an initialization data holding unit that holds an initial value of the equipment data, and the execution result display means uses the update information of the equipment data included in the execution log, The initial value of the equipment data held in the initialization data holding means is updated, and a snapshot of the equipment data including other equipment data held in the initialization data holding means is displayed.

  According to still another desirable aspect of the present invention, the model debugging apparatus displays a list of decision table models and a list of equipment data included in the decision table model, and the user designates the decision table model in the list of decision table models. In response to the specification of equipment data in the equipment data list, a breakpoint holding means is provided for saving the specified model and equipment data as breakpoint information, and the execution result display means is designated as breakpoint information. The execution log up to the previous Dell or equipment data is read, and the initial value of the equipment data held in the initialization data holding means is updated using the equipment data update information contained in the read execution log. .

  According to the present invention, the model can be directly edited, and the source code can be automatically generated again from the corrected model, so that it is possible to save the trouble of double management of the model and the source code.

It is a structural example of model debugging. It is an example of a decision table model. It is the example which showed the decision table model in the XML format. This is an example in which source code is generated from a decision table model. It is an example of an execution log. It is an example of a breakpoint input screen. It is an example of breakpoint information. It is an example of a model execution result display screen. It is an example of a data snapshot confirmation screen. It is a hardware configuration example of model debugging. It is a flowchart which shows the flow of a process of a model debug apparatus. It is an example which shows the process which determines the breakpoint of the model to set next. It is an example which shows the process which determines the breakpoint of the installation to set next.

  The software updates the value (data) of the defined variable as the process is executed. In particular, in control software such as train route control, the state of equipment to be controlled and control commands (facility data) to the equipment are handled as variables. In the present embodiment, in the development of such software, it is noted that if the process to be executed is defined corresponding to the update of the equipment data, it is easy to define and debug the defined process. . The processing corresponding to the update of the equipment data is hereinafter referred to as a processing unit.

  A software specification that involves updating the equipment data, a condition part that indicates the conditions for updating the equipment data, and a definition part that indicates the update contents of the equipment data that are executed when the conditions described in this condition part are met It is represented by a decision table model that is represented by the corresponding relationship. One correspondence corresponds to a processing unit. Source code is generated from this decision table model. For each process that updates equipment data included in the decision table model (for each processing unit), executes the decision table model that includes the process, identification information that identifies the process, and update information of the equipment data that accompanies this process Log processing to be output as a log is added to the source code.

  As the source code is executed, the decision table model included in the execution log is displayed, the process indicated by the identification information is highlighted, and the update information of the facility data is displayed. With such a display, the user can determine the success or failure of the decision table model from the update information of the equipment data, so that the decision table model and the source code can be easily verified and debugged.

  A large-scale system such as a train route control system is divided into several subsystems such as train approach judgment and traffic light control, and a decision table model is created for each subsystem.

  FIG. 1 is a configuration example of a model debugging apparatus according to this embodiment. The model debugging apparatus 100 includes a model editing unit 101, a model holding unit 102, a source code generating unit 103, a source code holding unit 104, a program execution unit 105, an execution log holding unit 106, a breakpoint input unit 107, and a breakpoint holding unit 108. , A log reading control unit 109, an initialization data holding unit 110, an execution result display unit 111, and a confirmation result holding unit 112.

  The model editing unit 101 displays an empty or template decision table model on the screen of the display device, and causes the user to create a decision table model by editing the text of the decision table in units of cells. In the decision table model, the user inputs conditions and definitions to be described later, with a group of processes involving updating of facility data as a processing unit, based on the required specifications of the software. Therefore, the decision table model includes at least one processing unit. The model editing unit 101 stores the edited decision table model in the model holding unit 102.

  The source code generation unit 103 generates a source code from the decision table model stored in the model holding unit 102 and stores it in the source code holding unit 104. When generating source code, information and equipment related to the decision table model corresponding to the processing unit for each processing unit of the source code corresponding to the processing unit included in the decision table model (processing involving updating of certain equipment data) Add a log output process that outputs data update information.

  The program execution unit 105 compiles the source code held in the source code holding unit 104 into an executable program format, and executes the compiled program. The log output process added to the source code with the execution of the program outputs an execution log including information related to the processing unit of the decision table model and the update information of the equipment data in a text file format and saves it in the execution log holding unit 106 To do.

  The breakpoint input unit 107 displays the decision table model held in the model holding unit 102 and the equipment data held in the initialization data holding unit 110 on the breakpoint input screen, and breakpoint information used when debugging. Let the user select a decision table model and equipment data. If debugging using breakpoint information is not performed, it is not necessary to select a decision table model and equipment data.

  The initialization data holding unit 110 holds equipment data. An initial value is set in advance for the equipment data.

  The log reading control unit 109 displays the execution log held in the execution log holding unit 106 as one line (corresponding to the processing unit) until the breakpoint information of the decision table model and equipment data held in the breakpoint holding unit 108 appears. Execution log), and sequentially read the read information to the execution result display unit 111. When debugging using breakpoint information is not performed, the execution log up to the completion of program execution is read. Note that the data transfer to the execution result display unit 111 may be performed collectively after the execution log is read to the end.

  The execution result display unit 111 displays the information of the decision table model held in the model holding unit 102 on the model execution result display screen, reads the execution log received from the log reading control unit 109 line by line, and stores it in the execution log. Along with the update information of the included equipment data, the row of the processing unit of the decision table model corresponding to the update information is highlighted. A check box for user confirmation is also displayed together with a part for displaying the update information of the equipment data so that the user confirmation result can be held. In addition, the execution result display unit 111 uses the initial value of the facility data held in the initialization data holding unit 110 to construct the initial state of the facility data on the memory. After that, based on the update information of the equipment data included in the execution log data received from the execution log reading control unit 109, a snapshot of the equipment data value at the time when the specified breakpoint model is executed is taken, and the data snap Display on the shot confirmation screen. When the user finds an error in the model using the model execution result display screen and the data snapshot confirmation screen, the execution result display unit 111 notifies the model editing unit 101 of the information on the model having the error, and immediately To be able to edit the model.

  The confirmation result holding unit 112 holds information checked by the user on the model execution result display screen. The stored information is reused at the next and subsequent debugging, and if the model, the equipment handled by the model, and the equipment data value to be set are the same as those at the previous debugging, it is checked.

  FIG. 2 is an example of a decision table model edited and created by the model editing unit 101. FIG. 2 shows a determination table model 200 having a table name “train approach determination processing” and a determination table model 210 having a table name “signal control processing”. The table names “train approach judgment processing” and “traffic signal control processing” are model names and indicate software to be developed. The decision tables 200 and 210 include a process name, a condition part, and a definition part corresponding to a serial number (No) for identifying a processing unit. The process name is a name of a process defined by the condition part and the definition part. In the condition part, the condition part describes the conditions for executing the process defined in the definition part. In the definition part, all the conditions described in the condition part hold (if there are multiple conditions, the AND condition is Describe the contents of the process to be executed if The decision table model of the software to be developed is described by a condition part and a definition part corresponding to a serial number (No) that is identification information of processing units constituting the decision table model. Similarly, the processing according to various conditions is defined by describing the condition part and the definition part over a plurality of lines like processing units 201, 202, 203 and 211, 212, 213. The process described in the definition part of the decision table 200 is used in the condition part of the decision table 210. In this way, the process described in the definition part of a certain decision table is used as the condition part of another decision table. This is a description method that can be used as a condition to be described.

  FIG. 3 is an example showing the decision table model of FIG. 2 in the XML file format. 3, 301, 302, 303, 311, 312, and 313 correspond to the processing units 201, 202, 203, 211, 212, and 213 in FIG. The format of data to be saved will be described by taking XML file formats 300 and 310 as an example, but any file format or database that can read text information such as CSV format may be used.

  FIG. 4 is an example in which the decision table model of FIG. 2 is output as C ++ source code. FIG. 4 is expressed in Japanese for convenience. In the source codes 400 and 410 of FIG. 4, the condition part in the decision tables 200 and 210 is the condition part 401, 403, 405, 411, 413, 415 of the if clause, and the definition part is the body part 402 of the if clause. 404, 406, 412, 414, 416 and converted into an executable format. Here, in addition to the contents of the decision table model, a log output unit that outputs information about the execution time and the corresponding decision table model is added to the main body portion of the “if” section, as indicated by the underline in the figure. The information regarding the decision table model includes a decision table model name (table name), a serial number for identifying a processing unit in the decision table model, an attribute name of the facility, and an attribute value thereof. Depending on the target equipment, the attribute name of the equipment may be the equipment name (equipment data name), and the attribute value may be the state of the equipment (equipment data value).

  FIG. 5 is an example of an execution log. In the execution log, information regarding the execution time and the determination table model is output in the order of execution.

  FIG. 6 is an example of a breakpoint input screen 600 displayed by the breakpoint input unit. The model list view 610 is a view that displays a list of models that have been created. In this view 610, in addition to model information (model type, model name, model line name) corresponding to one line (record) of the decision table model, a breakpoint (BP in the figure, BP) 611 control is provided. indicate. The equipment data list view 620 is a view that displays a list of equipment data (equipment names) used by the decision table model included in the model list view 610 in the order of station and equipment type. This view 620 also displays a breakpoint 621 control. In the screen including these two views, the user checks the breakpoint 611 in the procedure (view) corresponding to the decision table model for which the facility data being executed is to be confirmed in the procedure list view 610. Moreover, since the execution format program generated and compiled from the decision table model is repeatedly executed for all stations, when checking by paying attention to a specific station equipment, the equipment data list view 620 is a confirmation target. A breakpoint 621 is set in the equipment data. It should be noted that at least one of the breakpoints corresponding to the decision table model and the breakpoints corresponding to the equipment data only needs to be set, and if both are set, the breakpoint that arrives first in the program execution becomes effective. .

  FIG. 7 is an example of breakpoint information 700 held by the breakpoint holding unit 108. Breakpoints specified for a plurality of pieces of equipment data corresponding to one model can be held.

  FIG. 8 is an example of a model execution result display screen 800 displayed by the execution result display unit 111. The step execution control 810 and the batch execution control 811 are user interfaces for the user to instruct the log reading control unit 109 how to read the log. The former is a user interface for the user to check the model execution result step by step, and the latter is a user interface for the user to check the model execution result collectively. The step execution control 810 performs log reading control so that one line (execution log corresponding to a processing unit) is read from the execution log holding unit 106 by one action (one operation of the step execution control 810). The unit 109 is instructed. The batch execution control 811 is effective when a breakpoint is set, and instructs the log reading control unit 109 to read the execution log until the set breakpoint information appears. The model execution history view 820 is displayed based on the contents of the execution log obtained by the action for the step execution control 810 or the batch execution control 811. The model execution history view 820 includes executed decision table models 822, 823, and 824, equipment data update information (update results) 825, 827, and 829 executed in each model, and a check box 826 for user confirmation of equipment data update information, 828, 830 are included. In the executed models 822, 823, and 824, the line corresponding to the processing unit executed in each model is highlighted (for example, the display color is different from other colors, or the character color and the background color are highlighted). In the equipment data update information 825, 827, and 829, an actually set attribute (equipment data name or equipment data attribute) and its attribute value (equipment data state or equipment data attribute value) are displayed. Since information on many stations is displayed in the model execution history view 820, information to be displayed and confirmed at a time can be reduced by selecting a station using the station selection control 821.

  FIG. 9 is a data snapshot confirmation screen 900 that displays a snapshot of equipment data values at the time when a breakpoint is set (when the model is executed up to the breakpoint). The equipment data list view 910 is a view that displays a list of equipment, similar to the equipment data list view 620 of the breakpoint input screen 600, but does not display the breakpoint control 621. The data snapshot view 920 displays in detail the attribute information (attribute name, attribute value) of the equipment in units of equipment. When displaying facility information, the user designates a facility by selecting one line of the facility data list view 910 or by entering a facility name in the facility name input form 921. When one line is selected in the equipment data list view 910, the equipment name input form 921 automatically displays the selected equipment name. The detailed equipment information display view 922 includes an equipment attribute name, an attribute value, a corresponding row of the model in which this attribute is last changed (processing of a related model), and a check box for confirming the result by the user. The user checks the check box in the row for the attribute whose result is confirmed in the detailed facility information display view 922.

  FIG. 10 shows a hardware configuration example of the model debugging apparatus 100. The model debug device 100 includes a CPU 1002, a memory 1003, an external storage device 1004, a display device 1005, an input device 1006, and a communication unit 1007. The CPU 1002 executes a program stored in the memory 1003. Specifically, the model editing unit 101, the source code generation unit 103, the program execution unit 105, the breakpoint input unit 107, the log reading control unit 109, and the execution result display unit 111 are executed. The memory 1003 is a storage area for storing a program and data necessary for program execution by the CPU 1002. Specifically, the program to be stored is the same as the program executed by the CPU 1002, and data necessary for program execution includes model information held in the model holding unit 102 and source code held in the source code holding unit 104. The execution log held in the execution log holding unit 106, the breakpoint information held in the breakpoint holding unit 108, the initial value of facility data held in the initialization data holding unit 110, and held in the confirmation result holding unit 112 This is user confirmation result information. However, these pieces of information are not always stored in the memory 1003 but are normally stored in the external storage device 1004, and are read out as necessary when the program is executed. The external storage device 1004 holds data and programs stored in the memory 1003. The display device 1005 displays the processing result of the program. The display device is, for example, a display. The input device 1006 receives an execution instruction and data input necessary for execution from the user. Specifically, model information input in the model editing unit 101, source code generation instruction in the source code generation unit 103, source code compilation and execution instruction in the program execution unit 105, breakpoint information input in the breakpoint input unit 107, log reading An execution log reading instruction in the control unit 109 and a user confirmation result input in the execution result display unit 111. A communication unit 1007 communicates with other devices via the network 1001. In FIG. 1, the model debug device is realized on one device, but each function and data storage area can be executed by another device, and the communication unit 1007 is provided when executed by a plurality of devices. To communicate between devices.

  FIG. 11 is a flowchart showing the flow of processing of each unit of the model debugging apparatus 100. First, the CPU 1002 executes the model editing unit 101 and displays a model editing screen. Using the model editing screen, the user creates a decision table model based on the required specifications and at the same time prepares equipment data held in the initialization data holding unit 110. The model editing unit 101 stores information on the created decision table model in the model holding unit 102. (Step 1101).

  Subsequently, the CPU 1002 executes the source code generation unit 103, generates a source code using the decision table model held in the model holding unit 102, and stores it in the source code holding unit (step 1102). The CPU 1002 executes the program execution unit 105, compiles and executes the source code held in the source code holding unit 104 based on the execution request from the user, and stores the execution log in the execution log holding unit 106 ( Step 1103). The CPU 1002 executes the execution result display unit 111 and displays the model execution result display screen 800 (step 1104). However, at this time, only the step execution control 810 and the batch execution control 811 are displayed, and the user executes an action using either one of the controls. The CPU 1002 executes the log reading control unit 109 and determines whether the action executed by the user is debugging using breakpoint information (step 1105).

  In the case of debugging using breakpoint information, the log execution control unit 109 uses the decision table model held in the model holding unit 102 and the equipment data held in the initialization data holding unit 110 to breakpoints. The input unit 107 is executed and a breakpoint input screen is displayed. The user inputs a breakpoint to the model and facility data on the breakpoint input screen. Thereafter, the breakpoint input unit 107 stores the input breakpoint information in the breakpoint holding unit 108 (step 1106). Thereafter, the log reading control unit 109 reads the execution log held in the execution log holding unit 106 until the input breakpoint information appears, and passes it to the execution result display unit 111 (step 1107).

  On the other hand, if the action executed by the user is not debugging using breakpoint information, the log execution control unit 109 reads the execution log held in the execution log holding unit 106 and passes it to the execution result display unit 111 (step S1). 1108). Here, the execution result display unit 111 checks whether or not a result already confirmed by the user already exists in the confirmation result holding unit 112 (step 1109). If there is a result confirmed by the user, the information is read (step 1110). The execution result display unit 111 displays a model execution result display screen based on the model procedure information and facility data update information included in the received execution log. In addition, the execution result display unit 111 reads the facility data held in the initialization data holding unit 110 into the memory, and sets the facility data based on the facility data change information included in the execution log from the log reading control unit 109. Is taken and displayed on the data snapshot confirmation screen. Thereafter, the user confirms the facility data change information and the facility data snapshot on the screen, inputs the confirmation result for each attribute, and stores it in the confirmation result holding unit 112 (step 1111). When checking the result, the user checks whether there is an error in the equipment data. If there is an error, the execution result display unit 111 informs the model editing unit 101 of information on the model having an error (step 1112). If there is no error, the process is terminated (step 1103). Thereafter, steps 1101 to 1112 are repeated until there is no error in the facility data.

  FIG. 12 shows an example of a process for determining a breakpoint of a model to be set next when a model error cannot be found by executing the model once. In the model list 610, when the break point of No. 6 is set and the process 1202 of the model of that part is executed, the process immediately before calling the process 1202 is specified (1201), and the corresponding model list 610 is applicable. Highlight the part.

  FIG. 13 shows an example of a process for determining a breakpoint for the next equipment to be set when a model error cannot be found by executing the model once. In the equipment data list 620, when a breakpoint is set for the equipment No. 1301 and executed, the equipment related to the equipment 1301 is identified from the equipment correspondence definition 1303 (1302), and the equipment data list 620 Highlight the relevant part. In the facility correspondence definition 1303, a facility related to a certain facility is defined. When a plurality of facilities related to one facility are defined in the facility correspondence relationship definition 1303, the plurality of facilities are highlighted. In addition, it is possible to specify a facility whose result has already been confirmed using the breakpoint information held in the breakpoint holding unit 108 (1304), and to prevent the checkpoint from being displayed for the breakpoint of that facility.

  According to this embodiment, the corresponding decision table model information is embedded in the log output portion of the source code generated from the decision table model, and the log is output at the time of execution. Debugging is possible. As a result, the model can be directly edited, and the source code can be automatically generated again from the corrected model, so that the labor of double management of the model and the source code can be saved.

  In addition, the decision table model includes only design information that satisfies the required specifications, but the source code also includes information that is not related to the direct specifications, such as detailed arithmetic processing on the implementation for realizing it. Therefore, compared to the debugging of source code, where details of the implementation must be grasped, the debugging of the model eliminates the personalization of work.

  Furthermore, in this embodiment, since the results on the actual machine are used, defects such as execution timing can be accurately reproduced as compared with the debugging in the simulator that uses the result of the non-real machine environment, so that the quality of the software to be developed is improved. Leads to. Moreover, since it is not necessary to prepare a simulator and simulator data, software development costs can be reduced.

  DESCRIPTION OF SYMBOLS 100: Model debug apparatus, 101: Model edit part, 102: Model holding part, 103: Source code production | generation part, 104: Source code holding part, 105: Program execution part, 106: Execution log holding part, 107: Breakpoint input 108: Breakpoint holding unit 109: Log reading control unit 110: Initialization data holding unit 111: Execution result display unit 112: Confirmation result holding unit

Claims (9)

The specification of the software accompanying the update of the equipment data indicates a condition part indicating a condition for updating the equipment data, and the update contents of the equipment data executed when the condition described in the condition part is satisfied Model editing means for editing the decision table model represented by the correspondence with the definition part,
Source code is generated from the edited decision table model, and for each processing unit that is processing for updating the equipment data, the decision table model including the processing unit, identification information for identifying the processing unit, and the equipment Source code generating means for adding log processing for outputting data update information to the generated source code;
As the source code is executed, the execution log obtained by the log process is read, the decision table model included in the execution log is displayed, and the processing unit indicated by the identification information in the decision table model is highlighted. A model debugging apparatus comprising: an execution result display means for displaying and displaying update information of the equipment data. Initialization data holding means for holding an initial value of the equipment data is provided, and the execution result display means is held in the initialization data holding means by using update information of the equipment data included in the execution log. The model debugging apparatus according to claim 1, wherein the initial value of the equipment data is updated, and a snapshot of equipment data including other equipment data held in the initialization data holding unit is displayed. In the model debug device, a list of the decision table models and a list of the equipment data included in the decision table model are displayed, and a user designates a decision table model in the decision table model list and / or the In response to the designation of equipment data in the equipment data list, a breakpoint holding means for saving the designated model and equipment data as breakpoint information is provided.
The execution result display means reads the execution log up to the model or the equipment data designated as the breakpoint information, and uses the update information of the equipment data included in the read execution log, The model debugging apparatus according to claim 2, wherein the initial value of the facility data held in the initialization data holding unit is updated. The breakpoint holding means derives, from the model, a line that calls a component of the model included in the breakpoint information saved at the time of previous execution when an error in the model cannot be found in one execution. The model debugging apparatus according to claim 3, wherein the model debugging apparatus is highlighted on a list of components of the model to assist a user in selecting. The breakpoint holding means derives from the model equipment data related to the equipment data included in the breakpoint information saved at the previous execution when the model error cannot be found in one execution. The model debugging apparatus according to claim 3, wherein the model debugging apparatus is highlighted on a list of the equipment data to assist a user in selecting. The execution result display means designates the result of the equipment data confirmed by the user, stores the information of the designated equipment data, and uses the confirmed equipment data information at the next execution to use the equipment data that has not been previously confirmed to the user. The model debugging apparatus according to claim 3, wherein only the information is displayed. A model debugging method using a model in a model debugging apparatus, wherein the model debugging apparatus includes:
The specification of the software accompanying the update of the equipment data indicates a condition part indicating a condition for updating the equipment data, and the update contents of the equipment data executed when the condition described in the condition part is satisfied Edit the decision table model represented by the correspondence with the definition part,
Generate source code from the edited decision table model,
Log processing for outputting the decision table model including the processing unit, identification information for identifying the processing unit, and update information of the facility data for each processing unit that is a process for updating the facility data in the source code Add
As the source code is executed, an execution log obtained by the log process is read.
Displaying the decision table model included in the execution log;
Highlighting the processing unit indicated by the identification information in the decision table model;
A model debugging method comprising displaying update information of the equipment data. The model debug device holds an initial value of the equipment data, updates the initial value of the equipment data to be held by using update information of the equipment data included in the execution log, and holds the other The model debugging method according to claim 7, wherein a snapshot of the equipment data including the equipment data is displayed. The model debugging device displays a list of the decision table models and a list of the equipment data included in the decision table model,
In response to designation of a decision table model in the list of decision table models and / or designation of equipment data in the list of equipment data by a user, the designated model and equipment data are saved as breakpoint information,
The execution log up to the model and the equipment data designated as the breakpoint information is read, and the update information of the equipment data included in the read execution log is used to store the equipment data. The model debugging method according to claim 8, wherein the initial value is updated.

Images