JP2008090418A - File management device and file management method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a file management device for efficiently browsing files strongly related files according to each state in dealing a task. <P>SOLUTION: Browsing history information 60 of failure slips is acquired from a browsing history database 13 in coping with the failure slips stored in a failure slip management server 11. Acquiring a coefficient value information 80 of relevance intensity, and using a browsing hour 607 of the value information 80 and the browsing history information 60 calculation of the relevance intensity is performed. Documents related to the failure slips are displayed in order of the calculated relevance intensity. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a file management apparatus and a file management method for managing a file related to a task including a plurality of states.

  Conventionally, a file management apparatus that manages work processes such as software development associates a plurality of digitized documents and drawing data with a failure slip for a product under development / evaluation and manages it with a computer or other computer device Is done. A plurality of users can browse associated documents and drawing data.

  In general, a development process for a software program, a precision instrument, and the like is provided with a period (process) for evaluating the function by some method, correcting and improving the function. Such a process is called a test process. For example, in a test process in software program development, a tester tests whether the software program functions correctly according to the required specifications. In this test, if an error is found in the operation of the target software program, it is assumed that a failure has occurred. In this case, data describing the content of the failure that has occurred, called a failure slip, is created.

  In general, a trouble ticket workflow (called a process) consists of trouble tickets in a test process as a task, and each work from creation to handling / end is arranged according to the work order, and occurs from the start to the end. Each task to be performed is defined as a state. The failure vote workflow includes at least a state involving a tester in charge of a test and a state involving a developer of a software program for correcting a failure that has occurred in this test.

  For example, the failure slip 180 (see FIG. 4) holds details regarding the content of the failure that has occurred, the countermeasure, and the confirmation of the countermeasure. The failure slip 180 includes basic information such as a failure slip identifier 1801, a workflow state 1802, a person in charge 1803, and the like. Each evaluation 1804, 1805, and 1806 describes the contents and correspondence of the failure in each state.

  A workflow system that manages and browses such a trouble ticket workflow includes a server and a plurality of clients. In this workflow system, a list of work for each individual called a work list is displayed on each client. Further, a form or document for performing a selected job is displayed / edited from the work list.

  In addition, as this type of system, an apparatus has been proposed that associates work files from work histories so that even inexperienced users can view documents efficiently (see Patent Document 1). ). This apparatus stores a history of browsing a document by a user together with a user name in a browsing history database. Furthermore, from the individual browsing histories stored in the browsing history database, the browsing order information of other documents viewed by the user before and after is stored in the browsing order database. When a user views a document, the degree of similarity between the current user and the past user is obtained from the viewing order database and the user registration database, and information on documents closely related to the document to be viewed before and after that is viewed. Generate and present as navigation information. The user work support is realized by such a procedure.

As another system, a device that calculates and displays the relationship strength according to the display state (CLOSE, OPEN, SUBWINDOW, etc.) of the link destination node referenced by the hypertext in the document displayed on the node. Is known (see Patent Document 2). Thereby, the user can grasp the relation strength between documents.
JP 2004-145509 A JP-A-7-282059

  However, the conventional file management apparatus has the following problems. That is, in Japanese Patent Laid-Open No. 2004-228867, a case where a document related to a state changes every time a work point of the workflow, that is, a state transitions, is based on the task from the creation to the end of a failure form, as in the case of a trouble form workflow. Nothing was considered. For this reason, there is a possibility that the navigation information to the related document may be different from the navigation information actually required by the user.

  Further, in Patent Document 2, unless the hypertext is displayed on the screen, the related strength cannot be given to the document.

  Therefore, an object of the present invention is to provide a file management apparatus and a file management method that allow a user to browse a file efficiently by presenting a strongly related file in accordance with the state transition.

  In order to achieve the above object, a file management apparatus according to the present invention is a file management apparatus that manages a file related to a task including a plurality of states, and that obtains coefficient value information for each state of the task. An information acquisition means, a related strength calculation means for calculating a related strength for each state using the acquired coefficient value information, and a file related to the task in order of the related strength calculated for each state are displayed. And a file display means.

  The file management method of the present invention is a file management method for managing files related to a task having a plurality of states, the coefficient value information acquiring step for acquiring coefficient value information for each state of the task, and the acquired Using the coefficient value information, a related strength calculating step for calculating the related strength for each state, and a file display step for displaying a file related to the task on the display device in the order of the related strength calculated for each state. It is characterized by having.

  According to the file management apparatus of the first aspect of the present invention, coefficient value information is acquired for each task state, and using the acquired coefficient value information, a related strength is calculated for each state. Files related to the task are displayed in the order of the calculated relation strength. Therefore, when a user responds to a task, a highly relevant file can be browsed efficiently according to each state.

  According to the file management apparatus of the second aspect, the user's intention can be reflected. According to the file management apparatus of the third aspect, the user browsing history can be reflected. According to the file management apparatus of the fourth aspect, it is possible to efficiently browse strongly related files in units of groups to which the user belongs. According to the file management apparatus of the fifth aspect, an appropriate browsing time can be used as the browsing history.

  Embodiments of a file management apparatus and a file management method of the present invention will be described with reference to the drawings. The file management apparatus according to the present embodiment is applied to a related document browsing management system including a client / server system.

[First Embodiment]
FIG. 1 is a diagram showing a configuration of a related document browsing management system in the first embodiment. This related document browsing management system includes a client / server system connected via a network (intranet / Internet) 2. As a server, a failure slip management server 11, a document management server 12, and a browsing history database 13 are provided. On the other hand, a plurality of related document browsing devices 31, 32, and 33 are provided as clients. In FIG. 1, three related document browsing devices are connected, but the number is not particularly limited.

  The related document browsing devices 31, 32, and 33 are configured by a personal computer (PC) or a mobile PC, and have an information processing operation function that holds and manages digitized signals and information. Since the related document browsing devices 31, 32, and 33 have the same configuration, the related document browsing device 31 will be described as a representative here.

  FIG. 2 is a diagram showing a functional configuration of the related document browsing apparatus 31 in the present embodiment. The related document browsing device 31 includes a display device 311, an input device 312, and an arithmetic processing unit 313. The arithmetic processing unit 313 is provided with a hint information control unit 3131, a failure slip control unit 3132, a related strength control unit 3133, a coefficient control unit 3134, a browsing time measurement unit 3135, and a browsing history information control unit 3136. Although the relationship strength will be described later, in the present embodiment, it is assumed that a document having a higher relationship has a higher relationship strength.

  The coefficient control unit 3134 includes a coefficient setting unit 31341 and coefficient information 31342. In addition to having a timer function, the browsing time measuring unit 3135 includes a browsing time acquisition unit 31351 and a measurement status control unit 31352. In the present embodiment, the browsing history information control unit 3136 is held in the related document browsing device 31, but may be held on the server side. The functions of these units are realized by the CPU executing a control program stored in a storage medium in the PC.

  On the other hand, on the server side, the failure slip management server 11 has a failure slip management database 111. The document management server 12 has a document management database 121.

(Failure slip workflow)
FIG. 3 is a diagram showing a trouble ticket workflow in the present embodiment. As described above, the failure slip workflow is a task in which the failure slip in the test process is regarded as one task, and the operations from the creation to the failure handling and the end of the handling are arranged according to the work order. Each operation that occurs from the start to the end is defined as a state. In the drawing, reference numerals P111, P121, P122, P123, P131, P132, and P141 indicate states on the workflow. Reference signs P11 to P14 indicate phases in which the states are classified according to their properties. The workflow consists of one process P1, and holds each state P111 to P141 and the phases P11 to P14 to which each state belongs.

  Specifically, the phase P11 is an evaluation phase in which a certain system / device / software / process is evaluated and a failure slip is issued. Phase P12 is a failure handling phase in which the occurrence of a failure is confirmed from the contents of the failure slip created in phase P11 and the failure is corrected. The phase P13 is a handling confirmation phase that is found in the phase P11, confirms that the handling of the fault is finished in the phase P12, and the same fault does not occur. The phase P14 is an end phase in which the failure is dealt with and finished when the confirmation of the failure handling is completed in the phase P13.

  This workflow is an example, and the number, name, and role of each state, phase, and process are changed as necessary.

(User interface (UI))
FIG. 4 is a diagram showing a failure slip in the development of the software program in the present embodiment. The failure slip 180 holds details regarding the content of the failure that has occurred, how to handle it, and confirmation of the response. The failure slip 180 includes basic information such as a failure slip identifier 1801 for identifying a failure, a workflow state 1802, and a person in charge 1803. In each evaluation phase 1804, 1805, and 1806, the contents and correspondence of the failure in each state are described.

  FIG. 5 is a diagram showing a main UI screen displayed on the display device 311 in the present embodiment. On the main UI screen 190, referred to as “work hint”, the failure tag number or failure ticket identifier 1901 of the designated corresponding failure slip, the document name of the related document 1902, and the selection switching of the corresponding failure slip are displayed. A button 1903 is provided. In addition, a setting button 1904 is provided for setting a coefficient for each state and setting the number of related documents to be displayed.

  Further, the failure slip identifier 1901 is a link to the failure slip, and the screen of FIG. 4 is displayed in response to a user operation. The display order of the related documents 1902 is in the descending order of the related strengths calculated according to the related strength calculation procedure. The document name of the related document 1902 is a link to the document body, and the document body is displayed in response to a user operation.

(Designated UI for disability slip)
FIG. 6 is a diagram showing a UI screen for designating a failure slip displayed in the failure slip number or failure slip identifier 1901 in this embodiment. This UI screen 200 is displayed when the corresponding failure slip selection switching button 1903 is selected. On this UI screen 200, an input field 2001 for designating a failure slip, a button 2002 for displaying a list of failure slips that have been designated in the past by the user as a [failure slip currently supported], and a failure slip search. A search button 2003 is set. In addition, an OK button (designation button) 2004 for designating the designated trouble slip as [handling trouble slip] and a cancel button (cancel button) 2005 for interrupting the designation of the trouble slip are set. The user can search for a failure slip held in the failure slip management server 11 using the search button 2003.

(Coefficient value setting UI)
FIG. 7 is a diagram showing a UI screen for setting coefficient values in the present embodiment. The coefficient in the present embodiment is a weight for calculating the related strength of a document. The UI screen 210 is displayed when a setting button 1904 is selected by a user operation and a coefficient value setting is further selected. In the UI screen 210, a process 2101 to which the trouble slip being handled belongs and a coefficient list 2102 for calculating the relation strength are set. In the coefficient list 2102, a state transition order 21021, a state 21022, and a coefficient value 21023 are displayed. An OK button 2103 is a button for reflecting the coefficient value changed by the coefficient value 21023. A cancel button 2104 is used when it is desired to cancel the change.

  In the state 21022, each state in the workflow held in the process 2101 is displayed. The transition order 21021 displays the transition order of each state in the normal flow on the workflow. The coefficient value 21023 displays the coefficient value currently set for each state. When it is desired to change the coefficient value, the user uses the input device 312 to change the value of the coefficient value 21023. Thereby, a user's intention can be reflected.

(Configuration of browsing history information)
FIG. 8 is a table showing the browsing history information 60 of the failure slip “Problem001”. The browsing history information 60 is registered in the browsing history database 13. In the browsing history information 60, history information of a document browsed at the time of browsing / editing the trouble ticket “Problem001” is held. The failure slip “Problem001” represents a failure slip designated by the user. As the history information of the document, a history number 600, a browsed document ID 601, a document name 602, and a browsed document storage location 603 are stored. In addition, the status 604 of the trouble form “Problem001” when viewing the document, the operator 605 of the trouble form “Problem001” when viewing the document, and the person in charge 606 of the trouble form “Problem001” when viewing the document are held. Further, a document browsing time 607, a browsing start time 608, and a browsing end time 609 are held.

  FIG. 9 is a table showing the coefficient management information 70. The coefficient management information 70 is included in the coefficient information 31342 in the related document browsing device 31. The coefficient management information 70 is managed in units of processes to which the failure forms designated in [Handling Failure Forms] in the “work hint” (see FIG. 5) belong. The coefficient management information 70 stores a number 700, a process ID 701, a workflow (WF) type 702, a coefficient information ID 703, and a coefficient last update date and time 704.

  FIG. 10 is a table showing coefficient value information 80 associated with the process ID of FIG. The coefficient value information 80 is included in the coefficient information 31342 in the related document browsing device 31. The coefficient value information 80 includes a number 800, a state ID 801, a state 802 corresponding to the state ID 801, an addition coefficient 803 for the browsing time of each state 802 identified by the state ID 801, a coefficient last update date and time 804, and a last updater 805. Is retained. The role of the addition coefficient 803 will be described later.

  The coefficient information 31342 (see FIG. 2) is a combination of the coefficient management information 70 (see FIG. 9) and the coefficient value information 80 (see FIG. 10).

  The operation of the related document browsing apparatus 31 having the above configuration will be described.

(Designation of disability slip)
FIG. 11 is a diagram showing the flow of processing when the user designates a failure slip to be viewed / edited using the input device 312 of the browsed document management device 31. When a failure slip is designated by a user operation (T400, T401), the hint information control unit 3131 receives the designated information. Thereafter, the hint information control unit 3131 uses the failure slip control unit 3132 to access the failure slip management server 11 and acquires information such as the ID / URL of the designated failure slip (T402, T403).

  The hint information control unit 3131 accesses the browsing history database 13 using the browsing history information of the browsing history information control unit 3136 with the information of the failure slip “Problem001” having the failure identifier acquired in T402 and T403 as a key. Then, the browsing history information 60 of the trouble ticket “Problem001” (see FIG. 4) is acquired (T404, T405).

  The hint information control unit 3131 acquires list information of already opened documents in the related document browsing apparatus 31 in which the “work hint” (see FIG. 5) which is the main UI screen is activated (T406). For the already opened document acquired in T406 and the document included in the browsing history information 60 acquired in T404 and T405, information on whether or not the document belongs to the document management server 12 is acquired for each document. (T407).

  Based on the document affiliation information acquired in T407, a link enabled / disabled state is set for each document (T408). That is, if the document is managed by the document management server 12 or the document is held in the browsed document management apparatus 31, the link is set to be permitted. On the other hand, if the document is not managed by the document management server 12 and is not held in the browsed document management apparatus 31, it is determined that the document is not related to the failure slip, and the link is disabled.

  The hint information control unit 3131 starts processing for determining the display order of documents related to the failure slip “Problem001” based on the browsing history information 60 acquired in T404 and T405. The hint information control unit 3131 determines, for each related document of the failure slip “Problem001”, a coefficient for calculating the related strength using the coefficient control unit 3134 as a browsing time history unit. Then, the strength of association is calculated using the determined coefficient and browsing time (T409, T410, T411). A specific calculation method will be described later.

  The relation strength control unit rearranges the calculated relation strengths in descending order, and passes the order information to the hint information control unit 3131 (T412). The hint information control unit 3131 is based on the browsing history information 60 acquired in T404 and T405, the order information of the related strength ordered by the related strength control unit 3133 in T412, and the link enable / disable information for each document set in T408. The contents to be displayed in the “work hint” are determined (T413). The information determined in T413 is output to the display device 311 (T414). Thereafter, the browsing time measurement unit 3135 starts browsing time measurement for the already opened document acquired in T406 (T415).

(Deletion of disability vote)
An operation when the processing of the trouble ticket “Problem 001” is terminated in a situation where the trouble ticket “Problem 001” is designated as [Handling trouble ticket] is shown. FIG. 12 is a diagram showing a processing flow when the user cancels the designation of the trouble ticket using the input device 312 of the browse document management device 31. Here, it is assumed that the trouble slip “Problem 001” is specified in “Handling trouble slip” in “Work hint” (see FIG. 5), and the trouble slip “Problem 001” is opened.

  First, the user issues an instruction to close the trouble ticket “Problem001” using the input device 312 (T500, T501). In response to the instruction, the hint information control unit 3131 issues an instruction to release the link between the “work hint” and the failure slip “Problem001” to the failure slip control portion 3132 (T502, T503). The hint information control unit 3131 uses the browsing history information control unit 3136 to acquire browsing time history information regarding the failure slip “Problem001” (T504, T505).

  The hint information control unit 3131 instructs to stop measuring the browsing time of the related document based on the browsing time history information acquired at T504 and T505 (T506). When receiving the instruction, the browsing time measuring unit 3135 stops measuring the browsing time of the related document (T507).

  The hint information control unit 3131 uses the browsing history information control unit 3136 to access the browsing history database 13 and updates the browsing history information of the failure slip “Problem001” on the server (T508, T509). Then, the display content of “work hint” is updated (T510). In this update of the display content, [corresponding failure slip] is not specified, so on the main UI screen (see FIG. 5), the failure slip number or failure slip identifier 1901 of the failure slip being handled and the document name of the related document are displayed. 1902 is displayed in a closed state.

(Corrective action)
FIG. 13 is a flowchart showing an operation processing procedure when the browsing document management apparatus 31 activates “work hint” by the user's operation and designates a failure slip to be browsed / edited for correspondence. This processing program is stored in a storage medium in the PC constituting the related document browsing apparatus 31, and is executed by the CPU.

  When the user uses the UI screen 200 (see FIG. 6) for specifying the failure slip, when the failure slip is specified by the user, the hint information control unit 3131 acquires the specified failure slip (step S2201). Then, the browsing history information 60 of the document related to the failure slip is acquired (step S2202).

  Using the browsing history information 60, information such as the ID and storage location of the document related to the failure slip is acquired (step S2203). Next, the coefficient control unit 3134 obtains a relevance coefficient from the coefficient information 31342 (step S2204). Then, using the obtained association degree coefficient (coefficient value information), the association strength is calculated for all the documents obtained in step S2203 (step S2205). Based on the calculated relation strength, the related documents are ordered (step S2206). In accordance with the ordered order, the related document information is displayed in the “work hint” (step S2207). Then, this process is complete | finished.

(Relation strength calculation and ordering)
Next, processing for calculating the relation strength for all the documents related to the trouble slip “Problem001” and ordering them will be described. FIG. 14 is a flowchart showing a processing procedure for acquiring coefficient value information in steps S2204, S2205, and S2206, calculating a related strength, and ordering related documents.

  When a related strength calculation command is issued from the hint information control unit 3131 to the related strength control unit 3133 (see T409 in FIG. 11), first, the related strength control unit 3133 displays the process ID of the process to which the failure slip “Problem001” belongs. Is acquired (step S901). Then, a coefficient value information acquisition command is issued to the coefficient control unit 3134. When receiving the coefficient value information acquisition command, the coefficient control unit 3134 acquires the coefficient value information (step S902). The coefficient value information acquired in step S902 is coefficient value information set in step S1008 or step S1003 described later. When acquiring the coefficient value information 80, the related strength control unit 3133 acquires the state of the process on the WF from the coefficient value information 80 (step S903).

  A history corresponding to the state acquired from the browsing history information 60 is acquired (step S904), and the related strength of each document is calculated (step S905). It is determined whether or not the processing of S904 and S905 has been completed for all the acquired states (step S906). If not completed, the process returns to step S904. On the other hand, if the processing has been completed, the related strengths of each document are ordered (step S907). When the related strength control unit 3133 calculates the related strength of each document, the related strength control unit 3133 rearranges the document IDs in the order of strong relationship. Then, this process is complete | finished.

  FIG. 15 is a flowchart showing a procedure for acquiring the coefficient value information 80 in step S902. The coefficient control unit 3134 confirms whether or not the process information specified by the process ID exists in the coefficient management information 70 (step S1001).

  If this process information exists in the coefficient management information 70, the coefficient control unit 3134 acquires the coefficient ID 703 using the given process ID as a key (step S1002). Using the coefficient ID 703 acquired from the coefficient management information 70 as a key, the process coefficient value information is acquired from the coefficient value information 80 (step S1003). Then, this process is complete | finished.

  On the other hand, if the process information does not exist in the coefficient management information 70 in step S1001, the hint information control unit 3131 receives the information and confirms whether or not to set the process browsing history addition coefficient. An instruction to display a UI is issued (step S1004). Upon receiving this instruction, the display device 311 displays a confirmation UI (step S1009).

  The display device 311 waits to receive an input from the user via the confirmation UI (step S1010), and when the input is received, passes the input information (Yes / No) to the hint information control unit 3131.

  Upon receiving the input information (Yes / No), the hint information control unit 3131 generates coefficient information and sets a default value (step S1005). Then, it is confirmed whether the input information is Yes or No (step S1006). If the input information is Yes, a coefficient is set (step S1007), and the coefficient control unit 3134 acquires the set coefficient value information. (Step S1008). On the other hand, in the case of No, the processing proceeds to step S1008 as it is. Then, this process is complete | finished.

(Relation strength calculation)
FIG. 16 is a flowchart showing the related strength calculation processing procedure in step S905. Here, among the history items of the browsing history information 60, the number is “No. 096-No. 104 will be used for the description. Further, it is assumed that the state 604 is “Failure handling”.

  First, the related strength control unit 3133 acquires the coefficient setting information 803 in the “handling of failure” state from the coefficient value information 80 (step S1101). Here, 1 / (ln + 1) (where ln is the order in which histories in the same state are arranged in order from the latest history) is acquired.

  According to the obtained coefficient value setting information, the history item No. of the browsing history information 60 is displayed. 096-No. A coefficient is assigned to 104 (step S1102). The coefficient value information is 1 / (ln + 1). In the case of 104, since ln is 1, the coefficient is 1/2. When calculated in the same manner, no. 103 for 1/3,. 096 is 1/10.

  Subsequently, all history item Nos. 096-No. For 104, the process proceeds to a process for calculating the relevance strength of the document for each history item. This calculation is performed by integrating the document reference time 607 held in each history item and the coefficient assigned in step S1102 (step S1103). Next, the document ID held by the history item is acquired (step S1104), and the related strengths of other documents having the same document ID are added (step S1105). This addition processing is realized by providing a temporary storage variable of related strength and performing addition processing on this variable.

  Thereafter, it is determined whether or not the processing has been completed for all the history items (step S1106). When the processing has been completed, this processing is terminated. On the other hand, if not completed, the process returns to step S1103.

(Generate coefficient information and set default values)
FIG. 17 is a flowchart showing a procedure for generating coefficient information and setting default values in step S1005. Here, as described above, the coefficient information includes coefficient management information 70 and coefficient value information 80.

  The hint information control unit 3131 transmits a command for acquiring the WF information of the process specified by the process ID 701 to the failure control unit 3132 (step S1201). Here, the WF information is the WF type, all the states held by the WF, the order on the workflow for each state, and phase information.

  The failure control unit 3132 transmits the WF information acquisition command received from the hint information control unit 3131 to the failure slip management server 11, and acquires WF information from the failure slip management server 11 (step S1202). The failure slip management server 11 acquires WF information of the designated process (step S1203).

  When the hint information control unit 3131 receives the WF information acquired by the failure slip management server 11, the hint information control unit 3131 generates a coefficient value of this process (step S1204). When the coefficient control unit 3134 receives the coefficient value of the process from the hint information control unit 3131, the coefficient control unit 3134 generates a coefficient ID of the received process (step S1205).

  The process ID of this process, the coefficient ID generated in step S1205, the WF type, and the current time are added to the coefficient management information 70 (step S1206). The coefficient control unit 3134 generates coefficient value information 80 based on the coefficient ID generated in step S1205, and adds the state IDs and states of all states of the WF to the coefficient value information 80 (step S1207). At this time, the last update date is the current time, and the last updater is System. Then, a coefficient value is set in each state of the coefficient value information 80 (step S1208). The value set here is as shown in Equation (1).

1 / (ln + 1) (1)
In addition, ln is a history number when the history in the same state is arranged in order from the latest history.

(Coefficient information setting section)
FIG. 18 is a flowchart showing a coefficient setting processing procedure for setting a coefficient value for each state in the process P1 to which the failure slip “Problem001” belongs in step S1007. First, the hint information control unit 3131 confirms whether or not the process for setting the coefficient value already holds the coefficient information 31342 (step S1301). If the coefficient management information 70 holds a process ID, it is determined that this process holds coefficient information.

  If the process holds coefficient information, the hint information control unit 3131 transmits a command to acquire coefficient value information to the coefficient control unit 3134 (step S1302). The coefficient control unit 3134 acquires the coefficient management information 70 (step S1303), and acquires the coefficient value information 80 (step S1304). On the other hand, if the process does not hold the coefficient information 31342 in step S1301, the coefficient information shown in FIG. 17 is generated and a default value is set (step S1312), and the process proceeds to step S1302.

  The hint information control unit 3131 transmits the coefficient value information acquired in step S1304 to the display device 311 together with a command for displaying a coefficient value setting UI (step S1305).

  Upon receiving the information transmitted in step S1305, the display device 311 displays a coefficient setting UI based on this information (step S1306). The setting UI displays at least the entire state of the process and the coefficient value for each state, and holds an information transmission unit for updating the coefficient.

  The display device 311 waits until an event for instructing processing is received from the user (step S1307). When the event is received, the display device 311 distributes the processing according to the content. That is, it is determined whether or not the content of the event is an update instruction (step S1308). If the event is an update instruction, the display device 311 transmits coefficient value update information to the hint information control unit 3131 (step S1309). ).

  When the hint information control unit 3131 receives the update information, the hint information control unit 3131 transmits a coefficient value setting command to the coefficient control unit 3134 (step S1310). When the coefficient control unit 3134 receives the update information of the coefficient value from the hint information control unit 3131, the coefficient control unit 3134 acquires the coefficient value for every state from the received update information, and sets the value in the coefficient value information 80 ( Step S1311). Then, this process is complete | finished.

  On the other hand, if the content of the event is not an update instruction, it is determined whether or not it is a process cancellation instruction (step S1313). If the instruction is to cancel the process, the process is terminated. On the other hand, if it is not a cancel instruction, the process returns to step S1307.

(Browsing time measurement)
When the trouble slip “Problem001” is designated as “work trouble slip” in “work hint”, a method of measuring the browsing time when the document D1 (see FIG. 5) is opened is shown. FIG. 19 is a flowchart showing a browsing time measurement start processing procedure. This processing program is stored in a storage medium in the related document browsing apparatus 31, and is executed by the CPU.

  Here, the browsing time is a time during which a related document is being browsed when a trouble ticket designated in [Handling trouble card] is opened in the “work hint”. Further, the related document is a document opened together when the failure slip is opened. Further, “opened together” means a state in which a display area and a display layer such as a document window are not hidden by a display area and a display layer of another document. In the case where the display area is minimized, during the screen saver activation or the screen lock activation, it is determined that “not opened” and the browsing time is not measured during this time. The document D1 is a document held and managed by the document management server 12. By performing the processing as described above, the related strength can be calculated based on the substantial browsing time, so that the calculation accuracy is improved. Thus, the user can easily access related documents.

  First, when the document D1 is opened, the hint information control unit 3131 acquires information on this document (step S1401). At this time, the acquired information includes a document ID, a document name, a last update date, and the like.

  When receiving the document information acquisition command from the hint information control unit 3131, the document management server 12 on the server side acquires information on the designated document and transmits it to the hint information control unit 3131 (step S1402). The hint information control unit 3131 issues a command for generating a timer for measuring the browsing time of the document D1 to the browsing time measuring unit 3135 (step S1403).

  Upon receiving the timer generation command, the browsing time measuring unit 3135 generates a timer and issues a timer ID (step S1404). Measurement status information is added to the generated timer (step S1405). When the timer generation process ends, the hint information control unit 3131 issues a measurement start command to the browsing time measurement unit 3135 (step S1406). Upon receiving the measurement start command, the browsing time measuring unit 3135 uses the measurement status control unit 31352 to change the measurement status held by the timer generated in step S1404 to “being measured” (step S1407). The browsing time measurement unit 3135 starts timer measurement using the browsing time acquisition unit 31351 (step S1408). Then, this process is complete | finished.

(End of measurement)
FIG. 20 is a flowchart showing a browsing time measurement end processing procedure. This processing program is stored in a storage medium in the related document browsing apparatus 31, and is executed by the CPU. When the document D1 is closed, the hint information control unit 3131 acquires a timer ID from the document ID of this document (step S1501), and issues a command to stop the timer measurement to the browsing time measurement unit 3135 (step S1502).

  Upon receiving this timer measurement stop command, the browsing time measuring unit 3135 changes the timer measurement status to “stop” (step S1503), and stops timer measurement (step S1504). The hint information control unit 3131 issues a document browsing time acquisition instruction using the timer ID acquired in step S1501 as a key (step S1505). Upon receiving a browsing time acquisition instruction from the hint information control unit 3131 in step S1505, the browsing time measurement unit 3135 acquires the time held by the timer and transmits it to the hint information control unit 3131 (step S1506).

  Upon receiving the document browsing time, the hint information control unit 3131 adds the document browsing time history to the browsing time history information 60 (see FIG. 8) of the failure form “Problem001” (step S1507).

  Upon receiving the browsing time history addition command, the browsing history information control unit 3136 accesses the browsing history database 13 and gives an instruction to acquire browsing time history information of the failure slip “Problem001” (step S1508). The browsing history database 13 acquires browsing time history information and returns it to the browsing history information control unit 3136 (step S1509).

  The browsing history information control unit 3136 adds information (see FIG. 8) such as the document ID 601 and the browsing time 607 to the browsing time history information 60 of the acquired failure slip “Problem001”, and updates the browsing time history information 60 (step). S1510). An instruction to save the updated browsing time history information 60 in the browsing history database 13 is issued (step S1511). The browsing history database 13 updates browsing history information (step S1512). Thereafter, the browsing time measuring unit 3135 releases the timer that has been measuring the browsing time of this document (step S1513), and ends this process.

(Pause measurement and resume measurement)
FIG. 21 is a flowchart showing a procedure for pause processing for browsing time measurement. This processing program is stored in a storage medium in the related document browsing device 31, and is executed by the CPU when an event for temporarily stopping the browsing time measurement occurs. Here, the event for temporarily stopping the measurement is that the display area of the document D1 (display area) is minimized, the display area is hidden behind the display area of another file or document, and the screen saver is activated. Or it is a change in the state such as the screen being locked.

  When these events occur, the hint information control unit 3131 acquires the timer ID of the document (step S1601), and issues a timer measurement stop command (step S1602). Upon receiving the timer measurement stop command, the browsing time measuring unit 3135 changes the measurement status to “pause” (step S1603) and stops the measurement (step S1604). Then, this process is complete | finished.

  FIG. 22 is a flowchart showing a resumption processing procedure of browsing time measurement that has been paused. This processing program is stored in a storage medium in the related document browsing device 31, and is executed by the CPU when an event occurs in which browsing time measurement is resumed. Here, the event for which measurement is resumed is a change in the state in which the situation generated by the event for which measurement is stopped is released.

  The hint information control unit 3131 acquires the timer ID of the document (step S1701), and issues a timer measurement start command (step S1702). Upon receiving the measurement start command, the browsing time measuring unit 3135 changes the measurement status to “under measurement” (step S1703) and starts measurement (step S1704). Then, this process is complete | finished.

  As described above, according to the browsed document management apparatus of the first embodiment, when dealing with a trouble ticket (task) of a workflow that a user is in charge of, a highly relevant file is efficiently browsed according to each state. Can do.

[Second Embodiment]
In the second embodiment, when calculating the relation strength, unlike the first embodiment, the reference time is not used. Here, the user interface (UI) of the second embodiment is the same as that of the first embodiment. Further, the configuration of the related document browsing apparatus in the second embodiment is the same as that of the first embodiment except that the browsing time measuring unit 3135 is omitted. The workflow configuration of the second embodiment is the same as that of the first embodiment. In addition, the designation of the failure slip in the second embodiment is the same as that in the first embodiment except that the measurement start (T415 in FIG. 11) and the measurement stop (T506, T507 in FIG. 12) are omitted. . The configuration of the browsing history information 60 of the second embodiment is the same as that of the first embodiment except that the browsing time 607 (see FIG. 8) is omitted.

  The calculation and ordering of the related strengths in the second embodiment are the same as those in the first embodiment, except that the use of the browsing time (reference time) is omitted in calculating the related strengths.

  FIG. 23 is a flowchart showing a related strength calculation processing procedure in the second embodiment. This processing program is stored in a storage medium in the related document browsing apparatus 31, and is executed by the CPU. Here, the history item No. of the browsing history information 60 is displayed. 096-No. 104 will be used for the description. Further, it is assumed that the state is “fault handling”.

  The related strength control unit 3133 acquires the state coefficient setting information 803 from the coefficient value information 80 (step S2301). Here, the coefficient value setting information related to “failure handling” in the browsing history information 60, that is, [1 / (ln + 1)] is acquired. In the same way as in the first embodiment, ln is a history number when history in the same state is arranged in order from recent history. In accordance with the acquired coefficient value setting information 803, the browsing history information 60 of No. 096-No. A coefficient is assigned to 104 (step S2302). The coefficient is No. 104, 1/2, no. 103, 1/3,. 096 becomes 1/10.

  No. 096-No. With respect to all the history items 104, the process proceeds to a process of calculating the relation strength of the document for each history item. First, it is assumed that the relation strength is the same as the coefficient value of S2302 (step S2303), and the document ID held by the history item is acquired (step S2304). A process of adding the calculated relation strength for each document is performed (step S2305). In this process, as in the first embodiment, the relation strength of the document having the same document ID as the document ID acquired in step S2304 is added to the temporary storage variable. Thereafter, it is determined whether or not processing has been completed for all history items (step S2306). When the process is completed for all history items, this process is terminated. On the other hand, if the process has not ended, the process returns to step S2303.

  The generation of coefficient information and the setting of default values in the second embodiment are the same as those in the first embodiment. In addition, the coefficient information setting unit in the second embodiment is the same as that in the first embodiment.

  Thus, according to the browsing document management apparatus of 2nd Embodiment, since the reference time of a document is not used, a related intensity | strength can be calculated easily. Therefore, it is possible to quickly display a screen in which documents are rearranged.

[Third Embodiment]
The user interface (UI) of the third embodiment is the same as that of the first embodiment. The configuration of the related document browsing apparatus in the third embodiment is the same as that in the first embodiment. The configuration of the workflow in the third embodiment is the same as that in the first embodiment. The designation of the failure slip in the third embodiment is the same as that in the first embodiment.

  In the third embodiment, a user who operates a task held by a process is held as a group for each process. FIG. 24 is a diagram showing a group for each process in the third embodiment. A group 240 represents a group in the process A-001. In the figure, reference numeral 2401 denotes an ID for identifying a process. Reference numerals 2402 and 2403 denote a group ID and a group name, respectively. Reference numeral 2404 denotes a member name as a user held by the group identified by the group ID 2402. The connection between the process and the group, or the connection between the process and the group user is held and managed by the failure slip management server 11.

  Process P1 (see FIG. 3) holds one or more groups. In the failure slip management server 11, the group held by the process P1 is linked by the management user who manages the process. For example, the management user sets “the group with the group ID“ XX ”is the main group in charge in the evaluation phase P11 and the action confirmation phase P13 of the process P1”. The setting of the main charge group is also performed in the phase unit indicated by P11 to P14 or the state unit indicated by P111 to P141.

  The configuration of the browsing history information 60 in the third embodiment is the same as that in the first embodiment. Further, the calculation and ordering of the related strengths in the third embodiment are the same as those in the first embodiment, except that a group (see FIG. 24) is used when calculating the related strengths.

  FIG. 25 is a flowchart showing the procedure for calculating the related strength. This processing program is stored in a storage medium in the related document browsing apparatus 31, and is executed by the CPU. When a related strength calculation command is issued from the hint information control unit 3131 to the related strength control unit 3133 (T409 in FIG. 11), the related strength control unit 3133 acquires the process ID of the process to which the failure slip “Problem001” belongs. (Step S2501). The related strength control unit 3133 issues an acquisition command for the coefficient value information 80 to the coefficient control unit 3134 (step S2502). Upon receiving the coefficient value information 80 acquisition command, the coefficient control unit 3134 starts processing for acquiring the coefficient value information 80 shown in FIG.

  That is, the coefficient control unit 3134 checks whether or not the information on the process specified by the process ID exists in the coefficient management information 70 in step S1001 of FIG. If the process information exists in the coefficient management information 70, the coefficient control unit 3134 acquires the coefficient ID using the given process ID as a key in step S1002. In step S1003, coefficient value information of this process is acquired from the coefficient value information 80 using the coefficient ID acquired from the coefficient management information 70 as a key.

  On the other hand, if the process information does not exist in the coefficient management information 70 in step S1001, upon receiving the information, the hint information control unit 3131 sets the browsing history addition coefficient for this process in step S1004. A UI for confirming whether or not is displayed is displayed.

  In step S1009, the display device 311 displays a confirmation UI. In addition, when the display device 311 receives a user input in step S1010, the display device 311 passes input information, that is, “Yes” or “No” to the hint information control unit 3131. When the hint information control unit 3131 receives the information in step S1005, the hint information control unit 3131 generates coefficient information and sets a default value.

  Thereafter, in step S1006, the hint information control unit 3131 confirms whether the input information is “Yes” or “No”. If the input information is “Yes”, the process of setting the coefficient value in step S1007 is performed. In step S1008, the set coefficient value information is acquired. The coefficient value information acquired in step S2502 described above is the coefficient value information acquired in step S1008 or step S1003.

  When acquiring the coefficient value information 80 in step S2502, the related strength control unit 3133 acquires a list of WF states of this process from the coefficient value information 80 (step S2503).

  The related strength control unit 3133 acquires group information to which the user who has activated the “work hint” belongs (step S2504), and issues an instruction to acquire the names of all members of the group (step S2505). The failure slip management server 11 acquires the names of all members of the group according to the instruction and transmits them to the related strength control unit 3133 (step S2506).

  The related strength control unit 3133 extracts, from the browsing history information 60 acquired in T404 and T405 of FIG. 11, a history in which the members acquired in steps S2505 and S2506 are operator names (step S2507). Further, the following processing is performed for each state acquired in step S2503. That is, the history of this state is acquired from the browsing history information 60 (step S2508), and the related strength of each document is calculated (step S2509). The calculation of the related strength will be described later. And it is discriminate | determined whether the process of all the states was complete | finished (step S2510). If not completed, the process returns to step S2508. On the other hand, if all the states have been processed, the related strengths of the respective documents are ordered (step S2511).

  The calculation unit in the third embodiment is the same as that in the first embodiment. The ordering in the third embodiment is the same as that in the first embodiment.

  When the related strength is calculated based on the present embodiment, different related strengths are calculated according to the group to which the user belongs. For example, the member qaUser02 (see FIG. 24) has a history No. 096 to History No. Consider a case where “work hint” is activated after 104 (see FIG. 8). In this case, in the group Qa-WT (see FIG. 24) to which the member qaUser02 belongs, the related document is “Aa specification.doc”.

  Further, the member devUser01 (see FIG. 24) has a history No. 096 to History No. When the “work hint” is activated after 104 (see FIG. 8), the relation strength of the group Dev-BZ (see FIG. 24) to which the member devUser01 belongs is as follows. That is, when the reference time × coefficient (= 1 / (ln + 1)) is used, the history item No. 103-No. 99 related strengths are 102/3, 254/4, 548/5, 201/6, 345/7, respectively. 97, no. 98 is 219/9 and 10/10, respectively. Therefore, the related documents added as the same document ID are “AaaaProblem.java”, “Bbbb problem analysis.doc”, “AaaaProblemResource.java”, and “Aa specification.doc” in descending order of the relation strength.

  The generation of coefficient information and the setting of default values in the third embodiment are the same as those in the first embodiment. In addition, the coefficient information setting unit in the third embodiment is the same as that in the first embodiment. Further, the configuration of the browsing history information in the third embodiment is the same as that in the first embodiment.

  Thus, according to the browsing document management apparatus of 3rd Embodiment, while using the reference time of a document for every group, calculation of a related strength is performed for every group. Therefore, it is possible to present a related document in consideration of a group.

[Fourth Embodiment]
The user interface (UI) of the fourth embodiment is the same as that of the third embodiment. The configuration of the related document browsing apparatus in the fourth embodiment is the same as that in the third embodiment. The configuration of the workflow in the fourth embodiment is the same as that in the third embodiment. The designation of the failure slip in the fourth embodiment is the same as that in the third embodiment. However, in the fourth embodiment, the measurement start process at T415 in FIG. 11 and the measurement stop process at T506 and T507 in FIG. 12 are not executed.

  The group in the fourth embodiment is the same as the group in the third embodiment. The configuration of the browsing history information of the fourth embodiment is the same as that of the third embodiment. However, in the fourth embodiment, the browsing time 607 in the browsing time history information 60 of FIG. 8 is not used.

  Further, the calculation and ordering of the related strengths in the fourth embodiment are the same as the calculation and ordering in the third embodiment. However, in the fourth embodiment, the browsing time is not used in calculating the related strength.

  The calculation of the relation strength in the fourth embodiment is based on the history item No. of the browsing history information 60 (see FIG. 8). 96-No. 104 will be used for the description. These states are assumed to be “failure handling”.

  In step S2301 in FIG. 23, the related strength control unit 3133 acquires the coefficient setting information 803 in this state from the coefficient value information 80. That is, [1 / (ln + 1)] is acquired as the coefficient value setting information regarding “Failure handling” in the browsing history information 60 (see FIG. 10). Note that ln indicates a history number when history in the same state is arranged in order from the latest history.

  In step S2302, according to the coefficient value setting information acquired in step S2301, No. of the history information 60 is set. 096-No. A coefficient is assigned to 104. This coefficient is the No. 104, value 1/2, No. 103, the value 1/3,. At 096, the value becomes 1/10.

  No. 096-No. With respect to all the history items 104, the process proceeds to a process of calculating the relation strength of the document for each history item. In step S2303, it is assumed that the relation strength is the same as the coefficient value in S2302, and in step S2304, the document ID held by the history item is acquired. A process of adding the relation strength calculated in step S2305 for each document is performed. That is, an addition process to the related strength temporary storage variable of the same document ID as that acquired in step S2304 is performed. Thereafter, in step S2306, it is determined whether or not processing has been completed for all history items. When the process is completed for all history items, this process is terminated. On the other hand, if the process has not ended, the process returns to step S2303. The ordering in the fourth embodiment is the same as the ordering in the second embodiment.

  In the fourth embodiment, when the association strength is calculated, different association strengths are calculated according to the group to which the user belongs. For example, the member qaUser02 (see FIG. 24) has a history No. 096 to History No. Consider a case where “work hint” is activated after 104 (see FIG. 8). In this case, in the group Qa-WT (see FIG. 24) to which the member qaUser02 belongs, the related document is only “Aa specification.doc”.

  Further, the member devUser01 (see FIG. 24) has a history No. 096 to History No. When the “work hint” is activated after 104 (see FIG. 8), the relation strength of the group Dev-BZ (see FIG. 24) to which the member devUser01 belongs is as follows. That is, when the coefficient (= 1 / (ln + 1)) is used, the history item No. 103-No. The related strength for every 99 is 1/3, 1/4, 1/5, 1/6, 1/7, respectively. 97, no. 98 is 1/9 and 1/10, respectively. Accordingly, the related documents are “AaaaProblem.java”, “AaaaProblemResource.java”, “Bbbb problem analysis.doc”, and “Aa specification.doc” in descending order of relevance strength.

  As described above, according to the browsed document management apparatus of the fourth embodiment, it is possible to easily calculate the relation strength without using the document reference time for each group. Then, users in each group can efficiently browse documents related to the task being handled according to the strength of the association.

  The present invention is not limited to the configuration of the above-described embodiment, and any configuration can be used as long as the functions shown in the claims or the functions of the configuration of the present embodiment can be achieved. Is also applicable.

  For example, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device.

  The object of the present invention is also achieved by the following. That is, a storage medium storing software program codes for realizing the functions of the above-described embodiments is supplied to the system or apparatus. The computer (or CPU, MPU, etc.) of the system or apparatus reads out and executes the program code stored in the storage medium.

  In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiments. The program code and a storage medium storing the program code constitute the present invention.

  Further, for example, a floppy (registered trademark) disk, a hard disk, a magneto-optical disk, a CD-ROM, a CD-R, or a CD-RW can be used as a storage medium for supplying the program code. Further, an optical disc such as a DVD-ROM, a DVD-RAM, a DVD-RW, a DVD + RW, a magnetic tape, a nonvolatile memory card, a ROM, or the like can be used. Alternatively, the program code may be downloaded via a network.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also the following cases are included. That is, based on the instruction of the program code, an OS (operating system) running on the computer performs part or all of the actual processing. The case where the functions of the above-described embodiments are realized by such processing is also included.

  Further, the program code read from the storage medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. Thereafter, based on an instruction of the program code, a CPU or the like provided with the extension function in the extension board or the extension unit performs part or all of the actual processing. The case where the functions of the above-described embodiments are realized by such processing is also included.

It is a figure which shows the structure of the related document browsing management system in 1st Embodiment. 3 is a diagram illustrating a functional configuration of a related document browsing device 31. FIG. It is a figure which shows a trouble vote workflow. It is a figure which shows the trouble vote in development of a software program. 4 is a diagram showing a main UI screen displayed on the display device 311. FIG. FIG. 10 is a diagram showing a UI screen for designating a failure slip displayed on a failure slip number or failure slip identifier 1901. It is a figure which shows UI screen for setting a coefficient value. It is a table which shows the browsing history information 60 of the failure slip “Problem001”. 5 is a table showing coefficient management information 70. It is a table which shows the coefficient value information 80 linked | related with process ID of FIG. It is a figure which shows the flow of a process when the user designates the trouble vote to browse and edit using the input device 312 of the browsing document management apparatus 31. FIG. 10 is a diagram illustrating a processing flow when a user cancels designation of a trouble ticket using the input device 312 of the browsed document management device 31. It is a flowchart which shows the operation | movement process sequence at the time of the browsing document management apparatus 31 starting a "work hint" by a user's operation, and designating the failure slip to browse and edit for correspondence. It is a flowchart which shows the process sequence which acquires the coefficient value information in step S2204, S2205, and S2206, calculates a related strength, and orders related documents. It is a flowchart which shows the acquisition process procedure of the coefficient value information 80 in step S902. It is a flowchart which shows the related strength calculation processing procedure in step S905. It is a flowchart which shows the production | generation procedure of the coefficient information in step S1005, and the setting process of a default value. It is a flowchart which shows the coefficient setting process sequence which sets a coefficient value to each state in the process P1 to which the failure vote “Problem001” belongs in step S1007. It is a flowchart which shows the measurement start processing procedure of browsing time. It is a flowchart which shows the measurement end processing procedure of browsing time. It is a flowchart which shows the pause processing procedure of browsing time measurement. It is a flowchart which shows the resumption processing procedure of the browsing time measurement paused. It is a flowchart which shows the calculation process procedure of the related intensity | strength in 2nd Embodiment. It is a figure which shows the group for every process in 3rd Embodiment. It is a flowchart which shows the calculation process procedure of related intensity | strength.

Explanation of symbols

11 Failure slip management server 13 Browsing history database 31, 32, 33 Related document browsing device 60 Browsing history information 70 Coefficient management information 80 Coefficient value information 180 Failure slip 190 Main UI
3131 Hint information control unit 3132 Failure slip control unit 3133 Browsing intensity control unit 3134 Coefficient control unit 3135 Browsing time measurement unit 3136 Browsing history information control unit

Claims (7)

A file management device for managing files related to a task including a plurality of states,
Coefficient value information acquisition means for acquiring coefficient value information for each state of the task;
Using the acquired coefficient value information, a related strength calculating means for calculating a related strength for each state,
A file management apparatus comprising: file display means for displaying a file related to the task in order of the relation strength calculated for each state. Receiving means for receiving the setting of the coefficient value information for each state;
The file management apparatus according to claim 1, wherein the coefficient value information acquisition unit acquires coefficient value information whose setting is accepted for each state. Comprising browsing history information acquisition means for acquiring browsing history information of the file;
The file management apparatus according to claim 1, wherein the related strength calculation unit calculates the related strength using the acquired browsing history information and the coefficient value information.   The browsing history information acquisition means acquires the browsing history information for each group to which a user belongs, and the related strength calculation means calculates the related strength using the acquired browsing history information for each group. The file management apparatus according to claim 3.   The browsing history information acquisition unit holds a browsing time history as a database as the browsing history information, and the browsing strength calculation unit calculates the related strength using the browsing time history. The file management apparatus according to claim 3. A file management method for managing files related to a task having a plurality of states,
A coefficient value information acquisition step of acquiring coefficient value information for each state of the task;
Using the acquired coefficient value information, a related strength calculating step of calculating a related strength for each state;
And a file display step of displaying a file related to the task on a display device in the order of the relation strength calculated for each state.   A program having computer-readable program code for realizing the file management apparatus according to claim 1.

Images