JP6303591B2 - Control program, control method, and control apparatus - Google Patents

Description

  The present invention relates to a control program and the like.

  When developing application software such as a Web (World Wide Web) system, an operation for confirming whether or not an output screen as a result of processing by the application software is in a specification state is performed in a test stage. For example, it is possible to record information on a screen to be confirmed by using a conventional technique for capturing a screen output by application software. In the following description, application software is simply referred to as an application.

JP 2011-76152 A

  However, the above-described conventional technique has a problem in that it is not possible to generate evidence that the application has been correctly tested and confirmed.

  When submitting documentation to the delivery destination, not only the appearance of the screen is as specified, but also that the processing executed by the user's operation input on the screen is correctly reflected in the database. It is desirable to show.

  For this reason, for example, it is conceivable to create the evidence material by storing the screen transition and the change history of the data in the database accompanying the screen transition in the actual transition / change order. However, a user manually inputs a SQL (Structured Query Language) sentence in order to obtain data as evidence data from the database, but the SQL sentence may be erroneously included. An SQL sentence with an incorrect content cannot be used as evidence material because desired data cannot be acquired from the database.

  In one aspect, an object of the present invention is to provide a control program, a control method, and a control device that can generate evidence that an application has been correctly tested and confirmed.

  In the first plan, the computer executes the following processing. A computer is caused to execute a process of referring to a storage unit that stores a keyword and a request command used for data acquisition from a database in association with each other. The computer is caused to execute a process of detecting that the first keyword stored in the storage unit is included in the first screen output to the display unit of the computer by the application software. The computer is caused to execute a process of reading the first request command stored in the storage unit in association with the first keyword. The computer causes the image data of the first screen to be recorded and the process of recording the data acquired by the first request command from the database.

  According to one embodiment of the present invention, there is an effect that it is possible to generate evidence material that an application has been correctly tested and confirmed.

FIG. 1 is a diagram illustrating a configuration of a system according to the present embodiment. FIG. 2 is a diagram illustrating an example of the data structure of the input support DB. FIG. 3 is a diagram illustrating the configuration of the terminal device according to the present embodiment. FIG. 4 is a diagram (1) illustrating an example of a data structure of evidence information. FIG. 5 is a diagram (2) illustrating an example of a data structure of evidence information. FIG. 6 is a diagram illustrating an example of an input screen displayed by the evidence information generation unit. FIG. 7 is a diagram illustrating an example of a display screen displayed by the detection unit. FIG. 8 is a diagram for explaining the processing of the setting unit. FIG. 9 is a flowchart illustrating the processing procedure of the terminal device according to the present embodiment. FIG. 10 is a flowchart showing a processing procedure of evidence acquisition processing. FIG. 11 is a flowchart illustrating a processing procedure of DB evidence proposal acquisition processing. FIG. 12 is a flowchart illustrating a processing procedure of DB evidence acquisition processing. FIG. 13 is a diagram illustrating an example of a computer that executes a control program.

  Embodiments of a control program, a control method, and a control device disclosed in the present application will be described below in detail with reference to the drawings. Note that the present invention is not limited to the embodiments.

  FIG. 1 is a diagram illustrating a configuration of a system according to the present embodiment. As shown in FIG. 1, this system includes a Web system 50, an input support server 60, and terminal devices 100a, 100b, and 100c. In the following description, the terminal devices 100a, 100b, and 100c are collectively referred to as the terminal device 100 as appropriate. The Web system 50, the input support server 60, and the terminal devices 100a to 100c are connected to each other via the network 70.

  The web system 50 includes a web server 51, a DBMS (DataBase Management System) 52, a public DB 53, and a DB 54.

  The web server 51 is a device that activates application software and responds to a request from the terminal device 100.

  The Web server 51 responds to a request from a browser operating on the terminal device 100 in cooperation with the DBMS 52. The Web server 51 provides content and image data described in HTML (Hyper Text Markup Language) to the terminal device 100 using HTTP (Hyper Text Transfer Protocol).

  The DBMS 52 manages the public DB 53 and DB 54. The DBMS 52 transmits data stored in the public DB 53 and the DB 54 in response to a data request from the Web server 51 or the terminal device 100. The DBMS 52 may store data disclosed to the terminal device 100 in the public DB 53 and store non-public data in the DB 54.

  The input support server 60 is a device having an input support DB 61. The input support DB 61 holds SQL sentence candidates that are input when the user of the terminal device 100 tests an application running on the Web system 50. The input support server 60 notifies the terminal device 100 of information in the input support DB 61 in response to a request from the terminal device 100.

  FIG. 2 is a diagram illustrating an example of the data structure of the input support DB. As shown in FIG. 2, the input support DB 61 associates related keywords, SQL sentences, and the number of applications. The related keyword corresponds to, for example, a keyword included in a screen displayed by the application. The SQL statement is a statement for making a data request to the DBMS 52. When the DBMS 52 receives the SQL statement, the DBMS 52 transmits the data specified in the SQL statement to the request source. The number of times of application is the number of times of application of the SQL sentence. Processing using the input support DB 61 will be described later.

  The terminal device 100 is a device that tests an application that operates on the Web system 50. The terminal device 100 starts a browser, accesses the Web server 51, acquires and records image data of a screen displayed on the browser and data generated based on an operation input on the screen.

  The terminal device 100 generates evidence information in which the recorded screen image data and the processing result data are arranged in the order of acquisition. This evidence information provides evidence that the app has been properly tested and verified.

  FIG. 3 is a diagram illustrating the configuration of the terminal device according to the present embodiment. As illustrated in FIG. 3, the terminal device 100 includes a communication unit 110, an input unit 120, a display unit 130, a storage unit 140, and a control unit 150.

  The communication unit 110 is a processing unit that performs data communication with the Web system 50 and the input support server 60 via the network 70. For example, the communication unit 110 corresponds to a communication card or a communication device. The control unit 150 described later exchanges data with the Web system 50 and the input support server 60 via the communication unit 110.

  The input unit 120 is an input device for inputting various types of information to the terminal device 100. For example, the input unit 120 corresponds to a keyboard, a mouse, a touch panel, and the like.

  The display unit 130 is a display device that displays information output from the control unit 150. For example, the display unit 130 corresponds to a liquid crystal display, a touch panel, or the like.

  The storage unit 140 stores evidence information 141. For example, the storage unit 140 corresponds to a semiconductor memory device such as a random access memory (RAM), a read only memory (ROM), and a flash memory, and a storage device such as a hard disk drive (HDD).

  The evidence information 141 sequentially holds image data of a screen output from an application to be tested and data that is a result of processing executed based on an input operation on the screen. In the following description, data that is a result of processing executed based on an input operation on the screen is appropriately described as generated data.

  4 and 5 are diagrams illustrating an example of the data structure of the evidence information. FIG. 4 includes screen image data 20a and 20b, generation data 21a, and an SQL sentence 22a. The SQL statement 22 a is a command statement for acquiring the generation data 21 a from the DBMS 52. FIG. 5 includes screen image data 20c and 20d, generation data 21b, and an SQL sentence 22b. The SQL statement 22b is a command statement for acquiring the generated data 21b from the DBMS 52.

  For example, the evidence information 141 holds information in the order of screen image data 20a, SQL statement 22a, generation data 21a, screen image data 20b, 20c, 20d, SQL statement 22b, and generation data 21b.

  The content proved from the evidence information 141 shown in FIGS. 4 and 5 is, for example, the data of the portion designated by the SQL sentence 22a at the time when the screen image data 20a is displayed on the browser, and the generated data 21a. It is that. Further, the data specified by the SQL sentence 22b after the screen image data 20b, 20c, 20d is displayed on the browser is generated data 21b.

  The evidence information 141 shown in FIGS. 4 and 5 is an example. For example, the image data 20b on the screen in FIG. 4 and the image data 20c on the screen in FIG. 5 may include image data on other screens, other generated data, and other SQL statements.

  Returning to the description of FIG. The control unit 150 includes a browser 151 and an evidence information generation unit 152. The control unit 150 corresponds to an integrated device such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). The control unit 150 corresponds to an electronic circuit such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit).

  The browser 151 accesses the Web server 51, downloads an HTML file, image data, audio data, and the like, analyzes the layout, generates a window screen, and causes the display unit 130 to display the window screen. In addition, the browser 151 displays an input form, a button, or the like on the window screen, receives an operation input from the user, and transmits the received information to the Web server 51.

  The evidence information generation unit 152 is a processing unit that generates evidence information 141. The evidence information generation unit 152 includes an event detection unit 152a, a detection unit 152b, a recording unit 152c, and a setting unit 152d.

  For example, the evidence information generation unit 152 causes the display unit 130 to display the input screen 30 illustrated in FIG. FIG. 6 is a diagram illustrating an example of an input screen displayed by the evidence information generation unit. For example, the input screen 30 includes input forms 31, 32, and 33, an output destination setting button 34, a browser activation button 35, and an SQL issue button 36.

  The input form 31 is a form for designating an output destination of the evidence information 141. For example, the user operates the input unit 120 to input an output destination in the input form 31 and presses the output destination setting button 34 to determine the output destination.

  The input form 32 is a form for inputting an SQL sentence. The input form 33 is a form for inputting related keywords.

  The browser activation button 35 is a button for instructing the operation of the browser 151. For example, when the user operates the input unit 120 and presses the browser activation button 35, the browser 151 is activated.

  The SQL issue button 36 is a button for instructing the DBMS 52 to issue information on the SQL sentence input to the input form 32. When the SQL issue button 36 is pressed, the evidence information generation unit 152 transmits information on the SQL sentence to the DBMS 52 and receives data corresponding to the information on the SQL sentence from the DBMS 52.

  The event detection unit 152a is a processing unit that detects an event in which a screen displayed by the browser 151 is switched. For example, the event detection unit 152a detects a screen change by using an event function provided in Windows (registered trademark) or the like. When the event detection unit 152a detects a screen change, the event detection unit 152a outputs information indicating that the screen is changed to the detection unit 152b and the recording unit 152c.

  The detecting unit 152b scans the screen image data and extracts keywords included in the screen image data. For example, the detection unit 152b scans HTML data for displaying image data on the screen and extracts keywords. The detection unit 152b scans the screen image data and extracts not only keywords included in the screen image data, but also searches text data other than tags, for example, HTML data for displaying the screen image data. Keywords may be extracted.

  The detection unit 152b accesses the input support DB 61 of the input support server 60, compares the extracted keyword and the related keyword of the input support DB 61, and determines whether or not the related keyword identical to the keyword is hit.

  When the detection unit 152b hits the same related keyword as the keyword, the detection unit 152b acquires the SQL sentence associated with the hit related keyword from the input support DB 61 and causes the display unit 130 to display the acquired SQL sentence. When a plurality of related keywords are hit, the detection unit 152b causes the display unit 130 to display a plurality of SQL sentences associated with the plurality of related keywords. When displaying a plurality of SQL sentences, the detection unit 152b preferentially displays the SQL sentence having a large number of application times.

  FIG. 7 is a diagram illustrating an example of a display screen displayed by the detection unit. The display screen 40 includes radio buttons 41 a to 41 e and a setting button 41. In the example illustrated in FIG. 7, it is assumed that the detection unit 152b acquires the SQL sentence “select * from C” and the SQL sentence “select * from C2” from the input support DB 61. Further, it is assumed that the SQL statement “select * from C” is applied more frequently than the SQL statement “select * from C2” is applied. The user operates the input unit 120 to select one of the radio buttons 41 a to 41 e and presses the setting button 41 to confirm the process.

  When the radio button 41a is selected, the detection unit 152b automatically inputs the SQL sentence “select * from C” on the input form 32 of the input screen 30 illustrated in FIG. When the SQL issue button 36 is pressed, the detection unit 152b outputs an SQL sentence “select * from C” to the DBMS 52. The detection unit 152b outputs the SQL sentence information and the response of the DBMS 52 to the SQL sentence information to the recording unit 152c.

  The detecting unit 152b accesses the input support DB 61 of the input support server 60, and adds 1 to the number of times of application corresponding to the set of the related keyword and the SQL sentence “select * from C”.

  When the radio button 41b is selected, the detection unit 152b automatically inputs the SQL sentence “select * from C2” on the input form 32 of the input screen 30 illustrated in FIG. When the SQL issue button 36 is pressed, the detection unit 152b outputs an SQL sentence “select * from C2” to the DBMS 52. The detection unit 152b outputs the SQL sentence information and the response of the DBMS 52 to the SQL sentence information to the recording unit 152c.

  The detecting unit 152b accesses the input support DB 61 of the input support server 60, and adds 1 to the number of times of application corresponding to the set of the related keyword and the SQL statement “select * from C2”.

  When the radio button 41c is selected, the detection unit 152b does not support input of an SQL sentence. In this case, the user may operate the input unit 120 so that the user himself / herself inputs an SQL sentence in the input form 32 and presses the SQL issue button 36. The detection unit 152b outputs the SQL sentence information and the response of the DBMS 52 to the SQL sentence information to the recording unit 152c.

  When the radio button 41d is selected, the detection unit 152b automatically inputs the SQL sentence “select * from C” on the input form 32 of the input screen 30 shown in FIG. Accept. For example, the user operates the input unit 120 to edit the SQL sentence input to the input form 32 and then presses the SQL issue button 36. When the SQL issue button 36 is pressed, the detection unit 152b outputs the edited SQL sentence to the DBMS 52. The detection unit 152b outputs the SQL sentence information and the response of the DBMS 52 to the SQL sentence information to the recording unit 152c.

  In addition, the detection unit 152b newly registers in the input support DB 61 a record in which the edited SQL sentence input in the input form and the related keyword are combined. The detection unit 152b sets the application count corresponding to the newly registered record to 1.

  When the radio button 41e is selected, the detection unit 152b automatically inputs the SQL sentence “select * from C2” on the input form 32 of the input screen 30 shown in FIG. Accept. For example, the user operates the input unit 120 to edit the SQL sentence input to the input form 32 and then presses the SQL issue button 36. When the SQL issue button 36 is pressed, the detection unit 152b outputs the edited SQL sentence to the DBMS 52. The detection unit 152b outputs the SQL sentence information and the response of the DBMS 52 to the SQL sentence information to the recording unit 152c.

  In addition, the detection unit 152b newly registers in the input support DB 61 a record in which the edited SQL sentence input in the input form and the related keyword are combined. The detection unit 152b sets the application count corresponding to the newly registered record to 1.

  The recording unit 152c captures the image data of the screen displayed by the browser 151 at the timing when the information indicating that the screen has been switched is acquired from the event detection unit 152a, and records it in the evidence information 141. In addition, the recording unit 152c acquires the SQL sentence information and the response from the DBMS 52 for the SQL sentence from the detection unit 152b and the setting unit 152d, and records the response in the evidence information 141. The response from the DBMS 52 corresponds to the generated data. The recording unit 152c records the screen image data, the SQL sentence, and the generated data in the evidence information 141 in chronological order.

  The setting unit 152d is a processing unit that registers a record in the input support DB 61 of the input support server 60. For example, the setting unit 152d operates when a user who is skilled in inputting an SQL sentence registers information in the input support DB 61 in advance. Similarly to the detection unit 152b, the setting unit 152d outputs the SQL sentence to the DBMS 52, and acquires a response to the SQL sentence from the DBMS 52. The setting unit 152d outputs the SQL sentence and the response from the DBMS 52 to the recording unit 152c.

  The setting unit 152d displays the input screen 30 illustrated in FIG. 6 on the display unit 130, and receives input of an SQL sentence and a related keyword. The user operates the input unit 120 to input an SQL sentence in the input form 32 and input a related keyword in the input form 33. The user may refer to the screen displayed on the browser 151, select one of the keywords displayed on the referred screen, and input it as a related keyword.

  The setting unit 152d accesses the input support DB 61, and when a set of the input SQL sentence and the related keyword is already registered in the input support DB 61, the setting unit 152d adds 1 to the application count of the corresponding record. On the other hand, when the set of the input SQL sentence and the related keyword is not already registered in the input support DB 61, the setting unit 152d sets the set of the input SQL sentence and the related keyword as follows: A new registration is made in the input support DB 61 and the application count is set to 1. If either the SQL sentence or the related keyword is different, the setting unit 152d newly registers a set of the input SQL sentence and the related keyword in the input support DB 61.

  FIG. 8 is a diagram for explaining the processing of the setting unit. For example, the input support DB 61 is indicated by 61a. The input SQL sentence is “select * from C2”, and the related keyword is “balance inquiry, history inquiry”. The setting unit 152d compares the combination of the SQL sentence “select * from C2” and the related keyword “balance inquiry, history inquiry” with the input support DB 61a. Then, the SQL statement “select * from C2” and the related keyword “balance inquiry, history inquiry” set do not exist in the input support DB 61a. For this reason, the setting unit 152d registers a set of the SQL sentence “select * from C2” and the related keyword “balance inquiry, history inquiry” and the record of the application count “1” in the input support DB 61a, as shown in 61b. To do.

  Subsequently, it is assumed that the setting unit 152 receives an SQL sentence “select * from E” and a related keyword “transfer, other line”. The setting unit 152 compares the SQL statement “select * from E” and the related keyword “transfer, other line” with the input support DB 61b, and the SQL statement “select * from E” and the related keyword “transfer, other line”. There is no pair. For this reason, the setting unit 152d registers the set of the SQL sentence “select * from E” and the related keyword “transfer, other line” and the record of the number of application “1” in the input support DB 61b, and shows it in 61c. .

  Next, a processing procedure of the terminal device 100 according to the present embodiment will be described. FIG. 9 is a flowchart illustrating the processing procedure of the terminal device according to the present embodiment. As illustrated in FIG. 9, the evidence information generation unit 152 of the terminal device 100 receives designation of the evidence output destination file (step S <b> 101) and activates the browser function (step S <b> 102).

  The evidence information generation unit 152 executes evidence acquisition processing (step S103). The evidence information generation unit 152 executes DB evidence acquisition processing (step S104).

  The procedure of the evidence acquisition process in FIG. 9 will be described. FIG. 10 is a flowchart showing a processing procedure of evidence acquisition processing. As illustrated in FIG. 10, the evidence information generation unit 152 detects a browser event (step S201).

  The evidence information generation unit 152 determines whether a screen transition is detected (step S202). If the evidence information generating unit 152 has not detected a screen transition (No at Step S202), the evidence information generating unit 152 proceeds to Step S201 again.

  On the other hand, when the screen information is detected (Yes in step S202), the evidence information generation unit 152 acquires browser evidence (step S203). In step S <b> 203, the evidence information generation unit 152 captures the screen displayed by the browser 151 and appends the captured screen image data to the evidence information 141.

  The evidence information generation unit 152 executes a DB evidence proposal acquisition process (step S204), and proceeds to step S201.

  Next, the processing procedure of the DB evidence proposal acquisition process shown in step S204 of FIG. 10 will be described. FIG. 11 is a flowchart illustrating a processing procedure of DB evidence proposal acquisition processing.

  As illustrated in FIG. 11, the evidence information generation unit 152 reads a related keyword of each record in the input support DB 61 (step S <b> 301). The evidence information generation unit 152 searches the HTML data of the currently displayed screen with the related keyword of each read record (step S302).

  The evidence information generation unit 152 ends the DB evidence proposal acquisition process when there is no search hit (step S303, No).

  When the search hit is found (Yes in step S303), the evidence information generation unit 152 displays the SQL sentence of the record in which the related keyword is found as a search hit to the operator, and displays each process (step S304). For example, in step S304, the evidence information generation unit 152 displays the display screen 40 illustrated in FIG. 7 and selects any radio button.

  If “partially divert” is not selected (No in step S305), the evidence information generation unit 152 determines whether “apply as it is” is selected (step S306). “Apply as it is” means that the SQL sentence displayed on the display screen 40 is used as it is, and means that, for example, the radio button 41a or 41b shown in FIG. 7 is selected.

  If “apply as it is” is not selected (No in step S306), the evidence information generation unit 152 ends the DB evidence proposal acquisition process.

  On the other hand, when “apply as it is” is selected (Yes in step S306), the evidence information generation unit 152 adds 1 to the number of times of application of the record corresponding to the SQL sentence (step S307). The evidence information generation unit 152 transmits the SQL sentence to the DBMS 52 (step S308), and proceeds to step S312.

  By the way, in step S305, the evidence information generation unit 152 accepts the editing of the SQL sentence when “partially divert” is selected (step S305, Yes) (step S309).

  The evidence information generation unit 152 newly registers the combination of the edited SQL and the related keyword in the input support DB 61 (step S310). The evidence information generation unit 152 transmits the edited SQL sentence to the DBMS 52 (step S311).

  The evidence information generation unit 152 receives data from the DBMS 52 (step S312), and adds an SQL sentence to the evidence output destination file (step S313). The evidence information generation unit 152 adds the received data to the evidence output destination file (step S314), and ends the DB evidence proposal acquisition process.

  Next, the procedure of the DB evidence acquisition process shown in step S104 of FIG. 9 will be described. FIG. 12 is a flowchart illustrating a processing procedure of DB evidence acquisition processing.

  As shown in FIG. 12, the evidence information generation unit 152 receives an input of an SQL sentence from the operator (step S401), and receives an input of a related keyword from the operator (step S402). If the SQL issue button 36 is not pressed (No at Step S403), the evidence information generation unit 152 proceeds to Step S401 again.

  When the SQL issue button is pressed (step S403, Yes), the evidence information generation unit 152 determines whether there is an input of a related keyword (step S404). If there is no input of a related keyword (No at Step S404), the evidence information generation unit 152 transmits an SQL sentence to the DBMS 52 (Step S405).

  The evidence information generation unit 152 receives data from the DBMS 52 (step S406), and adds an SQL sentence to the evidence output destination file (step S407). The evidence information generation unit 152 adds the received data to the evidence output destination file (step S408), and proceeds to step S401. In step S408, for example, the evidence information generation unit 152 adds the data received from the DBMS 52 as CSV (Comma-Separated Values) data.

  By the way, in step S404, when there is an input of a related keyword (step S404, Yes), the evidence information generation unit 152 searches the input support DB 61 based on the related keyword (step S409). If there is no search hit (No in step S410), the evidence information generation unit 152 proceeds to step S414.

  On the other hand, when there is a search hit (Yes in step S410), the evidence information generation unit 152 compares the input SQL sentence with the SQL sentence of the record hit in the search (step S411).

  The evidence information generation unit 152 proceeds to step S414 if the input SQL sentence does not match the SQL sentence of the search hit record (step S412, No). On the other hand, when the input SQL sentence matches the SQL sentence of the record hit by the search (step S412, Yes), the evidence information generation unit 152 adds 1 to the number of times the record hit the search hit ( Step S413) and the process proceeds to Step S405.

  In step S410, when there is no search hit (No in step S410), the evidence information generation unit 152 newly registers a combination of the input SQL sentence and the related keyword in the input support DB (step S414).

  Next, effects of the terminal device 100 according to the present embodiment will be described. When the terminal device 100 tests an application, the terminal device 100 reads an SQL sentence associated with a keyword included in the image data of the screen from the input support DB 61. Then, the terminal device 100 adds screen image data to the evidence information 141, and adds data obtained by transmitting the SQL sentence read from the input support DB 61 to the DBMS 52 to the evidence information 141. Thereby, since the user does not need to input the SQL sentence manually, it is possible to prevent erroneous input of the SQL sentence, and to generate the evidence data for testing the application. Further, by using the terminal device 100 according to the present embodiment, even a user who does not have expertise in SQL text can create evidence materials.

  Further, according to the terminal device 100, the display screen 40 including the SQL sentence read from the input support DB is output, and when the correction is accepted, the SQL sentence is corrected, and the corrected SQL sentence is transmitted to the DBMS 52. . For this reason, it is possible to generate optimal evidence material in correspondence with the case where the SQL sentence is different from the intention of the user.

  In addition, according to the terminal device 100, a plurality of screens are output as the application process is executed, and the image data of the screen and the data acquired by the SQL statement corresponding to the screen are arranged in the order according to the execution of the process. Recorded in the evidence information 141. For this reason, it is possible to generate evidence that appropriately proves whether or not the application has been correctly tested and confirmed.

  Next, an example of a computer that executes a control program that realizes the same function as the terminal device 100 described in the above embodiment will be described. FIG. 13 is a diagram illustrating an example of a computer that executes a control program.

  As illustrated in FIG. 13, the computer 200 includes a CPU 201 that executes various arithmetic processes, an input device 202 that receives input of data from a user, and a display 203. The computer 200 includes a reading device 204 that reads a program and the like from a storage medium, and an interface device 205 that exchanges data with other computers via a network. The computer 200 also includes a RAM 206 that temporarily stores various information and a hard disk device 207. The devices 201 to 207 are connected to the bus 208.

  The hard disk device 207 has a detection program 207a and a recording program 207b. The CPU 201 reads out each program 207a, 207b and develops it in the RAM 206.

  The detection program 207a functions as a detection process 206a. The recording program 207b functions as the recording process 206b.

  For example, the detection process 206a corresponds to the detection unit 152b. The recording process 206b corresponds to the recording unit 152c.

  Note that the programs 207a and 207b are not necessarily stored in the hard disk device 207 from the beginning. For example, each program is stored in a “portable physical medium” such as a flexible disk (FD), a CD-ROM, a DVD disk, a magneto-optical disk, and an IC card inserted into the computer 200. Then, the computer 200 may read and execute the programs 207a and 207b from these.

  In the above embodiment, the detection unit 152b displays the display screen 40 and then transmits an SQL sentence to the DBMS 52 in response to a user input operation. However, the present invention is not limited to this. When the detection unit 152b hits the same related keyword as the keyword, the detection unit 152b acquires the SQL sentence associated with the hit related keyword from the input support DB 61, and transmits the acquired SQL sentence as it is to the DBMS 52. Also good.

  Moreover, in the said Example, although the input support server 60 had input support DB61, it is not limited to this. For example, any of the terminal devices 100 may have the same function as the input support server 60, and the terminal device 100 may include the input support DB 61. For example, the terminal device 100a may hold the input support DB 61, and the terminal device 100b may access the input support DB 61 of the terminal device 100a and read an SQL sentence. Alternatively, the terminal device 100a may hold the input support device 61, and the terminal device 100a may access the input support DB 61 held by itself to read the SQL sentence.

  The following supplementary notes are further disclosed with respect to the embodiments including the above examples.

(Supplementary note 1)
Reference is made to a storage unit that stores a keyword and a request command used for data acquisition from a database in association with each other, and the first screen output to the computer display unit by application software is stored in the storage unit. If it detects that the first keyword is included,
Read the first request command stored in the storage unit in association with the first keyword,
A control program for recording the image data of the first screen and recording the data acquired by the first request command from the database.

(Additional remark 2) The process which reads said 1st request command outputs the 2nd screen containing said 1st request command, and when correction is received, it corrects said 1st request command The control program according to appendix 1, which is characterized.

(Supplementary Note 3) The application software outputs a plurality of screens as the process is executed, and the recording process includes screen data and data acquired by a first request instruction corresponding to the screen. 3. The control program according to appendix 1 or 2, which is recorded in the order according to execution.

(Appendix 4) A control method executed by a computer,
Reference is made to a storage unit that stores a keyword and a request command used for data acquisition from a database in association with each other, and the first screen output to the computer display unit by application software is stored in the storage unit. If it detects that the first keyword is included,
Read the first request command stored in the storage unit in association with the first keyword,
A control method, comprising: storing image data of the first screen and recording data acquired by the first request command from the database.

(Additional remark 5) The process which reads said 1st request command outputs the 2nd screen containing said 1st request command, and when correction is received, it corrects said 1st request command The control method according to appendix 4, which is characterized.

(Supplementary note 6) The application software outputs a plurality of screens as the process is executed, and the recording process includes the screen data and the data acquired by the first request instruction corresponding to the screen. 6. The control method according to appendix 4 or 5, wherein recording is performed in the order according to execution.

(Additional remark 7) The memory | storage part which refers to the memory | storage part which matches and memorize | stores a keyword and the request command used for the data acquisition from a database, and is output to the display part of a computer by application software on said memory | storage part Is stored in the storage unit in association with the first keyword when it is detected that the first keyword is included. A detection unit for reading out the first request command being performed;
And a recording unit that records image data of the first image and records data obtained by the first request command from the database.

(Supplementary note 8) The supplementary note 7 is characterized in that the detection unit outputs a second screen including the first request command and corrects the first request command when correction is accepted. The control device described.

(Supplementary note 9) The application software outputs a plurality of screens as the process is executed, and the recording unit executes the process using the screen data and the data acquired by the first request instruction corresponding to the screen. 9. The control device according to appendix 7 or 8, wherein recording is performed in the order according to the above.

50 Web System 60 Input Support Server 70 Network 100a, 100b, 100c Terminal Device

Claims (5)

On the computer,
Reference is made to a storage unit that stores a keyword and a request command used for data acquisition from a database in association with each other, and the first screen output to the computer display unit by application software is stored in the storage unit. If it detects that the first keyword is included,
Read the first request command stored in the storage unit in association with the first keyword,
A control program for recording the image data of the first screen and recording the data acquired by the first request command from the database.   The process of reading the first request command outputs a second screen including the first request command, and corrects the first request command when correction is accepted. Item 2. A control program according to item 1.   The application software outputs a plurality of screens along with the execution of the process, and the recording process follows the execution of the process with the screen data and the data acquired by the first request instruction corresponding to the screen. The control program according to claim 1, wherein the control program is recorded in order. A control method executed by a computer,
Reference is made to a storage unit that stores a keyword and a request command used for data acquisition from a database in association with each other, and the first screen output to the computer display unit by application software is stored in the storage unit. If it detects that the first keyword is included,
Read the first request command stored in the storage unit in association with the first keyword,
A control method, comprising: storing image data of the first screen and recording data acquired by the first request command from the database. Reference is made to a storage unit that stores a keyword and a request command used for data acquisition from a database in association with each other, and the first screen output to the computer display unit by application software is stored in the storage unit. A first keyword stored in the storage unit in association with the first keyword when it is detected that the first keyword is included. A detection unit for reading one request command;
And a recording unit that records image data of the first screen and records data acquired from the database according to the first request command.

Images