JPH06337777A - Software resource rearrangement system - Google Patents

Abstract

(57) [Summary] [Purpose] The unnecessary part of the existing source program and JCL is identified and automatically deleted from the history information of data input by the system user. [Structure] Related information of existing software is created in advance (201), and a history of data input by a system user is accumulated (202). Data input time series information is created from history information and software related information (203).
3 to 6 months until enough data is available for analysis,
The processing of steps 201 and 202 is repeated (10
4). Data input period information is created from the accumulated information (105), and based on this result, unnecessary portions are identified and deleted from the relation between the data items in the existing software and the input period information (106). [Effect] It is possible to reduce the amount of maintenance work and improve the quality of work.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a computer support for maintenance work of a corporate information processing system, and in particular, selection of unnecessary software, improvement of efficiency of maintenance work of existing software, effective use of storage device, system performance improvement. The present invention relates to a software asset consolidation method suitable for use for improvement.

[0002]

2. Description of the Related Art Generally, maintenance work of a corporate information processing system is carried out by a system developer or a system operator different from the system user. For this reason,
When performing the system modification work, the worker should grasp the system usage characteristics such as the usage pattern and usage frequency of the system by multiple users and the user's request before carrying out the system modification work. I need to put it.

On the other hand, as a conventional technique related to software asset organization, the components of a corporate information processing system and the configuration rules of the components are prepared in advance, the contents of the components and the relationships between the components are analyzed, and the software components are analyzed based on the results. Is used as a suitable method for streamlining system maintenance work.

As a method of organizing software assets according to this type of conventional technology, (a) a numerical evaluation of the complexity and redundancy of existing software is performed, and an operator organizes software assets based on the evaluation result. How to do, (b)
A method of changing the expression format from existing software to generate specifications, and a worker organizing software assets based on the specifications, (c) Consistency maintenance rule between elements that make up existing software assets A method of automatically organizing software assets based on the change history that has been defined and recorded, and (d) analysis of the contents of existing software, and the possibility that changes to existing software may affect There is known a method of extracting a certain portion of the existing software and organizing existing software assets based on the result.

As a conventional technique of this kind, for example,
"Information Processing Research Report 93-IS-4" published by Information Processing Society of Japan
2) etc. are known, especially (C)
“SMART system”, and “RESCUE” (d) are described as advanced technologies.

[0006]

However, the above-described method according to the prior art cannot reflect the usage characteristics of the user of the system, which is the basis of the deletion and modification of software, when performing maintenance work. However, it has the following problems.

The method (a) evaluates the complexity and the redundancy, but the complexity and the redundancy of software cannot reflect the usage characteristics of the system. The method (b) requires the operator to extract the characteristics of the user. Method (c) requires the characteristics of the user to be expressed in terms of consistency retention rules. In the method (d), the characteristics of the user who can be extracted are limited to the processing for the data item, the execution order of the program, and the like.

[0008] Therefore, in the conventional techniques for applying these methods to organize the software, it is necessary for the maintenance worker to separately examine the information regarding the usage characteristics to determine whether the software should be deleted or changed. Since the extraction of the user's usage characteristic information and the modification and modification of the existing software are carried out separately, the following problems occur.

That is, in the above-mentioned prior art, it is not possible to determine which part of each piece of software is necessary only by analyzing the existing software, so it is necessary to investigate the characteristics of the system user. In addition, this causes a problem that the investigated usage characteristics and the actual usage status of the system in operation are different, which may cause a correction work based on an incorrect judgment. Further, the above-mentioned conventional technique has a problem that an operation for specifying which part of a software element such as a program or a job control statement is necessary or unnecessary from the usage information is generated. .

For this reason, the above-mentioned conventional technique does not have a sufficient function as a method for organizing assets in a corporate information processing system.

The object of the present invention is to solve the above-mentioned problems of the prior art, and to use the existing software in existing software based on the usage information of the system user at the stage of operation and maintenance of the corporate information system. It is to provide a software asset consolidation method capable of identifying a part that does not exist and deleting or correcting the part.

Another object of the present invention is to use the system user's usage information and the result of modification based on the usage information.
It is to provide a software asset consolidation method capable of dividing and relocating existing software assets.

[0013]

According to the present invention, the object is to previously create and store software component related information related to a data item in existing software,
Data item usage information is created and stored based on the data input by the use of the system and the software component-related information, and the stored data item usage information is analyzed and the input data is cycled. By calculating the data item usage rate and analyzing the data items used in the existing software assets related to the data item usage rate, the unused programs and job control statements in the software assets are extracted. This is achieved by deleting it.

Further, the purpose is to calculate the above-mentioned data item utilization rate, and then input / output relationships of files used in existing programs, existing job control statements, data items used in files, data in programs. Relationship between items,
It is also achieved by analyzing the usage rate of data items and dividing and rearranging existing software.

[0015]

According to the present invention, the data input by the user of the corporate information processing system from the terminal device is temporarily stored, and the stored input data is a software component related to the data item in the existing software. It is stored as usage information for each data item for a certain period of time using a correspondence table for each data item, and further related information generated by analyzing the relationship between data items in the existing software and each of the accumulated information for a certain period of time. From the information obtained by analyzing the usage information for each data item for each cycle input from the terminal, the unused programs and job control statements in the existing software assets are specified and deleted.

According to the present invention, as described above, the information input by the user of the system is processed and accumulated for a certain period of time.
Since it is possible to analyze by the cycle of the information input from the terminal, the result makes it easy to identify the programs and job control language in the existing software that the user is not using, and It can be deleted and modified automatically.

Further, according to the present invention, the data input by the user of the corporate information processing system from the terminal device is temporarily stored, and the stored input data is stored in the software related to the data item in the existing software. Data is stored for a certain period of time as usage information for each data item using a correspondence table between components, and further, programs in existing software, file input / output relationships used in job control statements, and data used in files. Existing files are divided and rearranged based on items, related information that analyzes the relationship between data items in the program, and utilization information of the data items calculated for each input cycle from the terminal device of the stored information. , The related programs and job control statements are corrected based on the relocated files and the information related to the previous term.

According to the present invention, as described above, the information input by the system user is processed and the information accumulated for a certain period is
Since it can be analyzed according to the cycle of the information input from the terminal, the result can automatically divide the existing file into a part with high usage frequency and a part with low usage frequency,
Furthermore, existing programs and job control statements can be automatically corrected based on the division result based on the related information.

[0019]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the software asset management system according to the present invention will be described in detail below with reference to the drawings.

FIG. 1 is a block diagram showing a system configuration of an embodiment of the present invention, and FIG. 2 is a flow chart for explaining a processing procedure of software asset arrangement according to an embodiment of the present invention.
FIG. 3 is a flowchart for explaining the input history information creation process, FIG. 4 is a diagram for explaining the input history information format, FIG. 5 is a flowchart for explaining the data input time series information creation process, and FIGS. The figure which shows the example of the software component related information produced from software, FIG. 14 is a flowchart explaining the production process of data input period information,
FIG. 15 is a diagram showing an example of data item usage information, FIG. 16 is a flowchart for explaining an unnecessary portion correction process, FIG. 17 is a diagram showing an example of a pre-correction program and a post-correction program which are software asset rearrangement targets, and FIG. FIG. 4 is a diagram showing an example of existing software including JCL to be modified.
In FIG. 1, 101 is a CPU, 102 is a memory, and 10
3 is a terminal device, 104 is a printer, 105 is an input history information file, 106 is a software component related information file, 107 is an existing software asset file, 10
Reference numeral 8 is a data item utilization information parts file, and 109 is a rearranged software file.

As shown in FIG. 1, a company information system according to one embodiment of the present invention includes a CPU 101 that sequentially performs processing based on a program, and a software asset rearrangement process according to one embodiment of the present invention described with reference to FIG. It has a memory 102 storing a program for realizing the procedure, a keyboard and a display screen, for a user of a corporate information system to input data, and a system maintenance worker's instruction for organizing software assets and software assets. An interactive terminal device 103 used for giving a new name after analysis, and a printer 10 for outputting the result
4, a file 105 for holding history information of electronic messages input from the terminal device 103, a file 106 for holding related information between elements constituting software assets to be organized, and existing software assets stored. File 107, a file 108 storing data item usage information indicating in which data item the input data is used, and a rearranged software asset file 109 storing software assets rearranged by the present invention.
It is composed of and.

The system shown in FIG. 1 is used by a user on a daily basis together with business files (not shown).
Then, each time the system is used, the information for organizing software assets according to the embodiment of the present invention described with reference to FIG. 2 is accumulated. The operation of accumulating information for organizing software assets will be described below with reference to FIG.

(1) The CPU 101 reads a program for executing the procedure shown in FIG. 2 from the memory 102 and executes it. That is, the CPU 101 has previously created the file 1 before collecting the information for organizing the software.
A program to be organized stored in 07, for example, C shown as an uncorrected program 1701 in FIG.
OBOL source program, job control statement (hereinafter referred to as JCL) that defines the execution procedure of the program, and software component related information that represents the relationship between the software elements that configure the asset from the software asset that is composed of the file entity Is created and the created information is stored in the software component related information file 106 (step 201).

The software component related information is a data item / record correspondence information (see FIG. 7) showing the correspondence between the record definition statement and the data item in the source program, and a data item attribute holding the type information of the data item. Information (see FIG. 8), equivalence data item information (see FIG. 9) representing a set of data items having the same value held by one data item (hereinafter referred to as equivalence data item), and records in the program Alternatively, record attribute information (see FIG. 10) that holds information such as data items that make up the table, related files, and data items, program processing types, related records, files in the storage device, and JC.
Program attribute information (see FIG. 11) that holds information such as L, file type information (see FIG. 12) having information about the type of file in the storage device, related records, and volumes, and a program related to JCL, JCL attribute information having information about software components such as files in the storage device and the processing cycle of the job (see FIG. 13).
(Refer to FIG. 6), a record definition statement associated with the type of input data input from the terminal device 103, and an input message / record correspondence information (see FIG. 6) holding the correspondence between programs. .

In the above, a method of creating a correspondence relationship between data items and record definition statements, an equivalence data item set, a record definition statement and a program, JCL, and a file in a storage device is known from existing software assets. For example, it is described as "software standardization method" in Japanese Patent Laid-Open No. 2-94925. Further, the record definition statement related to the input message, the correspondence information of the program, the processing cycle of the program, and the processing cycle of JCL are created in advance by the maintenance worker and stored in the software component related information file 106. And

(2) When the system is used after the above-described processing is performed in advance and the software component related information is created and stored in the file 106, the CPU 101
Data input from the terminal device 103 is analyzed to create input history information (step 202).

(3) This process is executed according to the flow shown in FIG. That is, the CPU 101 checks whether or not the system is in operation, and if the system is in operation, the terminal device 1 is operated by the user of the company information system.
The data input from 03 is acquired (step 30
0, 301).

(4) The acquired input data is edited in the format shown in FIG. 4 and stored in the input history information file 105 as input history information. At this time, the CPU 101 collects the input data as the input data 404 and adds the control information 401 such as the input date and time, the beginning and end of the input data, the length 402 of the input data, and the type of the input data as the message type 403. Create input history information. This operation is performed from the system start to the system end, and input history information for each time is accumulated (step 302).

(5) Next, data input time-series information is created from the input history information created and accumulated by the above-described processing (step 203).

(6) This processing is executed according to the flow shown in FIG. 5, that is, the CPU 101 first determines whether or not the input history information is stored in the input history information file 105, and the input history information is stored. If the information is not stored, the data input time-series information creation process is terminated, and if the input history information is stored, one input history information is acquired (steps 501 and 502).

(7) It is determined whether the length 402 of the input history information acquired in step 502 is not "0",
If it is "0", the process returns to step 501 to repeat the process for the next input history information. If it is not "0", the process of dividing the input data 404 and associating with the data item is performed (steps 503 and 504). .

The process of step 504 is performed when the value of the message type 403 of the history information created in the format shown in FIG. 4 is "1" as shown as 601 in FIG. This is a process for deriving a corresponding record name INPUT-DATA shown as 602 from the input message / record correspondence information in the software component related information shown in FIG. 6 which has already been created.

Further, in the processing of step 504,
From the record attribute information shown in FIG. 10, a data item name 1002 that constitutes a record corresponding to the record name INPUT-DATA (shown as 1001 in FIG. 10) derived above is determined, and the result is used to The length 80 of each data item 801 from the data item attribute information shown in FIG.
Get 2. Then, the input data 404 is
It is divided according to the length of the data items forming the record obtained above, and is associated with the individual data items forming the record.

(8) Next, using the data item attribute information shown in FIG. 8, from the data attribute correspondence information and individual data items, the type 803 and initial value 804 of the corresponding data item.
And are searched to determine whether or not data has been input by the user of the information system in the area of the associated input data. And, the length of the area is less than the length of the data item, and the value that does not match the range of the data item type is entered.
Alternatively, in the case of the initial value, it is determined that the data item is empty. If the area is not empty, it is considered that data has been input to the data item, it is determined that the data item has been used, the input date is extracted from the control information 401 of the input history information, and the corresponding data item of the data item usage information The value of the corresponding day of the data input time series information (the number of times of inputting the data input on that day) is increased (step 50).
6, 507).

(9) The processes of steps 506 and 507 are repeatedly executed for all the data items constituting the record, the created data input time series information is accumulated in the data use information file 108, and after the repetition process is completed, the step The processing from 501 is repeatedly executed (step 50).
5).

The data input time-series information of the data item usage information obtained by the process of step 507 is created as the number of times of use for each data item name on a daily basis, as shown in the upper part of FIG.

(10) Next, moving to the flow of FIG. 2, it is judged whether or not sufficient data usage information has been accumulated to judge whether or not the data item is used (step 204).

The above-described processing of steps 202 to 204 is executed every time the system is used, for example, for 3 months to 6 months until sufficient information is accumulated, and sufficient utilization information is accumulated. The maintenance worker selects the maximum input cycle from the program processing cycle and the batch processing cycle of the existing software asset, and the data input cycle information for multiple times is the criterion for judging whether the accumulated information is sufficient. It is given as a set value in advance so that it can be collected.

(11) If sufficient information has been accumulated for the determination of asset rearrangement by the above-mentioned processing, processing for creating data item input cycle information of data item usage information is performed (step 205).

(12) This process is executed according to the flow shown in FIG. That is, first, it is determined whether or not the data item input time series information exists in the data item usage information file 108, and if it exists, one data item input time series information is acquired (steps 1401 and 140).
2).

(13) The acquired input time series information is converted into data item usage information for each input cycle, and the information created by the conversion is stored in the data item usage information file 108. A method for converting the time-series numerical information described here into numerical information for each period is well known, and a widely known method is, for example, Fast Fourier Transform (FFT). .152 "or the like (step 1403).

The data input cycle information is represented by the input cycle and the number of times of use of each data item, as shown in the middle part of FIG.

(14) When the processes of steps 1402 and 1403 are repeatedly executed and all the data item input time series information in the data item file is converted into the data item usage information for each input cycle, the determination of step 1401 If it is determined that there is no input time-series information, then it is checked whether or not the data item input period information exists, and if it does not exist,
The process ends (step 1404).

(15) When the data item input period information is present in step 1404, in order to check the accuracy of the data input period information, the data input period correlation degree which is the information showing the correlation between the plurality of data input period information. Information is created and the created correlation information is stored in the data item usage information file 108. A method for calculating the correlation between a plurality of numerical data is known, and is described as a correlation coefficient in, for example, “Computer Software Encyclopedia, P.42” (step 1405).

An example of the created data input period creation information is shown in the lower part of FIG.

(16) Next, returning to the process of FIG. 2, the unnecessary portion of the existing software is corrected (step 206).

(17) This process is executed according to the flow shown in FIG. That is, first, it is determined whether or not the existing software asset file 107 contains the software asset to be modified, and if not, the process ends. (Step 1601).

(18) If it is determined in step 1601 that there is a software asset to be modified, the type of the software asset to be modified is checked (step 1602).

(19) In step 1602, for example, when it is determined that the software asset to be modified is a COBOL source program shown as 1701 in FIG. 17, the analysis target data item is selected. Specifically, the source program 1701 is analyzed and the program name PGM002 shown as 1703 is extracted. Then, from this program name PGM002 and the program attribute information shown in FIG. 11, as shown by 1101 in FIG. 11, the program processing type is B batch, the processing cycle is 20 days, and the related record is INPUT-D.
It is determined to be ATA. Further, the related data item name 1002 is extracted from the record attribute information shown in FIG. 10, and the data item use information shown in FIG. 15 is searched using the data item name as a key to retrieve the data item name SYOHIN-NA.
The ME and SYOIN-VALUE 1501 are acquired (step 1603).

(20) Next, it is determined whether or not the data item is used. That is, S, which is the data item acquired above
The data input cycle information 1502 and the data input cycle correlation information 1503 of YOHIN-NAME and SYOHIN-VALUE are acquired, and the sum of the input cycle information is calculated. If the sum is "0", or in the processing cycle of the program, On the other hand, if there are inconsistencies in the usage cycle of data items,
It is determined that the data item is not used. For example, for the program processing cycle of 20 days (1101),
If the peak usage cycle is 60 days, it is determined that there is a contradiction. Then, when there is the above-mentioned contradiction and the degree of correlation 1504 is high, the data item name SYOH
IN-NAME and SYOIN-VALUE are used by other software resources, and it is determined that the software resources targeted for rearranging this time are unnecessary. The threshold value for determining that the degree of correlation is high is given in advance as a set value by the maintenance worker (step 1604).

(21) In step 1604, if there is no contradiction between the processing cycle and the input cycle, the processing is terminated, and if there is a contradiction, then the source code portion related to the unnecessary data item is deleted. That is, the source program 1701
Of unnecessary data item name SYOH in the program
Search for sentences 1705 and 1706 that transfer the values of IN-NAME and SYOHIN-VALUE, select a sentence whose transfer source is composed only of unnecessary data items, and delete the corresponding sentence, sentence 1706 in this example (1710). To do. Statement 1 in which there are data items other than unnecessary data items at the transfer source
If the transfer source is composed of two or more data items, 705 deletes the unnecessary data item and converts the value of the remaining data item into a statement to move to the transfer destination (1706).

Further, the equivalent data items for the unnecessary data items are represented by the data item attribute information shown in FIGS. 8 and 9, and
Equivalence data item information is obtained by searching the equivalence data item information 805 in FIG. 8 and 901 and 902 in FIG.
The same rule is applied to No. 2 to delete the unnecessary source code part (1711).

Next, unnecessary data item SYOHIN-NAME from the data item / record correspondence information shown in FIG.
The program name and record name related to SYOHIN-VALUE are retrieved to obtain the program name and record name shown as 701 in FIG. 7, and the source code portion 1704 in the related unnecessary program is deleted (1708). Finally, the unnecessary part of the record definition is deleted (step 1605).

(22) In step 1602, for example, when the software asset to be modified is JCL, the input file is analyzed. Specifically, JCL1801 as shown in FIG. 18 is analyzed, and the job name in the JCL is J
The CL name 1802 is extracted. The JCL attribute information shown in FIG. 13 is searched by the extracted JCL name, and
The associated file name and program name shown as 01 are extracted. Next, the source program with the program name extracted from the existing software assets is searched, and the file allocation name (DD name) 1803 and COB in the JCL is searched.
The input / output section of the file name in the JCL is analyzed from the correspondence relationship between the file allocation names of the OL source program. This analysis method is publicly known, and is disclosed in, for example, JP-A-2-9
It is described as a "software standardization method" in Japanese Patent No. 4925.

Then, the file name DAT extracted above
The record format of ASET2 is extracted as 1201 from the file attribute information shown in FIG. A data item SY that constitutes a record using the record attribute information shown in FIG. 10 from the extracted record name SYOIN-DATA.
OHIN-NAME, SYOIN-VALUE 1
003 and 1004 (step 160)
6).

(23) Next, input file use cycle information is created. That is, in this example, the data items SYOHIN-NAME, SYOHIN-V that make up the record
The usage cycle of ALUE is 60 days as shown as 1504 in FIG. 15, and the processing cycle of JCL is as shown in FIG.
3 is a monthly process as indicated by 1301 (step 1607).

(24) Further, as described in step 1604 above, it is determined whether or not there is a contradiction between the processing cycle and the input cycle. Delete and correct unnecessary JCL parts. In the case of this example, the file DATAS in the JCL is calculated from the correspondence between the JCL and the file allocation name in the program.
When ET2 (1804) is an input, JCL1801
Is determined to be unnecessary and is deleted from the existing software asset 1701 of FIG. 17 (steps 1608 and 160).
9).

By the above-mentioned processing, FIG.
The pre-correction program 1071 shown in FIG. 7 can be organized as shown in the post-correction program 1702.

According to the above-mentioned embodiment of the present invention, when the unnecessary assets are sorted out from the existing software assets, the frequency of data input by the user of the enterprise information system is set to the data item related to the input data. Automatically identify the unused part of the program by associating with
Since unnecessary parts can be deleted, maintenance work can be performed without the need for maintenance personnel to modify the software.

Further, according to one embodiment of the present invention, since unnecessary existing software can be specified from the frequency of data input by the user of the company information system, a correction error due to a mistake made by the maintenance worker. Since it does not occur, it is possible to improve the work quality of the correction work.

In the above-described embodiment of the present invention, the information input by the user of the system is processed and the information accumulated for a certain period of time is analyzed according to the cycle of the information input from the terminal. Although the program and the job control language in the existing software that are not used by the above are specified and the unnecessary portions are automatically deleted, after the analysis, the present invention provides a program and a job control statement in the existing software. Input / output relations of files to be used, data items used in files, related information obtained by analyzing relations between data items in programs, and use of data items calculated from the terminal device for accumulated information Based on the rate information, the existing file is divided and relocated, and the related program and job control statement are corrected based on the relocated file and the related information of the previous term. It is possible.

By doing so, the information input by the user of the system can be processed and the information accumulated for a certain period can be analyzed by the cycle of the information input from the terminal. It is possible to automatically divide a file into a high-use portion and a low-use portion, and it is possible to automatically modify an existing program or job control statement based on the division result based on the related information.

[0063]

As described above, according to the present invention,
At the stage of operation and maintenance of the corporate information system, it is possible to identify the unused part of the existing software based on the usage information of the system user and correct the part. And existing software assets can be divided and rearranged based on the correction result by the usage information.

[Brief description of drawings]

FIG. 1 is a block diagram showing a system configuration of an embodiment of the present invention.

FIG. 2 is a flowchart illustrating a processing procedure for software asset consolidation according to an embodiment of the present invention.

FIG. 3 is a flowchart illustrating a process of creating input history information.

FIG. 4 is a diagram illustrating a format of input history information.

FIG. 5 is a flowchart illustrating a process of creating data input time series information.

FIG. 6 is a diagram showing an example of input message / record correspondence information which is software component related information.

FIG. 7 is a diagram showing an example of data item / record correspondence information which is software component related information.

FIG. 8 is a diagram showing an example of data item attribute information which is software component related information.

FIG. 9 is a diagram showing an example of equivalent data item information which is software component related information.

FIG. 10 is a diagram showing an example of record attribute information which is software component related information.

FIG. 11 is a diagram showing an example of program attribute information which is software component related information.

FIG. 12 is a diagram showing an example of file attribute information which is software component related information.

FIG. 13 is a JCL that is software component related information.
It is a figure which shows the example of attribute information.

FIG. 14 is a flowchart illustrating a process of creating data input cycle information.

FIG. 15 is a diagram showing an example of data item usage information.

FIG. 16 is a flowchart illustrating a correction process of an unnecessary portion.

FIG. 17 is a diagram illustrating an example of a pre-correction program and a post-correction program that are software asset rearrangement targets.

FIG. 18 is a diagram showing an example of existing software including JCL to be modified.

[Explanation of symbols]

 101 CPU 102 Memory 103 Terminal Device 104 Printer 105 Input History Information File 106 Software Component Related Information File 107 Existing Software Asset File 108 Data Item Usage Information Parts File 109 Rearranged Software File

Claims (2)

[Claims] 1. In a software asset rearrangement method for identifying an unused part of existing software and correcting it, software component related information related to a data item in the existing software is created and stored in advance. Every time, data item usage information is created and stored based on the data input by using the system and the software component-related information, and the input data is obtained by analyzing the stored data item usage information. By calculating the data item usage rate for each cycle and analyzing the data items used in the existing software assets related to the data item usage rate, the unused program and job control statements in the existing software assets are analyzed. A software asset consolidation method characterized by extracting and deleting. 2. In a software asset rearrangement method for identifying an unused portion of existing software and correcting it, software component related information relating to a data item in the existing software is created and stored in advance. Every time, data item usage information is created and stored based on the data input by using the system and the software component-related information, and the input data is obtained by analyzing the stored data item usage information. The data item usage rate is calculated for each cycle, and the input / output relationships of files used in existing programs and existing job control statements, data items used in files, relationships between data items in programs, and data A software asset consolidation method that analyzes the usage rate of items and divides and rearranges existing software.