JP2000029672A - Distribution management device for software - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve reliability by performing accurate reflection on software by trouble, function addition, function correction, etc., by managing the constitution and history of the same software distributed to systems of different version managing methods. SOLUTION: Distribution information on software inputted to a distribution indication input part 101 is sent by a terminal 100 to a software constitution management part 105 which obtains information on the latest version of distribution-source software saved in a software group storage device 114 and information on the directory by a software constitution management information storage device 108. Those pieces of information are sent to a version information generation part 107, which generates version information by distribution destinations through a version management rule storage device 109. The information is sent to a software distribution part 113 and a software distribution information storage part 111.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a software distribution management device. In various information processing devices operated by programs and application technology fields of information processing devices,
Software development takes a lot of time and money. As the scale of development increases, distributed software is often distributed to computer systems having the same functions as systems that have completed development.

[0002]

2. Description of the Related Art When the same software is distributed to a plurality of systems, if a change is made to the software due to a failure or a change in specifications, it is necessary to reflect the change in all the distributed systems.

[0003] In the conventional example, a public patent publication (Japanese Unexamined Patent Publication No.
As described in Japanese Patent Application Publication No. 8-320782), on the assumption that software is diverted from the system where the change was made to the system where the change is to be reflected, the structure of the diverted source and the diverted destination are assumed. Software distribution management by providing a diversion information recording unit for recording the software.

There is also a software distribution management tool such as a Microsoft System Management Server that has a server that manages master software and distributes it to clients who need it. This tool
Version management is performed in a CSS system on the same LAN, and a method of centrally managing the distribution source software and managing which version has been distributed to the distribution destination has been adopted.

[0005]

In the above-mentioned method, when the same software is repeatedly used, the connection between the preceding and following systems is lost due to a change in the system being used. For example, if a change is made only to B when the data is diverted from A to B and further diverted from B to C, the relationship between A and C is deleted, and the change of A cannot be reflected on C. Further, if the diversion is repeated, unless the respective systems are interconnected by a network, the work for obtaining the information of the first diversion source from the latest diversion destination becomes enormous. Also, in software development, the version management method is often different when the operating computer systems are different, and the above method is applied when distributing the same software to a plurality of systems with different version management methods. could not.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problems of the conventional diversion management device and distribution management device. The object of the present invention is to provide the same software distributed to systems having different version management methods. An object of the present invention is to provide a software distribution management device capable of obtaining configuration and history information. Still another object of the present invention is to provide a software distribution management device that enables, when a copy is made from a distribution destination system to another computer system, the information to be reflected in software distribution information. Still another object of the present invention is to provide a software distribution management device that can manage the software distribution order to distribution destination systems.

[0007]

SUMMARY OF THE INVENTION Therefore, claim 1 of the present application is provided.
The software configuration includes a software group that distributes software to a plurality of computer systems, a software management apparatus that manages a change history of the software group, and a software distribution apparatus that distributes software to a plurality of computer systems. In the management device, for each distribution destination system that distributes software, a version management rule storage device that stores version assignment rules to be assigned to software, and when distributing software to be distributed, based on rules of the version management rule storage device when distributing software to be distributed. Means for assigning a version to software, and a software distribution information storage device for storing a version of a distribution destination for each distributed software,
The configuration and history of the same software distributed to a plurality of systems of different version management methods are managed.

The software distribution management device according to the second aspect of the present invention compares the current version of software in the distribution destination system with the latest version of software managed in the distribution source software management device. It has a means for verifying and displaying a list of different items.

Further, the software distribution management device according to the third aspect of the present invention includes means for displaying a list of distribution system names to which software to be distributed is distributed and a distribution history.

According to a fourth aspect of the present invention, there is provided a software distribution management device for inputting information obtained by copying a software group from a distribution destination system to another computer system, and a software distribution information storage device based on the information. Means for reflecting the software distribution information within the server.

According to a fifth aspect of the present invention, there is provided a software distribution management device for inputting distribution level information for determining a distribution order of a distribution destination system, and distribution level information for managing the distribution level information. The system includes a management device, and includes means for instructing whether or not distribution is possible in response to a software distribution request, and means for displaying completion / incomplete of software distribution.

A software distribution management device according to a first aspect of the present invention assigns a version to software based on a version assignment rule set for each system to which the software is distributed, and provides a version of a distribution destination for each distributed software. Is stored, the software of the distribution source is associated with the software of the distribution destination, and it is recognized that different versions of software distributed to a plurality of systems are the same.

Further, the software distribution management device according to the second aspect of the present invention, by inputting key information to a system to be verified, obtains information on the version of software distributed in the system and information on the distribution source. By comparing and verifying the version information managed in the software management device and searching for different ones, information necessary to reflect changes made to software distributed in the system is obtained. .

According to a third aspect of the present invention, the software distribution management device inputs key information of software to be distributed and, based on the information, a key to which the software is distributed from the software distribution information storage device. Search and display the system name and distribution history.

Further, the software distribution management device according to the fourth aspect of the present invention provides a new area in the software distribution information storage device by inputting information obtained by copying a software group from a distribution destination system to another computer system. Is created, and the software distribution information of the distribution destination system is copied into the newly created area. As a result, the management can be performed in the same manner as the distribution without using the software distribution device. Further, the software distribution management device according to claim 5 of the present application, by inputting key information of software to be distributed, transfers key information from the software distribution information storage device to the system to which the software is distributed. Given to the distribution level information management device,
Obtain the distribution order of the distribution destination system.

Further, by inputting the key information of the software to be distributed, the information of the version of the software is compared with the information managed in the distribution source software management device from the software distribution information storage device. Obtain information on software distribution status. By associating the above-mentioned distribution order information with the distribution status information, it is indicated whether the software has been distributed to the distribution target system or not, and distribution is not performed to a system whose distribution order is set after the distribution-uncompleted system. Show that it is possible.

[0017]

DESCRIPTION OF THE PREFERRED EMBODIMENTS One embodiment of the software distribution management device of the present invention will be described in detail with reference to the drawings.

FIG. 1 shows the overall configuration of the software distribution management device. The computer system A115, the computer system B116, and the computer system C117 are systems to which software is distributed, respectively.

The terminal 100 allows the distribution instruction input unit 10
The information for identifying the distribution source software (for example, product ID, task No, etc.) and the information for indicating the distribution location of the distribution destination system (for example, directory information, etc.), which are input to 1, are software distribution instruction information. The software configuration management unit 105 is transmitted to the software configuration management unit 105, and the software configuration management unit 105
From 08, configuration management software configuration management information indicated by the latest version information and directory information of the distribution source software stored in the software group storage device 114 is obtained.

Next, these pieces of information are transmitted to the version information creating unit 107. The version information creating unit 107 creates version information for each distribution destination from the version management rule storage unit 109 as described later with reference to FIG. Further, such information is stored in the software distribution unit 113 and the software distribution information storage unit 1.
The software distribution unit 113 transfers the software of the software group storage device 114 from the directory where the software is stored to the computer system A1 to be distributed.
15, computer system B116, computer system C11
The software distribution information storage unit 111 stores these pieces of information in the software distribution information storage device 112.

The search key information input to the search key information input unit 102 by the terminal 100 is transmitted to the software distribution information acquisition unit 110, and the software distribution information acquisition unit 110 retrieves the search result from the software distribution information storage device 112. Is output to the search information display unit 103. The copy information input to the copy information registration unit 104 by the terminal 100 is transmitted to the software distribution information copy unit 118. The software distribution information copy unit 118 creates software distribution information and stores it in the software distribution information storage device 112. I do.

FIG. 2 shows the version information creating unit 10 shown in FIG.
7 shows an example of a version information creation algorithm for creating version information. 200 is
This is a table in which version upgrade rules for each system to be distributed are recorded. The master indicates the version management rules of the software configuration management information managed by the software configuration management unit 105. The system A, system B, and system C respectively Refers to the version control rules of the distribution destination system. Reference numeral 201 denotes an example of a history of version information created in accordance with the version management rule 200, which will be described below as an example.

The version information creation unit 107 obtains, from the software distribution information storage device 112, the latest version information of the software currently distributed to the distribution target system. For example, if the version of task 1 distributed to machine α of system A is Ver2.0, and if version 3.1 is specified to be distributed to machine α of system A in order to reflect the version UP, the version information The creating unit 107 stores the software distribution information storage device 1
12 to retrieve the data of task 1 of machine α of system A, and obtain information that the latest distribution version is Ver 3.0 (202).

Next, according to the version management rule 200, the increment 1.0 due to the version UP of the system A is added to the version 3.0.
In addition, version information is created as Ver 4.0.

FIG. 3 shows an example of searching for a distribution destination and distribution history of software to be distributed. In the software distribution information storage device 112, software distribution information is stored in the form of a table indicated by 300. Search key information input unit 1
When task 1 is input as a search key in 02, the software distribution information acquisition unit 110 searches only the information of task 1 from the information of 300 and obtains the result indicated by 301.

FIG. 4 shows an example of searching for software for which the latest version has not been distributed (= software requiring redistribution). Software distribution information is stored in the software distribution information storage device 112 in the form of a table indicated by 400. When the system A and the machine α are input to the search key information input unit 102 as search keys, the software distribution information acquisition unit 110 searches only the information of the system A and the machine α from the information of 400 and obtains a result indicated by 401.

On the other hand, reference numeral 402 denotes distribution software stored in the software configuration management information storage device 108;
Ver information. 401 and 402 are associated with each other using the distribution software as a key, and a search is made for distribution software in which the master version of 401 and the latest master version of 402 do not match, thereby obtaining a result 403. The difference between the distributed software and the latest software version indicates that the searched software is software that needs to be redistributed.

FIG. 5 shows the copy information registration unit 10 shown in FIG.
4 is shown in an enlarged manner. When the terminal 100 instructs the copy information registration unit 104 to copy the computer system A 115 to the computer system B 116, the software distribution information copying unit 118
2, the system 500 extracts information 500 of the system A, replaces the key information with the system B, and creates the information of the system B in 501, and at the same time, creates a new area in the software distribution information storage device 112 and Is stored in the new area.

FIGS. 6A and 6B show an example of a software distribution method when the software distribution order is determined. First, the system shown in the example is determined to distribute software in the order of the lowest machine operation rate (terminal → server → controlling CPU) (600). At this time, a distribution level is set from the earlier distribution order, and these are managed as distribution level information (601).

Next, software that needs redistribution is searched from the entire system (602). By combining this information with the existing software distribution information and obtaining the information on the machine that needs to be redistributed, the distribution level, the version of the master to be distributed, and the distributed version information,
Completion / incompletion of software distribution and availability / non-distribution of software can be derived (603). For example, since task 1 has been distributed to terminals 1 and 2 at distribution level 1, distribution of task 1 to server 1 at distribution level 2 is permitted. However, since the task 2 has not been distributed to the terminal 3 at the distribution level 1, the distribution of the task 2 is not permitted to the servers 1 and 2 at the distribution level 2.

[0031]

As described above, according to the first, second, and third aspects of the present invention, the software distributed to the computer system is caused by a defect, a function addition, a function correction, or the like. The changes can be accurately reflected and reliability can be improved.

According to the fourth aspect of the present invention, a function of copying the distribution information when the software is distributed from the computer system to which the software has been distributed to another computer system is provided, thereby eliminating the need for redistribution. Can improve development efficiency.

According to the fifth aspect of the present invention, since the software can be distributed according to the distribution order in response to the software distribution request, the influence of the software distribution particularly when redistributing the software to the operating system is obtained. Can be distributed in consideration of the above, and the security of the entire system can be improved.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a software distribution device according to an embodiment of the present invention.

FIG. 2 is a conceptual diagram of a copying process from a system A to a system B;

FIG. 3 is a diagram showing software distribution management data and a version assignment method.

FIG. 4 is a diagram showing a method for searching for software that requires redistribution.

FIG. 5 is a diagram showing a distribution management method according to a distribution order.

FIGS. 6A and 6B are diagrams illustrating a software distribution order and a distribution level.

[Explanation of symbols]

100: terminal, 101: distribution instruction input unit, 102: search key information input unit, 103: search information display unit, 104: copy information registration unit, 105: software configuration management unit, 107
... Version information creation unit, 108 ... Software configuration management information storage unit, 109 ... Version management rule storage unit, 110 ... Software distribution information acquisition unit, 111 ... Software distribution information storage unit, 112 ... Software distribution information storage unit, 113 ... Software Distributor, 114 ...
Software group storage device, 115 ... Computer system A,
116: Computer system B, 117: Computer system C, 118: Software distribution information copying unit.

 ────────────────────────────────────────────────── ─── Continuing on the front page (72) Inventor Masayuki Usami 5-2-1 Omika-cho, Hitachi City, Ibaraki F-term in the Omika Plant of Hitachi, Ltd. F-term (reference) 5B076 AB10 AC01

Claims (5)

[Claims] 1. A software configuration management apparatus comprising: a software group for distributing software to a plurality of computer systems, a change history of the software group, and a software distribution apparatus for distributing software to the plurality of computer systems. For each distribution destination system that distributes software, a version control rule storage device that stores the version assignment rules to be assigned to the software, and when distributing the software to be distributed, the version is converted to the software based on the rules of the version control rule storage device. Means for assigning, and a software distribution information storage device for storing a version of a distribution destination for each distributed software, and manages the configuration and history of the same software distributed to a plurality of systems of different version management methods. Distribution management device software, characterized in that. 2. The method according to claim 1, wherein the current version of the software in the distribution destination system is compared with the latest version of the software managed in the software management apparatus of the distribution source, and different software versions are listed. A software distribution management device comprising means for displaying. 3. The software distribution management device according to claim 1, further comprising means for displaying a list of system names of distribution destinations to which the distribution target software is distributed and a distribution history. 4. A means for inputting information obtained by copying software groups from a distribution destination system to another computer system, and means for reflecting software distribution information in a software distribution information storage device based on the information. A software distribution management device comprising: 5. A software distribution request according to claim 1, further comprising: means for inputting distribution level information for determining a distribution order of a distribution destination system; and a distribution level information management device for managing said distribution level information. A software distribution management apparatus, comprising: means for instructing whether or not distribution is possible to a user, and means for displaying completion / incomplete of software distribution.