JP2013037478A - Work man-hour calculation device, work man-hour calculation method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a work man-hour calculation device for more precisely grasping work man-hour that a worker has actually carried out in a development project, and to provide a work man-hour calculation method, and a program.SOLUTION: The work man-hour calculation device includes: a project information management database for registering project information in advance that includes information indicating managed object containing outcomes generated by work in each process of the project or reference to be referred to when working on processes; an operation history information database for storing operation history information that includes date of operation, operated objects operated by the worker, and name of operation performed by the worker with respect to the operated object, which are acquired from a working terminal for working on each process of the project; and a man-hour calculation part for calculating man-hour in each process of the project on the basis of the project information and the operation history information.

Description

  The present invention relates to a work man-hour calculating device, a work man-hour calculating method, and a program.

  In recent years, in software development, it has become important to accurately manage development projects in order to reduce development costs and shorten delivery times. In conventional software development project management, a technique using WBS (Work Breakdown Structure) is widely used to estimate development man-hours and manage progress. However, if there is an error in the work report submitted by the development project worker, the project manager who is the project manager cannot correctly manage the progress.

  For this reason, for the purpose of allowing the project manager to accurately and objectively grasp the status of the development project, as disclosed in Patent Document 1, a technique for measuring the operation time of the worker and the man-hour for each work, non-patent A product having a mechanism for measuring an operator's operating time, such as Document 1, has been proposed.

  Patent Document 1 is a technique for grasping the work content and work time based on the operation time and file update time of each work terminal. Further, in the product of Non-Patent Document 1, by automatically detecting the time when a user who is an operator logs on to a personal computer (hereinafter referred to as “PC”) as a work terminal and the time when he / she logs off from the PC. The work time for each user is recorded.

JP-A-9-138823

“Cybozu Garoon Basic Function (Time Card)”, Cybozu Co., Ltd., [Search June 29, 2011], Internet, <http: // g. cyzuzu. co. jp / gr / seihin / kihon / time_card />

  However, in software development, the operation time of the work terminal is generally different from the actual operation time of the worker. With the technique disclosed in Patent Document 1, although the work time can be grasped from the operation time of the work terminal and the file update time, the worker who has performed the development work cannot be specified. In addition, the work time includes the time when the work terminal automatically executes the process without human intervention. For this reason, with the technique disclosed in Patent Document 1, it is difficult to grasp the man-hour that is the time when the worker actually puts his hand.

  Further, in the product of Non-Patent Document 1, since the logon and logoff times of the PC are measured, it is possible to grasp the time during which the PC is operating for each worker. I haven't come to know the time I am doing.

  Thus, there is a problem that the actual work man-hour of the worker cannot be accurately grasped from the operation time of the work terminal and the file update time.

  The present invention has been made on the basis of the above problem recognition, and in a development project, a work man-hour calculating device, a work man-hour calculating method, and a program for more accurately grasping the work man-hours actually performed by the worker The purpose is to provide.

  In order to solve the above-described problems, the work man-hour calculating apparatus according to the present invention includes a management object including a deliverable generated by a work of each process of a project or a reference object referred to when performing the work of the process. Project information including information indicating, a project information management database that is registered in advance, an operation date and time acquired from a work terminal that performs the work of each step of the project, an operation object operated by an operator, and the Each step of the project based on the operation history information database storing operation history information including information indicating the name of the operation performed by the worker on the operation target, the project information, and the operation history information And a man-hour calculating unit for calculating man-hours in

  Further, the man-hour calculating unit in the work man-hour calculating device of the present invention is configured such that the operation history information is based on a management object determination criterion in which a condition for determining the management object in each step of the project is determined in advance. Whether or not the operation history information is project operation history information corresponding to the project by determining whether the operation object included in the project corresponds to the management object in any of the steps of the project The project operation history information is based on an operation type determination criterion in which a condition for determining an operation type (for example, editing, browsing, etc.) according to the operation content for the operation target is determined. The operation type of the operation content included is determined, and the management corresponding to the operation object included in the project operation history information By specifying the process in the project including the artifact as the work execution candidate process, the work type in the work execution candidate process is specified, and the work corresponding to the work type in each process of the project is performed. Whether the operation type of the project operation history information matches a work execution condition corresponding to the work type in the work execution candidate process, based on a predetermined work execution determination criterion for determining the condition By determining whether or not the operation content included in the project operation history information determines whether or not the operation of the operation execution candidate process has been performed, and it is determined that the operation of the operation execution candidate process has been performed The calculated project operation history information is used as the man-hour calculation operation history information, and the man-hours in each process of the project Is used to output, characterized in that.

  Further, the operation history information in the operation man-hour calculating device of the present invention includes information on the worker, the man-hour calculating unit includes the operation date and time included in the man-hour calculating operation history information, and the man-hour The man-hour calculation operation history in which the worker information, the operation object, and the application usage type (for example, file operation by the document creation application described in FIG. 14A) included in the calculation operation history information are the same. Calculate the man-hour of the operation unit based on the information, calculate the man-hour of the daily operation unit based on the man-hour of the operation unit on the same day in the calculated man-hour of the operation unit, and calculate the daily operation In the unit man-hour, based on the man-hour of the daily operation unit in which the management object in the project and the corresponding information of the worker is the same, Calculate the man-hour of the work unit for each physical object, further determine the operation type of the man-hour of the calculated work unit for each management object based on the operation type determination criterion, and calculate the determined operation type In the man-hours of the management object-by-management object unit added to the management object-by-management object unit and the operation type, the management object-by-management object work and the process in the corresponding project are the same. Based on the man-hours of the unit, the man-hours of the work units by process are calculated, and in the man-hours of the calculated work units by process, the man-hours of the work units by process in which the project is the same are added together, The number of man-hours in each step is calculated.

  Further, the work man-hour calculating device of the present invention calculates each step of the project, the worker, and the man-hour based on the calculation result of the man-hour in each step of the project calculated by the man-hour calculating unit. A display screen generation unit that generates a display screen in which any two items are associated with each other in the work execution period included in the result, and outputs the generated display screen to a management terminal that manages the project; It is further provided with the feature.

  Further, the project information in the work man-hour calculating device of the present invention includes information on a planned period for performing each process of the project, and the display screen generation unit includes the planned period included in the project information, The display screen including information indicating the progress of each process of the project is generated based on the work execution period.

  Further, the work man-hour calculation method of the present invention includes, in the project information management database, a management object including a deliverable generated by a work of each process of a project or a reference material referred to when performing the work of the process. Project information including information to be registered in advance, and operation history information database, operation date and time acquired from a work terminal that performs work of each process of the project, operation object operated by the operator And each step of the project based on the step of storing operation history information including information indicating an operation name performed by the worker on the operation target, the project information, and the operation history information. And a man-hour calculating step for calculating man-hours in

  Further, the program of the present invention stores, in the project information management database, information indicating a management object including a deliverable generated by the work of each process of the project or a reference material referred to when performing the work of the process. The project information including the step of registering in advance, the operation history information database, the operation date and time acquired from the work terminal performing the work of each step of the project, the operation object operated by the operator, and the Based on the step of storing operation history information including information indicating an operation name performed by the worker on the operation target, the project information, and the operation history information, the man-hours in each process of the project are calculated. And a step of calculating a man-hour to be calculated.

  According to the present invention, in the development project, it is possible to obtain an effect that it is possible to more accurately grasp the work man-hours that the worker actually hands.

It is the block diagram which showed schematic structure of the work man-hour calculation system in embodiment of this invention. It is the block diagram which showed schematic structure of the functional block in the operation man-hour calculation system of this embodiment. It is the figure which showed an example of the information of the object acquired in the work man-hour calculation system of this embodiment. It is the sequence figure which showed the flow of the registration process of the project information in the operation man-hour calculation system of this embodiment. It is the figure which showed an example of the data structure of the project information stored in information management DB in the work man-hour calculation system of this embodiment. It is the sequence figure which showed the flow of the collection process of the operation history information in the operation man-hour calculation system of this embodiment. It is the figure which showed an example of the data structure of the operation history information stored in information management DB in the work man-hour calculation system of this embodiment. It is the sequence figure which showed the flow of the calculation process of the man-hour in the work man-hour calculation system of this embodiment. It is the figure which showed the outline | summary of the algorithm of the man-hour calculation process in the work man-hour calculation system of this embodiment. It is the figure which showed an example of the information used when performing a man-hour calculation process in the work man-hour calculation system of this embodiment. It is a figure explaining an example at the time of implementing a man-hour calculation process algorithm in the work man-hour calculation system of this embodiment. It is a figure explaining another example at the time of implementing a man-hour calculation process algorithm in the work man-hour calculation system of this embodiment. It is the flowchart which showed the process sequence of the calculation process of the man-hour in the work man-hour calculation system of this embodiment. It is the figure which showed an example of the information of the result obtained by the information used when performing a man-hour calculation process in the work man-hour calculation system of this embodiment, or a man-hour calculation process. It is the sequence figure which showed the flow of the display process of the calculation result of the man-hour in the work man-hour calculation system of this embodiment. It is the figure which showed typically an example of the display format (henceforth "display classification") of the calculation result of the man-hour in the work man-hour calculation system of this embodiment. It is the figure which showed typically another example of the display classification of the calculation result of the man-hour in the work man-hour calculation system of this embodiment. It is the figure which showed typically another example of the display classification of the calculation result of the man-hour in the work man-hour calculation system of this embodiment.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a schematic configuration of a work man-hour calculation system in the present embodiment. In FIG. 1, an operation man-hour calculating system 10 includes an operation history collecting device 100, an operation history managing device 200, an information management database (hereinafter referred to as “information management DB”) 300, a man-hour calculating device 400, and a project information management. Device 500. In the work man-hour calculating system 10 shown in FIG. 1, each device and the information management DB 300 are connected via a network. In addition, a web browser 20 used by a project manager who is a project manager is connected to the work man-hour calculating system 10 via a network.

  The operation history collection device 100 is a device that collects operation histories of users who are workers. The operation history collection device 100 is a work terminal such as a PC used when an operator performs development work. The operation history collection apparatus 100 has resident agent software for detecting an operation by an operator, and information on the operation history of the worker detected by the agent software (hereinafter referred to as “operation history information”) is stored in an operation history management. To device 200.

  Note that the trigger for transmitting the operation history information collected by the operation history collection device 100 to the operation history management device 200 differs depending on whether or not the operation history collection device 100 is always connected to the network. For example, when the operation history collection device 100 is always connected to the network, the operation history information collected at any time when operated by the worker or at a constant interval (for example, every 1 minute) Is transmitted to the operation history management apparatus 200. In addition, for example, when the operation history collection device 100 is not always connected to the network and is connected to the network irregularly, the collected operation is triggered when the operation history collection device 100 is connected to the network. The history information is transmitted to the operation history management apparatus 200.

  When the operation history collection device 100 is a work terminal used by an operator for development work, the work man-hour calculation system 10 includes a plurality of operation history collection devices 100, which are not shown in FIG. It is thought that. In this case, each of the plurality of operation history collection devices 100 transmits the detected operation history information to the operation history management device 200, respectively.

  The operation history management apparatus 200 is an apparatus that receives operation history information transmitted from the operation history collection apparatus 100 via a network and stores (accumulates) the received operation history information in the information management DB 300. The operation history management apparatus 200 is connected to the network constantly or irregularly, and when connected to the network, the received operation history information is stored in the information management DB 300 via the network.

  The information management DB 300 includes the operation history information transmitted from the operation history management apparatus 200, the information on the man-hour calculated by the man-hour calculating apparatus 400 described later, and the information on the project transmitted from the project information management apparatus 500 described later (hereinafter, This database stores (accumulates) “project information”.

  The man-hour calculation device 400 is a device that acquires operation history information and project information stored in the information management DB 300 and calculates man-hours for a project. A detailed description of the method for calculating the man-hour of the project by the man-hour calculating device 400 will be described later.

  The project information management device 500 is a device that stores (accumulates) information related to a project transmitted from the Web browser 20 via a network in the information management DB 300 as project information.

  Next, functional blocks of the work man-hour calculation system 10 of this embodiment will be described. FIG. 2 is a block diagram showing a schematic configuration of functional blocks in the work man-hour calculation system 10 of the present embodiment.

  The operation history collection device 100 includes an operation history collection unit 110 and an information transmission unit 120. In the following description, it is assumed that the operation history collection device 100 is a personal computer (PC) used when an operator performs development work. The operation history collection unit 110 collects operation history information when a worker performs a project development work by using resident agent software. The operation history information collected by the operation history collection unit 110 includes information identifying the worker, the name of the application used by the worker, the name of the file accessed by the worker, the number of key touches by the worker, and mouse operations. The operation contents for the file such as time are included.

  Here, the operation history information collected by the operation history collection unit 110 will be described. FIG. 3 is a diagram illustrating an example of target information acquired by the operation history collection unit 110 provided in the work man-hour calculation system 10 of the present embodiment. FIG. 3 shows an example of an application that collects operation histories and an example of information (operation) acquired from each application. As illustrated in FIG. 3, the operation history information collected by the operation history collection unit 110 has different acquisition target information for each application used by the worker.

  In the example shown in FIG. 3, regardless of the application used by the worker, “operator name (login name)”, “machine name used”, “operation date / time”, “application (AP) start / end flag” It shows a case where common information such as “” is acquired.

  When the application used by the worker is a “document creation application”, in addition to common information, the operation content includes “file name”, “operation time (window active time)”, “key touch” This shows a case where “number of times”, “operation name (file open / close)”, “file size”, “number of pages”, and the like are acquired as operation results.

  When the application used by the worker is a “web browser”, in addition to common information, “operation object name (URL)”, “operation time (window active time)” as operation contents , “Key touch count”, “operation name (text box name at the time of input)”, and the like are acquired.

  In addition, when the application used by the worker is a “development tool application”, in addition to the common information, the operation contents include “operation object name (perspective name + file name)”, “operation time ( Window active time), “key touch count”, “operation name (file open / close / test effective / perspective switch)”, and operation results “number of characters”, “number of lines”, “test effective number, test error number” , "Number of test failures".

  In addition, when the application used by the worker is a “mail application”, in addition to common information, “operation object name (browsing / creation)”, “operation time (window active time) as operation contents ) ”,“ Number of key touches ”, and the like. Also, information such as “e-mail destination address” and “e-mail title text” may be acquired.

  The information transmission unit 120 transmits operation history information corresponding to each application collected by the operation history collection unit 110 for each application used by the worker to the operation history management apparatus 200 via the network. When the operation history collection device 100 is always connected to the network, the information transmission unit 120 is connected to the network at any time (for example, every minute) when the operation history collection device 100 is irregularly connected to the network. Transmits the operation history information to the operation history management device 200 when the operation history collection device 100 is connected to the network.

  The operation history management apparatus 200 includes an information transmission / reception unit 210 and a DB access unit 220. The information transmission / reception unit 210 receives the operation history information transmitted from the information transmission unit 120 included in the operation history collection device 100, and outputs the received operation history information to the DB access unit 220. The DB access unit 220 stores (accumulates) the operation history information input from the information transmitting / receiving unit 210 in the information management DB 300. Note that when the DB access unit 220 stores the operation history information in the information management DB 300, format conversion is performed to align the formats of the input operation history information in various formats. Then, the DB access unit 220 stores the operation history information after the format conversion in the information management DB 300. A detailed description of the operation history information stored in the information management DB 300 by the operation history management apparatus 200 will be described later.

  The project information management apparatus 500 includes an information transmission / reception unit 510 and a DB access unit 520. The information transmission / reception unit 510 receives information related to the project input from the web browser 20 by the project manager, and outputs the received information to the DB access unit 520 as project information. Here, the project information input from the Web browser 20 by the project manager includes WBS (Work Breakdown Structure) information as a project process. The WBS information is not information that is generated as a result of implementing the WBS of the current project or the result of implementing the WBS. Information on a reference object generated in advance of the WBS or generated in advance, which is referred to when the WBS is executed, is included as an object to be managed. A detailed description of the project information stored in the information management DB 300 by the project information management apparatus 500 will be described later.

  The DB access unit 520 stores (accumulates) the project information input from the information transmission / reception unit 510 in the information management DB 300. Note that when the DB access unit 520 stores the project information in the information management DB 300, format conversion is performed to align the format of the input project information, and the project information after the format conversion is stored in the information management DB 300. It may be stored.

  The information management DB 300 includes an operation history information DB 310, a project information management DB 320, and a man-hour management DB 330. The operation history information DB 310 stores operation history information input from the DB access unit 220 provided in the operation history management apparatus 200. The project information management DB 320 stores project information input from the DB access unit 520 provided in the project information management apparatus 500. The man-hour management DB 330 stores the man-hour calculation result calculated by the man-hour calculating device 400. A detailed description of the calculation result of the man-hour stored in the man-hour management DB 330 will be described later.

  The man-hour calculating device 400 includes an information transmitting / receiving unit 410, a DB access unit 420, and a man-hour calculating unit 430. Based on information input from the project manager via the Web browser 20, the information transmission / reception unit 410 outputs an instruction for executing the manhour calculation process in the manhour calculation device 400 to the DB access unit 420 and the manhour calculation unit 430. To do. In addition, the information transmitting / receiving unit 410 transmits the man-hour calculation result by the man-hour calculating unit 430 to the Web browser 20 for display. The man-hour calculating device 400 displays information related to various man-hours according to the calculation result obtained by the man-hour calculating process. Detailed description regarding the display of the man-hour calculation result will be described later.

  The DB access unit 420 is necessary to calculate the man-hour from the operation history information DB 310 and the project information management DB 320 provided in the information management DB 300 in response to the man-hour calculation processing execution instruction input from the information transmitting / receiving unit 410. Information is acquired and output to the man-hour calculation unit 430 via the information transmission / reception unit 410. More specifically, the DB access unit 420 acquires operation history information from the operation history information DB 310, acquires project information from the project information management DB 320, and outputs each information to the man-hour calculation unit 430.

  Further, the DB access unit 420 stores (accumulates) the man-hour calculation result by the man-hour calculating unit 430 input via the information transmitting / receiving unit 410 in the man-hour management DB 330 provided in the information management DB 300.

  In addition, the DB access unit 420 acquires the man-hour calculation result stored in the man-hour management DB 330, and outputs the result to the Web browser 20 via the information transmission / reception unit 410, thereby obtaining the man-hour calculation result by the man-hour calculation unit 430. It is displayed on the Web browser 20.

  The man-hour calculating unit 430 calculates the man-hours for the development work of the project corresponding to the project information based on the operation history information and the project information input via the information transmitting / receiving unit 410. A detailed description of a method for calculating the man-hour of the project by the man-hour calculating unit 430 will be described later.

  Next, a process for calculating the work man-hour in the work man-hour calculating system 10 of the present embodiment will be described. The work man-hour calculation system 10 presents a calculation result of a desired man-hour to the project manager by the following process.

(Process 1): Project information is stored (registered) in advance in the project information management DB 320 in the information management DB 300 via the project information management device 500 when the project manager inputs information on the project from the Web browser 20 in advance. Keep it.
(Process 2): The operation history collection device 100 collects operation history information in the project development work by the operator, and the operation history information is stored in the operation history information DB 310 in the information management DB 300 via the operation history management device 200. Store.
(Process 3): The man-hour calculating device 400 executes the man-hour calculating process according to the effective man-hour calculating process requested by the project manager input via the Web browser 20, and the man-hour calculating result is stored in the information management DB 300. Is stored in the man-hour management DB 330.
(Process 4): The man-hour calculation device 400 acquires the man-hour calculation result stored in the man-hour management DB 330 in the information management DB 300, and presents the man-hour calculation result to the project manager via the Web browser 20.

  First, processing (processing 1) for registering project information in the information management DB 300 will be described. FIG. 4 is a sequence diagram showing a flow of registration processing of project information in the work man-hour calculation system 10 of the present embodiment.

  First, the project information management apparatus 500 displays a project information input screen on the Web browser 20 (step S101). Then, the project manager inputs project information in accordance with the displayed input screen. Thereafter, the Web browser 20 transmits the input project information to the project information management apparatus 500 (step S102).

  Subsequently, the project information management apparatus 500 transmits the received project information to the information management DB 300 for storage (step S103). The information management DB 300 accumulates project information (step S104). Then, the project information management apparatus 500 displays information indicating whether or not the project information has been correctly stored on the Web browser 20 (step S105). When the project information cannot be correctly stored in the information management DB 300, the project information management apparatus 500 may cause the Web browser 20 to display the project information input screen again, similarly to step S101.

  By such a sequence, project information necessary for the man-hour calculation process in the work man-hour calculating system 10 is registered in the information management DB 300 in advance. FIG. 5 shows an example of the data configuration of project information stored in the information management DB 300 by the project information management apparatus 500 in the work man-hour calculation system 10 of the present embodiment. FIG. 5A shows an example of the data structure of the project profile information, and FIG. 5B shows an example of the data structure of the personal profile information of the worker who executes the project.

  Note that the example of the data structure of the project information shown in FIG. 5 shows an example in which each piece of information is divided into a plurality of levels and registered. For example, the “project profile” includes “project code”, “name”, “start date (plan)”, “end date (plan)”, “group”, “WBS”, “managed object”, etc. Registered as a lower level. For example, “Group ID”, “Group name”, “Parent group”, “Activity start date (plan)”, “Activity end date (plan)”, “Member”, etc. are subordinate to “Group”. Furthermore, “employee number”, “role”, “leader flag”, “affiliation start date”, “affiliation end date”, etc. are registered as lower levels in “member”.

  The data registered in each item of the profile information of the project shown in FIG. 5A and the personal profile information shown in FIG. 5B is shown in correspondence with each item in FIG. This is data representing the contents of “Description”.

  Next, a process (process 2) of collecting operation history information in the project development work and storing it in the information management DB 300 will be described. FIG. 6 is a sequence diagram showing a flow of operation history information collection processing in the work man-hour calculation system 10 of the present embodiment.

  First, when an operator performs an operation to be an operation history collection target in the project development work (step S201), the operation history collection device 100 detects an operation on the operation target by the worker by using the agent software. (Step S202). Then, the operation history collection device 100 collects the operation content for the detected operation object (step S203). Thereafter, the operation history collection device 100 transmits the collected operation content information to the operation history management device 200 as operation history information (step S204).

  Subsequently, the operation history management apparatus 200 performs format conversion of the received operation history information (step S205). Thereafter, the operation history management apparatus 200 outputs an operation history information accumulation request to the information management DB 300, and transmits and stores the operation history information after format conversion to the information management DB 300 (step S206). The information management DB 300 accumulates operation history information after format conversion (step S207).

  This operation history information collection processing sequence is executed every time an operation to be collected is performed by an operator, and operation history information necessary for the manhour calculation processing in the work manhour calculation system 10 is stored in the information management DB 300. Stored. FIG. 7 shows an example of the data structure of the operation history information collected by the operation history collection device 100 and stored in the information management DB 300 by the operation history management device 200 in the work man-hour calculation system 10 of the present embodiment. FIG. 7A shows an example of the data structure of the operation history information, FIG. 7B shows an example of parameters associated with the operation of the application used by the worker, and FIG. Shows an example of information on the operation result of the application.

  In the example of the data structure of the operation history information shown in FIG. 7A, an example is shown in which each information is divided into a plurality of levels and registered. For example, “header information”, “application operation information”, and “operation result information” are collected as the highest level information. Further, for example, in “application operation information”, “application name”, “start flag”, “end flag”, “operation content” and the like are collected as lower level information, and “operation content” , “Operation object name”, “operation time”, “key count”, “detailed operation content”, and the like are collected as lower-level information. Further, “operation name”, “operation parameter”, etc. are collected as lower level information in “detailed operation content”, and “parameter name”, “parameter value”, etc. are further collected in “operation parameter”. It is collected as lower level information.

  In addition, in the example of the parameter accompanying the operation of the application illustrated in FIG. 7B, an example in which the operation name and the parameter name of the application are registered for each “target application” is illustrated. For example, in “Web browser”, “view” and “input” are registered as operation names, and “target object name” is registered as a parameter name of “input”.

  In addition, the example of the operation result information of the application illustrated in FIG. 7C illustrates an example in which an application operation trigger name and a parameter name are registered for each “target application”. Yes. For example, in the “document creation application”, “file open” and “file close” are registered as trigger names, and “file size” and “number of pages” are registered as respective parameter names.

  The data registered in each item of the operation history information shown in FIG. 7A, the parameters associated with the operation of the application shown in FIG. 7B, and the operation result of the application shown in FIG. This is data representing the contents of “description” shown corresponding to each item in FIG.

  Next, the manhour calculation process (processing 3) by the manhour calculation device 400 will be described. FIG. 8 is a sequence diagram showing the flow of man-hour calculation processing performed by the man-hour calculating device 400 in the work man-hour calculating system 10 of the present embodiment.

  First, the man-hour calculating device 400 causes the Web browser 20 to display an input screen for inputting information on a period for calculating man-hours (step S301). Then, the project manager inputs the manhour calculation period information in accordance with the displayed input screen. Thereafter, the Web browser 20 transmits the input information of the man-hour calculation period to the man-hour calculating device 400 (step S302).

  Subsequently, the man-hour calculation device 400 obtains operation history information (step S303) and project information (step S304) necessary for man-hour calculation processing from the information management DB 300 based on the input man-hour calculation period information. get. Thereafter, the man-hour calculating device 400 calculates the man-hours of the development work in the input man-hour calculation period in the project corresponding to the project information based on the acquired operation history information and project information (step S305).

  Subsequently, the man-hour calculating device 400 transmits the man-hour calculation result to the information management DB 300 for storage (step S306). The information management DB 300 accumulates the man-hour calculation results (step S307). Then, the man-hour calculating device 400 causes the web browser 20 to display information indicating whether or not man-hours have been correctly calculated (step S308). If the man-hours cannot be correctly calculated, the man-hour calculating device 400 may cause the Web browser 20 to display the input screen for the period for calculating the man-hours again, similarly to step S301.

  By such a sequence, the man-hour calculating process in the work man-hour calculating system 10 is performed, and the calculation result is stored in the information management DB 300. Note that the trigger for the man-hour calculation device 400 to start the man-hour calculation process is not limited to the input of information on the man-hour calculation period as in the sequence shown in FIG. For example, it may be some other operation, or may be at predetermined intervals.

  Here, the process for calculating the man-hour in step S305 in the sequence diagram shown in FIG. 8 will be described. In the man-hour calculation process, it is specified which work in the project work (WBS) is the collected operation history. And the operation recorded in the operation history information is the result of the work of WBS defined by each WBS to identify the WBS of the project, the result of the work of the WBS, the work such as the source file, or the work In the case of an operation for a reference object to be referred to, the man-hour of the WBS is calculated based on the content of the operation recorded in the operation history information. In the following description, an object to be managed such as a deliverable or a reference object defined by the WBS is referred to as a “management object”.

  FIG. 9 is a diagram showing an overview of an algorithm for man-hour calculation processing in the work man-hour calculating system 10 of the present embodiment. FIG. 10 is a diagram illustrating an example of information used when the man-hour calculating process is performed in the work man-hour calculating system 10 of the present embodiment.

  In the man-hour calculation process in the work man-hour calculation system 10, first, in step S3051, the project work is determined. In the determination of the project work, it is determined whether or not the operation of the PC (operation history collection apparatus 100) by the worker corresponds to the WBS of the project for which the man-hour is calculated. More specifically, by determining whether or not the operation target included in the operation history information corresponds to the management target of the project for which the current man-hour is calculated, the current operation is the target project work. Determine if there is any other work (outside project work).

  Step S3051 shown in FIG. 9 shows a case where a predetermined “management object judgment criterion” (see FIG. 10A) is used when judging the project work. This management object determination criterion describes information for determining the management object, and is, for example, a table (data) in which a specific character string included in the file name of the management object is described. In determining the project work, it is included in the operation history information by determining whether or not the file name of the operation object includes a specific character string described in the management object determination criterion. It is mechanically determined whether the operation target being operated is a management target of the target project. As with the project information, the management object determination criterion may be registered in advance in the information management DB 300 by the project manager, or may be created in advance based on the management object information included in the WBS information. .

  In step S3051, the operation history information determined to be the project work for which the man-hour is calculated is the operation contents included in the operation history information in the subsequent step S3052, and the work of any WBS in the project. It is determined whether it is. Each WBS task has a unique characteristic (hereinafter referred to as “work type”; for example, coding, test, review, etc.), and the operation type (editing, browsing, etc.) for the deliverable or the reference object depending on the feature. ) Is different. Therefore, in the determination of the WBS work of the operation content, first, in step S3052, the operation type for the operation target is determined using the operation content included in the operation history information.

  Step S3052 shown in FIG. 9 shows a case where a predetermined “operation type determination criterion” (see FIG. 10B) is used when determining the operation type. This operation type determination criterion describes a criterion for determining the operation type for the operation target. For example, “operation time (window active time)” or “ Values such as “Key Touch Count” are included. In determining the operation type, the operation type is mechanically determined by determining whether or not the operation of the operation target file is equal to or greater than a value included in the operation type determination criterion. The value of the operation type determination criterion may be determined in advance, but may be determined, for example, by an experiment.

  In step S3053, the WBS of the project work is specified based on the operation history information. Step S3053 shown in FIG. 9 shows a case where “WBS information” (see FIG. 10C) included in predetermined project information is used when specifying the WBS. More specifically, the operation target included in the operation history information is compared with the management target included in the WBS information, and a WBS including the same management target as the operation target is selected.

  Subsequently, in step S3054, it is determined whether to perform the WBS work based on the operation type for the operation target. In the execution determination of the WBS work, it is determined whether or not the operation content included in the operation history information is an operation for executing the WBS work.

  Step S3054 shown in FIG. 9 shows a case where a predetermined “WBS work execution determination criterion” (see FIG. 10D) is used in the WBS work execution determination. This WBS work execution determination criterion describes a criterion for determining whether or not the WBS work has been executed according to the operation type for the operation on the management target object. For example, the operation type for the WBS product (FIG. 10B) The operation type in the operation type determination criterion shown in FIG. Then, in the execution determination of the WBS work, it is determined whether or not the operation included in the operation history information has performed the WBS work by determining whether or not an operation that matches the WBS work execution determination criterion has been performed. To do. Here, the operation recorded in the operation history information determined to have performed the WBS work is used as the WBS work for calculating the man-hours. Further, the operation history information determined that the WBS work has not been performed is not used for calculating the man-hours as work related to projects other than the WBS.

  Here, an example in which it is determined whether or not the operation included in the operation history information has performed the WBS work will be described. FIG. 11 is a diagram illustrating an example when the man-hour calculation processing algorithm is performed in the work man-hour calculating system 10 of the present embodiment. The example shown in FIG. 11 is an example of processing in a case where it is determined which WBS work execution corresponds to an operation (daily operation ID = 00001) for one operation target. 11A shows operation history information in FIG. 11A, FIG. 11B shows management object determination criteria, FIG. 11C shows operation type determination criteria, and FIG. 11D shows WBS work execution determination. Reference and FIG. 11 (e) show the WBS information of the project information, respectively. FIG. 11 also shows information used in each process.

  First, in process S1, the project work is determined (see step S3051 in FIG. 9). In process S1, it is determined from the management object determination criterion that the daily operation ID = 000001 is “ABC function program of α project”.

  Subsequently, in operation S2, the operation type is determined (see step S3052 in FIG. 9). In the process S2, it is determined from the operation type determination criterion that the operation type of the daily operation ID = 00001 is “debug”.

  Subsequently, in step S3, the WBS is specified (see step S3053 in FIG. 9). In the process S3-1, the management target object with the daily operation ID = 00001 is identified as the “ABC function program” from the result of the process S1. Here, the “ABC function program” is registered as “ABC function test reference” in the WBS information of the project information. From this, in the process S3-1, the WBS with the daily operation ID = 00001 is identified as the “ABC function test”. In addition, since the work type of the WBS “ABC function test” is “test”, in the process S3-2, the WBS work execution determination standard of the WBS “ABC function test” is the reference “ABC function”. It can be seen that “reference object = debug” for “program”.

  Subsequently, in step S4, the execution determination of the WBS work is performed (see step S3054 in FIG. 9). From the result of the processing S2, it is determined that “debugging” has been performed for the daily operation ID = 00001. That is, the daily operation ID = 000001 satisfies the “reference object = debug” of the WBS work execution determination standard. From this, in the process S4, it is determined that the WBS work of the WBS “ABC function test” is performed with the daily operation ID = 00001.

  Next, another example in the case where it is determined whether or not the operation included in the operation history information has performed the WBS work will be described. FIG. 12 is a diagram illustrating another example when the manhour calculation processing algorithm is performed in the work manhour calculation system 10 of the present embodiment. The example shown in FIG. 12 is an example of processing in the case of determining operations on two operation objects (daily operation ID = 00002 and daily operation ID = 00003). 12A shows operation history information in FIG. 12A, FIG. 12B shows management object judgment criteria, FIG. 12C shows operation type judgment criteria, and FIG. 12D shows WBS work execution judgment. The WBS information of the project information is shown in the standard and FIG. FIG. 12 also shows information used in each process.

  First, in process S1, the project work is determined (see step S3051 in FIG. 9). In process S1-1, it is determined from the management object determination criterion that the daily operation ID = 000002 is the “β project review result table”. Moreover, in process S1-2, it determines with daily operation ID = 00003 being "the user manual of (beta) project" from management object determination criteria.

  Subsequently, in operation S2, the operation type is determined (see step S3052 in FIG. 9). In the process S2-1, it is determined from the operation type determination criterion that the operation type of the daily operation ID = 00000 is “edit”. Further, in the process S2-2, it is determined from the operation type determination criterion that the operation type with the daily operation ID = 00003 is “browsing”.

  Subsequently, in step S3, the WBS is specified (see step S3053 in FIG. 9). In the process S3-1-1, the management target with the daily operation ID = 000002 is identified as the “review result table” from the result of the process S1-1. Here, the “review result table” is registered as “user manual review output” in the WBS information of the project information. From this, in the process S3-1-1, the WBS with the daily operation ID = 000002 is identified as “user manual review”. Further, since the work type of the user manual review is “review”, in the process S3-1-2, the first WBS work execution determination criterion of the WBS “user manual review” is the deliverable from the WBS work execution determination criterion. It can be seen that the edit to the “review result table” is “deliverable = edit”.

  Moreover, in process S3-2-1, the management target object with daily operation ID = 00003 is identified as the “user manual” from the result of process S1-2. Here, the “user manual” is registered as “reference material for user manual review” in the WBS information of the project information. From this, in the process S3-2-1, the WBS with the daily operation ID = 00003 is identified as “user manual review”. Further, since the work type of the user manual review is “review”, in the process S3-2-2, the second of the WBS work execution determination criteria of the WBS “user manual review” is referred to from the WBS work execution determination criteria. It can be seen that “reference object ≠ edit” with respect to the “user manual”.

  Subsequently, in step S4, the execution determination of the WBS work is performed (see step S3054 in FIG. 9). From the result of the process S2-1, it is determined that “editing” is performed in the daily operation ID = 000002. Further, from the result of the process S2-2, it is determined that “browsing” is performed in the daily operation ID = 00003. That is, the daily operation ID = 000002 satisfies the first condition “deliverable = edit” of the WBS work execution determination standard, and the daily operation ID = 00003 is the second condition of the WBS work execution determination standard. Satisfy "All references ≠ Edit". Thus, when the daily operation ID = 00002 and the daily operation ID = 00003 are combined, it is determined in step S4 that the WBS work of the WBS “user manual review” has been performed.

  Next, WBS man-hour calculation processing will be described. FIG. 13 is an example of a flowchart illustrating a processing procedure of man-hour calculation processing in the work man-hour calculating system 10 of the present embodiment. FIG. 14 is a diagram illustrating an example of information used when the man-hour calculating process is performed in the work man-hour calculating system 10 of the present embodiment or information obtained as a result of the man-hour calculating process.

  Based on the operation history information, man-hours are calculated for each man-hour totaling unit (operation unit, daily operation unit, management object-specific work unit, WBS-specific work unit), and the respective calculation results are stored in the man-hour management DB 330 ( accumulate. In addition, the operation history data determined to be performing the same WBS work are added together.

  First, when a man-hour calculation period is input from the Web browser 20 in step S302, the man-hour calculating apparatus 400 calculates the operation unit shown in step S351 based on the input operation history information in all the calculation periods. Perform the process. Note that the operation unit calculation processing loop in step S351 is repeated until the calculation of the operation unit in the calculation period input in step S302 is completed.

  Here, the operation unit is a sequence when the same worker performs the same operation on the same managed object with the same application usage type and the same application usage type, that is, adjacent in time. The work to be done. The “same work” is defined by an application or an operation on the application. For example, the operation history information at time t and the operation history information at time t + 1 adjacent to the PC (operation history collection apparatus 100). In this case, the screen saver is not activated and an operation is being performed on the same management object (the window is active) (see FIG. 14A).

  Further, in the calculation of the operation unit, it is determined that the same worker is “same work” even when the same worker operates the same management object using another account of a different PC (operation history collection apparatus 100). To do. For example, whether or not the account A and the account B are the same worker's account is determined based on information described in “account information” in the personal profile information included in the project information. If the dates of time t and time t + 1 are different, it is determined that time t and time t + 1 are not continuous. That is, the operation unit is divided into operations on the same date as one unit, and operations across dates are divided into different operation units.

  In the operation unit calculation processing in step S351, first, in step S3511, the DB access unit 420 in the manhour calculation device 400 acquires operation history information within all calculation periods from the operation history information DB 310, and the information transmission / reception unit 410. Is output to the man-hour calculation unit 430. Subsequently, in step S3512, the man-hour calculating unit 430 determines operation history information used for the man-hour calculating process from all the input operation history information using the algorithm shown in FIG. 9, and calculates an operation unit. Then, the man-hour calculation unit 430 stores (accumulates) the operation unit calculation result (see FIG. 14B) in the man-hour management DB 330 via the information transmission / reception unit 410 and the DB access unit 420.

  When the operation unit calculation processing loop in step S351 ends, the man-hour calculation device 400 performs the daily operation unit calculation processing shown in step S352 based on the calculated operation unit calculation result. Note that the daily operation unit calculation processing loop in step S352 is repeated until the calculation of the daily operation unit in the calculation period input in step S302 is completed.

  Here, the daily operation unit refers to a result obtained by tabulating, for each operation unit, those having the same “worker”, “day”, “operation object”, and “application usage type”. When the same worker operates the same managed object on the same day with the same application, it belongs to the same daily operation unit.

  In the daily operation unit calculation process in step S352, first, in step S3521, the DB access unit 420 in the manhour calculation device 400 acquires all the operation units stored in step S351 from the manhour management DB 330, and transmits and receives information. The data is output to the man-hour calculation unit 430 via the unit 410. Subsequently, in step S3522, the man-hour calculating unit 430 calculates a daily operation unit based on all input operation units. Then, the man-hour calculating unit 430 stores (accumulates) the calculation result of the daily operation unit (see FIG. 14C) in the man-hour management DB 330 via the information transmitting / receiving unit 410 and the DB access unit 420.

  When the processing loop for calculating the daily operation unit in step S352 ends, the man-hour calculation device 400 continues to calculate and operate the operation unit for each management object shown in step S353 based on the result of the calculated daily operation unit. The type determination process is performed. It should be noted that the management object-specific work unit calculation and operation type determination processing loop in step S353 is repeated until the management object-specific work unit calculation and operation type determination in the calculation period input in step S302 is completed.

  Here, the work unit by management object refers to the result of totaling the same “operator” and “management object” for each daily operation unit. More specifically, for example, depending on whether or not the operation object included in the daily operation unit matches the management object determination criterion registered as project information, it is included in the same management object-specific work unit. It is determined whether or not. Further, based on the information of “operation time” and “number of key touches” included in the work unit by management object, for example, the determination is performed according to the operation type determination standard shown in FIG. Determine the operation type of another unit of work.

  In the process of calculating the work unit by management object and determining the operation type in step S353, first, in step S3531, the DB access unit 420 in the man-hour calculation device 400 stores all the daily data stored in step S352 from the man-hour management DB 330. The operation unit is acquired and output to the man-hour calculation unit 430 via the information transmission / reception unit 410. Subsequently, in step S3532, the DB access unit 420 in the man-hour calculating device 400 acquires project information from the project information management DB 320 and outputs the project information to the man-hour calculating unit 430 via the information transmitting / receiving unit 410. Subsequently, in step S3533, the man-hour calculating unit 430 calculates a management unit-specific work unit and determines an operation type based on all the input daily operation units and project information. Then, the man-hour calculation unit 430 manages the man-hour management through the information transmission / reception unit 410 and the DB access unit 420, using the information transmission / reception unit 410 and the DB access unit 420, for the calculation result (see FIG. Store (accumulate) in the DB 330.

  When the processing loop for management object-specific work unit calculation and operation type determination in step S353 is completed, the man-hour calculation device 400 continues based on the result of the management object-specific work unit calculated in step S354. Processing for calculating another work unit is performed. It should be noted that the processing loop for calculating work units by WBS in step S354 is repeated until the calculation of work units by WBS for the calculation period input in step S302 is completed.

  Here, the work unit by WBS refers to the result of totaling the “workers” and “WBS” having the same work unit for each managed object. The calculation of work units by WBS is performed for each WBS. The WBS to be calculated is the lowermost WBS (corresponding to a leaf node in the WBS tree), and other cases (WBS In the tree, which corresponds to the internal node). In the process for calculating the work unit by WBS in step S354, the work units by management object are tabulated for the WBS that satisfies the WBS work execution determination criterion, with the WBS in the lowest layer as the calculation target. The work units by management object that have not been counted as work units by WBS are added together as project works that are not determined to have been subjected to the WBS work.

  In addition, the calculation of the work unit by WBS for the WBS corresponding to the internal node in the WBS tree that is not the lowermost WBS is the calculation result of the work unit by WBS in step S354 corresponding to the leaf node in the WBS tree. By adding together in step S355 described later, the work unit by WBS is calculated.

  In the process of calculating the work unit by WBS in step S354, that is, the process of calculating the work unit by WBS of the leaf node, first, in step S3541, the DB access unit 420 in the man-hour calculation device 400 starts from the man-hour management DB 330 to step S353. All the work units for each management object stored in step S1 are acquired and output to the man-hour calculation unit 430 via the information transmission / reception unit 410. Subsequently, in step S3542, the DB access unit 420 in the man-hour calculating device 400 acquires project information from the project information management DB 320 and outputs the project information to the man-hour calculating unit 430 via the information transmitting / receiving unit 410. Subsequently, in step S3543, the man-hour calculation unit 430 calculates the work unit by WBS of the leaf node based on all input work units by management object and project information. Then, the man-hour calculating unit 430 stores (accumulates) the calculation result of the work unit for each WBS of the leaf node (see FIG. 14E) in the man-hour management DB 330 via the information transmitting / receiving unit 410 and the DB access unit 420. .

  When the processing loop for calculating the work unit by WBS of the leaf node in step S354 is finished, the man-hour calculation device 400 subsequently performs the WBS of the internal node in step S355 based on the calculated result of the work unit by WBS of the leaf node. Calculation (summation) processing of another work unit is performed. By the calculation (summation) of the work unit by WBS of the internal node in step S355, the work unit by WBS of the upper node is calculated from the work unit by WBS of the leaf node.

  In the process of calculating the work unit by WBS of the internal node in step S355 (summing up), the DB access unit 420 in the man-hour calculating device 400 obtains the work unit by WBS of all leaf nodes stored in step S354 from the man-hour management DB 330. The information is acquired and output to the man-hour calculation unit 430 via the information transmission / reception unit 410. Then, the man-hour calculation unit 430 adds the input work units by WBS of all the leaf nodes, calculates the work units by WBS of the internal nodes, and calculates the calculation results of the work units by WBS of the internal nodes as information It is stored (accumulated) in the man-hour management DB 330 via the transmission / reception unit 410 and the DB access unit 420. In addition, in the summation of the work units by WBS of the internal nodes, for example, those having the same “parent WBSID of project information” are summed. The format of the calculation result of the work unit by WBS of the internal node is the same as the format of the calculation result of the work unit by WBS of the leaf node shown in FIG.

  As described above, in the man-hour calculation process in the work man-hour calculating system 10 of the present embodiment, the man-hour calculation result associated with “WBS”, “worker”, and “day (time)” is obtained. Thereby, in the work man-hour calculation system 10, the relationship between “WBS”, “worker”, and “day (time)” is shown.

  In the processing procedure of the man-hour calculation process shown in FIG. 13, the case where the calculation results obtained in the respective calculation processing steps are stored (accumulated) in the man-hour management DB 330 each time has been described. The apparatus 400 may include a storage area that holds the calculation result, and the calculation result may be held in the storage area. In this case, the calculation result of the previous calculation processing step held in the storage area is used in the next calculation processing step.

  In the man-hour calculation process shown in FIGS. 8 and 13, the case has been described in which the man-hour calculation device 400 executes the man-hour calculation process in response to an effective request for the man-hour calculation process by the project manager. The configuration may be such that the man-hour calculation process is automatically executed even when there is no effective calculation process request. For example, based on the operation history information for one day stored (accumulated) in the information management DB 300 at night, the man-hour calculation process for one day is executed in advance, and the man-hour calculation result is stored in the information management DB 300. Store (accumulate).

  Next, the process (process 4) for displaying the calculation result of the man-hour will be described. FIG. 15 is a sequence diagram showing the flow of display processing of the man-hour calculation result in the work man-hour calculating system 10 of the present embodiment. In the display of the man-hour calculation result, information on the man-hour is displayed in various formats according to the calculation result obtained by the man-hour calculating process by the man-hour calculating device 400. For example, information in a format that summarizes the work status in time series, information in a format that summarizes the work status for each worker, information in a format that summarizes the operation status for each worker, and the like are displayed. More specifically, “WBS” and “day (time)” indicate the work status in time series, “WBS” and “worker” indicate the work status for each worker, and “worker” The operation status for each worker is shown from "day (time)". Detailed description regarding the display type of the calculation result of the man-hour will be described later.

  First, the man-hour calculating device 400 causes the Web browser 20 to display an input screen for inputting information on a period for displaying the man-hour calculation result and a display type (step S401). Then, the project manager inputs information on the period and display type for displaying the calculation result of the man-hour according to the displayed input screen. Thereafter, the Web browser 20 transmits information on the period and display type for displaying the input man-hour calculation result to the man-hour calculating device 400 (step S402).

  Subsequently, the man-hour calculation device 400 receives man-hour information (calculation result in the man-hour calculation process) necessary for the man-hour display process from the information management DB 300 based on the period and display type information for displaying the input man-hour calculation result. ) Is acquired (step S403). Thereafter, the man-hour calculating device 400 generates a display screen to be displayed on the web browser 20 based on the acquired man-hour information (step S404).

  Subsequently, the man-hour calculation device 400 transmits the generated display screen to the Web browser 20 for display (step S405). As a result, the man-hour calculation result of the period and display type input by the project manager is displayed (presented).

  By such a sequence, display processing of the man-hour calculation result in the work man-hour calculating system 10 is performed. The man-hour calculation device 400 generates all display screens of a predetermined display type and first displays (presents) the display type input by the project manager, and then performs some operation (for example, on the display screen). The generated display screens may be sequentially switched and displayed according to a predetermined area clicked).

  Here, some examples of the display type of the calculation result of the man-hour in the work man-hour calculating system 10 are shown. FIGS. 16 to 18 are diagrams schematically illustrating examples of display types of man-hour calculation results in the work man-hour calculating system 10 of the present embodiment. FIG. 16 shows an example of a display result in a format that summarizes the work status in time series, FIG. 17 shows an example of a display result in a format that summarizes the work status for each worker, and FIG. It shows an example of a display result in a format that summarizes the operation status for each person.

  First, the display items common to the display of the man-hour calculation result in the work man-hour calculating system 10 will be described using the time-series work status display result shown in FIG. The man-hour calculation result display screen includes a tag area A, a project setting area B, a period setting area C, an item display area D, and a work status display area E.

  In the tag area A, display types for displaying the man-hour calculation results are arranged, and when the project manager selects any one tag, the man-hour of the display type associated with the selected tag on the display screen. Switch to the calculation result. The project setting area B is an area for selecting a project for displaying the man-hour calculation result. In the project setting area B, for example, the project name of the project information stored (accumulated) in the project information management DB 320 in the information management DB 300 is displayed in a pull-down menu, and the project manager selects the displayed project name. Select the project to display the man-hour calculation result. The period setting area C is an area for setting a period for displaying the man-hour calculation result. The period for displaying the man-hour calculation result is set by a pull-down menu or direct input. In the item display area D, an item for displaying the man-hour calculation result is displayed. In the work status display area E, the calculation result of the man-hour is displayed for each item displayed in the item display area D.

  Next, display contents unique to the display result of the time-series work status shown in FIG. 16 will be described. The time-series work status display is a display based on the relationship between “WBS” and “day (time)” of the man-hour calculation result. In the time-series work status display shown in FIG. 16, each item of “WBS” is displayed in the item display area D, and the work status for each “day (time)” in each item of WBS is displayed in the work status display area E. Is displayed. More specifically, on the time-series work status display screen, the work plans and results of each WBS are displayed side by side as the work status (display e1), and the total work time of the WBS with the results is represented by a number. (Display e2). Moreover, today is distinguished and displayed (display e3).

  By displaying such a display screen, the project manager can overlook the progress of the project. Thereby, it is possible to grasp the time that contributes to the progress of the WBS work (creation of the deliverables) and the work situation for each WBS. In addition, from the difference between the actual start time of the WBS work and the plan, it is possible to visually recognize the situation such as advance start and delay of the WBS work. In addition, it is possible to grasp the execution of work (display e4) that is not in the plan.

  Next, display contents specific to the display result of the work status for each worker shown in FIG. 17 will be described. The display of the work status for each worker is a display based on the relationship between “WBS” and “worker” in the man-hour calculation result. In the work status display for each worker shown in FIG. 17, each item of “WBS” is displayed in the item display area D, and the status of “worker” is displayed in the work status display area E. More specifically, on the display screen of the work status for each worker, the group name and the workers belonging to the group are hierarchically displayed (display e5), and each WBS and the group and the worker who performed the WBS work are displayed. Correspondence is indicated (display e6), and the total work time during which WBS work is performed is indicated by numbers (display e7). In addition, the progress of each WBS is shown separately (display e8).

  By displaying such a display screen, the project manager can overlook the work contents for each worker. Thereby, it is possible to grasp the workload of each worker and the balance of the workload in the entire project. In addition, it is possible to visually recognize the progress of the project (such as “as planned”, “planned delay”, “caution”, “advanced start”, “no work results”, etc.). In the work status display for each worker shown in FIG. 17, each WBS item has a box corresponding to “as planned”, “planned delay”, “caution”, and “advance start”. The case where there is no work is described as “no work record”.

  Note that “as planned” means that the man-hour calculation result display period set by the project manager depends on part or all of the implementation period (plan period) in the WBS plan and is actually within the displayed plan period. Shows the case where WBS work is carried out. “Plan delay” indicates that the WBS work has been carried out after the scheduled completion date of the WBS, and “Caution required” means that the WBS work has not been carried out within the displayed plan period. Indicates. “Preceding start” indicates that the WBS work is performed before the scheduled start date of the WBS, and “no work result” indicates that none of the above conditions are met, that is, in the period setting area. The WBS that is not determined to have performed the WBS work in the set period is shown.

  Next, display contents specific to the display result of the operation status for each worker shown in FIG. 18 will be described. The display of the operation status for each worker is a display based on the relationship between “worker” and “day (time)” of the man-hour calculation result. In the operation status display for each worker shown in FIG. 18, “worker” is displayed in the item display area D, and the work status for each “day (time)” of each worker is displayed in the work status display area E. doing. More specifically, on the operation status display screen for each worker, the group name and the workers belonging to the group are represented hierarchically (display e9), and the work plans and results of each worker are displayed side by side ( The display e10) represents the total work time in which each group or each person in charge has performed the WBS work (display e11). Moreover, today is distinguished and displayed (display e12).

  By displaying such a display screen, the project manager can overlook the operating status of each worker. Thereby, it is possible to visually recognize the worker who has contributed to the progress of the WBS work (creation of a product) and the period during which the WBS work has been performed. It is also possible to grasp the actual work time required for the entire project and each WBS work.

  As described above, according to the embodiment for carrying out the present invention, operation history information of a work terminal used when a worker performs a development work is automatically collected. Then, based on the collected operation history information, the man-hour of the work performed by the worker is mechanically calculated in units of WBS. In calculating the man-hours, the operation history information of the work terminal that is operated when the worker actually performs the development work is used as the man-hour calculation target, so that the work man-hours can be grasped more accurately. .

  Moreover, according to the form for implementing this invention, the manager of a project can present the information for grasping | ascertaining the work content and work time for every worker based on the calculation result of a man-hour. Moreover, the information of the actual work time required for the work can be presented for each work item. Accordingly, it is possible to provide an operation man-hour calculating device capable of supporting project management such as project man-hour management and progress management, or early detection of risk. As a result, in the form for carrying out the present invention, it is possible to automatically grasp the work contents that depended on the self-declaration of the worker himself in the progress management of the conventional project, and the risk in software development Can be easily detected early. Note that the scope of application of the embodiment for carrying out the present invention is not limited to software development, and can be easily applied to general business.

  In the embodiment for carrying out the present invention, the operation history management device 200, the information management DB 300, the man-hour calculation device 400, and the project information management device 500 are each calculated as a work man-hour comprising different terminal devices. Although the case of the system 10 has been described, the apparatus configuration of the work man-hour calculating system 10 is not limited to the form for carrying out the present invention. For example, even when the operation history management device 200, the information management DB 300, the man-hour calculation device 400, and the project information management device 500 are configured with the same terminal device, the present invention is implemented within the same terminal device. If it is the structure which implement | achieves the function similar to this form, the same process can be performed and the same result can be obtained.

  Note that a program for realizing processing by each component in the work man-hour calculating system 10 shown in FIGS. 1 and 2 is recorded on a computer-readable recording medium, and the program recorded on the recording medium is recorded. The above-described various processes related to the work man-hour calculating system 10 may be performed by being read and executed by a computer system. Here, the “computer system” may include an OS and hardware such as peripheral devices. Further, the “computer system” includes a homepage providing environment (or display environment) if a WWW system is used. The “computer-readable recording medium” means a flexible disk, a magneto-optical disk, a ROM, a writable nonvolatile memory such as a flash memory, a portable medium such as a CD-ROM, a hard disk built in a computer system, etc. This is a storage device.

  Further, the “computer-readable recording medium” refers to a volatile memory (for example, DRAM (Dynamic) in a computer system serving as a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. Random Access Memory)) that holds a program for a certain period of time is also included. The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for realizing a part of the functions described above. Furthermore, what implement | achieves the function mentioned above in combination with the program already recorded on the computer system, and what is called a difference file (difference program) may be sufficient.

  The embodiment of the present invention has been described above with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes various modifications within the scope of the present invention. It is.

10 ... Man-hour calculation system 100 ... Operation history collection device (working terminal)
110 ... Operation history collection unit (working terminal)
120: Information transmission unit (working terminal)
200 ... Operation history management device (work man-hour calculation device)
210 ... Information transmission / reception unit (work man-hour calculation device)
220 ... DB access unit (work man-hour calculating device)
300 ... Information management DB (operation history information database, project information management database, man-hour management database)
310 ... Operation history information DB (operation history information database)
320 ... Project information management DB (project information management database)
330 ... Effect management DB
400 ... man-hour calculating device (man-hour calculating unit)
410 ... Information transmission / reception unit (man-hour calculation unit)
420 ... DB access part (man-hour calculation part)
430 ... man-hour calculating unit 500 ... project information management device (work man-hour calculating device)
510... Information transmission / reception unit (work man-hour calculation device)
520... DB access unit (work man-hour calculating device)
20 ... Web browser (management terminal)

Claims (7)

Project information management database for pre-registering project information including information indicating a product generated by the work of each process of the project or a management object including a reference material referred to when performing the work of the process When,
It includes information indicating the operation date and time, the operation object operated by the operator, and the name of the operation performed by the operator on the operation object, obtained from the work terminal that performs the work of each process of the project An operation history information database for storing operation history information;
Based on the project information and the operation history information, a man-hour calculating unit that calculates man-hours in each process of the project;
An operation man-hour calculating device comprising: The man-hour calculation unit
Based on a management object determination criterion in which a condition for determining the management object in each step of the project is predetermined, the operation object included in the operation history information is any one of the projects Determining whether the operation history information is project operation history information corresponding to the project by determining whether the process corresponds to the management object;
Based on an operation type determination criterion in which a condition for determining the operation type according to the operation content for the operation target is determined in advance, the operation type of the operation content included in the project operation history information is determined,
By specifying a process in the project in which the management object corresponding to the operation object included in the project operation history information is included as a work execution candidate process, a work type in the work execution candidate process is specified. ,
The operation type of the project operation history information is determined to be the operation execution candidate step based on an operation execution determination criterion in which a condition for determining the execution of the operation corresponding to the operation type in each step of the project is determined. Whether or not the operation content included in the project operation history information has performed the work of the work execution candidate process by determining whether or not the work execution condition corresponding to the work type in Determine
The project operation history information determined to have performed the work of the work execution candidate process is used as the man-hour calculation operation history information to calculate the man-hour in each process of the project.
The work man-hour calculating apparatus according to claim 1. The operation history information includes information on the worker,
The man-hour calculation unit
The man-hour calculating operation history in which the operation date and time included in the man-hour calculating operation history information is continuous, and the worker information, the operation object, and the application usage type included in the man-hour calculating operation history information are the same. Based on the information, calculate the man-hour for the operation unit,
Based on the man-hour of the operation unit on the same day in the man-hour of the calculated operation unit, calculate the man-hour of the daily operation unit,
In the calculated daily operation unit man-hour, the man-hour of the management object-specific operation unit is calculated based on the worker information and the man-hour of the daily operation unit in which the management object in the corresponding project is the same. Calculate, and further, based on the operation type determination criteria, determine the operation type of the man-hour of the calculated work unit by management object, and add the determined operation type to the calculated work unit by management object And
In the man-hours of the work units by management object to which the operation type is added, the work units by process based on the man-hours of the work units by management object in which the processes of the worker information and the corresponding project are the same. Calculate the man-hour for
In the man-hours of the calculated work units by process, the man-hours of the work units by process in which the project is the same are calculated, thereby calculating the man-hours in each process of the project.
The work man-hour calculating apparatus according to claim 2. Based on the calculation result of the man-hour in each step of the project calculated by the man-hour calculation unit, among the steps of the project, the worker, and the work execution period included in the calculation result of the man-hour, A display screen generating unit that generates a display screen in which any two items are associated, and outputs the generated display screen to a management terminal that manages the project;
Further comprising
The work man-hour calculating device according to any one of claims 1 to 3, characterized in that: The project information includes information on a planned period for performing each process of the project,
The display screen generation unit
Based on the plan period included in the project information and the work execution period, the display screen including information indicating progress of each process of the project is generated.
The work man-hour calculating apparatus according to claim 4. In the project information management database, project information including information indicating a management object including a deliverable generated by work of each process of the project or a reference object referred to when performing the work of the process is registered in advance. Steps to keep
In the operation history information database, the operation date and time, the operation object operated by the operator, and the operation performed by the operator on the operation object acquired from the work terminal that performs the work of each process of the project Storing operation history information including information indicating a name;
Based on the project information and the operation history information, a man-hour calculating step for calculating man-hours in each process of the project;
The work man-hour calculation method characterized by including. In the project information management database, project information including information indicating a management object including a deliverable generated by work of each process of the project or a reference object referred to when performing the work of the process is registered in advance. Steps to keep
In the operation history information database, the operation date and time, the operation object operated by the operator, and the operation performed by the operator on the operation object acquired from the work terminal that performs the work of each process of the project Storing operation history information including information indicating a name;
Based on the project information and the operation history information, a man-hour calculating step for calculating man-hours in each process of the project;
A program that causes a computer to execute.

Images