Abnormal problem processing method and device, equipment and medium
By monitoring and processing the function comment information uploaded by users, determining the response strategy and handling abnormal problems in the software product, the problem of low processing efficiency in software product use is solved, and the work efficiency of the user experience and development department is improved.
Patent Information
- Application Number
- CN202411237488.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-04
- Publication Date
- 2024-12-03
AI Technical Summary
During the use of software products, the problems encountered by users are inefficient and inaccurate, resulting in increased workloads in the development department and impacted user experience.
By monitoring the function comment information uploaded by users, determine the type of comment information and deal with abnormal problems according to the response policy, including setting the function comment information upload options, configuring response priority and feedback period, and handling software operations, response exceptions, function implementation and interface problems in real time, , distinguish between hardware device failures and software problems, generate user experience logs and prioritize emergency issues.
It realizes accurate positioning and rapid processing of functional abnormalities, improves user experience and problem solving efficiency, and reduces the work burden of the development department.
Smart Images

Figure CN119065884A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to an abnormal problem handling method, device, equipment and medium. Background Art
[0002] When using the device's software products, users may encounter various problems, such as function usage problems, interface operation problems, data processing problems, and system compatibility problems. These problems may be caused by unfamiliarity with the product, or they may be defects in the product itself. Usually, users will choose to contact the product after-sales staff or call the customer service hotline to seek solutions.
[0003] However, this approach may take a long time to resolve the problem because the problem needs to be passed and processed through multiple links. Secondly, not all problems are caused by software development, but they are all submitted to the development department, which not only increases the workload of the development department, but may also lead to delays in problem resolution. In addition, this approach may also have a negative impact on user experience because users may have to wait a long time to get a solution.
[0004] In view of the above problems, how to solve the low efficiency and inaccurate processing methods of handling problems encountered by users during the use of software products is an issue that needs to be urgently addressed by technical personnel in this field. Summary of the invention
[0005] The purpose of this application is to provide an abnormal problem handling method, device, equipment and medium to solve the problem of low efficiency and inaccurate handling of problems encountered by users during the use of software products.
[0006] In order to solve the above technical problems, the present application provides a method for handling abnormal problems, including:
[0007] Monitoring function review information uploaded by users; wherein the function review information is the user's review information on the function that has abnormal problems in the target software product;
[0008] When receiving the function review information, determining the review information type of the function review information; wherein the review information type at least includes software operation problem type, software response exception type, function implementation exception type, operation experience type and interface problem type;
[0009] A response strategy corresponding to the functional review information is determined according to the review information type, and the function with abnormal problems in the target software product is processed according to the response strategy.
[0010] On the one hand, before monitoring the function review information uploaded by the user, it also includes:
[0011] Based on the operation interface of the target software product, setting a function review information upload option corresponding to each function, so that the user can upload the function review information through the function review information upload option;
[0012] The response priority and response feedback deadline are set for each type of comment information.
[0013] On the other hand, when a plurality of function review information are received, determining a response strategy corresponding to the function review information according to the type of the review information, and processing the function having an abnormal problem in the target software product according to the response strategy, includes:
[0014] Respectively determine the response priority of the comment information type of each of the functional comment information;
[0015] Determining the response strategy corresponding to each functional review information in turn according to each response priority;
[0016] According to each of the response priorities and the corresponding response strategies, processing in sequence each function having an abnormal problem in the target software product;
[0017] Based on the target software product, response feedback to the functional review information is outputted respectively within the response feedback period of each review information type.
[0018] On the other hand, determining a response strategy corresponding to the functional review information according to the review information type, and processing the function having an abnormal problem in the target software product according to the response strategy, includes:
[0019] When the comment information type is the software operation problem type, obtaining operation guidance information of the function corresponding to the function comment information;
[0020] Outputting the operation guidance information through the display interface of the target software product;
[0021] When the comment information type is the software response exception type and / or the function implementation exception type, obtaining a debug version program of the target software product;
[0022] Updating the target software product through the debugging version program;
[0023] When the comment information type is the operation experience type and / or the interface problem type, generating a user experience log according to the function comment information;
[0024] The user experience log is saved in a software development database.
[0025] On the other hand, if the comment information type is the software response exception type and / or the function implementation exception type, before obtaining the debug version program of the target software product, the method further includes:
[0026] According to the function review information, determining whether the function abnormality of the target software product is caused by a hardware device failure; wherein the target software product is an embedded software of the hardware device;
[0027] If not, proceed to the step of obtaining the debug version program of the target software product;
[0028] If so, hardware maintenance prompt information is generated, and the hardware maintenance prompt information is output through the display interface of the target software product.
[0029] On the other hand, after determining the comment information type of the functional comment information, the method further includes:
[0030] Determine whether the amount of target function review information is greater than a first preset amount; wherein the target function review information is function review information of the type of the software operation problem type or the software response abnormality type;
[0031] If so, a label indicating immediate processing is added to the target software product to prompt the target software product to immediately process the function with the abnormal problem.
[0032] On the other hand, it also includes:
[0033] When receiving the function review information uploaded by multiple users, respectively determining the number of target function review information uploaded by each user; wherein the target function review information is function review information of the type of the software operation problem type or the software response abnormality type;
[0034] Arrange the quantity of the target function review information uploaded by each user in descending order to generate an abnormal problem processing sequence;
[0035] The function review information uploaded by each user is processed in sequence according to the abnormal problem processing sequence.
[0036] In order to solve the above technical problems, the present application also provides an abnormal problem handling device, including:
[0037] A monitoring module, used to monitor the function review information uploaded by users; wherein the function review information is the user's review information on the function with abnormal problems in the target software product;
[0038] A determination module, configured to determine the comment information type of the function comment information when receiving the function comment information; wherein the comment information type at least includes a software operation problem type, a software response exception type, a function implementation exception type, an operation experience type, and an interface problem type;
[0039] The processing module is used to determine a response strategy corresponding to the functional review information according to the type of the review information, and process the function with abnormal problems in the target software product according to the response strategy.
[0040] In order to solve the above technical problems, the present application also provides an abnormal problem handling device, including:
[0041] Memory for storing computer programs;
[0042] A processor is used to implement the steps of the above-mentioned abnormal problem handling method when executing the computer program.
[0043] In order to solve the above technical problems, the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned abnormal problem handling method are implemented.
[0044] One of the above technical solutions has the following advantages or beneficial effects: it has high real-time performance by real-time monitoring of the function comment information about function abnormalities uploaded by users when using the target software product; when the function comment information is received, it can determine the comment information type of the function comment information, thereby clarifying the specific type of the function abnormality problem and accurately locating the function abnormality problem; finally, the corresponding response strategy is determined according to the specific comment information type, so as to handle the functions with abnormal problems according to the response strategy, which has the advantages of accurate and efficient processing methods, and greatly improves the user experience of the target software product.
[0045] In addition, the present application also provides an abnormal problem handling device, equipment and medium, with the same effect as above. BRIEF DESCRIPTION OF THE DRAWINGS
[0046] In order to more clearly illustrate the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0047] Figure 1 A flowchart of a method for handling abnormal problems provided in an embodiment of the present application;
[0048] Figure 2 A flowchart of another abnormal problem handling method provided in an embodiment of the present application;
[0049] Figure 3 A schematic diagram of an abnormal problem handling device provided in an embodiment of the present application;
[0050] Figure 4 A schematic diagram of an abnormal problem handling device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0051] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0052] The core of this application is to provide an abnormal problem handling method, device, equipment and medium to solve the problem of low efficiency and inaccurate handling method of problems encountered by users during the use of software products.
[0053] In order to enable those skilled in the art to better understand the present application, the present application is further described in detail below in conjunction with the accompanying drawings and specific implementation methods.
[0054] At present, when using software products, users may encounter various problems, such as function usage problems, interface operation problems, data processing problems, and system compatibility problems. These problems may be caused by unfamiliarity with the product, or they are indeed defects in the product itself. Usually, users will choose to contact after-sales personnel or call customer service to seek solutions. These problems will eventually be summarized and handled by the company's software development department.
[0055] However, there are some problems with this approach. First, it may take a long time to solve the problem because the problem needs to be transmitted and processed through multiple links. Secondly, not all problems are caused by software development, but they are all submitted to the development department in a unified manner, which not only increases the workload of the development department, but may also cause delays in problem solving. In addition, this approach may also have a negative impact on user experience because users may have to wait a long time to get a solution. Therefore, in order to improve the accuracy and efficiency of problem solving and improve user satisfaction, this application provides a method for handling abnormal problems.
[0056] It should be noted that the present application does not impose any restrictions on the application scenarios of the exception problem handling method. It only needs to ensure that the application scenarios of the exception problem handling method can communicate and transmit data with the target software product, such as a computer or server used for software development, etc., depending on the specific implementation scenario.
[0057] Figure 1 A flowchart of a method for handling abnormal problems provided in an embodiment of the present application. Figure 1 As shown, the method includes:
[0058] S10: Monitor the function review information uploaded by users.
[0059] The function review information is the user's review information on the function that has abnormal problems in the target software product.
[0060] In the specific implementation, the function review information uploaded by the user is first monitored. It should be noted that the function review information is the comment information of the user on the function of the target software product that has abnormal problems when using the target software product. It is understandable that the abnormal problems here include but are not limited to software operation problems where the user may not be familiar with the function of the software and does not know how to use certain specific operations or functions, the user may be confused about the interface layout or operation mode of the software, resulting in interface operation problems that cannot successfully complete the task, the user may find that the software is incompatible with other systems or software, resulting in system compatibility problems that cannot be used normally, the user may encounter performance problems such as slow running, freezing, crashing, etc. of the software, which affect the user experience, and the user may find bugs or defects in the software, resulting in bug problems that the function cannot be used normally or produce erroneous results. At the same time, the information form of the function review information can be in plain text form, such as the user manually editing the content of the function review information; it can also be in the form of option values, such as pre-setting specific options for users to choose, and the user realizes the editing of the content of the function review information by selecting specific option values.
[0061] It should be noted that the present embodiment does not limit the specific product type of the target software product used by the user, and may specifically be, for example, operating systems, office software, database management systems, graphic image processing software, multimedia software, network communication software, game software, industry application software, mobile applications, and cloud computing services, etc. In addition, the present embodiment does not limit the specific method for users to upload functional review information, and may, for example, upload through a function window preset in the target software product, or log in to the official website of the target software product to upload, depending on the specific implementation situation.
[0062] S11: When receiving function review information, determining the review information type of the function review information.
[0063] Among them, the comment information types at least include software operation problem types, software response exception types, function implementation exception types, operation experience types and interface problem types.
[0064] Furthermore, when function review information uploaded by a user is received, it is necessary to determine the review information type of the function review information.
[0065] It is worth noting that the comment information types in this embodiment at least include software operation problem types, such as users not knowing how to operate software functions; software response abnormality types, such as software flashback, freeze, freeze, and no response to clicks; function implementation abnormality types, such as software function confusion, parameter display abnormality, and text display errors; operation experience types, such as software operation methods are complicated and cumbersome, and user experience is poor; and interface problem types, such as the interactivity of the software interface is not friendly. Other specific comment information types may also be included, which are not limited in this embodiment.
[0066] In a specific implementation, after obtaining the function review information uploaded by the user, the review information type of the function review information can be directly determined according to the content of the function review information.
[0067] S12: Determine a response strategy corresponding to the functional review information according to the type of the review information, and process the function with abnormal problems in the target software product according to the response strategy.
[0068] Since the function review information has different types of review information, in order to accurately process the function review information of different types of review information, that is, to adopt an accurate processing method for the function with abnormal problems in the target software product, this embodiment specifically determines the response strategy corresponding to the function review information according to the review information type, and processes the function with abnormal problems in the target software product according to the response strategy.
[0069] It should be noted that in this embodiment, there is no restriction on the method of determining different response strategies, which depends on the specific type of comment information; at the same time, there is no restriction on the specific process of handling abnormal problems in the functions of the target software product according to the response strategy, which depends on the specific implementation situation.
[0070] In this embodiment, by real-time monitoring of the function comment information about function abnormalities uploaded by users when using the target software product, it has high real-time performance; when the function comment information is received, the comment information type of the function comment information can be determined, thereby clarifying the specific type of the function abnormality problem, and achieving accurate positioning of the function abnormality problem; finally, the corresponding response strategy is determined according to the specific comment information type, so that the function with abnormal problems can be processed according to the response strategy, which has the advantages of accurate and efficient processing methods, and greatly improves the user experience of the target software product.
[0071] Figure 2 A flowchart of another abnormal problem handling method provided by an embodiment of the present application. In order to facilitate users to upload function review information and improve the user experience, based on the above embodiments, in some embodiments, before monitoring the function review information uploaded by users, such as Figure 2 As shown, the method also includes:
[0072] S13: Based on the operation interface of the target software product, setting a function review information upload option corresponding to each function, so that the user can upload the function review information through the function review information upload option;
[0073] S14: Set the response priority and response feedback deadline for each comment information type respectively.
[0074] In a specific implementation, before monitoring the function review information uploaded by users, function review information upload options corresponding to each function may be set based on the operation interface of the target software product, so that users can upload function review information through the function review information upload options.
[0075] It should be noted that, in this embodiment, there is no restriction on the presentation form of the function comment information upload option in the operation interface of the target software product. For example, the function comment information upload option can be fixed in a fixed position in the operation interface, the corresponding function comment information upload option can be jumped after the user exits the function, and the function comment information upload option can also be jumped when the user operates a certain function for more than a time value, depending on the specific implementation situation.
[0076] On the other hand, the response priority of each type of comment information needs to be determined separately. It is understandable that different types of functional comment information uploaded by users have different degrees of severity, and correspondingly have different processing priorities. For example, in order to ensure the normal use of the target software product, the abnormal problems indicated by the functional comment information of the software response exception type should be processed before the abnormal problems indicated by the functional comment information of the software operation problem type, so it is necessary to configure the response priority of each type of comment information. The following is an optional setting method for the response priority of the comment information type, arranged in order from high to low: function implementation exception type > software response exception type > software operation problem type > operation experience type > interface problem type. It should be noted that the above response priority setting method is only a preferred embodiment, and other setting methods can be adopted according to actual needs in the specific implementation.
[0077] Finally, set a response feedback deadline for each type of comment information. The response feedback deadline refers to the deadline for sending response feedback to the user from the moment the function comment information uploaded by the user is received. It should be noted that the response feedback here indicates that the function comment information uploaded by the user has been received, and the problems mentioned in the function comment information have begun to be processed. Different types of comment information have different response feedback deadlines. For example, for urgent function implementation exception types, it can be set to send response feedback within 4 hours, and for non-urgent interface problem types, it can be set to feedback within 24 hours. In this embodiment, the specific setting method of the response feedback deadline for different types of comment information is not limited, and it depends on the specific implementation situation.
[0078] In this embodiment, based on the operating interface of the target software product, a function review information upload option corresponding to each function is set to facilitate users to upload function review information; at the same time, the response priority and response feedback deadline of each comment information type are set respectively, which improves the efficiency of handling abnormal problems and the user experience.
[0079] Based on the above embodiment, in some embodiments, when multiple function review information is received, such as Figure 2 As shown, a response strategy corresponding to the functional review information is determined according to the type of the review information, and the function with abnormal problems in the target software product is processed according to the response strategy, including:
[0080] S121: Determine the response priority of each type of comment information for each function comment information;
[0081] S122: Determine the response strategy corresponding to each functional comment information in turn according to each response priority;
[0082] S123: processing each function having abnormal problems in the target software product in turn according to each response priority and the corresponding response strategy;
[0083] S124: Based on the target software product, outputting response feedback to the functional review information respectively within the response feedback period of each review information type.
[0084] In a specific implementation, when multiple function review information sent by a user is received at the same time, in order to respectively process the function abnormalities pointed out in the multiple function review information, the response priority of the review information type of each function review information is specifically determined.
[0085] Further, according to the order of each response priority, the response strategy corresponding to each function comment information is determined in turn, and according to the order of each response priority and the corresponding response strategy, each function with abnormal problems in the target software product is processed in turn. The specific process of generating the response strategy and processing each function with abnormal problems is not limited in this embodiment.
[0086] In addition, in order to let the user know that the current function review information has been received and processed, based on the target software product, the response feedback to the function review information is output within the response feedback period of each review information type, so that the user can obtain the response feedback through the target software product. In this embodiment, there is no restriction on the output method of the response feedback, for example, the response feedback message can be displayed on the display interface of the target software product, or it can be displayed in a pop-up window, prompt box, or vibration prompt.
[0087] In this embodiment, when multiple function review information sent by the user is received at the same time, the response priority of the comment information type of each function review information is determined respectively; according to each response priority, the response strategy corresponding to each function review information is determined in turn, and each function with abnormal problems in the target software product is processed in turn, taking into account the severity of each function review information and processing it, thereby improving the efficiency of handling abnormal problems. At the same time, based on the target software product, the response feedback to the function review information is outputted respectively within the response feedback period of each comment information type, which meets the user's demand for feedback on abnormal problem handling and improves the user's experience.
[0088] Based on the above embodiments, in some embodiments, a response strategy corresponding to the functional review information is determined according to the type of the review information, and the function with abnormal problems in the target software product is processed according to the response strategy, including:
[0089] S125: When the comment information type is a software operation problem type, obtaining operation guidance information of the function corresponding to the function comment information;
[0090] S126: Outputting operation guidance information through a display interface of the target software product;
[0091] S127: When the comment information type is a software response exception type and / or a function implementation exception type, obtaining a debug version program of the target software product;
[0092] S128: updating the target software product through the debugging version program;
[0093] S129: When the comment information type is an operation experience type and / or an interface problem type, generating a user experience log according to the function comment information;
[0094] S130: Save the user experience log to the software development database.
[0095] In a specific implementation, when the comment information type is a software operation problem type, for example, when the user does not know how to operate the target software product, in order to let the user know how to operate the target software product, the operation guidance information of the function corresponding to the function comment information is specifically obtained, and the operation guidance information is output through the display interface of the target software product, so that the user can operate the target software product according to the operation guidance information. It should be noted that the specific form of the operation guidance information is not limited in this embodiment, for example, it can be a text description, or a video form or an audio form, depending on the specific implementation situation.
[0096] When the comment information type is software response abnormality type and / or function implementation abnormality type, such as the target software product crashes, freezes, freezes, no response to clicks, and / or has functional confusion, abnormal parameter display, and text errors, etc., in order to enable users to use the target software product normally, the debug version program of the target software product is specifically obtained, and the target software product is updated through the debug version program. It should be noted that the debug version program of the target software product may not be the latest version, but it needs to be guaranteed to run normally.
[0097] When the comment information type is an operation experience type and / or an interface problem type, for example, when the user believes that the operation method of the current target software product is complicated and / or the interface interaction is unfriendly, in order to improve the user experience, a user experience log is generated based on the functional comment information, and the user experience log is saved in the software development database, so that developers can determine the user's usage needs based on the user experience log in the software development database, and ultimately define whether new development needs are formed so that the new development needs can be implemented in the next iterative version of the target software product.
[0098] In addition, when the comment information type is other types, the corresponding functional comment information can be packaged and sent to the expert group, which will determine the specific problem type and then distribute it to the corresponding personnel for resolution.
[0099] In this embodiment, when the types of review information are software operation problem type, software response exception type, function implementation exception type, operation experience type and interface problem type, the response strategies for the corresponding function review information are determined respectively, and different processing methods are adopted for each function exception problem according to each response strategy, which can accurately solve the abnormal problems that arise and ensure the normal use of the target software product by users.
[0100] The operation of the target software product depends on the hardware device where it is located. When there is a problem or failure in the hardware device, it often affects the normal operation of the target software product, which is ultimately reflected in the abnormality of the target software product, that is, there will be software response abnormalities and / or function implementation abnormalities. At this time, if only the target software product is maintained, it cannot fundamentally solve the problem, but will affect the user's operating experience. Therefore, based on the above embodiments, in some embodiments, if the comment information type is a software response abnormality type and / or a function implementation abnormality type, before obtaining the debug version program of the target software product, it also includes:
[0101] S131: judging whether the functional abnormality of the target software product is caused by a hardware device failure according to the functional review information; wherein the target software product is an embedded software of the hardware device; if not, proceeding to step S127; if yes, proceeding to step S132;
[0102] S132: Generate hardware maintenance prompt information, and output the hardware maintenance prompt information through a display interface of the target software product.
[0103] Specifically, when it is confirmed that the comment information type is a software response exception type and / or a function implementation exception type, it is first necessary to determine whether the function exception of the target software product is caused by a hardware device failure based on the function comment information. It is understandable that the target software product is an embedded software for a hardware device. In this embodiment, there is no restriction on the specific judgment method. For example, a pre-built hardware inspection script is used to check the hardware device to determine whether the hardware device is faulty; a manual inspection method can also be used to determine whether the hardware device is faulty.
[0104] If it is confirmed that the functional anomaly of the target software product is not caused by a hardware device failure, it is considered that the target software product itself has a functional anomaly, and the step of obtaining the debug version program of the target software product is entered to update the target software product using the debug version program. If it is confirmed that the functional anomaly of the target software product is caused by a hardware device failure, it is considered that the hardware device failure has caused the functional anomaly of the target software product, and the hardware device needs to be maintained. Specifically generate hardware maintenance prompt information, and output the hardware maintenance prompt information through the display interface of the target software product, so that the user can maintain the hardware device according to the hardware maintenance prompt information. In this embodiment, there is no restriction on the specific form of the hardware maintenance prompt information, for example, it can be a text description, and it can also be in the form of video or audio, depending on the specific implementation situation.
[0105] In this embodiment, when the comment information type is confirmed to be a software response exception type and / or a function implementation exception type, by judging whether the functional abnormality of the target software product is caused by a hardware device failure, and taking corresponding maintenance measures when the hardware device failure is confirmed, the hardware device failure is detected, thereby avoiding the software product functional abnormality caused by the hardware device failure.
[0106] In order to remind developers to prioritize handling of urgent functional abnormalities, based on the above embodiments, in some embodiments, after determining the type of comment information of the functional comment information, the following is further included:
[0107] S15: Determine whether the number of target function review information is greater than a first preset number; if so, proceed to step S16;
[0108] The target function review information is function review information of a software operation problem type or a software response abnormality type;
[0109] S16: Add a label indicating immediate processing to the target software product to prompt immediate processing of the function with abnormal problems in the target software product.
[0110] In a specific implementation, in order to remind developers to give priority to urgent functional abnormality problems, after determining the comment information type of the functional comment information, it is further determined whether the number of target functional comment information is greater than the first preset number. It should be noted that the target functional comment information is functional comment information of the type of software operation problem type or software response abnormality type, such as the target software product flashing back, freezing, freezing, no response to clicks, or functional confusion, abnormal parameter display, and text errors. In this embodiment, there is no restriction on the first preset number, which depends on the specific implementation situation.
[0111] If it is confirmed that the number of target function review information is not greater than the first preset number, it is considered that the functional anomaly problem of the current target software product is not serious and can be handled normally. If it is confirmed that the number of target function review information is greater than the first preset number, it is considered that the functional anomaly problem of the current target software product is very serious and seriously affects the normal use of the target software product. At this time, it is necessary to add a label representing immediate processing to the target software product to prompt the staff to immediately handle the function with abnormal problems in the target software product. For example, immediately provide the user with a debug version of the target software product, so that the target software product can be updated through the debug version program to solve the functional anomaly problem.
[0112] In this embodiment, when the number of target function review information is greater than a first preset number, a label representing immediate processing is added to the target software product to prompt the staff to immediately process the function with abnormal problems in the target software product, thereby ensuring the rapid and normal operation of the target software product.
[0113] In order to maintain a software product with more serious functional abnormality problems, based on the above embodiments, in some embodiments, the method further includes:
[0114] S17: when receiving function review information uploaded by multiple users, determining the number of target function review information uploaded by each user;
[0115] The target function review information is function review information of a software operation problem type or a software response abnormality type;
[0116] S18: Arrange the number of target function review information uploaded by each user in descending order to generate an abnormal problem processing sequence;
[0117] S19: Process the function review information uploaded by each user in turn according to the abnormal problem processing sequence.
[0118] Specifically, when function review information uploaded by multiple users is received at the same time, in order to carry out targeted maintenance on software products with more serious function abnormality problems, the number of target function review information uploaded by each user is specifically determined. It should be noted that the target function review information is function review information of the type of software operation problem type or software response abnormality type, such as the target software product has flashback, freeze, freeze, no response to click, or function disorder, abnormal parameter display, and text errors.
[0119] Further, the number of target function comment information uploaded by each user is arranged in order from large to small to generate an abnormal problem processing sequence. For example, the number of target function comment information uploaded by user A is 3, the number of target function comment information uploaded by user B is 4, and the number of target function comment information uploaded by user C is 1. Then, the generated abnormal problem processing sequence is BAC, which is arranged in order from large to small. The function comment information uploaded by each user is processed in turn according to the abnormal problem processing sequence, that is, the function comment information uploaded by the user with the largest number of target function comment information is processed first. For example, based on the above-mentioned abnormal problem processing sequence BAC, the function comment information uploaded by user B, user A and user C are processed in turn.
[0120] In this embodiment, when function review information uploaded by multiple users is received at the same time, the number of target function review information uploaded by each user is determined respectively, and the number of target function review information uploaded by each user is arranged in order from large to small to generate an abnormal problem processing sequence. Finally, the function review information uploaded by each user is processed in turn according to the abnormal problem processing sequence, thereby achieving targeted maintenance of software products with more serious function abnormality problems and ensuring the normal operation of software products.
[0121] In the above embodiments, the abnormal problem handling method is described in detail, and the present application also provides a corresponding embodiment of the abnormal problem handling device.
[0122] Figure 3 A schematic diagram of an abnormal problem handling device provided in an embodiment of the present application. Figure 3 As shown, the device comprises:
[0123] The monitoring module 10 is used to monitor the function review information uploaded by users; wherein the function review information is the user's review information on the function with abnormal problems in the target software product.
[0124] The determination module 11 is used to determine the comment information type of the function comment information when receiving the function comment information; wherein the comment information type at least includes software operation problem type, software response exception type, function implementation exception type, operation experience type and interface problem type.
[0125] The processing module 12 is used to determine the response strategy corresponding to the function review information according to the type of the review information, and process the function with abnormal problems in the target software product according to the response strategy.
[0126] Since the embodiments of the apparatus part correspond to the embodiments of the method part, please refer to the description of the embodiments of the method part for the embodiments of the apparatus part, which will not be repeated here.
[0127] Figure 4 A schematic diagram of an abnormal problem handling device provided in an embodiment of the present application. Figure 4 As shown, the abnormal problem handling device includes:
[0128] A memory 20, used for storing computer programs;
[0129] The processor 21 is used to implement the steps of the abnormal problem handling method mentioned in the above embodiment when executing the computer program.
[0130] The abnormal problem handling device provided in this embodiment may include but is not limited to a smart phone, a tablet computer, a laptop computer or a desktop computer.
[0131] Among them, the processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, etc. The processor 21 can be implemented in at least one hardware form of a digital signal processor (DSP), a field programmable gate array (FPGA), and a programmable logic array (PLA). The processor 21 may also include a main processor and a coprocessor. The main processor is a processor for processing data in an awake state, also known as a central processing unit (CPU); the coprocessor is a low-power processor for processing data in a standby state. In some embodiments, the processor 21 may be integrated with a graphics processing unit (GPU), and the GPU is responsible for rendering and drawing the content to be displayed on the display screen. In some embodiments, the processor 21 may also include an artificial intelligence (AI) processor, which is used to process computing operations related to machine learning.
[0132] The memory 20 may include one or more computer-readable storage media, which may be non-transitory. The memory 20 may also include a high-speed random access memory, and a non-volatile memory, such as one or more disk storage devices, flash memory storage devices. In this embodiment, the memory 20 is at least used to store the following computer program 201, wherein, after the computer program is loaded and executed by the processor 21, it can implement the relevant steps of the abnormal problem handling method disclosed in any of the aforementioned embodiments. In addition, the resources stored in the memory 20 may also include an operating system 202 and data 203, etc., and the storage method may be temporary storage or permanent storage. Among them, the operating system 202 may include Windows, Unix, Linux, etc. Data 203 may include but is not limited to data related to the abnormal problem handling method.
[0133] In some embodiments, the abnormal problem handling device may also include a display screen 22 , an input and output interface 23 , a communication interface 24 , a power supply 25 , and a communication bus 26 .
[0134] Those skilled in the art will understand that Figure 4 The structure shown in the figure does not constitute a limitation on the abnormal problem handling device, and may include more or fewer components than those shown in the figure.
[0135] Finally, the present application also provides an embodiment corresponding to a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps recorded in the above method embodiment are implemented.
[0136] It is understandable that if the method in the above embodiment is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.
[0137] The above is a detailed introduction to an abnormal problem handling method, device, equipment and medium provided by the present application. The various embodiments in the specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same and similar parts between the embodiments can refer to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can refer to the method part description. It should be pointed out that for ordinary technicians in this technical field, without departing from the principles of the present application, several improvements and modifications can be made to the present application, and these improvements and modifications also fall within the scope of protection of the present application.
[0138] It should also be noted that, in this specification, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.
Claims
1. A method for handling abnormal problems, characterized in that: include: Monitoring function review information uploaded by users; wherein the function review information is the user's review information on the function that has abnormal problems in the target software product; When receiving the function review information, determining the review information type of the function review information; wherein the review information type at least includes software operation problem type, software response exception type, function implementation exception type, operation experience type and interface problem type; A response strategy corresponding to the functional review information is determined according to the review information type, and the function with abnormal problems in the target software product is processed according to the response strategy.
2. The abnormal problem handling method according to claim 1, characterized in that: Before monitoring the function review information uploaded by the user, it also includes: Based on the operation interface of the target software product, setting a function review information upload option corresponding to each function, so that the user can upload the function review information through the function review information upload option; The response priority and response feedback deadline are set for each type of comment information.
3. The abnormal problem handling method according to claim 2, characterized in that: When a plurality of function review information are received, determining a response strategy corresponding to the function review information according to the type of the review information, and processing the function having an abnormal problem in the target software product according to the response strategy, includes: Respectively determine the response priority of the comment information type of each of the functional comment information; Determining the response strategy corresponding to each functional review information in turn according to each response priority; According to each of the response priorities and the corresponding response strategies, processing in sequence each function having an abnormal problem in the target software product; Based on the target software product, response feedback to the functional review information is outputted respectively within the response feedback period of each review information type.
4. The abnormal problem handling method according to claim 1, characterized in that: The step of determining a response strategy corresponding to the functional review information according to the review information type, and processing the function having an abnormal problem in the target software product according to the response strategy, includes: When the comment information type is the software operation problem type, obtaining operation guidance information of the function corresponding to the function comment information; Outputting the operation guidance information through the display interface of the target software product; When the comment information type is the software response exception type and / or the function implementation exception type, obtaining a debug version program of the target software product; Updating the target software product through the debugging version program; When the comment information type is the operation experience type and / or the interface problem type, generating a user experience log according to the function comment information; The user experience log is saved in a software development database.
5. The abnormal problem handling method according to claim 4, characterized in that: If the comment information type is the software response exception type and / or the function implementation exception type, before obtaining the debug version program of the target software product, the method further includes: According to the function review information, determining whether the function abnormality of the target software product is caused by a hardware device failure; wherein the target software product is an embedded software of the hardware device; If not, proceed to the step of obtaining the debug version program of the target software product; If so, hardware maintenance prompt information is generated, and the hardware maintenance prompt information is output through the display interface of the target software product.
6. The abnormal problem handling method according to claim 1, characterized in that: After determining the comment information type of the function comment information, the method further includes: Determine whether the amount of target function review information is greater than a first preset amount; wherein the target function review information is function review information of the type of the software operation problem type or the software response abnormality type; If so, a label indicating immediate processing is added to the target software product to prompt the target software product to immediately process the function with the abnormal problem.
7. The abnormal problem handling method according to any one of claims 1 to 6, characterized in that: Also includes: When receiving the function review information uploaded by multiple users, respectively determining the number of target function review information uploaded by each user; wherein the target function review information is function review information of the type of the software operation problem type or the software response abnormality type; Arrange the quantity of the target function review information uploaded by each user in descending order to generate an abnormal problem processing sequence; The function review information uploaded by each user is processed in sequence according to the abnormal problem processing sequence.
8. An abnormal problem handling device, characterized in that: include: A monitoring module, used to monitor the function review information uploaded by users; wherein the function review information is the user's review information on the function with abnormal problems in the target software product; A determination module, configured to determine the comment information type of the function comment information when receiving the function comment information; wherein the comment information type at least includes a software operation problem type, a software response exception type, a function implementation exception type, an operation experience type, and an interface problem type; The processing module is used to determine a response strategy corresponding to the functional review information according to the type of the review information, and process the function with abnormal problems in the target software product according to the response strategy.
9. An abnormal problem handling device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the abnormal problem handling method as claimed in any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the abnormal problem handling method according to any one of claims 1 to 7 are implemented.
