JP2002182916A - Program alteration and management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To detect the confirmation range of SM correction contents without omission in SM registration or before registration, to shorten detecting time and time from detection of the corrected contents to a related developer and to relieve burden of the developer to confirm the related correction contents. SOLUTION: The SM and the developer in relation to correction are rapidly extracted by executing a source analyzing part, for example, investigation of calling relation, investigation of the developer, etc., of the entire program or the corrected SM in the case of the SM registration or before the registration by the developer. In addition, share of information that a confirmation state of correction information is promptly learned even in an area distributed from a connection confirming part to the developer, confirmation receiving part is performed from the extracted contents.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a program management system for product development, and more particularly, to a program management system for extracting the effects of a product development worker when changing an SM and transmitting information to a related development worker. Program change management method.

[0002]

2. Description of the Related Art In a conventional program management system, as shown in a program management method based on a program change notification described in JP-A-11-16099, an input of SM correction information from a developer is accepted. The contents were saved as data, and when necessary, they had to guess and refer to the necessary parts independently.

[0003] In addition, a developer who needs to grasp the status of confirmation of the effect of the SM modification must directly call a solution worker who is thought to be related to the modification based on the content of the modification in order to know the solution status of the modification information. Confirmation was performed using such methods.

[0004]

As described above, in the conventional program management system, the contents of the correction of the input SM are stored, but the SM and the development staff who are presumed to be affected by the correction of the SM are saved. There was no way to know. Also, there was no way to register the SM modifications to the relevant developers, or to promptly notify them prior to registration. Also, SM
The developer who checks the contents of the modification was guessed from the contents of the SM himself and contacted the development worker related to the modification of the SM.

SUMMARY OF THE INVENTION It is an object of the present invention to reduce the time required for SM registration or for confirming the modification range before registration, and to reduce the detection time, and the time from the detection to the confirmation of the modification contents to the relevant developers. Another object of the present invention is to reduce the burden on a developer to check the contents of a related modification.

[0006]

SUMMARY OF THE INVENTION In order to achieve the above object, a program change management system in a program change management method according to the present invention requires a developer to register or register a program before SM registration or registration.
By performing source analysis on the SM, for example, examining the calling relationship and investigating the developers, it is possible to quickly extract the SM and the developers involved in the modification.

[0007] Further, it is possible to share information such that the confirmation status of the correction information can be quickly known even in a distributed area by means of contact confirmation to the corresponding developer and confirmation reception means from the extracted contents.

[0008]

Next, embodiments of the present invention will be described with reference to the drawings.

In FIG. 1, one embodiment of the present invention is to automatically extract functions in SM that are affected by a change in a program, and to share the confirmation status in a development environment in a distributed area, FIG. 2 is a block diagram showing a configuration of a program change management method that enables real-time information to be grasped.

In FIG. 1, a program change management system according to an embodiment of the present invention includes an input unit 4, an output unit 5, a reception unit 6, a transmission unit 7, a storage unit 8, an analysis table analysis unit 9, It comprises a confirmation table analysis unit 10 and its peripheral devices.

The input device 2, the output device 3,
There are SM11, analysis table 12, and confirmation table 13,
The transmitting unit 7, the receiving unit 6, and the terminal 1 via the network 17
6 is connected, and the developer 14 has an ID such as a developer ID 15 at each terminal.

In the input section 4, a developer inputs a change of SM.

The output unit 5 outputs to the output device an ID of a development worker (hereinafter referred to as a related development worker) having an influence on the change of the SM. Further, the confirmation status of the related developer is output to the output device.

The receiving unit 6 receives confirmation completion notification data as shown in FIG. 10 from the confirmation table analysis unit, and outputs this data to the confirmation table analysis unit.

The transmitting unit 7 receives the list of IDs of the related developers from the confirmation table analyzer and sends a mail to the IDs of all the related developers.

In the storage unit 8, the input unit 4 inputs the
The SM change data is stored in the SM 11 on the magnetic disk.

The analysis table analysis unit 9 analyzes the function call relation of the SM, and outputs the relation between the function call source and the call destination to the analysis table in FIG. 6 to clarify the influence range related to the function call.

The confirmation table analysis unit 10 stores the ID list of the related developers in the confirmation table 13 and updates the data of the confirmation status of the related developers.

Next, the operation of the program change management system of this embodiment will be described with reference to the drawings.

FIG. 2 is a diagram showing a processing flow in a case where the program change management method of this embodiment is applied to SM change in actual program management.

Referring to the figure, in step 201, an SM change procedure is started. Next, in step 202, the developer changes the SM using the input device 2. Then, in step 203, the input unit 4 outputs the data received from the input device 2 to the storage unit 8 and the table analysis unit 9. In step 204, an analysis table is created based on the data changed by the confirmation table analysis unit 10. In step 205, the storage unit 8 outputs the data input from the input unit to the SM 11. In step 206, the SM change procedure ends.

FIG. 3 shows a processing flow in the case where the program change management method of the present embodiment is applied to a message transmission for confirming whether or not there is an effect on the function in charge for a relevant developer in the actual program management. FIG.

Referring to FIG. 3, in step 301, a procedure for transmitting to a related developer is started. Next, in step 302, S
M For development workers who may be affected by the
The development worker sends the change confirmation request data from the input device 2. Then, in step 303, when the input unit 4 receives the data, the input unit 4 issues an SM change confirmation request to the confirmation table analysis unit 9. In step 304, when the confirmation table analysis unit 10 receives the data, it outputs the related development worker list to the transmission unit 7 based on the related development worker list based on the analysis table. In step 305, the transmitting unit 7 transmits an SM change confirmation request to the corresponding ID by e-mail based on the received list of related developers. In step 306, the procedure for sending to the related developers is ended.

FIG. 4 is a diagram showing a processing flow when the program change management method of this embodiment is applied to reception of confirmation completion notification data from a related developer in actual program management.

In FIG. 4, a procedure for receiving an SM change confirmation status from a developer who has received the SM change confirmation notification in step 401 is started. Then, in step 402, the confirmation completion data transmitted by the relevant developer is transmitted. In step 403, the received data is output to a check table check procedure. In step 404, the confirmation table analysis unit 10 receives confirmation completion data from the reception unit 6, and reflects the confirmation status of the corresponding user ID in the confirmation table. In step 405, the procedure for receiving the SM change confirmation status from the developer receiving the SM confirmation notification ends.

FIG. 5 is a diagram showing a flow of processing for confirming the function confirmation status of the relevant developer in the actual program management using the program change management method of this embodiment.

In FIG. 5, the procedure for confirming the SM change confirmation status from the developer receiving the SM change confirmation notice in step 501 is started. Then, in step 502, a request is made to confirm the confirmation status of the relevant developer. Step 503
When the input unit 4 receives the confirmation status confirmation request from the input device 2, the input unit 4 reads the confirmation status from the confirmation table and outputs it to the output unit 5. In step 505, the output unit 5 outputs the confirmation status of the relevant developer from the confirmation table analysis unit 10 to the output device 3. In step 506, the SM change confirmation status confirmation from the developer receiving the SM change confirmation notification ends.

FIG. 6 is a diagram showing an example of an analysis table in the program change management system of the present embodiment. The meanings of “ROOT” and “END” in the analysis table of FIG. 6 are described below. A case where a function that calls a certain function corresponds to a function that does not exist is indicated by “ROOT”. The case where a function to be called from a certain function corresponds to a function that does not exist is referred to as “EN”.
D ".

FIG. 7 is a diagram showing an example of the confirmation table in the program change management system of the present embodiment. The confirmation table has information fields of a function name, a function worker ID, and a confirmation state.

FIG. 8 is a diagram showing an example of source change confirmation request data in the program change management system of the present embodiment. The data includes a source change confirmation request identifier, a function name, a developer ID, and the like.

FIG. 9 is a diagram showing an example of the confirmation status confirmation request data in the program change management system of this embodiment. The data includes a confirmation status confirmation request identifier and confirmation table position information.

FIG. 10 is a diagram showing confirmation completion notification data of the program change management system of this embodiment. The data includes a confirmation completion notification identifier, a function name, and a developer ID.

Here, as an actual program change management, the developer inputs the changed SM to the storage unit 8 and the analysis table analysis unit 9 through the input unit 4. The analysis table analysis unit receives the changed SM input from the input unit 4. The analysis table analysis unit 9 selects a source program before the change corresponding to the changed SM from the SMs 11 and outputs the selected source program from the SM 11 to a pre-change function call related table in the analysis table as shown in FIG. Thereafter, the storage unit 8 inputs the changed program input from the input unit 4. The changed program is registered in SM11.

Next, the development worker makes a source change confirmation request from the input device 2 to the development worker who may be affected by the change of the SM. When the input unit 4 receives the source change confirmation request, it issues a source change confirmation request to the analysis table analysis unit 9. The analysis table analysis unit is shown in FIG.
When the source change confirmation request data as shown in FIG. 6 is received, a function related to the changed function is searched from the analysis table as shown in FIG. A search for a related function at this time will be described. First, the confirmation table analyzer 10 reads the changed function name from the source change confirmation request data as shown in FIG. Then, a function name that matches this function name is searched from the change time call-related table of the analysis table shown in FIG. As shown in FIG. 8, the related function name is output to the responsible developer.

Next, the confirmation table analysis unit 10 outputs the related function group that has received the data as shown in FIG. 8 to the confirmation table. At this time, all the data in the confirmation state are initialized and set to an “unused” state.

Further, the check table check unit 10 notifies the developer ID corresponding to the function of the check table of the name of the function to be changed and the names of the functions that have an effect on the change by mail.

After sending the e-mail to the ID of the related development worker, the related development worker who received the mail confirms whether or not the function assigned to each development worker is affected by the change of the SM, and then uses the receiving unit 6 by mail. Then, transmission of confirmation completion notification data as shown in FIG. 10 is performed. Upon receiving the confirmation completion notification data, the receiving unit 6 compares the function in the confirmation table shown in FIG. 7 and the confirmed developer ID with respect to each of the function and the developer ID in FIG. Are compared, and only when both the function and the developer ID match, the corresponding confirmation state is changed from “not yet” to “completed”.

Finally, the developer who has changed the SM inputs a confirmation status confirmation request as shown in FIG.
When the input unit 4 receives the confirmation status confirmation request from the input device 2, it outputs a confirmation status confirmation request to the confirmation table analysis unit 10. Upon receipt of the confirmation status confirmation request, the confirmation table analysis unit 10 reads the position information of the most thousands of data stored in the confirmation table and stores it in the position information of FIG. Then, the confirmation status confirmation request data is output to the output means. Upon receiving this, the output unit 5 outputs the contents of the confirmation table data from the position information of the confirmation status confirmation request data.

[0039]

As described above, the program change management method based on the program change notification of the present invention allows the development workers related to the change to be contacted without omission, and eliminates the communication errors and the like caused by the program change, thereby correctly changing the program. There is an advantage that can be.

Further, in a development environment in a distributed area, there is an advantage that the SM confirmation status of each development worker is shared, and a large number of steps are not required to confirm the SM confirmation status in the distributed development environment.

Further, since the SM confirmation status of the developer can be grasped in real time, there is an advantage that the SM confirmation status can be obtained quickly.

[Brief description of the drawings]

FIG. 1 is a block diagram of a program change management method according to an embodiment of the present invention.

FIG. 2 is an SM change procedure of a program change management method according to an embodiment of the present invention;

FIG. 3 shows a procedure for transmitting a program change management method to related developers according to an embodiment of the present invention.

FIG. 4 is a procedure for receiving SM change confirmation completion notification data from a developer involved in a program change management system according to an embodiment of the present invention;

FIG. 5 is a procedure for confirming the confirmation status of a developer involved in the program change management method according to an embodiment of the present invention

FIG. 6 is an analysis table of a program change management system according to an embodiment of the present invention;

FIG. 7 is a program change management method confirmation table according to an embodiment of the present invention.

FIG. 8 shows an SM change confirmation request data of a program change management method according to an embodiment of the present invention.

FIG. 9 shows a confirmation status confirmation request data of a program change management method according to an embodiment of the present invention.

FIG. 10 shows confirmation completion notification data of a program change management method according to an embodiment of the present invention.

[Explanation of symbols]

 1. Central processing unit 2. Input device 3. Output device 4. Input unit 5. Output unit 6. Receiver section 7. Transmission section 8. Storage unit 9. Analysis table analysis unit 10. Confirmation table analyzer 11. SM12. Analysis table 13. Confirmation table Development staff 15. Development worker ID 16. Terminal 17. network

 ──────────────────────────────────────────────────続 き Continued on the front page (72) Inventor Daiki Nozue 216 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture Inside the Hitachi, Ltd.Communications Division (72) Inventor Yoshimi Saito 216 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture Hitachi, Ltd. Communications Division (72) Inventor Tatsumi Shiraishi 216 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture F-term in Hitachi Ltd. Communications Division 5B042 HH01 5B076 DA00 EC01

Claims (3)

[Claims] When a problem such as a bug in software development that occurs during the development of a product occurs, a source module (hereinafter referred to as SM) for solving the problem is modified. A program change management system, characterized in that a means for extracting an SM that is considered to be affected by the modification is provided in a program management system to be used. 2. The time required for transmitting information for confirming the effect of an SM change is reduced by notifying the status of the SM development staff extracted by the program change management method according to claim 1 in real time. A program change management system with information transmission means that enables sharing of confirmation status in development in distributed areas. 3. The program management system itself receives and holds the confirmation result of the SM development worker notified by the information transmission means according to claim 2, and transmits the unconfirmed development worker. A program management system that enables real-time understanding and reduces the burden on SM modifiers.