JP2005339228A - Software management system, management device, operating device, software management method, software operating method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To secure traceability by disclosing development details in a development apparatus side of an execution environment, and detecting alteration even in regard to software outside unitary management. <P>SOLUTION: In an operation part 1, software and an operation history management file including a hash value are inputted, the hash value is extracted from the operation history management file, a hash value is calculated from the software, the hash values are compared, the software is deleted as being altered when there is a mismatch, change operation of the software is carried out as having no alteration when there is a match, operation history core information indicating an operation time, an operation part ID, or the like is generated, and the software, the operation history management file, and the operation history core file are sent to a management part 2 after operation. In the management part 2, the hash value and version information of the software after operation are generated, the operation history management file is updated by adding the hash value, the version information, and the operation history core information to the operation history management file, and the software after operation, and the operation history management file after update are recorded. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a software history management technique.

  The conventional software distribution service method is a software distribution service method in which a plurality of machines are connected to a network, and an agent that distributes software between these machines and a client that receives software distribution are specified to distribute software. The agent (a) a version management file for registering difference information between the latest version software and the new version and the previous version, (b) distribution for creating a new version based on the difference information of the version management file. It has a distribution file creation device that generates information and distributes distribution information to the client, and the client has a new version generation device that generates a new version using the distributed distribution information. If there is, the distribution manager immediately prepares an appropriate version and redistributes it. Rukoto can. Furthermore, since the distribution file creation device generates distribution information for creating a new version based on the difference information in the version management file, when extracting a version, the latest version and the difference between the version to be extracted are used. Only. Therefore, the difference of the old version that does not need to be taken out can be deleted from the version management file, and the size of the version management file can be kept constant even if the revision is advanced. Along with this, it has become possible to perform management such that only the latest n versions are registered in the version management file, and resources such as disks have been used economically and efficiently.

  The distribution management machine has a falsification check device that requests a falsification check of software from a client and collects the results. The client checks the software for falsification based on the falsification check request and creates a falsification check file creation device that creates a file containing the checked information, and a falsification that sends the falsification check file to the distribution management machine. By having the check control device, it is possible to easily check the tampering of the user and to keep the environment uniform. Also, if the user accidentally erases the software, the administrator can know it by tampering check without the user notifying the distribution administrator, and immediately take appropriate measures such as redistribution. (For example, Patent Document 1).

  In addition, a conventional version management system is a version management system that manages a plurality of versions of specification data from which a program constituting an information system is derived. A plurality of versions of specification data that is a decryption of a plurality of different types of data. The specification data is compressed when storing the specification data from the workspace to the repository, and conversely, the compressed specification data is decompressed when the specification data is extracted from the repository to the workspace. A compression / decompression unit that performs configuration, a configuration difference management unit that manages a difference between versions according to the type of data held in the specification data when the specification data is stored in the repository, or vice versa, and single Text difference management means for managing differences in text data with a unique data structure This allows specification data consisting of a combination of multiple different types of data to be retained by the difference from the root version of the version or the base version representing an arbitrary version without having to copy the entire specification data for each version. There is an effect that can be done. In addition, since differences are managed for each data type, there is also proposed a method for version management that can accurately capture changed parts and improve space efficiency without comparing different types of data and creating differences. (For example, Patent Document 2).

  In addition, a conventional software module release management system and release management method includes an update history storage unit that stores an update history of a software module, an input unit that inputs data for specifying a software module to be released, and the input unit. An update history data acquisition method for acquiring update history data corresponding to the input identification data from the update history storage means, and at least a date and a software module name are added to the update history data acquired by the update history data acquisition There has also been proposed a method of directly obtaining an update history of a software module to be released via, for example, a terminal by providing execution result data output means for outputting the execution result data (for example, Patent Document 3). .

  A conventional software change history management system is a software change history management system that manages source code change differences and version numbers, and is a physical version that corresponds one-to-one to change differences as source code history information. By providing management means that manages two versions, the physical version number that is the number and the logical version number that is the logical version number corresponding to the change contents, this management means has an error in the contents of the change difference When canceling the wrong change difference in order to re-register the correct change difference, the history of the canceled change difference is managed, and the version number is not changed when re-registering the correct change difference after canceling the incorrect change difference. A method has also been proposed (for example, Patent Document 4).

In addition, in the conventional document and program management method, a first database that defines files constituting a document or a program, and a second database that manages change information for each file that constitutes a document or program when the document or program is changed. The change history is managed in document units or program units using a database. In addition, using a first database that defines the files that make up a document or program, and a second database that manages change information for each file that makes up a document or program, the document unit or program unit To manage change information including change contents and reason for change, and to make changes related to documents or programs using a third database that defines the relationships between files defined by the first database. Documents that are managed by document or program changes, using a third database that defines the relationship between the files defined by the first database, and that manages changes in the document or program. By managing the extent to which the program has been changed, it is possible to grasp the change history and change information in document units or program units, and changes in the document or program change the related document or program. A document and program management method has also been proposed (for example, Patent Document 5).
JP 7-44392 A Japanese Patent Laid-Open No. 7-44432 JP 2000-148453 A JP 2000-242474 A JP 2000-298581 A

  Conventional software distribution services, version management systems, software module release management systems and release management methods, software change history management systems, document and program management methods, etc. all manage software centrally by a management server or the like. As a result, not only the main revision of software, but also the derived revision branched from the main revision was managed by the same management server. For this reason, when a device that develops software (hereinafter referred to as “developed device”) acquires the software directly from the management server and performs an operation such as a change, the software after the operation is stored in the management server (Patent Literature 1, Patent Literature 2, Patent Literature 3, Patent Literature 4, Patent Literature 5).

  In the conventional software distribution method, as a software tampering check method, the management machine requests a client tampering check from the client, and the client responds to the request with the name, size, date, version, etc. of the software. Information is notified to the management machine, and the management machine checks for falsification (Patent Document 1).

  For example, in the cross-development environment, software that has been downloaded in advance to a device that is executed from another development device (hereinafter referred to as an actual device) without acquiring the software from the management server is uploaded to the execution device by executing the execution environment. Often changes are made to be optimal.

  In such a software development environment, the network to which the development device in the execution environment is connected and the network to which the management server is connected are separated by a firewall or the like. In some cases, the history of changes made cannot be stored in the management server.

  In addition, since changes are made to software that runs in other execution environments because it is specialized for the execution environment, the change history is not left on the management server to increase management data. There is.

  In the conventional method of centrally managing software by the management server, if changes are made outside the management of the management server for the reasons described above, even if the software is operating without problems in the execution environment, Has become unknown, and there is a problem that its reliability cannot be guaranteed.

  In addition, there is a problem that software that has been duplicated through a real machine and is separated from the centralized management by the management server cannot be detected by the conventional falsification check method.

  The main object of the present invention is to solve the above-mentioned problems, and software that is out of central management by a management server or the like by always attaching change history information and falsification detection information to the software, The main purpose is to clarify the development process on the development equipment side of the execution environment and to ensure traceability by detecting tampering.

The software management system according to the present invention includes:
A software management system for managing software change operations,
Performs a software change operation and outputs the software after the change operation, an operation history management file indicating the history of the software change operation performed up to the change operation, and operation attribute information indicating the attribute of the change operation An operation unit to
The software after the change operation, the operation history management file and the operation attribute information are input from the operation unit, the falsification detection information for falsification detection is generated from the software after the change operation, and the input operation history management file and Based on the operation attribute information, the update information for updating the operation history management file is generated by reflecting the change operation in the operation unit, the falsification detection information is added to the generated update information, and the falsification detection information is A management unit that updates the operation history management file by adding the added update information to the operation history management file and records the updated operation history management file and the software after the change operation in association with each other. To do.

  According to the present invention, the operation history management file and the falsification detection information are always attached to the software, so that the development environment of the execution environment is clarified on the development equipment side of the execution environment, and further, the falsification is further confirmed. Traceability can be ensured by detecting this.

Embodiment 1 FIG.
FIG. 1 is a block diagram showing a configuration example of a software history management system (software management system) according to the present invention.

  In FIG. 1, 1 is an operation unit, and 2 is a management unit. As will be described later, when the operation unit 1 and the management unit 2 are separate devices, the operation unit 1 corresponds to an example of an operation device, and the management unit 2 corresponds to an example of a management device.

  First, components of the operation unit 1 will be described. 11 is a project archive input unit (software input unit) for inputting a project archive, and 12 is a project reverse archive that returns the project archive from the project archive input unit 11 to a project and an operation history management file. Is Reference numeral 13 denotes a hash value extraction unit (falsification detection information extraction unit) that extracts a hash value (falsification detection information) of a recorded project from the operation history management file from the project reverse archiving unit 12. This is a temporary project archiving unit on the operation unit side that converts the project from the project reverse archiving unit 12 into a temporary project archive. 15 is an operation unit side hash value generation unit that generates a hash value (information for falsification detection) of a project before operation from the temporary project archive from the operation unit side temporary project archive unit 14 using a hash function. Falsification detection information calculation unit) 16 is the hash value of the project before the operation from the operation unit side hash value generation unit 15 and the hash of the project recorded in the operation history management file from the hash value extraction unit 13 It is a falsification detection unit that compares the values and detects whether the project has been falsified. Reference numeral 17 denotes an operation unit side operation input unit for inputting an operation to the project and a user ID of an operator who performs an operation on the project. Reference numeral 18 denotes an operation unit side operation input of the project from the project reverse archiving unit 12. This is a project operation unit (change operation unit) that performs a change operation on the project based on operation information on the project from the unit 17. Reference numeral 20 denotes an operation time measurement unit that measures the operation time from the project operation unit 18 to the project, and reference numeral 21 denotes an operation content extraction unit that extracts operation content from the project operation unit 18 to the project. 22 is a user ID storage unit that stores a user ID from the operation unit side operation input unit 17, and 23 is an operation unit ID storage unit that stores an operation unit ID. 24, from the operation time from the operation time measurement unit 20, the operation content from the operation content extraction unit 21, the user ID from the user ID storage unit 22, and the operation unit ID from the operation unit ID storage unit 23. An operation history core information generation unit that generates operation history core information (operation attribute information). Reference numeral 25 denotes a project after operation from the project operation unit 18, and operation history core information from the operation history core information generation unit 24. An operation unit side management unit I / F unit that transmits an operation history management file from the project reverse archiving unit 12 to the management unit 2. 26 is an operation history information display unit that extracts and displays operation history information from the operation history management file from the project reverse archiving unit 12, and 31 is an IP address information of a device on which the management unit 2 operates, and a management It is a pair management unit connection information storage unit that stores the standby port number of the unit 2.

  Next, components of the management unit 2 will be described. 51 denotes a management unit side operation unit I / F that receives a post-operation project, operation history core information, and an operation history management file from the operation unit side management unit I / F unit 25 included in the operation unit 1. An F unit (input unit) 54 is a management unit side temporary project archiving unit that converts the project after the operation from the management unit side operation unit I / F unit 51 into a temporary project archive. 55 is a management unit side hash value generation unit (tamper detection information generation) that uses a hash function to generate a hash value (falsification detection information) from the temporary project archive from the management unit side temporary project archive unit 54. 56 is an operation unit ID extraction unit that extracts an operation unit ID from the operation history core information from the management unit side operation unit I / F unit 51. 57 is a version information extraction unit that extracts version information before operation from the operation history management file from the management unit side operation unit I / F unit 51, and 58 is a management unit ID storage that stores a management unit ID. Part. 59 is a version information generation unit that generates version information after operation from the version information from the version information extraction unit 57 and the operation unit ID from the operation unit ID extraction unit 56, and 60 is a management unit side pair operation. From the operation history core information from the unit I / F unit 51, the management unit ID from the management unit ID storage unit 58, the version information after operation from the version information generation unit 59, and the management unit side hash value generation unit 55 This is an operation history information generation unit (update information generation unit) that generates operation history information from the hash value. 61 is a project ID generation unit that generates a project ID for each project if the operation content included in the operation history core information from the management unit side operation unit I / F unit 51 is newly created. The operation history management file generation unit generates an operation history management file and records the project ID from the project ID generation unit 61 and the management unit ID from the management unit ID storage unit 58. 63, the operation history information from the operation history information generation unit 60 is converted into an operation history management file from the management unit side operation unit I / F unit 51 or an operation history management file from the operation history management file generation unit 62. An operation history information recording unit (operation history management file update unit) that additionally records and records the operation history management file 64 from the operation history information recording unit 63 and the management unit side operation unit I / F unit 51. This is a project archiving unit that generates a project archive by converting one project into one file. Reference numeral 65 denotes a project archive storage unit (recording unit) that stores a project archive from the project archive unit 64. Reference numeral 70 denotes a management that designates a project archive to be output to the project archive storage unit 65. It is a part side operation input part. Reference numeral 66 denotes a project archive output unit that outputs a project archive from the project archive storage unit 65 designated by the management unit side operation input unit 70.

  FIG. 2 is a diagram showing the file structure of a project, 101 is a source code file group in which software source code is described, and 102 is a parameter in which various parameters affecting the operation of the software are described. A parameter value file group 103 is a resource file group in which resources such as image data and documents embedded in software are described. 104 is a source code file group 101, a parameter value file group 102, a resource file This is a project consisting of all files constituting one software, consisting of the group 103. The project shown in FIG. 2 corresponds to an example of change operation target software.

  FIG. 3 is a diagram showing an example of generating a temporary project archive, and 111 indicates a temporary project archive.

  FIG. 4 is a diagram illustrating an example of generation of a hash value after operation, and 112 is a hash value after operation.

  FIG. 5 is a diagram illustrating an example of management unit ID information, where 121 is management unit ID information, 122 is management unit ID core information, and 123 is IP address information.

  FIG. 6 is a diagram showing an example of version information, and 131 is version information.

  FIG. 7 is a diagram illustrating an example of generation of version information.

  FIG. 8 is a diagram showing an example of an operation history management file. 141 is an operation history management file, 142 is version information, operation time information (hereinafter also referred to as “operation time”), and operation unit ID information. (Hereinafter also referred to as “operation unit ID”), user ID information (hereinafter also referred to as “user ID”), operation content information (hereinafter also referred to as “operation content”), hash value information (hereinafter referred to as “hash value”). Operation history information consisting of management unit ID information (hereinafter also referred to as “management unit ID”), and 143 is operation history core information consisting of operation time, operation unit ID, user ID, and operation content. Show. The operation history core information is information indicating the attribute of the change operation in the operation unit 1 and corresponds to an example of the operation attribute information.

  FIG. 9 is a diagram showing an example of generating and disassembling a project archive, 151 is an operation history management file, and 161 is a project archive.

  FIG. 10 is a flowchart outlining an exemplary operation of the operation unit 1.

  FIG. 11 is a flowchart outlining an exemplary operation of the management unit 2.

  FIG. 12 is a diagram showing a connection configuration between the operation unit and the management unit in the software history management system according to the present embodiment.

  FIG. 13 is a flowchart showing the falsification detection function of the present embodiment.

  FIG. 14 is a flowchart showing the version information generation function according to this embodiment.

  FIG. 15 is a flowchart showing the operation unit ID information generation function according to the present embodiment.

  FIG. 16 is a flowchart showing the management unit ID information generation function according to the present embodiment.

  FIG. 17 is a flowchart showing generation of an operation history management file according to the present embodiment.

  Next, an operation example of the operation unit 1 will be outlined with reference to FIG. First, in step S1001, the project archive input unit 11 inputs a project archive (input step). In the project archive, the project 104 and the operation history management file 151 are converted into one file by archiving as shown in FIG. The project 104 corresponds to the change operation target software. As shown in FIG. 8, the operation history management file 151 includes a hash value (information for falsification detection). Next, after the project reverse archiving unit 12 performs reverse archiving processing on the input project archive, the hash value extraction unit 13 obtains a hash value (falsification detection information) from the operation history management file 151 in step S1002. Extract (tamper detection information extraction step). In step S1003, the operation unit side hash value generation unit 15 calculates a hash value (falsification detection information) from the project using a hash function (falsification detection information calculation step). Note that the hash value calculated in S1003 corresponds to calculated falsification detection information. Next, in step S1004, the falsification detection unit 16 compares the hash value extracted in S1002 with the hash value calculated in S1003 to detect the presence or absence of falsification of the project (falsification detection step). If the two hash values are the same (Yes in S1005), in step S1006, the project operation unit 18 performs a change operation on the project in accordance with the input content from the operation unit side operation input unit 17 (change operation step). Next, in step S1007, the operation history core information generation unit 24 generates operation history core information (operation attribute information) indicating the attributes of the change operation such as operation time, operation unit ID, user ID, and operation content. In step S1008, the operation unit side management unit I / F unit 25 transmits the post-operation project, operation history core information, and operation history management file to the management unit. On the other hand, if the two hash values are not the same in step S1005, it is considered that the project has been tampered with. Therefore, in step S1009, the project archive is discarded and the process is terminated.

  Next, an operation example of the management unit 2 will be outlined with reference to FIG. First, in step S1101, the management unit side operation unit I / F unit 51 receives a post-operation project, operation history core information, and an operation history management file from the operation unit 1 (input step). Next, in step S1102, the management unit-side hash value generation unit 55 generates a hash value (falsification detection information) from the received project after the operation (falsification detection information generation step). Next, in step S1103, the version information extraction unit 57 extracts the version information before operation included in the operation history management file. Next, in step S1104, the operation unit ID extraction unit 56 extracts the operation unit ID included in the operation history core information. Next, in step S1105, software version information after operation is generated from the version information before operation and the operation unit ID. A method for generating the version information after the operation will be described later. Next, in step S1106, the operation history information generation unit 60 generates update information (update information generation step). The update information is information for updating the operation history management file by reflecting the change operation in the operation unit, and includes version information, operation time information, operation unit ID information, user ID information, operation content information, and the like. , Hash value information and management unit ID information. Next, in step S1107, the operation history information generation unit 60 adds the hash value to the update information to obtain operation history information (operation history management file update step). In step S1108, the operation history information recording unit 63 updates the operation history management file by adding the operation history information generated in step S1107 to the operation history management file (operation history management file update step). Next, in step S1109, the project archiving unit 64 performs archiving processing of the project after operation and the operation history management file after update, and generates a project archive. Next, in step S1110, the project archive storage unit 65 records the project archive (recording step).

  Next, the operation of the software history management system according to the present embodiment will be described in detail with reference to FIGS. First, a project archive is input from the project archive input unit 11 of the operation unit 1. In the project archive, the project 104 and the operation history management file 151 are made into one file by archiving as shown in FIG. Further, the project is all files necessary for realizing one software including a source code file group 101, a parameter value file group 102, and a resource file group 103 as shown in FIG.

  The project reverse archiving unit 12 receives the project archive from the project archive input unit 11 and decomposes the project archive into a project and an operation history management file by reverse archiving processing.

  The hash value extraction unit 13 receives the operation history management file separated from the project archive from the project reverse archiving unit 12 and extracts hash value information from the latest operation history information described in the operation history management file. . As shown in FIG. 8, the operation history information is included in the operation history management file 141, and the hash value information is included in the operation history information 142 described in the newest order.

  The operation unit side temporary project archiving unit 14 receives the project separated from the project archive from the project reverse archiving unit 12 and generates a temporary project archive. The temporary project archive is obtained by archiving the project 104 as shown in FIG. 3 and differs from the project archive in that the operation history management file is not included.

  The operation unit side hash value generation unit 15 receives the temporary project archive from the operation unit side temporary project archive creation unit 14 and generates a hash value of the project before the operation. The hash value information is generated from the temporary project archive using a hash function as shown in FIG. For the hash function, for example, MD5 function or SHA-1 function, it is impossible to generate the original input data from the hash value information, and other input data having the same hash value is generated. Apply functions that are extremely difficult to do.

  As shown in FIG. 13, the falsification detection unit 16 receives the hash value in the operation history management file from the hash value extraction unit 13, and the hash value of the project before the operation from the operation unit side hash value generation unit 15, These two hash values are compared, and if they are the same value, it is detected that they have not been tampered with, and if they are different values, it has been detected that they have been tampered with. If falsification has occurred, the project archive input to the project archive input unit 11 is discarded as an unreliable object, and the process ends.

  Next, an operation such as a change to a project to the project operation unit 18 is input from the operation unit side operation input unit 17, and a user ID is input to the user ID storage unit 22. The user ID is given to each operator in advance, such as an e-mail address. The user ID is always different for each operator, so this information identifies which operator operated the project. can do.

  The project operation unit 18 receives a project from the project reverse archiving unit 12 and changes the project based on the operation input from the operation unit side operation input unit 17.

  The operation time measurement unit 20 monitors the operation of the project in the project operation unit 18 and measures the time when a change is made.

  The operation content extraction unit 21 monitors the operation on the project in the project operation unit 18 and extracts the operation content when a change is made.

  The user ID storage unit 22 receives an operator's user ID from the operation unit side operation input unit 17 and stores the user ID.

  The operation unit ID storage unit 23 stores an operation unit ID given in advance for each operation unit. If the operation unit ID is not stored, as shown in FIG. 15, the current time, the IP address of the device on which the operation unit operates, the machine name, the product ID specified at the time of installation, etc. are used as random seeds. A numerical value is generated and stored as an operation unit ID.

  The operation history core information generation unit 24 receives the operation time from the operation time measurement unit 20, the operation content from the operation content extraction unit 21, the user ID from the user ID storage unit 22, and the operation unit ID from the operation unit ID storage unit 23. , Respectively, to generate an operation history information core. The operation history core information is a part of the operation history information 142 described in the operation history management file 141 as shown in FIG. 8, and includes operation time information, operation unit ID information, user ID information, and operation content information. It consists of.

  The pair management unit connection information storage unit 31 stores a predetermined IP address of a device on which the management unit 2 operates and a standby port number of the management unit 2.

  The operation unit side management unit I / F unit 25 receives the project after the operation from the project operation unit 18, the operation history core information from the operation history core information generation unit 24, and the operation history management file from the project reverse archiving unit 12. The management unit 2 is provided with the IP address of the device on which the management unit 2 operates and the standby port number of the management unit 2 are input from the pair management unit connection information storage unit 31 and the management unit 2 includes the IP address and standby port number. A connection is established with the side-to-side operation unit I / F unit 51, and a project, operation history core information, and an operation history management file are transmitted.

  The operation history information display unit 26 receives the operation history management file from the project reverse archiving unit 12 and extracts and displays the operation history information. By using the operation history information display unit 26, it is possible to confirm operation history information indicating when and who performed what operation with respect to a project, and clarifying the development process of software. it can.

  The management unit side operation unit I / F unit 51 included in the management unit 2 receives a project, operation history core information, and operation history from the operation unit side management unit I / F unit 25 included in the operation unit 1. Receive management files.

  The management unit side temporary project archiving unit 54 receives a project after operation from the management unit side operation unit I / F unit 51 and generates a temporary project archive after operation.

  The management unit side hash value generation unit 55 receives the temporary project archive after the operation from the management unit side temporary project archive generation unit 54 and generates a hash value using a hash function.

  The management unit ID storage unit 58 stores management unit ID information given in advance for each management unit. As shown in FIG. 5, the management unit ID information is obtained by concatenating the management unit ID core information and the IP address of the device on which the management unit operates. When the management unit ID information is not stored, as shown in FIG. 16, the current time, the IP address of the device on which the management unit operates, the machine name, the product ID specified at the time of installation, and the like are used as seeds of random numbers. A random number value is generated and used as management unit ID core information 122. Next, it is generated by connecting the IP address information 123 of the device on which the operation unit operates.

  The version information extraction unit 57 receives the operation history information management file from the counter operation unit I / F unit 51 and extracts the version information before the operation.

  The operation unit ID extraction unit 56 receives the operation history core information from the pair operation unit I / F unit 51 and extracts the operation unit ID.

  The version information generation unit 59 receives the version information from the version information extraction unit 57 and the operation unit ID from the operation unit ID extraction unit 56, and generates version information after the operation. As shown in FIG. 6, the version information is information in which pairs of operation unit IDs and serial numbers are continuous.

  In order to generate the version information, as shown in FIG. 14, if the last operation unit ID in the version information is the same as the operation unit ID after the operation, the serial number at the end of the version information is incremented by one. If they are different, a set of the operation unit ID after operation and the serial number “1” is added to the end of the version information. Thus, as shown in FIG. 7, when the operation is repeated in the same operation unit, the number of pairs of the operation unit ID and the serial number in the version information does not increase, and the serial number at the end increases by one, and a different operation is performed. When the operation is performed on the part, the number of the combination of the operation part ID and the serial number in the version information is increased by 1, and the serial number at the end returns to “1”.

  The operation history information generation unit 60 receives the operation history core information from the management unit side operation unit I / F unit 51, the hash value after operation from the management unit side hash value generation unit 55, and the management unit ID storage unit 58 from the management unit Version information is input from the version information generation unit 59, and update information is generated from the version information, operation time information, operation unit ID information, user ID information, operation content information, and management unit ID. Then, the operation history information is generated by adding the hash value to the update information. As shown in FIG. 8, the operation history information is information described in the operation history management file 141, and includes version information, operation time information, operation unit ID information, user ID information, operation content information, It consists of hash value information and management unit ID information.

  The project ID generation unit 61 receives the operation history core information from the management unit side operation unit I / F unit 51 and extracts the operation content from the operation history core information as shown in FIG. If it is created, a project ID is generated.

  The operation history management file generation unit 62 receives a project ID from the project ID generation unit 61 and a management unit ID from the management unit ID storage unit 58, and creates a new operation history management file as shown in FIG. The project ID and management unit ID are recorded in the operation history management file. When no project ID is input from the project ID generation unit 61, the operation history management file generation unit 62 does not operate.

  The operation history information recording unit 63 receives operation history information from the operation history information generation unit 60, receives an operation history management file from the operation history management file generation unit 62 or the management unit side operation unit I / F unit 51, and The operation history information is recorded in the operation history management file, and the operation history management file is updated.

  The project archiving unit 64 receives the project from the management unit side operation unit I / F unit 51 and the operation history management file after recording the operation history information from the operation history information recording unit 63, respectively. Is generated. As shown in FIG. 9, the project archive is obtained by forming the project 104 and the operation history management file 151 into one file by archiving processing.

  The project archive storage unit 65 receives the project archive from the project archive unit 64 and stores the project archive.

  Next, the project ID and version information of the project archive to be output are specified from the management unit side operation input unit 70 to the project archive storage unit 65.

  The project archive output unit 80 receives the project archive designated by the management unit side operation input unit 70 from the project archive storage unit 65 and outputs the project archive.

  In the first embodiment, the operation unit side management unit I / F unit 25 provided in the operation unit 1 and the management unit side provided in the management unit 2 based on the IP address stored in the pair management unit connection information storage unit 31. Since the counter operation unit I / F unit 51 transmits and receives data, the operation unit 1 and the management unit 2 do not need to operate in the same device. Accordingly, as shown in FIG. 12, (a) in each device, a connection configuration in which the operation unit and the management unit transmit and receive data within the same device is possible. In this case, the IP address of the management unit is 127.0.0.1. In addition, (b) a connection configuration in which the operation unit transmits and receives data to and from a management unit that operates on another device is also possible. In this case, the management unit transmits / receives data to / from an operation unit that operates in the same device and an operation unit that operates in another device. Furthermore, (c) there is a device in which a management unit operates, and a connection configuration in which an operation unit operating in another device transmits and receives data to and from the management unit is also possible.

  As described above, the project hash value recorded in the operation history management file included in the project archive input to the project archive input unit 11 of the operation unit 1 and the operation from the temporary project archive generated from the project. Since the falsification detection unit 16 compares the hash value generated by the department-side hash value generation unit 15, it is possible to detect whether or not the project has been falsified. Further, by displaying the operation history information included in the operation history management file on the operation history information display unit 26, the operator can know when and who performed what operation with which operation unit. As a result, it becomes possible to ensure traceability of the software. In addition, since the operation unit 1 and the management unit 2 operate independently and enable a plurality of connection configurations between them, both distributed management and centralized management of project archives are possible.

Embodiment 2. FIG.
In the first embodiment described above, the user ID input from the operation unit side operation input unit is a part of the operation history information. Next, whether the input user ID is that of the operator. An embodiment will be described in which the user ID is authenticated when in doubt.

  FIG. 18 is a configuration diagram showing a configuration example of the software history management system in such a case.

  In FIG. 18, reference numeral 301 denotes a user authentication unit. As will be described later, when the user authentication unit 301 is a separate device from the operation unit 1, the user authentication unit 301 corresponds to a user authentication device.

  In the present embodiment, the operation unit 1 further includes elements 302 to 304. 302 receives a user ID and password from the operation unit side operation input unit, inputs the password to the operation unit side hash value generation unit 15, acquires a password hash value as its output, and obtains the user ID and password hash. It is a user ID inquiry part which inquires of the user authentication part 301 whether a value corresponds. Reference numeral 303 denotes a user operation unit connection information storage unit that stores IP address information of a device on which the user authentication unit 301 operates and a standby port number of the user authentication unit 301. 304 receives a user ID and password / hash value from the user ID inquiry unit 302 and establishes a connection with the user authentication unit 301 based on the IP address and port number input from the user authentication unit connection information storage unit 303. It is an operation unit side user authentication unit I / F unit that transmits a user ID and a password / hash value and receives an authentication result in the user authentication unit 301.

  In the present embodiment, the operation unit side hash value generation unit 15 corresponds to an example of a user authentication information calculation unit, the project operation unit 18 corresponds to an example of a change operation unit, and the operation unit side vs. user authentication unit I. The / F unit 304 corresponds to an example of an output unit and an authentication result input unit.

  The user authentication unit 301 includes elements 311 to 341. In the user authentication unit 301, 331 is a user authentication unit side operation input unit that inputs a user ID and a password, and 332 receives a password and password from the user authentication unit side operation input unit 331, and will be described later. The password is output to the unit-side hash value generation unit 333, the user authentication unit-side hash value generation unit 333 receives the password / hash value generated from the password, and the user authentication information is obtained from the password and the password / hash value. It is a user authentication information generation part which produces | generates. Reference numeral 333 denotes a user authentication unit-side hash value generation unit that receives the password from the user authentication information generation unit 332 and generates a password / hash value using a hash function, and 341 receives from the user authentication information generation unit 332 User authentication information is input, the user authentication information is stored, and a user ID and password / hash value are input from a user authentication result generation unit 321 described later, and user authentication including the previous period user ID and the password / hash value is performed. It is a user authentication information storage unit that checks whether information is stored and outputs the truth value. 311 receives a user ID and a password / hash value from the operation unit side user authentication unit I / F unit 304 of the operation unit 1 and outputs them to a user authentication result generation unit 321 to be described later. 321 is a user authentication unit side operation unit I / F unit that transmits the verification result returned by 321 to the operation unit side user authentication unit I / F unit 304, and 321 is a user authentication unit side operation unit I / F unit 311. The user ID and password / hash value are input from the user ID, the user authentication information storage unit 341 is inquired whether user authentication information including the user ID and the password / hash value is stored, and stored from the user authentication information storage unit 341. This is a user authentication result generation unit that receives a true / false value indicating whether or not the user is authentic and outputs the true / false value to the user authentication unit side operation unit I / F unit 311.

  FIG. 19 is a flowchart showing the user authentication function of the present embodiment.

  FIG. 20 is a diagram showing a connection configuration between the operation unit and the user authentication unit in the software history management system of the present invention.

  Next, the operation will be described with reference to FIGS.

  First, a user ID and password stored in the user authentication information storage unit 341 are input from the user authentication unit side operation input unit of the user authentication unit 301.

  The user authentication information generation unit 332 receives the user ID and password from the user authentication unit side operation input unit 331, and outputs the password to the user authentication unit side hash value generation unit 333.

  The user authentication unit side hash value generation unit 333 receives the password from the user authentication information generation unit 332 and generates a password / hash value using a hash function.

  The user authentication unit side hash value generation unit 333 outputs the generated password / hash value to the user authentication information generation unit 332.

  The user authentication information generation unit 332 receives the password / hash value from the user authentication unit-side hash value generation unit 333, and generates user authentication information including the user ID and the password / hash value.

  The user authentication information storage unit 341 receives user authentication information from the user authentication information generation unit 332 and stores the user authentication information.

  Next, operations from when a project archive is input from the project archive input unit 11 of the operation unit 1 to when an operation such as a change to a project to the project operation unit 18 is input from the operation unit side operation input unit 17 Is equivalent to the first embodiment. That is, in FIG. 18, the same functional units as those in FIG. 1 are denoted by the same numbers. The operation different from the previous embodiment is after the operation unit side operation input unit 17 inputs the user ID and password to the user ID inquiry unit 302.

  That is, the user ID inquiry unit 302 receives the user ID and password from the operation unit side operation input unit 17 and outputs the password to the operation unit side hash value generation unit 15.

  As shown in FIG. 19, the operation unit side hash value generation unit 15 receives a password from the user ID inquiry unit 302 and generates a password hash value using a hash function. The password / hash value generated by the operation unit side hash value generation unit 15 corresponds to an example of calculated user authentication information.

  The operation unit side hash value generation unit 15 outputs the generated password / hash value to the user ID inquiry unit 302.

  The user ID inquiry unit 302 receives the password / hash value from the operation unit side hash value generation unit 15 and outputs the user ID and the password / hash value to the operation unit side user authentication unit I / F unit 304. .

  The user authentication unit connection information storage unit 303 stores a predetermined IP address of a device on which the user authentication unit 301 operates and a standby port number of the user authentication unit 301.

  The operation unit side user authentication unit I / F unit 304 receives the user ID and password / hash value from the user ID inquiry unit 302, and the IP address of the device on which the user authentication unit 301 operates from the user authentication unit connection information storage unit 303. And the standby port number of the user authentication unit 301 are input, respectively, and a connection is established with the user authentication unit side operation unit I / F unit 311 of the user authentication unit 301 based on the IP address and standby port number, and the user The ID and the password / hash value are transmitted.

  The user authentication unit side operation unit I / F unit 311 receives the user ID and password / hash value from the operation unit side user authentication unit I / F unit 304, and receives the user ID and password / hash value from the user. The result is output to the authentication result generation unit 321.

  The user authentication result generation unit 321 receives the user ID and the password / hash value from the user authentication information storage unit 341, generates user authentication information from the user ID and the password / hash value, and the user authentication information storage unit 341. Whether the user authentication information is stored.

  The user authentication information storage unit 341 receives the user authentication information from the user authentication result generation unit 321 and checks whether or not the corresponding user authentication information is stored as shown in FIG. A true / false value that is “true” or “false” if not stored is output to the user authentication result generation unit 321.

  The user authentication result generation unit 321 receives a true / false value from the user authentication information storage unit 341 and outputs the true / false value to the user authentication unit side operation unit I / F unit 311.

The user authentication unit side operation unit I / F unit 311 receives a true / false value from the user authentication result generation unit 321,
The true / false value is output to the operation unit side user authentication unit I / F unit 304 of the operation unit 1.

  The operation unit side user authentication unit I / F unit 304 receives a true / false value from the user authentication unit side operation unit I / F unit 311 and outputs the true / false value to the user ID inquiry unit 302.

  The user ID inquiry unit 302 receives a true / false value from the operation unit side user authentication unit I / F unit 304 and outputs the user ID to the user ID storage unit 22 if the true / false value is “true”. To do. If the true / false value is “false”, the operator is notified of an authentication error and waits for the user ID and password to be input again from the operation unit side operation input unit 17.

  The operation after the user ID storage unit 22 receives the user ID from the user ID inquiry unit 302 instead of the operation unit side operation input unit 17 is the same as that of the first embodiment.

  In the second embodiment, the operation unit side user authentication unit I / F unit 304 and the user authentication unit 301 included in the operation unit 1 are provided based on the IP address stored in the connection information storage unit 303. Since the user authentication unit side operation unit I / F unit 311 transmits and receives data, the operation unit 1 and the user authentication unit 301 do not need to operate in the same device. Accordingly, as shown in FIG. 20, (a) in each device, a connection configuration in which the operation unit and the user authentication unit transmit and receive data within the same device is possible. In this case, the IP address of the user authentication unit is 127.0.0.1. In addition, (b) a connection configuration in which the operation unit transmits and receives data to and from a user authentication unit that operates on another device is also possible. In this case, the user authentication unit transmits and receives data to and from an operation unit that operates in the same device and an operation unit that operates in another device. Furthermore, (c) there is a device in which the user authentication unit operates, and a connection configuration in which an operation unit operating in another device transmits and receives data to and from the user authentication unit is also possible.

  As described above, the password is input together with the user ID from the operation unit side operation input unit 17, and the user ID inquiry unit 302 determines whether or not the user authentication information matches the user authentication information stored in the user authentication information storage unit 341 in advance. By checking, it is possible to authenticate the user ID input by the operator at the operation unit, and it is possible to use a common user ID by transmitting and receiving data to and from the same user authentication unit by a plurality of operation units It is.

  In each embodiment described above, the operation unit 1, the management unit 2, and the user authentication unit 301 can be realized by a computer. Although not shown, the operation unit 1, the management unit 2, and the user authentication unit 301 include a CPU (Central Processing Unit) that executes a program.

  For example, a CPU is connected to a ROM (Read Only Memory), a RAM (Random Access Memory), a communication board, a display device, a K / B (keyboard), a mouse, an FDD (Flexible Disk Drive), and a CDD (Compact Disc) via a bus. Drive), magnetic disk device, optical disk device, printer device, scanner device and the like. The RAM is an example of a volatile memory. ROM, FDD, CDD, magnetic disk device, and optical disk device are examples of nonvolatile memory. Data and information handled by the operation unit 1, management unit 2, and user authentication unit 301 of each embodiment described above are stored in a storage device or storage unit, and are operated by each unit of the operation unit 1, management unit 2, and user authentication unit 301. , Recorded and read out.

  The communication board may be connected to a WAN (Wide Area Network) such as a LAN, the Internet, or ISDN, for example.

  The magnetic disk device stores an operating system (OS), a window system, a program group, and a file group (database). The program group is executed by a CPU, OS, and window system.

  Each unit of the operation unit 1, the management unit 2, and the user authentication unit 301 may be configured by a program that can be partially or entirely operated by a computer. Alternatively, it may be realized by firmware stored in the ROM. Alternatively, it may be implemented by software, hardware, or a combination of software, hardware, and firmware.

  The program group stores a program that causes the CPU to execute the processing described as “˜unit” in the description of the embodiment. These programs are created by computer languages, such as C language, HTML, SGML, and XML, for example.

  The program is stored in another recording medium such as a magnetic disk device, FD (Flexible Disk), optical disk, CD (compact disk), MD (mini disk), DVD (Digital Versatile Disk), and read by the CPU. And executed.

  Here, the features of the software history management system shown in the first and second embodiments are shown below.

The software history management system shown in the first embodiment is
A software history management system that manages operation history information and version information such as new creations and changes made to software,
It has an operation unit and a management unit,
In the operation section,
A file group (hereinafter referred to as a project) that constitutes one software consisting of a source code file group, a parameter value file group, a resource file group, and a file that records operation history information added to the project. A project archive input unit for inputting a file (hereinafter referred to as an operation history management file) (hereinafter referred to as a project archive);
A project reverse archive unit that returns the project archive from the project archive input unit to the project and the operation history management file;
A hash value extraction unit for extracting the hash value of the recorded project from the operation history management file from the project reverse archiving unit;
A temporary project archiving unit on the operation unit side that converts the project from the project reverse archiving unit into one file (hereinafter referred to as a temporary project archive);
An operation unit side hash value generation unit that generates a hash value of a project using a hash function from the temporary project archive from the operation unit side temporary project archive unit;
A falsification detection unit that compares the hash value of the project from the hash value generation unit on the operation unit side with the hash value of the recorded project from the hash value extraction unit, and detects whether the project has been falsified;
An operation input unit on the operation unit side for inputting a user ID given in advance to an operation to the project or an operator who performs an operation on the project,
A project operation unit for operating a project from the project reverse archiving unit based on operation information to the project from the operation unit side operation input unit;
A project output section for outputting a project after operation from the project operation section;
An operation time measurement unit that measures the operation time from the project operation unit to the project;
An operation content extraction unit for extracting operation content to the project from the project operation unit;
A user ID storage unit for storing a user ID from the operation unit side operation input unit;
An operation unit ID storage unit that stores an ID (hereinafter referred to as an operation unit ID) given in advance for each operation unit that performs operations on the project;
From the operation time from the operation time measurement unit, the operation content from the operation content extraction unit, the user ID from the user ID storage unit, and the operation unit ID from the operation unit ID storage unit, an operation history core An operation history core information generation unit for generating information;
A management unit connection information storage unit that stores IP address information of a device on which the management unit operates and a standby port number of the management unit that is a fixed value;
The project after the operation from the project operation unit, the operation history core information from the operation history core information generation unit, and the operation history management file from the project reverse archive unit are stored in the connection management unit connection information storage unit. Based on the stored connection information, the operation unit side management unit I / F unit that transmits to the management unit,
An operation history information display unit that extracts and displays operation history information from the operation history management file from the project reverse archiving unit,
In the management department,
A management unit side operation unit I / F unit that receives a project after operation, operation history information, and an operation history management file from the operation unit side management unit I / F unit included in the operation unit;
A management unit side temporary project archiving unit that converts the project after the operation from the management unit side operation unit I / F unit into one file (hereinafter referred to as a temporary project archive);
A management unit side hash value generation unit that generates a hash value using a hash function from the temporary project archive from the management unit side temporary project archive unit;
An operation unit ID extraction unit that extracts an operation unit ID from operation history information from the management unit side operation unit I / F unit;
A version information extraction unit for extracting version information before operation from an operation history management file from the management unit side operation unit I / F unit;
A management unit ID storage unit that stores an ID (hereinafter referred to as a management unit ID) given in advance for each management unit that manages the project;
A version information generation unit that generates version information after operation from the version information from the version information extraction unit and the operation unit ID from the operation unit ID extraction unit;
Operation history core information from the management unit side operation unit I / F unit, management unit ID from the management unit ID storage unit, version information after operation from the version information generation unit, and the management unit side An operation history information generation unit that generates operation history information from the hash value from the hash value generation unit;
If the operation content included in the operation history core information from the management unit side operation unit I / F unit is newly created, a project ID generation unit that generates a unique ID (hereinafter, project ID) for each project;
An operation history management file generating unit that generates an operation history management file and records the project ID from the project ID generation unit and the management unit ID from the management unit ID storage unit;
The operation history information from the operation history information generation unit is added to the operation history management file from the management unit side operation unit I / F unit or the operation history management file from the operation history management file generation unit. An operation history information recording unit for recording;
An operation history management file from the operation history information recording unit, a project archiving unit for generating a project archive by making a project from the management unit side operation unit I / F unit into one file,
A project archive storage unit for storing a project archive from the project archive unit;
A management unit side operation input unit for designating a project archive to be output to the project archive storage unit;
A project archive output unit that outputs a project archive from the project archive storage unit designated by the management unit side operation input unit;
Record in the operation history management file the change history information about when and who performed what operation on which operation section for the project, and the hash value that enables detection of tampering of the project. The software is operated by a project archive in which a management file and a project are made into one file, thereby ensuring the traceability of the software and enabling both distributed management and centralized management of the project archive.

The software history management system shown in the second embodiment
In addition to the operation unit and management unit, a user authentication unit
The operation unit is
A user ID and password are input from the operation unit side information input unit, and a password hash value (hereinafter referred to as a password / hash value) is generated from the password using the operation unit side hash value generation unit. And a user ID inquiry part that inquires of the user authentication part whether or not
A user authentication unit connection information storage unit that stores IP address information of a device on which the user authentication unit operates and a standby port number of the user authentication unit that is a fixed value;
The operation unit side that transmits the user ID and password / hash value from the user ID inquiry unit to the user authentication unit based on the connection information stored in the connection authentication storage unit for user authentication and receives the inquiry result A user authentication unit I / F unit,
The user authentication unit
A user authentication unit side operation input unit for inputting a user ID and a password;
A password and a password are input from the user authentication unit side operation input unit, a password / hash value is generated using a user authentication unit side hash value generation unit, which will be described later, and user authentication information is generated from the user ID and the password hash value A user authentication information generation unit to perform,
A user authentication unit side hash value generation unit that receives a password from the user authentication information generation unit, generates a password hash value from the input password using a hash function, and returns the password hash value to the user authentication information generation unit;
A user authentication information storage unit that receives and stores user authentication information from the user authentication information generation unit;
A user ID and a password / hash value are received from the operation unit side user authentication unit I / F included in the operation unit, output to a user authentication result generation unit described later, and a verification result returned by the user authentication result generation unit is returned. A user authentication unit side operation unit I / F unit that transmits to the operation unit side user authentication unit I / F;
Whether a user ID and a password / hash value are input from the user authentication unit side operation unit I / F unit, and the user authentication information including the user ID and the password / hash value is stored in the user authentication information storage unit A user authentication result generation unit that returns “true” if stored and “false” if not stored to the user authentication unit side operation unit I / F unit,
It is possible to authenticate a user ID input by an operator at the operation unit, and to use a common user ID at a plurality of operation units.

1 is a configuration diagram illustrating a configuration example of a software history management system according to Embodiment 1. FIG. The figure which shows the file structural example of a project. The figure which shows the example of a production | generation of a temporary project archive. The figure which shows the production | generation example of the hash value after operation. The figure which shows the example of management part ID information. The figure which shows the example of version information. The figure which shows the example of the production | generation procedure of version information. The figure which shows the example of an operation history management file. The figure which shows the production | generation of a project archive, and an example of decomposition | disassembly. The flowchart figure which shows the operation example of an operation part. The flowchart figure which shows the operation example of a management part. The figure which shows the example of a connection structure of an operation part and a management part. The flowchart figure which shows the falsification detection function. The flowchart figure which shows a version information generation function. The flowchart figure which shows the operation part ID information generation function. The flowchart figure which shows the management part ID information generation function. The flowchart figure which shows the production | generation procedure of the operation history management file. FIG. 6 is a configuration diagram illustrating a configuration example of a software history management system according to a second embodiment. The flowchart figure which shows a user authentication function. The figure which shows the example of a connection structure of an operation part and a user authentication part.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 Operation part, 2 Management part, 11 Project archive input part, 12 Project reverse archive part, 13 Hash value extraction part, 14 Operation part side temporary project archive part, 15 Operation part side hash value generation part, 16 Tampering Detection unit, 17 operation unit side operation input unit, 18 project operation unit, 20 operation time measurement unit, 21 operation content extraction unit, 22 user ID storage unit, 23 operation unit ID storage unit, 24 operation history core information generation unit, 25 Operation unit side management unit I / F unit, 26 operation history information display unit, 31 management unit connection information storage unit, 51 management unit side operation unit I / F unit, 54 management unit side temporary project archive unit, 55 management unit side hash value generation unit, 56 operation unit ID extraction unit, 57 version information extraction unit, 58 management unit ID storage unit, 59 version information generation unit, 60 Operation history information generation unit, 61 Project ID generation unit, 62 Operation history management file generation unit, 63 Operation history information recording unit, 64 Project archive generation unit, 65 Project archive storage unit, 66 Project archive output unit, 70 Management Operation side input unit, 301 User authentication unit, 302 User ID inquiry unit, 303 Connection information storage unit for user authentication unit, 304 Operation unit side user authentication unit I / F unit, 311 User authentication unit side operation unit I / F part, 321 User authentication result generation part, 331 User authentication part side operation input part, 332 User authentication information generation part, 333 User authentication part side hash value generation part, 341 User authentication information storage part.

Claims (19)

A software management system for managing software change operations,
Performs a software change operation and outputs the software after the change operation, an operation history management file indicating the history of the software change operation performed up to the change operation, and operation attribute information indicating the attribute of the change operation An operation unit to
The software after the change operation, the operation history management file and the operation attribute information are input from the operation unit, the falsification detection information for falsification detection is generated from the software after the change operation, and the input operation history management file and Based on the operation attribute information, the update information for updating the operation history management file is generated by reflecting the change operation in the operation unit, the falsification detection information is added to the generated update information, and the falsification detection information is A management unit that updates the operation history management file by adding the added update information to the operation history management file and records the updated operation history management file and the software after the change operation in association with each other. Software management system. The management unit
The software management system according to claim 1, wherein the updated operation history management file and the software after the change operation are archived and recorded. The operation unit is
Enter the change operation target software that is the target of the change operation and the operation history management file of the change operation target software that contains the falsification detection information for falsification detection of the change operation target software.
From the change operation target software, information for alteration detection of the change operation target software is calculated as information for falsification detection,
Extract the falsification detection information from the operation history management file of the software to be changed,
Compare the calculated falsification detection information with the extracted falsification detection information,
The software management system according to claim 1, wherein when the two match as a result of the comparison, the change operation target software is changed. The operation unit is
4. The software management system according to claim 3, wherein archive information in which the change operation target software and the operation history management file of the change operation target software are archived is input. The management unit
Generate software version information after the change operation from the operation history management file and operation attribute information input from the operation unit,
2. The software management system according to claim 1, wherein update information is generated based on the generated version information, management unit ID information indicating an ID of the management unit, and operation attribute information. The operation unit is
We have an operation history management file that contains at least the version information of the software before the change operation.
Operation attribute information including at least operation unit ID information indicating the ID of the operation unit is generated,
Along with the software after the change operation, an operation history management file including at least the version information of the software before the change operation and operation attribute information including at least the operation unit ID information are output to the management unit,
The management unit
Extracting the version information of the software before the change operation in the operation unit from the operation history management file input from the operation unit,
From the operation attribute information input from the operation unit, the operation unit ID information of the operation unit is extracted,
The software version information after the change operation is generated based on the extracted version information of the software before the change operation and the extracted operation unit ID information of the operation unit. Management system. The operation unit is
Operation attribute information including operation time information indicating the time when the change operation is performed, user ID information indicating the ID of the user who performed the change operation, and operation content information indicating the content of the change operation is generated. The software management system according to claim 1. The software management device further includes:
Storing user authentication information for user authentication, and having a user authentication unit for performing user authentication of the user of the operation unit using the stored user authentication information;
The operation unit is
Prior to the software change operation, information for user authentication is calculated as calculated user authentication information using input information from the user, and the calculated calculated user authentication information is output to the user authentication unit.
The user authentication unit includes:
Calculated user authentication information is input from the operation unit, user authentication is performed using the input calculated user authentication information and stored user authentication information, and an authentication result is output to the operation unit.
The operation unit is
The software management system according to claim 1, wherein when a user is authenticated by the user authentication unit by inputting an authentication result from the user authentication unit, a software change operation is performed. A management device that communicates with an operation device that performs software change operations and manages software change operations,
Software after the change operation from the operation device, an operation history management file indicating the history of the change operation of the software performed until the change operation in the operation device, and operation attribute information indicating the attribute of the change operation in the operation device An input unit for inputting and
A falsification detection information generating unit that generates falsification detection information for falsification detection from the software after the change operation input by the input unit;
Based on the operation history management file and operation attribute information input by the input unit, an update information generation unit that generates update information for updating the operation history management file by reflecting the change operation in the operation device;
Operation history management file update for adding the falsification detection information to the update information generated by the update information generation unit and adding the update information with the falsification detection information added to the operation history management file to update the operation history management file And
A management apparatus comprising: a recording unit that records the operation history management file updated by the operation history management file update unit in association with the software after the change operation. The recording unit is
The management apparatus according to claim 9, wherein the updated operation history management file and the software after the change operation are archived and recorded. The management device further includes:
A version information generation unit that generates version information of the software after the change operation from the operation history management file and the operation attribute information input by the input unit;
The update information generation unit
The management apparatus according to claim 9, wherein update information is generated based on version information generated by the version information generation unit, management apparatus ID information indicating an ID of the management apparatus, and operation attribute information. The input unit is
The operation history management file including at least version information of the software before the change operation in the operation device, and operation attribute information including at least operation device ID information indicating the ID of the operation device together with the software after the change operation from the operation device. Input,
The version information generation unit
The version information of the software before the change operation in the operation device is extracted from the operation history management file input by the input unit, and the operation device ID information of the operation device is extracted from the operation attribute information input by the input unit. 12. The version information of the software after the change operation is generated based on the extracted version information of the software before the change operation extracted and the extracted operation device ID information of the operation device. The management device described. An operating device for performing a software change operation,
A software input unit that inputs the change operation target software to be changed and the operation history management file of the change operation target software including the falsification detection information for detecting falsification of the change operation target software; ,
An alteration detection information calculation unit that calculates information for alteration detection of the alteration operation target software as calculation alteration detection information from the alteration operation target software input by the input unit;
A falsification detection information extraction unit that extracts falsification detection information from the operation history management file input by the input unit;
A falsification detection unit that compares the calculated falsification detection information calculated by the falsification detection calculation unit with the falsification detection information extracted by the falsification detection information extraction unit;
An operation apparatus comprising: a change operation unit configured to perform a change operation of the change operation target software when the two match as a result of the comparison by the falsification detection unit. The input unit is
14. The operating device according to claim 13, wherein archive information in which the change operation target software and the operation history management file of the change operation target software are archived is input. The operating device is:
It is possible to communicate with a user authentication device that performs user authentication of a user of the operation device,
The operating device further includes:
Prior to a software change operation by the change operation unit, a user authentication information calculation unit that calculates information for user authentication as calculated user authentication information using input information from a user;
An output unit that outputs the calculated user authentication information calculated by the user authentication information calculation unit to the user authentication device;
As a response to the output of the calculated user authentication information, an authentication result input unit that inputs an authentication result of user authentication from the user authentication device,
The change operation unit includes:
The operation device according to claim 13, wherein when the user is authenticated by the user authentication device, a software change operation is performed. A software management method for managing software change operations,
From the operating device performing the software changing operation to the software after the changing operation, the operation history management file indicating the history of the software changing operation performed until the changing operation in the operating device, and the attribute of the changing operation in the operating device An input step for inputting operation attribute information indicating
Falsification detection information generation step for generating falsification detection information for falsification detection from the software after the change operation input in the input step;
An update information generation step for generating update information for updating the operation history management file by reflecting the change operation in the operation device based on the operation history management file and the operation attribute information input in the input step;
Operation history management file update for adding the falsification detection information to the update information generated by the update information generation step and adding the update information with the falsification detection information to the operation history management file to update the operation history management file Steps,
A software management method comprising: a recording step of recording the operation history management file updated by the operation history management file update step in association with the software after the change operation. A software operation method for changing software,
An input step for associating and inputting the change operation target software to be changed and the operation history management file of the change operation target software including the falsification detection information for falsification detection of the change operation target software;
Falsification detection information calculation step for calculating information for falsification detection of the change operation target software as calculated falsification detection information from the change operation target software input in the input step;
Falsification detection information extraction step for extracting falsification detection information from the operation history management file input in the input step;
A falsification detection step for comparing the calculated falsification detection information calculated by the falsification detection calculation step with the falsification detection information extracted by the falsification detection information extraction step;
A software operation method comprising: a change operation step of performing a change operation of the change operation target software when both match as a result of the comparison in the falsification detection step. A program that causes a computer to manage software change operations,
From the operating device performing the software changing operation to the software after the changing operation, the operation history management file indicating the history of the software changing operation performed until the changing operation in the operating device, and the attribute of the changing operation in the operating device Input processing for inputting operation attribute information indicating
Falsification detection information generation processing for generating falsification detection information for falsification detection from the software after the change operation input by the input processing;
Update information generation processing for generating update information for updating the operation history management file by reflecting the change operation in the operation device based on the operation history management file and the operation attribute information input by the input processing;
Operation history management file update for adding falsification detection information to the update information generated by the update information generation process and adding the update information with the falsification detection information to the operation history management file to update the operation history management file Processing,
A program for causing a computer to execute a recording process for associating and recording the operation history management file updated by the operation history management file update process and the software after the change operation. A program for causing a computer to execute a software change operation,
Input processing for associating and inputting the change operation target software to be changed and the operation history management file of the change operation target software including the falsification detection information for falsification detection of the change operation target software;
Falsification detection information calculation processing for calculating information for falsification detection of the change operation target software as calculated falsification detection information from the change operation target software input by the input processing;
Falsification detection information extraction processing for extracting falsification detection information from the operation history management file input by the input processing;
Falsification detection processing for comparing the calculated falsification detection information calculated by the falsification detection calculation processing and the falsification detection information extracted by the falsification detection information extraction processing;
A program for causing a computer to execute a change operation process for performing a change operation of a change operation target software if both match as a result of the comparison by the falsification detection process.

Images