JP2000200185A - Version management device for program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To eliminate the situation that the version can not be recognized for the source program used for preparation of an application program. SOLUTION: A data base 21 stores the respective version numbers of the application program and the source program utilized for the preparation in relation. In this case, when a source generator 22 is activated and the version number of the application program is inputted, the corresponding source program is obtained from the data base 21. After it is edited in an editor 23, when a prescribed version registration command is issued, the version number is updated and registered in the data base 21 by a version manager 24. Thus, the source program is edited by an application program unit and the efficiency in bug analysis or the like is improved.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a program version control device.

[0002]

2. Description of the Related Art Heretofore, as a version control device of this type of program, Japanese Patent Application Laid-Open No. 6-8359 by the present applicant has been proposed.
No. 6 is known. In the technique disclosed in the publication, every time the source program is changed, the update date and time, the version number increased by the update, and the changed part from the parent source program are acquired and written in the version management database. To reproduce the past state of the source program due to reasons such as bug analysis, a date parameter or a version number parameter is specified. Then, a corresponding source program is created from the current version source program and the version control database.

[0003]

In the above-mentioned prior art, there is room for improvement in the following points. That is,
The above-described conventional technique is excellent in that the state of the past source program can be reproduced and the procedure of bug analysis becomes easy. However, since a bug is actually discovered at the time of execution of an application program, it may not be clear which version of the source program is used by the application in question. Was sometimes applied.

SUMMARY OF THE INVENTION The present invention has been made in view of the above circumstances, and, when a source program is edited by bug analysis or the like, a program version control apparatus capable of simplifying the procedure and improving work efficiency. For the purpose of providing.

[0005]

In order to achieve the above object, the invention according to claim 1 stores each version of an application program in association with a source program used to create an application program of each version. A program storage unit, a source program acquisition unit that acquires a corresponding source program from the program storage unit in response to input of a version number of an application program, and a source program acquired by the source program acquisition unit. There is provided a program editing means for storing the edited source program and the version number of the application program updated by the editing in the program storage means in association with each other.

That is, the program storage means stores each version of the application program in association with a source program used for creating the application program of each version. Here, when a bug or the like is found in the application program and the source program is corrected, the version number of the application program is input. Then, the source program acquisition means acquires the corresponding source program from the program storage means. Here, the obtained source program can be edited by the program editing means, and the program editing means associates the edited source program with the version number of the application program updated by the editing to the program storage means. Remember.

Although the version number of the application program is managed, the version number of the source program may be similarly managed. As an example of a suitable configuration in that case,
According to a second aspect of the present invention, in the version control apparatus for the program according to the first aspect, the source program is version-managed, and the program storage means comprises:
Each source program is the initial version of the source program,
The initial version number is stored as difference information from the source program, and the source program obtaining means obtains a source program corresponding to the initial version source program and the difference information based on the difference information. After editing the source program, the difference information is extracted and stored in the program storage means.

That is, the program storage means stores the entire source program of the initial version number, but stores the source program with the updated version number as difference information from the initial version number. Therefore, the source program obtaining means obtains a source program corresponding to the source program of the initial version number and the difference information. Further, the program editing unit extracts difference information between the edited source program and the source program of the initial version number, and stores the difference information in the program storage unit.

In the case of storing the difference information here, a configuration may be used in which the difference from the initial version number is strictly stored for each of the source programs whose version numbers have been updated, but, of course, the configuration is limited to this configuration. Never. As an example, the invention according to claim 3 is a program version management device according to claim 2, wherein:
The difference information is configured by accumulating sequential difference information from the parent source program for each version number update. That is, every time the version is updated from the initial version of the source program, the sequential difference information from the parent source program is acquired,
This sequential difference information is accumulated to be difference information from the initial version number.

In the case of using the sequential difference information,
As an example of a specific configuration of the source program acquisition means, the invention according to claim 4 is the program version management device according to claim 3, wherein the source program acquisition means is configured to execute the initialization from the source program to be acquired. The parent program is sequentially traced back to the source program of the version number to obtain the sequential difference information, and the sequential version difference information is applied in a reverse order to the acquisition order, and the source program of the initial version number is changed. It is configured to acquire a source program. In other words, when the source program obtaining means obtains a source program, it sequentially obtains difference information from the source program while going back to the initial version number, and changes the source program to the initial version number while applying it in the reverse order of the order in which it was obtained. Add.

The program editing means extracts the sequential difference information from the parent source program. As a specific example of the extracting method, the invention according to claim 5 is based on any one of claims 3 and 4 In the version control device for a program described in the above item (1), the program editing means is configured to store the edited source program as a temporary file, and compare the temporary file with a parent source program to sequentially extract difference information. . That is, the program editing means does not directly edit the parent source program, but edits and saves it as another temporary file. Then, the stored temporary file is compared with the original parent source program to sequentially extract difference information.

By the way, an application program is not always created by one source program. For example, for a process that can be used for general purposes, a source program is created as one function and linked when necessary. Therefore, as an example of a configuration suitable for such a case, the invention according to claim 6 is the program version management device according to any one of claims 1 to 5, wherein the application program includes a plurality of source programs. It is created by using a program, and the program editing means is configured to be able to edit the plurality of source programs collectively. That is, the program editing means can edit a plurality of source programs used for creating the application at once. For example, one editing screen may be divided to display each source program, or a plurality of editing windows may be displayed corresponding to each source program, and various methods can be applied.

[0013]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a schematic block diagram showing a hardware configuration of a program version management apparatus according to an embodiment of the present invention. In the figure,
The computer 10 includes a CPU 11, a ROM 12, and a RAM.
13 and the like, and the hard disk 20, the output device 30, the input device 40, and the like are connected via an interface circuit (not shown). That is, the computer 10 can access the hard disk 20, the execution results of the program are output from the output device 30, and the input device 40
And the like can be input via the. The output device 30 corresponds to a display or a printer, and the input device 40 corresponds to a keyboard or a mouse.

The purpose of the program version control device is to control the version of a source program used when creating an application program. It is assumed that the application program in the present embodiment is generated by compiling a plurality of source programs, respectively, and statically linking the resulting modules. The hard disk 20 is provided with various programs for supporting the creation and modification of such applications, and can be executed by the computer 10 when necessary. next,
These support programs will be described with reference to FIG.

The source program of each version is managed by the database 21. More specifically, the database 21 manages the version information 21a of the source program and the version information 21b for each application. The version information 21a of the source program is tabulated according to the type of the source program, and the "version number", "parent version number",
A record consisting of three fields of "contents" is stored.

FIG. 3 shows an example of a record in a table for a certain source program A. In this case, 4
There are two records, which mean the following: That is, Vers
Edit the source program A of ion1 and select Versio
This means that the source program A of Version 2 was created by editing the source program A of Version 2 while creating the source program A of n2 and Version 3. In each record, the parent version number field stores the version number of the source program before editing, and the content field stores sequential difference information that is a change from the source program before editing. However, Versio
For the n1 source program A, there is no parent source program, so there is no data in the parent version number field, and the source program A itself of Version 1 is stored in the content field.

FIG. 4 shows an example of a record in a table for another source program B. In this case, only the record for Version 1 exists. Therefore, it means that the source program B of Version 1 has not been edited at all.

FIG. 5 shows an example of a record in a table for another source program C. In this case, records for Version 1 and Version 2 exist. Therefore, Version 1
Means that the source program C of Version 2 was edited by editing the source program C of No. 2.

When editing such a source program individually, the source generator 22 is started,
Enter the source program name and version number to be edited. Then, the source generator 22
The target source program is output according to the flowchart shown in FIG.

In FIG. 2, in step S110, the version information 21a of the source program is searched, a record corresponding to the input source program name and version number is obtained and stored in a predetermined list.
In the next step S120, it is determined whether or not a parent version number exists from the acquired record. Here, if the parent version number exists, step S130
Moves the survey to its parent version number record,
In step S110, the record is similarly stored in the list. Thereafter, the parent version number is sequentially stored in the list until it no longer exists. That is, step S110
In the processing from S130 to S130, the records of the respective version numbers are stored in the list while sequentially going back the records of the parent version numbers from the version number to be edited to Version1.

In step S140, Version1
Is read, and the next step S150
It is determined whether or not there is a record stored in the list.
If it is determined that there is no record stored in the list, the source program read in step S160 is output as it is. For example, for a source program that has not been edited from Version 1 like the above-described source program B, the record does not have a parent version number, so that no record is stored in the list and the source program of Version 1 is output. .

On the other hand, when it is determined that the record stored in the list exists, the difference information is sequentially obtained by tracing the record stored in step S170 in reverse. That is, when there are a plurality of records in the list, the difference information is sequentially acquired from the record having the lower version number.
Then, after making a change to the source program of Version 1 based on the sequential difference information, the record is deleted from the list and the process returns to step S150, and the same processing is repeatedly executed until there are no more records in the list. Then, the source program to be edited is restored, and the source program is output.

The source program output from the source generator 22 is passed to the editor 23 as a current version source program. Since the editor 23 displays the current version source program on the editing screen, the program creator edits the current version source program on the editing screen. When the editing is completed, a source program version registration command is issued according to a predetermined operation. In addition,
Here, the edited source program is stored as a temporary file.

When a version registration command of the source program is issued from the editor 23, the version manager 24 starts. This version manager 24
Compares the temporary file saved by the editor 23 with the current version source program, extracts a changed portion from the current version source program, and sequentially generates difference information. At the same time, a new version number is assigned to the edited source program, and a record including the version number, the parent version number, and the generated sequential difference information is stored in the version information 21 of the source program.
Register in a.

As described above, in this embodiment, since the source program of each version is stored as sequential difference information from the parent source program, the required storage capacity of the hard disk can be reduced. That is, when each version of the source program is stored in a complete format, the disk usage rate becomes redundant because of the mutual overlap, and according to the present embodiment, such redundancy does not occur. And the disk can be used efficiently.

In this embodiment, any past version of the source program can be restored by inputting the source program name and the version number to the source generator 22. Therefore, it is not necessary for the program creator to separately manage the version of the source program, and the working procedure is simplified, which is preferable.

The source program created as described above is finally compiled, and an application program is created by linking the modules generated as a result. Then, various tests are performed with the application program created in this way, and it is tested whether or not the operation is performed as specified. Here, when a bug is found in the application program, it is necessary to investigate the cause of the bug and correct the source program. Of course, in order to make such a correction, it is necessary to know which version of the source program was used to create the application program. However, if the source program is modified many times and the version is updated, it may become impossible to know which version of the source program was used.

Therefore, in the present embodiment, the source program is managed on an application basis. More specifically, in the database 21,
It is managed as version information 21b for each application. FIG. 7 shows a record example of the version information 21b for each application. In the figure, each record is composed of a version number of an application program, a source program name and a version number used for creating the application program. As is clear from the figure, it can be seen that the version number of the source program actually used is different for each version number of the application program.

In order to register a record in the version information 21b for each application, the editor 23 is started, and a version registration command of the application program is issued according to a predetermined operation. Then, the version manager 24 starts up, searches the version information 21a of the source program, obtains the registered source program name and all version numbers, and
Pass to 3. Then, since the editor 23 displays the source program name and all version numbers, the program creator appropriately selects the version number of each source program and issues a predetermined registration command in association with the version number of the application program. . Then, the version manager 24 registers as a record as shown in FIG. 7 based on the registration command.

On the other hand, the version number of the application program can be input to the source generator 22. In this case, the source generator 22 outputs the version information 21 for each application.
b to retrieve the corresponding record. Then, the version number is detected for each source program included in the record, and the target source program is reproduced and output according to the procedure shown in FIG.

For example, assume that Version 4 is input to the source generator 22 as the version number of the application program shown in FIG.
In this case, according to the procedure shown in FIG.
Source program A, version 1 source program B and version 2 source program C
Is generated and output. Of course, the source program output here can be edited by the editor 23. More specifically, the source program may be displayed in an individual editing window by the editor 23 and edited.

As described above, in the present embodiment, by inputting the version number of the application program, the source program used to create the application program can be easily edited.
The work efficiency at the time of bug analysis will also be improved.

Next, the operation of this embodiment configured as described above will be described. When the registered source programs are to be individually edited, the source generator 22 is started, and the name and the version number of the source program to be edited are input. Then, the source generator 22 outputs the version information 2 of the source program in the database 21.
1a, retrieves the corresponding record, and stores it in a predetermined list (step S110). Then, it is determined from the acquired record whether or not the parent version number exists (step S120). If the parent version number exists, the investigation target is moved to the record of the parent version number (step S130), and the record is stored in the list in the same manner (step S11).
0). Thereafter, similarly, the parent version number is sequentially stored in the list until it no longer exists.

When the storage of the list is completed, the Versio
The source program of n1 is read (step S14).
0), it is determined whether or not there is a record stored in the list (step S150). If there is no record stored in the list, the read source program is output as it is (step S160). For example, for a source program that is not edited at all from Version 1, such as the source program B described above,
Since the parent version number does not exist in the record, the record is not stored in the list, and the source program of Version 1 is output.

On the other hand, when there is a record stored in the list, the sequential difference information is obtained by tracing the record stored in the list in reverse, and the Ver.
After making a change to the source program of section1, the record is deleted from the list (step S170).
Thereafter, the same process is repeated until there are no more records in the list. Then, the source program to be edited is restored and the source program is output.

The output source program is passed to the editor 23 as a current version source program. Since the editor 23 displays the current version source program on the editing screen, the program creator edits the current version source program on the editing screen. Then, the edited source program is saved as a temporary file. When the editing is completed, a source program version registration command is issued according to a predetermined operation.

When this version registration command is issued, the version manager 24 starts. Then, the temporary file saved by the editor 23 is compared with the current version source program, and a changed portion from the current version source program is extracted to sequentially generate difference information. At the same time, a new version number is assigned to the edited source program, and a record including the version number, the parent version number, and the generated sequential difference information is registered in the version information 21a of the source program.

On the other hand, to register a version number for each application, the editor 23 is activated, and a version registration command of the application program is issued according to a predetermined operation. Then, the version manager 24 is activated and the version information 21 of the source program is
a, and retrieves all registered source program names and version numbers and passes them to the editor 23. Then, since the editor 23 displays the source program name and the version number, the program creator appropriately selects the version number of each source program and issues a predetermined registration command in association with the version number of the application program. Then, the version manager 24 registers in the version information 21b for each application based on the registration command.

On the other hand, when the source generator 22 is activated and the version number of the application program is input, the source generator 22 searches the version information 21b for each application and acquires a corresponding record. Then, the version number is detected for each source program included in the record, and the target source program is reproduced and output according to the procedure shown in FIG. Of course, the source program output here can be edited by the editor 23. Then, similarly, after registering the version number of the edited source program, the version number of each application is registered.

As described above, the database 21 stores each version number of the application program and the source program used for its creation in association with each other. When the source generator 22 is activated and the version number of the application program is input, Since a corresponding source program is acquired from the database 21 and edited by the editor 23 and then a predetermined version registration command is issued, the version number is updated by the version manager 24 and registered in the database 21. The source program can be edited for each application program, and work efficiency such as bug analysis can be improved.

[0041]

As described above, according to the present invention, by inputting the version number of an application program, the source program used for its creation can be acquired and edited, thereby facilitating procedures such as bug analysis. A program version control device capable of improving work efficiency can be provided. According to the second aspect of the present invention, the source program whose version has been updated is stored as difference information from the initial version, so that the required storage capacity can be reduced. Further, according to the third aspect of the invention, since the sequential difference information from the parent source program is stored every time the version number is updated, the required storage capacity can be minimized.

Further, according to the invention according to claim 4,
When the sequential difference information is used, a specific method of reproducing a source program can be provided. further,
According to the invention according to claim 5, it is possible to provide a specific extraction method of the sequential difference information. Further, claim 6
According to the present invention, a plurality of source programs can be edited collectively, so that there is no need to edit them individually,
Further, work efficiency can be improved.

[Brief description of the drawings]

FIG. 1 is a schematic block diagram illustrating a hardware configuration of a program version management device according to an embodiment of the present invention.

FIG. 2 is a block diagram showing a program configuration provided in a hard disk.

FIG. 3 is a diagram showing an example of a record in version information of a source program.

FIG. 4 is a diagram showing an example of a record in version information of a source program.

FIG. 5 is a diagram showing an example of a record in version information of a source program.

FIG. 6 is a flowchart showing a procedure for reproducing a source program.

FIG. 7 is a diagram illustrating an example of a record in version information for each application.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 10 Computer 11 CPU 12 ROM 13 RAM 20 Hard disk 21 Database 21a Version information of a source program 21b Version information of each application 22 Source generator 23 Editor 24 Version manager 30 Output device 40 Input device

Claims (6)

[Claims] 1. A program storage means for storing each version of an application program in association with a source program used for creating each version of the application program, and the program according to an input of the version of the application program Source program acquisition means for acquiring the corresponding source program from the storage means; and editing the source program acquired by the source program acquisition means, the version number of the edited source program and the application program updated by the editing. And a program editing means for storing the program in the program storage means. 2. The program version control device according to claim 1, wherein the source programs are version-controlled, and the program storage means stores each source program as an initial version of a source program, and The source program obtaining means stores the source program corresponding to the initial version number based on the difference information, and stores the source program corresponding to the initial version number source program based on the difference information. A program version management device, wherein after editing a source program, the difference information is extracted and stored in the program storage means. 3. The program version control device according to claim 2, wherein the difference information is configured by accumulating sequential difference information from a parent source program for each version number update. Version control device. 4. The program version control device according to claim 3, wherein the source program acquiring means sequentially traces back the parent source program from the source program to be acquired to the source program of the initial version number. A program version management device for acquiring the difference information and acquiring the source program by modifying the source program having the initial version number while applying the sequential difference information in the reverse order of the acquisition order. . 5. The program version control device according to claim 3, wherein the program editing means stores the edited source program as a temporary file, and stores the edited source program in a temporary file. A program version control device for comparing source programs and successively extracting difference information. 6. The program version control device according to claim 1, wherein the application program is created using a plurality of source programs, and the program editing means includes: A program version control device, wherein the plurality of source programs can be edited collectively.