JP2004288151A - Operation history management device, operation history management method, and operation history management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an operation history management device, an operation history management method and an operation history management program for grasping each operation carried out with the execution of a plurality of application programs, as a common concept among the respective application programs. <P>SOLUTION: The conceptual meaning of each operation carried out with the execution of the plurality of application programs 11, 12, etc., is detected by a detecting part 21. Each detected result is stored as operation history information in a history information table 32. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an operation history management device, an operation history management method, and an operation history management program related to an artificial operation associated with execution of a plurality of programs.

  In a device equipped with a plurality of application programs, such as an application program for searching a Web page on a network in response to an operation of an operator and an application program for creating an electronic document in response to an operation of an operator, a history of artificial operations is stored. When trying to manage, it is common to collect an outline of each operation such as an operation name and an operation date and time.

  However, simply collecting the outline of each operation is not sufficient for managing the operation history.

On the other hand, there is a method that collects not only a superficial outline of each operation but also a history of how a series of operations have a dependency with each other (for example, Patent Document 1).
JP-A-10-21192

  However, in this example, each operation performed along with the execution of a plurality of application programs cannot be grasped as a common concept among the application programs.

  The present invention has been made in consideration of the above circumstances, and has an operation history management device capable of grasping, as a common concept, each operation performed along with execution of a plurality of application programs. It is an object to provide an operation history management method and an operation history management program.

  An operation history management device according to claim 1, wherein each time an artificial operation is performed along with execution of a plurality of programs, a detection unit that detects a conceptual meaning of each operation; And a storage unit for storing the respective detection results as operation history information.

  An operation history management method according to claim 6, wherein each time an artificial operation is performed along with execution of a plurality of programs, a step of detecting a conceptual meaning of each operation; Respectively as operation history information.

  The operation history management program according to the invention according to claim 8, comprising: a computer that detects a conceptual meaning of each operation each time an artificial operation is performed by executing a plurality of programs; Storing each detection result as operation history information.

  According to the present invention, an operation history management device, an operation history management method, and an operation history management method capable of grasping each operation performed along with execution of a plurality of application programs as a common concept among the application programs An operation history management program can be provided.

[1] Hereinafter, a first embodiment of the present invention will be described.

  As shown in FIG. 1, a Web application server 1 using a computer and a terminal (for example, a personal computer) 2 are connected via a communication network 3. The communication network 2 is further connected to a Web application server 4 and a number of Web servers 5.

  The Web application server 1 includes a program memory 10, an application program execution control unit 20, a detection unit (detection unit) 21, a search unit 22, a registration unit 23, an extraction unit 24, and a data memory (storage unit) 30.

  The program memory 10 stores a Web search application program 11, a memo creation application program 12, a document file management application program 13, a search application program 14, a registration application program 15, and the like. An operation history management program (not shown) is stored.

  The application program execution control unit 20 reads one or a plurality of application programs from the program memory 10 according to an instruction from the terminal 2, and executes the read one or a plurality of application programs. The data memory 30 stores a concept conversion rule table 31, a history information table 32, and various data groups 33.

  Each time one or a plurality of application programs are executed by the application program execution control unit 20 and an artificial operation by an operator is performed on the terminal 2 in accordance with the execution, the detection unit 21 executes the concept of each operation. Detect the meaning of meaning. Specifically, the outline of the operation (the name of the application program being executed, the operation date and time, etc.) is compared with each concept conversion rule in the concept conversion rule table 31 to obtain the “conceptual meaning” of each operation. (Referred to as semantic information). The detecting unit 21 stores each of the detected pieces of semantic information in the history information table 32 as operation history information.

  The search unit 22 searches one or more pieces of operation history information among the pieces of operation history information in the history information table 32 based on input information (keyword) from the terminal 2. Further, the search unit 21 displays and outputs one or a plurality of pieces of operation history information searched for on the display of the terminal 2. The processing of the search unit 21 is executed by the search application program 14.

  The registration unit 23 registers one or more new concept conversion rules input from the terminal 2 in the concept conversion rule table 31. The processing of the registration unit 23 is executed by the registration application program 15.

  The extraction unit 24 extracts a characteristic cooperation pattern of a plurality of operations related to each other from each operation history information in the history information table 32. Further, the extraction unit 24 displays and outputs the extracted cooperation pattern on the display of the terminal 2. The processing of the extraction unit 24 is also executed by the registration application program 15.

  Next, the operation will be described with reference to the flowcharts of FIGS.

  (1) Each operation performed along with the execution of the Web search application program 11 will be described.

  When the Web search application program 11 is started by accessing the Web application server 1 from the terminal 2, an operation screen for Web search shown in FIG. 4 is displayed on the display of the terminal 2. The operator of the terminal 2 inputs one or a plurality of keywords (character strings) into a character input window of the operation screen, and then clicks a Search button on the operation screen. This operation is notified to the Web application server 1.

  In the Web application server 1, every time each operation is performed on the terminal 2, the semantic information of each operation is detected (Step 102). That is, the outline of the operation is compared with each concept conversion rule in the concept conversion rule table 31 to detect the semantic information of each operation.

  As shown in FIG. 5, each concept conversion rule in the concept conversion rule table 31 includes items of “Application Name”, “Command”, “Type”, “Name”, “Context”, “Operation Type”, and “Operation Contents”. .

  As for the click operation of the Search button, the concept conversion rule on the first line is applied, and the operation of the Submit type Search button posted by the Web search application program is performed by using the WORDS notified by the Context as a search key. Was used to search for a Web page. "

  When the semantic information is detected (YES in step 103), the semantic information is included as operation history information together with the outline of the click operation of the Search button (name of the application program being executed, operation date and time, Operation Type, operator name, etc.). It is stored in the history information table 32 (step 104). FIG. 6 shows the operation history information of the Search button.

  When one or a plurality of Web pages are searched from each Web server 5 based on the input keyword, the URL of the searched one or more Web pages is changed as shown in FIG. Is displayed in the form of a list on the operation screen. The operator of the terminal 2 inputs a Check mark in an arbitrary Check box in the list and clicks the Browse button to view the Web page of the URL in the column where the Check mark is input on the display of the terminal 2. It is possible to do. When the operator of the terminal 2 inputs a Check mark in an arbitrary Check box in the above list and clicks the Cache button, the URL of the column in which the Check mark is input is cached as a document in the data memory 30. You.

  Every time the Browse button and the Cache button are clicked, the semantic information of each operation is detected (step 102).

  At the time of the click operation of the Browse button, the concept conversion rule in the second line in FIG. 5 is applied, so that the operation of the Submit type Browse button posted by the Web search application program is performed by the URL notified in the Context. For browsing the Web page of "."

  At the time of the click operation of the Cache button, the concept conversion rule in the second line in FIG. 5 is applied, so that the operation of the Submit type Cache button posted by the Web search application program is performed by the URL notified in the Context. Was created as a document. "Is detected.

  When semantic information is detected (YES in step 103), the semantic information is stored in the history information table 32 as operation history information together with an outline of the operation (step 104). That is, as shown in FIG. 7, following the operation history information of the Search button, the operation history information of the Browse button and the operation history information of the Cache button are stored.

  The operation history information of the Browse button includes the name of the Web search application program 11, the date and time when the Browse button was clicked, semantic information, Operation Type, and the operator name. The operation history information of the Cache button includes the name of the Web search application program 11, the date and time when the Cache button was clicked, the meaning information, the Operation Type, the path, and the operator name. The path indicates the storage location of the cached document.

  If there is no concept conversion rule suitable for the operation in the concept conversion rule table 31 and no semantic information can be detected (NO in step 103), only when the default conversion rule is set in advance (step 105) YES), only the operation summary is stored in the history information table 32 as operation history information (step 106). If the default conversion rule is not set in advance (NO in step 105), the operation history information is not stored.

  (2) Each operation performed along with the execution of the memo creation application program 12 will be described.

  When the memo creation application program 12 is started by accessing the Web application server 1 from the terminal 2, an operation screen for memo creation shown in FIG. 8 is displayed on the display of the terminal 2. The operator of the terminal 2 inputs text (character string) into a text box on the operation screen, and then clicks an OK button on the operation screen. This operation is notified to the Web application server 1.

  The text entered in the text box is stored as a document file in the data memory 30 by clicking the OK button.

  In the Web application server 1, every time an operation is performed on the terminal 2, the semantic information of each operation is detected (Step 102).

  At the time of clicking the OK button, the concept conversion rule on the fourth line in FIG. 5 is applied, so that the operation of the Submit type OK button posted by the memo creation application program is performed by the text notified in the Context. Was created as a document. "Is detected.

  When the semantic information is detected (YES in step 103), the semantic information is stored in the history information table 32 as operation history information together with the outline of the OK button click operation (step 104). That is, as shown in FIG. 9, the operation history information of the OK button includes the name of the memo creation application program 12, the date and time when the OK button was clicked, the meaning information, the Operation Type, the path, and the operator name. The path indicates the storage location of the document file.

  (3) Each operation performed according to the execution of the document file management application program 13 will be described.

  When the document file management application program 13 is started by accessing the web application server 1 from the terminal 22, an operation screen for document file management shown in FIG. 10 is displayed on the display of the terminal 2. On the operation screen, a plurality of folders stored in the data memory 30 are displayed in a tree shape. Each folder stores a number of document files.

  The operator of the terminal 2 specifies and opens an arbitrary folder among the displayed folders, specifies an arbitrary document file in the opened folder, and clicks the Check Out button. When the Check Out button is clicked, the specified document file is read from the specified folder in the data memory 30 and sent to the terminal 2. The document file sent to the terminal 22 can be edited by the operation of the operator.

  After the editing of the document file is completed, the operator of the terminal 2 clicks the Check In button. When the Check In button is clicked, the edited document file is sent to the Web application server 1 and updated and stored in the data memory 30.

  When the operator creates a new document on the terminal 2, the operator inputs a desired file name in a text box and clicks a New button. When the New button is clicked, the created document is sent to the Web application server 1 and stored in the data memory 30.

  In the Web application server 1, every time an operation is performed on the terminal 2, the semantic information of each operation is detected (Step 102).

  At the time of the click operation of the Check Out button, the concept conversion rule on the fifth line in FIG. 5 is applied, so that the operation of the Submit type Check Out button posted by the document file management application program is notified by Context. To start editing the document file at the specified path. "

  When the semantic information is detected (YES in step 103), the semantic information is stored in the history information table 32 as operation history information together with the outline of the click operation of the Check Out button (step 104). That is, the operation history information of the Check Out button includes, as shown in FIG. 11, the name of the document file management application program 13, date and time when the Check Out button was clicked, semantic information, Operation Type, path, and operator name. The path indicates the storage location of the document file.

  At the time of the click operation of the Check In button, the concept conversion rule on the sixth line in FIG. 5 is applied, so that the operation of the Submit type Check In button posted by the document file management application program is notified by the Context. This is for ending the editing of the edited document file. "

  When the semantic information is detected (YES in step 103), the semantic information is stored in the history information table 32 as operation history information together with the outline of the click operation of the Check In button (step 104).

  At the time of clicking the New button, the concept conversion rule on the seventh line in FIG. 5 is applied, so that the operation of the Submit type New button posted by the document file management application program is notified by the Context. It was for creating a new document newly. "

  When the semantic information is detected (YES in step 103), the semantic information is stored in the history information table 32 as operation history information together with the outline of the New button click operation (step 104).

  (4) A search process of each operation history information stored in the history information table 32 will be described.

  When a keyword for searching for operation history information is input from the terminal 2, one or more words in the input keyword are included in any of the items of each concept conversion rule in the concept conversion rule table 31. It is determined whether or not there is (Step 108). If it is included (YES in step 109), one or more pieces of operation history information including the word are searched from the history information table 32 (step 110). The retrieved one or more pieces of operation history information are sent to the terminal 2 and displayed on the display of the terminal 2 (step 111).

  The input keyword is a question sentence of a natural language having a conceptual meaning, for example, "What is a Web page browsed by Mr. XXX?" ]. This question sentence is linguistically analyzed to extract at least one word “browse”. If the extracted word “browse” is included in at least one item of each concept conversion rule, for example, Operation Type or Operation Content, one or a plurality of operation history information including the “browse” is stored in the history information table 32. Searched from.

  By displaying one or a plurality of pieces of operation history information retrieved in this manner on the display of the terminal 2, the operator can perform each operation performed along with the execution of the plurality of application programs between the application programs. It can be understood as a common concept.

  For example, when comparing the click operation of the Cache button with the execution of the Web search application program 11 and the click operation of the OK button with the execution of the memo creation application program 12, both of them have completely different operation outlines and Contexts. Both conceptual meanings can be understood to be the creation of a document.

  When at least one of the displayed one or more pieces of operation history information is specified by the operator (YES in step 112), at least one application program related to the specified operation history information is stored in the program memory 10. Is read by the application program execution control unit 20 and is automatically started (step 113).

  For example, when the operation history information of the Search button as shown in FIG. 6 is specified, the Web search application program 11 is automatically started based on the application program name included in the operation history information. With this activation, the work environment of the Web search is reproduced.

  The above search processing of the operation history information is executed by the search application program 14. The operation history information is also stored for each operation performed along with the execution of the search application program 14 by repeating the processing from step 101.

  (5) The process of registering a concept conversion rule in the concept conversion rule table 31 will be described.

  When the concept conversion rule registration mode is set on the terminal 2 (YES in step 114), each concept conversion rule already registered in the concept conversion rule table 31 is displayed on the display of the terminal 2 (step 115). In this state, when the operator specifies the concept conversion rule addition mode (step 116), one or more new concept conversion rules created on the terminal 2 by the operator are additionally registered in the concept conversion rule table 31. Is performed (step 117). This additional registration is appropriately performed when a new application program is added to the program memory 10 or the like.

  The above registration process is executed by the registration application program 15. The operation history information is also stored for each operation performed along with the execution of the registration application program 15 by repeating the processing from step 101.

  (6) A process of extracting a characteristic cooperation pattern of a plurality of operations related to each other from each operation history information will be described.

  When the cooperation pattern extraction mode is set on the terminal 2 (step 118), a characteristic cooperation pattern of a plurality of operations related to each other is extracted from each operation history information in the history information table 32. For example, "editing of a document file by the memo creation application program 12 is started, and thereafter, a Web page is searched and browsed by the Web search application program 11, and thereafter, editing of the document file by the memo creation application program 12 is ended. Is extracted as the most common cooperation pattern. The extracted cooperation pattern of the plurality of operations is displayed on the display of the terminal 2 (step 115).

The operator can derive semantic information (conceptual meaning) that "each operation was to edit a document file while referring to a Web page" with respect to the extracted cooperation pattern of a plurality of operations.
Then, based on the derived semantic information, the operator can create a concept conversion rule for a plurality of operations as shown in FIG. The created concept conversion rule can be additionally registered in the concept conversion rule table 31 by setting the registration mode.

  The above extraction processing and registration processing are executed by the registration application program 15. The operation history information is also stored for each operation performed along with the execution of the registration application program 15 by repeating the processing from step 101.

[2] A second embodiment of the present invention will be described.

  In the second embodiment, as shown in FIG. 14, the semantic information and the outline of each operation are stored in the history information table 32 as operation history information for each job, which is a set of a plurality of operations related to each other. Along with this, retrieval of each operation history information is also executed on a job basis.

  Other configurations, operations, and effects are the same as those of the first embodiment.

[3] The present invention is not limited to the above embodiment as it is, and can be embodied by modifying its components in an implementation stage without departing from the scope of the invention. Various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above embodiments. For example, some components may be deleted from all the components shown in the embodiment. Further, components of different embodiments may be appropriately combined.

FIG. 1 is a diagram illustrating a configuration of first and second embodiments of the present invention. 5 is a flowchart for explaining the operation of each embodiment. The flowchart following FIG. FIG. 4 is a diagram illustrating a web search operation screen according to the first embodiment. FIG. 4 is a diagram illustrating a format of each concept conversion rule according to the first embodiment. FIG. 7 is a diagram illustrating a format of one piece of operation history information regarding a Web search according to the first embodiment. FIG. 5 is a diagram illustrating a format of a plurality of pieces of operation history information related to a Web search according to the first embodiment. FIG. 6 is a diagram illustrating an operation screen for creating a memo according to the first embodiment. FIG. 7 is a diagram illustrating a format of a plurality of pieces of operation history information regarding memo creation according to the first embodiment. FIG. 7 is a diagram illustrating an operation screen related to document file management according to the first embodiment. FIG. 6 is a diagram illustrating a format of one piece of operation history information relating to document file management according to the first embodiment. FIG. 6 is a diagram illustrating an operation screen related to a history search according to the first embodiment. FIG. 9 is a diagram illustrating an example of a new concept conversion rule additionally registered in the first embodiment. FIG. 12 is a diagram illustrating a format of a plurality of pieces of operation history information collected in units of jobs according to the second embodiment.

Explanation of reference numerals

  REFERENCE SIGNS LIST 1 Web application server 2 Terminal 3 Communication network 5 Web server 10 Program memory 11 Web search application program 12 Memory creation application program 13 Document file management application program 14 Search Application program, 15: registration application program, 20: application program execution control unit, 21: detection unit (detection unit), 22: search unit, 23: registration unit, 24: extraction unit, 30: data memory (storage unit) ), 31: Concept conversion rule table, 32: History information table

Claims (9)

Detecting means for detecting the conceptual meaning of each operation, each time an artificial operation is performed along with execution of a plurality of programs;
Storage means for storing each detection result of the detection unit as operation history information,
Operation history management device characterized by comprising:   2. The operation according to claim 1, wherein the detection unit detects a conceptual meaning of each operation by comparing an outline of each operation with a plurality of concept conversion rules registered in advance. History management device.   2. The apparatus according to claim 1, further comprising a search unit configured to search and output one or a plurality of pieces of operation history information among the pieces of operation history information stored in the storage unit based on the input information. Operation history management device.   2. The operation history management device according to claim 1, further comprising an extraction unit configured to extract a characteristic cooperation pattern of a plurality of operations related to each other from each operation history information in the storage unit.   2. The storage device according to claim 1, wherein the storage unit stores a conceptual meaning of each operation detected by the detection unit as operation history information of a job unit including a set of a plurality of operations related to each other. Operation history management device as described. Detecting a conceptual meaning of each operation each time an artificial operation is performed along with execution of a plurality of programs;
Storing each of the detection results as operation history information,
An operation history management method comprising:   7. The method according to claim 6, wherein the detecting step detects a conceptual meaning of each operation by comparing an outline of each operation with a plurality of concept conversion rules registered in advance. Operation history management method. On the computer,
A procedure for detecting a conceptual meaning of each operation each time an artificial operation is performed along with execution of a plurality of programs;
Storing each of the detection results as operation history information,
Operation history management program for executing   9. The method according to claim 8, wherein the detecting step detects a conceptual meaning of each operation by comparing an outline of each operation with a plurality of concept conversion rules registered in advance. Operation history management program.

Images