JP2013033380A - Software management system, management server and control method and program of software management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To allow project design information to be compared with an actual utilization scene in which the project design information is utilized.SOLUTION: Each user terminal 2 comprises: a video recording section 14 for video recording a utilization scene in which an accounting software is actually utilized; and a distributing agent 19 for transmitting video recording data in which a video recording result, operation video, of the utilization scene is added with a display ID of a software display A operated when the accounting software is utilized to a provider data center 3. The provider data center 3 comprises: a software management information storage section 33 for storing project proposal data in which a project proposal prepared in a project design stage of the accounting software is added with the display ID; and a DB recording section 37 that associates the video recording data transmitted from each user terminal 2 and project design data with each other by the display ID and records the video recording data and the project design data in a video recording management data base 31.

Description

  The present invention relates to a software management system, a management server, a control method for the software management system, and a program comprising one or more user terminals in which software is installed and a management server connected to each of the user terminals via a network. It is about.

  Conventionally, as a development process management system, a development process management document database for storing management documents for each stage of the development process in software and a development process management document processing unit for controlling reading and writing to the development process management document database have been provided. Things are known. In this development process management system, the development process management document processing section automatically reflects the contents of the peer review (e.g. review evaluation) deliberated on the electronic conference system in the management document of the development process management system, and the development process management document Store in the database.

JP 2007-219829 A

  However, with the conventional configuration, design documents are evaluated on the assumption that the software is used in the peer review on the electronic conference system. The software is not always used. For this reason, there is a difference between the assumed usage scene and the actual usage scene, and as a result, there is a problem that software with high usability cannot be developed. On the other hand, it is possible to reduce the above difference by recording the actual usage scene and comparing it with the design document. However, it is possible to determine which design document corresponds to the recorded usage scene. There was a problem that the design document and the utilization scene could not be compared with each other.

  An object of the present invention is to provide a software management system, a management server, a control method for a software management system, and a program capable of comparing planned design information with an actual use scene.

  A software management system according to the present invention is a software management system including one or more user terminals in which software is installed and a management server connected to each of the user terminals via a network. , A recording unit that records the usage scene that actually uses the software, and recording data that adds the screen ID of the software screen that is operated at the time of use to the recording result of the usage scene, and that is sent to the management server The management server is transmitted from each user terminal and a planning design data storage unit that stores planning design data in which a screen ID is added to the planning design information created in the planning and designing stage of the software. A database that links recording data and planning and design data with screen IDs And DB recording unit for recording, and further comprising a.

  A control method for a software management system according to the present invention is a control method for a software management system including one or more user terminals in which software is installed, and a management server connected to each user terminal via a network. In addition, each user terminal manages the recording step of recording the usage scene where the software is actually used, and the recording data obtained by adding the screen ID of the software screen operated at the time of use to the recording result of the usage scene A recording data transmission step to be transmitted to the server, and the management server appends a screen ID to the recording data transmitted from each user terminal and the planning / designing information created in the planning / designing stage of the software. The planned design data is linked with the screen ID and recorded in the database The DB recording step that, and executes.

  According to these configurations, by adding a screen ID to the recording result of the utilization scene and the planning / designing information, linking them with the screen ID and storing them in the database, by referring to the database, The actual use scene (recording result) can be compared with the plan design information. For example, by displaying and verifying the recorded result and the planning / designing information in a comparable manner, it can be used for development of software with high usability.

  In the software management system, the management server further includes a development management data storage unit that stores development management data in which a screen ID is added to the development management information created in the software development stage, and the DB recording unit It is preferable that the data, the planning / design data, and the development management data are linked by the screen ID and recorded in the database.

  According to this configuration, actual utilization scenes, planning / designing information, and development management information can be compared. The development management information is, for example, a development schedule, development man-hours, development costs, etc. required for developing a program related to a software screen.

  In the above software management system, the recording unit preferably records a change in the software screen accompanying a user operation as a moving image.

  According to this configuration, since the recording process can be performed by, for example, capture, the recording unit can be configured simply.

  In this case, each user terminal preferably further includes a masking processing unit that performs masking processing on confidential information included in the recording result with respect to the recording data before being transmitted by the recording data transmission unit.

  According to this configuration, it is possible to prevent leakage of confidential information (for example, a company name of a business partner or customer information) due to transmission of recorded data. Note that the masking process referred to here is a process for making confidential information unrecognizable, and is a concept including a mosaic process and a replacement process as well as a narrowly defined masking process that covers the confidential information. Further, the masking process of the confidential information may be configured so that only the portion displaying the confidential information is processed so as not to be seen, or the entire software screen is processed (for example, the resolution of the entire screen is reduced). It may be configured so that confidential information is not visible.

  In the above software management system, the recording unit preferably records the user's operation with a camera provided in the user terminal.

  According to this configuration, since the recording process can be performed by a camera (for example, a web camera) already provided in the user terminal, the user's operation can be recorded without newly providing a camera.

  On the other hand, it is preferable that the recording unit starts and stops recording by operation of an operator displayed on the software screen.

  According to this configuration, since the user who operates the user terminal can operate the start and stop of recording, it is possible to prevent recording and transmission without the user's will.

  Moreover, it is preferable that the management server further includes a display unit that displays the recording data and the plan design data associated with the screen ID in different areas on the same screen.

  According to this configuration, it is possible to perform efficient verification by displaying the recording result and the plan design information in a comparable manner on the same screen.

  In addition, each user terminal includes a creation data transmission unit that sends creation data obtained by adding the screen ID of the software screen operated at the time of creation to creation information created using software to the management server, and a DB It is preferable that the recording unit associates the recording data, the plan design data, and the creation data with the screen ID and records them in the database.

  According to this configuration, actual utilization scenes, planning / designing information, and creation information can be compared.

  The management server of the present invention is used in the above-described software management system.

  According to this configuration, it is possible to provide a management server capable of recording an actual use scene and plan design information in association with each other.

  A program according to the present invention causes a computer to function as each user terminal and management server in the above-described software management system.

  According to this configuration, the computer can be caused to function as each user terminal and management server of the above-described software management system simply by installing this program on the computer.

It is a system configuration figure of a software management system. It is a functional block diagram of a software management system. It is the figure which showed the specific example of the examination screen. It is the flowchart which showed the recording process of the video recording data to a provider data center.

  Hereinafter, a software management system, a management server, a software management system control method, and a program according to the present invention will be described with reference to the accompanying drawings. In the present embodiment, a software management system to which the present invention is applied will be described as an example. This software management system manages information on accounting software (software).

  As shown in FIG. 1, the software management system 1 includes one or more user terminals 2 on which accounting software is installed, and a provider data center (management server) 3 connected to each user terminal 2 via a network NW. And. The provider data center 3 is configured by connecting a main server 3a and a sub server 3b. Further, the user terminal 2, the main server 3a, and the sub server 3b are configured by a computer, and include an input unit 7 having a keyboard 5, a mouse 6 and the like, and a display unit 9 having a display 8 and the like. Although not shown, the communication device includes a communication unit that performs data communication and a control unit that controls each unit.

  The accounting software installed in each user terminal 2 is a program that sequentially displays one or more software screens (operation screens) A and creates a form B based on input information on the software screen A. That is, by installing the accounting software, the user terminal 2 is caused to function as a form creation device.

  Next, each function of the user terminal 2 and the provider data center 3 will be described with reference to the functional block diagram of FIG. As shown in FIG. 2, each user terminal 2 includes a screen display unit 11, an operation unit 12, a form creation unit 13, a recording unit 14, an information collection unit 15, a recording data recording unit 16, and form data. A recording unit 17, a masking processing unit 18, and a distribution agent (recorded data transmission unit and created data transmission unit) 19 are provided. Each user terminal 2 includes a recording database 21 that stores recording data that will be described later, a form database 22 that stores form data that will be described later, and a software database 23 that stores information used for the form creation processing of accounting software. I have.

  The screen display unit 11 displays each software screen A with the display means 9 as a main part. Each software screen A is assigned a screen ID. The operation unit 12 includes a keyboard 5 and a mouse 6 as main parts, and performs various operations and inputs on the software screen A. The form creation unit 13 creates a form B based on input information on the software screen A with the control means as a main part. A form ID is assigned to each form B to be created. As described above, the screen display unit 11, the operation unit 12, and the form creation unit 13 execute a form creation process for creating a form B in accordance with a user operation.

  The recording unit 14 records a utilization scene in which the accounting software is actually utilized with the control means as a main part. Strictly speaking, as the utilization scene, the recording unit 14 records a change in the software screen A accompanying a user operation as a moving image. That is, the operating software screen A is captured as a moving image. Hereinafter, the recorded moving image is referred to as an operation moving image. The recording unit 14 records the operation moving image in accordance with the operation of the recording menu (operator) A1 displayed on each software screen A. That is, recording is started and stopped by the recording menu A1. Further, the recording unit 14 records the operation moving image in units of the software screen A.

  The information collecting unit 15 collects information related to the recorded operation moving images. Specifically, for each operation video, the information collection unit 15 performs the operation date / time (system date / time) when the operation video was operated, the user ID of the user who performed the operation video, Performed due to the screen ID of the software screen A that recorded each operation video, the form ID of the form B created by the software screen A of each operation video, and the operation of the software screen A of each operation video Each process ID of the process (batch process or the like) and the operation content (such as pressing the enter key) performed on the software screen A of each operation moving image are acquired. In addition, the information collection unit 15 retrieves the software ID and version number from the software database 23. And the customer ID and the product terminal, slip information and customer information related to the software screen A of each operation video, and the user terminal 2 at the time of recording each operation video from the OS (Operating System) The DB size, free capacity, operation service, etc. of the server are acquired.

  The recording data recording unit 16 adds various information collected by the information collecting unit 15 to each operation moving image (recording result of the use scene) recorded by the recording unit 14 to obtain recording data, and records this in the recording database 21. . The form data recording unit 17 adds the screen ID of the software screen A operated at the time of creation to each form B (creation information) created by the accounting software (form creation unit 13) to form form data (creation data). This is recorded in the form database 22.

  The masking processing unit 18 processes each recording data stored in the recording database 21 and performs a masking process on confidential information (for example, a company name of a business partner or customer information) included in the operation moving image for each recording data. . Specifically, the masking process is performed on the display portion of the confidential information, or the masking process is performed on the entire software screen A. The masking process mentioned here is a masking process in a broad sense, and includes a masking process that covers a part with black paint, a mosaic process that applies a mosaic, and a replacement process that replaces confidential information with sample data. May be. Further, the masking process may be applied to the form data stored in the form database 22.

  The distribution agent 19 sends each recorded data after masking processing stored on the recording database 21 and each form data stored on the form database 22 to the providing source data center 3 (strictly, the main server 3a). Send. Further, prior to the transmission of these data, the distribution agent 19 pops up a transmission confirmation screen for confirming whether or not to perform the transmission.

  When recording data is transmitted, a discount coupon that can be used at the time of product purchase may be issued by the provider data center 3 as an incentive on the user side. For example, the provider data center 3 transmits an email describing a coupon code to the user terminal 2. The providing source data center 3 associates the coupon code with the customer ID (or user ID) and registers it in the customer management database in the providing source data center 3, and when the user purchases an application, Enter the coupon code and get a discount.

  As described above, the provider data center 3 includes the main server 3a and the sub server 3b. The sub-server 3b includes a software management information storage unit (planned design data storage unit) 33, a development management information storage unit (development management data storage unit) 34, a change history storage unit 35, and a property storage unit 36. ing.

  The software management information storage unit 33 stores software management information for each accounting software. Specifically, plan management information, development management information, quality evaluation document, operation design document and support information of each accounting software are stored as software management information. The plan management information includes plan document data (plan design data), requirement definition document data, and design document data for each screen ID (that is, for each software screen A). The plan document data, requirement definition data, and design document data have screen IDs corresponding to the plan document (plan design information), requirement definition document, and design document for each software screen A created at the planning and design stage of accounting software. It is the added data. The development management information includes development tool and component information and source code data for each screen ID. The source code data is data obtained by adding a corresponding screen ID to the development source code for each software screen A created at the development stage. The support information includes a manual, a customer maintenance chart, inquiry information, and failure information.

  The development management information storage unit 34 stores development project management information for each accounting software. Specifically, schedule data, man-hour data, and expense data (development management data) for each screen ID of each accounting software (that is, for each software screen A) are stored as development project management information. The schedule data, man-hour data, and expense data are data in which a corresponding screen ID is added to the development schedule, development man-hours, and development expenses (development management information) for each software screen A created in the software development stage.

  The change history storage unit 35 stores a change history of each item of software management information and development project management information. The property storage unit 36 stores properties of each item of software management information and development project management information.

  The main server 3 a includes a recording management database (database) 31, a DB recording unit 37, and an examination screen display unit 38. The recording management database 31 stores recording data from each user terminal 2. Although details will be described later, each piece of data associated with the recorded data is stored.

  The DB recording unit 37 records the recording data transmitted from each user terminal 2 in the recording management database 31. Further, when recording the recording data, the DB recording unit 37 records the recording data and other data in the recording management database 31 in association with the screen ID. Specifically, the plan document data, the requirement definition document data, the design document data, the development source code data, the development schedule data, the development man-hour data, and the development expense data to which the screen ID common to the recording data is added are stored in the sub server 3b. Are collected from the software management information storage unit 33 and the development management information storage unit 34, and form data to which a screen ID common to the recording data is added is selected, and the recording data and these data are linked and recorded. .

  The examination screen display unit 38 displays the examination screen C for performing various examinations of designated accounting software with the display means 9 as a main part. The examination screen C is for examining the accounting software in units of the software screen A, and extracts the recorded data and other data (any one) associated with the screen ID from the recording management database 31; These are displayed in different areas on the same screen. That is, the screen is substantially equally divided into two, and the recorded data is displayed in one divided area, and other data associated with the recorded data is displayed in the other divided area (see FIG. 3). In this way, various examinations of the software screen A can be performed by displaying the operation moving image of the recording data and the other data associated therewith in a comparable manner.

  On the examination screen C, the data to be displayed so as to be comparable with the recorded data is changed according to the matter to be examined. Specifically, as shown in FIG. 3, when examining whether the plan document is as intended, it is possible to compare the recorded data with the plan document data linked to this on the study screen C. indicate. When examining whether the response or the like is appropriate, the recorded data and the design document data and source code data associated with the recorded data are displayed on the examination screen C so as to be comparable. Furthermore, when studying development efficiency, the recorded data and schedule data, man-hour data, and expense data associated with the recorded data are displayed on the study screen C so that they can be compared. Furthermore, when examining how the form B is created, the recorded data and the form data associated with the recorded data are displayed on the examination screen C so that they can be compared. In addition, the configuration may be such that the requirement definition data is displayed in a comparable manner according to the matter to be examined. Further, the screen may be divided into three or more parts and a plurality of data may be displayed on the same screen so as to be compared with the recorded data.

  Next, with reference to FIG. 4, the recording process of the recording data to the provider data center 3 will be described. As shown in FIG. 4, first, the user terminal 2 records an operation moving image by the recording unit 14 due to the operation of the recording menu A1 (S1). When the operation video is recorded, the information collecting unit 15 collects information related to the recorded operation video (S2). Then, the recorded data recording unit 16 adds various kinds of collected information to the recorded operation video to obtain recorded data, which is recorded in the recorded database 21 (S3).

  After recording the recorded data, the masking processing unit 18 performs masking processing on the recorded data (S4). Thereafter, the distribution agent 19 displays a recording data transmission confirmation screen (S5). When it is selected that transmission is not performed on the transmission confirmation screen (S6: No), transmission of the recording data is canceled and this operation is terminated.

  On the other hand, when transmission is selected on the transmission confirmation screen (S6: Yes), the distribution agent 19 transmits the recording data to the provider data center 3 (S7: recording data transmission step). On the other hand, the provider data center 3 (main server 3a) receives the recording data (S8), and the DB recording unit 37 associates the received recording data with the other data by the screen ID to record the data. It records in the management database 31 (S9: DB recording step). Thus, this operation is finished. Each recording data recorded here and the other data linked | related with this are accumulate | stored in the recording management database 31, and are used for the display of the examination screen C by the examination screen display part 38. FIG.

  According to the configuration as described above, by adding screen IDs to the recording results of the utilization scene and the plan, respectively, by linking them with the screen IDs and storing them in the recording management database 31, the recording management database By referring to 31, it is possible to compare the actual use scene (recording result) with the plan document. Also, by displaying and verifying the recorded result and the plan document for comparison, it can be used for the development of software with high usability.

  In addition, recording data and development management data (schedule data, man-hour data and cost data) are recorded in association with screen IDs, so that actual usage scenes, planning documents and development management information (development schedule, development man-hours) are recorded. And development costs).

  Furthermore, since the recording unit 14 records the change of the software screen A accompanying the user's operation as a moving image and displays the recording result on the examination screen C, the recording process can be performed by, for example, capture. The part 14 can be configured simply.

  Further, by performing masking processing by the masking processing unit 18, it is possible to prevent leakage of confidential information due to transmission of recorded data.

  In addition, by starting and stopping recording by operating the recording menu A1 displayed on the software screen A, the user operating the user terminal 2 can operate starting and stopping recording. It is possible to prevent the recording and transmission without going through the process.

  Further, the examination screen display unit 38 displays the recorded result (operation video) and the plan document in a comparable manner on the same screen, thereby enabling efficient verification.

  Furthermore, the recorded data is linked to the form data by the screen ID and recorded in the recording management database 31, so that the actual utilization scene, the plan document, and the form B can be compared.

  In the present embodiment, the recording unit 14 is configured to record a change in the software screen A accompanying a user operation as a moving image and display the recording result on the examination screen C. A configuration in which a user's operation is recorded by a camera (for example, a Web camera used for video chatting) provided in the user terminal 2 and the recording result is displayed on the examination screen C may be adopted. In this case, since the recording process can be performed by the camera already provided in the user terminal 2, it is not necessary to provide a new camera, and the user's operation can be recorded.

  In this embodiment, the operation by the user after the release is recorded and displayed on the examination screen C. However, a video of the operation by the developer at the time of development (so-called in-house video) is recorded. The configuration may be such that this is displayed on the examination screen C. That is, the user terminal 2 may be a terminal in which a development product (accounting software) is installed, and is not necessarily operated by a user who has purchased the development product.

  Further, the manual, inquiry information, failure information, and the like for each software screen A may be data to which a screen ID is added, and may be configured to be compared and displayed together with recorded data on the examination screen C in units of software screen A.

  In the present embodiment, the recording unit 14 starts and ends recording by operating the recording menu A1, but the user terminal 2 has a predetermined timing (for example, when accounting software is started for the first time). Thus, a recording confirmation screen for confirming whether or not recording can be started is displayed in a pop-up, and recording by the recording unit 14 is started only when the user permits recording on the recording confirmation screen.

  In the present embodiment, when recording data is received, the recording data and the other data are recorded in the recording management database 31. However, the received recording data is stored on the sub server 3b. In addition, when the examination screen C is displayed, the recording data and the other data may be collected from the sub server 3b and recorded in the recording management database 31.

  Furthermore, in the present embodiment, the recording data and the other data are recorded in the recording management database 31, but instead of recording the other data itself in the recording management database 31, the other data The recording data and the other data may be linked by recording information indicating the storage location of the data in the recording management database 31.

  In this embodiment, instead of the operation video, an operation log such as a click or an input operation when the accounting software is actually used is recorded for each software screen A, and the operation log is recorded as the other data. It may be configured to be displayed so as to be comparable.

  1: Software management system 2: User terminal 3: Source data center 14: Recording unit 18: Masking processing unit 19: Distribution agent 31: Recording management database 33: Software management information storage unit 34 Development management information storage unit, 37: DB recording unit, 38: Examination screen display unit, A: Software screen, A1: Recording menu, NW: Network

Claims (11)

A software management system comprising one or more user terminals installed with software, and a management server connected to each user terminal via a network,
Each user terminal is
A recording unit for recording a utilization scene in which the software is actually utilized;
A recording data transmission unit that transmits recording data obtained by adding a screen ID of a software screen operated at the time of utilization to the recording result of the utilization scene;
The management server is
A plan design data storage unit for storing plan design data with the screen ID added to the plan design information created in the plan design stage of the software;
A software management system comprising: a DB recording unit that associates the recording data transmitted from each user terminal with the plan design data by the screen ID and records the data in a database. The management server is
A development management data storage unit for storing development management data with the screen ID added to the development management information created in the software development stage;
2. The software management system according to claim 1, wherein the DB recording unit associates the recording data, the plan design data, and the development management data with the screen ID and records them in the database.   The software management system according to claim 1, wherein the recording unit records a change in the software screen accompanying a user operation as a moving image. Each user terminal is
The software management according to claim 3, further comprising a masking processing unit that masks confidential information included in the recording result with respect to the recording data before being transmitted by the recording data transmission unit. system.   The software management system according to claim 1, wherein the recording unit records a user's operation by a camera provided in the user terminal.   6. The software management system according to claim 1, wherein the recording unit starts and stops recording by operation of an operator displayed on the software screen. The management server is
7. The display device according to claim 1, further comprising a display unit configured to display the recording data and the plan design data associated with the screen ID in different areas on the same screen. Software management system. Each user terminal is
A creation data sending unit for sending creation data in which the screen ID of the software screen operated at the time of creation is added to the creation information created using the software, to the management server;
The said DB recording part links | relates the said recording data, the said plan design data, and the said creation data with the said screen ID, and records them in the said database. The described software management system.   A management server used in the software management system according to claim 1. A control method of a software management system comprising one or more user terminals installed with software and a management server connected to each of the user terminals via a network,
Each user terminal is
A recording step of recording a utilization scene in which the software is actually utilized;
A recording data transmission step of transmitting to the management server recording data obtained by adding a screen ID of a software screen operated at the time of utilization to the recording result of the utilization scene;
The management server is
The recording data transmitted from each user terminal and the planning design data stored by adding the screen ID to the planning design information created in the planning and designing stage of the software are linked by the screen ID, A control method for a software management system, wherein a DB recording step for recording in a database is executed.   A program for causing a computer to function as each user terminal and the management server in the software management system according to any one of claims 1 to 8.

Images