JPH02236608A - Operation supporting system - Google Patents

Abstract

(57) [Summary] This bulletin contains application data before electronic filing, so abstract data is not recorded.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention relates to an operation support method for a software system used by a user, and in particular, it stores events that occur due to user operations as historical information, and stores historical information and rules. This paper relates to an operation support method that uses base knowledge to infer instructions that match the user's intentions. [Prior art] In the conventional technology, information to support the operation of the software used by the user, that is, messages for errors, guidance, and help, is limited to content fixedly prepared by the system side in response to events. It did not utilize the N history of operations. For example, as described in Japanese Unexamined Patent Publication No. 179016/1983, the correspondence relationship between help information and output messages is determined in advance, and when a message is issued, the information at that time is saved. , H h L 1) This is achieved by displaying help information with It) that was saved at the time the key was pressed. [Problems to be Solved by the Invention] The above-mentioned prior art does not give consideration to supporting the user's operations by flexibly providing information that matches the user's intention according to the user's operation status. In addition, the output information did not necessarily correspond to the user's desired operation, and its effects were not sufficient. The present invention solves the above-mentioned drawbacks and provides an operation support method that extracts instructions that match the user's intentions. Means for solving the commercial problem] The above purpose is to store events that occur due to user operations as historical information, and to output instructions suitable for the user's intention by reasoning using the historical information and a rule base. This is achieved through an operation support method. [Operation] As shown in FIG. 1, the operation support system according to the present invention includes a control section i, an H history information storage section 2, an inference mechanism 3, and a rule base 4.
Consists of. The control unit 1 investigates phenomena related to user operations, stores events 5 in the history information storage unit 2, and controls the execution of the inference mechanism 3. Event information 6 stored in the history information storage unit 2 is stored in the control unit 1
Comparison data 7 for making inferences according to the instructions of
As shown in Figure 2, it consists of the following elements. Function: Information that indicates the unit of processing Target: Information that indicates the target of the operation Human power code Value set for the two-person power item Parameter: Value set as a parameter Error cause: Number indicating the cause of the error Error message: Number indicating the type of error message Status: Information that indicates the state of processing Acquisition level: A value that indicates the stage of acquisition Frequency: A value that indicates the frequency of use of two functions The inference mechanism 3 is based on a rule-based language processing system, and solves problems according to instructions from the control unit 1. for rule base 4
Make inferences using knowledge 8. Rule base 4 is
It stores a set of rules written in a rule-type expression of ``rif condition then action.'' The rule condition section matches the history information with the rule, and the action section gives instructions when the conditions are met. Instruction 9 is output by control unit 1 to the user as instruction 10. [Example] Examples of the present invention are shown below. Embodiment 1 is an example of instructing an error message tailored to the user, and it is possible to instruct an error message according to the user's learning level. Second wU, what is the essence of the event that becomes historical information? ! 421 and its value 22. Figure 3 shows an example of rules for error message instructions depending on the user's learning level. In this example, the level of proficiency is expressed in five levels from level 1, beginner to level 5, expert.
Number 1 indicating that the cause of the error exceeded the allowable number of characters.
5, the error message differs depending on the learning level. Previously, the error message was simply displayed as "Incorrect specification", but now the user's level of proficiency for each operation is determined from historical information, and the error message is changed from simple to detailed based on the level of proficiency of the operation. By changing the error message to the following, it provides an error message appropriate to the user's operating level for each operation situation. This makes it possible to improve operability. Embodiment 2 is an example of providing guidance by rearranging function names according to the frequency of use. By displaying the function names frequently used by the user at the top, the efficiency of function search is improved. FIG. 4 shows a summary 41 of events serving as M history information and a value 42 of t.
is shown. Also, change the function name to qQ depending on the frequency of use. Figure 5 shows an example of rules for guidance. Previously, guidance for function names used in operations was displayed in a fixed order predetermined by the system, so if the function name to be used was displayed on a later screen, it was necessary to display that screen each time. . In this embodiment, by sorting and outputting the function names used in a certain process (in the example of Figure 5, processing of ledgers and slips) based on past history information, according to the frequency of use, the function names can be adjusted according to the user's operation. Guidance can be displayed, improving operability.

Embodiment 3 is an example of displaying the processing status. For example, when processing takes a long time, the screen does not change, so it is difficult to tell whether the processing is being performed normally or not. As a result, users feel psychologically uneasy. This embodiment has the effect of solving such operability problems. FIG. 6 shows event elements 61 and their values 62 that serve as KFD history information. Furthermore, an example of a rule for displaying the processing status is shown in Figure 7. Conventionally, once a process is executed, the screen state does not change until it is finished, so the user may not be able to determine whether the process is being executed, is in an error state, or has finished.

In this embodiment, while the process of a certain function (in the example of FIG. 7, the storage process in the ledger process) is being executed (the value of the status is set to ``executing''), it is indicated that it is [processing in progress]. Outputs the message to be displayed, and when the process is finished, "End"
By outputting a message indicating what has been done, it is possible to prevent the user from erroneous operation and at the same time relieve anxiety. Embodiment 4 is an embodiment in which errors are taught, correct operations and countermeasures for errors are instructed, and correction operations are facilitated. FIG. 8 shows a summary 81 of events serving as historical information and their values 82.
is shown. In addition, examples of rules for teaching countermeasures against errors are provided in Chapter 9.
It is shown in the figure. In conventional technology, when an error occurs, a message is often output that only indicates that an error has occurred, and the same error message does not tell the user that the countermeasures they should take will differ depending on the cause. Figure 9 is an example showing how the error countermeasures for the same specification error differ depending on the cause.The processing function is storage processing for ledger processing, the target of user operation is the table name, and the error message indicates the specification error. When the number 100 indicates that the cause of the error is a character attribute and an error in the number of specifications, number 10 indicates an error in the number of specifications, and number 15 indicates an error in the number of specifications.This is a case where different error countermeasures are taught depending on the cause of the error. This allows the user to perform appropriate operations in response to errors, improving operability. [Effects of the Invention] In the operation support method according to the present invention, events that occur when a user operates a software system are stored as history information, and based on the history information and rule-based knowledge, finger movements that match the user's intentions are created. By inferring this, it is possible to specify the display of error messages, guidance display, processing status display, error countermeasures, etc. that match the user's operating level.

[Brief explanation of drawings]

Fig. 1 is a system configuration diagram of an embodiment of the present invention, Fig. 2 is a diagram showing an example of event elements and their values that serve as history information in the embodiment of the present invention, and Fig. 3 is a diagram illustrating user learning. Diagram 4 showing an example of a rule that instructs error messages depending on the degree of error.
The figure shows an example of elements of events that serve as history information and their values in an example in which functions are rearranged according to frequency of use for guidance. Figure 5 shows an example of rearranged functions according to frequency of use and their values. FIG. 6 is a diagram showing an example of the rules for guidance. FIG. 6 is a diagram showing an example of event elements and their values that serve as history information in an example of displaying the processing status. FIG. 7 is a diagram showing an example of displaying the processing status. FIG. 8 is a diagram showing an example of the elements of an event serving as history information and their values in an example of teaching an error target, and FIG. 9 is a diagram showing an example of error countermeasures. FIG. 2 is a diagram illustrating an example embodiment of rules for teaching. DESCRIPTION OF SYMBOLS 1... Control unit, 2... History information storage unit, 3... Reasoning mechanism, 4... Rule base, 5... Event, 6...
・Event information, 7... Comparative data, 8... Knowledge, 9.
10... Instructions. Figures Collection Figures A Figure S Cause Figures Collection Musu 15! li

Claims (1)

[Claims] 1. In an operation support method for a software system used by a user, operation events that occur in the target software are stored as historical information, and the historical information and rule base are used to provide information that is suitable for the user's intentions. An operation support method characterized by inferring instructions. 2. Enter the operation events that occur in the target software,
A control unit that stores events in the history information storage unit and controls the execution of the inference mechanism, a history information storage unit that stores events of input operations, and rules written in rule-type expressions of “if condition then action” and an inference mechanism that uses history information and the rule base to infer instructions suitable for the user's intention according to instructions from the control unit. Section description operation support method.