JPH0683606A - Control system for registration of source program - Google Patents

Abstract

PURPOSE:To prevent the production of an incomplete execution module in a function extension state. CONSTITUTION:The source program designated by an input means 9 is transferred from a development environment 16 to a registration environment 17 through a release source registering part 10. A release source control part adds a version number to the source file name of the source program sent to the environment 17. Then the source program is sent from the environment 17 to a release environment in the source file name having its version number.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a source program registration management system for registering and managing a source program necessary for releasing a software system developed by a plurality of programmers to an end user.

[0002]

2. Description of the Related Art The development of a huge software system is often a joint development in which a plurality of programmers create programs for each functional unit. In this joint development, the functions of the system are divided into functional units, and the source programs in the divided functional units are created by individual programmers. Then, by integrating the source programs of the functional units, an execution module as a software system is created.

Software that goes through such a development process
In the case of creating a version-upgraded software system with expanded functions in the system, extract the source program that has been modified under the function expansion and is stored under the control of each programmer. The method of creating the execution module of the upgraded software system by integrating the extracted source programs has been used.

[0004]

However, in the above method, when an upgraded execution module is created, a source program to which an extended function is added is extracted from a plurality of source programs under the control of individual programmers. At this time, because the extraction method was done manually, the situation where a source program under development or a source program to which a function required for version upgrade is not added is extracted, or a source program which is needed is extracted. Problems such as forgetting occurred and incomplete execution modules were released.

The present invention was devised to solve the above problems, and an object thereof is to provide a source program registration management system capable of preventing the creation of an incomplete execution module.

[0006]

In order to solve the above-mentioned problems, the source program registration management system of the present invention is designated by the input means when the environment in which the source program developed by the programmer is stored is the development environment. The release source registration part that transfers the source program from the development environment to the registration environment, and the version number is added to the source file name of the source program transferred to the registration environment. And a release source management unit that transfers the file from the registration environment to the release environment. Also, when the release standard is the standard required for the source program when creating the execution module, the release source registration unit checks whether the source program specified by the input means conforms to the release standard, and then releases this release standard. A source program that conforms to is transferred from the development environment to the registration environment. Further, the release source registration unit is configured to store data indicating transfer of the source file as a release history in the release history file when the source program is transferred from the development environment to the registration environment.

[0007]

The release source registration unit transfers only the designated source program among the plurality of source programs stored in the development environment to the registration environment. Then, the source program transferred to the registration environment is given a version number indicating the version to the source file name by the release source management unit, and is transferred to the release environment with the source file name given the version number. In other words, even if a source program has the same source file name at the time of development, it will be a source program that can be distinguished for each version in the release environment.

[0008]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing an electrical configuration of an embodiment of a release source registration unit of a source program registration management system of the present invention.

In the figure, the release source registration unit 10 is
The registration control unit 11, the inspection unit 12, the transfer unit 13, and the deletion unit 14 are composed of four blocks, and all the blocks 11 to 14 are composed of software executed by the computer 8.

Input means 9 composed of a keyboard of the computer 8 and its control software
The registration control unit 11 to which the output of is given is a block that controls each block of the inspection unit 12, the transfer unit 13, and the deletion unit 14 to which the output is sent, and is activated by the creator of the program. It is a block that will be played.

The inspection unit 12 also inspects whether or not the source program to be released conforms to the release standard (for example, inspects whether the source file name is composed of characters within the allowable number of characters). The inspection file 15 to which the output of the inspection unit 12 is guided is a file for storing the inspection result of the inspection unit 12. The output of the inspection file 15 is led to the registration control unit 11.

The development environment 16 is a block composed of files or the like in which a plurality of source programs developed by a plurality of programmers are stored in advance, and the registration environment 17 is a block composed of a file or the like in which a plurality of source programs are stored. Has become. Then, the transfer unit 13 includes the registration control unit 11
Is a block that transfers the source program from the development environment 16 to the registration environment 17 according to the instructions from.

The release history file 18 to which the output of the transfer unit 13 and the output of the deletion unit 14 are guided stores data indicating the history at the time of creation and the history after creation for each of the created source programs. The deletion file 19 to which the output of the deletion unit 14 is given is a file indicating a series of source programs to be deleted.

FIG. 2 is a block diagram showing the electrical construction of an embodiment of the release source management section according to the present invention.

The release source management unit 21 includes a management control unit 2
3, inspection unit 24, transfer unit 25, and execution module generation unit 2
It is composed of four blocks of 6, and all the blocks 23 to 26 are composed of software executed by the computer 8.

The management control unit 23 is a block that controls each block of the inspection unit 24, the transfer unit 25, and the execution module generation unit 26, which are the destinations of the output, and is a block activated by the creator of the execution module. Has become. The inspection unit 24 is a block that compares the source program to be released with the source program in the development environment 16 and that in the registered environment 17, and sends the comparison result to the inspection file 22. The output of the inspection file 22 is sent to the management control unit 23.

In accordance with an instruction from the management control unit 23, the transfer unit 25 loads the source program stored in the registration environment 17 into
The release environment 27 is a block that is transferred to the release environment 27 with a source file name according to a naming rule which will be described later in detail. The release environment 27 is a block including files and the like in which the source program is stored.

The execution module generation unit 26 creates an execution module by integrating (compiling and linking) the source programs stored in the release environment 27, and stores the created execution module in the execution module environment 28. It is a block to do. The execution module environment 28 is composed of files in which execution modules are stored.

The operation of one embodiment of the present invention having the above configuration will be described below with reference to the flow charts shown in FIGS. 3 and 4.

The registration control unit 11 started by each creator of the source program includes a step S10 for selecting one of two operations, registration or deletion, and when the creator selects the registration, the step S10 is executed. In the operation of S11, the registration information such as the target source file name is input from the input means 9. Then, the inspection unit 12 is activated at step S12.

The inspection unit 12 inspects the target source program in accordance with a preset release standard, and inspects whether the source program conforms to the release standard (source file of the source program. Check whether the first name has 10 characters or less). Then, the inspection result is sent to and stored in the inspection file 15.

Then, the operation is returned to the registration control unit 11, and the registration control unit 11 reads the inspection file 15 to check whether or not the target source program conforms to the release standard. If it does not match, the operation is terminated (step S13), and if it matches, the operation of the transfer unit 13 is started (step S1).
Four).

The activated transfer unit 13 is a source program stored in the development environment 16 (a program having the source file name input by the registration control unit 11 and determined by the inspection unit 12 to be suitable). Read out source program) and store the read source program in the registration environment 17. Also, as information indicating the history of the source program, the time when this source program was transferred from the development environment 16 to the registration environment 17, the name of the person who transferred the source program, and comments are stored in the release history file 18 as release history. To be done.

On the other hand, when the deletion is selected in the operation of the registration control unit 11, the deletion information such as the source file name to be deleted is input from the input means 9 in step S15, and then the operation of the deletion unit 14 is activated. (Step S16). At this time, the deletion information entered in step S15 (name of the source file targeted for deletion, etc.)
Is stored in the deletion file 19.

By repeating the above operation as necessary, the registration environment 17 stores the source program required for the release, and the release history file 18 stores the history of the release for each source program. Information to be stored is stored, and the source file name or the like to be deleted is stored in the deletion file 19.

Next, the operation of the release source management unit 21 will be described.

When the creator of the execution module activates the management control unit 23, the version number of the execution module to be released is input to the management control unit 23 from the input means 9 (step S17). Next, it is checked whether or not the source program corresponding to the release target exists in the registration environment 17 (step S18), and if there is the corresponding source program, the inspection unit 24 is activated (step S1).
9).

The activated inspection unit 24 compares the source program in the registered environment 17 with the source program in the development environment 16 and stores the comparison result in the inspection file 22. Then, since the operation is returned to the management control unit 23, the management control unit 23 reads the inspection file 22, and when the comparison contents show a match, the source program stored in the registration environment 17 is the corresponding source program. Assuming that there is, the transfer unit 25 is activated (steps S20 and S21). (However, at this time, by referring to the deletion file 19, it is confirmed that the corresponding source program is not the deletion target).

However, when the comparison result in step S20 shows a mismatch, the time when the source program is registered in the registration environment 17 and the creator of the execution module are set by the management control unit.
The development environment 16
Since the source program stored in the registration environment 17 cannot be used to indicate that the source program stored in (1) has been changed, the subsequent operation is stopped immediately because of an error.

The transfer unit 25, which is activated because the comparison contents match, transfers the source program stored in the registration environment 17 to the release environment 27. In this transfer, the source file name of the source program is transferred. Changes are given to.

In this modification, the source file name of the source program stored in the registration environment 17 is, for example, "B.
"FOR" (indicated by 55 in FIG. 5), the changed source file name is "B. FO
The source file name has an underline symbol and "001" added to "R", and the version number is indicated by a three-digit numerical value such as "001".

Regarding this version number, since the source program having the same source file name when the version number is excluded is already stored in the release environment 27, the source program of the newly transferred source program is transferred. Whereas the file name has already been stored, when the version number is included, the value is set so that the source file names are different from each other (the value is incremented by 001 in each transfer).

That is, in the transfer at this time, a version number which is incremented by a value from the version number added to the source program already transferred to the release environment 27 is added.

The changes in the source file name due to the transfer of the source program are shown below (note that in the release environment 27,
The source program group that was used when the first version of the execution module was created is adopted as the original source without any change in the source file name.

It is assumed that a source program group indicated by 51 in FIG. 5 is stored in the development environment 16 and that a source program group indicated by 52 is transferred to the registration environment 17 from these source programs (source file name). Is the same as when stored in development environment 16). Release environment
If the source program group indicated by 53 is already stored in 27, and the value of the version number input in step S17 is M (M> 7), the registration environment
When the 17 source program groups are transferred to the release environment 27, the release environment 27 stores the source program group indicated by 53.

As described above, when the operation of the transfer section 25 started in step S21 ends and the source program required for the release environment 27 is transferred, the operation of the execution module generation section 26 is started (step S22).

Therefore, the execution module generation unit activated
In 26, when the version number is not input, it is assumed to be the original, and only the source program to which the version number is not added is selected to create the execution module.

When a version number is input, if a plurality of source programs having version numbers equal to or less than the input version number are stored in the release environment 27, the same source program (source file name excluding version number Are the same source program)
, The value is less than or equal to the entered version number,
The source program to which the maximum version number is added within the range is selected as the target source program. Then, an execution module is created from the selected source program.

This means that, for example, if the value M is input as the version number and the source program group stored in the release environment 27 is the source program group indicated by 53, the selected source program group is 58.
The source program group shown by.

The execution module created from the source program selected by the above method is then transferred to and stored in the execution module environment 28. That is, the target execution module is stored in the execution module environment 28 (when the value M is input as the version number to the execution module group 54 and the created execution module is stored in the execution module environment 28). The execution modules in the execution module environment 28 are shown (including the execution modules created before that).

In the operation of step S18, if there is no corresponding source program, it is assumed that the required source program is already stored in the release environment 27, and the operation shifts from step S18 to step S22 and is immediately executed. Module creation starts. Then, the created execution module is stored in the execution module environment 28.

As described above, in the present embodiment, by providing the inspection unit 12, it is inspected whether the source program conforms to the release standard, and the source program conforming to the release standard is registered in the registration environment. Since it is configured to be registered, it is possible to prevent the creation of an execution module from an erroneous source program.

Further, since the release history file 18 is provided, the changes in the handling of each source program are recorded, and it is easy to refer to the changes during the maintenance of the software system. It is possible to improve efficiency.

The present invention is not limited to the above embodiment,
Any part can be changed within the range of not changing the gist of the invention.

[0045]

The source program registration management system according to the present invention transfers the source program designated by the input means from the development environment to the registration environment by using the release source registration unit, and the release source management unit A version number is added to the source file name of the source program transferred to the registration environment, and the source program is configured to transfer from the registration environment to the release environment with the source file name with the version number added. The user and the creator of the execution module are bridged by the registration environment, and the management is performed by the version number method, so that it is possible to prevent the creation of an incomplete execution module when the function is expanded.

[Brief description of drawings]

FIG. 1 is a block diagram showing an electrical configuration of an embodiment of a release source registration unit of a source program registration management system of the present invention.

FIG. 2 is a block diagram showing an electrical configuration of an embodiment of a release source management section of the source program registration management system of the present invention.

FIG. 3 is a flowchart showing the operation of an embodiment of the release source registration unit shown in FIG.

4 is a flowchart showing an operation of an embodiment of a release source management unit shown in FIG.

FIG. 5 is an explanatory diagram showing source file names of a source program group.

[Explanation of symbols]

 9 Input method 10 Release source registration section 16 Development environment 17 Registration environment 21 Release source management section 27 Release environment

Claims (3)

[Claims] 1. A release source registration unit for transferring a source program specified by an input means from a development environment to a registration environment when the environment in which a source program developed by a programmer is stored is used as the development environment, and the registration environment. A release source management unit that adds a version number to the source file name of the transferred source program and transfers the source program from the registered environment to the release environment with the source file name added with the version number. A source program registration management system characterized by: 2. The release source registration unit determines whether the source program specified by the input means conforms to the release standard when the standard required for the source program when creating the execution module is the release standard. The source program registration management system according to claim 1, wherein the source program registration management system inspects and transfers a source program conforming to the release standard from a development environment to the registration environment. 3. The release source registration unit, when a source program is transferred from a development environment to the registration environment, stores data indicating transfer of the source file in a release history file as a release history. The source program registration management system according to claim 1 or claim 2.