Software product inquiry creation device, software product inquiry creation method and program

Abstract

To provide a software product inquiry generation device which can clarify inquiry contents.SOLUTION: A software product inquiry generation device 1 comprises: a moving image acquisition unit 52 which acquires a moving image in which an operation screen changing in display contents in response to an operation of a user is recorded by a software product having a function to display the operation screen; a heart rate acquisition unit 53 which acquires a heart rate of the user measured during a prescribed period in which the operation is performed; an inquiry generation unit 59 which generates an inquiry screen including the moving image and the heart rate; and a communication unit 60 which transmits the inquiry screen to a responder.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a software product inquiry creation device, a software product inquiry creation method, and a program. [Background technology]

[0002] A screen selection device that selects screens that are estimated to be highly useful and transmits these screens to a server device as information necessary for an operator to resolve an inquiry is described, for example, in Patent Document 1. Patent Document 1 describes the user's heart rate as an example of a numerical value that is extracted from an operation / state by a judgment rule (judgment on whether to acquire a screen) (see paragraph 0041).

[0003] In response to this, the inventors considered clarifying the content of technical inquiries about software products, taking into consideration that when making technical inquiries about software products, the content of the inquiry may not be accurately conveyed to the respondent using only a written explanation. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] International Publication No. 2013 / 042180 Summary of the Invention [Problem to be solved by the invention]

[0005] However, Patent Document 1 does not propose at all to clarify the content of technical inquiries about software products.

[0006] In view of the above-mentioned problems, an object of the present invention is to provide a software product inquiry creation device, a software product inquiry creation method, and a program that can clarify the content of technical inquiries about software products. [Means for solving the problem]

[0007] The software product inquiry generation device of the present invention comprises: a video acquisition unit that acquires a video of a software product having a function of displaying an operation screen whose display content changes in response to a user's operation; a heart rate acquisition unit that acquires the user's heart rate measured within a predetermined period during which the operation is performed; an inquiry creation unit that creates an inquiry screen including the video and the heart rate; and a communication unit that transmits the inquiry screen to the respondent.

[0008] The software product inquiry generation method of the present invention comprises: a video acquisition step of acquiring a video of a software product having a function of displaying an operation screen whose display content changes in response to a user's operation; a heart rate acquisition step of acquiring the user's heart rate measured within a predetermined period during which the operation is performed; an inquiry creating step of creating an inquiry screen including the video and the heart rate; and a communication step of transmitting the inquiry screen to a respondent.

[0009] The program of the present invention is A process of acquiring a video recording of an operation screen of a software product having a function of displaying an operation screen whose display content changes in response to a user's operation; A process of acquiring the user's heart rate measured within a predetermined period during which the operation is performed; a process of creating an inquiry screen including the video and the heart rate; a process of transmitting the inquiry screen to a respondent; It is a program for causing a computer (information processing device) to execute the above. [Effects of the Invention]

[0010] According to the present invention, it is possible to provide a software product inquiry creation device, a software product inquiry creation method, and a program that can clarify the content of a technical inquiry about a software product. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a schematic configuration diagram of a software product inquiry creation device 1. FIG. [Figure 2] 10 is a flowchart showing an example of the operation of the software product inquiry making device 1. [Figure 3] FIG. 10 is a block diagram showing a configuration of a software product inquiry making system 100 including a software product inquiry making device 1 according to a second embodiment. [Figure 4] 10 is an example of heart rate data recorded in the wearable device 10. [Figure 5] 10 is an example of operation history data. [Figure 6] 1 is an example of video data. [Figure 7] 10 is an example of data generated as a result of executing a process (synchronization process) for associating the heart rate with the playback position of a video. [Figure 8] 10 is an example of data generated as a result of executing a process (synchronization process) that associates each item in the operation history with the playback position of the video. [Figure 9] 10 is an example of an inquiry screen. [Figure 10] 10 is a flowchart of an example of the operation of the software product inquiry making device 1. [Figure 11] 10 is a flowchart of a synchronization process. [Figure 12] FIG. 10 is a diagram illustrating a flow of data synchronization. [Figure 13] 1 is a diagram illustrating an example of a hardware configuration of a software product inquiry creation device 1. FIG. DETAILED DESCRIPTION OF THE INVENTION

[0012] (Embodiment 1) First, an example of the configuration of a software product inquiry creation device 1 according to the first embodiment will be described with reference to FIG.

[0013] FIG. 1 is a schematic diagram of a software product inquiry creation device 1. As shown in FIG.

[0014] As shown in FIG. 1, the device includes a video acquisition unit 52 that acquires a video (video data) recorded from the operation screen of a software product that has the function of displaying an operation screen whose display content changes in response to user operations, a heart rate acquisition unit 53 that acquires the user's heart rate (heart rate data) measured within a predetermined period during which the operation is performed, an inquiry creation unit 59 that creates an inquiry screen including the video and heart rate, and a communication unit 60 that transmits the inquiry screen to the respondent.

[0015] Next, an example of the operation of the software product inquiry making device 1 will be described.

[0016] FIG. 2 is a flowchart showing an example of the operation of the software product inquiry making device 1.

[0017] First, the video acquisition unit 52 acquires a video (video data) that records an operation screen of a software product that has a function of displaying an operation screen whose display content changes in response to user operations (step S1). Next, the heart rate acquisition unit 53 acquires the user's heart rate (heart rate data) measured within a predetermined period during which the operation is performed (step S2). Next, the inquiry creation unit 59 creates an inquiry screen that includes the video and the heart rate (step S3). Next, the communication unit 60 transmits the inquiry screen to the respondent.

[0018] As described above, according to the first embodiment, the content of technical inquiries about software products can be clarified.

[0019] This is because the respondent can understand at a glance which part the inquiry is about by looking at the video and heart rate on the inquiry screen (see FIG. 9).

[0020] (Embodiment 2) Next, a description will be given of embodiment 2. Embodiment 2 is an embodiment that embodies embodiment 1. Hereinafter, a software product inquiry making system 100 including a software product inquiry making device 1 will be described in detail as embodiment 2 of the present invention.

[0021] FIG. 3 is a block diagram showing the configuration of a software product inquiry making system 100 including a software product inquiry making device 1 according to the second embodiment.

[0022] As shown in FIG. 3, the software product inquiry creation system 100 includes a software product inquiry creation device 1, a wearable terminal 10, an input unit 20, and a display unit 30.

[0023] First, an overview of the software product inquiry creation device 1 will be described.

[0024] The software product inquiry creation device 1 creates an inquiry screen A (see FIG. 9) and transmits the created inquiry screen A to the respondent. The inquiry screen A (see FIG. 9) includes a video recording of an operation screen whose display content changes in response to operations by the inquirer (hereinafter referred to as the user), the user's heart rate measured while the user was operating, an operation history including at least one of an item representing the user's operation and an item representing an error message, and supplementary information regarding the inquiry entered by the user. Note that at least one of the operation history and the supplementary information may be omitted.

[0025] The reason for using heart rate here is to focus on user stress. That is, when a user encounters a problem they cannot solve while operating a software product, they feel stressed and their heart rate rises. Therefore, the time when the heart rate measured exceeds a threshold can be identified as the time when the problem occurred. Furthermore, by using the synchronization process described below to link the heart rate (heart rate data) with the video (video data) (by associating the heart rate with the video playback position), the video can be played from the playback position corresponding to the time when the problem occurred (the time when the heart rate measured exceeded the threshold). This allows the respondent to understand at a glance which part of the problem the question is about by looking at the video and heart rate on inquiry screen A (see Figure 9). In other words, the content of the technical inquiry about the software product can be clarified.

[0026] Furthermore, by combining the operation history (operation history data) and the video (video data) through the synchronization process described below (by associating each item in the operation history with the playback position of the video), when the video is played, it is possible to display the item in the operation history that corresponds to the playback position of the video. Also, by viewing the operation history and supplementary information in addition to the video and heart rate on inquiry screen A (see Figure 9), the respondent can understand the inquiry in more detail.

[0027] Next, the software product inquiry making device 1 will be described in detail.

[0028] The software product inquiry creation device 1 is, for example, an information processing device such as a personal computer. As shown in Fig. 3, a wearable terminal 10, an input unit 20, and a display unit 30 are connected to the software product inquiry creation device 1. In addition, a software product 40 and inquiry creation software 50 are installed in the software product inquiry creation device 1.

[0029] The wearable terminal 10 is, for example, a wristwatch-type wearable terminal worn by a user. The wearable terminal 10 has functions such as measuring the heart rate of the user wearing it, recording heart rate data including the measured heart rate (for example, recording as CSV data), and communicating with the software product inquiry creation device 1 (inquiry creation software 50). FIG. 4 shows an example of heart rate data recorded in the wearable terminal 10. The heart rate data is recorded, for example, in a storage device (not shown) built into the wearable terminal 10. As shown in FIG. 4, the heart rate data includes the fields "date and time" and "heart rate per minute." The time when the heart rate was measured is recorded in the "date and time." The heart rate measured in one minute is recorded in the "heart rate per minute."

[0030] The input unit 20 is an input device such as a keyboard or a mouse. As will be described later, the input unit 20 is used to input thresholds and supplementary information related to inquiries. An inquiry refers to a technical inquiry about a software product (an inquiry to people involved in the development of the software product, such as an inquiry about a fault or how the product works. This does not include inquiries that can be resolved by a manual or FAQ). A supplementary information refers to a minimum explanation related to the inquiry (for example, I don't understand XX).

[0031] The display unit 30 is, for example, a display device such as a liquid crystal display, etc. As will be described later, the display unit 30 displays an operation screen (GUI) or the like whose display content changes in response to a user operation.

[0032] The software product 40 is software purchased by a user. The software product 40 has functions such as displaying an operation screen (GUI) or the like on the display unit 30, the display contents of which change in response to user operations, and recording (e.g., recording as text data) an operation history (operation history data) including at least one of items representing user operations and items representing error messages. The operation history data is recorded, for example, in a storage device (not shown) built into the software product inquiry creation device 1. FIG. 5 shows an example of the operation history data. As shown in FIG. 5, the operation history data includes the following items: "Type," "Date and Time," and "Operation Information, Error Message." The "Type" field records the type of operation information and error message. The "Date and Time" field records the time when the user operation was performed or the time when an error occurred. The "Operation Information, Error Message" field records the specific content of the user operation and the specific content of the error message.

[0033] The query creation software 50 includes a recording unit 51, a video acquisition unit 52, a heart rate acquisition unit 53, an operation history acquisition unit 54, a supplementary information acquisition unit 55, a combination unit 56, a threshold setting unit 57, a threshold memory unit 58, a query creation unit 59, and a communication unit 60 (transmission / reception unit).

[0034] The recording unit 51 has a function of recording, as a video, an operation screen (GUI) whose display content changes in response to user operations. The video recorded by the recording unit 51 is stored as a video file in a storage device (not shown) built into the software product inquiry creation device 1. The video (video file) includes video data. FIG. 6 is an example of video data. As shown in FIG. 6, the video data includes the items "date and time" and "mark on seek bar." The time when the video was recorded is recorded in "date and time." The presence or absence of a seek bar is recorded in "mark on seek bar." In the initial state, "none" is recorded in the "mark on seek bar" field.

[0035] The video acquisition unit 52 acquires the video (video data; see FIG. 6) recorded by the recording unit 51. The heart rate acquisition unit 53 acquires heart rate data (see FIG. 4) from the wearable device 10. The operation history acquisition unit 54 acquires operation history data (see FIG. 5) from the software product 40. The supplementary information acquisition unit 55 acquires supplementary information regarding the inquiry input via the input unit 20.

[0036] The combining unit 56 executes a synchronization process to combine the video (video data) acquired by the video acquiring unit 52, the heart rate (heart rate data) acquired by the heart rate acquiring unit 53, and the operation history (operation history data) acquired by the operation history acquiring unit 54. Specifically, as the synchronization process, the combining unit 56 executes a process to associate the heart rate with the playback position of the video. Fig. 7 shows an example of data generated as a result of executing the process (synchronization process) to associate the heart rate with the playback position of the video.

[0037] Furthermore, the combining unit 56 executes a process of associating each item in the operation history with the playback position of the video as a synchronization process. Fig. 8 shows an example of data generated as a result of executing a process (synchronization process) of associating each item in the operation history with the playback position of the video.

[0038] The threshold setting unit 57 stores (sets) the threshold input from the input unit 20 in the threshold storage unit 58. The threshold is a threshold for determining that an abnormality has occurred (that the user is feeling stress) when operating the software product 40, and is determined by the user in consideration of the heart rate (normal value) at rest.

[0039] The query creation unit 59 creates a query screen. Fig. 9 is an example of the query screen. As shown in Fig. 9, the query screen A includes an operation history display area A1, a supplementary information display area A2, a video display area A3, and a heart rate display area A4. The query screen A is written in, for example, HTML.

[0040] The operation history display area A1 displays the operation history data acquired by the operation history acquisition unit 54. Specifically, when a video is played, an item in the operation history data corresponding to the playback position (playback time) of the video is displayed. The item in the operation history data corresponding to the playback position (playback time) of the video can be identified by referring to the data in FIG. 8. For example, in the case of FIG. 8, when the playback position (playback time) of the video becomes 14:10:12, the item "Software startup" corresponding to 14:10:12 is displayed in the operation history display area A1. Similarly, when the playback position (playback time) of the video becomes 14:47:17, the item (error message) "Error at ****. **** Service startup failed" corresponding to 14:47:17 is displayed in the operation history display area A1.

[0041] The supplementary information display area A2 displays supplementary information acquired by the supplementary information acquisition unit 55. The supplementary information is supplementary information related to the inquiry, such as the time of the video that is the subject of the inquiry and a supplementary sentence.

[0042] In the video display area A3, video M recorded by the recording unit 51 and seek bars SB (SB1 to SB3) associated with specific times are displayed. The specific times are, for example, the times when a heart rate exceeding a threshold value is measured. The seek bars are displayed based on the data in FIG. 8. The specific times can be specified by referring to the data in FIG. 8. For example, in the case of FIG. 8, the specific times are 14:48:00, the time when a heart rate 110 exceeding a threshold value (e.g., 95) is measured, and 14:49:00, the time when a heart rate 100 exceeding a threshold value (e.g., 95) is measured. The specific times may also be times input by the user, as described below.

[0043] When a seek bar SB (SB1 to SB3) is selected (e.g., clicked) by the user (or respondent), the video M is played from the playback position corresponding to the specific time associated with the seek bar (e.g., 14:48:00, the time when the heart rate 110 was measured). This allows the respondent to understand at a glance what time the problem occurred. The playback position corresponding to the specific time associated with the seek bar (e.g., 14:48:00, the time when the heart rate 110 was measured) can be identified by referring to the data in FIG. 8.

[0044] The heart rate display area A4 displays a graph G showing the time variation of the heart rate acquired by the heart rate acquisition unit 53 and a display L showing the threshold value set by the threshold setting unit 57. The graph G is displayed based on the data in FIG. 8. By looking at the graph G and the display L (e.g., a horizontal line) showing the threshold value set by the threshold setting unit 57, the respondent can ascertain the time when the problem occurred (the time when the measured heart rate exceeded the threshold value).

[0045] The communication unit 60 (transmission / reception unit) transmits the inquiry screen A to the respondent (for example, by email).

[0046] Next, an example of the operation of the software product inquiry creation device 1 configured as described above will be described. Hereinafter, it is assumed that the user is wearing the wearable terminal 10, that the user's heart rate is measured while the user is operating the software product 40, and that heart rate data including the measured heart rate (see FIG. 4) is sequentially recorded in a storage device (not shown) built into the wearable terminal 10. It is also assumed that 95 is set as the threshold value in the threshold value storage unit 58.

[0047] FIG. 10 is a flowchart showing an example of the operation of the software product inquiry making device 1.

[0048] First, the user U starts the software product 40 (step S10), which causes the software product 40 to display an operation screen (GUI) on the display unit 30, the display contents of which change in response to the user's operation (step S11).

[0049] Next, the user U starts the inquiry generation software 50 (step S12) and instructs it to start recording (step S13), which causes the inquiry generation software 50 (recording unit 51) to start recording the operation screen (GUI) displayed in step S11 (step S14).

[0050] Next, the user U starts operating the software product 40 (operation screen (GUI)) (step S15). The software product 40 records (for example, as text data) an operation history (operation history data; see FIG. 5) including at least one of an item representing the user's operation and an item representing an error message (step S16). During this time, the query creation software 50 (recording unit 51) continues recording the operation screen (including the user's operation on the operation screen).

[0051] Next, it is assumed that a problem occurs that the user U cannot solve by himself while operating the software product 40 (operation screen (GUI)) (step S17; Yes).

[0052] Next, the user U instructs the inquiry creation software 50 to display an inquiry screen (step S18), which generates a moving image (moving image data) that records the operation screen (GUI).

[0053] Next, the query generation software 50 (combining unit 56) executes synchronization processing (step S19).

[0054] Fig. 11 is a flowchart of the synchronization process, and Fig. 12 is a diagram showing the flow of data synchronization.

[0055] 11, first, video data (see FIG. 6) and heart rate data (see FIG. 4) are acquired (step S191). The video data is acquired by the video acquisition unit 52. Meanwhile, the heart rate data is acquired from the wearable device 10 by the heart rate acquisition unit 53.

[0056] Next, the combining unit 56 executes a synchronization process to combine the video data and heart rate data acquired in step S191 (step S192). Specifically, as the synchronization process, the combining unit 56 executes a process to associate the heart rate with the playback position of the video. As a result, data obtained by synchronizing the video data and heart rate data (data in which the heart rate is associated with the playback position of the video) is generated, as shown in FIGS. 7 and 12.

[0057] Next, if the heart rate exceeds the threshold (step S193: Yes), a seek bar is associated with the playback position of the video associated with the heart rate exceeding the threshold (step S194). Specifically, as shown in Fig. 7, "Yes" is set in the "Mark on Seek Bar" field corresponding to the playback position (14:48:00) associated with the heart rate (110) exceeding the threshold (95 in this case). Similarly, "Yes" is set in the "Mark on Seek Bar" field corresponding to the playback position (14:49:00) associated with the heart rate (100) exceeding the threshold (95 in this case). Furthermore, "No" is set in the other "Mark on Seek Bar" fields.

[0058] Next, the operation history data (see FIG. 5) is acquired (step S195). The operation history data is acquired from the software product 40 by the operation history acquisition unit .

[0059] Next, the combining unit 56 executes a synchronization process to combine the video data acquired in step S191 with the operation history data acquired in step S195 (step S196). Specifically, as the synchronization process, the combining unit 56 executes a process to associate each item in the operation history with a playback position of the video. As a result, as shown in FIGS. 8 and 12, data obtained by synchronizing the video data and heart rate data (data obtaining a correspondence between the heart rate and the playback position of the video) with the operation history data (data obtaining a correspondence between each item in the operation history and the playback position of the video) is generated. In this case, "Yes" is set in the "Mark on Seek Bar" column (see the "Mark on Seek Bar" column corresponding to the playback position (14:47:17) in Figure 8) immediately before the "Mark on Seek Bar" column (see the "Mark on Seek Bar" column corresponding to the playback position (14:48:00) in Figure 8) where the first heart rate exceeding the threshold value (95 in this case) appears and "Yes" is set.

[0060] On the other hand, if the heart rate does not exceed the threshold value in step S193 (step S193: No), the user inputs the time of the inquiry location (step S196). At that time, the user U checks the time of the inquiry location while watching the video M, etc. on the inquiry screen A, and inputs the checked time. This time of the inquiry location is input via the input unit 20. Next, the seek bar is associated with the playback position of the video corresponding to this input time. That is, as above, "Yes" is set in the "Mark on Seek Bar" field corresponding to the playback position of the video corresponding to this input time. Furthermore, "No" is set in the other "Mark on Seek Bar" fields.

[0061] 10, the inquiry screen A (see FIG. 9) is displayed (step S20). The inquiry screen A is displayed on the display unit 30.

[0062] Next, the user U inputs supplementary information (step S21). At that time, the user U creates supplementary information (text for the inquiry) while viewing the inquiry screen A (for example, video M and graph G showing changes in heart rate over time). The supplementary information is input via the input unit 20. The supplementary information input in step S21 is acquired by the supplementary information acquisition unit 55 and displayed in the supplementary information display area A2 (see FIG. 9).

[0063] After completing the input of the supplementary information, the user instructs the inquiry generation software 50 to send an inquiry (step S22). As a result, the inquiry generation software 50 (communication unit 60) transmits an inquiry screen A (see FIGS. 9 and 12) to the respondent (step S23). Specifically, HTML data (including the video (video file), the data shown in FIG. 8, and the supplementary information input in step S21) for displaying the inquiry screen (see FIG. 9) is transmitted as the inquiry screen A. The respondent can understand the content of the inquiry by displaying the inquiry screen A (see FIG. 9) based on the HTML data transmitted from the software product inquiry device 1. At this time, by viewing the video and heart rate displayed on the inquiry screen A (see FIG. 9), the respondent can understand at a glance which part the inquiry is about. In other words, the technical content of the inquiry about the software product can be clarified. Furthermore, the respondent can understand the content of the inquiry in more detail by viewing the operation history and supplementary information in addition to the video and heart rate displayed on the inquiry screen A (see FIG. 9).

[0064] As described above, according to the second embodiment, the content of technical inquiries about software products can be clarified.

[0065] This is because, first, by linking the heart rate (heart rate data) with the video (video data) (by associating the heart rate with the playback position of the video), the video can be played from the playback position corresponding to the time the problem occurred (the time when the heart rate was measured to exceed the threshold), and second, by looking at the video and heart rate on inquiry screen A (see Figure 9), the respondent can understand at a glance which part the inquiry is directed to.

[0066] Furthermore, according to the second embodiment, by combining the operation history (operation history data) with the video (video data) (by associating each item in the operation history with the playback position of the video), when the video is played, it is possible to display the item in the operation history that corresponds to the playback position of the video.

[0067] Furthermore, according to the second embodiment, the respondent can understand the details of the inquiry by viewing the operation history and supplementary information in addition to the video and heart rate on the inquiry screen A (see FIG. 9).

[0068] Furthermore, according to the second embodiment, a video recording of an operation screen whose display content changes in response to user operations, the user's heart rate measured during the period in which the user is operating, an operation history including at least one of items representing the user's operations and items representing error messages, and supplementary information regarding the inquiry entered by the user are displayed on a single inquiry screen A, so that the respondent can grasp the user's problem (situation) at a glance. Also, problems that the user cannot solve by himself / herself can be shared more easily and accurately between the user (inquirer) and the respondent.

[0069] Moreover, the second embodiment has the following advantages.

[0070] Generally, when a user (inquirer) makes a technical inquiry about a software product, the inquiry text written by the user (inquirer) about a problem that the user cannot solve by himself or herself, as well as text information such as the software product's operation history, are sent to the inquiry desk. The respondent must understand the content of the inquiry and create a response solely based on the text information, such as the inquiry text, sent to the inquiry desk.

[0071] However, when only text information is exchanged, the following problems arise for the user (inquirer) and the respondent.

[0072] First, users (inquirers) need to think about how to write their inquiries in order to convey them more accurately. Also, if users (inquirers) are not familiar with the product, they may lack the information necessary for their inquiries, and may not be able to convey what they need to say to the respondent (hereinafter referred to as the first problem).

[0073] Second, respondents are required to think about what the inquirer really wants to know from the text information, which may contain inaccuracies, or to confirm with the inquirer (hereinafter referred to as the second problem).

[0074] In contrast to this, according to the second embodiment, the user only needs to input supplementary information (minimal explanation of the inquiry), thereby solving the first problem.

[0075] Furthermore, according to the second embodiment, the respondent can grasp the problem (situation) of the user (inquirer) at a glance from the inquiry screen A. This solves the second problem described above.

[0076] Next, a modified example will be described.

[0077] In the second embodiment, an example was described in which the user issues a query transmission instruction to the query generation software 50 (step S22), causing the user (inquirer) heart rate data to be transmitted to the respondent (step S23). However, this is not limiting. For example, the user (inquirer) heart rate data may be continuously and automatically transmitted to the respondent. Then, when the user (inquirer)'s heart rate exceeds a threshold while operating a software product, data on the user's (inquirer's) operation location may be transmitted to the respondent. This allows the respondent to prepare and generate a response before an inquiry arrives.

[0078] (Other embodiments) The software product inquiry creation device 1 described in the above embodiment may have the following hardware configuration: FIG. 13 is a diagram showing an example of the hardware configuration of the software product inquiry creation device 1.

[0079] 13, the software product query creation device 1 includes a processor 201 and a memory 202. The processor 201 reads and executes software (the software product 40, the query creation software 50) from the memory 202, thereby performing the processing of the software product query creation device 1 described using the flowcharts in the above-described embodiment. The processor 201 may be, for example, a microprocessor, an MPU (Micro Processing Unit), or a CPU (Central Processing Unit). The processor 201 may include multiple processors.

[0080] The processor 201 executes software (query creation software 50) read from memory 202, such as RAM, to function as a recording unit 51, a video acquisition unit 52, a heart rate acquisition unit 53, an operation history acquisition unit 54, a supplementary information acquisition unit 55, a combining unit 56, a threshold setting unit 57, a threshold storage unit 58, a query creation unit 59, and a communication unit 60 (transmitter / receiver). These functions may be implemented in a single personal computer or server, or may be distributed across multiple servers. Even if the functions are distributed across multiple servers, the processes of the above flowcharts can be realized by the multiple servers communicating with each other via a communication line (e.g., the Internet). Note that some or all of these functions may be realized by hardware.

[0081] The memory 202 is configured by a combination of volatile memory and non-volatile memory. The memory 202 may include storage located remotely from the processor 201. In this case, the processor 201 may access the memory 202 via an I / O (Input / Output) interface (not shown).

[0082] 13, the memory 202 is used to store a group of software modules. The processor 201 reads and executes these software modules from the memory 202, thereby performing the processing of the software product inquiry creation device 1 described in the above embodiment.

[0083] As explained using FIG. 13, each of the one or more processors included in the software product query creation device 1 executes one or more programs including a set of instructions for causing a computer to perform the algorithm explained using the drawing.

[0084] In the above examples, the program includes instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more functions described in the embodiments. The program may be stored on a non-transitory computer-readable medium or a tangible storage medium. By way of example and not limitation, computer-readable medium or tangible storage medium includes random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD-ROM, digital versatile disc (DVD), Blu-ray® disc or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device. The program may also be transmitted on a transitory computer-readable medium or communication medium. By way of example and not limitation, transitory computer-readable medium or communication medium includes electrical, optical, acoustic, or other forms of propagated signals.

[0085] The present invention is not limited to the above-described embodiment, and can be appropriately modified without departing from the spirit of the invention. Furthermore, the present invention may be implemented by appropriately combining the respective embodiments. [Explanation of symbols]

[0086] 1...Inquiry creation device 10...Wearable devices 20...Input section 30…Display section 40...Software products 50...Inquiry creation software 51...Recording section 52...Video acquisition section 53...Heart rate acquisition unit 54...Operation history acquisition unit 55…Supplementary information acquisition department 56...Joining part 57...Threshold setting unit 58...Threshold memory unit 59...Inquiry Creation Department 60…Communications Department 100...Inquiry creation system 201...Processor 202...Memory A...Inquiry screen A1: Operation history display area A2…Supplementary information display area A3: Video display area A4: Heart rate display area G...Graph L…display M...Video SB (SB1~SB3)...Seek bar U...User

Claims

1. a video acquisition unit that acquires a video of a software product having a function of displaying an operation screen whose display content changes in response to a user's operation; a heart rate acquisition unit that acquires the user's heart rate measured within a predetermined period during which the operation is performed; an inquiry creation unit that creates an inquiry screen including the video and the heart rate; a communication unit that transmits the inquiry screen to a respondent.

2. an operation history acquisition unit that acquires an operation history including at least one of an item representing an operation by the user and an item representing an error message; 2. The software product inquiry making device according to claim 1, wherein the inquiry screen further includes the operation history.

3. a combining unit that performs a synchronization process to combine the video, the heart rate, and the operation history; The software product inquiry creation device according to claim 2, wherein the combining unit executes, as the synchronization processing, a process of associating the heart rate with the playback position of the video, and generating data that associates each item in the operation history with the playback position of the video.

4. 4. The software product inquiry making device according to claim 3, wherein when the video is played, an item in the operation history corresponding to the playback position of the video is displayed.

5. a supplementary information acquisition unit that acquires supplementary information regarding the inquiry input by the user; 5. The software product inquiry making device according to claim 1, wherein the inquiry screen further includes the supplementary information.

6. the inquiry screen further includes a seek bar associated with a specific time; 6. A software product inquiry creation device according to claim 1, wherein when the seek bar is selected by the user's operation, the video is played from a playback position corresponding to the specific time associated with the seek bar.

7. 7. The software product inquiry generating device according to claim 6, wherein the specific time is a time when a heart rate exceeding a threshold value is measured.

8. 8. The software product inquiry making device according to claim 7, wherein the inquiry screen includes a graph showing the change in the heart rate over time and a display showing the threshold value.

9. a video acquisition step of acquiring a video of a software product having a function of displaying an operation screen whose display content changes in response to a user's operation; a heart rate acquisition step of acquiring the user's heart rate measured within a predetermined period during which the operation is performed; an inquiry creating step of creating an inquiry screen including the video and the heart rate; a communication step of transmitting the inquiry screen to a respondent.

10. A process of acquiring a video recording of an operation screen of a software product having a function of displaying an operation screen whose display content changes in response to a user's operation; A process of acquiring the user's heart rate measured within a predetermined period during which the operation is performed; a process of creating an inquiry screen including the video and the heart rate; a process of transmitting the inquiry screen to a respondent; A program that causes a computer to execute the following.

Images