JPH09106343A - Maintenance controlling method for software resources - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve the efficiency of a maintenance control work by effectively reusing the analysis information (= maintenance information) determined for pertinent software resources before, regarding the maintenance controlling method for software resources. SOLUTION: When a large quantity of analysis information can be obtained once, the analysis information (= maintenance information) is divided into some parts and a maintenance control work is performed by using each of the parts. When the analysis information for every program can be obtained, each information is integrated into one and the maintenance control work is performed. By flexibly reusing the existing analysis information obtained individually by the analysis of the program composing software resources without being thrown away, the efficiency of the maintenance control works such as the standardization of a data item and the influence range investigation at the time of the change can be improved.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software resource maintenance management method, and more particularly, to the standardization work of the names and attributes of data items described in software resources, and the work of specifying the range of influence due to the change of description contents. The present invention relates to a data-centered approach to software resource maintenance management method for effectively reusing maintenance information about the corresponding software resource.

[0002]

2. Description of the Related Art Generally, when a naming rule is not strictly adhered to when software is created, or when a name is repeatedly changed, a plurality of different names are assigned to one data item having the same role in the software. A synonymous tag name is assigned, and it often becomes very difficult to understand when performing maintenance. Therefore, when it becomes necessary to make further changes to such incomprehensible software, the maintenance staff must spend a great deal of effort to understand the software prior to all other tasks. In particular, in the work of specifying the range of influence of the software change, there is always a risk of degrading from the current state due to the change, and thus the responsibility and the burden on the maintenance worker become heavy.

Conventionally, two types of methods have been proposed to reduce the burden on maintenance workers in such software modification work. Method (JP-A-3-29492)
In the "software standardization method" described in Japanese Patent Publication No. 5), among the analysis information obtained by analyzing each program constituting the software, after obtaining a set of data items having synonymous relations and accumulating them as related information, By replacing the entire set of synonymous data items with standard names and attributes, an attempt is made to make the software easier to understand. Also, the method (“Software standardization method” described in Japanese Patent Laid-Open No. 6-131164) uses the synonymous relationship between data items similarly to the method, but a system consisting of large-scale software resources is subject to maintenance management. Instead of analyzing the entire system at once, it is divided into several subsystems each containing a common program, and after obtaining the related information of the data item from the analysis information obtained by analyzing the program for each subsystem By gradually integrating subsystems using data items in a common program as keys, the names and attributes of data items in the entire system are finally replaced with standard names and attributes.

[0004]

In the above-mentioned conventional method, when the amount of analysis information obtained by analyzing the individual programs constituting the software resource reaches a huge amount, the reason for the processing performance of the maintenance work system or the like is increased. Therefore, there is a problem in that the efficiency of maintenance work may be reduced. Then, in order to avoid such a decrease in efficiency, if another method is used to obtain data items having a synonymous relationship, all the analysis information obtained in the previous analysis will have to be discarded in vain. There was a problem that the initial maintenance work was not always achieved. In addition, when analyzing the configuration program for each subsystem obtained by dividing and obtaining the related information between data items, these are collectively reused as related information for maintenance work of the entire system. There was a problem that it could not be done.

An object of the present invention is to solve the above problems and flexibly reuse existing analysis information individually obtained by analysis of programs constituting software resources without discarding the maintenance management work. It is to provide a method of maintaining and managing software resources that can improve the efficiency of software.

[0006]

In order to achieve the above object, the method for maintaining and managing software resources according to the present invention provides data created by paying attention to access to data items defined in software resources. In the maintenance management method of the software resource of the data-centric approach type, which performs the maintenance management for the software resource by using the related information representing the synonymous relationship between items, the existing maintenance information about the system composed of various software resources is added. Based on the included related information, the connection part and the state of the other software resource by the related information are obtained for each software resource, and the related information at the connection part with the specific software resource is separated. The above maintenance information is divided into subsystems, and each subsystem is It is obtained to perform the maintenance with the relevant information.

[0007] Alternatively, data for performing maintenance management on the software resource by using related information indicating synonymous synonyms between the data items created by paying attention to access to the data item defined in the software resource. In the central approach type software resource maintenance management method, a new correspondence corresponding to the association is added to the related information included in the existing maintenance information created separately for each of the plurality of subsystems having the association. By additionally setting related information as a connection unit, all maintenance information is integrated into maintenance information for one system, and maintenance management is performed using the related information included in the integrated maintenance information. It is the one.

With the above configuration, even if the efficiency of the maintenance work is reduced due to performance reasons due to the huge amount of analysis information, the analysis work has already been created without redoing it. The analysis information (= maintenance information) can be reused flexibly without being discarded. Further, it is possible to reduce the data amount of the analysis information that is the target of the maintenance management work at a time by dividing, and prevent the deterioration of the processing performance due to the data amount. Further, even when analysis information is created separately for each of a plurality of systems, the created analysis information that has been saved can be collected and reused without restarting the analysis work. Furthermore, by organically integrating a plurality of sets of analysis information into one piece of analysis information, waste can be reduced and a mechanically processable range can be expanded as compared with a case where there are a plurality of work targets. As described above, it is possible to improve the efficiency of maintenance work by flexibly reusing the existing analysis information individually obtained by the analysis of the programs constituting the software resources without discarding it.

[0009]

BEST MODE FOR CARRYING OUT THE INVENTION An embodiment of a software resource maintenance management method of the present invention will be described in detail below with reference to the drawings.

FIG. 1 is a diagram showing an example of a hardware configuration of a system for realizing a software resource maintenance management method of the present invention. In the figure, 11 is a CPU that performs overall control of the entire system, 12 is a memory necessary for the operation of the CPU, 13 is an input device for the user to perform necessary input operations, and 14 is a display for displaying processing results and the like. An apparatus, 15 is a printer that also prints out the processing result, and 16 is an external storage device that stores software resources to be processed and analysis information obtained as the processing result.

FIG. 2 is a flow chart showing the flow of processing in the case of dividing the analysis information of the software resources collectively created by the system of FIG. 1, and the maintenance management initially stored in the external storage device 16. The software resource to be processed is read and a predetermined analysis process is performed (step 201).

FIG. 3 is a diagram (part 1) showing an example of a specific software resource which is the target of the processing of FIG. In the job control indicated by reference numeral 310 in the figure, for example, when the program "P1" (reference numeral 311) accesses the data set "DSN1" (reference numeral 313a), the assigned name is "FI".
LE1 ”(reference numeral 312) is defined. Further, in the actual program“ P1 ”(311a) controlled by the job control 310, the logical file name is“ file 1 ”(reference numeral 314). In addition, regarding the data definition at the time of file access, the data item name of “01” level is “RECORD-1” (reference numeral 315) and the data item of the subordinate “05” level is “DATA-1” ( Similarly, in the job control indicated by reference numeral 320, the program “P2” (reference numeral 321) is the data set “DSN1” (reference numeral 3).
The assigned name when accessing 13b) is "FILE
2 "(reference numeral 322) is defined and the actual program" P2 "controlled by the job control 320
In (321a), the logical file name is set to "file 2" (reference numeral 324), and regarding the data definition at the time of file access, the data item name of "01" level is set to "RECORD-2" (reference numeral 325). And the subordinate “0
The data item of the 5 "level is" DATA-2 "(reference numeral 326).
, Respectively.

In the software resource of FIG. 3 described above, the data item "RE" in the program "P1" (311a)
CORD-1 ”(315) and program“ P2 ”(321
a) data item “RECORD-2” (325) in the program “P1” (311a) data item “DATA-1” (3)
16) and the data item "DATA-2" (reference numeral 326) in the program "P2" (321a) are both areas used for accessing the same data set "DSN1" (reference numeral 313). Such a relationship is called a "synonymous relationship with the same file", and related information is created based on this relationship.

FIG. 4 is a diagram (part 2) showing an example of a concrete software resource which is the target of the processing of FIG. 2, and the program "P1" shown by reference numeral 410 is the argument "shown by reference numeral 411a". DATA-3 "(reference numeral 411a) and reference numeral 4
An example of calling the subprogram “P2” shown by 20 will be shown. In the figure, in the program "P1" (410), the content of the data item "DATA-3" is transferred to another data item "DATA-5" (reference numerals 411b, 412a). In the subprogram “P2” (420), the argument “DA” on the receiving side is
The content of "TA-4" is transferred to another data item "DATA-6" (reference numerals 421b and 422a).

In the software resource of FIG. 4 described above, the data item "DATA" in the program "P1" (410).
-3 "(411) and subprogram" P2 "(420)
The data item “DATA-4” (421) in the above is an area used to transfer the same contents between programs, so such a relationship is “synonymous relationship by CALL relationship”.
Call. In addition, the data item “DATA-3” (411b) and the data item “DATA-” in the program “P1” (410).
5 "(412a) and subprogram" P2 "(420)
Since the data item “DATA-4” (421b) and the data item “DATA-6” (422a) in the above are both used for transferring the contents of the data item in the same program, such a relation “Synonymous relationship by MOVE relationship”
Call. Then, the related information is created based on these relationships. The above is the creation of related information (step 202) in the flowchart of FIG.

FIG. 5 is a diagram showing an example of related information included in the software resource analysis information. In the same figure, the respective related information created based on FIG. 3 and FIG. 4 are the program name 51 and the data item name 52 as the source of the relationship, the program name 53 and the data item name 5 as the other party of the relationship.
4, and is stored in the related information table 50, classified into 55 of types of relationships indicating the existence reasons of synonymous relationships. In the related information table 50 of FIG. 5, rows 5a and 5b are shown in FIG.
From the software resources of FIG. 4, lines 5c and 4d are the related information respectively created from the software resources of FIG.

Such related information can be effectively used, for example, in the following maintenance management work. [Maintenance work A] When attempting to replace the name of the data item "DATA-3" in the program "P1" with a standard name determined based on a predetermined naming rule, the replacement is performed by tracing the above related information. Make a list of all required data items in advance. [Maintenance work B] When it is necessary to make some changes, such as increasing the area length of the data item "DATA-3" in the program "P1", the data items affected by this change and their data items The range of the program including is specified in advance.

The information obtained by the above-mentioned maintenance management operations A and B is information that is a really effective clue. Especially, the scale of the software resource to be maintained is large, and the person in charge of maintenance is not the creator of the software resource. If you are a skilled person, while you can expect immeasurable effects,
Generally, as the scale of software resources increases, the processing performance of the maintenance management work A and B described above decreases.

Therefore, as a method effective for avoiding such a decrease in processing performance, a method of dividing analysis information including related information will be sequentially described. Hereinafter, FIG.
The investigation / display processing of the connecting portion performed in step 203 therein will be described.

FIG. 6 is a diagram showing an example of the inspection conditions of the connecting portion set in the processing of FIG. In the figure, the item 610 indicating the purpose of the survey is set to “division” of two types of selection branches of “division” (reference numeral 611) and “integration” (reference numeral 612) (reference numeral 611a: "Yes").
The division number 620 is set to divide the original analysis information into two (reference numeral 620a: “2”). Division method 63
In 0, among three types of selection branches of “averaging analysis information amount” (reference numeral 631), “averaging disk capacity” (reference numeral 632), and “dividing by designated program” (reference numeral 633)
“Averaging of analysis information amount” is set (reference numeral 631)
a: “Yes”). As described above, in FIG. 6, the original analysis information (including related information) so that the analysis information amount is averaged.
The following shows an example in which it is set to divide into two.

FIG. 7 is a diagram showing an example of the result of the investigation of the connecting portion displayed during the processing of FIG. 2, in which the connecting portion between related information in the original analysis information and its state, and the condition set in FIG. The division result expected from (division condition) is shown. In the figure, 710 and 720 are division units respectively corresponding to the division number value (= 2) designated by the division condition. Reference numerals 711 to 714 are programs belonging to the division unit 710, and 711a and 711b are some of the data items used in the program 711. 721-
724 is a program belonging to the division unit 720,
21a and 724a are programs 721 and 72
4 are some of the data items used in 4. And 73
1, 732 are respectively placed between the data item 711a in the division unit 710 and the data item 721a in the division unit 720, and between the data item 711b in the division unit 710 and the data item 724a in the division unit 720, respectively. Related information. Further, 741 is the number of connections at the division points (= the number of related information = 2) in the case of the above-mentioned division condition, and 742 is detailed information about the related information of this connection portion. And 720 the amount of analysis information (= number of cases) 743a and disk occupancy 7
43b and numerical values are displayed respectively. The user selects the number of division points connected 741 displayed in the detailed information 742, the division point related information 742 (the related information contents 731a and 73).
2a), referring to information such as the state 743 after the division, it is determined whether the division is continued under the division condition or the division condition is reset.

In the above, if it is possible to continue the division under the displayed division conditions, the user:
The related information shown in steps 204 and 205 in FIG.
By separating the related information indicated by, the maintenance information that has been integrated into one as a whole can be semantically divided into two division units. After this process, the process of dividing the maintenance information semantically divided into two division units into separate files as necessary is steps 206 and 207 in FIG. Then, in step 208, as described above in step 202 (creation of related information),
A group of synonymous data items with related information as a key is created for the maintenance information for each division unit, and one standard name is given to these data items. Finally, in step 209, the original name of the data item in each program is replaced with the standard name given in step 208.

FIG. 8 is a flow chart of the processing when dividing the analysis information of the software resources collectively created by the system of FIG. 1 and investigating the range of influence caused by the change of the data items required therewith. It is a flowchart showing. In the figure, the contents of the processing in steps 801 to 807 are the same as the contents of the processing in steps 201 to 207 in FIG. 2, and therefore detailed description will be omitted. And
In the last step 808, a set of synonymous data items with related information as a key is created for the maintenance information for each division unit obtained by the processing up to step 807, and necessary changes are made to these data items. Investigate the range of impact when

FIG. 9 shows the flow of processing in the case where the analysis information of the software resources created separately in the system of FIG. 1 is integrated, and the range of influence caused by the change of the data items required therewith is investigated. It is a flow chart shown, and it is assumed that there is already maintenance information created individually by a user for each of a plurality of systems, and an attempt is made to collectively investigate the influence range of these plurality of maintenance information. In the figure, step 901 is a software resource analysis process, step 902 is a related information analysis process, and the processes performed in steps 201 and 202 in FIG. 2 except that there are a plurality of systems to be processed. Is the same as.
In steps 903 and 904, analysis information of a plurality of software resources, each managed as maintenance information, is moved to the same file as needed. In addition,
It is not necessary to perform this process for the analysis information originally recorded in the same file, and step 903.
Only the movement of the analysis information is performed in the processing of 904, and each analysis information is semantically completely independent. After that, in step 905, the investigation / display processing of the connecting portion is performed as in step 203 in FIG.

FIG. 10 is a diagram showing an example of the inspection conditions of the connecting portion set in the processing of FIG. In the figure, the item 1010 indicating the purpose of the survey is “division” (reference numeral 101
1) and “integration” (reference numeral 1012) of the two types of selection branches, “integration” is set (reference numeral 1012a: “Y”).
es "). Then, in the integration method 1040, it is set that the original analysis information should be integrated by a designated program (reference numeral 1041a:" P1 ").

FIG. 11 is a diagram showing an example of the survey result of the connecting portion displayed in the processing of FIG. 9, and the condition set in FIG. 10 (based on the analysis information individually obtained for each of a plurality of maintenance information). An integration result expected from (integration condition), a connection part between related information in the analysis information of the two systems immediately before being integrated, and the state thereof are shown (processing performed in step 905 in FIG. 9). In the figure, reference numeral 11
Reference numerals 10 and 1120 are systems before integration, reference numerals 1131 and 1132 are related information of a connecting portion that the user is about to additionally set, 1141 is detailed information about the related information of the connecting portion, and a state before and after integration 1142. As a numerical value, the amount (= the number of pieces) of analysis information 1142a and the disk occupancy 1142b in the integrated system 1150 with the systems 1110 and 1120 are numerically displayed. The user selects related information 1141 (content of related information 1) of the integration point displayed in the detailed information 1141.
131a and 1132a), state 1142 before and after integration
It is determined whether to continue the integration under this integration condition or to reset the integration condition again with reference to the information such as.

In the above, when the integration is continued under the displayed integration conditions, the user performs step 90 in FIG.
When the related information 1131 and 1132 is added to the analysis information by performing the additional setting of the related information indicated by 6 and 907, the maintenance information originally created separately for each of the plurality of systems is semantically changed. Are also organically connected and integrated into one maintenance information. Finally step 9
In 08, the effect of creating a set of synonymous data items with related information 1131 and 1132 as keys for new integrated maintenance information, and making necessary changes to these data items Examine the range.

FIG. 12 is a flow chart showing the flow of processing in the case where the analysis information of the software resources created separately in the system of FIG. 1 is integrated and the necessary data items are changed accordingly. In the figure, step 120
The contents of the processing in 1 to 1207 are step 9 in FIG.
Since the processing contents are the same as those in 01 to 907, detailed description thereof will be omitted. Then, in step 1208, a set of synonymous data items having related information as a key is created for the integrated maintenance information, and one standard name is given to these data items. Finally, in step 1209, the original name of the data item in each program is replaced with the standard name given in step 1208.

In the above-described embodiment, the information obtained by analyzing the software resource is described as analysis information, and the information used for maintenance management work of the software resource is described as maintenance information. The contents of analysis information and maintenance information are the same. The above-described embodiment is merely one specific example of the software resource maintenance management method of the present invention, and is not limited to this embodiment.

[0030]

As described above in detail, according to the software resource maintenance management method of the present invention, when a huge amount of analysis information is obtained at one time for all software resources, the analysis information (= maintenance) (Information) is divided into several parts, and then maintenance and management work is performed for each of them. Also, when analysis information is obtained for each program, these are integrated into one and then maintenance and management work is performed. Enables flexible reuse of existing analysis information individually obtained by analysis of programs that make up software resources without discarding it, and improves efficiency of maintenance management work such as standardization of data items and investigation of impact range at the time of change. The effect that it can be improved is obtained.

[Brief description of the drawings]

FIG. 1 is a diagram showing an example of a hardware configuration of a system that implements a software resource maintenance management method of the present invention.

FIG. 2 is a flowchart showing a processing flow when dividing analysis information of software resources created collectively by the system of FIG.

FIG. 3 is a diagram (part 1) showing an example of a specific software resource that is a target of the process of FIG. 2;

FIG. 4 is a diagram (part 2) showing an example of a specific software resource that is the target of the processing of FIG.

FIG. 5 is a diagram illustrating an example of related information included in software resource analysis information.

FIG. 6 is a diagram showing an example of a check condition of a connecting portion set in the process of FIG.

FIG. 7 is a diagram showing an example of a survey result of a connecting portion displayed during the processing of FIG.

8 is a flowchart showing the flow of processing in the case of dividing analysis information of software resources created collectively by the system of FIG. 1 and investigating the range of influence caused by the change of the data items required therewith. Is.

9 is a flowchart showing the flow of processing in the case of integrating analysis information of software resources created separately in the system of FIG. 1 and investigating the range of influence caused by the change of the data items required therewith. is there.

FIG. 10 is a diagram showing an example of the inspection conditions of the connecting portion set in the processing of FIG. 9.

FIG. 11 is a diagram showing an example of a survey result of a connecting portion displayed in the process of FIG. 9.

FIG. 12 is a flowchart showing the flow of processing in the case of integrating analysis information of software resources created separately in the system of FIG. 1 and changing the data items required accordingly.

[Explanation of symbols]

611a Analysis information investigation purpose setting (= division) 620a Analysis information division number setting (= 2) 631a Analysis information division method setting (= averaging analysis information amount) 710a, 720a Analysis information after division 731a, 732a Related information about connection part at the time of division 743a Amount of analysis information after division 743b Disk occupancy after division 1012a Setting of purpose of investigating analysis information (= integration) 1041a Setting of integration method of analysis information (= 1131a, 1132a Related information about connection part at the time of integration 1142a Amount of analysis information before and after integration 1142b Disk occupancy before and after integration 1150 State after integration

Claims (6)

[Claims] 1. A data center for performing maintenance management on a software resource using related information representing synonymous synonyms between data items created by focusing on access to data items defined in the software resource. In the approach-based software resource maintenance management method, based on the related information included in the existing maintenance information about the system configured from various software resources, the software resources are linked with other software resources for each individual software resource. Of the connection information and the state thereof according to the related information, and the maintenance information is divided into subsystems by separating the related information at the connection portion with a specific software resource, and the related information is used for each subsystem. Maintenance of software resources Management method. 2. A data center for performing maintenance management on the software resource using related information representing synonymous synonyms between data items created by focusing on access to data items defined in the software resource. In the approach-type software resource maintenance management method, a new association corresponding to the association is added to the association information included in the existing maintenance information created separately for each of the plurality of subsystems having the association. By additionally setting information as a connection unit, all maintenance information is integrated into maintenance information about one system, and maintenance management is performed using the related information included in the integrated maintenance information. A software resource maintenance management method characterized by the above. 3. The maintenance information is sub-divided so that the number of pieces of maintenance information belonging to each generated subsystem is averaged and the number of connecting parts required for separating the related information is minimized. The method for maintaining and managing software resources according to claim 1, wherein the method is divided into system units. 4. The maintenance information is sub-divided so that the capacity of the maintenance information belonging to each generated subsystem is averaged and the number of connecting parts required for separating the related information is minimized. The method for maintaining and managing software resources according to claim 1, wherein the method is divided into system units. 5. The software resource maintenance management method according to claim 1, wherein the maintenance information is divided into subsystems among designated arbitrary programs. 6. The data item used between arbitrary programs belonging to different subsystems, the specified related information is added and then integrated into maintenance information for one system. Item 2. A software resource maintenance management method according to item 2.