JP7103973B2 - Software package update support device, software package update support method, and software package update support program - Google Patents

Description

The present invention relates to a software package update support device, a software package update support method, and a software package update support program.

By reading the software, the computer realizes the operations and the like described in advance in the software. It is also software that realizes web distribution processing, transaction processing, database management processing, and so on. The operating system as a base function and the applications running on the base are also software. Computers are introduced by combining a plurality of software subdivided for each function in this way. The software distributor improves the functions of the software while maintaining the same identity, and introduces the improved software to the market (release). This is commonly referred to as a version upgrade. Software users change existing software to improved software. This is commonly referred to as a version update.

Version upgrades and version updates are called differently depending on the position of the distributor and the user, but they are essentially the same concept. A set of software having a specific function is called a "software package". Software packages are often the unit of release. Hereinafter, the software package is abbreviated as "PKG (Package)".

One PKG operates in cooperation with another PKG. The interface, logic, data structure, etc. used for cooperation can be changed depending on the version of PKG. For example, it is assumed that PKG1 and PKG2 are operating in cooperation with each other. It is assumed that PKG1 has been upgraded to PKG1.2. At this time, if PKG1.2 and PKG2 cannot operate in cooperation with each other, the user must refrain from updating from PKG1 to PKG1.2 or introduce another PKG2.2 or the like that operates in cooperation with PKG1.2. Must be.

That is, there are restrictions on whether or not cooperation is possible between PKG versions. There are many PKGs and their versions, the forms of restrictions are various, and the existence of restrictions themselves is often unclear, which makes it difficult to determine the version update. Furthermore, even if a new version that works in cooperation is found, the new version may carry the risk that the operation itself as an individual is not stable.

The software update support device of Patent Document 1 stores a table (table) that stores a combination of a plurality of versions that are guaranteed to operate in cooperation with each other. Then, when the combination of versions already installed in the device does not match the combination stored in the table, the software update support device upgrades a certain PKG or downgrades a certain PKG (to an older version). Change) is proposed. The software management device of Patent Document 2 determines whether or not it is possible to update the software of a spare machine among a plurality of computers when they are operating in cooperation with each other.

Japanese Unexamined Patent Publication No. 2009-230398 Japanese Unexamined Patent Publication No. 2012-141878

The software update support device of Patent Document 1 is premised on a combination of versions that are guaranteed to work together, and Patent Document 1 refers to the case where such a premise is not given. Not done. Further, the software update support device does not show the judgment criteria when the user selects one of the candidates of the combination specified in advance. Furthermore, Patent Document 1 does not mention the risks of the new version.

The software management device of Patent Document 2 aims to determine the timing for safely updating the software of the spare machine. The software management device stores a plurality of combinations of versions that operate in a consistent manner. Patent Document 2 is based on the premise that the operators of many computers, including spare machines, create the software themselves. Furthermore, Patent Document 2 also does not mention which of these combinations is selected based on what criteria.

However, especially when using open source software, it is rather rare to be able to confirm the technical guarantee that one version of one PKG will work in tandem with another version of PKG without any problems. Even if the technical guarantee can be confirmed, the technical guarantee will soon become obsolete for the development of a new version. On the other hand, even if it is not strictly guaranteed that a plurality of PKGs operate in cooperation with each other, it is often sufficient to confirm the fact that the combination actually operates (appears to be) in cooperation with each other.
Therefore, an object of the present invention is to provide a combination of versions that is as new as possible and avoids unknown risks in a model that suppresses human judgment and operation as much as possible.

The software package update support device of the present invention has a map having a normalized continuous value as an axis indicating the specifications of software packages that operate in cooperation with each other in a computer, and a plurality of software packages described in the map. It is characterized by having a display processing unit that displays the combination of versions of the above and highlights the combination of recommended versions determined based on the number of achievements of the candidates among the candidates of the combination shown on the map. ..
Other means will be described in the form for carrying out the invention.

According to the present invention, it is possible to provide a combination of versions that is as new as possible and avoids unknown risks in a format that minimizes human judgment and operation.

It is a figure explaining the structure of the PKG update support apparatus. It is a figure explaining the logical structure of the computer to be managed. This is an example of computer group information. This is an example of computer information. This is an example of PKG information. It is a figure explaining the version quantitative value. This is an example of an achievement map. This is an example of update recommended information. Reason for recommendation This is an example of pattern information. It is a flowchart of a processing procedure. This is an example of the update recommendation screen. This is an example of the update recommendation screen (continued).

Hereinafter, a mode for carrying out the present invention (referred to as “the present embodiment”) will be described in detail with reference to figures and the like. This embodiment is an example in which a software package update support device (PKG update support device) supports a version update of PKG installed in a plurality of managed computers, and is an example in which PKG is open source software. be. However, the present invention is also applicable when the PKG is a general commercial PKG other than open source software. In the following description, version update may be abbreviated as "update" unless a misunderstanding occurs.

(Configuration of PKG update support device)
FIG. 1 is a diagram for explaining the configuration of the PKG update support device 1. The PKG update support device 1 is a general computer, and includes a central control device 11, an input device 12 such as a mouse and a keyboard, an output device 13 such as a display, a main storage device 14, an auxiliary storage device 15, and a communication device 16. .. These are connected to each other by a bus. The auxiliary storage device 15 stores computer group information 31, computer information 32, PKG information 33, actual map 34, update recommendation information 35, and recommendation reason pattern information 36 (all of which will be described in detail later).

The computer information acquisition unit 21, the public information analysis unit 22, the version analysis unit 23, the performance map creation unit 24, the incentive management unit 25, the update recommendation information creation unit 26, and the display processing unit 27 in the main storage device 14 are programs. The central control device 11 reads these programs from the auxiliary storage device 15 and loads them into the main storage device 14, thereby realizing the functions of the respective programs (details will be described later). The PKG update support device 1 may acquire these programs from an external device via the network 2 or via any medium. The auxiliary storage device 15 may have a configuration independent of the PKG update support device 1.

The PKG update support device 1 is connected to the managed computer 3, the PKG distribution source 5, and the PKG risk information distribution source 6 via the network 2. Each managed computer 3 has a plurality of PKGs 7. There are a plurality of managed computers 3 and they belong to the computer group 4 which is a set of managed computers 3. The PKG update support device 1 can acquire the number (actual number) of the managed computers 3 belonging to the computer group 4 that have introduced a combination of a certain version (details will be described later).

The PKG distribution source is a distribution source of the PKG 7 introduced in the managed computer 3, and transmits the PKG 7 itself (source code), information on the version of the PKG 7, and the like to the PKG update support device 1. The PKG distribution source 5 in FIG. 1 is, more accurately, an arbitrary device operated by the PKG distribution source.

The PKG risk information distribution source is a distribution source of information about security vulnerabilities of PKG introduced in the managed computer 3. The PKG risk information distributor is a manufacturer in the case of commercial PKG, a development community in the case of open source software, a third party community, or the like. The PKG risk information distributor discloses information on security vulnerabilities discovered after the release of PKG (contents of security holes, virus attack methods against security holes, defense methods against attacks, etc.). The PKG risk information distribution source 6 in FIG. 1 is, more accurately, an arbitrary device operated by the PKG risk information distribution source.

(Logical configuration of managed computer)
FIG. 2 is a diagram illustrating a logical configuration of the managed computer 3. The managed computer 3 has an application layer 41, a middleware layer 42, and an OS (Operating System) layer 43. These layers have a hierarchical structure.

The application layer 41 is an entity of a user application implemented by the user for each managed computer 3. Each application may include a PKG, or may call the PKG from an area outside the application within the application layer 41. The middleware layer 42 is composed of a PKG that provides basic functions such as distribution processing, transaction processing, and database management processing when the managed computer 3 realizes a web system, for example. The OS layer 43 constitutes an operating system. When an external computer 44 different from the managed computer 3 provides a function to the managed computer 3, the function can be regarded as PKG. Even if the PKGs in FIG. 2 are PKGs distributed by the same PKG distributor, it may be unclear whether or not they can be linked.

(Computer group information)
FIG. 3 is an example of computer group information 31. In the computer group information 31, the computer ID is in the computer ID column 102, the computer name is in the computer name column 103, and the computer operation information column 104 is in association with the computer group ID stored in the computer group ID column 101. Computer operation information is stored, computer failure information is stored in the computer failure information column 105, and incentive cumulative value is stored in the incentive cumulative value column 106.

The computer group ID in the computer group ID column 101 is an identifier that uniquely identifies the computer group 4.
The computer ID in the computer ID column 102 is an identifier that uniquely identifies the managed computer 3.
The computer name in the computer name column 103 is the name of the managed computer 3.
The computer operation information in the computer operation information column 104 is information (load amount, cumulative operation time, etc.) related to the operation of the managed computer 3. “#” Indicates a different numerical value abbreviated (the same applies hereinafter).

The computer failure information in the computer failure information column 105 is information related to the failure of the managed computer 3 (time stopped due to failure, time required for recovery, etc.).
The cumulative incentive value in the cumulative incentive value column 106 is the cumulative value of the incentive evaluation value (detailed later).
In addition to the computer operation information column 104 and the computer failure information column 105, there may be a column for storing other attributes of the managed computer 3.

(Calculator information)
FIG. 4 is an example of computer information 32. In the computer information 32, the PKG-ID is in the PKG-ID column 112, the PKG name is in the PKG name column 113, and the current version name column 114 is currently in association with the computer ID stored in the computer ID column 111. As for the version name, PKG operation information is stored in the PKG operation information column 115, and PKG failure information is stored in the PKG failure information column 116.

The computer ID in the computer ID column 111 is the same as the computer ID in FIG.
The PKG-ID in the PKG-ID column 112 is an identifier that uniquely identifies the PKG7. PKG-ID does not specify a combination of PKG and version.
The PKG name in the PKG name column 113 is the name of PKG7.
The current version name in the current version name column 114 is the name of the current (before update) version of PKG7. The PKG distributor 5 usually names each version with a combination of letters and numbers. In many cases, the higher the number, the newer the version (released later in time).

The PKG operation information in the PKG operation information column 115 is information related to the operation of the PKG 7 (load amount, cumulative operation time, etc.).
The PKG failure information in the PKG failure information column 116 is information related to the failure of PKG7 (time stopped due to failure, time required for recovery, etc.).
In addition to the PKG operation information column 115 and the PKG failure information column 116, there may be a column for storing other attributes of the PKG 7.

(PKG information)
FIG. 5 is an example of PKG information 33. In the PKG information 33, in association with the PKG-ID stored in the PKG-ID column 121, the PKG name column 122 has the PKG name, the version name column 123 has the version name, and the version specification column 124 has the version specification. However, the version quantitative value is stored in the version quantitative value column 125.

The PKG-ID in the PKG-ID column 121 is the same as the PKG-ID in FIG.
The PKG name in the PKG name column 122 is the same as the PKG name in FIG.
The version name in the version name column 123 is the name of the PKG version.

The version specification in the version specification column 124 is a value indicating the specification of the PKG itself, which is not affected by the performance of the hardware such as the central control device 11 and the main storage device 14, and is defined for each version. The following are examples of values that can be version specifications.
・ Number of risk information (column 124a)
The number of risk information is, for example, the number of security vulnerabilities (security holes), the number of countermeasures against security vulnerabilities, or the sum of these weighted by importance. The number of risk information is disclosed by the PKG risk information distribution source 6.
-Number of steps (column 124b)
The number of steps is the number of operations included in the source code of the security vulnerability or the number of operations included in the source code of countermeasures against the security vulnerability. The number of steps is also disclosed by the PKG risk information distributor 6.

-Other values For example, the number of languages used in the document creation PKG, such as the resolution, frame advance speed, number of pixels, reproducible color number, etc. in the video processing PKG, the number of mathematical model parameters (variables) in the statistics creation PKG, etc. , The size of the dictionary, etc. can also be version specifications. Furthermore, the time stopped due to a failure and the time required for recovery can also be version specifications.

Now, for the sake of clarity, the newer the version, the larger the value of the version specification. In fact, some of the above examples of version specification values are smaller as the version is newer. In such a case, the PKG update support device 1 converts the value t of the version specification into "ct" or "c / t". Here, "c" is a positive constant sufficiently large with respect to t.

The version quantitative value in the version quantitative value column 125 is a value obtained by quantitatively and continuously normalizing the novelty of the version. The PKG distribution source 5 names the version name according to its own rule. Therefore, the average user cannot tell which version is newer than which version just by looking at the named version. According to the version quantitative value, this degree becomes clear (details will be described later).

(Version quantitative value)
FIG. 6 is a diagram illustrating a version quantitative value. Now, if there are multiple versions of a PKG, "v1.1.1", "v1.1.2", "v1.2.3", "v2.1.1" and "v3.1.1" do. Of these, "v1.1.1" is the initial version, and "v3.1.1" is the latest version.

The PKG update support device 1 places short vertical line segments 131a to 131e indicating these versions on the number line (horizontal axis) 131. The scale on the horizontal axis 131 is the version name (three numbers in the version name are regarded as three-digit numbers). Therefore, although it depends on the version naming method, in many cases, the position on the horizontal axis 131 of each version shows the order indicating the newness of the version, but the newness in consideration of the difference in the version specifications and the like. It does not indicate the degree of.

Next, the PKG update support device 1 maps (converts) the line segments 131a to 131e on the horizontal axis 131 onto another number line (horizontal axis) 132 as line segments 132a to 132e. The scale on the horizontal axis 132 is a version quantitative value. The PKG update support device 1 calculates a version quantitative value according to, for example, the following rules 1 and 2.

<Rule 1> The PKG update support device 1 sets the version quantitative value of the initial version to "0.0" and the version quantitative value of the latest version to "10.0".
<Rule 2> The PKG update support device 1 performs the following processing for a version (intermediate version) other than the initial version and the latest version.
-The PKG update support device 1 acquires the number of risk information items, the number of steps, or other version specifications from the version specification column 124 of the PKG information 33 (FIG. 5).
-The PKG update support device 1 calculates a version quantitative value for each intermediate version based on these acquired values. For example, assume that the number of risk information items in the latest version is _rn , the number of risk information items in the initial version is _rs , and the number of risk information items in the intermediate version is _rm . At this time, the version quantitative value of the intermediate version is "(( _rm - _rs ) / ( _rn - _rs )) x 100".

According to such processing, the performance of all intermediate versions is normalized in the same range of "0.0 to 100.0" so that it can be compared among a plurality of types of PKGs, which will be described later. Achievement map creation and clustering are effectively executed. In general, a certain intermediate version may change (improve) its own source code or the like without changing the name. Even in such cases, the modified intermediate version is also guaranteed to be mapped to any position on the horizontal axis 132. That is, the continuity of the version quantitative value is guaranteed.

(Achievement map)
FIG. 7 is an example of the actual map 34. The achievement map 34 is a matrix as a whole. For convenience of explanation, a horizontal (X) axis and a vertical (Y) axis are provided with respect to the actual map 34. The X-axis scale is a version quantitative value of PKG “X” introduced (or may be introduced) in a managed computer 3. The Y-axis scale is a version quantitative value of PKG “Y” introduced (or can be introduced) in the managed computer 3. PKG "X" and PKG "Y" operate in cooperation depending on the combination of both versions. A part (reference numeral 143) of the actual map 34 shown on the right side of FIG. 7 will be described later.

The version quantitative value is a value that continuously fluctuates in the range of 0 or more and 100 or less. In FIG. 7, both the X-axis and the Y-axis are separated by 10 columns and rows having a width of "10". In the cell at the intersection of the X-axis and the Y-axis, the actual number of PKGs corresponding to those version quantitative values are stored at the same time as a fact in a computer. For example, the actual number "12" is stored in the cell 141. This means that among the computers that have introduced PKG "X" and PKG "Y" at the same time, the version quantitative value of PKG "X" is in the range of "20 to 30" and that of PKG "Y". There are 12 versions whose quantitative values are in the range of "70 to 80". " The computer here is premised on being the managed computer 3, but other computers may be used.

Bandwidth risk column 142a along the X-axis stores the total number of achievements in each column and the evaluation for the total. Bandwidth risk column 142b along the Y-axis stores the total number of achievements in each row and the evaluation for the total. The evaluation here is "high", "medium", and "low" in order from the one with the smallest number of achievements to the one with the largest number. That is, it is evaluated that the smaller the introduction record of the PKG update support device 1, the higher the risk that the operation of the version itself becomes unstable. The number of achievements indicates the number of facts that the combination of versions is actually working, and is irrelevant to whether or not technical cooperation is possible. In short, whether the combination is guaranteed to work together or not, it is counted as the same case.

(Number of dimensions of achievement map)
The performance map 34 in FIG. 7 is represented by a two-dimensional matrix, which is solely for the sake of simplification of the description. When the managed computer 3 introduces m types of PKG, the PKG update support device 1 creates an actual map 34 in the n (n = 2, 3, ..., M) dimensional space. Then, the PKG update support device 1 draws as many actual points as a combination of n version quantitative values in the n-dimensional space. Further, the PKG update support device 1 clusters a large number of actual points among those in the vicinity by using a method such as the “k-means method”.

In FIG. 7, three shaded rectangles appear in the matrix. These rectangles correspond to the result of clustering (cluster). In FIG. 7, when the number of achievements belonging to a cell in the cluster is "0", "0" is stored in that cell, and when the number of achievements belonging to a cell outside the cluster is "0", that cell is stored. Leaves blank.

(Recommended update information)
FIG. 8 is an example of update recommended information 35. In the update recommended information 35, the PKG-ID, the current version name, and the recommended version name are displayed in the PKG (X-axis) column 152 in the PKG (Y-axis) column 153 in association with the computer ID stored in the computer ID column 151. The PKG-ID, the current version name and the recommended version name are stored in, the incentive evaluation value is stored in the incentive value column 154, and the recommended reason pattern ID is stored in the recommended reason pattern ID column 155.

The computer ID in the computer ID column 151 is the same as the computer ID in FIG.
The PKG-ID (column 152a) of the PKG (X-axis) column 152 is the PKG-ID of the PKG currently introduced by the managed computer 3 corresponding to the X-axis of FIG. The current version name (column 152b) is the name of the current version of the PKG. The recommended version name (column 152c) is the name of the updated version of the PKG recommended by the PKG update support device 1.

The PKG-ID (column 153a) in the PKG (Y-axis) column 153 is the PKG-ID of the PKG currently introduced by the managed computer 3 corresponding to the Y-axis in FIG. The current version name (column 153b) is the name of the current version of the PKG. The recommended version name (column 153c) is the name of the updated version of the PKG recommended by the PKG update support device 1.

The incentive evaluation value in the incentive value column 154 is a value indicating the merit when one or both of the two types of PKGs are updated. Originally, one incentive evaluation value corresponds to one combination of the current version name and the recommended version name of a certain PKG. In other words, the incentive evaluation value is defined for the combination of the "starting point" on the number line 132 of FIG. 6 and the "ending point" on the right side of the "starting point". The incentive evaluation value is defined not only on the number line but also in multiple dimensions. At this time, it is assumed that "value in column 154c> value in column 154a and value in column 154c> value in column 154b" is always established. Normally, "value in column 154c = value in column 154a + value in column 154b" is established, but it may not be established (see below).

The details will be described later, but the PKG update support device 1 promotes the update by giving the incentive evaluation value corresponding to the update to the managed computer 3 that has actually updated. The incentive evaluation value may be calculated based on the technical / functional effect that the user enjoys with the update, or is calculated based on the economic effect (PKG sales scale, etc.) returned to the PKG distributor. May be good. The incentive evaluation value is not directly related to the number of actual results mentioned above. In the present embodiment, the actual number is for determining the recommended version from a large number of candidates, and the incentive evaluation value is given to the managed computer 3 changed to the recommended version after the fact. It is a thing.

The recommendation reason pattern ID column 155 is an identifier that uniquely identifies the recommendation reason pattern. Reason for recommendation The pattern is a type of grounds on which the PKG update support device 1 recommends the update. Reason for recommendation The pattern ID is used to narrow down the recommended version candidates presented to the user.

(Calculation method of incentive evaluation value)
The PKG update support device 1 calculates an incentive evaluation value according to, for example, the following rule 11 or 12.
<Rule 11> The PKG update support device 1 calculates the number of managed computers 3 or the number of PKGs to be updated, and uses them as incentive evaluation values.

<Rule 12> The PKG update support device 1 uses the length of the arrow in the performance map 34 (see reference numeral 143 of FIG. 7) as the incentive evaluation value. The incentive evaluation value when only PKG “X” is updated is the length of arrow 144a. The incentive evaluation value when only PKG “Y” is updated is the length of arrow 144b. The incentive evaluation value when updating both PKG “X” and PKG “Y” is the length of arrow 144c. The length of the arrow indicates the degree of improvement in the newness (version specification) before and after the update. In the case of Rule 12, the above-mentioned "value in column 154c = value in column 154a + value in column 154b" does not hold.

(Recommended reason pattern information)
FIG. 9 is an example of the recommendation reason pattern information 36. In the recommended reason pattern information 36, the recommended reason pattern column 162 contains the recommended reason pattern, and the recommended version abbreviation column 163 contains the recommended version abbreviation in relation to the recommended reason pattern ID stored in the recommended reason pattern ID column 161. The condition is stored in the condition column 164.

The recommended reason pattern ID in the recommended reason pattern ID column 161 is the same as the recommended reason pattern ID in FIG.
The reason for recommendation pattern column 162 The reason for recommendation pattern is a type of grounds for which the PKG update support device 1 recommends the update, as described above. The reason for recommendation pattern is composed of a cluster inside / outside distinction (column 162a) and a recommendation policy (column 162b).

The distinction between inside and outside of a cluster is either "inside a cluster" or "outside a cluster". “Intracluster” indicates that the update is done within one cluster (FIG. 7). For example, the distinction between the inside and outside of the cluster of the three types of updates indicated by arrows 144a to 144c (FIG. 7) is all "inside the cluster". It is also possible to update from cell 145 to cell 146 in FIG. 7. The distinction between inside and outside the cluster of the update is "outside the cluster". The recommendation policy is information indicating the type of PKG (one or both of the two types) for which an update is recommended and whether or not the updated version is the latest.

The recommended version abbreviation in column 163 is one or both of "Vx" and "Vy". If the recommended version abbreviation has only one of "Vx" or "Vy", the recommendation policy does not recommend updating the other PKG. If the recommended version abbreviation has "Vx" and "Vy", the recommendation policy recommends updating both PKGs.

For example, the recommended version "v2.3.4" is associated with "Vx", and the recommended version "v4.3.2" or the like is associated with "Vy" (not shown). .. The associated recommended version may or may not be the latest version (according to the recommended policy).
The condition in the condition column 164 is a condition regarding the risk that the user can tolerate after the update. The conditions are essentially the same as the recommendation reason pattern, but the wording is easier to understand as a display target for the user.

As is clear from looking at FIGS. 8 and 9 at the same time, both are linked by the recommendation reason pattern ID. When the user selects the condition of the recommended reason pattern information 36 (column 164 in FIG. 9), the recommended reason pattern ID is determined. Then, from many records of the update recommendation information 35 (FIG. 8), those having the recommendation reason pattern ID determined here can be extracted.

(Processing procedure)
FIG. 10 is a flowchart of the processing procedure. As a premise for starting the processing procedure, it is assumed that the auxiliary storage device 15 stores the recommendation reason pattern information 36 (FIG. 9) in a state completed by the user in principle (exceptions to the principle will be described later). .. In the middle of the description of FIG. 10, reference is made to FIGS. 11 and 12 as appropriate.

In step S201, the computer information acquisition unit 21 of the PKG update support device 1 creates computer group information 31 (FIG. 3). Specifically, first, the computer information acquisition unit 21 accesses all the managed computers 3 belonging to the computer group 4, and includes the computer group ID, the computer ID of each managed computer 3, the computer name, and the computer. Acquire operation information and computer failure information.

At this time, the computer information acquisition unit 21 also acquires the PKG-ID, PKG name, current version name, PKG operation information, and PKG failure information of the PKG possessed by each managed computer 3. The computer information acquisition unit 21 accesses the managed computer 3 by using a specific connection agent or a general-purpose protocol.
Secondly, the computer information acquisition unit 21 creates the computer group information 31 by using the information acquired in the “first” step S201.

In step S202, the computer information acquisition unit 21 creates computer information 32 (FIG. 4). Specifically, the computer information acquisition unit 21 creates the computer information 32 by using the information acquired in the “first” step S201.

In step S203, the public information analysis unit 22 of the PKG update support device 1 creates PKG information 33 (FIG. 5). Specifically, first, the public information analysis unit 22 identifies the PKG for which the public information is to be acquired. At this time, the public information analysis unit 22 receives an instruction from the user by using the computer group information 31 and the computer information 32, and narrows down the PKGs for which the public information is to be acquired, for example, as follows.

-All PKGs introduced by managed computers belonging to the computer group G01
-All PKGs introduced by computer C001
-PKG whose names are "webA", "dbB", "someC", ...
-In addition, PKG independently determined by the user with definitions not defined in the computer group information 31 and the computer information 32.

Second, the public information analysis unit 22 accesses the PKG distribution source 5 and acquires information about the PKG specified in "first" of step S203 (excluding the information acquired in step S201).
Third, the public information analysis unit 22 accesses the PKG risk information distribution source 6 and acquires the version specifications (number of risk information cases, number of steps, etc.) for the PKG specified in the “first” of step S203.
Fourth, the public information analysis unit 22 creates the PKG information 33 by using the information acquired in the "second" and "third" of step S203. At this stage, the version quantitative value column 125 of the PKG information 33 is blank.

In step S204, the version analysis unit 23 of the PKG update support device 1 calculates the version quantitative value. Specifically, first, the version analysis unit 23 calculates the version quantitative value by the method described above based on the version specifications stored in the PKG information 33 (FIG. 5).
Second, the version analysis unit 23 stores the version quantitative value calculated in "first" of step S204 in the version quantitative value column 125 of the PKG information 33.

In step S205, the display processing unit 27 of the PKG update support device 1 displays the update recommendation screen 51 (FIG. 11). Specifically, the display processing unit 27 displays the update recommendation screen 51 on the output device 13. At this time, the computer group information 31 (FIG. 3) is displayed in the managed computer list column 52 of the update recommendation screen 51.

In step S206, the update recommendation information creation unit 26 of the PKG update support device 1 receives the computer ID and the like. Specifically, first, the update recommendation information creation unit 26 accepts the user to select the computer name or computer ID of any managed computer in the computer column 54 of the managed computer detail column 53. Here, it is assumed that "C001" is selected as the computer ID.

Second, the update recommendation information creation unit 26 searches the computer information 32 (FIG. 4) using "C001" as a search key, and acquires the PKG-ID, PKG name, and current version name of the corresponding record. Then, the update recommendation information creation unit 26 inputs the acquired PKG-ID, PKG name, and current version name to the PKG-ID column 55a, PKG name column 55b, and current version name column 55c in the search result list 55 (FIG. 11), respectively. Display in.

Third, the update recommendation information creation unit 26 accepts the user to press two of the display buttons in the analysis result column 55f of the search result list 55. The PKG of the record of the display button pressed here corresponds to the two axes of the actual map 34 (FIG. 7). Here, it is assumed that the "webA" display button and the "dbB" display button are pressed.
Fourth, the update recommendation information creation unit 26 accepts the user to input any one of the version specifications (FIG. 5) via the input device 12. Here, it is assumed that the “number of risk information items” has been entered.

In step S207, the update recommendation information creation unit 26 accepts the condition. Specifically, the update recommendation information creation unit 26 displays the recommendation reason pattern information 36 (FIG. 9) on the output device 13 and accepts the user to select the condition of one or a plurality of arbitrary records. For the sake of clarity, it is assumed that the user has selected the condition "risk of the latest version of X, Y is unacceptable, Vx, Vy is acceptable".

In step S208, the performance map creation unit 24 of the PKG update support device 1 creates the performance map 34 (FIG. 7). Specifically, first, the actual map creation unit 24 creates an actual map 34 in which each cell and the bandwidth risk columns 142a and 142b are blank.
Secondly, the performance map creation unit 24 investigates the performance (case) in which the PKG corresponding to each axis of the performance map 34 is simultaneously introduced. At this time, the performance map creation unit 24 may access the managed computer 3, the PKG distribution source 5, and the PKG risk information distribution source 6, or may access any other external device. It may accept the user to input via the input device 12.

Thirdly, as described above, the achievement map creation unit 24 draws the achievement points on the achievement map 34 and clusters the adjacent ones. The achievement map creation unit 24 counts the number of achievement points belonging to the cell, stores the counted number as the achievement number in the cell, and then deletes the achievement points.
Fourth, the actual map creation unit 24 totals the actual numbers of the actual map 34 for each column and each row, and stores them in the band risk columns 142a and 142b. Note that the achievement map creation unit 24 may store the total number of achievements only for the rows and columns of the cluster to which the combination of the current versions belongs (see FIG. 7).
Fifth, the achievement map creation unit 24 applies a predetermined threshold value to the achievement number to add "high", "medium" or "medium" to the total number of achievements stored in "fourth" of step S208. Add either "low".

In step S209, the update recommendation information creation unit 26 of the PKG update support device 1 creates update recommendation information 35 (FIG. 8). Specifically, the update recommendation information creation unit 26 is based on the computer information 32 (FIG. 4), the PKG corresponding to the display button pressed in the “third” of step S206, and the conditions received in step S207. , Create a record of update recommendation information 35.

At this time, the update recommendation information creation unit 26 sets the version quantitative value of the recommended version to be equal to or higher than the version quantitative value of the current version. The update recommendation information creation unit 26 stores “P004” corresponding to the condition “the risk of the latest version of X and Y is unacceptable and Vx and Vy are acceptable” in the recommendation reason pattern column 155. The update recommendation information creation unit 26 stores two recommended version names satisfying the above conditions in columns 152c and 153c. The incentive evaluation value column 154 of the record created at this stage is blank.

In step S210, the incentive management unit 25 of the PKG update support device 1 calculates the incentive evaluation value. Specifically, first, the incentive management unit 25 calculates the incentive evaluation value for each record of the update recommendation information 35 by the method described above, and stores the calculated result in the incentive evaluation value column 154. The incentive management unit 25 calculates the incentive evaluation value when only the PKG corresponding to the X-axis is updated, when only the PKG corresponding to the Y-axis is updated, or when both are updated.

Second, the incentive management unit 25 displays the recommended version name and the incentive evaluation value in the recommended version name column 55d and the incentive evaluation value column 55e of the update recommendation screen 51 (FIG. 11). When there are a plurality of recommended versions, the incentive management unit 25 may display a plurality of recommended version names. Similarly, the incentive management unit 25 may display a plurality of corresponding incentive evaluation values.

In step S211th, the display processing unit 27 of the PKG update support device 1 displays the update recommendation screen (continued) 51b (FIG. 12). Specifically, first, the display processing unit 27 displays the update recommendation screen (continued) 51b on the output device 13. At this stage, "C001 (HIKO)" is displayed in the computer column 61, "webA" is displayed in the PKG (X-axis) column 62a, and "dbB" is displayed in the PKG (Y-axis) column 62b. Is displayed. The “number of risk information” is displayed in the important viewpoint column 63.
Second, the display processing unit 27 displays the actual result map 34 created in step S208 in the actual result map column 64 (FIG. 12). Then, the display processing unit 27 determines as the recommended version the version of the candidate belonging to the cluster to which the current version belongs, which has the largest number of actual results.

Third, the display processing unit 27 displays the recommended information 65 (FIG. 12). More specifically, the display processing unit 27 displays the following.
-Position in the actual map of the cluster to which the combination of the current version belongs (column 65a)
-Version name and version quantitative value of the combination of the current version (column 65b)

-Version name and version quantitative value of the latest version combination (column 65c)
-Version name and version quantitative value of the recommended version combination (column 65d)
The version quantitative values "79.4" and "78.2" here are averages of the version quantitative values of PKG belonging to the cell.
-Incentive evaluation value (column 65e) when only the X-axis (or Y-axis) PKG of the current version is updated to the recommended version, and incentive evaluation value (column 65f) when both are updated to the recommended version.

Fourth, the display processing unit 27 highlights the cell 66 indicating the current version and the cell 67 indicating the recommended version on the actual map 34, and connects them with an arrow.
Fifth, the display processing unit 27 displays the condition (see FIG. 9) received in step S207 in the condition column 68.

The PKG (Y-axis) column 62b can display the PKG name that operates in cooperation with "webA" by a drill-down method. In the important viewpoint column 63, all candidates of the version specification can be displayed by a drill-down method. When the user selects another PKG name and / or another version specification in these fields, the update recommendation information creation unit 26 or the like repeats the processes of steps S206 to S211 based on the newly selected information. ..
After that, the processing procedure ends.

(Modification example 1: Granting incentive evaluation value)
The incentive management unit 25 accesses the managed computer 3 at any timing of the processing procedure, or at periodic batch processing or the like, and updates to the recommended version highlighted in “4th” of step S211. Investigate whether or not the managed computer 3 is running. When executing, the incentive management unit 25 uses the incentive evaluation value displayed in the column 65e or the column 65f of FIG. 12 as the incentive cumulative value column of the record for the managed computer in the computer group information 31 (FIG. 3). Add to the value stored in 106.

(Modification example 2: Input of "condition" from the user)
In the above, in step S207, the update recommendation information creation unit 26 receives the condition from the user. However, this process is not essential. When the update recommendation information creation unit 26 does not execute step S207, the display processing unit 27 determines the recommended version from among more candidates in the “second” step S211. Then, in the “fifth” of step S211 the display processing unit 27 displays the condition (column 164 in FIG. 9) corresponding to the determined recommended version in the condition column 68 in FIG.

(Modification example 3: Determining the recommended version that reflects the incentive evaluation value)
The display processing unit 27 may determine a combination of versions whose actual number is equal to or greater than a predetermined threshold value as a candidate for the recommended version. At this time, the display processing unit 27 highlights all the determined candidates in the performance map column 64 (FIG. 12), and displays the incentive evaluation values corresponding to the respective candidates in the columns 65e and 65f (FIG. 12). Accepts the user's selection. In this way, the number of achievements is not the maximum, but it becomes easier to select a newer version combination.

(Effect of this embodiment)
The effects of the PKG update support device of this embodiment are as follows.
(1) The PKG update support device can display an appropriate updated version to the user based on the number of achievements in a space where the newness of the version can be compared in each axial direction.
(2) The PKG update support device can calculate the version quantitative value based on the information on the risk of PKG or the source code.
(3) The PKG update support device can calculate the version quantitative value based on the security vulnerability of PKG or the number of operations of the source code.
(4) The PKG update support device can display the recommended version even for the user who avoids the latest version.
(5) The PKG update support device can promote the update to the recommended version by using the incentive evaluation value.
(6) The PKG update support device can promote updates within the cluster (do not update to an extremely new version).
(7) The PKG update support device can notify the user of the conditions regarding the risk tolerance of the recommended version.

The present invention is not limited to the above-described embodiment, and includes various modifications. For example, the above-described embodiment has been described in detail in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to the one including all the configurations described. Further, it is possible to replace a part of the configuration of one embodiment with the configuration of another embodiment, and it is also possible to add the configuration of another embodiment to the configuration of one embodiment. Further, it is possible to add / delete / replace a part of the configuration of each embodiment with another configuration.

Further, each of the above-mentioned configurations, functions, processing units, processing means and the like may be realized by hardware by designing a part or all of them by, for example, an integrated circuit. Further, each of the above configurations, functions, and the like may be realized by software by the processor interpreting and executing a program that realizes each function. Information such as programs, tables, and files that realize each function can be placed in a memory, a hard disk, a recording device such as an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.
In addition, control lines and information lines are shown as necessary for explanation, and not all control lines and information lines are shown in the product. In practice, it can be considered that almost all configurations are interconnected.

1 Software package (PKG) update support device 2 Network 3 Managed computer 4 Computer group 5 PKG distribution source 6 PKG risk information distribution source
7 Software Package (PKG)
11 Central control device 12 Input device 13 Output device 14 Main memory device 15 Auxiliary storage device 16 Communication device 21 Computer information acquisition department 22 Public information analysis department 23 Version analysis department 24 Performance map creation department 25 Incentive management department 26 Update recommended information creation department 27 Display processing unit 31 Computer group information 32 Computer information 33 PKG information 34 Achievement map 35 Update recommended information 36 Recommended reason Pattern information

Claims (9)

A map having a normalized continuous value as an axis showing the specifications of software packages that operate in cooperation with a computer, and a combination of a plurality of versions of the software packages described in the map are displayed.
Provided with a display processing unit that highlights the recommended version combination determined based on the number of achievements of the candidate among the combination candidates shown in the map.
A software package update support device featuring. Provided with a version analysis unit that calculates a normalized continuous value indicating the specification based on information on the risk of the version or information obtained from the source code.
The software package update support device according to claim 1. Information on the risks
Information about security vulnerabilities
The information obtained from the source code is
Information about the number of operations included in the source code,
The software package update support device according to claim 2. The display processing unit
If the user wants to update to a version other than the latest version, determine the version other than the latest version as the recommended version.
The software package update support device according to claim 3. Calculate the incentive evaluation value that shows the merit of updating to the recommended version,
Provided with an incentive management unit that assigns the calculated incentive evaluation value to the computer that has actually performed the update.
The software package update support device according to claim 4. It is provided with an achievement map creation unit that classifies the achievements into clusters in the space or plane of the map.
The display processing unit
If the user wants to update the version in the same cluster, determine the version that belongs to the same cluster as the current version as the recommended version.
The software package update support device according to claim 5. The display processing unit
Display the risk tolerance conditions of the recommended version along with the recommended version.
The software package update support device according to claim 6. The display processing unit of the software package update support device is
A map having a normalized continuous value as an axis showing the specifications of software packages that operate in cooperation with a computer, and a combination of a plurality of versions of the software packages described in the map are displayed.
To highlight the recommended version of the combination candidates shown in the map, which is determined based on the number of achievements of the candidate.
A software package update support method for a software package update support device. For the display processing unit of the software package update support device
A map having a normalized continuous value as an axis showing the specifications of software packages that operate in cooperation with a computer, and a combination of a plurality of versions of the software packages described in the map are displayed.
To execute the process of highlighting the recommended version combination determined based on the number of achievements of the candidate among the combination candidates shown in the map.
A software package update support program for operating the software package update support device.

Images