JP2004164068A - Software use condition management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a software use condition management system capable of easily and accurately grasping use condition and a purpose of use of a software downloaded in the network environment possible to specify a user. <P>SOLUTION: A management server 100 structuring a software management system is provided with an activity information obtaining unit 101, an execution information obtaining unit 102, a use condition display unit 103 and a memory unit 104 as a use condition management means. The activity information obtaining unit 101 obtains the activity information of a user transmitted from each of client terminals 110 through a network 120, and stores it in the memory unit 104. The execution information obtaining unit 102 stores the execution information of software 113 transmitted from each of the client terminals 110 in the memory unit 104. The use condition display unit 103 displays use condition of each of the softwares 113, while corresponding the activity information of each of the users to the execution information of each of the softwares 113, which are stored in the memory unit 104. <P>COPYRIGHT: (C)2004,JPO

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a system for managing the use status of software that can be downloaded via a network.
[0002]
[Prior art]
In recent years, with the speeding-up of networks, the spread of networks such as the Internet has progressed, and a service for downloading various software collected in a server via a network is known. Similarly, in a company, there is also used a system in which a server is provided on an intranet, software as development support software is library-stored on the server, and distributed to client terminals used by developers.
A system that manages software libraries such as development support software and software installed in each client terminal is known (for example, see Patent Document 1).
[0003]
[Patent Document 1]
JP-A-10-269065 (pages 4 to 5, FIGS. 11 and 14)
[0004]
[Problems to be solved by the invention]
However, when managing the software to be installed on the client terminal as a library, the purpose of using the software (for example, development work using software) and the usage status are used as guidelines for determining the software to be registered in the library. However, in the system of Patent Document 1, there is no means for managing the purpose of use and the state of use of the software installed in the client terminal.
In this case, regarding the purpose of using the software, it is conceivable that the information such as what kind of development project is used can be grasped by a questionnaire at the time of downloading, but after the software is installed on the client terminal, it is described in the questionnaire It was not possible to know how much was used for the intended purpose. Further, when the purpose of use is changed according to the development situation of the user, etc., it is not possible to accurately grasp each purpose of use.
[0005]
The present invention has been made to solve the above-described problem, and can easily and accurately grasp a use situation according to each use purpose for software downloaded in a network environment in which a user can be specified. The purpose is to provide a software usage status management system.
[0006]
[Means for Solving the Problems]
In order to solve the above-mentioned problems, the present invention is a software usage status management system including a management server that manages the usage status of software to be managed by a client terminal connected via a network. The management server may further include, as behavior information related to the use of the software input by the user of the client terminal, identification information of each user, behavior details of the user, start time and end time of each behavior. Action information acquiring means for acquiring action information including a time and storing the action information in a storage means; and identification information of each user and execution start time and end time of the software as execution information of the software in the client terminal. Execution information acquisition means for acquiring execution information including the following, and storing the execution information in the storage means; A usage state in which the action information and the execution information are associated with each other and the usage status of each software is displayed based on each user's identification information, each start time and an end time included in the performed action information and execution information; Display means.
Further, the use status display means receives designation of a period by an administrator of the management server, acquires the execution information and action information having a start time and an end time corresponding to the designated period, and acquires the acquired execution information. And means for displaying the use status of each software in association with the behavior information.
[0007]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, a software management system according to an embodiment of the present invention will be described with reference to the drawings.
The software management system includes a management server 100 for managing the use status of software to be managed, and is connected to a plurality of client terminals 110 via a network 120.
The management server 100 includes an activity information acquisition unit 101, an execution information acquisition unit 102, a use status display unit 103, and a storage unit 104 as use status management means. Further, the management server 100 includes a known library management unit for managing software distributed to the client terminal 110.
Each client terminal 110 includes an action information input unit 111 such as schedule management software, a software execution monitoring unit 112, and software 113 distributed by the management server 100.
The behavior information acquisition unit 101 acquires past behavior information input by the user using the behavior information input unit 111 of each client terminal 110 via the network 120, and stores the acquired past behavior information in the storage unit 104. The behavior information includes information for identifying the user of the client terminal 110, information of the behavior, and start / end times of each behavior as information on the behavior of the user of each client terminal 110. Here, the action content indicates work or the like using each client terminal 110. For example, in the case of a user who develops software, a project name and a process related to the work using the client terminal 110 are used. The name is included.
The execution information obtaining unit 102 obtains, via the network 120, the start information and the end information of the software 113 as the management target transmitted by the software execution monitoring unit 112 of each client terminal 110, and executes the start information and the end information. Is stored in the storage unit 104. The execution information includes information for identifying the user of the client terminal 110, information for identifying the executed software 113, and information of the software 113. Execution start (start) and end times are included.
The usage status display unit 103 acquires the behavior information of each user and the execution information of each software 113 stored in the storage unit 104, and based on the identification information of the user and the start / end time included in each information. The usage information of each software 113 is displayed in association with the behavior information and the execution information.
The storage unit 104 has a software table 105, a user table 106, a project table 107, an action information table 108, and execution information 109.
[0008]
FIG. 2 is a diagram showing a data structure of the software table 105 in the storage unit 104.
The software table 105 stores information about each piece of software to be managed in advance, and includes a software ID (soft_id) 201 for uniquely identifying each piece of software, a software name (name) 202, , Detailed information (detail) 203 indicating details of the software, a field (field) 204 to which the software belongs, and a file name (file) 205 when distributing the software.
[0009]
FIG. 3 is a diagram showing a data structure of the user table 106 in the storage unit 104.
The user table 106 stores information about the user of each client terminal 110 in advance, and includes a user ID (name_id) 301 for uniquely identifying each user, a name (name) 302, and an affiliation name ( (division) 303 and position information 304.
[0010]
FIG. 4 is a diagram showing a data structure of the project table 107 in the storage unit 104.
The project table 107 stores information of each project related to the purpose of using the software in advance, and includes a project ID (project_id) 401 for uniquely identifying each project, a project name (project_name) 402, The information includes a project scale (scale) 403, a development style (project_style) 404 of each project, and a customer name (customer) 405 indicating a customer of each project.
[0011]
FIG. 5 is a diagram showing a data structure of the action information table 108 in the storage unit 104.
The behavior information table 108 stores the behavior information transmitted by the behavior information input unit 111 of the client terminal 110. FIG. 5 shows an example in which the operation contents related to software development are stored as an example of the behavior information. ing. The action information table 108 includes an action information ID (event_id) 501 for uniquely identifying each piece of action information, a task name (event_name) 502 for each task, and a user ID (name_id) 503 indicating a user who performed the task. , A project ID (project_id) 504 indicating a project that the user has engaged in each work, a process name (process) 505 indicating a process in the project, and a start time (beg_date) 506 indicating the start and end of each work. Each item of information includes an end time (end_date) 507.
The behavior information acquisition unit 101 assigns the behavior information ID 501 to each piece of behavior information transmitted from the behavior information input unit 111.
The user ID 503 corresponds to the user ID 301 in the user table 106. The project ID 504 corresponds to the project ID 401 of the project table 107.
[0012]
FIG. 6 is a diagram illustrating a data structure of the execution information table 109 in the storage unit 104.
The execution information table 109 stores the execution information transmitted by the software execution monitoring unit 102 of the client terminal 110. The execution information table 109 includes an execution information ID (exe_id) 601 for uniquely identifying each execution information, and an execution information ID. ID (soft_id) 602 for identifying the software 113, the user ID 603 (name_id) for identifying the user of each software 113, and the start time indicating the time when the software 113 was in the execution state ( beg_date) 604 and end time (end_date) 605.
The execution information acquisition unit 102 gives the execution information ID 601 to each execution information transmitted from the software execution monitoring unit 102.
The software ID 602 corresponds to the software ID 201 of the software table 105. The user ID 603 corresponds to the user ID 301 in the user table 106.
[0013]
A method of storing the behavior information and the execution information in each of the tables 108 and 109 in the storage unit 104 in the above configuration will be described.
[0014]
FIG. 7 is a diagram illustrating a screen configuration example of the behavior information input screen displayed on the client terminal 110 by the behavior information input unit 111.
The behavior information input screen 700 shows the date 701 on the horizontal axis and the time 702 on the vertical axis, and the activity 703 or the non-operation activity 704 is input as the user's activity content at each time on each date. In this case, for the work 703, the project name and the process name are input, and for the non-work activity 704, "lunch", "holiday", and the like are input.
Information set in advance for each client terminal 110 is shown as user information 705 for identifying each user.
The behavior information input unit 111 transmits the behavior information of each user to the behavior information acquisition unit 101 of the management server 100 based on the content input on the behavior information input screen 700. For example, as the contents of the work 703, for the user “Taro Hitachi”, “9: 00 AM to 12:00 AM on July 29, 2002”, the respective information of the process name “functional design” of the project name “A-project” is added. Send.
The behavior information acquisition unit 101 of the management server 100 assigns a behavior information ID 501 to each piece of behavior information transmitted by the behavior information input unit 111, and stores the behavior information in the behavior information table 108 in the storage unit 104.
[0015]
FIG. 8 is a flowchart illustrating a processing procedure in which the software execution monitoring unit 112 of each client terminal 110 transmits the execution information of each software 113 to the execution information acquisition unit 102 of the management server 100.
In response to the activation of the client terminal 110, the software execution monitoring unit 112 starts (step 801), and starts monitoring the software 113 (step 802).
When the software 113 is activated (step 802), the software execution monitoring unit 112 transmits the activation information including the software name, the user identification information, and the activation time to the execution information of the management server 100 via the network 120. The data is transmitted to the acquisition unit 102 (step 803). The execution information acquisition unit 102 assigns an execution information ID 601 to each piece of boot information, stores it in the execution information table 109 of the storage unit 104, and transmits the execution information ID 601 to the client terminal 110 that has transmitted the boot information.
If the software 113 has terminated abnormally (step 804) or terminated by user operation (step 805), the end information including the execution information ID 601 transmitted from the execution information acquisition unit 102 and the end time Is transmitted to the execution information acquisition unit 102 of the management server 100 via the network 120 (step 806). The execution information acquisition unit 102 stores the end time in the execution information table 109 based on the execution information ID 601 included in the end information.
The above monitoring process is performed until a shutdown operation is performed on the client terminal (step 807), and the software execution monitoring unit 112 ends with the shutdown operation (step 808).
[0016]
Next, regarding the behavior information and the execution information stored in each of the tables 108 and 109 in the storage unit 104 by the behavior information acquisition unit 101 and the execution information acquisition unit 102, the usage status display unit 103 responds to the operation by the administrator. A method for displaying the usage status of the wear 113 will be described.
[0017]
FIG. 9 is a diagram illustrating an example of a usage status display screen displayed by the usage status display unit 103.
As shown in FIG. 9A, the usage status display screen 900 includes a management period display column 910, a software usage status display column 920, and a project usage status display column 930.
The management period input column 910 shows the period input by the administrator of the management server 100.
In the usage status display column 920 for each software, as the usage status of each software 113, a software name 921, the number of users 922, a total number of startups 923, a total startup time 924, an average usage time 925, Each information of the utilization rate 926 for each section is displayed.
In the usage status display column 930 for each project, as the usage status of the software 113 for each project, the project name 931, the number of users 932, the number of software usage 933, the software usage rate 934, the total project time 935 And information of the period 936 required for the project.
For each project displayed in the project-specific use status display column 930, a staff-specific use status display screen 940 is displayed according to the operation of the administrator.
The in-person usage status display screen 940 displays the information on the name of the person in charge 941, the software usage rate 942, and the total design time 943 as the usage status of the software 113 of each person in charge. .
[0018]
FIG. 10 is a flowchart illustrating an outline of the usage status display process performed by the usage status display unit 103.
As shown in FIG. 10, the usage status display unit 103 receives an input of a designated period from the administrator (step 1001), and refers to the start time 506 and the end time 507 of the action information table 108 based on the inputted designated period. Then, a record of the corresponding behavior information is extracted from the behavior information table 108 (step 1002).
Similarly, the record of the corresponding execution information is extracted from the execution information table 109 by referring to the start time 604 and the end time 605 of the execution information table 109 based on the input designated period (step 1003).
Based on the extracted action information and execution information, an extraction process and a calculation process, which will be described later, are performed on the display items in the respective display columns shown in FIG. 9 (step 1004), and the respective display columns 920 and 930 or the display screen 940 are displayed (step 1004). 1005).
[0019]
FIG. 11 is a flowchart illustrating extraction / calculation processing relating to display items in the usage status display column 920 for each software.
The usage status display unit 103 acquires items such as a software name and a user name from each record extracted based on the designated period from each of the tables 105 to 109 in the storage unit 104 (step 1101), and stores each record. After grouping by software name (step 1102), the number of users calculation process (step 1103), the total number of startups calculation process (step 1104), the total operation time calculation process (step 1105), and the average usage time calculation process (step 1106) ), And each processing of the department-specific utilization rate calculation processing (step 1107).
In the number-of-users calculation process (step 1103), a record of execution information for each software 113 is acquired, and the number of users is calculated based on the number of records in the execution information table 109 excluding the duplication of the user ID 603.
In the total activation count calculation process (step 1104), a record of execution information for each piece of software 113 is acquired, and the total activation count is obtained based on the acquired number of records.
In the total operation time calculation processing (step 1105), records of execution information for each software 113 are acquired, and the operation times of the records obtained from the start time 604 and the end time 605 shown in the execution information table 109 are totaled. Find the total operating time.
In the average usage time calculation process (step 1106), the usage time per person per day is divided for each software by dividing the result of the total operation time calculation process by the result of the calculation of the number of users and the number of days indicated in the designated period. Ask for.
In the department use rate calculation process (step 1107), a record of execution information for each piece of software is acquired, and the rate of each department is obtained based on the affiliation name 303 shown in the user table 106.
Through the above-described processes, information of each display item in the software-based usage status display column 920 is generated and displayed.
[0020]
FIG. 12 is a flowchart showing the extraction / calculation processing relating to the display items in the project-specific usage status display column 930.
The use status display unit 103 acquires items such as a project name and a user name from each record extracted based on the specified period from the behavior information storage unit 102 and the execution information storage unit 103 (step 1201), and stores each record. After grouping by project name (step 1202), total project time calculation processing (step 1203), project period calculation processing (step 1204), software user count calculation processing (step 1205), software usage count calculation processing (step 1205) 1206), and each processing of the software utilization rate calculation processing (step 1207) is performed.
In the project total time calculation process (step 1203), a record of the activity information for each project is obtained, and the activity time of each record obtained from the start time 506 and the end time 507 shown in the activity information table 108 is totaled to obtain the total project time. Ask for time.
In the project period calculation process (step 1204), a record of the behavior information for each project is obtained, and the minimum value of the start time 506 (earliest date) and the maximum value of the end time 507 (date of the date) are obtained from each record. And the project period from the slowest one).
In the software user number calculation process (step 1205), a record of the behavior information for each project is obtained, and the number of users is obtained based on the number of records in the behavior information table 108 excluding the duplication of the user ID 503.
In the software usage number calculation process (step 1206), the execution information table 109 is shown for each record of the activity information for each project based on the user ID 503, the start time 506, and the end time 507 acquired from the activity information table 108. With reference to the user ID 603, the start time 604, and the end time 605, a record of the corresponding execution information is acquired. For each record of the acquired execution information, the software usage count is obtained based on the record count excluding the duplication of the software ID 602.
In the software usage rate calculation process (step 1207), similarly to the software usage number calculation process (step 1206), each record of the execution information corresponding to each record of the action information for each project is acquired, and the execution information table 109 is obtained. The total execution time of the software is obtained based on the execution time of each record obtained from the start time 604 and the end time 605 shown in FIG.
Through the above processes, information on each display item in the project-specific use status display column is generated and displayed.
[0021]
FIG. 13 is a flowchart showing extraction / calculation processing relating to display items on the in-person use status display screen 940.
The use status display unit 103 acquires items such as a project name and a user name from each record extracted based on the designated period from each of the tables 105 to 109 in the storage unit 104 (step 1301), and stores each record in the project. After grouping by name and user name (step 1302), each processing of total design time calculation processing (step 1303) and software utilization rate calculation processing (step 1304) is performed.
In the total design time calculation process (step 1303), a record of the behavior information for each user in charge of each project is obtained, and the behavior time of each record obtained from the start time 506 and the end time 507 shown in the behavior information table 108 Find the total design time based on
In the software usage rate calculation process (step 1304), each record of the behavior information for each user in charge of each project is executed based on the user ID 503, start time 506, and end time 507 acquired from the behavior information table 108. With reference to the user ID 603, the start time 604, and the end time 605 shown in the information table 109, a record of the corresponding execution information is acquired. For each record of the acquired execution information, the execution time of each record obtained from the start time 604 and the end time 605 shown in the execution information table 109 is summed to obtain the total execution time of the software, and the quotient of the total execution time with the total design time is obtained. Find the software usage rate.
Through the above processes, the information of each display item in the use status display column for each person in charge is generated and displayed.
[0022]
As described above, the software usage management system according to the present embodiment manages the behavior information of each user and the execution information of each software related to the purpose of using the software, and By displaying the usage status based on the information, the usage status of each software can be easily and accurately grasped from various viewpoints. In particular, the execution status and the behavior information are associated with each other based on the user identification information and each start time and end time, and the usage status is displayed. The situation can be easily and accurately grasped. For example, by displaying the usage status of each software, it is possible to grasp the detailed usage status, such as the number of users of each software and the number of users per day. At a glance. Therefore, when software is managed in a library, it can be used as judgment data of software to be registered in the library.
In addition, by displaying the software usage status in each project, in a software development project, it is possible to know the software usage rate during the project, etc., and to understand which projects use the software more. It becomes possible.
In addition, by displaying the usage status of each person in charge of each project, it is possible to grasp the status of software utilization among the people in charge of the project, and it is easy to know who is using the software more easily Thus, the know-how and the like can be used as an index when developing between the persons in charge.
In this case, based on the period specified by the administrator of the management server, the start time and the end time included in the behavior information and the execution information are referred to, and the behavior information and the execution information corresponding to the specified period are obtained and the software is acquired. Since the usage status of the software is displayed, it is possible to appropriately manage the usage status according to the time when the library management is started for each software.
[0023]
In the above-described embodiment, the example of FIG. 9 is shown as a display item displayed by the usage status display unit. However, the present invention is not limited to this, and a display item that can be acquired and calculated based on action information and execution information. Any item is acceptable. For example, the software name and usage rate of the software used may be acquired, calculated, and displayed for each project.
Further, the configuration of the management server and each client terminal is not limited to those shown in the example of FIG. 1, as long as execution information and action information can be managed and each display item can be displayed according to the operation of the administrator. Alternatively, another configuration may be used.
Further, the software to be managed in the present invention is not limited to software used for development project work, and all software that can be downloaded in a network environment where users can be specified should be managed. Can be. Therefore, the action information managed by the software usage status management system of the present invention is not limited to information related to the work of the development project, but includes various action contents related to the use of each software.
[0024]
【The invention's effect】
As described above, according to the present invention, a means for managing execution information of software installed on a client terminal and behavior information of a client terminal user, and a usage status of each software based on the execution information and behavior information Means for calculating and displaying information related to the software, the software usage status can be easily and accurately grasped from various viewpoints, such as the purpose of using each software, and appropriate management of each software can be performed. It is possible to do.
[Brief description of the drawings]
FIG. 1 is a diagram showing a schematic configuration of a software usage status management system according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating an example of a data structure of a software table.
FIG. 3 is a diagram illustrating an example of a data structure of a user table.
FIG. 4 is a diagram illustrating an example of a data structure of a project table.
FIG. 5 is a diagram illustrating an example of a data structure of an action information table.
FIG. 6 is a diagram illustrating an example of a data structure of an execution information table.
FIG. 7 is a diagram illustrating an example of an action information input screen displayed by an action information input unit.
FIG. 8 is a flowchart illustrating an execution monitoring process performed by a software execution monitoring unit.
FIG. 9 is a diagram illustrating an example of a usage status display screen displayed by a usage status display unit.
FIG. 10 is a flowchart illustrating a usage status display process performed by a usage status display unit.
FIG. 11 is a flowchart illustrating software-based usage status display processing performed by a usage status display unit.
FIG. 12 is a flowchart illustrating a project-specific use status display process performed by a use status display unit.
FIG. 13 is a flowchart illustrating a usage status display process for each person in charge performed by a usage status display unit.
[Explanation of symbols]
100 management server, 101 action information acquisition section, 102 execution information acquisition section, 103 usage status display section, 104 storage section, 105 software table, 106 user table, 107 project table, 108 action information table, 109 execution information table, 110 client terminal, 111 action information input unit, 112 software execution monitoring unit, 113 software, 120 network, 501 action information ID, 502 work name, 503 user ID, 504 project ID, 505 process name, 506 start time, 507 end time, 601 execution information ID, 602 user ID, 603 software ID, 604 start time, 605 end time.

Claims (2)

A software usage status management system including a management server that manages usage status of the software in a client terminal connected via a network for software to be managed,
The management server,
As the action information related to the use of the software input by the user of the client terminal, action information including identification information of each user, action content of the user, and start time and end time of each action. Behavior information acquisition means for acquiring and storing in the storage means;
Execution information acquisition means for acquiring execution information including identification information of each user and execution start time and end time of the software as the execution information of the software in the client terminal, and storing the execution information in a storage unit;
Based on the identification information of each user included in the behavior information and the execution information stored in the storage unit, and each start time and end time, the use information of each software is associated with the behavior information and the execution information. And a usage status display means for displaying the software usage status. The usage status display means receives a designation of a period by an administrator of the management server, acquires the execution information and the behavior information having a start time and an end time corresponding to the designated period, and acquires the acquired execution information and behavior. 2. The software usage status management system according to claim 1, further comprising means for displaying usage status of each software in association with the information.

Images