JPH0667871A - Automatic program updating system - Google Patents

Abstract

PURPOSE:To automate the updating work of another part program in a range influenced by the correction/change of an existing part program and the updating work of a synthetic source program formed by using the updated part program. CONSTITUTION:A preparation processing part 20 divides a source program 10 into plural part programs in each function, variable, or the like and registers each part detailed information 42 in a part file 40. Parts mutual relation information 41 expressing parts mutual relation among respective part programs is registered in the file 40. An updating processing part 70 judges an influenced range based upon the information 41 at the time of updating parts and updates the information 42 to be influenced. At the time of updating a synthetic source program, the parts detailed information of updated parts out of parts specified by a synthesis specification file 60 is extracted from the file 40 and substituted for corresponding parts in a synthetic program 50.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software development system for developing a new program using an existing part program, and the efficiency of update work when a registered part program is modified or changed. The present invention relates to a component program automatic updating method suitable for implementation.

[0002]

2. Description of the Related Art When a program is developed by reusing an existing part program, when a specification change or a defect absorption occurs in the reusing part program, a synthetic source generated using the part program. Efficient and reliable program update work is important for the entire software development cycle.

Conventionally, when a registered part program is modified or changed in an environment for newly developing a program using an existing part program, another registered part program that references the part program is registered. The work of identifying and updating the synthetic source program generated by using these component programs and all of them was done by hand.

As a recent publicly known example of the processing of the component program and its composite source program, for example, regeneration of the program and re-evaluation confirmation at the time of reusing the program described in Japanese Patent Laid-Open No. 2-302826 are automated. There is a method and a program reuse expert system that judges the program code and design information described in Japanese Patent Laid-Open No. 2-257216 by inference operation and extracts a necessary program. It does not describe the automation of the update work of the component program and the synthesis source program that are related to the change.

[0005]

DISCLOSURE OF THE INVENTION In the prior art,
Washing out other registered component programs related to the component program when a change is made to the registered component program, washing out a synthetic source program generated by using these component programs, and Since the updating work is manually performed, the work takes a lot of time and takes a long time, and there is a problem in reliability.

An object of the present invention is to automatically wash out and update a component program and a synthetic source program related to an existing component program when a modification is made, thereby improving the efficiency of the program updating process. , To ensure certainty.

[0007]

In order to achieve the above object, the present invention divides a source program into a plurality of component programs in units of functions and variables which are the constituent elements thereof, and detailed information of each component program ( In a software development support system that includes a component file storing detailed component information) and uses the component detailed information of the component file to generate a synthesis source program, the component files are mutually dependent on each other. When the information indicating the relationship (part mutual relationship information) is registered and a certain part program is updated, the range affected by the update of the part program is determined from the part mutual relationship information, and the part details of the affected part program are determined. The information is automatically updated.

Further, according to the present invention, in updating the synthesis source program, only the updated detailed component information is automatically generated from the detailed component information of each component program constituting the synthetic source program by referring to the component file. That is to replace it.

[0009]

According to the present invention, when the component program is registered in the component file, all references and referenced relationships between the component programs are identified in advance and the component mutual relation information is provided in the component file. Then, at the time of updating the component program, the referenced relation between the component programs that is derived by analyzing the referenced relation of the component program to be updated based on this component mutual relationship information is repeatedly searched in the upper direction, and is analyzed. Sequentially determine the component programs to be updated,
The detailed part information is updated. Then, the update flag is set to ON in the updated parts program. Next, in the update of the synthesis source program, the component program information taken into each synthesis source is acquired from the synthesis specification file in which the component configuration information of the synthesis source program is registered, and the update is performed to determine whether the relevant component program has been updated. The component detailed information of the relevant component program is replaced only with respect to the synthesis source that has determined the flag state and has incorporated the component program to be updated.

In this manner, the system automatically analyzes and determines the range of influence when a component program is modified and changed, updates the affected component program, and deletes all synthesized source programs that incorporate the component program. Parts can be replaced automatically.

[0011]

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

FIG. 1 shows a block diagram of an embodiment of the present invention. In the figure, 10 is a source program, 20 is a generation processing unit that generates a component file and a composite source program, 30 is a conversation device including a keyboard, display, etc., 40 is a component file, 50 is a source file, 60
Is a combination designation file in which the name of the component program to be combined is registered, 70 is an update processing unit for updating the component file and the combination source file, and 80 is an interface control unit.

The processing of the generation processing section 20 is the component generation processing 2
1 and synthetic source generation processing 22. In the component generation process 21, the interface controller 8 is operated by the conversation device 30.
Based on a user command input through 0, the source program 10 to be registered is divided into a plurality of component programs in units of functions, variables, etc., and the component mutual relationship information 41 showing the mutual dependency between the component programs.
And detailed parts information 4 which is the detailed contents of the parts program.
2 is generated and registered in the parts file 40. In the synthesis source generation processing 22, the component detailed information 42 of the corresponding component program group is input from the component file 40 by the component program name designated by the synthesis designation file 60, and the synthesis source program 50 is generated.

The processing of the update processing unit 70 is the component update processing 7
1 and synthetic source update processing 72. In the component update processing 71, the interface control unit 8 from the conversation device 30.
Based on the user command input through 0, the detailed parts information 42 in the parts file 40 is specified by the parts mutual relation information 41, and the parts program specified by the user command and the corresponding parts of the parts program which refers to the parts program Update detailed information. In the synthesis source update process 72, the component program changed in the component program name designated in the synthesis designation file 60 is
The component detailed information 42 of the component file 40 is taken out, and the component detailed information of the relevant component program in the synthesis source program 50 is replaced.

In the synthesis designation file 60, a group of component program names for which the user has designated synthesis using the conversation device 30 is registered through the interface control unit 80.

Explaining the example shown in FIG. 1, in the component generation processing 21, the source program 10 is changed to A, B, C ,.
It is divided into four parts programs of D, and parts file 40
The component mutual relation information 41 and the component detailed information 42 of these component programs A, B, C, D are registered in the. In the example, the component program A is referred to by the component programs C and D, and further, the component program B is referred to by the component program C. In the synthesis source generation processing 22, the component program names A, B, C, D are extracted from the synthesis designation file 60 designated by the user, and the corresponding component programs A, B, C, D from the component file 40 Information 42 is taken out, and the synthesis source program 5
Generates 0. On the other hand, when the user modifies a part of the component program A, the component file 40 for the component program A specified by the user in the component update processing 71.
The corresponding part detailed information 42 in the inside is updated, and at the same time, the corresponding part detailed information 42 in the part file 40 corresponding to the part programs C and D referring to the part program A is updated from the part mutual relationship information 41. . Then, in the composition source process 72, the detailed parts information 42 of each part corresponding to the updated parts program A, C, D among the programs A, B, C, D specified in the composition specification file 60.
Is selected and acquired from the component file 40, and the component programs A, C, and D in the synthesis source program 50 are replaced with the updated detailed component information.

FIG. 2 shows an example of the structure of the parts mutual relationship information 41 and the parts detailed information 42 in the parts file 40. In addition,
In FIG. 2, the component programs A, B, C, D shown in FIG.
It is shown about the example of.

A component program list list 411 in the component mutual relation information 41 shows a list of component programs. For each component program, a component program name, a component update flag indicating whether or not a component update has been performed,
Also, it has a pointer value (head pointer, number, etc.) to the component referred information 412 for retrieving another component program name that refers to the component program. The component detailed information 42 is detailed information 421, 423 of each component program obtained by dividing the source program in units of variables and functions.
424 and the like. The component referenced information 412 in the component mutual relationship information 41 is for collectively registering a component program name of each component program when another component program refers to the component program.

FIG. 3 shows how the detailed parts information 42 shown in FIG. 2 is updated to the detailed parts information 43.
In this example, “int” of the component program A of 421 is
The variable declaration "x;" has an update component program A of 431
Has been updated to "char * x;". At this time, in the component program C of 423 which refers to the component program A, the substitution statement “x =
By updating the declaration information of x, it is necessary to change “1;” to “x =“ 1 ”;” in the update component program C of 433. Similarly, the component program A is referenced 42.
In the component program D of No. 4, it is necessary to change to “x =“ 10 ”;” in the updated component program D of 434. For such a program update, processing is efficiently performed using the component mutual relationship information 41 of FIG. In this example, for the updated component program A, the component programs C and D are obtained from the component referred information 412 of the component mutual relationship information 41, and the component programs C and D are updated.

FIG. 4 shows a flowchart of the component update processing 71 for updating the component file 40 in the update processing section 70 of FIG. Further, FIG. 5 shows a specific example of the state transition of the component stack used in the update processing. Hereinafter, a case where the component program A is updated will be described as an example with reference to FIGS. 2 and 3.

First, as a part file update process, a part program A for making corrections / changes from the part file 40.
Is taken out and pushed as an updated part onto the parts stack (step 200). FIG. 5 shows this state.
Next, the component detail information 42 of the updated component is modified / changed (step 210). That is, in FIG. 3, the component program A is changed from 421 to 431. At this time, the component program list list 4 in the component mutual relationship information 41
The update flags corresponding to the 11 update components are turned on (step 220). That is, the component update flag corresponding to the component program name A in the component program list list 411 of FIG. 2 is turned on. Next, the referenced information of the component program is searched from the component mutual relationship information 41 for this updated component (step 230). Then, it is checked whether there is a referenced part program for the updated part, and if there is, check whether all the referenced part programs have been updated (step 240). One is taken out as an updated part and pushed to the parts stack (step 260). In the case of FIG. 2, the component program list list 411 is searched, the component referenced information pointer of the component program name A is traced, and the component program names C and D are obtained from the component referenced information 412. Here, the component program name C is taken out and pushed onto the component stack. FIG. 5 shows this state.

Next, the processing of steps 210 and 220 is repeated for this component program C. That is, in FIG. 3, the detailed parts information of the parts program C is changed from 423 to 4
33, and the component update flag corresponding to the component program C in the component program list of FIG. 2 is turned on. Next, the relationship of the referenced parts to the parts program C of the updated parts is checked (steps 230 and 240). From FIG. 2, there is no referenced parts program in the parts program C, so the parts program C is popped up from the parts stack. (Step 250). FIG. 5 shows this state. That is, the processing related to the component program C as the updated component is completed.

Next, it is checked whether the parts stack is empty (step 270). If not empty, the top part of the parts stack is set as the updated part (step 280). From FIG. 5, here, the component program A becomes an updated component again. In step 240, the presence / absence of the referenced component of the component program A and the processing status thereof, if any, are checked again. Here, of the referenced component programs C and D of the component program A, C has already been processed, but D remains unprocessed. Therefore, in step 260, the component program D is extracted as an updated component,
Push onto a parts stack. FIG. 5 shows this state.

Next, the processing of steps 210 and 220 is performed for this component program D, the detailed component information of the component program D is changed from 424 to 434 as shown in FIG. 3, and the component program list in FIG. The component update flag corresponding to the component program D is turned on. next,
The process proceeds to steps 230 and 240 to check the referenced component relationship of the component program D, but since there is no such reference, the process proceeds to step 250 to pop up the component program D from the component stack. FIG. 5 shows this state.

Next, it is checked whether or not the component stack is empty (step 270). If it is not empty, the top component of the component stack is set as the updated component (step 280). From FIG. 5, the component program A becomes an updated component again. In step 240, the presence / absence of the referenced component of the component program A and the processing status of the referenced component, if any, are checked again.
At this point, all of the referenced parts programs C and D have been processed, so in step 250, the parts program A is popped up from the parts stack. In Figure 5,
This is the state. That is, the update process related to the component program A is completed.

In step 270, it is checked whether or not the parts stack is empty. If the parts stack is empty, it is determined whether or not the above parts update check has been performed for all updated parts (step 290). If there is a processing object, the processing from 220 to 280 is repeated. If the update processing check has been completed for all the update components, the update processing of the component file 40 ends.

FIG. 6 shows a flow chart of the synthesis source update processing 72 for updating the synthesis source program 50 in the update processing section 70 of FIG.

First, one of the synthesis designation files designated by the user is taken out (step 310). Next, one component program name designated by this synthesis designation file is taken out (step 320), and the component program list list 411 of the component mutual relationship information 41 in the component file 40.
, The part update flag of the corresponding part program name is O
Check if N is set (step 33).
0). If it is ON, the component program to be updated in the synthesis source program 50 is replaced with the updated component detailed information 42 in the component file 40 (step 3).
40). If it is not ON, the process of step 340 is skipped. Next, it is determined whether or not the processes of steps 320 to 340 have been completed for all the component programs in the synthesis designation file 60 (step 350). If not already processed, steps 320 to 340 are performed for the unprocessed component programs. The process of is repeated. If all of the files have been processed, it is further determined whether or not all of the synthesis specification files specified by the user have been processed (step 36).
0) If not already processed, the processes of steps 310 to 350 are repeated for the unprocessed combination designation file.
Then, when the processing has been completed for all the composition designation files, the composition source program update processing ends.

Thus, in the case of the synthesis designation file 60 shown in FIG. 1, the designated component program name A,
Of B, C, D, parts program list list 4 of FIG.
As shown in FIG. 11, the updated component detailed information (431, 433, 434 in FIG. 3) corresponding to the component program names A, C, D for which the component update flag is ON is read from the component file 40, The detailed parts information of the corresponding parts programs A, C, and D in the synthesis source program 50 are replaced.

[0030]

As described above, according to the present invention,
When a user updates a program registered as a component program in a component file, the system automatically analyzes and determines the range of influence, updates the component program in the range of influence, and synthesizes it using the corresponding component program. The program part can be updated at the same time. In this way, since the correction / change feedback of the component program can be reliably and automatically performed, the efficiency and reliability of the program development work using the component program can be improved.

[Brief description of drawings]

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

FIG. 2 is a data configuration diagram showing an example of component mutual relationship information and component detailed information of a component file in FIG.

FIG. 3 is a diagram showing a specific example of updating detailed component information.

FIG. 4 is a flowchart for explaining a component file update process.

5 is an operation transition diagram of a component stack during the update process of FIG.

FIG. 6 is a flowchart illustrating an update process of a combined source program.

[Explanation of symbols]

 10 Source Program 20 Generation Processing Unit 21 Component Generation Process 22 Synthesis Source Generation Process 30 Conversation Device 40 Component File 41 Component Mutual Relationship Information 42 Component Detailed Information 50 Synthesis Source Program 60 Synthesis Designation File 70 Update Processing Unit 71 Component Update Process 72 Synthesis Source Update process 80 Interface control unit

Claims (2)

[Claims] 1. A component file is provided, in which a source program is divided into a plurality of component programs in units of functions and variables that are constituent elements of the source program, and detailed information of each component program (hereinafter, referred to as detailed component information) is stored. In a software development support system for generating a synthesis source program by using the detailed parts information of the parts file, in the parts file, information indicating mutual dependence between the respective parts programs (hereinafter referred to as parts mutual relationship information and (Referred to as), and when a certain component program is updated, the range in which the update of the component program influences is determined based on the component mutual relation information, and the component detailed information of the affected component program is updated. Automatic program updating method. 2. The automatic program updating method according to claim 1, wherein only the updated part detail information is replaced among the part detail information of each part program constituting the composition source program by referring to the part file. A program automatic update method characterized in that