JPH06131164A - Software standardizing method - Google Patents

Abstract

PURPOSE:To execute work to standardize and unify the synonymous data item of an existing software product both in stages and in parallel. CONSTITUTION:The existing software product is divided into plural parts (101). Then, first of all, the software product is analyzed for every divided unit (102), and the set of the data items equal mutually in their contents and to be of the same meaning is detected on the basis of this analyzed result, and synonymous data item set information is generated (103), and a standard name is given to it (104). Next, the synonymous data item set information containing the same data item in plural divided units is combined, and overall synonymous data item set information is generated (105), and overall standard information is given to it (106). Finally, the data item name of the existing software product is converted by this overall standard information (107).

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for supporting reuse of software, and particularly by unifying and standardizing data item names in existing software, improving productivity of software and maintenance work. The present invention relates to a software standardization method suitable for improving the efficiency of.

[0002]

2. Description of the Related Art In order to improve the efficiency of software maintenance work, it is effective to standardize and standardize data items in software.

Conventionally, as a method for supporting this type of work, for example, there is a method described in Japanese Patent Laid-Open No. 3-294925. Here, standardization and unification of synonymous data items of existing software are performed as follows. (1) In order to standardize and standardize the data items in the existing software, the data items having the same contents are synonymous with the data items such as the input / output of the data items and the analysis of the transfer relationship and the data structure for the programs and job control programs. Synonymous data item set information is created by automatically detecting as item candidates and confirming the synonymous data items from the synonymous data item candidates. (2) Next, the user sets standard information for the determined synonymous data item set information by giving a standard name and standard attribute. (3) Next, the data items in the existing program are standardized and standardized by replacing the usage locations of the synonymous data items in the existing program with the corresponding standard information.

[0004]

In the above-mentioned prior art, operations such as determining group information of synonymous data items (including records and files) by analyzing existing software products, creating standard information, etc. are performed. There are the following problems because it is done collectively for the whole.

(1) The existing software cannot be divided into a plurality of parts, and the detection of synonymous data item set information and the creation of standard information cannot be performed in parallel in each division unit, resulting in poor work efficiency. (2) If you want to revise a part of the created standard information,
I can't redo only a part. (3) When standardizing only a part of the existing software, the standard information standardized by the work is
It is not possible to standardize gradually by using the rest of the standardization work. (4) It is not possible to perform stepwise standardization by using the synonymous data item set information created when standardizing only part of the existing software for standardization work of other parts.

A first object of the present invention is to divide the existing software into a plurality of parts, individually standardize and unify the individual division units, and then integrate the whole to standardize and unify It is possible to perform the work for each unit in parallel and to perform the work for re-doing for each divided unit.

A second object of the present invention is to standardize and unify a part of the existing software in advance, and then use the standard information of the already standardized part when standardizing and unifying the remaining part. , It is possible to standardize and unify the rest.

A third object of the present invention is to create synonymous data item set information for a part of existing software, standardize it, and then standardize and unify a larger part including that part. This is to enable standardization and unification in stages by using the synonymous data item set information of the already created part.

[0009]

According to the software standardization method of the present invention, an existing software product is divided into a plurality of parts, and synonymous data item set information and standard information (standard data item name, standard attribute) are divided for each division unit. Determine and share synonymous data item set information containing the same data item in multiple division units based on sharing relationship information such as programs, files, and databases that are shared between division units, and the entire system or multiple divisions It is characterized by creating synonymous data item set information and standard information for each unit.

Further, it is characterized in that synonymous data item set information and standard information are created stepwise by further merging a plurality of division units.

Further, in determining the standard information for each division unit, the programs, files, and data in the database shared among the division units are based on the sharing relation information such as the programs, files, and databases shared among the division units. It is characterized in that standard information of another division unit whose standard information has already been determined is adopted for the item.

Further, in the creation of the synonymous data item set information for each division unit, the synonymous data item set information has already been created based on the sharing relationship information such as the programs, files and databases shared among the division units. It is characterized in that, in addition to the synonymous data item set information of the division unit, the synonymous data item set information of the upper division unit or the whole including the division unit is created.

[0013]

According to the present invention, an existing software product is divided into a plurality of parts, synonymous data item set information and standard information (standard data item name, attribute) are determined for each division unit, and the program is shared among the division units. Based on the sharing relationship information of files, databases, etc., it is determined that the data items of the program shared between division units are the same, and that the data items shared between division units and the data items at the same position of the database are the same. Then, the synonymous data item set information including the same data item is merged in a plurality of division units to create synonymous data item set information and standard information of the entire system or a plurality of division units. Before the synonymous data item set information is merged, there is no relation between the division units. Therefore, the creation of synonymous data item set information and the creation of standard information for each division unit can be performed in parallel. In addition, it is possible to perform the re-doing work for each division unit. In addition, if the standardization of some division units is redone after the whole standardization,
If the work after the merging of the entire synonymous data item set information is performed without redoing the other division units, the whole can be restandardized.

Further, in the determination of the standard information for each division unit, the files, databases, and data items in the programs shared among the division units are based on the sharing relation information of the files, databases, and programs shared among the division units. For, the standard information of other division units for which the standard information has already been determined is adopted. Therefore, it is possible to standardize the remaining part by using the already standardized information.

Further, in the creation of synonymous data item set information for each division unit, other division units for which synonymous data item set information has already been created based on sharing relationship information of files, databases, and programs shared among the division units. In the form of adding to the synonymous data item set information of, the synonymous data item set information of the upper division unit including the division unit or the whole is created. At this time, if standard information is added to the original synonymous data item set information to be added, the standard information can be used. Therefore, it is possible to standardize in stages.

[0016]

FIG. 2 is a schematic block diagram of a hardware environment that supports the software standardization method of the present invention. The central processing unit (CPU) 200 reads the software product to be standardized stored in the external storage device 250,
Partial and stepwise standardization of synonymous data items. The created standardized software product is stored in the external storage device 250 again. The memory 210 is the CPU 20
It is used as a working memory of the CPU 200 while storing a processing program of 0, parameters, and the like.
The input device 200 is a keyboard or the like and is used by the user to input commands and data. The display device 230 is a CRT display or the like, and the contents of the target software product before, during or after the standardization, the input device 2
Used to display input data from 20 and the like. The output device 240 is a laser printer or the like, and is used when the software product to be standardized or the created standardized software product is printed out as necessary.

Each embodiment of the software standardization method of the present invention will be described in detail below.

<Embodiment 1> FIG. 1 shows a processing procedure in the first embodiment of the present invention, and the software standardization processing of the present embodiment will be described in accordance with this.

First, the software product to be standardized is divided into a plurality of parts (step 101). Here, each divided part is called a subsystem.

FIG. 3 shows an example of the configuration of the standardized software product and the division of subsystems. The configuration of the software product in FIG.
1) and subsystem B (302). Of these, the subsystem A is the program P1 (303), the program P2 (304), and the file entity FILE1 (30
5) and a job control program J1 (306) that defines the execution procedure of the program. Further, the subsystem B has a program P2 (304) and a program P3 (3
07), the file entity FILE2 (308), and the job control program J2 that defines the execution procedure of the program
It consists of (309).

FIG. 4 shows the program P1 (30
3), P2 (304), P3 (307),
Source program P1 (4
01), P2 (402), and P3 (403).

In FIG. 3, the program P2 (30
4) Subsystem A (301) and Subsystem B (3)
02), but the sharing relationship is not considered in the stage of step 101, and the configuration of the standardized software product is divided into subsystem A and subsystem B.

Next, for each subsystem, the software product is analyzed (step 102), synonymous data item set information is created (step 103), and a standard name is given (step 104). Hereinafter, these processes will be described in order.

First, one subsystem is selected from the unprocessed subsystem group, and the software product of the subsystem is analyzed (step 102). Specifically, analysis of the source programs that make up the subsystem,
Analyze the job control program.

Information on the relationship between the data item name in the program and the file allocation name containing the data item is analyzed by analyzing the source program, and information on the relationship between the file allocation name and the file entity name is extracted by analyzing the job control program. Further, information on the relationship between the data item name and the file entity name is extracted from the relationship between the data item name and the file allocation name and the relationship between the file allocation name and the file entity name. The file allocation name is a tentative name for identifying the file in the program, and the file entity name is the name given to the file entity accumulated in the external storage device used when executing the program. When extracting the relationship between the data item name and the file allocation name, the position and length of the corresponding data item in the input / output record of the file are also extracted.

The method of extracting the relationship between the data item name and the file allocation name, the relationship between the file allocation name and the file entity name, and the relationship between the data item name and the file entity name is as follows.
For example, it is described in Japanese Patent Application No. 2-97676.

FIG. 5 shows the subsystem A (301) of FIG.
The information of the analysis result of the software product of is shown. That is,
Program P1 (303), Program P2 (304)
The information (501) on the relationship between the data item name and the file allocation name is analyzed by analyzing the program P1 (401) and the program P2 (402) shown in FIG. 4, and the file allocation name is analyzed by the job control program J1 (306). And the information (502) about the relationship between the file entity name and
Information (503) on the relationship between the data item name and the file entity name is extracted from the information (501) on the relationship between the data item name and the file assignment name and the information (502) on the relationship between the file assignment name and the file entity name.

Next, the synonymous data item set information of the data items in the subsystem is created (step 10).
3).

Since the same file entity is used when the file entity name at the time of execution is the same, the position and length in the input / output record are the same among the data items input / output to / from the same file entity. Things can be considered to have the same content and be considered synonymous. Therefore, synonymous data item set information is created by assigning the same synonymous identifier to data items having the same position and length in the input / output record of the same file entity. In addition, even if an intermediate data item is used between data items, items having a transfer relationship are regarded as synonymous and synonymous data item set information is created. Furthermore, data items that share the same physical position are regarded as synonymous, and synonymous data item set information is created.

The method of creating the synonymous data item set information itself is also described in Japanese Patent Application No. 2-97676.

FIG. 6 shows an example of creating synonymous data item set information of subsystem A (301) from the analysis information of FIG. That is, in the subsystem A (301), among the input / output data items of the same file entity FILE1, the data item OUTDA of the program P1 having the same length as the start position.
Data item INDA of TA (504) and program P2
It is determined that TA (507) is synonymous data, and synonymous data item set information (601) having the same synonymous identifier 01.
Data item NO1 (50
5) and the data item SYO-NO (50 of the program P2)
8) is a synonym data item, a synonym set (602) having the same synonym identifier 02 is created, and the data item NAME1 (506) and the program P of the program P1 are created.
The second data item SYOIN-NAME (509) is determined to be a synonymous data item, and a synonym set (603) having the synonymous identifier 03 is created.

Next, after creating the synonymous data item set information of the subsystem, a standard name is given to the synonymous data item set information (step 104).

To assign a standard name, a plurality of data item names having the same synonymous identifier are displayed on the display device 230, and the user uses the input device 220 to input the item number of the standard data item name or the name determined by the user. By entering. At this time, if the attributes of each data item are also displayed, the user can determine the standard attribute as well as the data item name.

FIG. 7 shows an example of a procedure for assigning a standard name to the synonymous data item set information in FIG. 6 in subsystem A. FIG. 8 shows a procedure for assigning a standard name to the synonymous data item set information in FIG. An example of standard information of the subsystem A is shown.

In the example of assigning the standard name of the synonym set 01 (701) in FIG. 7, the synonym set (601) of the synonym identifier 01 of FIG. 6 is displayed on the display device 230, and the input device 220 is displayed.
The user inputs SYOHIN-REC to determine SYOHIN-REC as a standard name. Further, in the example of assigning the standard name of the synonym set 03 (702), the synonym set (603) of the synonym identifier 03 of FIG. 6 is displayed on the display device 230, and the user inputs the item number 2 from the input device 220. The name SYO corresponding to item number 2
HIN-NAME is decided as the standard name.

FIG. 8 shows the synonym data item set information of the subsystem A of FIG. 6 with the standard name determined above. The synonym set (601) of the synonym identifier 01 has the standard name S.
YOHIN-REC is a synonym set (6
02) has the standard name SYOIN-NO and the synonym identifier 0.
The standard name SYOHIN-NA is assigned to the synonymous set (603) of 3
MEs are given respectively.

For each subsystem, the above 102 to 104
Repeat step. The analysis of software products for each subsystem (step 102), creation of synonymous data item set information (step 103), and standard name assignment (step 104) may be performed in parallel or at different times. Good. This allows the work to proceed while ignoring the relationships between the subsystems.

An example in which steps 102 to 104 are executed for the subsystem B in FIG. 3 is shown below.

FIG. 9 shows information on the analysis result of the software product of the subsystem B of FIG. Figure 3
Program P2 (30
4) and P3 (307) for details, see program P2 in FIG.
(402) and P3 (403). This program P
2 (402) and the program P3 (403) are analyzed to obtain information on the relationship between the data item name and the file allocation name (90
1), information (902) on the relationship between the file allocation name and the file entity name is extracted by analysis of the job control program J2 (309) in FIG. 3, and information on the relationship between these data item names and the file allocation name (901). Then, information (903) on the relationship between the data item name and the file entity name is extracted from the information (902) on the relationship between the file assignment name and the file entity name.

FIG. 10 shows synonymous data item set information of subsystem B created from the information of the analysis result of the software product of FIG.

In the subsystem B, the same file entity F
Among the input / output data items of ILE2, the data item INDATA (90 of the program P2 having the same position and the same length)
4) and the data item OUTDATA (9 of the program P3
08) is synonymous, a synonym set (1001) having the same synonym identifier 01 is created, and the data item SYO-NO (905) of the program P2 and the data item ID (909) of the program P3 are synonymous. It is determined that there is a synonym set (1002) having the same synonym identifier 02 and the data item SYOHIN-VAL of the program P2 is created.
Data item PRIC of UE (907) and program P3
It is determined that E (910) has the same meaning, and a synonymous set (1003) having the same synonymous identifier 03 is created.

FIG. 11 shows an example of creating standard information of subsystem B for the synonymous data item set information of FIG.

In FIG. 11, for the subsystem B, the standard name SYOHIN-REC is assigned to the synonym set (1001) of the synonym identifier 01 in the synonym data item set information of FIG.
The standard name SYOIN-ID is assigned to the synonym set (1002) of the synonym identifier 02, and the synonym set (1
003) is given the standard name SYOIN-PRICE.

After the synonymous data item set information and standard name for each subsystem are determined as described above, the synonymous data item set information of the subsystems is then merged to obtain the synonymous data of the standardized software product as a whole. Item set information is created (step 105).

In merging synonymous data item set information of each subsystem, the programs, files, and databases shared between the subsystems are the merging key.

In this embodiment, the same overall synonymous identifier is given to the synonymous data item set information of each subsystem including the same data item in the program shared by the subsystems.

In addition, files shared between subsystems, data items at the same position in the input / output records of the database are regarded as synonymous data items, and synonymous data item set information of each subsystem including this synonymous data item is used. Merge by giving the same overall synonymous identifier.

When merging synonymous data item set information, synonymous data sets in each subsystem that do not include data shared between subsystems or data that are synonymous between subsystems are given different overall synonymous identifiers. Then, the synonymous data item set information is incorporated.

In FIG. 12, the synonymous data item set of subsystem A (FIG. 6) and the synonymous data item set of subsystem B (FIG. 10) are merged by the same data item in the shared program to obtain a synonymous data item. An example of creating group information will be shown.

In this embodiment, since the program P2 is shared by the subsystem A and the subsystem B as shown in FIG. 3, the data items INDATA, SYO-NO, SYOIN- used in the program P2 are shared. NA
ME and SYOIN-VALUE are the merging keys.

First, the synonymous data item set information 01 (60) of the subsystem A including INDATA of the program P2
1) is taken out and the synonym set identifier is set to 01. Further, the synonym set 01 (1001) of the subsystem B including the same data item is taken out and the same overall synonym set identifier 01 is given. Since there are no synonymous sets of other subsystems that include the same data item, it is assumed that there is no other synonymous set identifier 01 (1201).

Next, the synonym set 02 (602) of the subsystem A including SYO-NO of the program P2 is taken out, and the overall synonym set identifier is set to 02. Furthermore, a synonymous set 02 (100 of subsystem B including the same data item)
2) is taken out and the same overall synonymous set identifier 02 is given. Since there is no synonymous set of other subsystems including the same data item, it is assumed that there is no other synonymous set identifier 02 (1202).

Next, SHOIN-N of the program P2
Synonymous set 03 (603) of subsystem A including AME
, And the synonym set identifier is 03. Since there are no synonymous sets of other subsystems that include the same data item, it is considered that there is no other corresponding synonymous set identifier 03 (1203).

Next, SHOIN-V of the program P2
Synonymous set 03 (100) of subsystem B including ALUE
3) is taken out and the whole synonymous set identifier is set to 04. Since there is no synonymous set of other subsystems that include the same data item, it is considered that there is no other synonymous set identifier 04 (1204).

As shown in FIG. 12, step 10
The standard name of the subsystem A (FIG. 8) and the standard name of the subsystem B (FIG. 11) given to No. 4 are retained as the subsystem standard name in the overall synonymous data item set information.

In this way, a standard name (whole standard name) is given to the created synonymous data item set information (step 106).

To assign the entire standard name, the standard names (subsystem standard names) of a plurality of subsystems having the same overall synonymous set identifier are displayed on the display device 230, and the user inputs the entire standard name from the input device 220. By entering the item number of the subsystem standard name or the name determined by the user. At this time, if the same standard name is given to all the synonymous sets of the merge source, the name is adopted as a candidate for the whole standard name. At this time, the standard attributes in each subsystem are also displayed, and the user can determine the overall standard attributes as well as the standard name.

FIG. 13 shows an example of the procedure for assigning the overall standard name to the overall synonymous data item set information of FIG.
Shows an example of creating the standard information.

In FIGS. 13 and 14, the whole synonymous set 01
On the other hand, (1201), since the standard name SYOHIN-REC ((FIGS. 8 and 11) is given to both subsystems A and B, this is adopted as a candidate for the entire standard name, and the user is confirmed. Has been decided (1301, 140
1).

Subsystem standard names SYOHIN-NO (FIG. 8) and SYOH are included in the entire synonym set 02 (1202).
Although the IN-ID (Fig. 11) is given, the new standard name SYOHIN-C as a whole is input by the user.
ODE is given (1302, 1402).

Overall synonymous sets 03 (1203) and 04 (1
204) are subsystem standard names SYOIN-N
AME (Fig. 8) and SYOIN-PRICE (Fig. 11)
Since it has only one, the subsystem standard name is directly used as the general standard name (1403, 1404).

As described above, by using the information standardized independently for each subsystem, it is possible to efficiently standardize the entire system.

Finally, the data item name in each source program is replaced by the entire standard name to create a standard source program (step 107).

In FIG. 15, the data item names of the program P1, program P2, and program P3 in FIG.
YOHIN-REC, SYOIN-CODE, SYO
An example in which HIN-NAME and SYOIN-PRICE are substituted is shown.

The synonymous data item set information can be merged not only for all subsystems at once but also for some subsystems in the same manner. Furthermore, the partially synonymous synonym data item set information can be merged. This can be easily realized by repeating the procedure of the above embodiment.

Further, at the time of merging, it is optional whether or not a standard name is given to the subsystem synonymous data item set information of the merging source, and when deciding the overall standard name after merging, the merging source standard name is given. It is also possible to easily refer to only the existing standard name assignment by modifying the standard name assignment process in step 104.

Regarding the shared information at the time of merging, the user can select it by the following method. That is, by displaying the names of programs, files, and databases having the same name between subsystems on the display device, and by instructing the user whether or not to adopt them as shared information,
You can choose.

When determining the standard name of the entire step 106, it is possible to simultaneously create the standard record configuration information adopting the standard name of each data item in the same input / output record. That is, at the time of analysis of the software product (step 102), the highest level data item name for each data item is acquired, and synonymous data item set information creation (step 105) and standard name assignment (step 106) are performed. After that, the standard name for the synonymous data item set information of the highest level data item is set as the highest level data item, and the standard name for the existing lower data item having the existing data item name in the synonymous data item set information at the highest level,
A standard record structure can be created by placing it in the position of an existing subordinate data item.

FIG. 16 shows an example of the standard information having the information of the highest data item name for the existing data item with respect to the standard information of FIG. 14, and FIG. 17 shows the standard record structure generated by the standard information of FIG. For example:

First, the standard name of the synonymous set 01 (1601) of the highest level data items in FIG. 16 is adopted as the highest level data item name of the standard record structure (1701).

Then, OUTDATA of the program P1, INDATA of the program P2, and OU of the program P3, which are the existing data items of the synonymous set 01 (1601).
The standard names of the lower data items for TDATA are adopted in the standard record structure in order from the smallest position in the record.

No. 1 of the program P1 and SYO-NO of the program P2 whose position in the record is the smallest 1.
And the ID of the program P3 are standard name SYOIN-CO
Since it has a DE (1602), SYOIN-CODE
Is placed at the next position of the standard record (1702).

NAME1 of program P1 and SYOH of program P2 whose position in the record is the next smallest 9
Since IN-NAME has the standard name SYOIN-NAME (1603), SYOIN-NAME is arranged at the next position of the standard record (1703).

SHOIN-VALUE of program P2 and position P of program P3 whose position in the record is 17
Since RICE has the standard name SYOIN-PRICE (1604), SYOIN-PRICE is arranged at the last position of the standard record (1704).

When creating this standard record structure, a standard attribute corresponding to the standard name may be adopted as the attribute of each data item in the standard record.

Further, in step 0107, when the data item name in each source program is replaced by the entire standard name, the standard record structure can be replaced in record units.

FIG. 18 shows the data item names of the programs P1, P2 and P3 of FIG. 4 as standard data item names in the standard record SYOHIN-REC (FIG. 1).
An example of the standard source program replaced in 7) is shown below. In this example, the definition information of the standard record structure is expanded in the source program, but the standard record structure may be replaced with a COPY clause having a COPY original sentence.

<Embodiment 2> FIG. 19 shows a processing procedure in the second embodiment of the present invention. In this embodiment, when a standard name is assigned to each subsystem, the standard information of another subsystem is determined by using the information of the subsystem whose standard information has already been determined.

In FIG. 19, the processing procedure is the same as that shown in FIG. 1 except that a standard name is assigned using standard information of another subsystem (step 1901).

Standard name assignment of this embodiment (step 190)
In 1), when a standard name for each subsystem is given in the embodiment of FIG. 1, among the data items in the synonymous data item set information, the data items are included in the synonymous data item set information of another subsystem, For a standard name already assigned to another subsystem, the standard name of the other subsystem is displayed on the display device 230 as reference information, and the user uses the input device 220 to set the standard data item name. Enter the item number or the name determined by the user.

The software product structure illustrated in this embodiment uses the software product structure shown in FIG. 3 as in the first embodiment.

In the standard name assignment of the subsystem A (301) in this embodiment, since the synonymous data item set information creation and standard name assignment of other subsystems have not been performed yet, refer to other subsystem information. There is no.

When the standard name of the subsystem B (302) is assigned, the standard name of the subsystem A has already been assigned, so the standard information of the subsystem A (FIG. 8) is used as a reference.

FIG. 20 shows an example of assigning the standard name of subsystem B with reference to the standard information of subsystem A (FIG. 8).

First, a standard name is given to the synonymous identifier 01 (1001) of the synonymous data item set information (FIG. 10) of subsystem B (2001). Here, since the data item INDATA of the program P2 is given the synonymous identifier 01 and the standard name SYOHIN-REC in the subsystem A (801 in FIG. 8), the subsystem name and the standard name are displayed on the display device 230. (2002). Since the data item OUTDATA of the program P3 is not included in any synonymous set in the subsystem A,
The subsystem name and standard name are not displayed on the display device 230 (2003). The user inputs the item number 1 from the input device 220, so that the program P2 corresponding to the item number 1 is input.
The standard name SYOHIN-REC in the subsystem A of the data item INDATA is adopted as the standard name.

Next, a standard name is assigned to the synonymous identifier 02 (1002) of the synonymous data item set information (FIG. 10) of subsystem B (2004). Again, since the data item SYO-NO of the program P2 is given the synonymous identifier 02 and the standard name SYOIN-NO in the subsystem A (802 in FIG. 8), the subsystem name and the standard name are displayed on the display device 230. It is displayed (2005). Since the data item ID of the program P3 is not included in any synonymous set in the subsystem A, the display device 2
Subsystem name and standard name are not displayed in 30 (200
6). By inputting SYOHIN-ID by the user, SYOHIN-I is used as the standard name in subsystem B.
Adopt D.

Next, in the standard name assignment (2007) to the synonymous identifier 03 (1003) of the synonymous data item set information (FIG. 10) of the subsystem B, the data item SYOHIN-VALUE of the program P2 and the data item PRICE of the program P3. Since neither is included in the synonymous data item set information of subsystem A, the subsystem name and the standard name are not displayed (2008, 2009), and the standard name is given with reference to the existing data item name.

According to the example of FIG. 20, the standard information as a result of adding the standard name of the subsystem B becomes the same as the case of FIG. 11 (FIG. 11).

In this embodiment, when the standard information of each subsystem is determined, the same standard name as the standard names of other subsystems that have already been assigned must be assigned to all subsystems. Since the first name is adopted, it is not necessary to merge the synonymous data item set information to create standard information common to all (steps 105 and 0106).

The data item name change in the program by the standard name (step 107) may be performed for each subsystem immediately after the standard name is given (step 1901) in each subsystem of this embodiment.

<Third Embodiment> FIG. 21 shows a processing procedure according to a third embodiment of the present invention. This embodiment differs from the first embodiment in that the synonym data item set information of another subsystem is added to the synonym data item set information of the subsystem after the synonym data item set information of the subsystem is created. The item set information is created.

In FIG. 21, division of software products (step 101), software product analysis of each subsystem (step 102), creation of synonymous data item set of the first subsystem (103), creation of standard information thereof (104). ) Is the same as in the first embodiment.

In the creation of the synonymous data item set information of the second and subsequent subsystems, the synonymous data item set information is created for each subsystem in the first embodiment, whereas in the present embodiment, the synonymous data item set information is created. Instead of making the set information unique to the subsystem, the information of the subsystem is added to the synonymous data item set information created in the previous subsystem, and the entire synonymous data item set information is updated (step 210).
1). After that, the standard name is similarly added and changed (step 2102).

In the synonymous data item set information creation (step 2101) of the present embodiment, for a data item group considered as synonymous in the subsystem being processed, a certain synonymous data item in which a certain data item has already been created When included in the set information, a synonymous set identifier including the same is given to all the data items of the above-mentioned data item group, and additionally registered in the overall synonymous data item set information. Also, for any data item group that is considered synonymous within the subsystem being processed, if none of the data items in it are included in the already-created general synonymous data item set information, all data items of this data item group A new global synonym set identifier is assigned to and is additionally registered in the global synonymous data item set information.

In this embodiment, since the synonymous data item set information and the standard information are inherited between the subsystems as the overall information, the standard information including the synonymous data item set information is the synonymous data item set information as the overall synonymous data item set information. Shall be added.

The configuration of the software product illustrated in this embodiment also uses the configuration of the software product shown in FIG. 3 as in the first and second embodiments.

First, in the synonymous data item set information creation (step 103) of subsystem A (301), there is no synonymous data item set information because it is the first subsystem. Therefore, as in the first embodiment, synonymous data item set information is created (FIG. 6), and a standard name is given in step 104 (FIG. 8).

Next, in the creation of the synonymous data item set information of the subsystem B (302) (step 2101), since the synonymous data item set information of the subsystem A has already been created, addition is made to this.

In this embodiment, the synonymous data item set information in FIG. 6 is used as work information, and standard information (FIG. 8) including this synonymous data item set information is used as the entire synonymous data item set information to add information. .

FIG. 22 shows synonymous data item set information created by adding synonymous data items of subsystem B to the standard information (FIG. 8) of subsystem A created in steps 103 and 104. The additional procedure in FIG. 22 is as follows.

With respect to the analysis result of the software product of subsystem B (FIG. 9), the data item INDATA (904) of the program P2 having the same position and length among the input / output data items of the same file entity FILE2. It is assumed that the data items OUTDATA (908) of the program P3 are the same. Among these, the data item INDATA of the program P2 is included in the synonym set (801) of the synonym identifier 01 of the standard information of FIG. Therefore, program P3
The data item OUTDATA of is also a synonymous identifier 01,
It is added to the standard information (2201).

Next, the data item SYO of the program P2
-NO (905) and data item ID of program P3
(909) are considered to be the same. Among these, the data item SYO-NO of the program P2 is included in the synonym set (802) of the synonym identifier 02 of the standard information of FIG. Therefore, the data item ID of the program P3 is also the synonymous identifier 02.
Is added to the standard information (2202).

Next, the data item SYO of the program P2
It is considered that the HIN-VALUE (907) and the data item PRICE (910) of the program P3 are the same. Since both of them do not exist in the existing standard information, a new synonymous identifier 04 is added and added to the standard information (220).
3).

In FIG. 22, the standard name for the newly added data item is not fixed. Therefore, after adding the synonymous data item set information, a standard name is given (step 21).
02).

Assigning the standard name of this embodiment (step 210)
2) is performed after updating the synonymous data item set information for each subsystem. At this time, even for the synonymous data item set information to which the standard name has already been assigned in the previous subsystem, the standard name can be changed by adding new synonymous data item set information.

To change or add the standard name, the standard information to which the synonymous data item set information is added is displayed on the display device 230 for each synonymous identifier, and if the user adopts the standard name already assigned, If the item number of the data item to which the standard name is added is input from the input device 220 and if the name of the data item to which the standard name is not yet assigned is adopted, the item number of the data item is input and a completely new item is input. If a name is given, it is decided by inputting a new name.

FIG. 23 shows an example of a standard name change / addition setting method for the standard information of FIG. 22, and FIG. 24 shows an example of standard information after the change / addition of the standard information of FIG.

First, a standard name is given to the synonymous set of the synonymous identifier 01 of FIG. 22 (2301). Here, the data item OUTDATA of the program P1 and the program P
The data item INDATA of 2 is already the standard name SYOIN
-Because REC is added, the fact is displayed on the display device 230. Data item OUTDAT of program P3
Since the standard name is not given to A because it was added in subsystem B, the standard name is blank. In the example of 2301, when the user inputs the item number 1, the item number 1
The standard name of the data item is adopted again as the standard name of the synonymous identifier 01. As a result, the standard name of the data item OUTDATA of the program P3 is also SYOHIN-REC.
(2401).

Next, a standard name is given to the synonymous set of the synonymous identifier 02 of FIG. 22 (2302). In this case as well, the data item NO1 of the program P1 and the data item SYO-NO of the program P2 are already the standard name SYOHIN-NO.
Is added, the display device 230 displays that fact. Data item ID of program P3 is subsystem B
Since the standard name has not been given since it was added in, the standard name is blank. In the example of 2302, the user inputs SYOIN-CODE
YOHIN-CODE is re-determined as the standard name of the synonymous identifier 02. As a result, the standard names of the data item NO1 of the program P1 and the data item SYO-NO of the program P2 are changed to SYOIN-CODE, and the standard name of the data item ID of the program P3 is SYOIN-CO.
It becomes DE (2402).

Next, a standard name is given to the synonymous set of the synonymous identifier 03 of FIG. 22 (2303). Again, data item NAME1 and program P2 of program P1
The data item SYOIN-NAME of is already the standard name SY
Since OHIN-NAME is added, the display device 2
The fact is displayed on 30. Since there is no other data item with the synonymous identifier 03, all standard names have been decided,
If necessary, change is possible. In the example of 2303, no change is made.

Next, the standard name is given to the synonymous set of the synonymous identifier 04 of FIG. 22 (2304). Here, since the data item SYOIN-VALUE of the program P2 and the data item PRICE of the program P3 are added in the subsystem B, the standard name is not given, so the standard name is blank. In the example of 2304, when the user inputs SYOHIN-PRICE, SYOHIN-PRICE is adopted as the standard name (2
403).

At this time, if the user inputs item number 1, the standard name is the name SYOHIN- of the data item of item number 1.
VALUE is adopted.

In this embodiment, the data item name change (step 107) in the program is the same as in the first embodiment.

[0114]

As is apparent from the above description, according to the present invention, the following effects can be obtained.

(1) Standardize existing software products,
In unifying work, existing software products can be divided into multiple parts and standardization for each division unit can be performed in parallel, so when standardizing large-scale software, it is easy to divide work among a large number of people and adjust work schedules. The work efficiency can be improved and the work period can be shortened.

(2) Since partial standardization can be easily redone, it is possible to reduce rework work.

(3) Since the standard information of the already standardized part and the synonymous data item set information can be utilized at the time of standardizing the remaining part, the standardization of the remaining part and the whole can be made efficient.
Can standardize existing software in stages. . Further, even if one part is standardized in advance, the same standard information and synonymous data item set information can be applied to other parts, so that the overall uniformity can be maintained.

[Brief description of drawings]

FIG. 1 is a diagram showing a processing procedure of a first embodiment of the present invention.

FIG. 2 is a block diagram showing a hardware environment of each embodiment of the present invention.

FIG. 3 is a diagram showing a configuration example of a software product used in each embodiment of the present invention.

FIG. 4 is a diagram showing an example of a source program described in COBOL language.

5 is a diagram showing an example of an analysis result of a software product of the subsystem A of FIG.

FIG. 6 is a diagram showing an example of synonymous data item set information of the subsystem A of the first embodiment.

FIG. 7 is a diagram showing an example of assigning a standard name to the subsystem A of the first embodiment.

FIG. 8 is a diagram showing an example of a standard information creation result of the subsystem A of the first embodiment.

9 is a diagram showing an example of analysis results of software products of subsystem B of FIG.

FIG. 10 is a diagram showing an example of synonymous data item set information of the subsystem B of the first embodiment.

FIG. 11 is a diagram showing an example of a standard information creation result of the subsystem B of the first embodiment.

FIG. 12 is a diagram showing an example of overall synonymous data item set information according to the first embodiment.

FIG. 13 is a diagram showing an example of assigning an overall standard name according to the first embodiment.

FIG. 14 is a diagram showing an example of an overall standard information creation result of the first embodiment.

FIG. 15 is a diagram showing an example of a standard source program creation result of the first embodiment.

FIG. 16 is a diagram showing an example of the overall standard information creation result having the information of the highest data item name for the existing data item of the first embodiment.

FIG. 17 is a diagram showing an example of a standard record structure creation result of the first embodiment.

FIG. 18 is a diagram showing an example of a standard source program creation result with the standard record configuration of the first embodiment.

FIG. 19 is a diagram showing a processing procedure according to the second embodiment of the present invention.

FIG. 20 is a diagram showing an example of assigning a standard name to a subsystem B in the second embodiment.

FIG. 21 is a diagram showing a processing procedure of the third embodiment of the present invention.

FIG. 22 is a diagram showing an example of a synonymous data item set information creation result by the addition of the subsystem B in the third embodiment.

FIG. 23 is a diagram showing an example of standard name addition by adding a subsystem B in the third embodiment.

FIG. 24 is a diagram showing an example of a standard information creation result by adding a subsystem B in the third embodiment.

[Explanation of symbols]

101 software product division step 102 software product analysis step 103 synonymous data item set information creation step 104 standard name giving step 105 synonymous data item set information merging step 106 overall standard name giving step 107 in-program data item name changing step 1901 Step 2101 of assigning standard name using standard information of other subsystems Step 2101 of updating overall synonymous data item set information Step 2102 Adding / changing standard name

─────────────────────────────────────────────────── ───

[Procedure amendment]

[Submission date] October 28, 1992

[Procedure Amendment 1]

[Document name to be amended] Statement

[Correction target item name] 0026

[Correction method] Change

[Correction content]

A method of extracting the relationship between the data item name and the file allocation name, the relationship between the file allocation name and the file entity name, and the relationship between the data item name and the file entity name is described in, for example, Japanese Patent Laid-Open No. 3-294925. ing.

Front page continuation (72) Inventor Ichiro Naito 1099 Ozenji, Aso-ku, Kawasaki City, Kanagawa Prefecture System Development Laboratory, Hitachi, Ltd. Factory Information Systems Division

Claims (4)

[Claims] 1. A method for standardizing an existing software product, wherein the existing software product is divided into a plurality of parts, and the software product is analyzed for each division unit. The process of detecting the set of the following data items, creating the synonymous data item set information, and adding the standard data item name or the standard information consisting of the standard attribute, and the sharing of the software shared by the division units A process of merging related information together with synonymous data item set information including the same or synonymous data items in a plurality of division units to create synonymous data item set information of the whole or a plurality of division units and adding standard information. , Standard data items that determine the usage and definition of each data item belonging to the set of synonymous data items in the existing software product Universal, or software standardization method comprising a process of converting the standard attributes in addition to this, in that it consists of. 2. The software standardization method according to claim 1, wherein when standard information is given to each division unit, the division units are divided into units based on sharing relationship information such as files, databases and programs shared between the division units. Among the data items in the file, the database, and the program shared by the above, for the data items whose standard information has already been determined in other division units, the standard information in the other division units is adopted. Standardization method. 3. The software standardization method according to claim 1, wherein when the synonymous data item set information for each division unit is created, a file, a database shared between the division units,
Based on shared relationship information such as programs, synonymous data item set information for which other synonymous data item set information has already been created is added to the synonymous data item set information, and higher-order or entire synonymous data including that division unit A software standardization method characterized by creating item set information. 4. The software standardization method according to claim 1, wherein a plurality of division units of the synonymous data item set information are merged stepwise.