WO2013108334A1 - 評価装置、評価方法、および、評価プログラム - Google Patents
評価装置、評価方法、および、評価プログラム Download PDFInfo
- Publication number
- WO2013108334A1 WO2013108334A1 PCT/JP2012/007926 JP2012007926W WO2013108334A1 WO 2013108334 A1 WO2013108334 A1 WO 2013108334A1 JP 2012007926 W JP2012007926 W JP 2012007926W WO 2013108334 A1 WO2013108334 A1 WO 2013108334A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- workers
- work
- evaluation
- development
- pair
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0639—Performance analysis of employees; Performance analysis of enterprise or organisation operations
- G06Q10/06398—Performance of employee with respect to a job function
Definitions
- the present invention relates to an evaluation apparatus, an evaluation method, and an evaluation program, and more particularly, to an evaluation apparatus, an evaluation method, and an evaluation program for system evaluation of system development and operation.
- the device disclosed in Patent Document 1 is that when the amount of communication logs measured between individuals in the observation period (number of meetings, total time, number of emails, etc.) exceeds a predetermined threshold, there is a link between the individuals. to decide.
- the apparatus calculates and outputs an index indicating how central a person is based on the number of links that the individual has with other individuals.
- Patent Document 2 discloses a device that analyzes the content and scale of communication that occurs in a certain organization and is used in other organizations and evaluates the value of the organization. To do.
- Patent Document 3 discloses an apparatus for registering association of various information.
- Patent Document 4 discloses a client device that searches log files.
- JP 2008-257539 A Japanese Laid-Open Patent Publication No. 2004-252946 JP 2003-150644 PR Japanese Laid-Open Patent Publication No. 2001-22613
- Patent Document 1 does not consider work attributes such as processes and roles in the analysis.
- An object of the present invention is to provide an evaluation apparatus, an evaluation method, and an evaluation program capable of solving the above-described problems and performing organization evaluation for each attribute of development and operation work.
- An evaluation apparatus has, for each of a plurality of workers engaged in system development or operation work, the worker having any of a plurality of work attributes related to the work.
- Worker information storage means for storing a work table indicating the period of time,
- log storage means for storing a work log that records the occurrence time of the interaction and the workers who participated; From the work log, for each combination of the plurality of work attributes and the plurality of worker pairs, the number of the interactions in the pair performed when the workers constituting the pair have the work attributes.
- evaluation means for calculating and outputting a relationship strength indicating the strength of the relationship between the workers constituting the pair.
- An evaluation program has, for each of a plurality of workers engaged in system development or operation work, the worker having any of a plurality of work attributes related to the work.
- a worker information storage process for storing a work table indicating a period of time, For each interaction between the plurality of workers, a log storage process for storing a work log in which the occurrence time of the interaction and the workers who participated are recorded; From the work log, for each combination of the plurality of work attributes and the plurality of worker pairs, the number of the interactions in the pair performed when the workers constituting the pair have the work attributes. Based on this, the computer is caused to execute an evaluation process for calculating and outputting a relationship strength indicating the strength of the relationship between the workers constituting the pair.
- An evaluation method has, for each of a plurality of workers engaged in system development or operation work, the worker having any of a plurality of work attributes related to the work.
- the present invention makes it possible to analyze a log and perform development organization evaluation for each attribute of development and operation work such as work process and role.
- the present invention facilitates management and analysis of development and operation projects by analyzing logs and clarifying the actual state of work.
- FIG. 3 is a schematic operation flowchart of an evaluation unit 11 of the evaluation device 10. 6 is an operation flowchart of processing in which the evaluation unit 11 accumulates the relationship strength with reference to an access log 50.
- an evaluation unit 11 refers to a cooperation log 60 and is an operation flowchart of a process of accumulating relation strengths. It is a block diagram of the evaluation apparatus 10 which concerns on 3rd Embodiment.
- FIG. 1 is a diagram showing the relationship between workers and software development / operation processes.
- the software is developed through a plurality of development processes and is then put into operation.
- software is developed through each development process of requirements analysis (RA), system analysis (SA), architecture design (AD), and application implementation (AI) in sequence, and is put into operation in the cloud operation management process (COM).
- RA requirements analysis
- SA system analysis
- AD architecture design
- AI application implementation
- the worker a is engaged in requirements analysis in the period A, system analysis in the period B, and architecture design in the period C, and then in the period D. And return to requirements analysis. That is, the software development shown in the example of FIG. 1 returns to the process in which the development work is once completed between the periods C and D.
- Worker a is then engaged in system analysis in period E, architecture design in period F, application implementation in period G, and cloud operation management in period H.
- FIG. 2 is a diagram showing the relationship between workers and roles.
- a worker engaged in a software development project has a role to play in the project, that is, a role.
- the role of one worker may change with the process.
- one worker may have a plurality of rolls in one process. In this embodiment, in order to simplify the description, one worker has one roll for a certain period.
- worker a has the role of service designer (SD) in the requirements analysis and system analysis processes.
- This worker a has three roles of service designer, resource planner (RP) and application implementer (AI) in the architecture design process, and resource planner and application implementer in the application implementation process.
- RP resource planner
- AI application implementer
- the worker a has two roles of a service administrator (SA) and a cloud administrator (CA) in the cloud operation management process.
- SA service administrator
- CA cloud administrator
- FIG. 3 is an overall configuration diagram of the evaluation system 30 according to the present embodiment.
- the evaluation system 30 includes an evaluation apparatus 10 and a development operation support server 20 connected to the evaluation apparatus 10 via a communication line or the like.
- the evaluation device 10 includes an evaluation unit 11, a log storage unit 12, and an operator information storage unit 13 that are configured by a logic circuit, a storage device, and the like.
- the evaluation unit 11 is connected to the display device 14.
- the evaluation device 10 may be a computer that operates under program control.
- the evaluation unit 11 may be realized by a processing device included in the computer reading and executing a program stored in the storage device.
- the log storage unit 12 and the worker information storage unit 13 may be a disk device provided in a computer.
- the development operation support server 20 is, for example, a server computer equipped with a CASE (Computer-added Software Engineering) tool.
- the development operation support server 20 includes a support unit 21 that executes a CASE tool and a development repository 22 that stores information related to development.
- the support unit 21 is connected to a development client 23 in which a worker engaged in development performs development work.
- the development repository 22 stores development process information, activity information, and worker personal information in addition to a development target program, usable program parts, and the like.
- Development process information defines the development process as a flow that combines multiple activities.
- Activity information defines the work of each activity that constitutes the development process.
- the activities include design document registration, design document review, design document approval, and return.
- Each activity has the role of the worker who executes the activity as an attribute.
- Worker personal information is a list of workers involved in the project. Each worker is assigned a role as the work process progresses.
- the worker personal information may record a role held by each worker at a certain time or process.
- the worker personal information may be a list of worker teams involved in the project. In this case, the evaluation system 30 treats the work team as one unit.
- the support unit 21 inputs an operation instruction of each worker from the development client 23, refers to the information in the development repository 22, and executes processing such as creation and correction of the development target program.
- the support unit 21 generates information stored in the log storage unit 12 and the worker information storage unit 13 of the evaluation device 10 in the course of execution of the process.
- the generated information is input to the evaluation apparatus 10 via a data exchange storage medium such as a communication line or a CD-ROM (Compact Disk-Read Only Memory).
- FIG. 4 is a diagram showing a configuration of the work table 40 stored in the worker information storage unit 13.
- the worker information storage unit 13 stores a work table 40 corresponding to each of a plurality of workers engaged in the development or operation work of the development target program.
- the work table 40 includes a worker name 41 and personal data 42.
- the worker name 41 is an identifier that identifies the worker, such as the worker's name and employee number.
- the personal data 42 is information on the worker's individual such as the worker's career and skills.
- the work table 40 further includes one or more pairs of attributes 43 and periods 44. This pair is information indicating when and what attribute 43 the operator of the work table 40 has.
- the period 44 includes, for example, a start period and an end period.
- the attribute 44 is, for example, a development process in which an operator participates.
- the attribute 44 may be a role played by the worker.
- the attribute 44 may be a combination of a development process in which an operator participates and a role played by the worker in that process.
- FIG. 4 shows an example of data when the attribute is a combination of a process and a role.
- the support unit 21 of the development / operation support server 20 creates this pair every time the attribute of the worker changes. For example, when logging into the development operation support server 20 from the development client 23, the worker inputs the process and role he / she is responsible for into the support unit 21. The support unit 21 detects the input process and role change and generates a pair of the attribute 43 and the period 44.
- the first line of FIG. 4 shows that an operator whose worker name 41 is a (hereinafter abbreviated as worker a) is an SD roll (see FIG. 2) in the RA process (see FIG. 1). Shows that he participated in the project from January 2 to January 30, 2011.
- the second line in FIG. 4 indicates that the worker a participated in the project from February 1, 2011 to April 15, 2011 in the role of SD in the SA process.
- FIG. 5 shows the configuration of the access log 50 stored in the log storage unit 12.
- the support unit 21 of the development operation support server 20 generates an access log 50 each time access to a file is detected.
- the access log 50 includes an accessor name 51, a file name 52, and an access date / time 53.
- the accessor name 51 is the worker name 41 of the worker who accessed the file.
- the file name 52 is an identifier of the accessed file.
- the access date and time 53 is the date and time when access to the file occurred.
- FIG. 6 shows a configuration of the cooperation log 60 stored in the log storage unit 12.
- the support unit 21 of the development operation support server 20 generates a collaboration log 60 each time a request between workers and a response to the request are detected.
- the support unit 21 monitors the mail between the workers and detects a request between the workers and a response to the request from the title or the like.
- the support unit 21 may detect a response between a request and a request between workers by detecting a command input for a work request / response.
- the collaboration log 60 includes a sender name 61, a recipient name 62, a category 63, and a collaboration date and time 64.
- the sender name 61 is the worker name 41 of the worker who sent the request or response for the collaborative work.
- the recipient name 62 is the worker name 41 of the worker who has received the request or response for the collaborative work.
- the category 63 indicates the type of opportunity that the collaborative log 60 has occurred.
- the category 63 is information for distinguishing, for example, work requests, work responses, approval requests, and approval responses.
- the section 63 may include other additional data.
- the collaboration date and time 64 is the date and time when a request or response for collaboration work is transmitted or received between workers.
- the log storage unit 12 may store only the access log 50, store only the cooperation log 60, or store both. When both are stored, the log storage unit 12 stores the access log 50 and the cooperation log 60 as separate files, or adds the distinction information between the two and stores them in the same file. .
- the log storage unit 12 may store other logs.
- FIG. 7 is a schematic operation flowchart of the evaluation unit 11 of the evaluation apparatus 10.
- the evaluation unit 11 refers to the work table 40, the access log 50, and the cooperation log 60, and calculates and outputs the relationship strength that is an index of the strength of interaction between workers for each attribute.
- the evaluation unit 11 reads out all the work tables 40 from the worker information storage unit 13 and extracts all the pairs of worker names 41 and all the attributes (S11). Next, the evaluation unit 11 creates a variable for accumulating relation strength with an initial value 0 for every combination of pairs and attributes of the worker name 41 (S12).
- the evaluation unit 11 refers to the access log 50 to accumulate the relationship strength for each variable (S13), and further refers to the cooperation log 60 to accumulate the relationship strength for each variable (S14).
- the evaluation unit 11 may execute only one of S13 and S14. Further, the evaluation unit 11 may accumulate the relationship strength in each variable with reference to other logs in the log storage unit 12.
- the evaluation unit 11 outputs the relation strength of each variable for each attribute (S15).
- the evaluation unit 11 may create and output a matrix or graph indicating the relationship strength.
- FIG. 8 is an operation flowchart of processing in which the evaluation unit 11 accumulates the relationship strength with reference to the access log 50. This operation flowchart shows details of the processing of S13 of FIG.
- the evaluation unit 11 executes the processing from S21 to S24 for all the access logs 50. First, the evaluation unit 11 selects one log in chronological order based on the access date 53 (S21). The log selected here is referred to as log A.
- the evaluation unit 11 performs the processing of S22 to S24 for all the subsequent logs on the time series of the log A. Based on the access date and time 53, the evaluation unit 11 selects one log that satisfies the following three conditions from the subsequent logs in the time series of the log A (S22). The log selected here is referred to as log B.
- the first condition is that log B includes an accessor name 51 different from log A. That is, the first condition is that the values of the access name 51 of the log A and the access name 51 of the log B are different.
- the second condition is that the attributes 43 of the log A and log B workers are the same.
- the evaluation unit 11 obtains the worker attribute 43 in the access log 50 by searching the work table 40 in which the accessor name 51 and the worker name 41 coincide with each other for a period 44 including the access date and time 53.
- the third condition is that the file names 52 of log A and log B are the same.
- the evaluation unit 11 accesses the pair of the accessor name 51 of the log A and the log B and the variable of the relationship strength specified by the attribute 43. A value corresponding to the difference between the date and time 53 is added (S24).
- the evaluation unit 11 adds a value indicating a higher relationship strength as the difference between the access date 53 of the log A and the access date 53 of the log B is smaller. For example, the evaluation unit 11 adds 1.5, for example, if the difference between the access dates 53 of both access logs 50 is smaller than a predetermined value T, and adds 1 if it is larger than the predetermined value T, for example.
- a value indicating a high relationship strength does not necessarily have to be a large value.
- the evaluation unit 11 may show higher relationship strength as the value is smaller. In this case, for example, the evaluation unit 11 adds 1 if the difference between the access dates and times 53 of both the access logs 50 is smaller than the predetermined value T, and 1.5 if the difference is equal to or larger than the predetermined value T.
- the evaluation unit 11 may set the relationship strength between accesses that have occurred at a predetermined time or longer to zero.
- the evaluation unit 11 may simply count the number of times each worker has accessed the same file, and obtain the relationship strength between the workers based on the number of times.
- the evaluation unit 11 When the log B cannot be acquired (N in S23), the evaluation unit 11 returns to S21 without adding it to the relation strength variable.
- FIG. 9 is an operation flowchart of processing in which the evaluation unit 11 accumulates the relationship strength with reference to the cooperation log 60. This operation flowchart shows details of the processing of S14 of FIG.
- the evaluation unit 11 executes the processes of S31 to S33 for all the cooperation logs 60.
- the evaluation unit 11 acquires one cooperation log 60 (S31), and determines whether the attribute 43 of the sender and the receiver for the cooperation log 60 is the same (S32).
- the evaluation unit 11 obtains the attribute 43 of the sender by searching the work table 40 in which the sender name 61 and the worker name 41 coincide with each other for a period 44 including the cooperation date and time 64.
- the evaluation unit 11 similarly obtains the recipient attribute 43 from the recipient name 62.
- the evaluation unit 11 When the attributes 43 of the sender and the receiver are the same (Y in S32), the evaluation unit 11 is specified by the pair of the sender name 61 and the receiver name 62 and the same attribute 43 of the sender and the receiver. 1 is added to the variable of the relationship strength (S33). When the attribute 43 of the sender and the receiver is not the same (N in S32), the evaluation unit 11 returns to S31 without adding anything to the relationship strength variable.
- FIG. 10 is an operation flowchart of processing in which the evaluation unit 11 creates a relationship strength matrix and a graph. This operation flowchart shows details in the case of creating a matrix and a graph in the processing of S13 of FIG.
- FIG. 11 shows a matrix created by the evaluation unit 11.
- FIG. 12 shows a graph created by the evaluation unit 11.
- the evaluation unit 11 executes the processing of S41 to S47 for all types of the attribute 43.
- the evaluation unit 11 displays the relationship strength between the worker corresponding to the row and the worker corresponding to the column at the intersection as a matrix having the rows and columns corresponding to the workers (S41). That is, the evaluation unit 11 displays the relation strength of each variable corresponding to the attribute in the form of a matrix shown in FIG. In FIG. 11A, the evaluation unit 11 normalizes the relationship strength so that the maximum value is 1, and does not display the value when the relationship strength is 0.
- the worker a has a relationship strength of 0.4 with the worker b1, but with the other workers. There is no relationship.
- the fact that there is no relationship between the two workers means that S12 and S13 in FIG. 4 have been completed with the initial value of the variable for accumulating the relationship strength corresponding to the pair of the workers remaining at 0. means.
- the worker b1 has a relationship strength of 0.4 with the worker a and a relationship with the workers b2 and b3.
- a relationship of strength 1.0 is provided between the workers b4 and b5, and a relationship strength 0.6 is provided, but there is no relationship with other workers.
- the evaluation unit 11 extracts a cluster of workers, that is, a group (S42).
- the evaluation unit 11 forms a cluster of workers while exchanging the rows and columns of the matrix.
- the evaluation unit 11 is arranged close to the diagonal line of the matrix, and extracts groups so that the sum of the relationship strengths of the workers configuring the cluster becomes large.
- the evaluation unit 11 uses a genetic algorithm or the like, for example, while switching the rows and columns of the matrix in FIG. 11 (a) so that the total sum of the related work levels of the workers constituting the group is maximized. Extract groups along the diagonal.
- the evaluation unit 11 can use a technique used in DSM (Design Structure Matrix) or the like.
- FIG. 11B shows the matrix after the rows and columns of the matrix of FIG.
- evaluation unit 11 may improve visibility by color-coding clusters according to the sum of the relational strengths within the clusters on the matrix in FIG.
- the evaluation unit 11 arranges the centers of the group areas for each extracted group on the screen buffer with a certain distance from each other (S43).
- the evaluation unit 11 draws a node for each worker on the screen buffer by making the distance between the nodes proportional to the reciprocal of the relationship strength between the workers (S44). At this time, the evaluation unit 11 arranges the nodes in the group within a certain distance from the center of the area of the group.
- the evaluation unit 11 ties up the nodes of the workers whose relationship strength is not 0 (S45), draws the smallest ellipse including the nodes in the group in the screen buffer (S46), and outputs the screen buffer to the display device 14 (S47).
- FIG. 12 shows a graph displayed on the display device 14.
- the evaluation unit 11 may perform only one of matrix display and graph display. When only the graph display is performed, the evaluation unit 11 may perform the group extraction without depending on the matrix. For example, the evaluation unit 11 extracts a group so that the relationship work between the workers constituting the group becomes a predetermined value or more. Furthermore, the evaluation unit 11 may not perform group extraction / display.
- the evaluation apparatus 10 makes it possible to analyze a log and perform development organization evaluation for each attribute 43 of development and operation work such as work process and role. This development organization evaluation is also possible for agile development and iteration development. The reason is that the evaluation unit 11 calculates and displays the relationship strength between workers based on the number of interactions between workers and the weight of each interaction for each attribute based on the work table 40. is there.
- the evaluation apparatus 10 outputs the relationship strength between workers for each role of the workers in the development process.
- the manager of the development project can grasp the workers who have leadership or know-how across the roles.
- the evaluation device 10 outputs the relationship strength between workers for each work process in the development process.
- development project managers and the like can grasp key persons (proxy, mediator) across each work process.
- the evaluation device 10 displays the relationship strength in a matrix (FIG. 11) or graph (FIG. 12), and visualizes the relationship between the workers' clusters. This cluster shows the worker's instructions. This makes it easier for development project managers and the like to grasp the existence of groups based on the relationship strength and the relationship between them, and to determine the appropriateness of the group structure for development or operation.
- managers and others can identify the group structure for which know-how is easy to accumulate and grasp the independence of the group. Furthermore, managers and others can divide groups that can be developed in parallel. As a result, the administrator can review the organizational design and the work processes that can be developed in parallel.
- the evaluation apparatus 10 accumulates the relationship strength for each work process from the cooperation log 60. At that time, the evaluation device 10 adds a larger value when the roles of the sender and the receiver are the same than when the roles are different.
- the attribute 44 in the work table 40 is a combination of the development process in which the worker participates and the role played by the worker in the process.
- the evaluation unit 11 creates a variable for cumulative relationship strength with an initial value 0 for every combination of the pair of worker names 41 and processes. That is, the relationship strength accumulation variable exists not for every combination of the worker name 41 pair and attribute but for every combination of the worker name 41 pair and process.
- FIG. 13 is an operation flowchart of processing in which the evaluation unit 11 accumulates the relationship strength with reference to the cooperation log 60 in the second embodiment.
- FIG. 13 replaces FIG. 9 in the first embodiment.
- the evaluation unit 11 executes the processing from S51 to S55 for all the cooperation logs 60.
- the evaluation unit 11 acquires one cooperation log 60 (S51), and determines whether or not the processes in the sender 43 and receiver attributes 43 are the same for the cooperation log 60 (S52).
- the evaluation unit 11 obtains the sender's process by searching the work table 40 in which the sender name 61 and the worker name 41 coincide with each other for a period 44 including the cooperation date and time 64.
- the evaluation unit 11 similarly obtains the recipient attribute 43 from the recipient name 62.
- the evaluation unit 11 determines whether or not the roles in the attribute 43 of the sender and the receiver for the cooperation log 60 are the same ( S53).
- the evaluation unit 11 adds 1 to the variable of the relationship strength specified in the same process as the pair of the sender and the receiver (S54). ).
- the evaluation unit 11 sets a value less than 1 to the variable of the relationship strength specified in the same process as the pair of the sender and the receiver. Is added (S54).
- the addition value 1 or 0.8 is set as a parameter in the evaluation device 10 and may be appropriately changed by the operator of the evaluation device 10. Further, the added value when the roles of the sender and the receiver are not the same may be changed according to the combination of the roles of the sender and the receiver.
- the evaluation unit 11 returns to S51 without adding anything to the relationship strength variable.
- the evaluation unit 11 may reverse the roles of the process and the roll.
- the evaluation apparatus 10 reflects the difference between the roles (or processes) of both workers who have interacted in the relation strength when calculating the relation strength for each process (or roll). Moreover, the operator of the evaluation apparatus 10 can change the degree of reflection. The reason is that the evaluation unit 11 determines the difference between the roles (or processes) of the two workers who have performed the interaction, and changes the value added to the variable of the relationship strength.
- FIG. 14 is a configuration diagram of the evaluation apparatus 10 according to the third embodiment.
- the evaluation device 10 includes an evaluation unit 11, a log storage unit 12, and an operator information storage unit 13.
- the worker information storage unit 13 indicates, for each of a plurality of workers engaged in system development or operation work, a period 44 during which the worker has any of a plurality of work attributes 43 related to the work.
- the work table 40 is stored.
- the log storage unit 12 stores, for each interaction between a plurality of workers, a work log that records the occurrence time of the interaction and the participating workers.
- the work log is, for example, the access log 50 or the cooperation log 60.
- the evaluation unit 11 For each combination of a plurality of work attributes and a plurality of worker pairs from the work log, the evaluation unit 11 performs the number of interactions performed in the pair when the workers constituting the pair have the work attributes. Based on the above, the relationship strength indicating the strength of the relationship between the workers constituting the pair is calculated and output.
- the evaluation apparatus 10 makes it possible to analyze a log and perform development organization evaluation for each attribute 43 of development and operation work such as work process and role. This development organization evaluation is also possible for agile development and iteration development. The reason is that the evaluation unit 11 calculates and displays the relationship strength between workers based on the number of interactions between workers and the weight of each interaction for each attribute based on the work table 40. is there.
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Strategic Management (AREA)
- Theoretical Computer Science (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Marketing (AREA)
- Game Theory and Decision Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
Description
前記複数の作業者間の各インタラクションについて、当該インタラクションの発生時期および参加した前記作業者を記録した作業ログを記憶するログ記憶手段と、
前記作業ログから、前記複数の作業属性及び前記複数の作業者のペアのおのおのの組み合わせごとに、当該ペアを構成する作業者が当該作業属性を有する時に行った当該ペア内の前記インタラクションの回数を基に、当該ペアを構成する作業者間の関係の強さを示す関係強度を算出して出力する評価手段と、を備える。
前記複数の作業者間の各インタラクションについて、当該インタラクションの発生時期および参加した前記作業者を記録した作業ログを記憶するログ記憶処理と、
前記作業ログから、前記複数の作業属性及び前記複数の作業者のペアのおのおのの組み合わせごとに、当該ペアを構成する作業者が当該作業属性を有する時に行った当該ペア内の前記インタラクションの回数を基に、当該ペアを構成する作業者間の関係の強さを示す関係強度を算出して出力する評価処理と、をコンピュータに実行させる。
前記複数の作業者間の各インタラクションについて、当該インタラクションの発生時期および参加した前記作業者を記録した作業ログを記憶し、
前記作業ログから、前記複数の作業属性及び前記複数の作業者のペアのおのおのの組み合わせごとに、当該ペアを構成する作業者が当該作業属性を有する時に行った当該ペア内の前記インタラクションの回数を基に、当該ペアを構成する作業者間の関係の強さを示す関係強度を算出して出力する。
本発明を実施するための形態について図面を参照して詳細に説明する。
本発明の第2の実施形態にかかる評価装置10は、協働ログ60から作業工程ごとに関係強度を累積する。そのさい、評価装置10は、送信者と受信者のロールが同一である場合、異なる場合よりも大きな値を加算する。
図14は、第3の実施の形態に係る評価装置10の構成図である。
11 評価部
12 ログ記憶部
13 作業者情報記憶部
14 表示装置
20 開発運用支援サーバ
21 支援部
22 開発リポジトリ
23 開発クライアント
40 作業表
41 作業者名
42 個人データ
43 属性
44 期間
50 アクセスログ
51 アクセス者名
52 ファイル名
53 アクセス日時
60 協働ログ
61 送信者名
62 受信者名
63 区分
64 協働日時
Claims (24)
- システムの開発または運用の作業に従事する複数の作業者のおのおのについて、当該作業者が前記作業に関する複数の作業属性の何れかを有していた期間を示す作業表を、記憶する作業者情報記憶手段と、
前記複数の作業者間の各インタラクションについて、当該インタラクションの発生時期および参加した前記作業者を記録した作業ログを記憶するログ記憶手段と、
前記作業ログから、前記複数の作業属性及び前記複数の作業者のペアのおのおのの組み合わせごとに、当該ペアを構成する作業者が当該作業属性を有する時に行った当該ペア内の前記インタラクションの回数を基に、当該ペアを構成する作業者間の関係の強さを示す関係強度を算出して出力する評価手段と、を備える評価装置。 - 前記評価手段は、ペアを構成する作業者間の関係強度を、前記複数の作業者のおのおの対応に行および列を有するマトリクスとして出力する、請求項1の評価装置。
- 前記評価手段は、前記複数の作業者から、前記マトリクスの対角線に寄せて配置され、グループ内の作業者間の前記関係強度の総和が大きくなるようなグループを抽出し、
前記複数の作業者のおのおのをノードとし、2つの前記ノード間を前記関係強度に応じた表示のノードで結び、前記グループ内の前記ノードを互いに近傍に配置したグラフを作成して出力する、請求項2評価装置。 - 前記作業者情報記憶手段は、少なくとも一人の前記作業者について、時系列上、第1の前記作業属性を持つ前記期間の前後に、第2の前記作業属性をもつ前記期間が存在する前記作業表を記憶する請求項1乃至3の何れかの評価装置。
- 前記複数の作業属性は、前記複数の作業者のおのおのが関わった、システムの開発または運用に係る複数の工程、
前記複数の作業者のおのおのが担った、システムの開発または運用に係る複数のロール、または、
前記複数の作業者のおのおのが関わったシステムの開発または運用に係る複数の工程、および、前記複数の工程のおのおのにおいて、前記複数の作業者のおのおのが担ったシステムの開発または運用に係る複数のロールの組み合わせ、
の何れかである、請求項1乃至4の何れかの評価装置。 - 前記複数の作業属性は、前記複数の作業者のおのおのが関わったシステムの開発または運用に係る複数の工程、および、前記複数の工程のおのおのにおいて、前記複数の作業者のおのおのが担ったシステムの開発または運用に係る複数のロールの組み合わせであり、前記工程及びロールの、一方を第1の属性、他方を第2の属性としたときに、
前記評価手段は、前記複数の第1の属性のおのおの及び前記複数の作業者のペアのおのおのごとに、当該ペアを構成する作業者が属性として当該第1の属性を有する時に行った当該ペア内の前記インタラクションの回数から得られる関係強度を、前記ペアを構成する異なる作業者の前記第2の属性が同一である場合、異なる場合よりも高く算出する、請求項1乃至4の何れかの評価装置。 - 前記作業ログは、前記作業者によるファイルへのアクセスログを含み、
前記評価手段は、前記作業ログから、前記ペアを構成する異なる作業者による2つの連続した同一ファイルへのアクセスを検出する度に、前記ペア間に、両アクセスの時間的近さに応じて大きくなる重みを求め、前記重みを累積して前記関係強度を求める、請求項1乃至6の何れかの評価装置。 - 前記作業ログは、作業者間の依頼、または、応答の共働ログを含み、
前記評価手段は、前記共働ログから、前記ペアを構成する異なる作業者間の前記共働ログの個数をカウントして前記関係強度を求める、請求項1乃至7の何れかの評価装置。 - システムの開発または運用の作業に従事する複数の作業者のおのおのについて、当該作業者が前記作業に関する複数の作業属性の何れかを有していた期間を示す作業表を、記憶する作業者情報記憶処理と、
前記複数の作業者間の各インタラクションについて、当該インタラクションの発生時期および参加した前記作業者を記録した作業ログを記憶するログ記憶処理と、
前記作業ログから、前記複数の作業属性及び前記複数の作業者のペアのおのおのの組み合わせごとに、当該ペアを構成する作業者が当該作業属性を有する時に行った当該ペア内の前記インタラクションの回数を基に、当該ペアを構成する作業者間の関係の強さを示す関係強度を算出して出力する評価処理と、をコンピュータに実行させる評価プログラム。 - 前記コンピュータに、ペアを構成する作業者間の関係強度を、前記複数の作業者のおのおの対応に行および列を有するマトリクスとして出力する前記評価処理を実行させる、請求項9の評価プログラム。
- 前記コンピュータに、前記複数の作業者から、前記マトリクスの対角線に寄せて配置され、グループ内の作業者間の前記関係強度の総和が大きくなるようなグループを抽出し、前記複数の作業者のおのおのをノードとし、2つの前記ノード間を前記関係強度に応じた表示のノードで結び、前記グループ内の前記ノードを互いに近傍に配置したグラフを作成して出力する前記評価処理を実行させる、請求項10評価プログラム。
- 前記コンピュータに、少なくとも一人の前記作業者について、時系列上、第1の前記作業属性を持つ前記期間の前後に、第2の前記作業属性をもつ前記期間が存在する前記作業表を記憶する前記作業者情報記憶処理を実行させる請求項9乃至11の何れかの評価プログラム。
- 前記複数の作業属性は、前記複数の作業者のおのおのが関わった、システムの開発または運用に係る複数の工程、
前記複数の作業者のおのおのが担った、システムの開発または運用に係る複数のロール、または、
前記複数の作業者のおのおのが関わったシステムの開発または運用に係る複数の工程、および、前記複数の工程のおのおのにおいて、前記複数の作業者のおのおのが担ったシステムの開発または運用に係る複数のロールの組み合わせ、
の何れかである、請求項9乃至12の何れかの評価プログラム。 - 前記複数の作業属性は、前記複数の作業者のおのおのが関わったシステムの開発または運用に係る複数の工程、および、前記複数の工程のおのおのにおいて、前記複数の作業者のおのおのが担ったシステムの開発または運用に係る複数のロールの組み合わせであり、前記工程及びロールの、一方を第1の属性、他方を第2の属性としたときに、
前記コンピュータに、前記複数の第1の属性のおのおの及び前記複数の作業者のペアのおのおのごとに、当該ペアを構成する作業者が属性として当該第1の属性を有する時に行った当該ペア内の前記インタラクションの回数から得られる関係強度を、前記ペアを構成する異なる作業者の前記第2の属性が同一である場合、異なる場合よりも高く算出する前記評価処理を実行させる、請求項9乃至12の何れかの評価プログラム。 - 前記作業ログは、前記作業者によるファイルへのアクセスログを含み、
前記コンピュータに、前記作業ログから、前記ペアを構成する異なる作業者による2つの連続した同一ファイルへのアクセスを検出する度に、前記ペア間に、両アクセスの時間的近さに応じて大きくなる重みを求め、前記重みを累積して前記関係強度を求める前記評価処理を実行させる、請求項9乃至14の何れかの評価プログラム。 - 前記作業ログは、作業者間の依頼、または、応答の共働ログを含み、
前記コンピュータに、前記共働ログから、前記ペアを構成する異なる作業者間の前記共働ログの個数をカウントして前記関係強度を求める前記評価処理を実行させる、請求項9乃至15の何れかの評価プログラム。 - システムの開発または運用の作業に従事する複数の作業者のおのおのについて、当該作業者が前記作業に関する複数の作業属性の何れかを有していた期間を示す作業表を記憶し、
前記複数の作業者間の各インタラクションについて、当該インタラクションの発生時期および参加した前記作業者を記録した作業ログを記憶し、
前記作業ログから、前記複数の作業属性及び前記複数の作業者のペアのおのおのの組み合わせごとに、当該ペアを構成する作業者が当該作業属性を有する時に行った当該ペア内の前記インタラクションの回数を基に、当該ペアを構成する作業者間の関係の強さを示す関係強度を算出して出力する、評価方法。 - ペアを構成する作業者間の関係強度を、前記複数の作業者のおのおの対応に行および列を有するマトリクスとして出力する、請求項17の評価方法。
- 前記複数の作業者から、前記マトリクスの対角線に寄せて配置され、グループ内の作業者間の前記関係強度の総和が大きくなるようなグループを抽出し、前記複数の作業者のおのおのをノードとし、2つの前記ノード間を前記関係強度に応じた表示のノードで結び、前記グループ内の前記ノードを互いに近傍に配置したグラフを作成して出力する、請求項18評価方法。
- 少なくとも一人の前記作業者について、時系列上、第1の前記作業属性を持つ前記期間の前後に、第2の前記作業属性をもつ前記期間が存在する前記作業表を記憶する請求項17乃至19の何れかの評価方法。
- 前記複数の作業属性は、前記複数の作業者のおのおのが関わった、システムの開発または運用に係る複数の工程、
前記複数の作業者のおのおのが担った、システムの開発または運用に係る複数のロール、または、
前記複数の作業者のおのおのが関わったシステムの開発または運用に係る複数の工程、および、前記複数の工程のおのおのにおいて、前記複数の作業者のおのおのが担ったシステムの開発または運用に係る複数のロールの組み合わせ、
の何れかである、請求項17乃至20の何れかの評価方法。 - 前記複数の作業属性は、前記複数の作業者のおのおのが関わったシステムの開発または運用に係る複数の工程、および、前記複数の工程のおのおのにおいて、前記複数の作業者のおのおのが担ったシステムの開発または運用に係る複数のロールの組み合わせであり、前記工程及びロールの、一方を第1の属性、他方を第2の属性としたときに、
前記複数の第1の属性のおのおの及び前記複数の作業者のペアのおのおのごとに、当該ペアを構成する作業者が属性として当該第1の属性を有する時に行った当該ペア内の前記インタラクションの回数から得られる関係強度を、前記ペアを構成する異なる作業者の前記第2の属性が同一である場合、異なる場合よりも高く算出する、請求項17乃至20の何れかの評価方法。 - 前記作業ログは、前記作業者によるファイルへのアクセスログを含み、
前記作業ログから、前記ペアを構成する異なる作業者による2つの連続した同一ファイルへのアクセスを検出する度に、前記ペア間に、両アクセスの時間的近さに応じて大きくなる重みを求め、前記重みを累積して前記関係強度を求める、請求項17乃至22の何れかの評価方法。 - 前記作業ログは、作業者間の依頼、または、応答の共働ログを含み、
前記共働ログから、前記ペアを構成する異なる作業者間の前記共働ログの個数をカウントして前記関係強度を求める、請求項17乃至23の何れかの評価方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2013537995A JP5464305B2 (ja) | 2012-01-18 | 2012-12-12 | 評価装置、評価方法、および、評価プログラム |
US14/001,109 US8924918B2 (en) | 2012-01-18 | 2012-12-12 | Evaluation apparatus, an evaluation method and an evaluation program storing medium |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2012007855 | 2012-01-18 | ||
JP2012-007855 | 2012-01-18 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013108334A1 true WO2013108334A1 (ja) | 2013-07-25 |
Family
ID=48798792
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2012/007926 WO2013108334A1 (ja) | 2012-01-18 | 2012-12-12 | 評価装置、評価方法、および、評価プログラム |
Country Status (3)
Country | Link |
---|---|
US (1) | US8924918B2 (ja) |
JP (1) | JP5464305B2 (ja) |
WO (1) | WO2013108334A1 (ja) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2015038693A (ja) * | 2013-08-19 | 2015-02-26 | 株式会社大和総研ビジネス・イノベーション | フロー図作成システム |
JP2017173991A (ja) * | 2016-03-22 | 2017-09-28 | 日本電気株式会社 | 支援装置、支援方法及びプログラム |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH11296461A (ja) * | 1998-04-14 | 1999-10-29 | Nippon Telegr & Teleph Corp <Ntt> | ユーザ間情報交換システム及び方法、ユーザ端末、サーバ計算機、並びに、ユーザ間情報交換プログラムを記録した記録媒体 |
JP2004054606A (ja) * | 2002-07-19 | 2004-02-19 | Hitachi Ltd | リスク予測支援方法および情報処理装置 |
JP2006092368A (ja) * | 2004-09-24 | 2006-04-06 | Fuji Xerox Co Ltd | 活動記録装置、活動記録方法およびプログラム |
JP2008257539A (ja) * | 2007-04-06 | 2008-10-23 | Fuji Xerox Co Ltd | コミュニケーション分析装置および方法 |
JP2011086231A (ja) * | 2009-10-19 | 2011-04-28 | Ricoh Co Ltd | チーム抽出装置、該チーム抽出装置を用いたチーム抽出方法及びチーム抽出プログラム、該チーム抽出プログラムを記憶した記憶媒体 |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001022613A (ja) | 1999-07-07 | 2001-01-26 | Hitachi Ltd | ログファイル内ログ情報の検索方法 |
JP3730156B2 (ja) | 2001-11-09 | 2005-12-21 | 有限会社築城ソフト研究所 | 関係付け情報管理システム、関係付け情報管理用プログラム、及び記録媒体 |
JP4344922B2 (ja) | 2003-01-27 | 2009-10-14 | 富士ゼロックス株式会社 | 評価装置およびその方法 |
US20130179359A1 (en) * | 2012-01-09 | 2013-07-11 | Psc Industrial Outsourcing, Lp | System and method for job safety analysis |
US20130238785A1 (en) * | 2012-03-06 | 2013-09-12 | Rackspace Us, Inc. | System and Method for Metadata Discovery and Metadata-Aware Scheduling |
US9460264B2 (en) * | 2012-05-04 | 2016-10-04 | Elwha Llc | Devices, systems, and methods for automated data collection |
-
2012
- 2012-12-12 US US14/001,109 patent/US8924918B2/en active Active
- 2012-12-12 WO PCT/JP2012/007926 patent/WO2013108334A1/ja active Application Filing
- 2012-12-12 JP JP2013537995A patent/JP5464305B2/ja active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH11296461A (ja) * | 1998-04-14 | 1999-10-29 | Nippon Telegr & Teleph Corp <Ntt> | ユーザ間情報交換システム及び方法、ユーザ端末、サーバ計算機、並びに、ユーザ間情報交換プログラムを記録した記録媒体 |
JP2004054606A (ja) * | 2002-07-19 | 2004-02-19 | Hitachi Ltd | リスク予測支援方法および情報処理装置 |
JP2006092368A (ja) * | 2004-09-24 | 2006-04-06 | Fuji Xerox Co Ltd | 活動記録装置、活動記録方法およびプログラム |
JP2008257539A (ja) * | 2007-04-06 | 2008-10-23 | Fuji Xerox Co Ltd | コミュニケーション分析装置および方法 |
JP2011086231A (ja) * | 2009-10-19 | 2011-04-28 | Ricoh Co Ltd | チーム抽出装置、該チーム抽出装置を用いたチーム抽出方法及びチーム抽出プログラム、該チーム抽出プログラムを記憶した記憶媒体 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2015038693A (ja) * | 2013-08-19 | 2015-02-26 | 株式会社大和総研ビジネス・イノベーション | フロー図作成システム |
JP2017173991A (ja) * | 2016-03-22 | 2017-09-28 | 日本電気株式会社 | 支援装置、支援方法及びプログラム |
Also Published As
Publication number | Publication date |
---|---|
US20140325471A1 (en) | 2014-10-30 |
JPWO2013108334A1 (ja) | 2015-05-11 |
JP5464305B2 (ja) | 2014-04-09 |
US8924918B2 (en) | 2014-12-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4717945B2 (ja) | 業務分析プログラムおよび業務分析装置 | |
Dakic et al. | BUSINESS PROCESS MINING APPLICATION: A LITERATURE REVIEW. | |
Song et al. | Towards comprehensive support for organizational mining | |
Hornix | Performance analysis of business processes through process mining | |
Ozorhon et al. | Critical success factors of enterprise resource planning implementation in construction: Case of Turkey | |
US20120232947A1 (en) | Automation of business management processes and assets | |
Fabijan et al. | The lack of sharing of customer data in large software organizations: challenges and implications | |
US20110218843A1 (en) | Non intrusive system and method for monitoring business processes | |
Vera-Baquero et al. | Business process improvement by means of Big Data based Decision Support Systems: a case study on Call Centers | |
Fernandes et al. | Workload control in unbalanced job shops | |
US10417712B2 (en) | Enterprise application high availability scoring and prioritization system | |
US20170236086A1 (en) | Systems and/or methods for context-driven contribution ranking | |
Lin et al. | An approach to twinning and mining collaborative network of construction projects | |
Abbsaian-Hosseini et al. | Social network analysis for construction crews | |
JP2017059111A (ja) | 組織改善活動支援システム、情報処理装置、方法およびプログラム | |
Tripathi et al. | Exploring processes in small software companies: a systematic review | |
CN114124743B (zh) | 一种数据应用全链路检查规则执行方法及系统 | |
JP5464305B2 (ja) | 評価装置、評価方法、および、評価プログラム | |
KR20070033728A (ko) | 지적자산 정보의 핵심특허지수 제공 시스템과 그 방법 | |
Özdağoğlu et al. | Monitoring the software bug‐fixing process through the process mining approach | |
JP5765529B2 (ja) | 業務システム変更支援システム、業務システム変更支援プログラム、および業務システム変更支援方法 | |
JP7384768B2 (ja) | コミュニティ評価システム、コミュニティ評価方法、行動評価システム及び行動評価方法 | |
Kumar et al. | Analyzing performance of a global help desk team operation–country handoffs, efficiencies and costs | |
Phasom et al. | Process mining for improvement of IT service in automobile industry | |
CN111506826A (zh) | 基于亲密度的用户推荐方法、装置、设备及存储介质 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
ENP | Entry into the national phase |
Ref document number: 2013537995 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14001109 Country of ref document: US |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12865770 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 12865770 Country of ref document: EP Kind code of ref document: A1 |