Software product experience monitoring method, device and related components based on physiological parameters

Abstract

The present invention discloses a software product experience monitoring method, device and related components based on physiological parameters. The method includes obtaining the user's test time, eye movement data, facial expression data and operation behavior data; judging whether the test task is completed; if the test task is completed, continuing to judge whether the test time exceeds the test time threshold; if the test time does not exceed the test time threshold, the test task is judged to be successful and ended, otherwise the test task is judged to be failed, and the facial expression data is input into the expression analysis module to obtain the expression judgment result; judging whether the eye movement data is abnormal, if the eye movement data is abnormal, the eye movement data is combined with the expression judgment result and the experience fault report is output. By analyzing the real-time data of the user in the process of executing the test task, the method can accurately judge the user's emotions and operational feedback generated in the process of using the software, and then provide effective reference information for the development team of the software product.

Description

Technical Field

[0001] The present invention relates to the field of computer vision, and in particular to a method, device and related components for monitoring software product experience based on physiological parameters. Background Art

[0002] At present, the user experience of software products refers to the overall physiological and psychological feelings of users in the process of using software products to achieve their desired goals. The user experience of software products has an important impact on the user's work efficiency, user acceptance of software products and purchase decisions.

[0003] Currently, the evaluation of software product user experience is mainly completed through some subjective scales. This method invites a certain number of typical users to use the product and then fill out the relevant user experience scale to obtain the user's subjective impression of the software product experience. Later, a large amount of data analysis is required to infer the experience barriers of the software product. This method is labor-intensive and the data obtained is not accurate, which cannot help researchers accurately locate the problems of the software product. Summary of the invention

[0004] The purpose of the present invention is to provide a method, device and related components for monitoring software product experience based on physiological parameters, aiming to solve the problem of inaccurate evaluation of existing software products.

[0005] In order to solve the above technical problems, the object of the present invention is to achieve the following technical solutions: to provide a software product experience monitoring method based on physiological parameters, which comprises:

[0006] Obtain the test duration, eye movement data, facial expression data, and operation behavior data of the user during the test task execution;

[0007] Based on the operation behavior data, determining whether the test task is completed;

[0008] If the test task is completed, continue to determine whether the test duration exceeds the test duration threshold; if the test duration does not exceed the test duration threshold, determine that the test task is successful and end; if the test duration exceeds the test duration threshold, determine that the test task has failed, and input the facial expression data into the expression analysis module to obtain an expression judgment result;

[0009] Determine whether the eye movement data is abnormal. If the eye movement data is abnormal, combine the eye movement data with the expression judgment result and output an experience fault report.

[0010] In addition, the technical problem to be solved by the present invention is to provide a software product experience monitoring device based on physiological parameters, which includes:

[0011] An acquisition unit, used to acquire the test duration, eye movement data, facial expression data, and operation behavior data of the user during the test task execution;

[0012] A first judging unit, configured to judge whether the test task is completed based on the operation behavior data;

[0013] A second judgment unit is used to, if the test task is completed, continue to judge whether the test duration exceeds the test duration threshold; if the test duration does not exceed the test duration threshold, determine that the test task is successful and end; if the test duration exceeds the test duration threshold, determine that the test task fails, and input the facial expression data into the expression analysis module to obtain an expression judgment result;

[0014] The output unit is used to determine whether the eye movement data is abnormal. If the eye movement data is abnormal, the eye movement data is combined with the expression judgment result and an experience fault report is output.

[0015] In addition, an embodiment of the present invention provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the software product experience monitoring method based on physiological parameters described in the first aspect above is implemented.

[0016] In addition, an embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the processor executes the software product experience monitoring method based on physiological parameters described in the first aspect above.

[0017] The embodiment of the present invention discloses a software product experience monitoring method, device and related components based on physiological parameters, wherein the method includes: obtaining the test time, eye movement data, facial expression data and operation behavior data of the user in the process of executing the test task; judging whether the test task is completed based on the operation behavior data; if the test task is completed, then continue to judge whether the test time exceeds the test time threshold; if the test time does not exceed the test time threshold, then judge the test task to be successful and end; if the test time exceeds the test time threshold, then judge the test task to fail, and input the facial expression data into the expression analysis module to obtain the expression judgment result; judge whether the eye movement data is abnormal, if the eye movement data is abnormal, then combine the eye movement data with the expression judgment result and output the experience fault report. By analyzing the test time, eye movement data, facial expression data and operation behavior data of the user in the process of executing the test task, the method can accurately judge the emotions and operation feedback generated by the user in the process of using the software, and then provide the modification reference message for the development team of the software product. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying any creative work.

[0019] Figure 1 A schematic diagram of a process flow of a method for monitoring software product experience based on physiological parameters provided by an embodiment of the present invention;

[0020] Figure 2 A schematic diagram of the structure of a method for monitoring software product experience based on physiological parameters provided by an embodiment of the present invention;

[0021] Figure 3 A schematic diagram of a substructure of a method for monitoring software product experience based on physiological parameters provided by an embodiment of the present invention;

[0022] Figure 4 A schematic block diagram of a software product experience monitoring device based on physiological parameters provided by an embodiment of the present invention;

[0023] Figure 5 A schematic block diagram of a computer device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0024] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0025] It should be understood that when used in this specification and the appended claims, the terms "include" and "comprises" indicate the presence of described features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.

[0026] It should also be understood that the terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in the specification of the present invention and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.

[0027] It should be further understood that the term "and / or" used in the present description and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0028] See also Figure 1 , Figure 1 A schematic diagram of a process flow of a method for monitoring software product experience based on physiological parameters provided by an embodiment of the present invention;

[0029] like Figure 1 As shown, the method includes steps S101 to S104.

[0030] S101, obtaining the test duration, eye movement data, facial expression data, and operation behavior data of the user during the test task execution;

[0031] S102, judging whether the test task is completed based on the operation behavior data;

[0032] S103, if the test task is completed, continue to determine whether the test duration exceeds the test duration threshold; if the test duration does not exceed the test duration threshold, determine that the test task is successful and end; if the test duration exceeds the test duration threshold, determine that the test task fails, and input the facial expression data into the expression analysis module to obtain an expression judgment result;

[0033] S104, determining whether the eye movement data is abnormal; if the eye movement data is abnormal, combining the eye movement data with the expression judgment result and outputting an experience fault report.

[0034] In this embodiment, the product performance to be tested is first defined, and the process of users using this function to complete a specific goal is defined as a test task; the interface elements that the user needs to operate in the process of completing the test task are defined, such as buttons, drop-down menus, dialog boxes that need to be filled in, etc., and the operation process for these interface elements, such as first clicking a button, then filling in a dialog box, and then clicking another button, etc.; the starting point and end point of the test task are defined, for example, clicking on a certain interface element represents the start of the test task, and clicking on another interface element represents the end of the test task; the maximum acceptable time limit for the test task is defined. It should be noted that the acceptable maximum time limit can be obtained by collecting data on the time it takes users who frequently use software-related functions to complete test tasks and analyzing the time it takes.

[0035] After completing the above preparations, start the software to monitor the user experience on the software running platform, and let the user start the test task according to the task flow, obtain the user's eye movement data, facial expression data, and operation behavior data during the test task, and record the test time spent by the user in the entire test task.

[0036] It should be noted that the software product running platform is the operating system environment and hardware system that supports the operation of the software to be monitored, such as a personal computer or smart phone; this application integrates and analyzes eye movement data, facial expression data, and operational behavior data to determine whether the pages or operation items encountered by users when completing specific test tasks have caused obstacles to the use process. Based on the judgment rules and results, the experience obstacle page is reported to the experience researchers, which can accurately judge the emotions and operational feedback generated by users during the use of the software, and then provide modification reference messages to the software product development team.

[0037] In a specific embodiment, the step S101 includes the following steps:

[0038] S10, using an eye tracker to obtain the user's gaze point, eye movement trajectory, and gaze point dwell time to obtain eye movement data;

[0039] S11, using a camera to capture images of the user's eyes, mouth, and forehead area to obtain facial expression data;

[0040] S12: Monitor the user's mouse click instructions, keyboard input instructions, and mouse hovering time to obtain operation behavior data.

[0041] It should be noted that before the test task begins, the eye tracker needs to be focused first so that the user does not need to spend time operating the eye tracker after putting it on, thereby ensuring the effectiveness of the test time; among them, the mouse hover time refers to the time spent when the mouse is in an idle state.

[0042] The eye tracker and the camera installed facing the subject's face are used to collect the subject's eye movement physiological data and facial expression data when using the software product. The eye tracker and the camera are installed in the same operating system environment as the software to be monitored. After the software to be monitored is started, the user's operation behavior data is collected in the system background. By integrating and analyzing the experience data from the eye tracker, camera, and monitoring system, it is determined whether the page or operation item encountered by the user when completing a specific test task has caused obstacles to the use process. Based on the judgment rules and results, the experience obstacle page is reported to the experience researcher.

[0043] Combination Figure 2 In a specific embodiment, the step S102 includes the following steps:

[0044] S20, obtaining the current mouse hovering time, and determining whether the mouse hovering time exceeds the no-operation time threshold, if the mouse hovering time exceeds the no-operation time threshold, executing step S21, if the mouse hovering time does not exceed the no-operation time threshold, executing step S22;

[0045] S21, recording the current operation page, the operation behavior of the previous operation object, and the operation behavior of the predefined next operation object, and outputting an experience fault report, wherein the operation objects include a mouse and a keyboard;

[0046] S22. Continue to determine whether the current operation behavior is the last operation behavior in the test task. If the current operation behavior is the last operation behavior in the test task, determine that the test task is completed. If the current operation behavior is not the last operation behavior in the test task, determine that the test task is not completed.

[0047] In the actual software experience process, the user performs software testing according to the test task flow. If during the test task process, the user feels that the operation of this step is difficult, or cannot understand the specific content of the operation step, the mouse will be in an inoperative state for a long time, and the mouse hovering time will exceed the inoperative time threshold. Therefore, it is necessary to record the current user operation interface and the operation behavior of the previous operation object and the next operation behavior that needs to be operated. For example, if the user currently needs to execute command A, but the user does not execute it within the specified time range, then the screen where the software stays when executing command A is recorded, and the operation behavior before executing command A is recorded, such as clicking the "Start" button, and the next operation behavior that needs to be operated, such as clicking the "End" button to end command A. This part of the process with poor user experience is output as an experience failure report, which is convenient for software developers to understand the user's experience failure situation in a timely manner.

[0048] If the current operation behavior is the last operation behavior in the test task, it means that the user will not click the mouse again, and the mouse hovering time will definitely exceed the no-operation time threshold, and then it can be determined whether the test task is completed.

[0049] In a specific embodiment, before step S104, the following steps are included:

[0050] S30, if the expression judgment result is a negative emotion, execute step S31, if the expression judgment result is a non-negative emotion, execute step S33;

[0051] S31, obtaining the duration of the negative emotion, and determining whether the duration of the negative emotion exceeds the negative emotion time threshold, if the duration of the negative emotion exceeds the negative emotion time threshold, executing step S32, if the duration of the negative emotion does not exceed the negative emotion time threshold, executing step S33;

[0052] S32, backtracking and outputting an experience fault report consisting of the user's operation behavior data and eye movement data within the duration of the negative emotion;

[0053] S33, retracing all eye movement data, and determining whether the eye movement data is abnormal.

[0054] It should be noted that the present application does not make specific limitations on the expression analysis module; if it is determined that the user has negative emotions, and the duration of the negative emotions exceeds the negative emotion time threshold, it means that the user's experience with the software within this period of time is very bad, so it is necessary to output the experience failure report at that time and inform the software developer in time. If the user has negative emotions, but the duration of the negative emotions does not exceed the negative emotion time threshold, it means that the user's negative emotions at this stage have been predicted in advance. For example, users who initially experience the software may have negative emotions such as doubts when encountering new things during the operation process, and they can be accepted as long as they are within a reasonable negative emotion time threshold.

[0055] In order to more clearly understand the user's software experience process, this application not only uses facial expression recognition, but also determines whether there are abnormal eye movement trajectories. Figure 2 In a specific embodiment, the step S104 includes the following steps:

[0056] S40, retracing the eye movement data to determine whether there is an abnormal eye movement trajectory; if there is an abnormal eye movement trajectory, executing step S41, if there is no abnormal eye movement trajectory, then ending.

[0057] S41, obtaining the duration of the abnormal eye movement trajectory, obtaining the operation behavior data within the duration of the abnormal eye movement trajectory, and outputting an experience fault report.

[0058] In this embodiment, if the eye movement trajectory in the eye movement data is abnormal, a corresponding experience fault report is output for reference by software developers.

[0059] Combination Figure 3 In a specific embodiment, the step S40 includes the following steps:

[0060] S50, determining whether the number of repetitions of the user's gaze point in the two gaze focus marks exceeds the repetition number threshold, if the number of repetitions of the user's gaze point in the two gaze focus marks exceeds the repetition number threshold, executing step S51, if the number of repetitions of the user's gaze point in the two gaze focus marks does not exceed the repetition number threshold, executing step S52, wherein the two gaze focus marks are two non-overlapping screen areas;

[0061] S51, determining that the eye movement trajectory is abnormal;

[0062] S52, determining whether the user's gaze point repeatedly moves in sequence across multiple gaze focus marks, if the user's gaze point repeatedly moves in sequence across multiple gaze focus marks, returning to step S51, if the user's gaze point does not repeatedly move in sequence across multiple gaze focus marks, executing step S53;

[0063] S53, determining whether the user's gaze point moves in multiple gaze foci within the preset movement time threshold, if the user's gaze point moves in multiple gaze foci within the preset movement time threshold, executing step S54, if the user's gaze point does not move in multiple gaze foci within the preset movement time threshold, executing step S55;

[0064] S54, determining whether the user has any operation behavior within the preset moving time threshold, if the user has no operation behavior within the preset moving time threshold, returning to step S51, if the user has any operation behavior within the preset moving time threshold, executing step S55;

[0065] S55, determining whether the dwell time of the user's gaze point exceeds the dwell time threshold; if the dwell time of the user's gaze point exceeds the dwell time threshold, returning to step S51, if the dwell time of the user's gaze point does not exceed the dwell time threshold, executing step S56;

[0066] S56: Determine whether the eye movement trajectory is abnormal.

[0067] In this embodiment, when the eye tracker is working, it will mark certain areas in the picture viewed by the user as gaze focuses in time sequence and number them, such as 1, 2, 3...; in step S50, the repetition of the user's gaze point in the two gaze focus marks is found after calculation and analysis by the eye tracker, that is, the user's visual focus goes back and forth between 1 and 3, that is, first looking at area 1, then looking at area 3, then looking at area 1, and then looking at area 3, and so on, which is a regular behavior; if the number of repetitions of the user's gaze point in the two gaze focus marks exceeds the repetition number threshold, it is determined that the eye movement trajectory is abnormal.

[0068] In step S52, whether the user's gaze point repeatedly moves in sequence among multiple gaze focus marks means that after the eye tracker calculation and analysis, it is found that the user's visual focus moves back and forth between the three areas 1, 3, and 5, that is, first looking at area 1, then area 3, then area 5, then area 1, then area 3, then area 5, and so on, which is a regular behavior.

[0069] When the eye movement trajectory is determined to be abnormal, the operation object involved in the abnormal eye movement trajectory and the operation object whose focus stays for more than a predetermined time limit are declared as experience obstacle items and reported to the researchers.

[0070] The embodiment of the present invention further provides a software product experience monitoring device based on physiological parameters, and the software product experience monitoring device based on physiological parameters is used to execute any embodiment of the software product experience monitoring method based on physiological parameters. Figure 4 , Figure 4 It is a schematic block diagram of a software product experience monitoring device based on physiological parameters provided by an embodiment of the present invention.

[0071] like Figure 4 As shown, the software product experience monitoring device 500 based on physiological parameters includes:

[0072] The acquisition unit 501 is used to acquire the test duration, eye movement data, facial expression data and operation behavior data of the user during the test task execution;

[0073] A first judging unit 502 is used to judge whether the test task is completed based on the operation behavior data;

[0074] The second judgment unit 503 is used to, if the test task is completed, continue to judge whether the test duration exceeds the test duration threshold; if the test duration does not exceed the test duration threshold, the test task is judged to be successful and ended; if the test duration exceeds the test duration threshold, the test task is judged to have failed, and the facial expression data is input into the expression analysis module to obtain an expression judgment result;

[0075] The output unit 504 is used to determine whether the eye movement data is abnormal. If the eye movement data is abnormal, the eye movement data is combined with the expression judgment result and an experience fault report is output.

[0076] The device integrates and analyzes eye movement data, facial expression data, and operational behavior data to determine whether the pages or operation items encountered by users when completing specific test tasks have caused obstacles to the use process. Based on the judgment rules and results, the experience obstacle page is reported to the experience researchers. It can accurately judge the emotions and operational feedback generated by users during the use of the software, and provide modification reference messages to the software product development team.

[0077] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0078] The above-mentioned software product experience monitoring device based on physiological parameters can be implemented in the form of a computer program, which can be used in Figure 5 Runs on the computer device shown.

[0079] See also Figure 5 , Figure 5 11 is a schematic block diagram of a computer device provided by an embodiment of the present invention. The computer device 1100 is a server, which may be an independent server or a server cluster composed of multiple servers.

[0080] See also Figure 5 The computer device 1100 includes a processor 1102 , a memory, and a network interface 1105 connected via a system bus 1101 , wherein the memory may include a non-volatile storage medium 1103 and an internal memory 1104 .

[0081] The non-volatile storage medium 1103 can store an operating system 11031 and a computer program 11032. When the computer program 11032 is executed, the processor 1102 can execute a software product experience monitoring method based on physiological parameters.

[0082] The processor 1102 is used to provide computing and control capabilities to support the operation of the entire computer device 1100 .

[0083] The internal memory 1104 provides an environment for the operation of the computer program 11032 in the non-volatile storage medium 1103. When the computer program 11032 is executed by the processor 1102, the processor 1102 can execute the software product experience monitoring method based on physiological parameters.

[0084] The network interface 1105 is used for network communication, such as providing data information transmission, etc. Those skilled in the art will understand that Figure 5 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present invention, and does not constitute a limitation on the computer device 1100 to which the solution of the present invention is applied. The specific computer device 1100 may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0085] Those skilled in the art will understand that Figure 5 The embodiments of the computer device shown in the figure do not constitute a limitation on the specific composition of the computer device. In other embodiments, the computer device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. For example, in some embodiments, the computer device may only include a memory and a processor. In such embodiments, the structure and function of the memory and the processor are the same as those of the embodiment of the present invention. Figure 5 The embodiments shown are consistent and will not be described again here.

[0086] It should be understood that in the embodiment of the present invention, the processor 1102 may be a central processing unit (CPU), and the processor 1102 may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0087] In another embodiment of the present invention, a computer-readable storage medium is provided. The computer-readable storage medium may be a non-volatile computer-readable storage medium. The computer-readable storage medium stores a computer program, wherein when the computer program is executed by a processor, the software product experience monitoring method based on physiological parameters of an embodiment of the present invention is implemented.

[0088] The storage medium is a physical, non-transient storage medium, for example, it can be a USB flash drive, a mobile hard disk, a read-only memory (ROM), a magnetic disk or an optical disk, etc., which can store program codes.

[0089] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described equipment, devices and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0090] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed by the present invention, and these modifications or replacements should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.

Claims

1. A software product experience monitoring method based on physiological parameters, characterized in that: include: Obtain the test duration, eye movement data, facial expression data, and operation behavior data of the user during the test task execution; Based on the operation behavior data, determining whether the test task is completed; If the test task is completed, continue to determine whether the test duration exceeds the test duration threshold; If the test duration does not exceed the test duration threshold, the test task is determined to be successful and ended; if the test duration exceeds the test duration threshold, the test task is determined to have failed, and the facial expression data is input into the expression analysis module to obtain an expression judgment result; Determine whether the eye movement data is abnormal, and if the eye movement data is abnormal, combine the eye movement data with the expression judgment result and output an experience fault report; The acquisition of the test duration, eye movement data, facial expression data, and operation behavior data of the user during the test task execution includes: Use an eye tracker to obtain the user's gaze point, eye movement trajectory, and gaze point retention time to obtain eye movement data; Use the camera to capture images of the user's eyes, mouth, and forehead area to obtain facial expression data; Monitor the user's mouse click instructions, keyboard input instructions, and mouse hover time to obtain operation behavior data; The determining whether the test task is completed based on the operation behavior data includes: Determine whether the mouse hovering time exceeds a no-operation time threshold; If the mouse hovering time exceeds the no-operation time threshold, the operation behavior of the current operation page and the previous operation object and the operation behavior of the pre-defined next operation object are recorded, and an experience fault report is output, wherein the operation objects include a mouse and a keyboard; If the mouse hovering time does not exceed the no-operation time threshold, continue to determine whether the current operation behavior is the last operation behavior in the test task; If the current operation behavior is the last operation behavior in the test task, then the test task is determined to be completed; If the current operation behavior is not the last operation behavior in the test task, it is determined that the test task is not completed; The determining whether the eye movement data is abnormal, and if the eye movement data is abnormal, combining the eye movement data with the expression determination result and outputting the experience fault report, comprises: If the expression judgment result is a negative emotion, then obtaining the duration of the negative emotion, and determining whether the duration of the negative emotion exceeds a negative emotion time threshold; If the duration of the negative emotion exceeds the negative emotion time threshold, then backtrack and output an experience fault report consisting of the user's operation behavior data and eye movement data within the duration of the negative emotion; If the duration of the negative emotion does not exceed the negative emotion time threshold or the expression judgment result is a non-negative emotion, all eye movement data are traced back to determine whether the eye movement data is abnormal.

2. The method for monitoring software product experience based on physiological parameters according to claim 1, characterized in that: The determining whether the eye movement data is abnormal, and if the eye movement data is abnormal, combining the eye movement data with the expression determination result and outputting an experience fault report, includes: Reviewing the eye movement data to determine whether there are abnormal eye movement trajectories; If there is an eye movement trajectory abnormality, obtain the duration of the eye movement trajectory abnormality, obtain the operation behavior data within the duration of the eye movement trajectory abnormality, and output an experience fault report; If there is no abnormal eye movement trajectory, the process ends.

3. The method for monitoring software product experience based on physiological parameters according to claim 2, characterized in that: The determining whether there is an abnormal eye movement trajectory includes: Determine whether the number of repetitions of the user's gaze point in the two gaze focus marks exceeds the repetition number threshold. If the number of repetitions of the user's gaze point in the two gaze focus marks exceeds the repetition number threshold, then determine that the eye movement trajectory is abnormal, wherein the two gaze focus marks are two non-overlapping screen areas.

4. The method for monitoring software product experience based on physiological parameters according to claim 3, characterized in that: The determining whether there is an abnormal eye movement trajectory also includes: If the number of repetitions of the user's gaze point in the two gaze focus marks does not exceed the repetition number threshold, continue to determine whether the user's gaze point repeatedly moves in the multiple gaze focus marks in sequence; If the user's gaze point repeatedly moves in sequence across multiple gaze focus marks, then the eye movement trajectory is determined to be abnormal; If the user's gaze point does not repeatedly move in sequence across multiple gaze focus marks, continue to determine whether the user's gaze point moves across multiple gaze focus marks within a preset movement time threshold, and whether there is any operation behavior within the preset movement time threshold; If the user's gaze point moves between multiple gaze focal points within the preset movement time threshold, and there is no operation behavior within the preset movement time threshold, then it is determined that the eye movement trajectory is abnormal; If the user's gaze point moves between multiple gaze focal points within the preset movement time threshold, and there is an operation behavior within the preset movement time threshold, then continue to determine whether the user's gaze point stays for longer than the stay time threshold; If the duration of the user's gaze point does not exceed the duration threshold, the eye movement trajectory is determined to be normal; if the duration of the user's gaze point exceeds the duration threshold, the eye movement trajectory is determined to be abnormal.

5. A software product experience monitoring device based on physiological parameters, characterized in that: include: An acquisition unit, used to acquire the test duration, eye movement data, facial expression data, and operation behavior data of the user during the test task execution; A first judging unit, configured to judge whether the test task is completed based on the operation behavior data; A second judgment unit, configured to continue to judge whether the test duration exceeds a test duration threshold if the test task is completed; If the test duration does not exceed the test duration threshold, the test task is determined to be successful and ended; if the test duration exceeds the test duration threshold, the test task is determined to have failed, and the facial expression data is input into the expression analysis module to obtain an expression judgment result; an output unit, used to determine whether the eye movement data is abnormal, and if the eye movement data is abnormal, combine the eye movement data with the expression judgment result and output an experience fault report; The acquisition of the test duration, eye movement data, facial expression data, and operation behavior data of the user during the test task execution includes: Use an eye tracker to obtain the user's gaze point, eye movement trajectory, and gaze point retention time to obtain eye movement data; Use the camera to capture images of the user's eyes, mouth, and forehead area to obtain facial expression data; Monitor the user's mouse click instructions, keyboard input instructions, and mouse hover time to obtain operation behavior data; The determining whether the test task is completed based on the operation behavior data includes: Determine whether the mouse hovering time exceeds a no-operation time threshold; If the mouse hovering time exceeds the no-operation time threshold, the operation behavior of the current operation page and the previous operation object and the operation behavior of the pre-defined next operation object are recorded, and an experience fault report is output, wherein the operation objects include a mouse and a keyboard; If the mouse hovering time does not exceed the no-operation time threshold, continue to determine whether the current operation behavior is the last operation behavior in the test task; If the current operation behavior is the last operation behavior in the test task, then the test task is determined to be completed; If the current operation behavior is not the last operation behavior in the test task, it is determined that the test task is not completed; The determining whether the eye movement data is abnormal, and if the eye movement data is abnormal, combining the eye movement data with the expression determination result and outputting the experience fault report, comprises: If the expression judgment result is a negative emotion, then obtaining the duration of the negative emotion, and determining whether the duration of the negative emotion exceeds a negative emotion time threshold; If the duration of the negative emotion exceeds the negative emotion time threshold, then backtrack and output an experience fault report consisting of the user's operation behavior data and eye movement data within the duration of the negative emotion; If the duration of the negative emotion does not exceed the negative emotion time threshold or the expression judgment result is a non-negative emotion, all eye movement data are traced back to determine whether the eye movement data is abnormal.

6. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method for monitoring software product experience based on physiological parameters as described in any one of claims 1 to 4 is implemented.

7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, enables the processor to execute the software product experience monitoring method based on physiological parameters as described in any one of claims 1 to 4.

Images