JP6665637B2 - Program creation support system - Google Patents

Description

  The present invention relates to a program creation support system. More specifically, the present invention relates to a program creation support system that supports creation of a program for performing a process of changing a database table associated with an operation screen when a predetermined operation is performed on the operation screen.

  In the development process of a program using the program creation support system, for example, as disclosed in Patent Document 1 (Japanese Patent Application Laid-Open No. H8-16429), a bug of a program created using the program creation support system is found. Includes test work to fix. The efficiency of test work has a great effect on the efficiency of program development.

  Some programs created by using the program creation support system change a database table associated with the operation screen when a predetermined operation is performed on the operation screen. When developing a program for performing such processing, it is tested whether or not the operation screen operates correctly as a result of a predetermined operation on the operation screen. When a program for performing such processing is developed, it is tested whether or not the information in the database table is changed as intended as a result of a predetermined operation on the operation screen.

  When such a test is performed, there is a problem that the test operation time is likely to be long for the following reasons.

  For one thing, when performing such a test, the test operator needs to use a database access tool after a predetermined operation on the operation screen to check whether the information in the database table has been correctly changed. That is, the test operator needs to separately confirm that the operation screen correctly operates by the predetermined operation on the operation screen and that the information in the database table is correctly changed by the predetermined operation on the operation screen. Therefore, confirmation is troublesome, and the test operation time is likely to be prolonged.

  In addition, the test work of such a program is not performed by one test worker, but is often performed by a plurality of test workers in parallel. In such an environment where a plurality of test workers perform tests at the same time, whether the database table has been changed is the result of the operation on the operation screen performed by the test worker A or the test work performed by the test worker B. In some cases, it is not known whether the result is the result of the operation on the operation screen. Therefore, if the operation on the operation screen performed by the test operator does not match the change in the database table, the operation on the operation screen of another test operator may affect the database table. May need to be verified. Therefore, confirmation is troublesome, and the test operation time is likely to be prolonged.

  An object of the present invention is to provide a program creation support system that can efficiently test a program when a predetermined operation is performed on an operation screen and a program for performing a process of changing a database table associated with the operation screen is created. Is to provide.

  A program creation support system according to a first aspect of the present invention includes an output unit, a reception unit, and a change unit. The output unit displays an operation screen related to information in the database table on a display unit that presents information to a user. The receiving unit receives a predetermined operation on the operation screen displayed on the display unit. The change unit changes information in the database table according to a predetermined operation. The output unit causes the display unit to display, at the same time as the operation screen, a history screen indicating a change history of the database table according to the predetermined operation.

  In the program creation support system according to the first aspect of the present invention, the operation screen and the history screen indicating the change history of the database are simultaneously displayed on the display unit. Therefore, the user (test operator) of the system performing the test can simultaneously confirm that the operation screen has correctly operated and that the database table has been correctly (as intended) changed. Therefore, in this program creation support system, the test operation time can be reduced.

  Further, the history screen displayed on the display unit in the program creation support system according to the first aspect of the present invention presents not a database table itself but a history of database table change according to a predetermined operation on the operation screen. Therefore, the user can confirm in a short time whether or not the intended change in the database table matches the actual change in the database table for the predetermined operation. Further, here, the change history of the database table according to the predetermined operation on the operation screen displayed on the display unit is displayed on the display unit. Therefore, the user does not mistakenly regard a change in the database table resulting from the operation of another user as a change in the database table resulting from the user's own operation. From such a viewpoint, the program creation support system according to the first aspect of the present invention can reduce the test operation time.

  A program creation support system according to a second aspect of the present invention is the program creation support system according to the first aspect, wherein the output unit displays an operation screen on each of the plurality of display units independently of the other display units. Let it. The receiving unit receives a predetermined operation on an operation screen displayed on each of the plurality of display units for each of the display units. The output unit causes each display unit to display, at the same time as the operation screen, a history screen indicating a change history of the database table according to a predetermined operation on the operation screen.

  In the program creation support system according to the second aspect of the present invention, an operation screen and a history screen indicating a change history of a database table according to a predetermined operation on the operation screen are displayed on the plurality of display units. Therefore, in this program creation support system, a plurality of users can execute a program test at the same time. Here, the change history of the database table generated as a result of each user performing a predetermined operation on the operation screen is displayed on the display unit that the user is looking at. Therefore, the user does not mistakenly regard a change in the database table resulting from the operation of another user as a change in the database table resulting from the user's own operation. Therefore, in the present program creation support system, a test can be efficiently executed even when a plurality of users execute the test of the program at the same time, and the test operation time can be reduced.

  A program creation support system according to a third aspect of the present invention is the program creation support system according to the first aspect or the second aspect, wherein the change unit changes information in a database table according to a command corresponding to a predetermined operation. I do. The output unit causes the display unit to display a message corresponding to a command corresponding to the predetermined operation on the history screen as a change history of the database table.

  In the program creation support system according to the third aspect of the present invention, a message corresponding to a command given to a change unit for changing information of a database table in response to a predetermined operation performed on an operation screen is displayed on a display unit. Let me do. In other words, in the present program creation support system, a message according to a command to change the information of the database table is displayed on the display unit instead of the content of the database table itself. Therefore, in this program creation support system, the user can easily confirm whether the predetermined operation on the operation screen and the content of the command given to the change unit correctly correspond.

  In addition, with this configuration, each user can execute a database operation by performing a predetermined operation even when a change occurs in the database table due to an operation of another user who is simultaneously testing the program. You can see exactly how the table has changed.

  A program creation support system according to a fourth aspect of the present invention is the program creation support system according to the third aspect, wherein the command given to the change unit includes registration of information in a database table, contents of information in the database table Changes and / or deletion of information from database tables.

  In the program creation support system according to the fourth aspect of the present invention, the user can easily confirm various changes made to the information in the database table by a message displayed on the history screen.

  A program creation support system according to a fifth aspect of the present invention is the program creation support system according to the third or fourth aspect, wherein the message is a summary of the contents of the command.

  In the program creation support system according to the fifth aspect of the present invention, a message summarizing the contents of the command is displayed on the history screen as the change history of the database table. Therefore, the user can easily understand what changes have been made to the database tables.

  A program creation support system according to a sixth aspect of the present invention is the program creation support system according to any of the third to fifth aspects, wherein the message includes the number of pieces of information changed in the database table.

  In the program creation support system according to the sixth aspect of the present invention, the user can grasp not only what kind of change has been made to the database table but also how many pieces of information have been changed. Therefore, in this program creation support system, the user can quickly and correctly grasp whether the intended change has been made to the database table by a predetermined operation on the operation screen.

  A program creation support system according to a seventh aspect of the present invention is the program creation support system according to any one of the first to sixth aspects, wherein the receiving unit stores a database table in a history screen displayed on the display unit. A designation operation for designating at least one history in the change history is further received. The output unit further causes the display unit to display details of the change in the information of the database table for the history specified by the specifying operation.

  In the program creation support system according to the seventh aspect of the present invention, the user can quickly confirm the details of the change made to the information in the database table in response to the predetermined operation as needed. As a result, the user can efficiently proceed with the test.

  In the program creation support system according to the first aspect of the present invention, the user of the system (the tester of the program) confirms that the operation screen has been correctly operated and that the database table has been correctly (as intended) changed. Can be confirmed at the same time. Therefore, in this program creation support system, the test operation time can be reduced.

  In the program creation support system according to the second aspect of the present invention, the test can be efficiently executed even when a plurality of users execute the test of the program at the same time, and the test operation time can be reduced.

  In the program creation support system according to the third aspect of the present invention, the user can easily confirm whether the predetermined operation on the operation screen and the content of the command given to the change unit are correctly associated.

  In the program creation support system according to the fourth aspect of the present invention, the user can easily confirm various changes made to the information in the database table by a message displayed on the history screen.

  In the program creation support system according to the fifth aspect of the present invention, the user can easily grasp what kind of change has been made to the database table.

  In the program creation support system according to the sixth aspect of the present invention, the user can quickly and correctly grasp whether the intended change has been made in the database table by a predetermined operation on the operation screen.

  In the program creation support system according to the seventh aspect of the present invention, a user can efficiently perform a test.

It is a block diagram of a program creation support system concerning one embodiment of the present invention. In the program creation support system of FIG. 1, the output unit of the server is an example of an operation screen and a history screen displayed on the display unit of the user terminal. 2 is an example of a database table whose information is changed by a change unit of the program creation support system of FIG. 1. FIG. 3 is an example of a database table of a customer master. When a predetermined operation is performed on the operation screen, a flow chart showing the flow of processing in the program creation support system 100 of FIG. 1 when confirming the operation of a program for performing a process of changing a database table associated with the operation screen. is there. FIG. 4 particularly shows the flow of processing in the program creation support system 100 of FIG. 1 when a predetermined operation is performed on the operation screen to confirm the operation of the program.

  A program creation support system 100 according to an embodiment of the present invention will be described with reference to the drawings. Note that the following description is merely an embodiment of the program creation support system according to the present invention, and can be appropriately changed without changing the gist of the present invention.

(1) Overall Overview The program creation support system 100 of this embodiment is used to register information in a database and create an application program that utilizes the registered information. The application program created by the program creation support system 100 of the present embodiment is a customer management application program. However, the program created using the program creation support system 100 is not limited to an application program for customer management, and may be a program used for other purposes.

  The program creation support system 100 according to the present embodiment is a system that allows a user of the system to create a program in a non-programming environment. In other words, the program creation support system 100 is a system that allows a user of the system to create a program without coding. Here, coding refers to using a programming language to describe a program in a form that can be processed by a computer. In the program creation support system 100, a program described in a programming language such as SQL (Structured Query Language) is generated by operating a GUI (Graphical User Interface) by combining prepared program parts (program patterns). . For example, in the program creation support system 100, a user executes a desired program by arranging previously prepared program parts on a program creation screen by mouse operation such as drag and drop. Create

  The language of the created program is not limited to SQL. In addition, the non-programming environment here is not limited to an environment in which a user of the system does not perform any coding. When creating a program using the program creation support system 100, the user may create at least a part of the program by coding.

  FIG. 1 is a block diagram showing a physical configuration of the program creation support system 100. The program creation support system 100 mainly includes a server 200 (see FIG. 1).

  The server 200 mainly includes an output unit 210, a reception unit 220, an input unit 230, a display unit 240, a storage unit 250, a processing unit 260, and a database 300 (see FIG. 1). The database 300 includes, for example, five DB tables 310, 320, 330, 340, and 350 (database tables 310, 320, 330, 340, and 350) (see FIG. 1). The number of DB tables 310-350 is an example, and is not limited to five.

  The server 200 is connected to user terminals 10A, 10B, and 10C used by users who develop programs via a network 50 (see FIG. 1). The user develops a program from the user terminals 10A, 10B, and 10C using the program creation support system 100 via the network 50. In FIG. 1, the program creation support system 100 is connected to three user terminals 10A, 10B, and 10C via the network 50. However, the number of user terminals is merely an example and is not limited to this. Not something. For example, the program creation support system 100 may be connected to one or two user terminals, or may be connected to four or more user terminals.

  In the present embodiment, the network 50 is the Internet. However, the network 50 is not limited to the Internet. The network 50 may be a LAN (Local Area Network), an intranet, or the like.

(2) Detailed Description The user terminals 10A, 10B, 10C and the server 200 will be described in detail.

(2-1) User Terminal The user terminals 10A, 10B, and 10C are client-side computers that receive a program creation support function from the server 200.

  The user terminals 10A, 10B, 10C are, for example, general personal computers. The user terminals 10A, 10B, and 10C include, for example, a CPU (Central Processing Unit), a memory, an external storage device such as a hard disk, and a communication device (not shown). The user terminals 10A, 10B, and 10C have input units 20A, 20B, and 20C such as a keyboard, a mouse, and a touch panel, respectively. The user terminals 10A, 10B, and 10C have display units 30A, 30B, and 30C, respectively, such as displays. The user terminals 10A, 10B, and 10C execute various processes by causing the CPU to read a program stored in the hard disk into the memory and execute the program.

  Here, among the functional units of the user terminals 10A, 10B, and 10C, the input units 20A, 20B, and 20C and the display units 30A, 30B, and 30C related to the creation of a program using the program creation support system 100 will be mainly described. I do.

  Since the user terminals 10A, 10B, and 10C are all configured in the same manner, only the user terminal 10A (only the input unit 20A and the display unit 30A of the user terminal 10A) will be described here. Description of 10B and 10C is omitted.

(2-1-1) Input Unit The input unit 20A is an input device such as a keyboard, a mouse, and a touch panel as described above. When creating a program from the user terminal 10A using the program creation support system 100, the user performs various operations on a screen displayed on the display unit 30A using the input unit 20A.

  Operations performed from the input unit 20A on the screen displayed on the display unit 30A include lines on the operation screen (screens for performing operations related to the information of the DB tables 310, 320, 330, 340, and 350) displayed on the display unit 30A. This includes a predetermined operation for changing information in the DB tables 310 to 350 of the database 300. The details of the predetermined operation for changing the information in the DB tables 310 to 350 will be described later together with the description of the operation screen displayed on the display unit 30A.

  For an operation performed on the screen displayed on the display unit 30A from the input unit 20A, at least one history in the change history of the database table is specified on a history screen described later displayed on the display unit 30A. Including the specification operation for. The content of the designation operation for designating at least one history in the change history of the database table will be described later together with the description of the history screen (second history screen 36A described later) displayed on the display unit 30A.

  The operation on the operation screen displayed on the display unit 30A and the operation on the history screen displayed on the display unit 30A using the input unit 20A are received by the reception unit 220 of the server 200 via the network 50.

(2-1-2) Display unit The display unit 30A presents information to the user. The display unit 30A is, for example, a display as described above.

  Various screens for presenting various information to the user are displayed on the display unit 30A by the output unit 210 of the server 200.

  Here, the display contents displayed on the display unit 30A when the user tests the program created by using the program creation support system 100 will be described. In particular, here, when an operation check test is performed on the operation screen on which the information of the DB tables 310 to 350 of the database 300 is changed when the predetermined operation is performed on the screen, the display is performed. Display contents displayed on the unit 30A will be described. Hereinafter, when the word “operation check test” is used without any special description, it means the above-described operation check test.

  At the time of the operation check test, an operation screen 32A, a first history screen 34A, and a second history screen 36A are displayed on the display unit 30A (see FIG. 2). The operation screen 32A, the first history screen 34A, and the second history screen 36A are simultaneously displayed on the display unit 30A. The operation screen 32A, the first history screen 34A, and the second history screen 36A are screens that the output unit 210 of the server 200 described later displays on the display unit 30A. That is, the display content of the display unit 30A is controlled by the output unit 210 of the server 200 so as to simultaneously display the operation screen 32A, the first history screen 34A, and the second history screen 36A during the operation check test. On the display unit 30A, a first history screen 34A is displayed in a left area, an operation screen 32A is displayed in an upper right area, and a second history screen 36A is displayed in a lower right area (see FIG. 2). .

  The design of each of the screens 32A, 34A, and 36A, the characters displayed on each of the screens 32A, 34A, and 36A, and the arrangement of the screens 32A, 34A, and 36A, etc. It depends on the user's design. Therefore, the screens 32A, 34A, and 36A drawn in FIG. 2 are merely examples. FIG. 2 illustrates screens 32A, 34A, and 36A suitable for explanation, and the contents of the screens 32A, 34A, and 36A may not correspond to the contents of other screens.

  Hereinafter, each of the screens 32A, 34A, and 36A will be described with reference to FIG.

(A) Operation Screen FIG. 2 shows an operation screen 32A for registering new information in a database table named a customer master existing in a database 300 of the server 200 described later. The operation screen 32A is a screen actually used by a user of the completed program (a user of the created customer management application program) when the program is completed.

  The operation screen 32A is an example of an operation screen related to information of a database table. In the operation screen 32A, a customer number, a customer name, a telephone number, and a person in charge are input to a text box from a keyboard, which is an example of the input unit 20A, and a "Save" button is clicked with a mouse, which is an example of the input unit 20A. Operations can be performed. When such a predetermined operation is performed on the operation screen 32A, the operation screen 32A is set so that the information input to the text box of the operation screen 32A is newly registered in a database table named customer master. Have been created. On the operation screen 32A, the operation screen 32A is created such that, when the predetermined operation is performed once, one line of information is newly registered in the database table of the customer master as shown in FIG. .

  The operation screen created using the program creation support system 100 is not limited to the operation screen 32A. The operation screen created by using the program creation support system 100 is not limited to the operation screen 32A or in addition to the operation screen 32A. May be included in the screen used for deleting the file.

  For example, the operation screen for changing (updating) the content of the information in the database table includes a customer number used to specify the information to be updated, a text box used to input the updated content, and a text box in the database table. An "update" button or the like for updating information is displayed. For example, an operation screen for deleting information in a database table includes a text box used for inputting a customer number to specify information to be deleted and a "delete" for deleting information in a database table. "Button and the like are displayed. However, the configuration of the operation screen for changing (updating) the content of the information in the database table and deleting the information is not limited to the screen configuration illustrated here, and may be appropriately designed.

  When a predetermined operation is performed on the operation screen 32A using the input unit 20A during the operation check test, the content of the predetermined operation is received by the reception unit 220 of the server 200 via the network 50. As described later, the command generation unit 264 of the server 200 generates a command corresponding to the predetermined operation received by the reception unit 220. Then, the change unit 266 of the server 200 changes the information of the database table of the database 300 according to the command generated by the command generation unit 264. When a predetermined operation is performed on the operation screen 32A via the input unit 20A during the operation check test, the change history of the database table is displayed on the first history screen 34A and the second history screen 36A.

  Note that an error that occurs when the user performs an operation on the operation screen 32A during the operation check test and is not related to a change in the information in the DB tables 310 to 350 of the database 300 is displayed on the display unit 30A. Can be confirmed by looking at the area where the operation screen 32A is displayed. For example, if the program is designed so that a screen (for example, a confirmation screen) other than the operation screen 32A is displayed as a pop-up when the "Save" button is pressed on the operation screen 32A, the user may not display this screen. Can be confirmed on the display unit 30A.

(B) First History Screen The first history screen 34A is an example of a history screen showing a change history of the database table according to a predetermined operation on the operation screen 32A.

  On the first history screen 34A, a list of names of database tables (DB tables 310 to 350) of the database 300 of the server 200 is displayed. For example, the first history screen 34A of FIG. 2 indicates that the database 300 has database tables named “Orders”, “Order Details”, “Customer Master”, “Employee Master”, and “Product Master”. ing.

  Further, the message M1 is displayed on the first history screen 34A as a change history of the database table in association with the name of each database table (adjacent to the right of the name in FIG. 2). In the first history screen 34A of FIG. 2, it is assumed that the information has not been changed in the database tables named "Employee Master" and "Product Master" (these database tables have not been changed). Information is assumed to be referenced only). Therefore, the message M1 is not displayed next to the characters “employee master” and “product master”.

  Message M1 shows a summary of the most recently executed information change in the database table to which message M1 is attached. The message M1 includes, in the database table, the information indicating which of the information registration, the information content change (update), and the information deletion was performed most recently. Further, the message M1 includes information on the number of recently changed information in the content. For example, when a database table as shown in FIG. 3 exists, the message M1 includes in its contents information on how many lines of information have been registered, changed (updated) or deleted in this database table.

(C) Second History Screen The second history screen 36A is an example of a history screen showing a change history of the database table according to a predetermined operation on the operation screen 32A.

  The second history screen 36A also shows the reference history of the database table in addition to the change history of the database table. The reference history of the database table displayed on the second history screen 36A indicates a history in which the information of the database table is referred to by the processing unit 260 of the server 200 for some processing. Referring to the information in the database table does not change the information in the database table.

  On the second history screen 36A, for example, a change history of the database table according to a predetermined operation on the operation screen 32A and a reference history of the database table are displayed such that the latest history is displayed at the top of the list. They are displayed in list format in chronological order. That is, on the second history screen 36A, the change histories of the database tables are displayed in order of time, not for each database table. In the second history screen 36A, the change history of the database table and the reference history of the database table are not separately displayed, but the change history and the reference history are displayed in order of time. If the change history and the reference history are too large to display all of them at the same time on the display unit 30A, the screen is scrolled to display the second history screen 36A so that all the change history and the reference history can be referred to. It is configured.

  On the second history screen 36A, the change history of the database table is displayed using the message M2. In the message M2 indicating the change history, which database table information was changed, what kind of information change (registration, content change (update), deletion) was performed, and how many pieces of information were changed Is included in the content of the message. Further, on the second history screen 36A, the reference history of the database table is also displayed using the message M2. The message M2 indicating the reference history includes, in the content of the message, which database table information has been referenced and how many pieces of information have been referenced.

  Each of the change history and the reference history of the database table displayed on the second history screen 36A (each row of the history displayed in the list format on the second history screen 36A) is clicked with, for example, the mouse of the input unit 20A. It is configured to be able to be specified. Here, the input unit 20A is configured so that the change history and the reference history of the database table can be specified one line at a time. However, the present invention is not limited to this, and the input unit 20A may be configured such that a plurality of rows can be specified at one time for the change history and the reference history of the database table. A history specifying operation on the second history screen 36A displayed on the display unit 30A using the input unit 20A is received by the receiving unit 220 of the server 200 described later via the network 50. When the accepting unit 220 accepts the history specifying operation, the output unit 210 of the server 200, which will be described later, displays the details of the change of the information in the database table or the database for the history specified by the input unit 20A on the display unit 30A. The details of the reference content of the table information are displayed on the display unit 30A. The details of the changed contents of the information in the database table indicate what specific information of the database table information has been registered / changed / deleted. The details of the reference content of the information of the database table indicate what kind of specific information in the information of the database table is referred to.

  In the present embodiment, both the change history and the reference history of the database table are displayed on the second history screen 36A, but the present invention is not limited to this. For example, the second history screen 36A may display only the change history of the database table.

(2-2) Server The server 200 is a computer that provides a program creation support function to the user terminals 10A, 10B, and 10C that are clients.

  The server 200 has, for example, a CPU, a memory, an external storage device such as a hard disk, and a communication device (not shown). The server 200 has an input unit 230 such as a keyboard and a mouse, and a display unit 240 such as a display. The server 200 executes various processes for supporting program creation by causing the CPU to read a program for supporting program creation stored in the hard disk into a memory and execute the program.

  As described above, the server 200 mainly includes the output unit 210, the reception unit 220, the input unit 230, the display unit 240, the storage unit 250, the processing unit 260, and the database 300 (see FIG. 1). Hereinafter, the output unit 210, the reception unit 220, the storage unit 250, the processing unit 260, and the database 300 will be particularly described.

(2-2-1) Output Unit When the user uses the program creation support system 100 at the user terminals 10A, 10B, and 10C connected to the server 200 via the network 50, the output unit 210 Various screens are displayed on 30A, 30B, and 30C. That is, the output unit 210 is a display control unit that controls display contents of the display units 30A, 30B, and 30C of the user terminals 10A, 10B, and 10C connected to the server 200.

  When the above-described operation check test is performed on the user terminals 10A, 10B, and 10C, the output unit 210 operates the display units 30A, 30B, and 30C of the user terminals 10A, 10B, and 10C, respectively, for operations related to information in the database table. A screen (for example, the operation screen 32A in FIG. 2) and a history screen indicating a change history of the database table according to a predetermined operation on the operation screen are displayed simultaneously.

  When the operation confirmation test is performed simultaneously on the plurality of user terminals 10A, 10B, and 10C, the output unit 210 outputs the other display units 30A, 30B to the display units 30A, 30B, and 30C of the user terminals 10A, 10B, and 10C, respectively. , 30C independently of the operation screen. For example, the operation screen displayed on the display unit 30A is determined by the content of the operation check test executed on the user terminal 10A, and which operation screen is displayed on the other display units 30B and 30C. Is not affected. Similarly, for example, the operation screen displayed on the display unit 30B is determined by the content of the operation check test executed on the user terminal 10B, and the operation screen displayed on the other display units 30A and 30C is determined by which operation screen. It is not affected by whether there is.

  When the operation confirmation test is performed simultaneously on the plurality of user terminals 10A, 10B, and 10C, the output unit 210 outputs the information of the database table to each of the display units 30A, 30B, and 30C of the user terminals 10A, 10B, and 10C. At the same time, and a history screen showing a change history of the database table corresponding to a predetermined operation on the operation screen. That is, when the operation confirmation test is performed simultaneously on the plurality of user terminals 10A, 10B, and 10C, the output unit 210 displays the display units 30A, 30B, and 30C on the user terminals 10A, 10B, and 10C, respectively. A change history of the database table according to a predetermined operation on the operation screens displayed on 30B and 30C is displayed on the history screen. On the user terminal 10A, the change history of the database table corresponding to the predetermined operation on the operation screens displayed on the display units 30B and 30C of the other user terminals 10B and 10C is not displayed simultaneously with the operation screen. Therefore, in the program creation support system 100, even if the user of the user terminal 10A changes the information of the database table of the database 300 by performing some operation on the user terminals 10B and 10C, This prevents the user from erroneously recognizing that the operation has been performed as a result of the predetermined operation performed by the user.

  How the output unit 210 generates a history screen to be displayed on the display units 30A, 30B, and 30C of the user terminals 10A, 10B, and 10C will be described later in the description of the history screen generation unit 268.

  In the present embodiment, the output unit 210 displays, on the history screen displayed on each of the display units 30A, 30B, and 30C of the user terminals 10A, 10B, and 10C, information on the database table in addition to the change history of the database table. The reference history of the database table corresponding to the operation on the operation screen is also displayed (see FIG. 2). The reference history of the database table indicates a history of a reference to the database table by the processing unit 260 of the server 200 for a certain process as a result of an operation on the operation screen. The output unit 210 does not have to display the reference history of the database table on the history screen displayed on each of the display units 30A, 30B, and 30C.

  In the history screen (for example, the second history screen 36A) displayed on the display units 30A, 30B, and 30C of the user terminals 10A, 10B, and 10C, the receiving unit 220 displays one of the changes in the database table change history and the reference history. When a designation operation for designating a history is received, the output unit 210 operates as follows. The output unit 210 displays, on the display units 30A, 30B, and 30C displaying the history screen on which the designation operation has been performed, the change contents / reference contents of the information in the database table for one history designated by the designation operation. Display the details of

  A history screen, which will be described later, describes how the output unit 210 generates details of the changed contents / reference contents of the information of the database table to be displayed on the display units 30A, 30B, 30C of the user terminals 10A, 10B, 10C. This will be described in the description of the generation unit 268.

(2-2-2) Reception Unit The reception unit 220 is a database 300 displayed on the display units 30A, 30B, and 30C, which is performed by the user terminals 10A, 10B, and 10C using the input units 20A, 20B, and 20C, respectively. (Including a predetermined operation) on the operation screen relating to the information of the DB tables 310 to 350 of the above are received via the network 50. The predetermined operations on the operation screens displayed on the display units 30A, 30B, and 30C include operations for changing information in the DB tables 310 to 350 (information registration, information content change (update), and information deletion). Including. The operation on the operation screen displayed on the display units 30A, 30B, and 30C includes an operation for referring to information in the DB tables 310 to 350. It should be noted that which information of which DB table 310-350 is to be changed / referenced by the operation on the operation screen is defined by the created program.

  The reception unit 220 receives a predetermined operation on an operation screen displayed on each of the display units 30A, 30B, and 30C of the plurality of user terminals 10A, 10B, and 10C for each of the display units 30A, 30B, and 30C. In other words, the accepting unit 220 accepts the predetermined operation on the operation screen for each of the user terminals 10A, 10B, and 10C, that is, the user terminal 10A, 10B, and 10C to distinguish and accept the operation.

  Upon receiving a predetermined operation on the operation screen related to the information in the DB tables 310 to 350, the receiving unit 220 transmits information related to the predetermined operation to the command generation unit 264 of the processing unit 260 described later. The information on the predetermined operation includes information on the content of the predetermined operation (which information is changed in any of the DB tables 310 to 350 of the database 300). The information on the predetermined operation includes information that can specify which of the user terminals 10A, 10B, and 10C performed the predetermined operation.

  In addition, the reception unit 220 performs, via the network 50, a designation operation for designating one of the change histories and the reference histories of the DB tables 310 to 350 on the history screen displayed on the display units 30A, 30B, and 30C. Accept. The history screens displayed on the display units 30A, 30B, and 30C indicate the change history and the reference history of the DB tables 310 to 350 according to the operations on the operation screens displayed on the display units 30A, 30B, and 30C, respectively. Screen.

  When accepting a history designation operation on the history screen displayed on the display units 30A, 30B, and 30C, the reception unit 220 transmits information related to the designation operation to the history screen generation unit 268 of the processing unit 260 described later. The information on the designated operation includes information on the content of the designated operation (which history is designated). The information on the designation operation includes information that can specify which of the user terminals 10A, 10B, and 10C has performed the designation operation.

(2-2-3) Storage Unit The storage unit 250 stores a program for causing the CPU to execute a program creation support process.

  Further, the storage unit 250 stores various kinds of information and the like necessary for causing the program creation support system 100 to function. The storage unit 250 has, for example, a format storage area 252 as a storage area for storing information necessary for causing the program creation support system 100 to function. The format storage area 252 stores in advance a format of a history screen generated by a history screen generation unit 268 of the processing unit 260 described later, a format of a sentence used when the message generation unit 268a generates the messages M1 and M2, and the like. Have been.

(2-2-4) Processing Unit The processing unit 260 performs various processes for supporting program creation by causing the CPU to execute the program creation support process stored in the storage unit 250.

  In particular, here, among the processing executed by the processing unit 260, processing related to the operation check test will be described. The processing unit 260 mainly functions as the operation screen generation unit 262, the command generation unit 264, the change unit 266, and the history screen generation unit 268 regarding the operation check test.

(2-2-4-1) Operation Screen Generation Unit The operation screen generation unit 262 causes the output unit 210 to display on the display units 30A, 30B, and 30C of the user terminals 10A, 10B, and 10C during the operation check test. Then, an operation screen for the information of the database table is generated.

  The operation screen generation unit 262 reads out the layout of the operation screen created in the program creation work from the storage unit 250 and operates the operation screen for each of the user terminals 10A, 10B, and 10C to perform the operation check test. Generate. The operation screen generation unit 262 performs various operations (input of characters, etc.) on the operation screen displayed on the display units 30A, 30B, 30C from the input units 20A, 20B, 20C of the user terminals 10A, 10B, 10C. Is included), an operation screen reflecting this is generated. The operation screen generated for each of the user terminals 10A, 10B, and 10C by the operation screen generation unit 262 is output to the display units 30A, 30B, and 30C of the user terminals 10A, 10B, and 10C by the output unit 210.

(2-2-4-2) Command Generation Unit As described above, the reception unit 220 is one of the operation screens displayed on the display units 30A, 30B, 30C of the plurality of user terminals 10A, 10B, 10C. When a predetermined operation is received at step, information regarding the predetermined operation is transmitted to the command generation unit 264. The information on the predetermined operation includes information for specifying the user terminals 10A, 10B, and 10C on which the predetermined operation has been performed, and the content of the predetermined operation (for any one of the DB tables 310 to 350 of the database 300, Information is changed). For example, the information transmitted from the reception unit 220 to the command generation unit 264 is, in the user terminal 10A, the customer number “000000003”, the customer name “CCC”, the telephone number “ZZ-ZZZZ-ZZZZ”, This information can specify that an operation of newly registering the information of the person "FFF-like" in one of the database tables (a database table named customer master, for example, DB310) is performed.

  When receiving information on a predetermined operation from the reception unit 220, the command generation unit 264 generates a command corresponding to the predetermined operation. For example, the command generation unit 264 newly registers information such as a customer number “0000003”, a customer name “CCC”, a telephone number “ZZ-ZZZZ-ZZZZ”, and a person in charge “FFF” in the DB table 310. If information on the predetermined operation is received, a command is generated for the DB table 310 to cause the later-described changing unit 266 to execute such processing.

  The command generated by the command generation unit 264 includes information registration in any one of the DB tables 310-350, change (update) of the content of any information in the DB tables 310-350, and information from the DB tables 310-350. Information deletion.

  Further, when receiving the information on the predetermined operation from the reception unit 220, the command generation unit 264 receives the information for specifying the user terminals 10A, 10B, and 10C on which the predetermined operation has been performed, and the command created as described above. , To the history screen generation unit 268.

(2-2-4-3) Changing Unit The changing unit 266 changes the information in the DB tables 310-350 instructed to be changed according to the command transmitted from the command generating unit 264. As described above, the command is generated by the command generation unit 264 according to a predetermined operation on the operation screen displayed on the display units 30A, 30B, 30C of any of the user terminals 10A, 10B, 10C. In other words, the change unit 266 stores the information in the DB tables 310-350 instructed to be changed according to a predetermined operation on the operation screen displayed on the display units 30A, 30B, 30C of any of the user terminals 10A, 10B, 10C. To change.

(2-2-4-4) History Screen Generating Unit The history screen generating unit 268 causes the output unit 210 to display on the display units 30A, 30B, and 30C of the user terminals 10A, 10B, and 10C during the operation check test. Generate history screen. The history screen is a screen showing a change history of the database table according to a predetermined operation on the operation screen displayed on the display units 30A, 30B, 30C of the user terminals 10A, 10B, 10C.

  Here, a case where the history screen generation unit 268 generates a history screen to be displayed on the display unit 30A of the user terminal 10A will be described as an example. Here, it is assumed that the history screen generation unit 268 generates the first history screen 34A and the second history screen 36A as shown in FIG.

  Note that generation of a history screen to be displayed on the display unit 30B of the user terminal 10B by the history screen generation unit 268 and generation of a history screen to be displayed on the display unit 30C of the user terminal 10C are performed by the user terminal 10A. This is the same as the generation of the history screen to be displayed on the display unit 30A, and thus the description is omitted.

  The history screen generation unit 268 generates a history screen for the display unit 30A of the user terminal 10A based on the format stored in the format storage area 252 stored in the storage unit 250.

  For example, specifically, the history screen generation unit 268 displays the first history screen in which the names of the database tables attached to the DB tables 310 to 350 are arranged and displayed based on the format stored in the format storage area 252. Generate 34A. The history screen generation unit 268 also displays a table frame line for displaying a history of change and reference of information in the DB tables 310 to 350 based on the format stored in the format storage area 252, A second history screen 36A that displays item names (characters such as No., event, and details) is generated.

  Further, the history screen generation unit 268 generates a message M1 and a message M2 to be displayed on the first history screen 34A and the second history screen 36A as the change history of the DB tables 310-350. The message M1 and the message M2 are generated by the message generation unit 268a, which is a functional unit of the history screen generation unit 268. The history screen generation unit 268 generates the first history screen 34A so that the created message M1 is displayed at a position corresponding to the name of the changed database table. Further, the history screen generation unit 268 generates the second history screen 36A such that the created message M2 is displayed in the first row of the table in the second history screen 36A.

  When the operation check test is performed on the user terminal 10A, the output unit 210 operates the first history screen 34A and the second history screen 36A (including the message M1 and the message M2) generated by the history screen generation unit 268. At the same time as the operation screen generated by the screen generator 262, the display is displayed on the display 30A of the user terminal 10A.

  In addition, when the receiving unit 220 receives the above-described designation operation, the history screen generating unit 268 displays the details of the change or reference of the information in the DB tables 310 to 350 to be displayed on the display unit 30A of the user terminal 10A. Generate the screen to be displayed. The screen that displays the details of the change or reference of the information in the DB tables 310 to 350 is generated by the detail display generation unit 268b, which is a functional unit of the history screen generation unit 268.

  When the operation confirmation test is performed on the user terminal 10A and the receiving unit 220 receives the designation operation, the output unit 210 changes the content of the information in the DB tables 310 to 350 generated by the detailed display generation unit 268b or the content of the reference content. A screen for displaying details is displayed on the display unit 30A of the user terminal 10A.

(A) Message Generating Unit The message generating unit 268a includes information for specifying, by the history screen generating unit 268, the user terminal 10A transmitted from the command generating unit 264 and performing the predetermined operation, and a command generating unit 264. Receives the command created to cause the change unit 266 to change the information in the database table, and generates a message M1 and a message M2. The message generation unit 268a generates a message M1 and a message M2 corresponding to a command corresponding to a predetermined operation performed on the operation screen 32A displayed on the input unit 20A of the user terminal 10A.

  The message generation unit 268a generates the message M1 and the message M2 based on the text format stored in the format storage area 252 of the storage unit 250 and the content of the command received by the history screen generation unit 268.

  The message M1 and the message M2 generated by the message generation unit 268a are summaries of the contents of the command generated by the command generation unit 264.

  For example, the command created by the command generation unit 264 and transmitted to the change unit 266 includes information such as a customer number “0000003”, a customer name “CCC”, a telephone number “ZZ-ZZZZ-ZZZZ”, and a person in charge “FFF”. Is newly registered in a database table named customer master. In this case, the message M1 generated by the message generation unit 268a to be displayed on the first history screen 34A has, for example, the content “one line has been registered in the last operation”. Further, the message M2 generated by the message generation unit 268a to be displayed on the second history screen 36A has, for example, a content that "one row of data has been registered in the table" customer master "".

  The message M1 includes information indicating whether the change in the information in the DB tables 310-350 is any of registration of information in the DB tables 310-350, change of information contents, and deletion of information. The message M1 includes the number of information changed in the DB tables 310 to 350 (here, the number of lines).

  The message M2 includes a content that indicates whether the change in the information in the DB tables 310-350 is any of registration of information in the DB tables 310-350, change of information contents, deletion of information, and reference to information. Including. Further, the message M2 includes the number (here, the number of lines) of information changed or referred to in the DB tables 310 to 350.

(B) Detailed display generating unit The detailed display generating unit 268b displays the second history screen 36A displayed on the display unit 30A of the user terminal 10A by the receiving unit 220 when the operation check test is being performed on the user terminal 10A. When a designating operation for designating one history in the change history of the DB tables 310-350 is received, a screen for displaying the details of the change and reference contents of the information of the DB tables 310-350 is generated.

  As described above, the message generation unit 268a generates a summary of the content of the command generated by the command generation unit 264, whereas the detailed display generation unit 268b generates the details of the content of the command generated by the command generation unit 264. I do.

  For example, the command created by the command generation unit 264 and transmitted to the change unit 266 includes information such as a customer number “0000003”, a customer name “CCC”, a telephone number “ZZ-ZZZZ-ZZZZ”, and a person in charge “FFF”. Is newly registered in a database table named customer master.

  Then, it is assumed that the message M2 displayed on the second history screen 36A in response to this command has a content of "one line of data has been registered in the table" customer master "".

  In this case, when this history on the second history screen 36A is specified, the detailed display generation unit 268b outputs the entire contents of the command (that is, the customer number "0000003", the customer name "CCC", and the telephone number " (ZZ-ZZZZ-ZZZZ) and a screen in which the user can understand the information of the person in charge "FFF" in a database table named customer master). The screen generated by the detailed display generation unit 268b may be in a text format or a table format. Note that the screen generated by the detailed display generation unit 268b is not limited to the example illustrated here. For example, the screen generated by the detailed display generation unit 268b is not as simple as the message M2, but may be such that the entire contents of the command are not presented. Taking the same case as the above as an example, the screen generated by the detailed display generation unit 268b may include, for example, information including the contents of the customer number “0000003” and the customer name “limited company” CCC in a database named customer master. A screen may be generated so that the user can understand the content of new registration in the table.

(2-2-4-5) Database The database 300 is stored in, for example, a hard disk and managed by the processing unit 260.

  The database 300 includes DB tables 310, 320, 330, 340, and 350 defined when a program is created using the program creation support system 100. In FIG. 2, the database 300 includes five DB tables 310 to 350, but the number of DB tables is not limited to the illustrated number. The DB table may be appropriately determined according to the program to be created. The number of DB tables may be less than 5, or may be 6 or more.

  The contents of the DB tables 310 to 350 included in the database 300 can be confirmed using a database access tool.

(3) Process flow in the program creation support system at the time of a program test When a predetermined operation is performed on the operation screen, the program creation support system at the time of testing a program that performs a process of changing a database table associated with the operation screen The flow of the processing in 100 will be described below. Here, in particular, a flow of processing in the program creation support system 100 when a predetermined operation is performed on the operation screen to perform a program operation confirmation test will be described with reference to the flowchart in FIG.

  Here, the processing in the program creation support system 100 will be described as an example in which the user performs a predetermined operation on the operation screen 32A displayed on the display unit 30A using the user terminal 10A to confirm the operation of the program. Will be described. Here, the flow of processing in the program creation support system 100 will be described by taking as an example a case where, when a predetermined operation is performed on the operation screen 32A, information in a database table (see FIG. 3) named history master of the database 300 is changed. explain. Here, it is assumed that the DB table 310 corresponds to a database table named “history master”. Depending on the program, when a predetermined operation is performed on the operation screen 32A, a process of transitioning to a different operation screen may be performed. Here, it is assumed that there is no transition from the operation screen 32A to another operation screen. I do.

  First, the user performs some input via the input unit 20A of the user terminal 10A, and notifies the program creation support system 100 that the operation of the program is to be checked when a predetermined operation is performed on the operation screen 32A. For example, the user clicks a button (not shown) for shifting the program creation support system 100 to the test mode, which is displayed on the display unit 30A, using a mouse, which is an example of the input unit 20A. As a result, a test (program operation check test) is started.

  In step S1, in response to the start of the operation check test, the output unit 210 of the server 200 displays the operation screen 32A, the first history screen 34A, and the second history screen 36A on the display unit 30A of the user terminal 10A. (See FIG. 2).

  More specifically, in response to the start of the operation check test, operation screen generating section 262 of processing section 260 of server 200 generates operation screen 32A. Further, in response to the start of the operation check test, the history screen generation unit 268 of the processing unit 260 of the server 200 generates the first history screen 34A and the second history screen 36A. On the first history screen 34A and the second history screen 36A generated by the history screen generation unit 268, for example, a change history and a reference history of the information of the DB tables 310 to 350 performed so far are displayed (see FIG. 2). .

  The output unit 210 of the server 200 causes the display unit 30A of the user terminal 10A to display the generated operation screen 32A, the first history screen 34A, and the second history screen 36A.

  Although a description is omitted below, when a character is input to the text box on the operation screen 32A, the operation screen generating unit 262 generates a screen in which the character is input to the text box. Then, the output unit 210 causes the display unit 30A of the user terminal 10A to display the generated operation screen 32A. That is, the output unit 210 appropriately updates the operation screen 32A.

  Next, the user performs a predetermined operation on the operation screen 32A displayed on the display unit 30A of the user terminal 10A using the input unit 20A of the user terminal 10A. For example, specifically, the user inputs an operation customer number, a customer name, a telephone number, and a person in charge in a text box (see FIG. 2) displayed on the operation screen 32A from a keyboard which is an example of the input unit 20A. I do. Further, the user operates a mouse, which is an example of the input unit 20A, and clicks a “Save” button (see FIG. 2) displayed on the operation screen 32A.

  The receiving unit 220 of the server 200 receives the above-described predetermined operation on the operation screen 32A of the display unit 30A of the user terminal 10A, which is input from the input unit 20A of the user terminal 10A (Step S2). Then, the reception unit 220 of the server 200 transmits information on the predetermined operation to the command generation unit 264 of the processing unit 360 of the server 200. The information related to the predetermined operation includes information for specifying the user terminal on which the predetermined operation has been performed (here, information for specifying the user terminal 10A) and the content of the predetermined operation received by the receiving unit 220. Contains information.

  Next, in step S3, the command generation unit 264 generates a command corresponding to the predetermined operation on the operation screen 32A received by the reception unit 220, based on the information on the predetermined operation received from the reception unit 220. The command generation unit 264 transmits the generated comment to the change unit 266 of the processing unit 360 of the server 200. In addition, the command generation unit 264 includes information for specifying the user terminal that has performed the predetermined operation included in the information on the predetermined operation received from the reception unit 220 (here, information for specifying the user terminal 10A). ) And the generated command are transmitted to the history screen generation unit 268.

  If there is a bug in the program, the command generator 264 may generate a command not intended by the program creator. For example, it is assumed that the predetermined operation on the operation screen 32A is intended to additionally register new one-line data in the DB table 310. However, if there is a bug in the program, the command generation unit 264 generates a command for additionally registering new one-line data in the DB table 330 or deletes data from the DB table 310 against this intention. Perform abnormal operations such as generating commands. Here, the explanation is continued assuming that the program has no bug.

  Next, in step S4, the changing unit 266 changes the information of the DB table 310 to be changed according to the command generated by the command generating unit 264. For example, the changing unit 266 newly registers one row of data in the DB table 310 in response to the command.

  Next, in step S5, the message generation unit 268a of the history screen generation unit 268 generates a message M1 and a message M2 according to the command generated by the command generation unit 264. The message generation unit 268a performs the predetermined operation based on the information transmitted from the command generation unit 264 to the history screen generation unit 268 for specifying the user terminal on which the predetermined operation has been performed, and the generated command. Message M1 and message M2 to be displayed on the display unit of the user terminal. For example, the message generation unit 268a registers the message M1 having the content “one line was registered in the last operation” in response to the command by the command generation unit 264 and “one line data in the table“ customer master ”. And a message M2 having the content "I did".

  Next, in step S6, the history screen generation unit 268 displays the first history screen 34A and the second history screen 36A including the messages M1 and M2 generated by the message generation unit 268a on the user terminal that has performed the predetermined operation. It is generated for the display unit (here, for the display unit 30A of the user terminal 10A). Then, the output unit 210 of the server 200 outputs the history screen to be displayed on the display unit 30A of the user terminal 10A to the first history screen 34A and the second history screen 36A newly generated by the history screen generation unit 268 (that is, the message The first history screen 34A and the second history screen 36A) including the message M1 and the message M2 generated by the generation unit 268a are updated.

  In other words, in step S6, the output unit 210 of the server 200 displays the message M1 and the message generated by the message generation unit 268a on the first history screen 34A and the second history screen 36A displayed on the display unit 30A of the user terminal 10A. M2 is displayed as a change history of the DB table 310.

  The operation check test is executed according to the above flow. To further continue the operation check test using the operation screen 32A, steps S2 to S6 may be executed again.

  After the end of step S6, the accepting unit 220 specifies one history in the change history of the DB tables 310-350 on the second history screen 36A displayed on the display unit 30A of the user terminal 10A. When the designation operation is received, the following processing is performed.

  When one history in the change history is specified, the detail display generation unit 268b generates a screen that displays the details of the change in the information of the DB tables 310 to 350 for the specified one history. I do. The output unit 210 causes the display unit 30A of the user terminal 10A to display a screen that displays the details of the change in the information of the DB tables 310 to 350 generated by the detailed display generation unit 268b.

  The screen that displays the details of the information change may be displayed in a pop-up manner on the display unit 30A, for example, over the second history screen 36A, or may be displayed on the display unit 30A. Only a screen that displays the details of the information may be displayed.

(4) Features (4-1)
The program creation support system 100 according to the embodiment includes an output unit 210, a reception unit 220, and a change unit 266. The output unit 210 displays an operation screen related to the information in the DB tables 310 to 350 on a display unit that presents information to the user. The receiving unit 220 receives a predetermined operation on the operation screen displayed on the display unit. The change unit 266 changes information in the DB tables 310 to 350 according to a predetermined operation. The output unit 210 causes the display unit to display a history screen indicating the change history of the DB tables 310 to 350 according to the predetermined operation, simultaneously with the operation screen.

  For example, the output unit 210 causes the display unit 30A that presents information to the user to display the operation screen 32A related to the information in the DB table 310. The receiving unit 220 receives a predetermined operation on the operation screen 32A displayed on the display unit 30A. The change unit 266 changes information in the DB table 310 according to a predetermined operation. The output unit 210 causes the display unit 30A to display the first history screen 34A and the second history screen 36A simultaneously with the operation screen 32A as a history screen indicating a change history of the DB table 310 according to a predetermined operation.

  In the program creation support system 100 according to the embodiment, the operation screen 32A and the history screens (the first history screen 34A and the second history screen 36A) indicating the change history of the database are simultaneously displayed on the display unit 30A. Therefore, the user (test operator) of the program creation support system 100 that performs the test simultaneously confirms that the operation screen has been operated correctly and that the DB tables 310 to 350 have been correctly (as intended) changed. it can. Therefore, in the program creation support system 100, the test operation time can be reduced.

  In the program creation support system 100 according to the above-described embodiment, the history screens 34A and 36A displayed on the display unit 30A are not the DB table 310 itself, but the change history of the DB table 310 according to a predetermined operation on the operation screen 32A. Present. Therefore, the user can confirm in a short time whether the intended change of the DB table 310 matches the actual change of the DB table 310 for the predetermined operation. Further, here, the changed contents of the DB table 310 in accordance with a predetermined operation on the operation screen 32A displayed on the display unit 30A are displayed on the display unit 30A. Therefore, the user does not mistakenly change the DB table 310 resulting from the operation of another user as the change of the DB table 310 resulting from the user's own operation. From such a viewpoint as well, the program creation support system 100 according to the above embodiment can reduce the test operation time.

(4-2)
In the program creation support system 100 according to the embodiment, the output unit 210 causes each of the plurality of display units 30A, 30B, 30C to display an operation screen independently of the other display units 30A, 30B, 30C. The receiving unit 220 receives a predetermined operation on an operation screen displayed on each of the plurality of display units 30A, 30B, and 30C for each of the display units 30A, 30B, and 30C. The output unit 210 causes each of the display units 30A, 30B, and 30C to display, at the same time as the operation screen, a history screen indicating a change history of the DB tables 310 to 350 according to a predetermined operation on the operation screen.

  In the program creation support system 100 according to the embodiment, the plurality of display units 30A, 30B, and 30C each include an operation screen and a history screen indicating a change history of the DB tables 310 to 350 corresponding to a predetermined operation on the operation screen. Is displayed. Therefore, in the program creation support system 100, a plurality of users can execute the program test at the same time. Then, here, the change histories of the DB tables 310 to 350 generated as a result of each user performing a predetermined operation on the operation screen are displayed on the display units 30A, 30B, 30C viewed by the user. Preferably, only the change histories of DB tables 310 to 350 resulting from the user performing a predetermined operation on the operation screen are displayed on display units 30A, 30B, and 30C viewed by the user. Therefore, the user does not mistakenly change the DB tables 310-350 resulting from the operation of another user as a change of the DB tables 310-350 resulting from the user's own operation. Therefore, in the program creation support system 100, even when a plurality of users execute the program test at the same time, the test can be efficiently executed, and the test operation time can be reduced.

(4-3)
In the program creation support system 100 according to the embodiment, the changing unit 266 changes information in the DB tables 310 to 350 according to a command corresponding to a predetermined operation. The output unit 210 causes the display units 30A, 30B, and 30C to display a message corresponding to a command corresponding to the predetermined operation and a message on the history screen as a change history of the DB tables 310 to 350. The output unit 210 causes the display unit 30A to display, on the first history screen 34A and the second history screen 34B, a message M1 and a message M2 corresponding to a command corresponding to a predetermined operation as a change history of the DB table 310, for example.

  In the program creation support system 100 according to the above embodiment, a message corresponding to a command given to the change unit 266 for changing information in the DB tables 310 to 350 in response to a predetermined operation performed on the operation screen is displayed on the display unit. It is displayed on 30A, 30B, 30C. In other words, in the program creation support system 100, a message corresponding to a change command of information of the DB tables 310-350 is displayed on the display units 30A, 30B, and 30C instead of the contents of the changes of the DB tables 310-350. . Therefore, in the program creation support system 100, the user can easily confirm whether the predetermined operation on the operation screen correctly corresponds to the content of the command given to the change unit 266.

  Further, with such a configuration, even when a change occurs in the DB tables 310 to 350 due to an operation of another user who is simultaneously testing the program, each user can perform the DB operation by the user's own operation. It is possible to accurately grasp how the tables 310 to 350 have been changed.

(4-4)
In the program creation support system 100 according to the above-described embodiment, the commands provided to the change unit 266 include registration of information in the DB tables 310-350, change of information contents of the DB tables 310-350, and DB tables 310-350. Including the removal of information from.

  The command includes one or two of registering information in the DB tables 310-350, changing the information contents of the DB tables 310-350, and deleting information from the DB tables 310-350. There may be. However, the command preferably includes all of information registration, information content change, and information deletion.

  In the program creation support system 100 according to the embodiment, the user can easily make various changes made to the information in the DB tables 310 to 350 by using messages (for example, the message M1 and the message M2) displayed on the history screen. Can be confirmed.

(4-5)
In the program creation support system 100 according to the embodiment, the messages M1 and M2 are summaries of the contents of commands.

  In the program creation support system 100 according to the embodiment, the messages M1 and M2 summarizing the contents of the commands are displayed on the history screen as the change history of the DB tables 310 to 350. Therefore, the user of the system can easily grasp what changes have been made to the DB tables 310-350.

(4-6)
In the program creation support system 100 according to the above embodiment, the messages M1 and M2 include the number of pieces of information changed in the DB tables 310 to 350.

  In the program creation support system 100 according to the above-described embodiment, the user can grasp not only what kind of change has been made to the DB tables 310 to 350 but also how many pieces of information have been changed. Therefore, in the program creation support system 100, the user can quickly and correctly grasp whether the intended change has been made in the DB tables 310 to 350 by a predetermined operation on the operation screen.

(4-7)
In the program creation support system 100 according to the above-described embodiment, the reception unit 220 displays a change screen of the DB tables 310-350 on the history screen (for example, the second history screen 36A) displayed on the display units 30A, 30B, and 30C. A designation operation for designating at least one history is accepted. The output unit 210 causes the display units 30A, 30B, and 30C to display details of the change in the information of the DB tables 310 to 350 for the history specified by the specifying operation.

  In the program creation support system 100 according to the above-described embodiment, the user can quickly confirm the details of the change made to the information in the DB tables 310 to 350 for the predetermined operation as needed. As a result, the user can efficiently proceed with the test.

(5) Modification (5-1) Modification A
In the above embodiment, the server 200 also functions as a database server that manages the database 300. However, it is not limited to this.

  For example, the program creation support system 100 may have a database server that manages the database 300 separately from the server 200.

  Alternatively, the database 300 may be managed by a database server external to the program creation support system 100 connected to the server 200 constituting the program creation support system 100 via the network 50.

(5-2) Modification B
In the above embodiment, two history screens (the first history screen 34A and the second history screen 36A) are displayed on the display unit 30A of the user terminal 10A. However, it is not limited to this. For example, the same content as the first history screen 34A and the second history screen 36A may be displayed on one screen on the display unit 30A. Further, three or more screens may be displayed as a history screen on the display unit 30A.

  With the program creation support system according to the present invention, when a predetermined operation is performed on an operation screen, a program test can be efficiently performed when creating a program for performing a process of changing a database table associated with the operation screen. Useful.

30A, 30B, 30C Display section 32A Operation screen 34A First history screen (history screen)
36A 2nd history screen (history screen)
100 Program creation support system 210 Output unit 220 Reception unit 266 Change unit 310, 320, 330, 340, 350 DB table (database table)
M1, M2 message

JP-A-8-16429

Claims (7)

An output unit (210) for displaying an operation screen (32A) related to information of the database tables (310, 320, 330, 340, 350) on a display unit (30A, 30B, 30C) for presenting information to a user; ,
A receiving unit (220) for receiving a predetermined operation on the operation screen displayed on the display unit;
A changing unit (266) for changing information of the database table according to the predetermined operation;
With
The output unit causes the display unit to display, at the same time as the operation screen, a history screen (34A, 36A) indicating a change history of the database table according to the predetermined operation.
Program creation support system (100). The output unit causes each of the plurality of display units to display the operation screen independently of the other display units,
The receiving unit receives the predetermined operation on the operation screen displayed on each of the plurality of display units, for each of the display units,
The output unit, on each of the display units, simultaneously with the operation screen, to display the history screen showing the change history of the database table according to the predetermined operation in the operation screen,
The program creation support system according to claim 1. The changing unit changes information in the database table according to a command corresponding to the predetermined operation,
The output unit causes the display unit to display a message (M1, M2) corresponding to the command corresponding to the predetermined operation on the history screen as a change history of the database table.
The program creation support system according to claim 1. The command includes registering information in the database table, changing the content of the information in the database table, and deleting at least one of the information from the database table,
A program creation support system according to claim 3. The message is a summary of the content of the command;
The program creation support system according to claim 3. The message includes a count of information changed in the database table,
The program creation support system according to claim 3. The receiving unit, on the history screen displayed on the display unit, further receives a specifying operation of specifying at least one history in the change history of the database table,
The output unit, for the history specified by the specifying operation, the details of the change of the information of the database table, further display on the display unit,
The program creation support system according to claim 1.

Images