JPH0713750A - Program module control method - Google Patents

Abstract

PURPOSE:To surely grasp the relationships of modules in an entire system by taking the latest module constitution and a list of registration collections out of an original program library group at a present time point. CONSTITUTION:A program module control method includes an original program converting process which converts an original program group into an original program image file, a hierarchical module converting process which divides the image file into plural hierarchical level modules, a module control connecting process which connects the hierarchical level modules to a main program to produce a main program connection file, a hierarchical structure printing process which prints a hierarchical structure list out of the connection file, and a module/registration list printing process which prints the lists of modules and registration collections out of the image file. Then the files are produced from the image file for each hierarchical level in the hierarchical module converting process, and the divisions between the submodules and the registration collections and the names are added for each hierarchical level with the main program defined as a retrieving iterm.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a program module management method, and more particularly to a program module management method using service program software.

[0002]

2. Description of the Related Art FIG. 7 is a flowchart showing an example of a conventional program module management method.

As shown in FIG. 7, a conventional method for managing program modules (modules) is to create a common module and a common registry in advance in the detailed system design (system remodeling work) of step 51, and to specify the specifications as needed. Although one detailed design is completed by describing it in the document, the management of the source program during the system construction and the maintenance after completion, especially the management of the module configuration, is managed manually by the documents. .

However, in such a management means, the judgment as shown in step 52 occurs, and it is difficult to revise the document each time the change is made in a system in which there are many module divisions or registration collections (copy originals). Yes, and when maintaining or newly registering a module,
Management omissions occur frequently.

When a certain module is maintained in the system alone or in the test run of the system, in principle, the execution programs of the related main modules must be recombined. If there is only one module, there is no problem if you know the information about that part, but if you miss the management of the module of the entire system, it will not operate normally in a certain subsystem,
For this reason, extra man-hours for system development and maintenance are required, and such problems are more likely to occur as the system scale increases.

In step 53, the hierarchical structure of the module is represented graphically for each level, but this work is very troublesome, and when the module is changed, the manual document management cannot be completely performed. is there.
For this reason, if the maintenance is complete (step 54
And step 55) is good, but if the maintenance was not completely done (step 54 and step 56)
Have trouble.

[0007]

As described above, in the conventional method of managing a program module, since module management is performed manually, a system in which there are many module divisions or registration collections (copy original text) in system construction. As for the system, the larger the system size, the more often it is not possible to write a complete module relation diagram. In addition, when maintenance work (maintenance) of a submodule or registry occurs, it requires a lot of work to grasp all the modules in the system related to the submodule or the registry that performed the maintenance work. However, there is also a problem that system failure occurs when management is missed. Such problems become more serious as the level of the hierarchical structure between modules becomes deeper.

[0008]

A program module management method according to the present invention comprises a source program conversion process for converting a source program group into a source program image file, and the source program image file converted by the source program conversion process. Module conversion processing for dividing a hierarchy level module into a plurality of hierarchies, and module management combination processing for combining the plurality of hierarchy level modules converted by the hierarchy module conversion processing into a main program to create a main program combination file And a hierarchical structure printing process for printing a hierarchical structure list from the main program combined file created by the module management combining process,
A module / registry list printing process for printing a list of modules and a list of registrations from the source program image file, wherein the source program image file converted by the source program conversion process is converted into the hierarchical module conversion process. In which a file for each hierarchical level is created, and the main program is used as an index item to add the division and name of the sub-module and the registry for each hierarchical level.
The number of layers of the layer level module divided by the layer module conversion processing is six layers.

[0009]

Embodiments of the present invention will now be described with reference to the drawings.

FIG. 1 is a flow chart showing an embodiment of the present invention, FIG. 2 is a flow chart showing details of the source program conversion processing of the embodiment of FIG. 1, and FIG. 3 is a detail of hierarchical module conversion processing of the embodiment of FIG. 4 is a flowchart showing
1 is a flow chart showing the details of the module management combining process of the embodiment of FIG. 1, FIG. 5 is a flow chart showing the details of the hierarchical structure printing process of the embodiment of FIG. 1, and FIG. 6 is a module / registry list of the embodiment of FIG. 6 is a flowchart illustrating details of print processing.

In FIG. 1, step 1 is a source program conversion process for converting a source program group into a source program image file. That is, as shown in FIG. 2, a person reads a source program library written in a business processing language (step 11), judges whether or not it is the end of the library (step 12), and when it is not the end. Only the program identification information of the source program is extracted, the contents are created as a program image file and stored in the source program image file (step 13).

Step 2 is a layer module conversion process for dividing the source program image file converted by the source program conversion process of step 1 into first layer level modules to sixth layer level modules. That is, as shown in FIG. 3, first, the source program image file created in step 1 is read (step 14), and it is judged whether or not it is the end of the file (step 15). Only the program information is written in the file to create a hierarchical level 1 file (step 16). Next, the hierarchy level 1 file created in step 16 is read (step 17), it is judged whether or not it is the end of the file (step 18), and if it is not the end, the source program conversion process of step 1 is executed. The program of the hierarchy level 1 file is searched for from the source program image file converted by (step 19), and the submodule calling instruction and the collection (copy phrase) therein are output as level 2 to the hierarchy level 2 file (step 19). 20).
After that, the above operation is performed up to level 6 (in reality, the level 6 level is sufficient), and the level 3 file
A hierarchy level 6 file is created (step 21 to step 36).

Step 3 is a module management coupling process for coupling the first hierarchical level module to the sixth hierarchical level module converted by the hierarchical module conversion process of step 2 to the main program to create a main program coupling file. That is, as shown in FIG. 4, the files of the hierarchical levels 1 to 6 are combined into modules by the same program until the end of the file (step 38) with the main program name as an index item (key item). Write to the combined file (main program combined file) (step 39).

Step 4 is a hierarchical structure printing process for printing a hierarchical structure list from the main program combined file created in the module management combining process of step 3.
That is, as shown in FIG. 5, the module combination file is read (step 40), and a module hierarchical structure list is created (step 42) until the file is completed (step 41). This list is organized for each main module and is developed as a hierarchical structure from level 1 to level 6. Therefore, this makes it possible to see the hierarchical structure of the modules at a glance.

Step 5 is a module / registry list printing process for printing a list of modules and a list of registrations (original copy) from the source program image disk file converted by the conversion processing of the source program in step 1. . That is, as shown in FIG. 6, the source program image file created in step 1 is read (step 43), and the contents thereof are included for each module unit or each registration collection unit until the file ends (step 44). All the main module names and sub module names and the original text names of the library (copy phrase) are printed as a list (step 45).

[0016]

As described above, the method of managing a program module of the present invention enables the latest module configuration and the list of registrations to be taken out from the current source program library group, thereby making the system There is an effect that it is possible to accurately grasp the relationship of all modules, and there is an effect that it is possible to improve the maintainability for the maintenance and management of the program during the system construction and after completion. Therefore, there are effects that the quality and reliability of software can be improved, the effort for creating a document can be reduced, and the occurrence of mistakes can be reduced.

[Brief description of drawings]

FIG. 1 is a flowchart showing an embodiment of the present invention.

FIG. 2 is a flowchart showing details of a source program conversion process of the embodiment of FIG.

FIG. 3 is a flowchart showing details of hierarchical module conversion processing of the embodiment of FIG.

FIG. 4 is a flowchart showing details of module management connection processing according to the embodiment of FIG.

FIG. 5 is a flowchart showing details of a hierarchical structure printing process of the embodiment of FIG.

FIG. 6 is a flowchart showing details of a module / registry list printing process of the embodiment of FIG.

FIG. 7 is a flowchart showing an example of a conventional program module management method.

[Explanation of symbols]

 1-5 ・ 11-45 ・ 51-56 steps

Claims (2)

[Claims] 1. A source program conversion process for converting a source program group into a source program image file,
A layer module conversion process for dividing the source program image file converted by the source program conversion process into a plurality of layer level modules, and the plurality of layer level modules converted by the layer module conversion process as a main program. A module management combining process for creating a main program combined file by combining them, a hierarchical structure printing process for printing a hierarchical structure list from the main program combined file created by the module management combining process, and a module from the source program image file Module for printing the list of the list and the list of the registry, and a process for printing the library list, wherein the source program image file converted by the source program converting process is the hierarchical module. Managing program modules, characterized in that it includes creating a file hierarchy level each at conversion process adds classification and designation of the library and submodule hierarchical level each said main program as an index item. 2. The program module management method according to claim 1, wherein the number of layers of the hierarchical level module divided by the hierarchical module conversion process is six layers.