JPH086769A - Device and method for processing software resources arrangement - Google Patents

Abstract

PURPOSE:To arrange information by which the present situation can be recognized and to output it as an arrangement result by finding fundamental resource information relating to existing software resources and correlative resource information as the information of membership between software resources. CONSTITUTION:Descriptive language judging processing for the software resources is performed by using a content stored in a language keyword storage means 10, and resource title analysis processing is performed by using a content stored in a resource title analytic keyword storage means 11. A fundamental resource information intermediate table as a result of completion of the resource title analysis processing and the software resources are read in, and resource characteristic analysis processing is performed by using a content stored in a characteristic information analytic keyword storage means 12. A fundamental resource intermediate table as a result of completion of the resource characteristic analysis processing, the content of a correlative resource analytic keyword storage means 13 and the software resources are read in, and the correlative resource information intermediate table as an intermediate table for the final result of the correlative resource information representing the membership between the resources can be generated.

Description

Detailed Description of the Invention

[0001]

The present invention relates to the contents of assets as a criterion for grasping the current status of software assets such as programs and job control information in a computer system, organizing software assets, and performing necessary asset maintenance. And a software asset rearrangement processing device for providing rearrangement information indicating mutual relationships among assets.

[0002]

2. Description of the Related Art In recent years, computer systems have become a weapon for business strategies in companies, and software assets owned by companies have increased and become valuable assets. However, large-scale / complex software assets are in a state of confusion, and it cannot be said that this valuable property is managed efficiently. Therefore, it is necessary to grasp existing software assets, sort out confused software assets, and realize a well-organized / organized and comfortable maintenance environment.

As computer system software assets, job assets such as JCL (job control language), program assets such as COBOL, ADL (language defining AIM operating environment information as a comprehensive online database), ACS Environment definition objects such as (software that helps develop AIM application programs), PSA
There are screen / form definition objects such as M (assets for defining / creating screen and form formats), etc. When organizing these software assets, they are described in what language, It is necessary to take an appropriate measure by accurately ascertaining how they are related to each other, whether there is excess or deficiency in the mutual relationship, and whether the same asset name exists.

For this purpose, the asset information of the software assets to be organized is printed or displayed and output, and by analyzing them, the description language and the characteristic information are discriminated using the characteristic character strings as keywords, and each description is described. It is necessary to identify the asset name, asset type, asset characteristics, etc. by decoding the output content according to the language specifications.

[0005] In addition, by detecting calls to subroutines, procedures, copies, schemas, etc., the parent-child relationship between assets is determined, and information such as the number of times the called assets are used is displayed in a table format to organize software asset data. It will be created in a listable format, and will be used as a reference material for software assets.

[0006]

FIG. 49 shows a conventional example of a method for confirming the presence / absence of software assets. When the process is started in the figure, the contents of the software asset designated in step S1 are analyzed first, the correlated asset is detected in step S2, and the presence or absence of the correlated asset is checked by searching the library in step S3. And the information is output.

FIG. 50 shows an example of checking the existence of software assets according to the prior art. In the figure, it is assumed that there is a software asset group 4 including program assets 5, 6, and 7. In the method described in FIG. 49, first, the method described in FIG. 49 is applied to the program asset 5 (asset name: A), and the correlated software asset 6 (asset name:
It is confirmed that there is B).

Next, the processing of FIG. 49 is applied to the program asset 6, and it is detected that the correlated asset C exists and the correlated asset D does not exist. Similarly, the same processing is performed for the program asset 7 (asset name; C), and the shortage of the correlated asset D is detected.

However, in the conventional method as described with reference to FIG. 49, in order to search for correlated software assets each time, particularly when a large amount of software assets must be analyzed, for example, FIG. There is a possibility that the same correlated asset may be searched many times, such as the processing for the software asset 6 to retrieve the correlated asset D, and the processing for the program asset 7 to retrieve the correlated asset D. There was a problem that it took a lot of time to organize.

[0010] Further, in the past, since the preparation of the rearranged material was entirely dependent on manpower, there was a problem that a relatively large number of man-hours were required and the cost required for that was increased. Furthermore, there has been a problem that as software assets become larger and more complex, it is easy to make erroneous decisions and drop out of surveys.

Therefore, even if it is attempted to promote automation of organization without relying on human labor, it is possible to analyze accurately various language specifications and asset types collectively, and to collect information obtained by analyzing correlated assets. The technique was not considered. For this reason, accurate analysis of various asset types, descriptive languages, asset characteristics, excess or deficiency of assets, analysis of the same asset name, etc. could not be conducted, and analysis and organization of software assets was incomplete. .

The present invention analyzes existing software assets, obtains basic asset information about existing software assets, and correlated asset information as information of parent-child relationship between software assets, and obtains the present status. It is an object of the present invention to provide a software asset rearrangement processing device that rearranges information that has been grasped and outputs a rearrangement result.

[0013]

FIG. 1 is a block diagram showing the principle of the present invention. In the figure, the language determination keyword storage means 10 is, for example, a language determination keyword table,
The keyword for determining the description language of the software asset is stored together with the description format information such as the column in which the keyword is described in the software asset record. The asset name analysis keyword storage means 11 is, for example, an asset name analysis keyword table, and stores a keyword for analyzing the asset name of a software asset together with information in a description format such as a column in which the keyword is described in a record. To do. The characteristic information analysis keyword storage means 12 stores a keyword for analyzing the characteristic of the software asset, for example, an operation distinction of the computer system or a distinction between the batch format and the online format as the definitional distinction. It is stored together with the description format information such as the columns described in the record. Further, the correlated asset analysis keyword storage unit 13 stores a keyword for analyzing a correlation as a parent-child relationship between assets such as a subroutine together with information in a description format such as a column in which the keyword is described in a record.

The software asset analysis unit 14 is, for example, an asset information analysis processing unit, and has a language determination keyword storage unit 10, an asset name analysis keyword storage unit 11, a characteristic information analysis keyword storage unit 12, and a correlated asset analysis keyword storage unit. The stored contents of 13 are used to perform a search and analysis for software assets.

The intermediate asset information storage means 16 is composed of, for example, a basic asset information intermediate table and a correlated asset information intermediate information table, and these tables store the progress of the analysis by the software asset analysis means 14. Further, the software asset analysis means 14 is stored in the asset information storage means 17.
The asset information of the software asset as the final result of the analysis by, for example, the basic asset information about the software asset actually existing in the library and the correlated asset information as the information of the parent-child relationship between the software assets are stored.

The asset rearrangement information output means 15 uses the asset information stored in the asset information storage means 17, that is, the basic asset information and the correlated asset information, for example, lacking assets, unused assets, same assets, asset type information. , A property information information, a shared property, a dedicated property, and the like, and organizes the information and outputs the result as a list.

[0017]

In the present invention, for example, as the first process in FIG. 1, the description language determination process for software assets is performed using the stored contents of the language determination keyword storage means 10. In this process, the software asset is read and the description language is determined for the asset having the keyword that matches the language determination keyword. Then, the result is reflected and stored in the basic asset information intermediate table as an intermediate table for outputting the final result of the basic asset information described later.

Next, as the second processing, the contents of the basic asset information intermediate table storing the description language for each software asset and the software asset are read,
Asset name analysis processing is performed using the stored contents of the asset name analysis keyword storage means 11. The asset name is acquired for the software asset in which the asset name analysis keyword is detected based on the asset name acquisition condition, and the result is reflected and stored in the basic asset information intermediate table.

As a third process, an asset characteristic analysis process is performed. In this processing, the basic asset information intermediate table and the software asset as a result after the asset name analysis processing is finished are read, and the characteristic information analysis keyword storage means 12 is read.
The stored contents of are used to analyze the property of the asset, for example, whether the database system is used or Japanese processing is used, and the result is reflected and stored in the basic asset information intermediate table.

Correlation analysis processing is performed as the fourth processing. In this processing, the basic asset information intermediate table as a result after the end of the asset characteristic analysis processing, the contents of the correlated asset analysis keyword storage means 13, and the software asset are read, and the correlation indicating the parent-child relationship between the assets is read. A correlated asset information intermediate table is created as an intermediate table for the final result of the correlated asset information shown. All of these processes are performed by, for example, the asset information analysis processing unit that constitutes the software asset analysis means 14.

The asset information analysis processing unit further uses the basic asset information intermediate table and the correlated asset information intermediate table at the end of the correlation analysis processing, and the asset as a processing for mutually adding the insufficient information of these tables. Sort processing is performed using the asset name, asset type, etc. by using the type determination processing and the contents of the basic asset information intermediate table and the correlated asset information intermediate table after this asset type determination processing is completed, The asset presence / absence analysis process is performed to analyze the number of times of use, and basic asset information and correlated asset information are output as final asset information.

Finally, the asset rearrangement information output means 1
From the basic asset information and the correlated asset information, the rearrangement information output processing unit constituting 5 outputs a rearrangement result of, for example, insufficient assets and unused assets as a list.

[0023]

FIG. 2 is a block diagram showing the overall system configuration of a software asset consolidation processing device according to the present invention. In the figure, a language determination keyword table 2 corresponding to the software assets 20 and the language determination keyword storage means 10 of FIG.
1, an asset name analysis keyword table 22 corresponding to the asset name analysis keyword storage means 11, a characteristic information analysis keyword table 23 corresponding to the characteristic information analysis keyword storage means 12, and a correlated asset analysis keyword storage means 13
The contents of the correlated asset analysis keyword table 24 corresponding to are given to the asset information analysis processing unit 25 in the processing unit. The asset information analysis processing unit 25 corresponds to the software asset analysis means 14 of FIG.

The asset information analysis processing section 25 uses the software asset 20 and the contents of the four keyword tables 21 to 24 to finally obtain the asset information 29 as the basic asset information 2
9a and the correlated asset information 29b are output, the basic asset information intermediate table 27 and the correlated asset information intermediate table 28 are used in the process of the processing. Here, the basic asset information is information on software assets that actually exist in the source library, and the correlated asset information 29b is information on the parent-child relationship between software assets. Here, the correlated asset is composed of a parent asset and a child asset.

The arrangement information output processing 26 corresponds to the asset arrangement information output means 15 in FIG. 1, and the asset information analysis processing unit 2
5 is used to output information such as insufficient assets, unused assets, the same assets, asset type information, asset characteristic information, shared assets, and dedicated assets as an output list 30 showing the result of software asset rearrangement. Output as.

FIG. 3 shows a format embodiment of the records stored in the four keyword tables 21 to 24 in FIG. FIG. 10A shows a record format of the language determination keyword table 21. As a determination condition, a language determination keyword for determining a language such as JCL and COBOL and a software asset, for example, a program record, that is, in one line. A column indicating which digit the keyword exists in is stored as a determination condition, and a description language of software assets when the determination condition is satisfied is stored as a determination result.

FIG. 3B shows a record format of the asset name analysis keyword table 22. In this format, in addition to the asset name analysis keyword, column, and description language as the analysis conditions, the asset name acquisition conditions, for example, in the case of a program, the "program name is the asset name" condition is stored, and the analysis corresponding to the analysis condition is stored. As a result, for example, an asset type that distinguishes a job asset, a program asset, etc., and an asset unit that distinguishes a program asset from a main program or a subroutine are stored.

In the record format of the characteristic information analysis keyword table 23 of FIG. 3 (c), the analysis result shows the asset characteristic as a distinction in the operation of the computer system or in the definition, for example, in the case of a job, a batch job or online. Data for distinguishing between a job, a database job, and a job using Japanese language processing, a characteristic information analysis keyword as an analysis condition, its storage column, and a description language are stored.

In the record format of the correlation asset analysis keyword table 24 of FIG. 3D, the correlation asset, that is, the description language of the parent asset among the two assets in the parent-child relationship, asset type, asset unit, correlation asset analysis keyword, And the description column in the record is given as the analysis condition, and the description language, asset type, and asset unit of the child asset are stored as the analysis result corresponding to the analysis condition.

FIG. 4 shows the record formats of the basic asset information intermediate table 27 and the correlated asset information intermediate table 28 used as an intermediate process until the final output of the asset information 29 by the asset information analysis processing unit 25 of FIG. This is an example. FIG. 11A shows a record format of the basic asset information intermediate table. In this format, the basic asset, that is, the software asset which actually exists in the source library, has a library name, a member name, a description language,
Stores asset name, asset type, asset unit, asset presence / absence, usage count, asset characteristics, and the same asset presence / absence data. FIG. 4B, which will be described later with respect to the stored contents, is a record format in the correlation asset information intermediate table, and for the parent asset as the correlation asset, the library name, member name, description language, asset name, asset type, asset The unit and the presence / absence of assets are stored. For child assets, the asset name, asset type, asset unit, description language, and presence / absence of assets are stored.

FIG. 5 shows the asset information analysis processing unit 2 in FIG.
5 is an example of a record format of basic asset information 29a as the asset information 29 finally output by 5 and correlated asset information 29b. In FIG. 4A, the format of the basic asset information is exactly the same as the format of the basic asset information intermediate table shown in FIG. On the other hand, the format of the correlated asset information shown in FIG. 5B has a configuration in which the presence / absence data of the asset is excluded from the parent asset and child asset columns of the correlated asset information intermediate table.

FIG. 6 is an overall flow chart of the software asset consolidation processing by the software asset consolidation processing apparatus of the present invention. In the figure, the same parts as those in FIG. 2 are designated by the same reference numerals. In the figure, the asset information analysis processing unit 2
5, the description language determination processing 31 is performed using the software asset 20 and the language determination keyword table 21, and the result is reflected in the basic asset information intermediate table 27a.

Next, the asset name analysis processing 32 is performed using the contents of the asset name analysis keyword table 22 and the basic asset information intermediate table 27a, and the result is reflected in the basic asset information intermediate table 27b.

Next, characteristic information analysis keyword table 2
3 and the basic asset information intermediate table 27b are used to perform the asset characteristic analysis processing 33, and the result is reflected in the basic asset information intermediate table 27c.

Further, the correlation asset analysis keyword table 24
And the basic asset information intermediate table 27c are used to perform the correlation analysis processing 34, and the result is reflected in the correlated asset information intermediate table 28a. With the above, the analysis process using the four keyword tables 21 to 24 in FIG. 2 ends.

Subsequently, the asset information analysis processing section 25 performs an asset type determination processing 35 and an asset presence / absence analysis processing 36. In the asset type determination processing 35, the basic asset information intermediate table 27c and the correlated asset information intermediate table 28a.
Is used to mutually add information that is lacking between these tables, and the result is reflected in the basic asset information intermediate table 27d and the correlated asset information intermediate table 28b.

Further, in the asset presence / absence analysis processing 36, the basic asset information intermediate table 27d and the correlated asset information intermediate table 2
8b is used to output the final basic asset information 29a and the correlated asset information 29b. here,
For example, sorting / aggregation processing is performed for asset names,
Information about the same asset is aggregated. Details of this processing will be described later.

After that, using the basic asset information 29a and the correlated asset information 29b output from the asset information analysis processing unit 25, the rearrangement information output processing unit 26 performs, for example, a list output processing 37 regarding the insufficient assets, and The result is output as the output list 30.

FIG. 7 is an example of a software asset.
In the figure, the software asset 40 includes four libraries 41 (library name: JCLLIB), 42 (library name: PGMLIB1), 43 (library name: PG).
MLIB2), and 44 (library name: CPYLI
B), each library has a plurality of members, for example, the library 41 has 41a (member name: ME
M1) and 41b (member name: MEM2). Here, the library name is the name indicating the location of the data set when the source form software asset is stored as a data set in the computer system, and the member name is the member when the member is stored in the library. Is a name indicating a place for placing. Although the software asset of the member name: M10 is shown outside the software asset 40 in FIG. 7,
This means a lack of assets.

Hereinafter, each processing in FIG. 6 will be described in detail for the software assets shown in FIG. FIG.
FIG. 7 is a detailed explanatory diagram of the description language determination processing 31 in FIG. 6. In the figure, the description language determination processing 31 is performed using the software asset 20 and the language determination keyword table 21 as described in FIG. 6, and the result is reflected in the basic asset information intermediate table 27a. Each item of the basic asset information intermediate table 27a determined by this process is a shaded part.

In the description language determination process, the language determination keyword shown as the determination condition in the language determination keyword table 21 is shown in the language determination keyword table 21 in FIG. 8 in each row (record) of each member in FIG. The language determination is performed by searching at the position of the digit (column) specified in the column of the determination condition. However, in FIG. 7, only a part of each line, that is, each record is shown, and therefore the writing method of each record, that is, the language specification will be described with reference to FIG.

FIG. 9 shows COBOL and JCL language specifications, that is, grammars. FIG. 9A shows COBO.
The fixed length specification of L, the language specification in the case of variable length of COBOL, and the language specification of JCL are shown in FIG. In each sequence column of FIGS. 9A and 9B, a serial number or the like for identifying the line order of the COBOL is described, and in each indicator area, a note line, a blank line, and a line connection of the COBOL are connected. Characters that have been determined to identify the continuation line etc. are described. Further, in each of the A area and the B area, a COBOL headline, a sentence, an instruction, etc. are described, and the IDE of FIG.
The description in the NTIFICATION column is arbitrary.

On the other hand, JCL is used to describe instructions of a program to be executed to the operating system and various conditions for reserving and securing necessary resources and environment for the instructed program. In the control column, operation column, operand column, and continuation column of c), the name of the job control statement, the type of job control statement, the information required for each control statement, and the control statement must be continued on the next line. Is described. The description in the sequence column is arbitrary.

Marking areas of FIGS. 9A and 9B, A
Areas and areas B, and the information described in the control column, operation column, operand column, and continuation column of FIG. 9C as keywords are used as language, asset name, asset type, asset unit, asset characteristic, and Each piece of information of the correlated asset is judged.

In the case of COBOL, for example, each record in FIG. 7 shows only the area A and area B in FIG.
It should be noted that the columns of the language determination keyword table in FIG. 8 correspond to the columns in FIG.

In FIG. 8, for each member in FIG.
For example, the description language determination process is performed in order from 41a. First, for MEM1, the library name and member name are reflected in the basic asset information intermediate table 27a, and the description language determination processing 31 is performed. 1st to 1st row of this member
Since "//" exists in the second column, the determination condition of the stored content of the first line of the language determination keyword table 21 is satisfied for this member in the first column and the second column of the record of the first line. Then, the description language is determined to be JCL. For MEM3, for example, the first line satisfies the determination condition, and the description language is determined to be COBOL. Similarly, the description language determination process 31 is performed for each member, but three members MEM5 and M in the library 44 are used.
For EM6 and MEM7, there is no record that satisfies the determination condition of the language determination keyword table 21, and the description language is blank.

For the column of presence / absence of assets in the basic asset information intermediate table 27a, the software assets MEM1 to MEM1 of FIG.
All MEM9s are real, and "Yes" is stored as the presence / absence of assets, and the number of times of use of each software asset is unconditionally "0" because the number of times of use of each software asset is unknown here. Is set. All items except the shaded items are left blank.

FIG. 10 is a detailed explanatory diagram of the asset name analysis process 32. In the figure, the asset name analysis process 32 for the software asset 20 is performed using the basic asset information intermediate table 27a and the asset name analysis keyword table 22 in which the result of the description language determination process 31 is reflected, and the result is the basic result. It is reflected in the asset information intermediate table 27b. Here, the items of the basic asset information intermediate table determined by this processing are shaded portions.

In the asset name analysis process 32, the asset name is analyzed for each description language determined by the description language determination process 31 described above. Specifically, the designated column of each record of the member to be analyzed is searched for the presence or absence of the asset name analysis keyword corresponding to the already determined description language. When the asset name analysis keyword is present in the designated column, the asset name, asset type, and asset unit corresponding to it are determined based on the asset name analysis keyword table 22.

For example, the language of MEM1 in the first row of the basic asset information intermediate table 27a is JCL, and for this language, the analysis conditions of the first to third rows of the asset name analysis keyword table 22 are used. , Each record of MEM1 in FIG. 7 is searched. In the case of MEM1, the asset name analysis keyword “JOB” in the first line of the asset name analysis keyword table 22 is stored in the third to 71st columns of the first record.
Exists, the asset name acquisition condition (here, job name) corresponding to this keyword is selected, and MEM1 in FIG. 7 is selected.
The job name "JOB1" between "//" and JOB in the first line of (41a) is set as the asset name, and is set in the asset name column of the basic asset information intermediate table 27b. In the asset type and asset unit fields, the corresponding asset type and asset unit in the asset name analysis keyword table 22 are set, respectively. In the keyword item in the second line of the table 22, (without JOB) is “when there is no JOB statement”.
Is the meaning of.

Similarly, the asset name analysis process 32 is performed for each member. For the MEM5 to MEM7 in which the language is not set by the description language determination processing of FIG. 8 and is left blank, the analysis condition of the asset name analysis keyword table 22 is set corresponding to each language, so the asset name is set. Cannot be obtained, the member name is set as it is as the asset name, and the process for that member ends.

The asset type set as a result of the asset name analysis in FIG. 10 indicates the type of job, program, environment definition body, or the like. The asset unit set as a result of the asset name analysis or the asset type determination described below represents a more detailed distinction between asset types.For program assets, language translation by a compiler or assembler for each program language and To identify the software asset that is input in combined editing with a linkage editor, etc. for job assets in job control interpretation of each operating system, and for environment definition assets in edit registration such as dictionary / directory creation for each environment definition entity In addition, it is an item for more clearly indicating the asset type.

The asset unit is a main program or a subprogram (subroutine) in the case of program assets.
In the job asset, such as the program to be copied, the job body, the cataloged procedure specified in the job control statement by being registered in the procedure library, or JC
For example, whether it is an inner stream procedure that is defined / used at the same time in L. In the environment definition, a schema as a structure definition of a database, a subschema as a structure definition of a virtual database, a form definition such as PSAM, A distinction is made between a screen definition body and a pedo as a definition body used for a usage environment declaration or the like when executing a JCL program when using a database or the like.

FIG. 11 is a detailed explanatory diagram of the asset characteristic analysis processing. In the figure, in the asset characteristic analysis processing 33, the basic asset information intermediate table 27b and the characteristic information analysis keyword table 2 obtained by the above-described asset name analysis processing.
3 is used to process the software asset 20, and the result is output as the basic asset information intermediate table 27c. For example, for MEM1 in FIG. 7, since the characteristic information analysis keyword “SUBSYS =” exists in the fourth to fourth columns of the fourth record, the fourth record is the first in the characteristic information analysis keyword table 23. The asset characteristic as a result of the analysis is satisfied as a result of the analysis, and here, "DB" indicating a database job using the database system is set as the asset characteristic.

On the other hand, for MEM2, the language J
There are no records that satisfy the two analysis conditions for CL, and the asset property is left blank. Similarly, the asset characteristic analysis process 32 is performed for each member. Also M
Regarding EM5 to MEM7, since the characteristic information analysis keyword table 23 stores the analysis conditions set corresponding to each language similarly to the asset name analysis keyword table 22, it is possible to analyze the asset characteristics. No, the field is left blank.

The asset characteristic set as a result of the asset characteristic analysis represents an operating environment or an operating form in which the software asset is used, such as a job form,
It represents a distinction in terms of operation and definition of a computer system. By analyzing the asset characteristics, the operating environment of the software asset is determined, such as the operation under the online environment, the operation under the database environment, or the operation under the Japanese language processing system environment. It is possible to analyze the operating environment and operating form of middleware such as subsystems and packaged products that have an interface and work together. This asset characteristic indicates, for example, whether a job is a batch job, an online job (DC), a database job (DB), a Japanese language job (Japanese), or the like.

FIG. 12 is a detailed explanatory diagram of the correlation analysis processing 34. In the figure, the correlation analysis processing 34 for the software asset 20 is performed using the basic asset information intermediate table 27c and the correlation asset analysis keyword table 24 in which the result of the asset characteristic analysis processing 33 is reflected, and the result is obtained. A correlated asset information intermediate table 28a is created as

The correlation asset analysis keyword table 24 is
It is used to analyze the language, asset type, and asset unit of the child asset corresponding to the parent asset, and the child asset is analyzed according to the analysis conditions set for the parent asset corresponding to each language. It

For example, for MEM1 in FIG. 7, the correlated asset analysis keyword “EXEC PROC =” in the first row of the correlated asset analysis keyword table 24 is detected in the 4th to 71st columns of the second record, and its child asset is detected. Asset name is "EXEC PROC =", followed by "MEM
2 ”is determined. Then, the analysis result of the correlated asset analysis keyword table 24 is set as the asset type, the asset unit, and the language of the child asset. In addition, regarding the item of presence or absence of the asset, the child asset actually exists. Since it is unknown, "No" is set unconditionally.

Next, regarding MEM2, the analysis keyword in the second row of the table 24 is detected in the third record, and it is determined that the asset name of the child asset is'PGM1 '. Then, "program" is set as the asset type of the child asset, and "main" is set as the asset unit in the column on the child asset side.

For MEM3, the keywords in the sixth and eighth rows of the correlation asset analysis keyword table 24 are detected in one record each, and the keyword in the seventh row is detected in two records, and the child M as an asset
EM10, MEM5, PGM2, and MEM6 are set. Similarly, for MEM4, two child assets ME
The analysis results for M5 and PGM3 are set.
Similarly, the correlation analysis process 34 is performed for each member.

Regarding the parent asset side of the correlated asset information intermediate table 28a, the contents of each item of the record of the basic asset information intermediate table 27c corresponding to the child asset whose correlation is analyzed by the correlation analysis processing 34. Is set as is.

By the above, four keyword tables 2
The processing using 1 to 24 is completed, and the obtained basic asset information intermediate table 27c and correlated asset information intermediate table 2 are obtained.
8c, the asset information analysis processing unit 25 performs the processing for creating the basic asset information 29a and the correlated asset information 29b as the asset information. The first processing is the asset type determination processing 35. In the asset type determination processing 35, the correlated asset information intermediate table 28b and the basic asset intermediate table 27d are created using the contents of the basic asset information intermediate table 27c and the correlated asset information intermediate table 28a.

13 and 14 show asset type determination processing 3
5 is a detailed explanatory diagram of FIG. In the figure, the items to be processed are the term of the asset unit for the parent asset and the term of the language for the child asset in the correlated asset information intermediate table 28b, and the basic asset intermediate table in the basic asset information intermediate table 27d. 27c are items of the language of real asset information, asset type, and asset unit corresponding to 27c. Further, as the basic asset information intermediate table 27d, the information of child assets is created as a completely new table in addition to the information of actual assets. .

In the actual asset information table of the basic asset information intermediate table 27d, the language, the asset type, and the lacking portion of the asset unit as the items are set. In this setting process, the asset name of the basic asset information intermediate table 27c and the asset name for the child asset of the correlated asset information intermediate table 28a are compared, and both match, and the language of the child asset of the correlated asset information intermediate table 28a, If there is a missing item in the basic asset information intermediate table 27c among the items of asset type and asset unit, the missing item is set and the actual asset information table of the basic asset information intermediate table 27d is created.

Regarding the child asset table of the basic asset information intermediate table 27d, a table having exactly the same format as the actual asset information table is newly created. As each line (record), the contents of the child asset of the correlated asset information intermediate table 28a will be transcribed.
For example, as the language for PGM1, the contents of the real asset table of the basic asset information intermediate table 27d are set. Note that the item of the number of times of use is unconditionally set to "1" because it is used once as a child asset.

Further, regarding the item of the asset unit of the parent asset information of the correlated asset information intermediate table 28b, the library name, the member name, and the real asset table of the correlated asset information intermediate table 28a and the basic asset information intermediate table 27d are targeted. The items of language, asset name, and asset type are compared, and the lacking part of the asset unit is set for the records that match all of them. As for the item of the language of the child asset of the correlated asset information intermediate table 28b, the asset name and the asset are displayed between the child asset information of the correlated asset information intermediate table 28a and the real asset table of the basic asset information intermediate table 27d. The items of the type and the asset unit are compared, and for the records in which all of them match, the item of the language of the real asset table of the basic asset information intermediate table 27d becomes the item of the insufficient language of the correlated asset information intermediate table 28b. Transcribed.

In FIGS. 15 and 16, after the four processes 31 to 34 using the four keyword tables 21 to 24 are completed,
Asset type determination process 3 for outputting the basic asset information 29a and the correlated asset information 29b by the asset information analysis processing unit 25
FIG. 11 is a detailed explanatory diagram of an asset presence / absence analysis process 36 as a second process subsequent to 5. In the figure, the asset type determination process 3
The basic asset information 29a is created by combining the two tables showing the information of the real asset and the child asset of the basic asset information intermediate table 27d obtained by No. 5 into one. Further, the items of presence / absence of each of the parent asset and the child asset are removed from the correlated asset information intermediate table 28b, and the correlated asset information 29b is obtained.

In the asset presence / absence analysis processing 36, sorting and aggregation processing for grouping the asset name, member name, and library name items of the basic asset information intermediate table 27d are performed, and the asset presence / absence of the basic asset information 29a, the number of uses, and the same are performed. The item of presence / absence of assets is set. Next, the sorting process and the aggregation process will be described in detail using a relatively simple example.

FIG. 17 and FIG. 18 are schematic explanatory views of sort and aggregation processing of program assets. In FIG. 17, for simplification, FIG.
Sorting and aggregation processing for the software asset group 4 described in 1. will be described. In this figure, as explained in FIG. 50, the real assets and the correlated assets for the program assets 5, 6, and 7 are checked, and the result is the format of the basic asset information intermediate table 27d originally as described above. However, here, only the item of the asset name and the presence or absence of the asset is shown as the analysis processing result 50.

For example, from the program asset 5, the asset name A
On the other hand, the item of presence / absence of assets is “present”, and the item of presence / absence of assets is “absent” for the program asset of the asset name B. In addition, "1" in parentheses indicates "existence", and "0" indicates "absence". Regarding the program asset 5, that is, the analysis processing result for the asset name A is the basic asset information intermediate table 27d.
Of the actual asset information, and the analysis result of the asset name B corresponds to each row of the child asset information of the correlated asset information of the basic asset information intermediate table.

In FIG. 17, sorting processing is performed on the analysis processing result 50. This sort processing is performed, for example, by arranging the asset names in alphabetical order. The result 51 of this sort processing indicates that the program asset A
There will be one record for, and two for B.

Next, aggregation processing is performed, and the aggregation processing result 52
Is obtained. In this aggregation process, each asset name A,
One record is obtained for each of B, C, and D, and items for presence / absence of assets and the number of times of use are set for the records. The item “presence or absence of assets” is set to “presence” when there is at least one record with “presence or absence of assets” for the asset name in the sorting result 51.

As for the number of times of use, the number of records in the sorting result 51 where the presence / absence of an asset is “absent” is set. That is, for the asset name A, the presence / absence of the asset is'Yes 'and the number of times of use is 0, whereas for the asset name D the presence / absence of the asset is'No', the number of times of use is twice .

FIG. 18 is an explanatory view of another example of not only program resources but also sort processing and aggregation processing. In FIG. 17, the software asset group 54 is shown in FIG.
Unlike the above, the sorting process and the aggregation process will be described assuming that the assets are of three types of assets, that is, the job assets 55, the program assets 56, and the copy phrase assets 57. In the same figure, the analysis processing result 58 is obtained as the format of each record of the basic asset information intermediate table 27d in the same manner as described above. For simplicity, only the asset type, asset name, and asset presence / absence items are shown here. FIG.
Similarly to the record in FIG. 7, the record in which the presence / absence of the asset is “present” corresponds to the record of the real asset information in the basic asset information intermediate table 27d, and the record of “absent” corresponds to the record of the child asset information.

59 is obtained as a result of the sorting process for the analysis process result 58. This sort processing result 59 is a result of sorting using the asset type as the first sort key, the asset name as the second sort key, and the presence or absence of the asset as the third sort key.

Next, an aggregate processing result 60 is obtained for the sorting processing result 59. This aggregate processing result 60 is shown in FIG.
Unlike the aggregation processing result 52 of No. 2, the item of asset type is shown in addition to the items of asset name, presence / absence of the asset, and the number of times of use.

FIG. 19 is a flow chart showing an embodiment of the analysis processing for obtaining the analysis processing results 50 and 58 in FIGS. The process in FIG. 15 corresponds to the process for outputting the real asset record as the real asset information and the correlated asset record as the information of the child asset in the basic asset information intermediate table 27d in FIG.

In FIG. 19, when the analysis process is started,
First, in step S61, the analysis information file for storing the real asset record and the correlated asset record as the analysis result is opened, and in step S62, it is determined whether or not the analysis processing for all the source libraries is completed. In S63, one source library is opened in S63, it is determined in S64 whether the processing for all members in one source library is completed, and if not, one member is opened in S65. , S
At 66, the record in that member is read. S67
It is determined whether or not the processing of all the records in the member opened in has already been completed, and if not completed, it is determined in step S68 whether the real asset information exists in the read member. If it exists, the record is output in S69. After that, the presence or absence of the correlated asset information is determined in S70, and if the correlated asset information exists, the correlated asset record is output in S71, and then the processing of S66 and subsequent steps is continued.

When it is determined in S67 that the process for one member is completed, the member is closed in S72, and the processes in and after S64 are continued. When it is determined in S64 that the processing for all members in one source library is completed, the source library is closed in S73, and the processing in S62 and subsequent steps is continued.
When it is determined in S62 that the processing for all the source libraries has been completed, the analysis information file is closed in S74, and the analysis processing ends.

The method of sort processing in FIGS. 17 and 18 is known, and its description is omitted. 20,
FIG. 21 is a flowchart of an embodiment of the aggregation process. This flowchart will be described with reference to the record format after the sorting process of FIG. 22, the record save area explanatory diagram of FIG. 23, and the aggregate information record format after the aggregation process of FIG.

FIG. 22 shows a record format after the sort processing is completed, and shows formats for records of real assets and correlated assets. In the same figure, as in FIG. 18, each record is made up of items of asset type, asset name, asset presence / absence, and number of times of use for simplicity.

The asset type and the asset name are used as a key for aggregation, and the real asset record is the item of presence / absence of an asset, like the record of the real asset information of the basic asset information intermediate table 27d of FIG. Is set to “Yes” and the number of times of use is set to “0” unconditionally. For correlated asset records,
Similar to the record of the child asset information of the same table 27d, it is assumed that “none” is set for the item of presence or absence of assets and “1” is unconditionally set for the number of times of use.

FIG. 23 is an area for temporarily saving a record in which the item of “presence / absence of assets” is “absent”, and the record format in that area is the same as that of FIG. 22 except that the aggregation key is the saving aggregation key. 22 is the same as in FIG. 22, and in addition to the records of this format, the record save area is provided with a usage count total area and a save flag. The save flag is a flag that is turned on when there is a saved record in the save area and turned off when it does not exist, and the usage count aggregation area adds the usage count of the correlated asset as a child asset in the aggregation process. It is an area for

FIG. 24 shows a record format after the end of the aggregation process. Items of the asset type, the asset name, the presence or absence of the asset, and the number of times of use for each record of the basic asset information 29a after the end of the asset presence / absence analysis process 36 in FIG. It is a format that only takes out.

The aggregation processing flowcharts of FIGS. 20 and 21 will be described with reference to the aggregation processing embodiments of FIGS. 25 and 26.
First, when the aggregation process is started in FIG. 20, the analysis information file storing the records after the completion of the sort process, which is the target of the aggregation process, is opened in S80, and the record of the result of the aggregation process is stored. The aggregate information file is opened. Next, as the initial setting, the save flag is turned off, the value of the usage count area is set to "0", and then S
The analysis information file is read at 81, and it is determined at S82 whether the file has ended, that is, whether or not there is a record to be aggregated, and if so, at S83 that record. It is determined whether or not the item of presence / absence of assets of “is present”.

The first record read is shown in FIG.
If it is the item (a) of (a), since the item of presence / absence of assets for this record is “absent”, the process proceeds to S84 of FIG. 21 and whether the save flag is off or not. To be judged. In this case the save flag is off,
In S85, the correlated asset record, that is, the record (a) is saved in the save area, the save flag is turned on, the number of times of use is added, that is, the value set in the number-of-uses aggregation area and the number of times of use stored in the record. Value, here, "1" is added, and the value "1" is set again in the usage count aggregation area. At this time, the contents of the save aggregation key in FIG. 23 are composed of CPY indicating the asset type of record (a) and C1 indicating the asset name.

After that, the process returns to S81 in FIG. 20, and the process for the next record is continued. For the next record (a), the item of presence or absence of assets is determined to be “present” in S83,
In S86, it is determined whether or not the save flag is on.
In this case, the save flag is on, and it is determined in S87 whether or not the record currently processed, that is, the aggregate key of (a) is the same as the save aggregate key. Since the aggregate key of record (a) is CPY C1 and is the same as the save aggregate key, in S88 the real asset record, in this case record (a) is the aggregate information record of the aggregate result, and that aggregate information record. Is set to a value in the usage count aggregation area, here "1", the aggregate information record is output, the save flag is turned off, the usage count aggregation area is cleared to 0, and the processing returns to S81. .

In step S81, the next record (c) in FIG. 25A is read, and after step S83, step S86.
It is determined whether or not the save flag is turned on in step S. However, at this time, the save flag is turned off, the process of S88 is performed, and the record (c) shows the aggregated information as shown in FIG. As a record, '0' is set as the value of the number of times of use, the save flag is turned off, the value of the number-of-times counting area is cleared to 0, and the process returns to S81.

With respect to the record (d) in FIG. 25A, the process proceeds to the process of S84 through the processes of S82 and S83, and since the save flag is off, this record is saved in the save area in S85. Then, the save flag is turned on, and the value of the usage count total area is set to "1". At this time, the save aggregation key becomes PGM P1.

After that, the processing of the record (e) is performed, and S
After the processes of 81 to S83 and S84, the save flag is determined to be ON in S86, the aggregation key and the save aggregation key are determined to be equal in S87, and the real asset record, here, (e) as the aggregate information record is determined in S88. Output is done. In this case, the number of times of use is set to the value of "1" added in S85 to the record (d).

Also for records (f), S81 to S83
After the processing of step S85, the processing such as saving the record to the save area is performed, and after the processing of step S81, it is determined in S82 that the record has ended, and in step S89, it is determined whether or not the save flag is on. At this time, S85 for the record (F)
The save flag is turned on in step S90, the record in the save area in step S90, that is, the record (K) is set as the aggregate information record, and the number of times of use “1” for the record (F) in step S85 is set, The information record is output, the analysis information file and the aggregate information file are closed in S91, and the process ends. FIG. 25D shows the contents of the aggregated information file after the completion of the aggregation process.

FIG. 26 shows another embodiment of the aggregation processing. With respect to this figure, points different from the example of FIG. 25 will be mainly described.
First, for the analysis information (service), the save flag is determined to be off in S84 through the processes of S80 to S83, and the record is moved to the save area in S85. At this time, the save flag is CP
It becomes Y C1 and the number of times of use becomes “1”.

For records (S), S81 to S83
After the processing of step S84, it is determined in S84 that the save flag is ON, and
At 92, the aggregation key and the saved aggregation key are compared. At this time, the aggregation key of the record (SH) is the same as the save aggregation key, and the number of times of use is added in S93, that is, the number of times of use of the record (SH) is set to "1" with respect to the value "1" of the number of times of use set in S85. 'Is added and the number of times of use becomes "2".

After that, S81 to S for the record (s)
After the process of 83, the processes of S84 and S92 are performed. S
In 92, it is determined that the aggregation key, here the PGM C1 and the save aggregation key CPY C1 are different, and in S94, the record in the save area, that is, the content of the record (service) is set as the aggregation information record, and the record count is used as the usage count. )), The value of “2” set in S93 is set as shown in FIG. 26B, and the integrated information record is output. Then, after the number-of-uses counting area is set to “0”, the number of times of use of the record (s) is added, and the correlation asset record,
Here, the record (s) is saved in the save area, and the process moves to the record (s) processing.

For the record (c), S81 to S8
After the process of 3, the save flag is determined to be ON in S86,
In S87, the contents of the aggregate key and the save aggregate key are compared. In this case, the record (SE) aggregation key is PGM C2
Since the save aggregation key is PGMC1, S9
In 5, the record in the save area, that is, the record (s) is set as the aggregated information record. FIG. 26 shows the number of times of use
As shown in (c), the value "1" added to the record (s) in S94 is set, the aggregated information record is output, and the use count aggregation area is cleared to zero. After that, in S88, the real asset record, here the record (SE) is made into an aggregate information record as shown in FIG.
The value 0 cleared in 95 is set, the integrated information record is output, the save flag is turned off, and the usage count total area is cleared to 0.

After that, through the processing of S81, it is determined that the analysis information record is completed in S82, the save flag is determined to be off in S89, the two files are closed in S91, and the processing ends. FIG. 26E shows the contents of the aggregated information file after the aggregation process is completed.

The sorting and aggregation processing in the asset presence / absence analysis processing 36 of FIG. 15 has been described above in detail. By this, the presence / absence of the asset and the number of times of use of the basic asset information 29a are set.

For the last item of the basic asset information 29a, the item of presence / absence of the same asset, the basic asset information intermediate table 2
If there is an asset with the same asset name only in the result of sorting the items of the asset name, member name, and library name of 7d, it is'Yes 1 ', the asset name and the member name are the same. If there is an asset, "Yes 2" is set, if there is an asset with the same asset name and library name, "Yes 3" is set, otherwise "No" is set. The basic asset information 29a shows the result of aggregation using the asset name, member name, and library name as the aggregation key.

FIG. 27 is an explanatory diagram of the list output processing 37. In the figure, the output processing of the output list 30 is performed using the basic asset information 29a and the correlated asset information 29b finally output as a result of the asset presence / absence analysis processing 36 by the asset information analysis processing unit 25.

FIG. 28 is an explanatory diagram of software asset rearrangement information obtained as a result of rearranging the basic asset information 29a and the correlated asset information 29b. In the figure, the organization information indicating the storage location of assets is from the items of library name and member name, the type of assets is from language, asset type, and asset unit items, the characteristics of assets are from the items of asset characteristics, and the asset name is Obtained from the item of asset name, the same asset, lacking asset, unused asset,
Information on shared assets and dedicated assets must be at least the asset name,
It is also obtained from items such as the number of times of use, existence of assets, and existence of the same assets. Furthermore, relationship information of parent assets and child assets,
That is, rearrangement information related to asset correlation is obtained from the correlated asset information 29b.

In FIG. 27 and FIG. 28, as the organization information of the asset type and the asset characteristic, the organization result is output using the basic asset information 29a for the information of the "presence" item of the presence or absence of the asset.

Arrangement information of the same asset, a lacking asset, an unused asset, a common asset, and a dedicated asset are all obtained from the basic asset information 29a. In the arrangement information of the same asset, the item of presence or absence of asset is “Yes”, and whether the same asset is present is “Yes 1”,
It is output for the records of "Yes 2" or "Yes 3", and the summary information of the insufficient assets is output for the records where the item of presence or absence of assets is "No" and the number of times of use is other than "0", As for the arrangement information of unused assets, the item of presence or absence of assets is'Yes' and the number of times of use is' 0 '. Also, the records that are used more than '2' are output. In addition, the organization information of the dedicated assets is output for the records in which the item of presence or absence of assets is “present” and the number of times of use is “1”.

Finally, the rearrangement information regarding the asset correlation can be obtained by outputting the content of the correlated asset information 29b as it is or by outputting only necessary items. Next, an example of the output list 30 output by the list output processing 37 of FIG. 27 will be described. Here, for the sake of simplicity, an example of the output list will be described taking the software asset group shown in FIG. 29 as an example.

In FIG. 29, the software asset group is JC.
It is assumed that the L asset 100, the program assets 101 and 102, the copy phrase 103, and the subroutines 104 and 105 are included, and the subroutine 106 does not exist.

FIG. 30 is an example of the asset type information list output for the software asset group of FIG. In the figure, software assets are arranged in a form sorted by asset type. The VOL serial number, record length, organization, and format in the list are items added by external input, for example, but since they are not directly related to the present invention, description thereof will be omitted.

FIG. 31 is an output example of the same asset check list. This figure shows an example of a checklist output for the case where the subroutine 105 has S1 as the program ID in the software asset group of FIG.

FIG. 32 shows an output example of the lacking asset list.
This figure also shows a list of insufficient assets for the software asset group of FIG. 29. The program S2 is an insufficient asset, and there are two programs P1 and P2 as assets directly using this insufficient asset, for example, parent assets of the correlated asset information. Indicates that it exists.

FIG. 33 is an output example of the unused asset list for the software asset group of FIG. 29, the program 102 of FIG. 29, that is, P2 is an unused asset, and the program S as a direct asset of this unused asset, for example, a child asset of the correlated asset information.
2, S3 and copy phrase asset C1 are shown to be present. However, the program S2 is a lacking asset.

FIG. 34 is an output example of the asset correlation list for the software asset group of FIG. In the figure, a list of these correlated assets is output for the assets whose asset type is program. For example, as a correlated asset for the program asset P1, one asset J in the upward direction
It is shown that there is OB1 and there are three assets as downward assets, that is, programs S1 and S2, copy phrase C1, and S2 is a lacking asset.

Examples of other output lists are shown in FIGS. 35 to 38 without showing the target software asset group.
The asset list of FIG. 35 outputs assets in a list format for each asset type, and the source library in which the relevant asset exists and the characteristics of the relevant asset can be checked.

The analysis information list of FIG. 36 outputs information acquired by analyzing software assets. As analysis information, the characteristics of the assets, additional information unique to each asset type, and other assets are listed. There is correlation information and the like.

The job summary list in FIG. 37 outputs information such as the programs executed in the job assets and the AIM environment that uses the programs. The asset statistics list shown in FIG. 38 outputs, for example, a result of summarizing the characteristics of program assets, and it is possible to check how many main programs and sub-programs are used and how many copy phrases are used.

Next, the method of using these output lists will be described. FIG. 39 shows an example of using the asset type information list. In the figure, the asset type information list is used for moving the assets stored in the wrong library to the correct library, that is, for organizing the storage location of the software assets.

FIG. 40 shows how to use the same asset checklist. The same asset checklist is used for organizing the same assets by deleting or renaming the assets with the same name.

FIG. 41 shows an example of using the lacking asset list.
In the figure, the lacking asset list is used to sort out the lacking assets by adding missing assets or deleting unnecessary assets.

FIG. 42 shows an example of using the unused asset list. The unused asset list is used for organizing unused assets by deleting unused assets and adding necessary assets.

FIG. 43 shows an example of using the asset correlation list.
In the figure, the asset correlation list is used to investigate the range of influence when the asset is modified. FIG. 44 shows an example of using the asset list. In this way, the asset list is used to find out in which library a specific asset is stored, that is, to find out where the software asset is stored.

FIG. 45 shows an example of using the analysis information list.
Thus, the analysis information list is used to find out what characteristics a particular asset has. In addition,
The ADJUST subroutine in the figure is a subroutine for creating, updating, and referring to a Japanese dictionary in Japanese processing software such as JEF.

FIG. 46 shows an example of using the job summary list. As described above, the job summary list is used to check what kind of processing a particular job is performing. FIG. 47 shows an example of using the asset statistics list. The asset statistics list is used to find out what characteristics the software assets have as a whole, for example, what proportion of programs use the batch format as an asset characteristic.

FIG. 48 is a related explanatory diagram of the output list.
In the figure, it is shown that more effective and detailed information can be obtained by using the output list of the software asset consolidation processing apparatus along the arrow shown in the figure.

[0122]

As described above in detail, according to the present invention, in the software asset rearrangement processing work of a computer system, the contents (asset information) of software assets are automatically analyzed and necessary as rearrangement data. Information, that is, organizing information, can be extracted and output in tabular form. Therefore, there is a remarkable industrial effect that it is possible to efficiently obtain accurate data for software asset consolidation.

That is, according to the present invention, first, the asset type,
Since the criteria for sorting information such as asset characteristics and presence / absence of assets are uniform, it is possible to accurately identify and evaluate software assets.

Secondly, because of a mechanism for collectively identifying and evaluating various sorts of software assets such as asset types, asset characteristics, and asset presence / absence, sort of confused software assets, library management, etc. The management support at the time of software asset development and the management support at the time of maintenance will be efficient. In addition, it can be used for investigating and confirming asset type, asset characteristics, presence / absence of assets for sorting and narrowing down when software conversion (porting) is performed.

Third, it is possible to realize an environment in which it is possible to smoothly search the influence on other software assets at the time of maintenance of software assets, emergency correction, and correction of bugs. For example, before registering or storing software assets in the dictionary, useless software assets, that is, unnecessary assets, can be eliminated, so that it is possible to perform an impact search only on valid asset information, for example, ripple analysis of maintenance. Can be done efficiently.
This is the effect exerted in the environment realized after the software assets are sorted.

Therefore, according to the present invention, the present condition of large-scale / complexed software assets can be grasped and the data can be efficiently arranged. It can be used in all industries such as companies that own assets.

[Brief description of drawings]

FIG. 1 is a principle block diagram of the present invention.

FIG. 2 is a block diagram showing the configuration of the entire system of the software asset consolidation processing device of the present invention.

3 is a diagram showing formats of records stored in four tables in FIG. 2. FIG.

FIG. 4 is a diagram showing record formats of a basic asset information intermediate table and a correlated asset information intermediate table.

FIG. 5 is a diagram showing record formats of basic asset information and correlated asset information.

FIG. 6 is a diagram showing an overall flowchart of software asset processing according to the present invention.

FIG. 7 is a diagram showing an example of software assets.

FIG. 8 is a detailed explanatory diagram of an example of a description language determination process.

FIG. 9 is a diagram showing language specifications of COBOL and JCL.

FIG. 10 is a detailed explanatory diagram of an example of an asset name analysis process.

FIG. 11 is a detailed explanatory diagram of an example of an asset characteristic analysis process.

FIG. 12 is a detailed explanatory diagram of an example of a correlation analysis process.

FIG. 13 is a detailed explanatory diagram (part 1) of the embodiment of the asset type determination processing.

FIG. 14 is a detailed explanatory diagram (part 2) of the embodiment of the asset type determination processing.

FIG. 15 is a detailed explanatory diagram (1) of the embodiment of the asset presence / absence analysis processing.

FIG. 16 is a detailed explanatory diagram (part 2) of the embodiment of the asset presence / absence analysis processing.

FIG. 17 is a diagram (part 1) explaining the concept of sorting and aggregation processing.

FIG. 18 is a diagram (part 2) explaining the concept of sorting and aggregation processing.

FIG. 19 is a flowchart of an analysis processing embodiment.

FIG. 20 is a flowchart (part 1) of the aggregation processing embodiment.
Is.

FIG. 21 is a flowchart (part 2) of the aggregation processing embodiment.
Is.

FIG. 22 is a diagram showing a record format after completion of sort processing.

FIG. 23 is an explanatory diagram of a record save area.

FIG. 24 is a diagram showing a format of an integrated information record.

FIG. 25 is a diagram illustrating an example of an aggregation process.

FIG. 26 is a diagram illustrating another embodiment of the aggregation processing.

FIG. 27 is an explanatory diagram of an example of list output processing.

FIG. 28 is an explanatory diagram of software asset arrangement information.

FIG. 29 is a diagram showing an example of a software asset group as a list output target.

FIG. 30 is a diagram showing an output example of an asset type information list.

FIG. 31 is a diagram showing an output example of the same asset check list.

FIG. 32 is a diagram showing an output example of a lacking asset list.

FIG. 33 is a diagram showing an output example of an unused asset list.

FIG. 34 is a diagram showing an output example of an asset correlation list.

FIG. 35 is a diagram showing an example of an asset list.

FIG. 36 is a diagram showing an example of an analysis information list.

FIG. 37 is a diagram showing an example of a job summary list.

FIG. 38 is a diagram showing an example of an asset statistics list.

[Fig. 39] Fig. 39 is a diagram illustrating a usage example of the asset type information list.

FIG. 40 is a diagram showing an example of using the same asset check list.

[Fig. 41] Fig. 41 is a diagram illustrating a usage example of a lacking asset list.

[Fig. 42] Fig. 42 is a diagram illustrating a usage example of an unused asset list.

FIG. 43 is a diagram showing an example of use of an asset correlation list.

[Fig. 44] Fig. 44 is a diagram illustrating a usage example of an asset list.

FIG. 45 is a diagram showing a usage example of an analysis information list.

FIG. 46 is a diagram illustrating a usage example of a job summary list.

FIG. 47 is a diagram showing an example of using the asset statistics list.

[Fig. 48] Fig. 48 is a diagram for describing the relationship of output lists.

FIG. 49 is a diagram illustrating a conventional example of a software asset organization method.

[Fig. 50] Fig. 50 is a diagram illustrating an example of checking the presence or absence of software assets.

[Explanation of symbols]

 10 language determination keyword storage means 11 asset name analysis keyword storage means 12 characteristic information analysis keyword storage means 13 correlated asset analysis keyword storage means 14 software asset analysis means 15 asset rearrangement information output means 20 software assets 21 language determination keyword table 22 assets Name analysis keyword table 23 Characteristic information analysis keyword table 24 Correlation asset analysis keyword table 25 Asset information analysis processing unit 26 Sorting information output processing unit 27 Basic asset information intermediate table 28 Correlation asset information intermediate table 29 Asset information 29a Basic asset information 29b Correlation asset Information 30 Output list 31 Descriptive language determination processing 32 Asset name analysis processing 33 Asset characteristic analysis processing 34 Correlation analysis processing 35 Asset type determination processing 36 Asset presence / absence analysis processing 37 List output processing

Claims (5)

[Claims] 1. A processing device for organizing existing software assets, a language determination keyword storage means (10) for storing a keyword for determining a description language of the software assets.
And an asset name analysis keyword storage means (11) for storing a keyword for analyzing the asset name of the software asset
A correlated asset analysis keyword storage means (13) for storing keywords for analyzing the correlation between the software assets, the language determination keyword storage means (10), and the asset name analysis keyword storage means (11). ), And software asset analysis means (14) for performing analysis on software assets using the stored contents of the correlated asset analysis keyword storage means (13). apparatus. 2. The software asset analysis means (14)
2. The software asset rearrangement processing device according to claim 1, wherein the software asset reorganization processing device searches the software asset with a keyword stored in the language determination keyword storage means (10), and determines a description language of the retrieved software asset. . 3. The software asset analysis means (14)
Searches the software asset by the keyword stored in the asset name analysis keyword storage means (11), and determines the asset name of the searched software asset,
The software asset consolidation processing device according to claim 1. 4. The software asset analysis means (14)
The method according to claim 1, wherein the software asset is searched by the keyword stored in the correlated asset analysis keyword storage means (13), and the software asset used in association with the searched software asset is determined. Or the software asset consolidation processing device described in 3. 5. A processing method for rearranging existing software assets using a software asset rearrangement processing device, wherein the software assets are searched by a keyword for determining a description language of the software assets. Determining the description language of the software asset, searching the software asset by a keyword for analyzing the asset name of the software asset, and determining the asset name of the software asset; A step of searching the software assets by a keyword for analyzing the correlation between the software assets and determining the software assets used in association with the searched software assets; Processing method.