JP3311067B2 - Program development management device - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a program development management system for managing interdependencies (repositories) between individual products when a plurality of programmers develop programs in groups.

[0002]

2. Description of the Related Art Conventionally, when a certain program is created, for example, a program for each processing portion that can be divided therein is individually created by a plurality of programmers, and finally a generation program for each individual is created. A program development environment is provided in a group unit, in which a desired program is obtained by combining.

FIG. 2 is a conceptual diagram showing a conventional program development environment. In this program development environment, for example, three programmers A to C have input / output units 11a to 11c for separately performing program development work. Input / output unit 1 for group manager M to perform program development work
1m, and a total of four people will develop programs.

The group manager M and each programmer A to C
Is for developing a program assigned to each individual via a program development processing unit 12 for performing data processing based on a preset program development tool, and is used in common with each individual's program development.
The shared files X and Y such as the ce file and the include file are created in advance by the group manager M, for example, and stored in the group management file (M) 13.

The personal files (A) 14a, (B) dedicated to each programmer are created by the individual programmers A to C so that the individual program files A to C cannot be referred to other programmers during the development. 14b,
(C) Stored in 14c. Here, each programmer A ~
C is used to read out and use the shared files X and Y stored in the group management file (M) 13 as needed and create personally generated files a to c. a is created using the shared file X, the personally created file b is created using the shared files X and Y, and the personally created file c is created using the shared file X. . The contents of the shared files X and Y may be appropriately changed and used for program development by the programmers A and B in some cases. In this case, the shared files X and Y in the group management file (M) 13
Is updated and saved to the content after the change.

[0006]

However, when the contents of the shared files X and Y are changed by a certain programmer, the contents are created using the changed shared files except for the personally generated files of the programmers. This will naturally affect other personally generated files.

That is, for example, after the programmer B creates the personally generated file b (x, Y) and the programmer C creates the personally generated file c (x), the programmer A changes the contents of the shared file X to generate the personally generated file a ( x), the personally generated files b and c would be affected, but the group manager M and each programmer A
-C have no means of knowing who is using which shared file to develop a program, and thus there is a problem that each program development work proceeds as it is.

In this case, each individual generated file a
Are performed, all of the shared files used in the combination file include the changed shared file X stored in the current group management file (M) 13.
And the shared file Y are combined, so that the personally generated files b and c created using the shared file X before the change
An error occurs in connection with the part.

SUMMARY OF THE INVENTION The present invention has been made in view of the above problems, and when a change occurs in a shared file, the program development work does not proceed as it is, and other affected files can be easily detected. It is an object of the present invention to provide a program development management device capable of performing the program development management.

[0010]

That is, a program development management apparatus according to the present invention comprises a group definition file in which information of programmers constituting a group for program development is registered, and a programmer registered in the group definition file. and each program development work with a common available shared files, and personal product files created on the basis of a program development work respectively each programmer, information for each of the respective programmer Thus created personal generated file is registered Personal file and the shared file used in the personal file
A relationship record reference relation yl is registered, when the change in the shared file has occurred, to find the relationship between records in the personal file corresponding to the programmer, which is registered in the group definition file, of the shared files And an affected file detecting means for detecting a personally generated file affected by the change.

[0011]

In other words, when a change occurs in the contents of the shared file, based on the relation record registered in each personal file corresponding to the programmer registered in the group definition file, the changed shared file is generated. Personally generated files related to the file will be detected.

[0012]

An embodiment of the present invention will be described below with reference to the drawings.

FIG. 1 is a block diagram showing the configuration of a program development management device. In this program development management device, for example, input / output units 11a to 11a through which three programmers A to C respectively perform program development work separately. 11
c and an input / output unit 11m for the group manager M to perform the program development work, and the program development is performed by a group of four people in total.

The group manager M and each of the programmers A to C
Is for developing a program assigned to each individual via a program development processing unit 21 that performs data processing based on a preset program development tool. In this case, the program development processing unit 21 In addition to development tools, a program development management tool is set.

The program development processing unit 21 includes an input / output unit 11 used by each group member M, AC.
m, 11a to 11c are connected, a group management file (M) 22 and a personal file (A) 2 dedicated to each individual.
3a to (C) 23c are connected.

The group management file 22 includes shared files X, Y, and Z such as a source file, an include file, and a load file that are commonly used in the program development by the programmers A to C.
For example, it is created and stored in advance by the group manager M. In the group management file 22, a group definition file 24 and a repository database 25 are provided.

In the group definition file 24, the names of programmers "A, A", which are permitted to use the shared files X, Y, Z stored in the group management file 22.
B, C "is registered, and based on the programmer names A to C registered in the group definition file 24, the programmers A to C can use the shared files X, Y, and Z.

That is, the program development processing unit 21 from the input / output unit corresponding to the programmer name not registered in the group definition file 24 of the group management file 22
Is prohibited in accordance with the above program development management tool.

In the repository database 25, object records 26x to 26 of the shared files X, Y and Z stored in the group management file 22 are stored.
z is registered by describing its respective attributes and file names, and relation records 27a and 27b indicating the relation between the shared files X, Y, and Z are registered by describing the related objects. When any of the contents of the shared files X, Y, and Z is changed, the related records 27a, 2a of the repository database 25 are changed according to the program development management tool.
Based on 7b, other affected shared files are detected and notified to the input / output unit 11m of the group manager M, for example.

On the other hand, the personal files (A) 23a-
(C) 23c stores personally generated files ac created by the corresponding programmers A to C, respectively.

The personal files (A) 23a-
(C) 23c includes group definition files 28a to 28c dedicated to each programmer and a repository database 29.
a to 29c are provided.

Each of the group definition files 28a to 28c dedicated to each programmer has an individual programmer A
The group manager name “M” of the group to which the group C belongs is registered.
Based on the group manager name M registered in c, the programmers A to C can access the group management file 22.

That is, the group definition file 28a
Data access processing to management files other than the group management file 22 corresponding to the group manager M registered in .about.28c is prohibited according to the program development management tool.

In the repository database 29a of the personal file 23a, the object record 30a of the personally created file a stored in the personal file 23a is registered by describing its attribute "AAA" and the file name "a". And the object record 30 of the shared file X used in the personally generated file a.
x is the attribute “source” and the file name “X”, and the substance of the file X is the personal file 23
a is registered by describing a shadow flag “*” indicating that it does not exist.

Further, in the repository database 29a of the personal file 23a, the personal generated file a is stored.
Record 31a indicating the relationship between the file and the shared file X
Are registered by describing the related objects “a · X”.

In the repository database 29b of the personal file 23b, the object record 30b of the personal file b stored in the personal file 23b is registered by describing its attribute "BBB" and the file name "b". At the same time, the object records 30x and 30y of the shared files X and Y used in the personally generated file b have the attributes “source” and “in”.
"clde", file names "X" and "Y", and a shadow flag "*" indicating that the substance of the files X and Y do not exist in the personal file 23b are registered.

Further, the repository file 29b of the personal file 23b stores the personal generated file b.
Record 31 showing the relationship between the shared files X and Y
b1, 31b2 indicate that the related objects are "b
.X "and" b.Y "are registered.

In the repository database 29c of the personal file 23c, the object record 30c of the personal file c stored in the personal file 23c is registered by describing its attribute "CCC" and file name "c". And the object record 30 of the shared file X used in the personal file c.
x is the attribute “source” and the file name “X”, and the substance of the file X is the personal file 23
c is registered by describing a shadow flag “*” indicating that it does not exist.

The repository file 29c of the personal file 23c stores the personal generated file c.
Record 31c indicating the relationship between the file and the shared file X
Are registered by describing the related objects "cX".

Here, along with each program development work by each of the programmers A to C, the shared files X,
When any of the contents of Y and Z is changed, the repository database 29a in each of the personal files 23a to 23c is used according to the program development management tool.
To 29c related records 31a, 31b1, 3
Based on 1b2 and 31c, the affected personally generated file is detected and notified to the input / output unit of the programmer that generated the file.

That is, for example, after the programmer B creates the personal file b (x, Y) and the programmer C creates the personal file c (x), the programmer A
Is changed to create the personally generated file a (x), the related records 31a, 31c of the respective repository databases 29a to 29c are changed in accordance with the process of changing and saving the shared file X in the group management file 25.
b1, 31b2, and 31c are searched, personally generated files a, b, and c related to the modified file X are detected, and the input / output unit 1 of the programmers A, B, and C that generated the files.
1a, 11b and 11c are notified that the shared file X has been changed. Next, the operation of the program development management device having the above configuration will be described.

First, the input / output unit 11m of the group manager M
Accordingly, when the group members of this program development group are defined as programmers A, B, and C, the program development management tool of the program development processing unit 21 is activated, and the group definition file 24 in the group management file 22 contains Programmer names "A, B, C" defined as group members are registered, and the individual files 23a, 23 corresponding to the programmers A, B, C are registered.
b, 23c, the group definition files 28a, 28b,
The group manager name "M" is registered in 28c.

In this way, the program definition names “A, B,
C ", and the group manager name" M "is registered in the group definition files 28a, 28b, 28c of the individual files 23a, 23b, 23c.
Data access to the group management file 22 associated with the B and C program development work is permitted.

The input / output unit 11 of the group manager M
m, the shared files X, Y, and Z are created in accordance with the program development tool of the program development processing unit 21. The shared files X, Y, and Z are stored in the group management file 22 and the object records 26x , 26y, 26z are sequentially registered in the repository database 25. Here, the shared files X, Y,
Objects related to each other between Z are related records 2
7a and 27b are registered.

On the other hand, the programmer A uses the shared file X to generate a personally generated file a (X), and the programmer B uses the shared files X and Y to generate a personally generated file b (x, y). When the personal generated files c (x) are individually created by using the shared file X by C, the personal generated file a (X) becomes the personal file 23a, and the personal generated file b (x, y) becomes The personal file 23b and the personal file c (x) are stored in the personal file 23c.

Then, in the repository database 29a of the personal file 23a, the personal generated file a (x)
Are stored in the repository database 29b of the personal file 23b, and the object records 30b, 30x, 30y corresponding to the personally generated file b (x, y) are stored in the repository database 29c of the personal file 23c. Is the object record 3 corresponding to the personally generated file c (x)
0c and 30x are registered.

In this case, each of the individual generated files a (x)
, B (x, y), c (x), each object record 30x,
A shadow flag “*” is added to each of 30y, indicating that there is no entity of the corresponding personal file 23a, 23b, 23c.

Here, the individual generated files a, b,
The objects of the shared files X and Y related to c are stored as related records 31a, 31b1, 31b2 and 31c, respectively.
29b and 29c are registered. As described above, when the personally generated files a, b, and c are created and stored using the shared files X and Y, for example, the content of the shared file X is changed and stored in the group management file 22. ,
According to the program development management tool in the program development processing unit 21, first, the relation record 27 in the repository database 25 of the group management file 22.
a and 27b are searched, and it is detected that the change of the shared file X affects the shared file Y. Then, the group manager M is notified through the input / output unit 11m that the change of the shared file X affects the shared file Y.

Further, according to the program development management tool in the program development processing section 21, the programmer names "A, B,
"C" is retrieved from the group definition file 24 of the group management file 22, and the individual files 23a, 23 corresponding to the retrieved programmer names "A, B, C".
b, 23c repository databases 29a, 29b,
Relationship records 31a, 31b1, 31b in 29c
2 and 31c are searched, and it is detected that the change of the shared file X affects any of the personally generated files a, b, and c. Then, the change of the shared file X affects all of the personally generated files a, b, and c.
To each of the programmers A, B, and C through

On the other hand, for example, when the contents of the shared file Y are changed and stored in the group management file 22, first, according to the program development management tool in the program development processing unit 21, the relation of the group management file 22 in the repository database 25 is first determined. Record 27a,
27b is searched, and it is detected that the change of the shared file Y affects the shared files X and Z. Then, the shared file X is changed by changing the shared file Y.
And Z are notified to the group manager M via the input / output unit 11m.

Further, according to the program development management tool in the program development processing section 21, the names of the programmers "A, B,
"C" is retrieved from the group definition file 24 of the group management file 22, and the individual files 23a, 23 corresponding to the retrieved programmer names "A, B, C".
b, 23c repository databases 29a, 29b,
Relationship records 31a, 31b1, 31b in 29c
2 and 31c are searched, and it is detected that the change of the shared file Y affects only the personally generated file b. Then, the fact that the change of the shared file Y affects the personally generated file b is determined by the corresponding input / output unit 1.
1b is notified to programmer B.

Therefore, according to the program development management apparatus having the above configuration, the group definition file 24 of the group management file 22 in which the shared files X, Y, and Z are stored.
, The programmer names "A, B, C" constituting the group are registered, and the personal files 23a, 23b, 23c corresponding to the programmers A, B, C are stored in the respective personally generated files a, b. , C, and the relationship records 31a, 31 indicating the relationship with the shared files X, Y used in creating the personally generated files a, b, c.
b1, 31b2, and 31c are stored in the individual files 23a and 2
Repository database 29 for each of 3b and 23c
a, 29b, and 29c, and when any of the contents of the shared files X, Y, and Z stored in the group management file 22 is changed, the programmer name "registered in the group definition file 24" Based on the related records 31a, 31b1, 31b2, 31c registered in the repository databases 29a, 29b, 29c in the individual files 23a, 23b, 23c corresponding to "A, B, C", Since the related personally generated file is detected and notified to the programmer who generated it, for example, after the programmer B creates the personally generated file b (x, Y) and the programmer C creates the personally generated file c (x), If A changes the contents of shared file X to create a personally generated file a (x), And c are notified to the corresponding programmers B and C, and the programmers B and C modify the corresponding personal generated files b and c according to the changed shared file X. become able to.

Therefore, finally, each personally generated file a,
When performing the combination of b and c, the personally generated files a and
Even if all of the shared files used in b and c are combined with the changed shared file X and shared file Y stored in the current group management file 22, no error occurs.

If the registration of the programmer name registered in the group definition file 24 is canceled, the programmer is prohibited from accessing the group management file 22, so that the group members can be easily changed. be able to.

Further, the individual personal files 23a,
Repository database 29a, 2 for each 23b, 23c
Since the 9b and 29c are provided, data processing does not concentrate on the group management file 22, and high-speed database registration and search processing can be performed.

[0046]

As described above, according to the present invention, a group definition file in which information of programmers constituting a group for program development is registered, and each program development work by the programmers registered in the group definition file are performed. individuals common available shared files, and personal product files created on the basis of a program development work respectively each programmer, information for each of the respective programmer Therefore <br/> created individuals generated files is registered with File and a personally generated file for this personal file.
A relationship record in which a reference relationship of a shared file to be used is registered and a relationship record in the personal file corresponding to a programmer registered in the group definition file when a change occurs in the shared file are searched. The system is provided with an influence file detecting means for detecting a personally generated file affected by the change of the shared file, so that when the shared file is changed, the program development work does not proceed as it is, Other affected files can be easily detected.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a program development management device according to an embodiment of the present invention.

FIG. 2 is a conceptual diagram showing a conventional program development environment.

[Explanation of symbols]

11a, 11b, 11c, 11m: input / output unit, 21: program development processing unit, 22: group management file, 2
3a, 23b, 23c ... personal files, 24, 28a,
28b, 28c: Group definition file, 25, 29
a, 29b, 29c ... repository database, 26
x, 26y, 26z... object records of shared files, 27a, 27b.
30a, 30b, 30c, 30x, 30y... Object records of personally generated files, 31a, 31b1, 3
1b2, 31c... Relationship records between personally created files and shared files.

Continuation of the front page (56) References Iwamoto et al., 2 repository systems for software distributed development, Information Processing Society of Japan 44th (Early 1992) National Convention Lecture Papers (5), pp. 146-64. 175-176 Kazuyasu Tsukijo and 2 others, CSS Integrated Development Environment, IPSJ 44th (Late 1992) National Conference Proceedings (5), pp. 339-354 Toru Matsuotani, Special Issue Software Management Ment software configuration management and maintenance, information processing, (1992), Vol. 33, No. 8, pp. 945-953 Hiroaki Abe et al., Approach to CASE Tool Integration, Proc. 311-314 Iwamoto et al., Deliverables Management of System Design Support Tool MYCASE, Information Processing Society of Japan 44th (Late 1992) National Conference Lecture Papers (5), pp. 223-314. 305-306 (58) Field surveyed (Int.Cl. ⁷ , DB name) G06F 9/06-9/45

Claims (1)

(57) [Claims] 1. A group definition file in which information of programmers constituting a group for program development is registered, a shared file commonly available for each program development work performed by programmers registered in the group definition file, and personal product files created on the basis of a program development work each programmer, thus creating individuals generated file to each programmer
A personal file in which information is registered for each personal file, and a shared file
A relationship record reference relation Airu is registered, when the change in the shared file has occurred, to find the relationship between records in the personal file corresponding to the programmer, which is registered in the group definition file, of the shared files A program development management device, comprising: an affected file detecting means for detecting a personally generated file affected by the change.