JP2007280357A - Program, device and method for generating screen - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a program, device and method for generating a screen which generate a screen displayed on a client. <P>SOLUTION: This screen generation program makes a computer execute an acquisition step of acquiring first data which are transmitted from a server to the client and for displaying a first screen for accepting an operation by a user to the client and second data which are transmitted from the client to the server and indicate an operation accepted by the first screen displayed to the client and a generation step of generating third data for displaying a second screen constituted by adding operation information based on the second data to the first screen based on the first data and the second data acquired by the acquisition step. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a screen generation program, a screen generation device, and a screen generation method for generating a screen displayed on a client.

  In a Web service provided by a client accessing a Web server, troubles caused by user operations at the client are solved by a call from the user to the call center.

As a related art related to the present invention, when an abnormality occurs in the Web server by the client holding the operation log, the client restores the processing up to the time when the abnormality occurred using the operation log, and the client There is a processing request recovery method in which a user using the process can seamlessly continue the subsequent processing (see, for example, Patent Document 1).
Japanese Patent Laid-Open No. 2003-6018

  However, as described above, when trouble occurs due to the operation on the client side, the information that can be acquired by the call center is the operation history, error log, customer information, etc. recorded on the Web server side. Can not grasp the correct operation and screen.

  The technique of Patent Document 1 is a technique in the case where a trouble occurs on the Web server side and is restored, and the trouble caused by the operation on the client side as described above cannot be solved. The technique of Patent Document 1 is a process performed only by the client in order to continue the client process before and after the trouble, and is a process unrelated to the Web server or the call center side.

  SUMMARY An advantage of some aspects of the invention is that it provides a screen generation program, a screen generation device, and a screen generation method for generating a screen displayed on a client.

  In order to solve the above-described problem, the present invention provides a screen generation program that causes a computer different from the client to generate a screen displayed on the client based on communication with the server, and is transmitted from the server to the client. First data that is displayed on the client, and is transmitted to the server from the first data that is displayed on the client. An acquisition step of acquiring second data that is data indicating an operation accepted on one screen, and an operation that is information based on the second data based on the first data and the second data acquired by the acquisition step Generate third data to display a second screen that is created by adding information to the first screen They are intended to execute a generating step that a computer.

  According to another aspect of the present invention, there is provided a screen generation device for generating a screen displayed on a client based on communication with a server, wherein the first data is data transmitted from the server to the client and accepts an operation by a user. First data that is data for displaying a screen on the client, and data that is transmitted from the client to the server and that indicates an operation accepted on the first screen displayed on the client. A second unit configured to add operation information, which is information based on the second data, to the first screen based on the first data and the second data acquired by the acquisition unit; And a generating unit that generates third data for displaying a screen.

Further, the present invention is a screen generation method for executing generation of a screen displayed on a client based on communication with a server by an information processing apparatus different from the client,
First data that is data transmitted from the server to the client and that causes the client to display a first screen that accepts a user operation; and data that is transmitted from the client to the server Based on the acquisition step of acquiring second data that is data indicating the operation accepted on the first screen displayed on the client, and based on the first data and the second data acquired by the acquisition step, the second data A generation step of generating third data for displaying a second screen obtained by adding operation information, which is information based on data, to the first screen is executed.

  According to the present invention, it is possible to generate a screen displayed on the client including the input contents in the client.

  Embodiments of the present invention will be described below with reference to the drawings.

Embodiment 1 FIG.
In this embodiment, a screen reproduction device that reproduces a screen on a client accessing a Web server will be described as an example of a screen generation device.

  First, the configuration of the Web system according to the present embodiment will be described.

  FIG. 1 is a block diagram illustrating an example of a configuration of a Web system according to the present embodiment. This Web system includes a client 1, a Web server 2, a network switch 3, a screen reproduction device 4, an operation log storage unit 5, and an error log storage unit 6. The client 1 and the web server 2 are connected via a network switch 3. The screen reproduction device 4 is connected to the mirror port of the network switch 3. Further, the operation log storage unit 5 and the error log storage unit 6 are connected to the Web server 2 and the screen reproduction device 4.

  The client 1 accesses the Web server 2 according to the user's operation, displays the Web screen received from the Web server 2, and transmits the operation on the Web screen by the user to the Web server 2. Further, the Web server 2 saves an operation history in the client 1 as an operation log in the operation log storage unit 5, and saves an error history generated in communication with the client 1 in the error log storage unit 6 as an error log. In addition, the network switch 3 captures communication between the client 1 and the Web server 2 and transmits it to the screen reproduction device 4 from the mirror port.

  Next, the configuration of the screen reproduction device 4 will be described.

  FIG. 2 is a block diagram showing an example of the configuration of the screen reproduction device according to the present embodiment. The screen reproduction device 4 includes an HTTP (HyperText Transfer Protocol) message observation unit 111, an HTTP analysis unit 112, a communication data storage unit 113, a communication data extraction unit 121, a screen data generation unit 122, a screen component file storage unit 123, screen data. A storage unit 124, a screen additional information storage unit 132, a screen control unit 133, and a screen display unit 134 are provided.

  Next, the operation log in the operation log storage unit 5 and the error log in the error log storage unit 6 will be described.

  The operation log and the error log are generated by the Web server 2 in the same manner as before. FIG. 3 is a table showing an example of the operation log according to the present embodiment. The operation log has a record for each operation. The operation log has a request time stamp, a customer ID, a source IP address, and an operation as items for each record. FIG. 4 is a table showing an example of the error log according to the present embodiment. The error log has a record for each error. The error log has a request time stamp, customer ID, source IP address, operation, and error message as items for each record.

  Next, an HTTP message captured by the network switch 3 will be described.

  First, the data structure of a request (HTTP request message) transmitted from the client 1 to the Web server 2 will be described. FIG. 5 is a table showing an example of the data structure of the HTTP request message. As shown in the left column of the figure, the data structure of the request includes a message header, a blank line, and a message body. The message header includes a request line, a request header, a general header, and an entity header. Further, the two columns on the right side of the figure show a sample GET method and a sample POST method as specific examples of the contents of the request data structure.

  First, the data structure of a response (HTTP response message) transmitted from the Web server 2 to the client 1 will be described. FIG. 6 is a table showing an example of the data structure of the HTTP response message. As shown in the left column of the figure, the data structure of the response is composed of a message header, a blank line, and a message body as in the request. The message header includes a status line, a response header, a general header, and an entity header. Furthermore, two columns on the right side of the figure show a sample when an HTML (HyperText Markup Language) file is acquired and a sample when an image file is acquired as specific examples of the contents of the response data structure.

  FIG. 7 is a sequence diagram illustrating an example of an HTTP message. Requests and responses appear alternately in a series of HTTP messages. Also, a certain request and a response immediately after that are paired. In addition, a response input input by the client 1 for a form in a response becomes an argument of the request immediately after that. Therefore, a form in a response and a response input in a request immediately after that form a pair. The image reproduction device 4 associates HTTP messages using these pairs.

  Next, communication data acquisition processing by the HTTP message observation unit 111 and the HTTP analysis unit 112 will be described.

  FIG. 8 is a flowchart showing an example of the operation of the communication data acquisition process according to the present embodiment. Here, the identification ID given to the HTTP message is expressed in the format of “(parent number) − (child number)”. First, the HTTP message observation unit 111 initializes a parent number (parent number = 0) (S111), extracts an HTTP message from the message captured by the network switch 3, and sends it to the HTTP analysis unit 112 (S112). Next, the HTTP analysis unit 112 performs an HTTP protocol analysis process on the received HTTP message (S113), and stores the result as communication data in the communication data storage unit 113 (S114). Next, the HTTP message observation unit 111 determines whether or not the observation of all messages has been completed (S115), and if not completed (S115, N), returns to the process S112, and if completed. (S115, Y), this flow is terminated.

  Next, HTTP protocol analysis processing during communication data acquisition processing will be described.

  FIG. 9 is a flowchart showing an example of the operation of HTTP protocol analysis processing according to the present embodiment. First, the HTTP analysis unit 112 analyzes the HTTP message received from the HTTP message observation unit 111 (S122), and determines whether or not the given HTTP message is a new connection (new session, new screen) ( S123). If it is not a new connection (S123, N), the process proceeds to S125. On the other hand, if the connection is new (S123, Y), the HTTP analysis unit 112 adds 1 to the parent number and initializes the child number (sets the child number to 1) (S124). Next, the HTTP analysis unit 112 determines whether or not the given HTTP message is a request (S125). When it is not a request (S125, N), the process proceeds to S131. On the other hand, if it is a request (S125, Y), the HTTP analysis unit 112 adds 1 to the child number (S126).

  Next, the HTTP analysis unit 112 determines whether or not the given HTTP message is a response (S131). If it is not a response (S131, N), an identification ID consisting of a parent number and a child number is registered in the communication data storage unit 113 (S132), and this flow is terminated. On the other hand, if it is a response (S131, Y), the HTTP analysis unit 112 corresponds to all of the transmission source IP address and port number, the transmission destination IP address and the port number (just before making a request / response pair). The request identification ID is registered in the communication data storage unit 113 as the response identification ID (S133), and this flow ends.

  Next, the data structure of the communication data storage unit 113 will be described.

  FIG. 10 is a table showing an example of the contents of the communication data storage unit 113 according to the present embodiment. The communication data storage unit 113 stores, as communication data, a communication data file that is a message body of an HTTP message and a communication data table that manages the communication data file in a table format. The communication data table has a record for each HTTP message. In addition, the communication data table has a time stamp, source IP (Internet Protocol) address: connection port, destination IP address: connection port, identification ID, type, HTTP message header, and body as items for each record.

  The identification ID is given by the HTTP protocol analysis process described above. The parent number of the identification ID is the same within one screen connection, and the child number of the identification ID is the same for the request and response pair. The type indicates either a request or a response. The body is a file name of a communication data file that is a message body of the HTTP message. The communication data file includes an HTML form, an HTTP message argument (HTML form response input), image data, and the like.

  According to the communication data acquisition process described above, by analyzing an HTTP message between the client 1 and the Web server 2 and generating a communication data table, it becomes easy to associate with an error log, and between HTTP messages. It becomes easy to extract the relationship between a request / response pair and a form / response input pair.

  Next, communication data extraction processing by the communication data extraction unit 121 will be described.

  FIG. 11 is a flowchart showing an example of the operation of the communication data extraction process according to the present embodiment. First, the communication data extraction unit 121 specifies extraction conditions based on the error log storage unit 6 (S141), and reads an HTTP message from the communication data storage unit 113 (S142). Here, the extraction condition is, for example, an HTTP message corresponding to an error designated by the user of the screen reproduction device 4 from the error log, and an HTTP message related to the HTTP message (a predetermined range before and after the HTTP message). HTTP message included in the message). The HTTP message corresponding to the error is, for example, an HTTP message that matches the request time stamp and the source IP address in the error log.

  Although the extraction condition is specified based on the error log here, the extraction condition may be specified based on the operation log.

  Next, the communication data extraction unit 121 determines whether or not reading of all HTTP messages in the communication data storage unit 113 is completed (S143). If completed (S143, Y), the flow ends. If not completed (S143, N), it is determined whether or not the read HTTP message meets the extraction condition (S144). If the extraction conditions are not met (S144, N), the process returns to step S142 to read the next communication data. On the other hand, when the extraction condition is met (S144, Y), the communication data extraction unit 121 sends the read HTTP message to the screen data generation unit 122, and the screen data generation unit 122 performs screen data generation processing (S145), Returning to step S142, the next communication data is read.

  Next, screen data generation processing by the screen data generation unit 122 during communication data extraction processing will be described.

  FIG. 12 is a flowchart showing an example of the operation of the screen data generation process according to the present embodiment. First, the screen data generation unit 122 determines whether or not the HTTP message received from the communication data extraction unit 121 is a response (S151).

  If the response is a response in process S151 (S151, Y), the screen data generation unit 122 determines whether the response is HTML or an image (S152). If it is HTML (S152, HTML), the screen data generation unit 122 analyzes the HTML to extract an HTML form (S153), writes the HTML form as a screen component file in the screen component file storage unit 123 (S154), This flow is finished. When it is an image (S152, image), the screen data generation unit 122 writes the image file as an image component file in the screen component file storage unit 123 (S155), and ends this flow.

  If the response is not a response in processing S151 (S151, N), the screen data generation unit 122 determines whether the HTTP message received from the communication data extraction unit 121 is a request (S161).

  In the process S161, if the request is a request (S161, Y), the screen data generation unit 122 determines whether the request is GET or POST (S162). When the request is GET (S162, GET), an argument (response input) is read from the request header (S163), and the process proceeds to S165. On the other hand, when the request is POST (S162, POST), an argument (response input) is read from the message body (S164), and the process proceeds to S165.

  Next, the screen data generation unit 122 reads the HTML form from the corresponding screen part file storage unit 123 (extracted from the response immediately before the request) (S165), and embeds a response input in the HTML form. (S166), the resulting HTML form is registered in the screen data storage unit 124 as a screen data file (S167), and this flow ends.

  If the request is not a request in process S161 (S161, N), this flow ends.

  Next, the response input embedding process during the screen data generation process will be described.

  FIG. 13 is a flowchart showing an example of the operation of the response input embedding process according to the present embodiment. First, the screen data generation unit 122 reads one line from the HTML form from the screen part file storage unit 123 (S171), and determines whether there is a <form> tag in the corresponding line (S172).

  If there is no <form> tag (S172, N), the process proceeds to S181.

  On the other hand, when there is an <form> tag (S172, Y), the screen data generation unit 122 determines whether there is an <input> tag in the corresponding line (S173). If there is an <input> tag and the type is text (S173, text), the screen data generation unit 122 sets the value of the argument in the value attribute (S174), and the process proceeds to S181. In addition, when there is an <input> tag and the type thereof is a radio checkbox (S173, radio checkbox), the screen data generation unit 122 adds a description “checked =“ checked ”to a line having a value equal to the value of the argument. (S175), the process proceeds to S181. If there is an <input> tag and the type is select (S173, select), the screen data generation unit 122 adds a description of selected = “selected” to the option element equal to the argument value (S176). The process proceeds to process S181.

  If there is no <input> tag (S173, NO), the screen data generation unit 122 determines whether there is a <textarea> tag (S177). If there is no <textarea> tag (S177, N) ), If the <textarea> tag is present (S177, Y), the screen data generation unit 122 sets the argument value in the <textarea> tag (S178), and proceeds to process S181. .

  In process S181, the screen data generation unit 122 determines whether or not reading of all lines of the HTML form has been completed (S181). If completed (S181, Y), this flow ends and does not complete. In the case (S181, N), the process returns to the process S171 to read the next line.

  Next, a specific example of the HTML form generated by the above-described response input embedding process will be described.

  FIG. 14 is a diagram showing a specific example of the operation of the response input embedding process according to the present embodiment. This figure shows the relationship between the HTML form “furikomi001”, the record of request 3-1 in the communication data table, the argument of request 3-1 in the communication data file, the record of response 2-1 in the communication data table, and the transfer source designation screen. Show.

  In this figure, the HTML form “furikomi001” indicates the result of the response input embedding process. The request 3-1 indicates a request having a response input to “furikomi001” as an argument. The argument of the request 3-1 indicates a response input to “furikomi001”. The response 2-1 is a response that returns “furikomi001”, and indicates a response immediately before the request 3-1. The transfer source designation screen is a screen displayed as a result of embedding a response input in the HTML form “furikomi001”.

  In the HTML form “furikomi001”, “value = 001” and “value = 00001” representing respective response inputs are embedded in two <input> tags by the above-described response input embedding process.

  According to the screen data generation process described above, an HTML form in which a response is input to the HTML form can be generated based on the error log stored on the Web server 2 side and the captured communication data.

  Next, the data structure of the screen data storage unit 123 will be described.

  FIG. 15 is a table showing an example of the contents of the screen data storage unit according to the present embodiment. The screen data storage unit 123 stores a screen data table and a screen data file. The screen data table has a record for each screen data. The screen data table includes a customer ID, a response time stamp, and a screen data file name as items for each record. The screen data file name is linked to the HTML form generated by the response input embedding process. For reference, the screen displayed by each screen data file is shown at the bottom of the figure.

  In process S167, the screen data generation unit 122 acquires the customer ID of the corresponding operation from the operation log storage unit 5, acquires the corresponding response time stamp from the communication data storage unit 113, and displays the screen data along with the screen data file name. Register in the table.

  Next, GUI (Graphical User Interface) displayed by the screen display unit 134 will be described.

  FIG. 16 is a diagram illustrating an example of a GUI according to the present embodiment. The GUI includes a time stamp display unit 151, a screen data display unit 152, a first screen movement button 153, a backward button 154, a forward button 155, a final screen movement button 156, a screen slider 157, an error log display unit 158, and an input support message display unit. 159.

  The time stamp display unit 151 displays the time stamp of the screen data HTTP message. The screen data display unit 152 displays the screen data sent from the screen control unit 133. The screen additional information display unit 158 displays the screen additional information sent from the screen control unit 133. The first screen movement button 153, the backward button 154, the forward button 155, the last screen movement button 156, and the screen slider 157 accept an operation by the user of the screen reproduction device 4 and send the operation to the screen control unit 133.

  Next, screen control processing by the screen control unit 133 will be described.

  FIG. 17 is a flowchart showing an example of the operation of the screen control process according to the present embodiment. First, the screen control unit 133 determines whether or not a button is pressed on the operation screen by the user of the screen reproduction device 4 (S211). When the advance button is pressed (S211, advance button), the screen control unit 133 advances the screen by one (S212), and proceeds to the process S231. When the backward button is pressed (S211, backward button), the screen control unit 133 returns the screen by one (S213), and proceeds to processing S231. If the first screen movement button is pressed (S211, first screen movement button), the screen control unit 133 moves to the first screen (S214), and proceeds to step S231. When the last screen movement button is pressed (S211, last screen movement button), the screen control unit 133 moves to the first screen (S215), and proceeds to processing S231.

  If the button is not pressed (S211, NO), the screen control unit 133 determines whether the user of the screen reproduction device 4 has operated the slider on the operation screen (S221). When the slider is operated to the left (S221, left), the screen control unit 133 returns to the screen corresponding to the slider position (S222), and proceeds to processing S231. When the slider is operated to the right (S221, right), the screen control unit 133 advances to a screen corresponding to the slider position (S223), and proceeds to processing S231.

  In process S231, the screen control unit 133 reads a screen data file corresponding to the moved screen from the screen data storage unit 124, and reads a screen component file used in the screen data file from the screen data storage unit 124 (S231). The screen data file and the screen component file are displayed on the screen display unit 134 (S232), the error log in the error log storage unit 6 and the screen additional information in the screen additional information storage unit 132 are read (S233), and the error log and screen additional information are read out. Is displayed on the screen display unit 134 (S234), and the process returns to step S211 to determine the next operation.

  When the slider is not operated (S221, NO), the screen control unit 133 determines whether the operation on the operation screen is ended by the user of the screen reproduction device 4 (S241). If the operation has not been completed (S241, N), the process returns to step S211 to determine the next operation. On the other hand, when the operation is finished (S241, Y), this flow is finished.

  FIG. 18 is a diagram showing a specific example of a screen displayed on the screen display unit according to the present embodiment. The screen displayed on the screen data display unit 152 by the above-described screen control process is a screen based on any of the four screen data managed in the screen data table of FIG. 15, and the forward button 155 and the backward button 154 are displayed. Move between the four screens.

  Next, the data structure of the screen additional information stored in advance in the screen additional information storage unit 132 will be described.

  FIG. 19 is a block diagram showing an example of the data structure of screen additional information according to the present embodiment. The screen additional information includes an operation-HTML form association table 161, an error content-response input argument association table 162, and a response input support message table 163.

  FIG. 20 is a table showing an example of the contents of the operation-HTML form association table according to the present embodiment. The operation-HTML form association table 161 is a table showing associations between operations in the operation log and HTML forms, and for each operation, items of operation name, HTML form name, request for request, and response input request. have. The screen control unit 133 can acquire the operation corresponding to the screen data (HTML form name, argument name) by referring to this table.

  FIG. 21 is a table showing an example of the content of the error content-response input correspondence table according to the present embodiment. The error content-response input argument correspondence table 162 is a table showing correspondence between error content and response input, and has items of error message, HTML form name, and argument name for each error content. The screen control unit 133 can obtain error contents corresponding to the screen data (HTML form name, argument name) by referring to this table.

  FIG. 22 is a table showing an example of the content of the response input support message table according to the present embodiment. The response input support message table 163 stores an input support message (information related to input contents) that is a message for supporting an appropriate response input for the user of the client 1, and includes an HTML form name and an argument. Has a name and input support message items. The screen control unit 133 can obtain an input support message corresponding to the screen data (HTML form name, argument name) by referring to this table.

  According to the screen control process described above, the user of the screen reproduction device 4 can easily switch the screen based on the order of the screens displayed on the client 1. Furthermore, by displaying an error log and screen additional information corresponding to the screen data, it is possible to display the details of the error and the content of input support.

  Next, the reproduction of the screen of the client 1 by the screen reproduction device 4 when a trouble due to the operation of the user of the client 1 occurs will be described using two specific examples.

  The first specific example is a case where the user of the client 1 has entered the account number of the transfer destination to be input with 6 digits on the transfer destination designation screen with 1 digit.

  FIG. 23 is a diagram showing an example of information used for display of the first specific example according to the present embodiment. This figure shows an error log in the error log storage unit 6, an error content-response input correspondence table and an input support message table in the screen additional information storage unit 132. The portion indicated by a thick underline in the figure is related information.

  FIG. 24 is a diagram showing an example of GUI display in the first specific example according to the present embodiment. The screen control unit 133 causes the screen data display unit 152 to display the screen data in a state where the response input is embedded in the screen corresponding to the error log according to the operation of the user of the screen reproduction device 4, and the time stamp display unit 151. To display. Further, the screen control unit 133 reads the error content corresponding to the HTML form name and the argument name of the displayed screen data from the error content-response input correspondence table, and causes the error log display unit 158 to display the error content. Further, the screen control unit 133 reads out an input support message corresponding to the HTML form name and argument name of the displayed screen data from the input support message table, and causes the input support message display unit 159 to display the input support message.

  The second specific example is a case where the telephone number entered by the user of the client 1 is incorrect in the input of the telephone number for confirming the password reissue.

  FIG. 25 is a diagram showing an example of screen data in the second specific example according to the present embodiment. In the client 1, first, a login screen which is the first screen is displayed. Here, when the user of the client 1 performs an operation when the password is forgotten, a name / phone number confirmation screen which is the second screen is displayed. Here, when the user of the client 1 inputs a telephone number having an incorrect format, an error screen which is the third screen is displayed.

  FIG. 26 is a diagram showing an example of GUI display in the second specific example according to the present embodiment. The screen control unit 133 causes the screen data display unit 152 to display screen data in a state where the response input is embedded in the form of the name and telephone number confirmation screen according to the operation of the user of the screen reproduction device 4. Further, the screen control unit 133 reads the error content corresponding to the HTML form name and the argument name of the displayed screen data from the error content-response input correspondence table, and causes the error log display unit 158 to display the error content. Further, the screen control unit 133 reads out an input support message corresponding to the HTML form name and argument name of the displayed screen data from the input support message table, and causes the input support message display unit 159 to display the input support message.

  For example, a call center person can reproduce the screen of the client 1 in which an error has occurred by using the screen reproduction device 4, and can freely operate the transition to the previous and subsequent screens. The contents can be grasped accurately. Further, by displaying additional information corresponding to the screen together with the reproduced screen, the person in charge of the call center can take an appropriate action in response to the user's inquiry from the client 1.

Embodiment 2. FIG.

  Here, an example of a user operation of the client in the stock trading application will be described. FIG. 27 is a diagram illustrating a first state of the stock purchase screen displayed on the client. FIG. 28 is a diagram illustrating a second state of the stock purchase screen displayed on the client. FIG. 29 is a diagram showing a third state of the stock purchase screen displayed on the client. FIG. 30 is a diagram showing a fourth state of the stock purchase screen displayed on the client. FIG. 31 is a diagram illustrating a first state of a transaction confirmation screen displayed on the client. FIG. 32 is a diagram illustrating a fifth state of the stock purchase screen displayed on the client.

  The stock purchase screen displays a stock price display field for displaying a stock price, an update button, a purchased stock number input field for inputting the number of purchased stocks, a clear button, a transaction execution button, and a return button. First, it is assumed that login authentication is performed at the client, a stock name to be purchased is specified, and the first state of the stock purchase screen is displayed. If the user presses the update button in the first state of the stock purchase screen, the stock purchase screen changes from the first state to the second state. In the second state of the stock purchase screen, the stock price in the stock price display column in the first state of the stock purchase screen is updated when the client acquires the current stock price from the Web server. Next, if the user presses the update button in the second state of the stock purchase screen, the stock purchase screen transits from the second state to the third state. In the third state of the stock purchase screen, the stock price in the stock price display column in the second state of the stock purchase screen is updated when the client acquires the current stock price from the Web server.

  Next, in the third state of the stock purchase screen, if the user inputs the number of purchased stocks in the purchased stock number input field, the stock purchase screen changes from the third state to the fourth state. The fourth state of the stock purchase screen is obtained by inputting the number of purchased stocks in the purchased stock number input field in the third state of the stock purchase screen. Next, if the transaction execution button is pressed by the user in the fourth state of the stock purchase screen, the fourth state of the stock purchase screen transitions to the first state of the transaction confirmation screen.

  The first state of the transaction confirmation screen displays the stock price and the number of purchased shares in the fourth state of the stock purchase screen, and also displays an OK button and a cancel button. Next, when the cancel button is pressed by the user in the first state of the transaction confirmation screen, the first state of the transaction confirmation screen changes to the fifth state of the stock purchase screen. The fifth state of the stock purchase screen is the same as the fourth state of the stock purchase screen. Next, it is assumed that the user calls the call center due to operational questions.

  However, in the case of the operation example described above, when the call center has the screen reproduction device according to the first embodiment, the operator (the person in charge of the call center) changes the screen while switching the screen reproduced by the screen reproduction device 4. It was necessary to trace.

  The screen reproduction device according to the first embodiment may display a list screen in which a plurality of reproduced screens are listed. FIG. 33 is a diagram showing an example of a list screen by the screen reproduction device according to the first embodiment. In this list screen, the first state, the second state, the third state, the fourth state, the first state of the transaction confirmation screen, and the fifth state of the stock purchase screen are displayed in order. is there. However, when displaying a list screen for the above-described operation examples, it is difficult for the operator to confirm the details of the detailed operation, and in particular, it is difficult to grasp which button has been pressed to change to the next screen.

  In the present embodiment, a screen reproduction device that allows an operator to more easily grasp the state of screen transition in a client will be described.

  First, the configuration of the screen reproduction device according to the present embodiment will be described.

  FIG. 34 is a block diagram showing an example of the configuration of the screen reproduction device according to the present embodiment. In this figure, the same reference numerals as those in FIG. 2 denote the same or corresponding parts as those in FIG. 2, and the description thereof will be omitted here. Compared with FIG. 2, this figure includes a screen reproduction device 7 instead of the screen reproduction device 4. Further, the screen reproduction device 7 is newly compared with the screen reproduction device 4, a new reproduction target data aggregation unit 311, a transition number addition unit 312, a reproduction image creation unit 313, a reproduction image display unit 314, a reproduction data storage unit 315, a screen. An image template DB (Database) 321, a button overwrite information DB 322, and a data overwrite information DB 323, a communication data extraction unit 121, a screen data generation unit 122, a screen component file storage unit 123, a screen data storage unit 124, and a screen additional information storage unit 132, the screen control unit 133, and the screen display unit 134 are not required.

  The reproduction data storage unit 315 stores a reproduction target record extraction table, a reproduction target aggregation table, a data transition management table A, a data transition management table B, and overwrite reproduction screen image data.

  Next, the operation of the screen reproduction device according to the present embodiment will be described.

  The screen reproduction device according to the present embodiment performs the next screen reproduction process after performing the communication data acquisition process by the HTTP message observation unit 111 and the HTTP analysis unit 112, as in the first embodiment.

  FIG. 35 is a flowchart showing an example of the operation of the screen reproduction process according to the present embodiment. First, the reproduction target data aggregation unit 311 performs reproduction target data aggregation processing for aggregating data to be reproduced from information stored in the communication data storage unit 113 (S311). Next, the transition number adding unit 312 performs a transition number adding process for adding a number related to the screen transition to the data to be reproduced (S312). Next, the reproduction image creation unit 313 performs reproduction image creation processing for creating a reproduction image (S313). Next, the reproduction image display unit 314 performs reproduction image display processing for displaying the created reproduction image (S314), and this flow ends. Hereinafter, in order to simplify the description, a case will be described in which one screen corresponds to one form and the form is simple HTML with no image in the screen targeted by the screen reproduction device.

  Next, the reproduction target data aggregation process will be described.

  FIG. 36 is a flowchart showing an example of the operation of the reproduction target data aggregation processing according to the present embodiment. First, the reproduction target data aggregation unit 311 acquires information for designating a reproduction target (S321). The reproduction target is a reproduction target customer that is a customer who has performed an operation to be reproduced, and a reproduction target time zone that is a time zone in which the operation to be reproduced is performed. In the present embodiment, the information for designating the reproduction target customer is an IP address and connection port pair. Here, the reproduction target data aggregation unit 311 acquires these pieces of information from the input by the operator. The operator can acquire these pieces of information from information stored in the error log storage unit 6 or the communication data storage unit 113.

  Next, the reproduction target data aggregation unit 311 records in the communication data table stored in the communication data storage unit 113 that the time stamp is within the reproduction target time zone and has a specified IP address and connection port pair. Are extracted in the order of time stamps and stored in the reproduction target record extraction table of the reproduction data storage unit 315 (S322). Here, the record having the specified IP address and connection port pair is a record having the pair in “source IP address: connection port” or “destination IP address: connection port”. FIG. 37 is a table showing an example of the contents of the reproduction target record extraction table according to the present embodiment. This reproduction target record extraction table stores a time stamp, type, HTTP message header, and body among items in the communication data table.

  Next, the reproduction target data aggregation unit 311 initializes a variable n representing a response record number in the reproduction target record extraction table to 1 (S323). Next, the reproduction target data aggregating unit 311 reads the nth response record from the reproduction target record extraction table (S324), and performs a response analysis process for analyzing the response record (S325).

  Next, the reproduction target data aggregating unit 311 determines whether or not the next record in the reproduction target record extraction table is a request record. If the next record is not a request record (S331, N), the process proceeds to process S334, and a request is made. If it is a record (S331, Y), a request record which is the next record is read (S332), a request record analysis process for analyzing the request record is performed (S333), and the process proceeds to S334. Next, the reproduction target data aggregating unit 311 increments n by 1 (S334), determines whether or not the last response record of the reproduction target record extraction table has been read, and when the final response record has not been read ( In step S335, N), the process returns to step S324, and when the final response record is read (S335, Y), this flow ends.

  Some items in the reproduction target aggregation table of the reproduction data storage unit 315 are set by the response record analysis process and the request record analysis process. FIG. 38 is a table showing an example of the contents of the reproduction target aggregation table according to the present embodiment. This reproduction target aggregation table includes items such as time stamp, screen ID, screen transition order, button ID, pressing order, time difference, data ID (response), data (response), data ID (request), and data (request). Have. In this embodiment, one data is included in one request, and one data is included in one response. However, one request and one response include a plurality of data. Even in such a case, the present invention can be applied.

  Next, the response record analysis process will be described.

  FIG. 39 is a flowchart showing an example of response record analysis processing according to this embodiment. First, the reproduction target data aggregation unit 311 analyzes the body portion of the read response record (S341). Next, the reproduction target data aggregation unit 311 identifies the form (screen) type from the analysis result of the body part, and sets it to the screen ID in the reproduction target aggregation table (S342). Next, the reproduction target data aggregation unit 311 determines whether there is argument data in which a value is set in the response record (S343). If there is no argument data for which a value is set (S343, N), this flow ends. When there is argument data in which a value is set (S343, Y), the reproduction target data aggregation unit 311 identifies the type of argument data, sets the data ID (response) in the reproduction target aggregation table (S344), and the argument The data value is extracted and set in the data (response) in the reproduction target aggregation table (S345), and this flow ends.

  Next, the request record analysis process will be described.

  FIG. 40 is a flowchart showing an example of the operation of the request record analysis process according to the present embodiment. First, the reproduction target data aggregation unit 311 sets the time stamp of the read request record to “time stamp” of the reproduction target aggregation table (S352).

  Next, the reproduction target data aggregation unit 311 determines whether n is greater than 1, and when n is not greater than 1 (S353, N), the process proceeds to step S355, and when n is greater than 1 ( (S353, Y), the difference between the time stamp of the request record and the time stamp of the previous record of the reproduction target aggregation table is calculated, and set as the time difference of the reproduction target aggregation table as a signed value (S354). Next, the reproduction target data aggregation unit 311 analyzes the body part of the read request record (S355), identifies the type of the clicked button (including a click operation such as a link) from the analysis result, and reproduces it. The button ID is set in the target aggregation table (S356).

  Next, the reproduction target data aggregation unit 311 determines whether there is argument data with a value set in the request record (S357). If there is no argument data for which a value has been set (S357, N), this flow ends. When there is argument data in which a value is set (S357, Y), the reproduction target data aggregation unit 311 identifies the type of argument data, sets the data ID (request) of the reproduction target aggregation table (S358), and the argument The data value is extracted and set in the reproduction target aggregation table data (request) (S359), and this flow ends.

  According to the reproduction target aggregation process described above, a series of operations by a user designated as a target can be extracted.

  Next, the transition number addition process will be described.

  FIG. 41 is a flowchart showing an example of the operation of the transition number addition processing according to the present embodiment. First, the transition number addition unit 312 performs screen transition order addition processing for setting information on the screen transition order in the reproduction target aggregation table (S361), and adds push button order information for setting the information on the push button order in the reproduction target aggregation table. Processing is performed (S362), data transition addition processing for setting data transition information in the reproduction target aggregation table is performed (S363), and this flow ends.

  Next, the screen transition order addition process will be described.

  FIG. 42 is a flowchart showing an example of the operation of the screen transition order addition processing according to the present embodiment. First, the transition number adding unit 312 initializes a variable n indicating a record number in the reproduction target aggregation table to 1 (S371), and sets 1 in the order of screen transition of the first record in the reproduction target aggregation table (S372). Next, the transition number adding unit 312 determines whether or not there are a plurality of records in the reproduction target aggregation table. If there is no record (S373, N), this flow ends, and if it exists (S373, S373). Y) The process proceeds to the next process.

  Next, the transition number adding unit 312 increments n by 1 (S374), and reads the nth record of the reproduction target aggregation table (S375). Next, the transition number adding unit 312 determines whether or not the screen ID is the same as the (n−1) th record (S376). If they are the same (S376, Y), the transition number adding unit 312 sets the same value as the screen transition order of the (n-1) th record in the screen transition order of the nth record of the reproduction target aggregation table (S377). If they are not the same (S376, N), the screen transition order value +1 of the (n-1) th record is set in the screen transition order of the nth record of the reproduction target aggregation table (S378), and the process proceeds to S379. Next, the transition number adding unit 312 determines whether or not the last record of the reproduction target aggregation table has been processed. If the last record has not been processed (S379, N), the process returns to step S374, and the last record is If processed (S379, Y), this flow ends.

  Next, the push button order addition process will be described.

FIG. 43 is a flowchart showing an example of the operation of the push button order addition processing according to the present embodiment. First, the transition number adding unit 312 initializes a variable n indicating a record number in the reproduction target aggregation table to 1 (S381), and reads the nth record in the reproduction target aggregation table (S382). Next, the transition number adding unit 312 determines whether a button ID is set for the read record,
If it has not been set (S383, N), this flow ends. If it is set (S383, Y), the transition number adding unit 312 sets n in the order of pressing the nth record (S384), and increases n by 1 (S385). Next, the transition number adding unit 312 determines whether or not the last record of the reproduction target aggregation table has been processed. If the last record has not been processed (S386, N), the process returns to step S382, If processed (S386, Y), this flow ends.

  In the present embodiment, the case where the screen transition is performed when the button is pressed is described. However, the present invention can be applied even when the screen transition is performed by another trigger.

  Next, the data transition addition process will be described.

  FIG. 44 is a flowchart showing an example of the operation of the data transition addition processing according to the present embodiment. First, the transition number adding unit 312 reads all the records in the reproduction target aggregation table in order (in ascending order of time stamps), data ID (response), data (response), data ID (request), data (request), and pressing. The order is read (S391). Next, the transition number adding unit 312 creates a data transition management table A for each value of the data ID (response) existing in the reproduction target aggregation table, and stores it in the reproduction data storage unit 315 (S392).

  FIG. 45 is a diagram showing an example of the contents of the data transition management table A according to the present embodiment. As described above, the response data transition management table A for each value of the data ID (response) is created. Here, since the data ID (response) has two types of values (purchased stock price, finalized stock price), two data transition management tables A are created. Each data transition management table A has items of data value and pressing order. The data value in the data transition management table A corresponds to the data (response) in the reproduction target aggregation table, and the pressing order corresponds to the pressing order in the reproduction target aggregation table.

  Next, the transition number adding unit 312 sets the value of the data (response) of the corresponding record in the reproduction target aggregation table as the data value of each record in the data transition management table A, and sets each record in the data transition management table A. As the pressing order, the value of the pressing order of the previous record in the reproduction target aggregation table is set (S393).

  Next, the transition number adding unit 312 acquires a record having a data value overlapping with the data value of the immediately preceding record in each data transition management table A, adds the pressing order to the pressing order of the immediately preceding record, and acquires it. The recorded record is deleted (S394).

  Next, the transition number adding unit 312 creates a data transition table B for each value of the data ID (request) existing in the reproduction target aggregation table, and stores it in the reproduction data storage unit 315 (S395).

  FIG. 46 is a diagram showing an example of the contents of the data transition management table B according to the present embodiment. Here, since the data ID (request) has two types of values (the number of purchased shares and the number of confirmed shares), two data transition management tables B are created. Each data transition management table B has a data value item. The data value in the data transition management table B corresponds to the data (request) in the reproduction target aggregation table.

  Next, the transition number adding unit 312 sets the data value of the corresponding record in the reproduction target aggregation table as the data value of each record in the data transition management table B (S396).

  Next, the transition number adding unit 312 deletes a record having a data value overlapping with the data value of the immediately preceding record in each data transition management table B (S397), and this flow ends.

  According to the transition number addition process described above, it is possible to extract the order of screens and the order of operations that have been transitioned in a target series of operations.

  In this embodiment, since the data (response) changes, the data value and the pressing order are set in the data transition management table A for each value of the data ID (response), but the data (request) changes. In this case, the data value and the pressing order may be set in the data transition management table B for each value of the data ID (request).

  Next, the reproduction image creation process will be described.

  The screen image template DB 321, the button overwrite information DB 322, and the data overwrite information DB 323 which are information used for the reproduction image creation processing are created in advance and stored in a storage device.

  FIG. 47 is a table showing an example of the contents of the screen image template DB according to the present embodiment. The screen image template DB 321 includes a screen ID and image data location as items. The screen ID in the screen image template DB 321 corresponds to the screen ID in the reproduction target aggregation table, and the image data location indicates the path of the screen image template data. The screen image template data is an image of a screen when the HTML form corresponding to the screen ID is displayed with a predetermined screen size. The screen image template data is created in advance without any value and stored in the image data location.

  FIG. 48 is a table showing an example of the contents of the button overwrite information DB according to the present embodiment. The button overwrite information DB 322 includes a button ID, a screen ID, an overwrite coordinate, and an overwrite image as items. The button ID in the button overwrite information DB 322 corresponds to the button ID in the reproduction target aggregation table, and the screen ID corresponds to the screen ID in the reproduction target aggregation table. The overwrite coordinates are coordinates (X, Y) indicating the position of the button when the HTML form corresponding to the screen ID is displayed with a predetermined image size. The overwrite image is an image for emphasizing the position of the button.

  FIG. 49 is a table showing an example of the contents of the data overwrite information DB according to the present embodiment. The data overwrite information DB 323 has data ID, screen ID, overwrite coordinates, and shift coordinates as items. The data ID in the data overwrite information DB 323 corresponds to the data ID (response) or the data ID (request) in the reproduction target aggregation table, and the screen ID corresponds to the screen ID in the reproduction target aggregation table. The overwrite coordinates are coordinates (X, Y) indicating the position of data when the HTML form corresponding to the screen ID is displayed with a predetermined image size. The shift coordinate is a coordinate unit (X, Y) for shifting the position of data to be overwritten.

  Note that the reproduction image creation unit 313 creates an image on which an HTML form corresponding to the screen ID is displayed and creates screen image template data based on a preset screen size before the reproduction image creation processing. May be. Further, the reproduction image creation unit 313 may calculate the overwrite coordinates based on a preset screen size. The reproduced image creation unit 313 may calculate the overwrite coordinates and the shift coordinates based on a preset screen size.

  FIG. 50 is a flowchart showing an example of the operation of the reproduction image creation processing according to the present embodiment. First, the reproduction image creation unit 313 reads all reproduction target aggregation tables (S411). Next, the reproduction image creation unit 313 acquires screen image template data corresponding to each screen ID in the reproduction target aggregation table based on the screen image template DB 321 and reproduces it as overwrite reproduction screen image data corresponding to each screen ID. The data is stored in the data storage unit 315 (S412). Here, the reproduction image creation unit 313 first acquires the image data location corresponding to the screen ID in the screen image template DB 321 and acquires the screen image template data from the acquired image data location.

  Next, the reproduction image creation unit 313 acquires all the button IDs in the reproduction target aggregation table, and performs button overwrite processing for overwriting the image on the overwrite reproduction screen image data based on the button overwrite information DB 322 (S413). Here, the reproduction image creation unit 313 acquires the overwrite coordinates and the overwrite screen by referring to the button overwrite information DB 322 using the button ID as a key, and overwrites the overwrite image at the position of the overwrite coordinates on the overwrite reproduction screen image data. To do.

  Next, the reproduction image creation unit 313 reads the button ID, the screen ID, the pressing order, and the time difference in all records in which the value of the pressing order of the reproduction target aggregation table is set, and overwrites the button using the button ID as a key. Overwriting coordinates are acquired by referring to the information DB 322, and a data overwriting process is performed to overwrite the vicinity of the position of the overwriting coordinates on the overwriting reproduction screen image data with the values in the pressing order and the time difference values as images (S414). This flow ends.

  Next, the data overwriting process will be described.

  FIG. 51 is a flowchart showing an example of the operation of data overwriting processing according to the present embodiment. First, the reproduction image creation unit 313 initializes a variable n indicating a record number of the data transition management table A to 0 (S421). Next, the reproduction image creation unit 313 reads the (n + 1) th record of the data transition management table A (S422). Next, the reproduction image creation unit 313 calculates data coordinates based on the data transition management table A and the data overwrite information DB 323, and sets the pressing order of the data transition management table A and the data value on the corresponding overwrite reproduction screen image data. The data coordinates are overwritten (S423). The data coordinates are coordinates of the order of pressing and data values arranged on the overwrite reproduction screen image data. Here, the reproduction image creation unit 313 acquires the overwrite coordinates and shift coordinates of the data overwrite information DB 323 using the data ID and screen ID of the data transition management table A as keys, and (overwrite coordinates) + (shift coordinates) * Let n be the data coordinate.

  Next, the reproduction image creation unit 313 increments n by 1 (S424), determines whether or not the process has been processed up to the last record of the data transition management table A, and if not processed to the last record (S425, N) ), The process returns to step S422, and if the process reaches the last record (Y in S425), the process proceeds to the next process. Next, the reproduction image creation unit 313 determines whether or not all the data transition management tables A have been processed. If all the data transition management tables A have not been processed (S426, N), the process proceeds to step S421. Returning, the process for the next data transition management table A is performed, and if all the data transition management tables A are processed (S426, Y), the process proceeds to the next process.

  Next, the reproduction image creation unit 313 initializes a variable n indicating the record number of the data transition management table B to 0 (S431). Next, the reproduction image creation unit 313 reads the (n + 1) th record of the data transition management table B (S432). Next, the reproduction image creation unit 313 calculates data coordinates based on the data transition management table B and the data overwrite information DB 323, and sets the pressing order of the data transition management table B and the data value on the corresponding overwrite reproduction screen image data. The data coordinates are overwritten (S433). Here, the reproduction image creation unit 313 acquires the overwrite coordinates and shift coordinates of the data overwrite information DB 323 using the data ID and screen ID of the data transition management table B as keys, and (overwrite coordinates) + (shift coordinates) * Let n be the data coordinate.

  Next, the reproduced image creation unit 313 increments n by 1 (S434), determines whether or not the process has been processed up to the last record of the data transition management table B, and if not processed to the last record (S435, N) ), The process returns to the process S432, and when the process up to the last record is performed (S435, Y), the process proceeds to the next process. Next, the reproduction image creation unit 313 determines whether or not all the data transition management tables B have been processed. If all the data transition management tables B have not been processed (S436, N), the process proceeds to the process S431. Returning, the process for the next data transition management table B is performed, and if all the data transition management tables B are processed (S436, Y), this flow ends.

  According to the above-described reproduction image generation processing, it is possible to generate a screen in which the content and order of operations on each screen and the content and order of display are added to a target series of screens. For click operations such as buttons, add an image that emphasizes the clicked position, the order of operations, a time difference from the previous operation, etc. to the form image, and input and display values. For example, an operator can easily grasp a series of operations by adding a value and an operation order, a time difference from the previous operation, and the like near the position of the value of the form image.

  Next, the reproduction image display process will be described.

  FIG. 52 is a flowchart showing an example of the operation of the reproduction image display process according to the present embodiment. First, the reproduction image display unit 314 acquires the screen transition order corresponding to the screen ID of each overwrite reproduction screen image data from the reproduction target aggregation table, and sets it as the attribute of each overwrite reproduction screen image data (S441). Next, each overwrite reproduction screen image data and its attributes are displayed together as a reproduction screen (S442), and this flow ends.

  Next, an example of a reproduction screen displayed by the reproduction image display process will be described.

  FIG. 53 is a diagram showing an example of a reproduction screen according to the present embodiment. This reproduction screen displays two overwrite reproduction screen image data side by side. Of the two overwrite reproduction screen image data, the first overwrite reproduction screen image data displayed on the left side is created based on the first screen image template data stored in the screen image template DB 321, and the second overwrite reproduction screen image data is displayed. The reproduction screen image data is created based on the second screen image template data stored in the screen image template DB 321. FIG. 54 is a diagram showing an example of first screen image template data according to the present embodiment. FIG. 55 is a diagram showing an example of second screen image template data according to the present embodiment. The screen ID of the first screen image template data is “stock purchase”, and the screen ID of the second screen image template data is “confirmed transaction”. These screen image template data are overwrite reproduction screen image data before being overwritten.

  In addition, by the button overwriting process, the overwrite image indicating the operated button (“update”, “transaction execution”) is overwritten on the overwrite coordinates in the first overwrite reproduction screen image data, and the second overwrite reproduction screen image is displayed. In the data, an overwrite image indicating the operated button (“CANCEL”) is overwritten on the overwrite coordinates.

  In addition, an image indicating the value of the input or displayed data (“purchased stock price”, “purchased stock number”) is overwritten on the data coordinates in the first overwrite reproduction screen image data by the data overwrite processing, and the second overwrite is performed. In the reproduction screen image data, the values of the manipulated data (“determined stock price”, “determined stock number”) are overwritten on the data coordinates. Further, the data overwrite processing overwrites the data coordinates with the time difference of the button press and the value of the button press (1, 2, 3) in the first overwrite reproduction screen image data and the second overwrite reproduction screen image data. The

  In this example, two overwrite reproduction screen image data are displayed. However, the screen image template data is created so that the screen size is easy to see, and the overwrite reproduction screen image data displayed on the reproduction screen is displayed based on the screen size. The number may be determined. Alternatively, the screen size may be determined based on the number of overwrite reproduction screen image data displayed on the reproduction screen, and the screen image template DB 321, the button overwrite information DB 322, and the data overwrite information DB 323 may be created according to the screen size. .

  According to the reproduction image display process described above, a series of screens generated by the reproduction image generation process and the order of each screen can be displayed. Further, by displaying a plurality of overwrite screen image data, the operator can easily grasp an operation involving screen transition.

  In addition, the screen generation apparatus according to the present embodiment can be easily applied to the information processing apparatus, and can further improve the performance of the information processing apparatus. Here, the information processing apparatus may include, for example, a server, a call center terminal, an administrator terminal, and the like.

  Furthermore, it is possible to provide a program that causes a computer constituting the screen generation apparatus to execute the above steps as a screen generation program. By storing the above-described program in a computer-readable recording medium, the computer constituting the screen generation device can be executed. Here, examples of the recording medium readable by the computer include an internal storage device such as a ROM and a RAM, a portable storage such as a CD-ROM, a flexible disk, a DVD disk, a magneto-optical disk, and an IC card. It includes a medium, a database holding a computer program, another computer and its database, and a transmission medium on a line.

  The acquisition step corresponds to the communication data acquisition process and the communication data extraction process in the embodiment. The generation step corresponds to screen data generation processing, reproduction target data aggregation processing, transition number addition processing, and reproduction image creation processing in the embodiment. The first display step corresponds to the screen control process in the embodiment. The second display step corresponds to the reproduction screen display process in the embodiment. The acquisition unit corresponds to the HTTP message observation unit 111, the HTTP analysis unit 112, and the communication data extraction unit 121 in the embodiment. The generation unit corresponds to the screen data generation unit 122, the reproduction target data aggregation unit 311, the transition number addition unit 312, and the reproduction image creation unit 313 in the embodiment.

  The first data corresponds to the HTML form in the embodiment. The first screen corresponds to the Web screen in the embodiment. The second data corresponds to the response input, argument data, and button type in the embodiment. The second screen corresponds to the overwrite reproduction screen image data in the embodiment. The third data corresponds to the HTML form and overwrite reproduction screen image data generated by the response input embedding process in the embodiment. The fourth data corresponds to the image data in the embodiment. The operation corresponds to a button click or a value input in the embodiment. The operation order corresponds to the pressing order, the data transition management table A, and the data transition management table B in the embodiment. The screen order corresponds to the screen transition order in the embodiment. The screen order corresponds to the screen transition order in the embodiment. The figure that emphasizes the operation position corresponds to the overwritten image in the embodiment. The operation position corresponds to the overwrite coordinates in the embodiment. The vicinity of the operation position corresponds to the data coordinates in the embodiment.

(Appendix 1) A screen generation program for causing a computer different from the client to generate a screen displayed on the client based on communication with the server,
First data that is data transmitted from the server to the client and that causes the client to display a first screen that accepts a user operation; and data that is transmitted from the client to the server An acquisition step of acquiring second data which is data indicating an operation accepted on the first screen displayed on the client;
Based on the first data and the second data acquired in the acquisition step, third data for displaying a second screen obtained by adding operation information, which is information based on the second data, to the first screen is displayed. A screen generation program that causes a computer to execute a generation step to be generated.
(Appendix 2) In the screen generation program described in Appendix 1,
The acquisition step further includes acquiring fourth data that is data transmitted from the server to the client and that causes the client to display a screen.
(Appendix 3) In the screen generation program described in Appendix 1 or Appendix 2,
The screen generating program characterized in that the acquiring step acquires first data and second data from captured data, which is data obtained by capturing communication between the server and the client.
(Appendix 4) In the screen generation program described in Appendix 3,
The acquisition step extracts a request message that is a message from the client to the server and a response message that is a message from the server to the client from the capture data, and acquires first data from the extracted response message. A screen generation program that acquires second data from a request message immediately after the response message.
(Appendix 5) In the screen generation program described in Appendix 4,
The obtaining step obtains an error content in the error log of the server, extracts a message corresponding to the error content from the message, extracts a message related to the message, and extracts first data and the message from the message. A screen generation program for acquiring second data.
(Appendix 6) In the screen generation program described in Appendix 4 or Appendix 5,
A screen generation program characterized in that the first data is a form and the second data is an argument of a request message.
(Appendix 7) In the screen generation program described in Appendix 6,
The screen generating program according to claim 1, wherein the generating step uses third data obtained by adding a description of the argument value to the form.
(Supplementary note 8) In the screen generation program according to any one of supplementary notes 1 to 7,
Further, screen data is selected based on an instruction from the user interface from among a plurality of screen data including the third data, which is data for displaying a screen, and the screen based on the selected screen data is selected. A screen generation program for causing a computer to execute a first display step for performing display.
(Supplementary note 9) In the screen generation program described in supplementary note 8,
In the first display step, in addition to a screen based on the selected screen data, an error content corresponding to second data among error contents in the error log of the server is displayed.
(Supplementary Note 10) In the screen generation program according to Supplementary Note 8 or Supplementary Note 9,
In the first display step, in addition to a screen based on the selected screen data, information corresponding to the input content among information relating to second data stored in advance is displayed.
(Supplementary note 11) In the screen generation program according to any one of supplementary notes 1 to 7,
The screen generation program, wherein the operation information includes an operation order which is the order of the operations.
(Supplementary note 12) In the screen generation program according to supplementary note 11,
The generation step acquires an operation position that is an operation position on the first screen based on the second data, and sets a second screen on which the operation information is added to the position based on the operation position on the first screen. A screen generation program characterized by a screen.
(Supplementary note 13) In the screen generation program according to supplementary note 11 or supplementary note 12,
The generation step acquires a screen order that is an order in which a plurality of first screens are displayed on the client based on the plurality of first data, and generates third data corresponding to the plurality of first screens,
Furthermore, the screen generation program which makes a computer perform the 2nd display step which matches and displays several 3rd data and the information which shows the said screen order.
(Supplementary Note 14) In the screen generation program according to any one of Supplementary Notes 11 to 13,
When the second data indicates a click on the operation position, the operation information includes a figure that emphasizes the operation position, and the generation step includes a screen with the operation information added in the vicinity of the operation position on the first screen. A screen generation program characterized by being a second screen.
(Supplementary Note 15) In the screen generation program according to any one of Supplementary Notes 11 to 14,
When the second data indicates input or display of a value at the operation position, the operation information includes the value, and the generation step includes a screen with the operation information added in the vicinity of the operation position on the first screen. A screen generation program characterized by being a second screen.
(Supplementary Note 16) In the screen generation program according to any one of Supplementary Notes 11 to 15,
The generation step further includes obtaining a time of the operation based on second data, and including information related to the time of the operation in the operation information.
(Supplementary note 17) In the screen generation program according to supplementary note 16,
The information relating to the time of the operation is a time difference between the target operation and the operation immediately before the operation.
(Supplementary note 18) In the screen generation program according to any one of supplementary notes 11 to 17,
The generating step acquires an image of the first screen having a predetermined screen size, acquires the operation position based on the first data and the predetermined screen size, and acquires the image of the first screen, the operation information, A screen generation program that generates an image of a second screen based on the operation position and uses the image as third data.
(Supplementary note 19) A screen generation device that generates a screen displayed on a client based on communication with a server,
First data that is data transmitted from the server to the client and that causes the client to display a first screen that accepts a user operation; and data that is transmitted from the client to the server An acquisition unit that acquires second data that is data indicating an operation received on the first screen displayed on the client;
Based on the first data and the second data acquired by the acquisition unit, third data for displaying a second screen obtained by adding operation information, which is information based on the second data, to the first screen is displayed. A screen generation device comprising:
(Supplementary note 20) A screen generation method for generating a screen displayed on a client based on communication with a server by using an information processing apparatus different from the client,
First data that is data transmitted from the server to the client and that causes the client to display a first screen that accepts a user operation; and data that is transmitted from the client to the server An acquisition step of acquiring second data which is data indicating an operation accepted on the first screen displayed on the client;
Based on the first data and the second data acquired in the acquisition step, third data for displaying a second screen obtained by adding operation information, which is information based on the second data, to the first screen is displayed. A screen generation method for executing a generation step and.

1 is a block diagram illustrating an example of a configuration of a Web system according to a first embodiment. 1 is a block diagram illustrating an example of a configuration of a screen reproduction device according to a first embodiment. 4 is a table illustrating an example of an operation log according to the first embodiment. 4 is a table illustrating an example of an error log according to the first embodiment. It is a table | surface which shows an example of the data structure of an HTTP request message. It is a table | surface which shows an example of the data structure of an HTTP response message. It is a sequence diagram which shows an example of an HTTP message. 6 is a flowchart illustrating an example of operation of communication data acquisition processing according to the first embodiment. 6 is a flowchart illustrating an example of an operation of HTTP protocol analysis processing according to the first embodiment. 4 is a table illustrating an example of contents of a communication data storage unit 113 according to Embodiment 1. 6 is a flowchart illustrating an example of operation of communication data extraction processing according to the first embodiment. 6 is a flowchart illustrating an example of an operation of screen data generation processing according to the first embodiment. 6 is a flowchart illustrating an example of an operation of a response input embedding process according to the first embodiment. 6 is a diagram illustrating a specific example of an operation of a response input embedding process according to Embodiment 1. FIG. 5 is a table showing an example of contents of a screen data storage unit according to the first embodiment. 3 is a diagram illustrating an example of a GUI according to Embodiment 1. FIG. 4 is a flowchart illustrating an example of an operation of a screen control process according to the first embodiment. 6 is a diagram illustrating a specific example of a screen displayed on the screen display unit according to Embodiment 1. FIG. 6 is a block diagram illustrating an example of a data structure of screen additional information according to Embodiment 1. FIG. 10 is a table showing an example of contents of an operation-HTML form association table according to the first embodiment. 10 is a table showing an example of contents of an error content-response input correspondence table according to the first embodiment. 7 is a table showing an example of the contents of a response input support message table according to the first embodiment. 6 is a diagram illustrating an example of information used for display of a first specific example according to Embodiment 1. FIG. 6 is a diagram showing an example of GUI display in the first specific example according to Embodiment 1. FIG. 6 is a diagram showing an example of screen data in a second specific example according to Embodiment 1. FIG. 10 is a diagram showing an example of GUI display in the second specific example according to Embodiment 1. FIG. It is a figure which shows the 1st state of the stock purchase screen displayed on the client. It is a figure which shows the 2nd state of the stock purchase screen displayed on the client. It is a figure which shows the 3rd state of the stock purchase screen displayed on the client. It is a figure which shows the 4th state of the stock purchase screen displayed on the client. It is a figure which shows the 1st state of the transaction confirmation screen displayed on the client. It is a figure which shows the 5th state of the stock purchase screen displayed on the client. 6 is a diagram showing an example of a list screen by the screen reproduction device according to Embodiment 1. FIG. 6 is a block diagram illustrating an example of a configuration of a screen reproduction device according to Embodiment 2. FIG. 10 is a flowchart illustrating an example of an operation of a screen reproduction process according to the second embodiment. 12 is a flowchart illustrating an example of operation of reproduction target data aggregation processing according to the second embodiment. 10 is a table showing an example of a reproduction target record extraction table according to the second embodiment. 10 is a table illustrating an example of contents of a reproduction target aggregation table according to Embodiment 2. 12 is a flowchart illustrating an example of an operation of a response record analysis process according to the second embodiment. 10 is a flowchart illustrating an example of an operation of a request record analysis process according to the second embodiment. 12 is a flowchart illustrating an example of an operation of a transition number addition process according to the second embodiment. 10 is a flowchart illustrating an example of an operation of a screen transition order addition process according to the second embodiment. 12 is a flowchart illustrating an example of an operation of a push button order addition process according to the second embodiment. 10 is a flowchart illustrating an example of an operation of a data transition addition process according to the second embodiment. It is a figure which shows an example of the content of the data transition management table A which concerns on Embodiment 2. FIG. It is a figure which shows an example of the content of the data transition management table B which concerns on Embodiment 2. FIG. 10 is a table showing an example of contents of a screen image template DB according to the second embodiment. 10 is a table showing an example of contents of a button overwrite information DB according to Embodiment 2. 10 is a table showing an example of contents of a data overwrite information DB according to Embodiment 2. 10 is a flowchart illustrating an example of an operation of a reproduction image creation process according to the second embodiment. 10 is a flowchart illustrating an example of an operation of data overwriting processing according to the second embodiment. 10 is a flowchart illustrating an example of an operation of a reproduction image display process according to the second embodiment. 10 is a diagram showing an example of a reproduction screen according to Embodiment 2. FIG. It is a figure which shows an example of the 1st screen image model data which concerns on Embodiment 2. FIG. It is a figure which shows an example of the 2nd screen image model data which concerns on Embodiment 2. FIG.

Explanation of symbols

1 client, 2 Web server, 3 network switch, 4,7 screen reproduction device, 5 operation log storage unit, 6 error log storage unit, 111 HTTP message observation unit, 112 HTTP analysis unit, 113 communication data storage unit, 121 communication data Extraction unit, 122 screen data generation unit, 123 screen part file storage unit, 124 screen data storage unit, 132 screen additional information storage unit, 133 screen control unit, 134 screen display unit, 151 time stamp display unit, 152 screen data display unit 153 First screen move button, 154 Backward button, 155 Forward button, 156 Last screen move button, 157 Screen slider, 158 Error log display section, 159 Input support message display section, 161 operation-HTML form correspondence table, 162 error Content-response input argument association table, 163 response input support message table, 311 reproduction target data aggregation unit, 312 transition number addition unit, 313 reproduction image creation unit, 314 reproduction image display unit, 315 reproduction data storage unit, 321 screen image Template DB, 322 Button overwrite information DB, 323 Data overwrite information DB.

Claims (10)

A screen generation program for causing a computer different from the client to generate a screen displayed on the client based on communication with a server,
First data that is data transmitted from the server to the client and that causes the client to display a first screen that accepts a user operation; and data that is transmitted from the client to the server An acquisition step of acquiring second data which is data indicating an operation accepted on the first screen displayed on the client;
Based on the first data and the second data acquired in the acquisition step, third data for displaying a second screen obtained by adding operation information, which is information based on the second data, to the first screen is displayed. A screen generation program that causes a computer to execute a generation step to be generated. The screen generation program according to claim 1,
The acquisition step further includes acquiring fourth data that is data transmitted from the server to the client and that causes the client to display a screen. In the screen generation program according to claim 1 or 2,
The screen generating program characterized in that the acquiring step acquires first data and second data from captured data, which is data obtained by capturing communication between the server and the client. In the screen generation program according to claim 3,
The acquisition step extracts a request message that is a message from the client to the server and a response message that is a message from the server to the client from the capture data, and acquires first data from the extracted response message. A screen generation program that acquires second data from a request message immediately after the response message. The screen generation program according to claim 4,
The obtaining step obtains an error content in the error log of the server, extracts a message corresponding to the error content from the message, extracts a message related to the message, and extracts first data and the message from the message. A screen generation program for acquiring second data. In the screen generation program according to claim 4 or 5,
A screen generation program characterized in that the first data is a form and the second data is an argument of a request message. The screen generation program according to claim 6,
The screen generating program according to claim 1, wherein the generating step uses third data obtained by adding a description of the argument value to the form. In the screen generation program in any one of Claims 1 thru | or 7,
The screen generation program, wherein the operation information includes an operation order which is the order of the operations. A screen generation device that generates a screen displayed on a client based on communication with a server,
First data that is data transmitted from the server to the client and that causes the client to display a first screen that accepts a user operation; and data that is transmitted from the client to the server An acquisition unit that acquires second data that is data indicating an operation received on the first screen displayed on the client;
Based on the first data and the second data acquired by the acquisition unit, third data for displaying a second screen obtained by adding operation information, which is information based on the second data, to the first screen is displayed. A screen generation device comprising: A screen generation method for generating a screen displayed on a client based on communication with a server by using an information processing apparatus different from the client,
First data that is data transmitted from the server to the client and that causes the client to display a first screen that accepts a user operation; and data that is transmitted from the client to the server An acquisition step of acquiring second data which is data indicating an operation accepted on the first screen displayed on the client;
Based on the first data and the second data acquired in the acquisition step, third data for displaying a second screen obtained by adding operation information, which is information based on the second data, to the first screen is displayed. A screen generation method for executing a generation step and.

Images