JP2009223822A - Source code update notifying device and source code update notifying method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prevent a plurality of developers from simultaneously updating a plurality of source codes having dependency. <P>SOLUTION: A request registering means 23 receives request information including a source code from a client device. A dependency accessing means 16 retrieves a relevant source code corresponding to the source code among the plurality of dependency source codes with reference to a dependency graph 32 for associating the plurality of source codes with a plurality of dependency source codes. A developer map accessing means 28 retrieves relevant developer identification information corresponding to a source code file including the relevant source code from a developer identification information aggregate with reference to a developer map 34 for associating a plurality of file names with the developer identification information aggregate. A notifying means 24 notifies a developer indicated by the relevant developer identification information of the request information. In such a case, the developer can confirm whether a source code which the developer attempts to update conflicts with update by other developers. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a source code update notification device and a source code update notification method, and more particularly to a source code update notification device and a source code update notification method that support parallel development of a plurality of people in software development.

  In software development, version management software that supports parallel development of multiple people is known. Examples of such software include open source “CVS” and “Subversion”, Microsoft “Visual SourceSafe”, and the like. Also, open source “Trac” is known as software for managing source code change requests, and the relationship between multiple change requests and multiple source codes is linked with the version management software “Subversion”. Can be managed.

  In the case of parallel development by multiple people, especially in the case of large-scale development, the source code is often checked in by multiple developers at the same time, and different developers update the source code that affects each other. Such a situation is also assumed. At this time, in order to understand the influence of other source code on the change request to a certain source code, check the source code that is the target of the change request, and the dependency between functions, classes, and methods. There is a problem that enormous man-hours are required.

  Japanese Patent Laying-Open No. 2005-266976 discloses a program storage device that can grasp the confirmation status of a program that may be affected by correction. The program storage device stores a program in association with information specifying a storage person who stores the program, and can store another program as a modified version of the stored program. Extracting means for extracting a part of a program that may be affected by another program when the other program is stored as a modified version program from the stored program before modification And display means for performing a display for notifying a saver who has saved the program part that the part of the program extracted by the extraction means may be affected. Check the effect of the other program when displaying the notification to the saved user. Effect that demanded, and / or is characterized by displaying the requesting notification of the confirmation result of the impact.

  In such a method, if other developers have updated the affected source code in parallel, it will be notified that the affected source code is affected only when the affected source code is registered in the repository. There is a problem that the source code update work performed before the notification may become invalid.

  Japanese Patent Application Laid-Open No. 2000-20298 discloses a software development support apparatus that supports a package configuration change operation that occurs during development and can perform design using an appropriate package. The software development support device is a software development support device that supports software development that incorporates the concept of modularization in the form of a package. The software development support device analyzes a source file and registers information about classes and members that constitute each package. Source analysis unit that creates a repository database and a parsing information database in which parsing information obtained as a result of analysis is registered, and information in the repository database is visualized, and symbols of classes and members, and references of classes and members A repository visualization unit that creates graphic data indicating the relationship, a display control unit that displays the generated graphic data on a graphic terminal and receives an instruction to change the package configuration of the source file, and a display control unit that receives the graphic data. Follow the instructions Database, and updates the contents of the parsed information database and the source file is characterized by comprising a program modifying unit to modify the package configuration of the source file.

  Japanese Unexamined Patent Application Publication No. 2002-41488 discloses a system for managing clusters in a computing environment. The system is a registry component for the system to provide global data storage for data of a cluster of the computing environment, the cluster comprising one or more nodes of the computing environment. A registry component comprising: a configuration component for maintaining data locally on at least one of the one or more nodes and storing global data in the registry component; and one of the clusters An active component for providing the status of one or more communication paths, one active component depending on the registry component and the configuration component, and one on one or more other components of the cluster A group service component for providing a plurality of services, the group service component depending on the registry component, the configuration component, and the active component; and one or more resource resources of the cluster A resource management component for enabling communication to a controller, the resource component depending on the registry component, the configuration component, and the group service component.

  Japanese Patent Application Laid-Open No. 2006-277435 ensures consistency of source files while allowing multiple developers to edit the same source file at the same time, and allows the developer to easily grasp the changed part of the source file A version control system is disclosed. The source file version management system registers the source files that make up the development target program, performs exclusive control of editing processing for the registered source files, and manages the change history of the edited source files In the management system, the source file is analyzed according to the programming language of the source file, a method file is generated by dividing the source file into source information files of common information other than methods and method units, and the method file is Source file division registration means for registering as a target of the exclusive control and change history management is provided.

  Japanese Unexamined Patent Application Publication No. 2007-122135 discloses a development support apparatus that supports software development by notifying other deliverables that are affected by the corrected deliverables for the deliverables at each stage of the development process. Has been. The development support apparatus includes a request description document describing a software request, a design model created from the request description document, and a development support apparatus that supports development of a product that is a program code created from the design model. A storage unit that stores a product and correspondence information between the product, a correction reception unit that receives an input of the product to be corrected, and a product received by the correction reception unit as a starting point. By tracking correspondence information between stored artifacts, a correction tracking unit that tracks other artifacts affected by the artifact to be corrected, a correction notification unit that notifies the artifacts tracked by the correction tracking unit, It is characterized by having.

JP 2005-266976 A JP 2000-20298 A JP 2002-41488 A JP 2006-277435 A JP 2007-122135 A

  In the conventional version management system, it is possible to avoid the risk of multiple developers updating the same file at the same time, but related files that are different from the files that are checked in are updated. In some cases, even if the file is affected by the update of the related file, it may not be possible to avoid the state of checking in the file without reflecting the effect of the update. .

  Also, in the conventional bug management system, the developer can check the details of each request from the list of requests currently made in the project, but the request is related to the part that he / she wants to update. Whether or not there exists must be confirmed manually one by one, and there is a problem that it is not realistic when the scale of the project increases.

  An object of the present invention is to provide a source code update notification apparatus and a source code update notification method that prevent a plurality of developers from updating a plurality of source codes having a dependency relationship at the same time.

  The source code update notification device according to the present invention comprises request registration means, dependency relationship access means, developer map access means, and notification means. The request registration means receives request information including source code from the client device. The dependency relationship access means refers to a dependency relationship graph that associates a plurality of source codes with a plurality of dependency source codes, and searches for the corresponding source code corresponding to the source code among the plurality of dependency source codes. The developer map access means refers to a developer map that associates a plurality of file names with a developer identification information set, and corresponds to a corresponding development code corresponding to a source code file including the corresponding source code from the developer identification information set. Search for person identification information. The notification means notifies the request information to the developer indicated by the corresponding developer identification information.

  The source code update notification method according to the present invention includes a step of receiving request information including a source code from a client device, and a dependency graph associating the plurality of source codes with the plurality of dependent source codes. A source including the corresponding source code from the developer identification information set by searching for the corresponding source code corresponding to the source code and a developer map that associates a plurality of file names with the developer identification information set; A step of retrieving corresponding developer identification information corresponding to the code file; and a step of notifying the request information to a developer indicated by the corresponding developer identification information.

  A source code update notification program according to the present invention includes a step of receiving request information including a source code from a client device, and a dependency graph that associates a plurality of source codes with a plurality of dependent source codes, A source including the corresponding source code from the developer identification information set by searching for the corresponding source code corresponding to the source code and a developer map that associates a plurality of file names with the developer identification information set; The computer is executed to search for the corresponding developer identification information corresponding to the code file, to notify the developer of the request information indicated by the corresponding developer identification information, and to the computer.

  According to the source code update notification device and the source code update notification method according to the present invention, the developer can check whether or not the source code to be updated conflicts with the update of another developer. It is possible to prevent a plurality of developers from updating a plurality of source codes at the same time.

  An embodiment of a source code update notification device according to the present invention will be described with reference to the drawings. The source code update notification device is applied to a source code update notification system 1 as shown in FIG. The source code update notification system 1 is connected so that a plurality of computers can mutually transmit information to and from each other. The plurality of information processing apparatuses include a client apparatus 100 and a server apparatus 200. There may be a plurality of client devices 100 in the source code update notification system 1, and at this time, the client device 100 may send a processing request to the server device 200 at the same time.

  The client device 100 includes a processing request unit 11 and a work space 12. The work space 12 is a storage area secured in the secondary storage device included in the client device 100, and is assigned to each developer. The workspace 12 holds a copy of the directory configuration checked out from the server device 200. The processing request unit 11 receives a processing request input from the developer via the input device, and transmits the requested processing to the server device 200. The processing is processing related to source code update, and includes “checkout”, “request creation”, and “checkin”. Further, the processing request unit 11 accesses the work space 12 and acquires the corresponding source code file based on the path information of the source code file.

  The server apparatus 200 includes a check-out processing unit 21, a check-in processing unit 22, a request registration unit 23, a notification unit 24, a repository access unit 25, a dependency access unit 26, a request access unit 27, a developer map access unit 28, and a repository. 31, a dependency relationship graph 32, a request storage 33, and a developer map 34.

  The checkout processing unit 21 passes the path of the target file received from the processing request unit 11 to the repository access unit 25, receives the source code file checked out from the repository 31, and transmits the source code file to the client device 100. .

  The check-in processing unit 22 passes the path of the target file and the source code file received from the processing request unit 11 to the repository access unit 25. The check-in processing unit 22 returns the check-in result returned from the repository access unit 25 to the processing request unit 11. The check-in processing means 22 also analyzes the file to be checked in, extracts the relationship between the function or class or method, and the function or method that is called in the function or method, and determines the dependency relationship access means. 26. For extracting the relationship between the function, class, and method, for example, a method described in Japanese Patent Laid-Open No. 2000-20298 is used. The check-in processing unit 22 further passes the source code file name received from the processing request unit 11 and the developer ID of the checked-in developer to the developer map access unit 28. If the check-in processing unit 22 receives a request from the processing request unit 11, it passes the request to the request access unit 27. The check-in processing unit 22 finally returns the processing result to the processing request unit 11 and passes the updated request to the notification unit 24.

  The request registration unit 23 receives the request from the processing request unit 11, sets the status of the request to “open”, and passes it to the request access unit 27. When the request registration processing result is returned from the request access unit 27, the request registration unit 23 returns the result to the processing request unit 11 and passes the registered request to the notification unit 24. The request registration unit 23 also passes the requested source code file name and developer ID received from the processing request unit 11 to the developer map access unit 28.

  The notification unit 24 passes the file name and the method name indicated by the request received from the check-in processing unit 22 or the request registration unit 23 to the dependency access unit 26. The notification unit 24 further passes the tree received from the dependency access unit 26 to the request access unit 27, and if there is a request whose status is “open” for each method on the tree, receives a list of requests. The notification unit 24 further scans the received request list in order to extract the file name, method name, and developer, and creates a notification list for each developer with the conflict flag set to true. The notification means 24 also searches the developer map 34 with the file name, acquires the developer ID, sets the conflict flag to false for the developer ID not included in the request, and lists the notifications. Create The notification unit 24 also accesses the developer map access unit 28 from the file name to which each method on the tree belongs with respect to the method for which the status is “open” from the method tree to which the method is referenced. Then, a list of developer IDs is acquired, the conflict flag is set to false, and the notification is updated for each developer. The notification unit 24 further notifies each developer of the updated notification.

  The repository access unit 25 accesses the repository 31 based on the path of the target file received from the checkout processing unit 21 and checks out the file. The repository access unit 25 also accesses the repository 31 based on the path of the target file received from the check-in processing unit 22 and checks in the received file. The repository access means 25 is implemented using, for example, open source “CVS” and “Subversion”.

  The dependency relationship access means 26 returns a tree of methods referring to the method from the received file name and method name, or depends on the directed relationship between the two received file name and method name pairs. A new addition or update is made to the relationship graph 32.

  The request access means 27 returns a request whose status is “open” among the requests including the received method name, registers or updates the received request in the request storage 33, and returns a processing result. To do.

  The developer map access means 28 adds or updates the relationship between the received file name and the developer ID to the developer map 34, or returns the developer associated with the received file name.

  The repository 31 is a version management database, and manages data by attaching a version number to time-series data of files. For example, as the repository 31, open source “CVS” and “Subversion” databases are used.

  The dependency relationship graph 32 stores a directed graph representing a call relationship between a function, a class, and a method (hereinafter abbreviated as “source code”). That is, the directed graph associates each source code with another source code that is affected by the update of the source code. In the directed graph, for example, in a call relationship between methods, each method is uniquely specified by a file name and a method name.

  The request storage 33 is a database that stores requests. The developer map 34 stores a map in which a file name is associated with a list of developers who have developed the file.

  The repository 31, the dependency graph 32, the request storage 33, and the developer map 34 may be on the server device 200 or in a storage area accessible from the server device 200.

  FIG. 2 shows requests stored in the request storage 33. The request 40 includes a request ID 41, a change reason 42, a developer ID 43, a status 44, and a plurality of source code information 45-1 to 45-N. The request ID 41 identifies the request 40. The change reason 42 indicates the reason for changing the source code according to the request 40. The developer ID 43 indicates one of a plurality of developer IDs respectively assigned to the plurality of developers, and identifies the developer who registers the request 40. The status 44 indicates the state of the source code that is changed by the request 40. The state includes “open” and “close”. The “open” indicates that the source code changed by the request 40 is being updated. The “close” indicates that the source code changed by the request 40 has been updated. Each source code information 45-i (i = 1, 2, 3,..., N) of the plurality of source code information 45-1 to 45-N indicates a source code to be changed by the request 40, and a file name 46 And method name 47 are shown. The file name 46 indicates the file name of the file including the source code changed by the request 40. The method name 47 indicates the method name of the method including the source code changed by the request 40.

  FIG. 3 shows a notification notified to the developer by the notification means 24. The notification 50 indicates a developer ID 51, a request 52, and a plurality of lists 53-1 to 53-N. A request 52 indicates one of the requests stored in the request storage 33. The developer ID 51 indicates one of a plurality of developer IDs respectively assigned to a plurality of developers, and identifies the developer who created the request indicated by the request 52. Each list 53-i of the plurality of lists 53-1 to 53-N indicates a file name 54, a method name 55, and a conflict flag 56. The method name 55 indicates the method name of one method among a plurality of methods indicated by a tree (a tree received from the dependency access means 26) referring to the method specified by the request indicated by the request 52. . The file name 54 indicates the file name of the file including the method indicated by the method name 55. The conflict flag 56 indicates whether or not the update of the method indicated by the method name 55 is in conflict, and indicates a value of either true or false. The true indicates that there is a conflict. The false indicates that there is no competition.

  That is, when the notification 50 is created in response to the request 40, the request 52 indicates the request ID 41.

  FIG. 4 shows a developer map stored by the developer map 34. The developer map 60 is a map in which a file name is associated with a developer ID that has developed the source code file, and the file name set 61 is associated with the developer set 62. That is, an arbitrary element of the file name set 61 corresponds to one element of the developer set 62. The element of the file name set 61 identifies a source code file and indicates the file name of the source code file. The element of the developer set 62 identifies a developer who has developed the source code file, and indicates a developer ID that identifies the developer. One element of the developer set 62 indicates a plurality of developer IDs that respectively identify the plurality of developers when there are a plurality of developers who have developed the source code file. The developer map 60 can add, update, or delete the association between the developer ID and the file name at the time of check-in or request registration, or at any other timing.

  The embodiment of the source code update notification method according to the present invention is executed by the source code update notification system 1. It includes an operation when a process is input, a check-out operation, a request creation operation, a check-in operation, and an operation when a request is received.

  FIG. 5 shows an operation when a process is input. When the developer causes the source code update notification system 1 to execute one of the processes “check out”, “request creation”, and “check in”, the client apparatus 100 sends information necessary for the process. To enter. That is, when the developer checks out the target file on the repository 31, the developer designates “checkout” as the type of processing, and inputs the path of the target file to the client device 100. At this time, a plurality of target file paths can be specified, or a directory name can be specified. When creating a request, the developer designates “request creation” as the type of processing and inputs a request to be registered to the client apparatus 100. When the developer checks in the target file, the developer specifies “check-in” as the processing type, and inputs the developer ID and the path of the target file to the client device 100. At this time, it is possible to specify a plurality of target files or to specify them by directory names. Further, the developer inputs a request with the status updated to “close” to the client device 100 as necessary.

  The processing request unit 11 determines the type of processing based on the information input to the client device 100 (step a1). If the processing type is “checkout”, the processing request unit 11 sends the received path of the target source code file to the checkout processing unit 21 on the server device 200 (step a2). If the process type is “request creation”, the process request unit 11 sends the received request to the request registration unit 23 on the server device 200 (step a3). If the type of processing is “check-in”, the processing request unit 11 accesses the workspace 12 from the path of the received target source code file and acquires the corresponding source code file (step a4). Next, the processing request unit 11 sends the received developer ID, the path of the target source code file, the source code file, and the request updated as necessary to the check-in processing unit 22 on the server device 200 (step a5). ).

  FIG. 6 shows the check-out operation. The check-out operation starts after step a2 is executed. The check-out processing unit 21 passes the path of the target source code file received from the processing request unit 11 to the repository access unit 25 (step b1). The repository access unit 25 accesses the repository 31 based on the received path of the target source code file and checks out the source code file (step b2). The checkout processing means 21 returns the checked out source code file to the processing requesting means 11 on the client device 100 (step b3). The process request unit 11 updates the workspace 12 with the received source code file (step b4).

  FIG. 7 shows a request creation operation. The request creation operation starts after step a3 is executed. The request registration unit 23 sets the status of the request received from the processing request unit 11 to “open”, and passes the set request to the request access unit 27 (step c1). The request access unit 27 registers the received request in the request storage 33 (step c2). The request registration unit 23 returns a processing result indicating that the request is registered in the request storage 33 to the processing request unit 11 of the client device 100 (step c3). The processing request unit 11 displays the processing result (step c4). The request registration unit 23 passes the registered request to the notification unit 24 (step c5). The request registration unit 23 passes the file name and developer ID in the request to the developer map access unit 28 (step c6). The developer map access means 28 adds the relationship between the received file name and developer ID to the developer map 34 (step c7). At this time, the processes of steps c3 to c4, the process of step c5, and the processes of steps c6 to c7 are executed simultaneously in parallel.

  FIG. 8 shows the check-in operation. The check-in operation starts after step a5 is executed. The check-in processing unit 22 passes the path and file of the target source code file received from the processing request unit 11 to the repository access unit 25 (step d1). The repository access unit 25 accesses the repository 31 based on the path of the received target source code file, and checks in the received source code file (step d2). The check-in processing means 22 analyzes the checked-in source code file and extracts the relationship between the method and the method that is calling in the method (step d3). The check-in processing unit 22 passes the extracted relation to the dependency relationship access unit 26 (step d4). The dependency relationship access means 26 updates the dependency relationship graph 32 based on the received relationship (step d5). The check-in processing means 22 passes the file name and developer ID to the developer map access means 28 (step d6). The developer map access means 28 adds the received file name and the developer's association to the developer map 34 (step d7).

  If the check-in processing unit 22 has received a request from the client device 100, the check-in processing unit 22 passes the received request to the request access unit 27 (step d8). The request access unit 27 registers the received request in the request storage 33 (step d9). The check-in processing unit 22 returns a processing result indicating that the request has been registered in the request storage 33 to the processing request unit 11 of the client device 100 (step d10). The processing request unit 11 displays the processing result (step d11). The check-in processing means 22 passes the registered request to the notification means 24 (step d12). At this time, the process of steps d10 to d11 and the process of step d12 are executed simultaneously in parallel.

  FIG. 9 shows the operation when a request is received. The operation upon receipt of the request starts after step d12 or after step c5. The notification unit 24 passes the file name and method name described in the request to the dependency relationship access unit 26 (step e1). The dependency relationship access means 26 accesses the dependency relationship graph 32 and obtains a list of method trees referring to the received method (step e2). The notification unit 24 passes the list of trees to the request access unit 27 (step e3). The request access unit 27 accesses the request storage 33 and searches for a request whose status indicates “open” from among the requests including each of the methods included in the tree list (step e4). The notification unit 24 sequentially scans the retrieved request list to extract the file name, method name, and developer ID, sets the conflict flag to true, and creates a notification list for each developer (step e5). The notification unit 24 passes the file name extracted in step e5 to the developer map access unit 28 (step e6).

  The developer map access means 28 accesses the developer map 34 based on the received file name and returns a list of developer IDs (step e7). The notification means 24 sets the conflict flag to false for the developer ID not included in step e5, and creates a notification list for each developer (step e8). The notification unit 24 passes the list obtained by removing the method name included in the request of step e5 from the list of trees to the developer map access unit 28 (step e9). The developer map access means 28 accesses the developer map 34 and searches for the developer ID of the source code file including each of the methods (step e10). The notification means 24 sets the conflict flag to false based on the searched developer ID and updates the notification list (step e11). The notification unit 24 notifies the request to each developer in the notification list (step e12). As a notification method in the notification unit 24, a method of transmitting to a terminal used by a developer by e-mail or the like is conceivable. In this case, the developer ID uses a mail address assigned to each developer.

  According to the source code update notification method of the present invention, when the developer starts changing the source code, by sending a request indicating the source code to the server device 200 at the start of the update of the source code, You can check if changes have already been made that affect the function, class, or method you are updating before you start making changes. Developers can also know why the changes are being made, if any, so that developers can determine whether they can implement the updates without conflict before starting the changes. Can be judged.

  The source code update notification system 1 is a mechanism for registering a request affected by the request and notifying the developer who is developing the source code with the fact that there is a conflict when registering the request. Have For this reason, developers who are registering requests and updating their source code will be affected by the change, and when other developers start a change to a source code other than the source code. , You can know the changes.

FIG. 1 is a block diagram showing an embodiment of a source code update notification device according to the present invention. FIG. 2 is a diagram illustrating a request. FIG. 3 is a diagram illustrating notification. FIG. 4 is a diagram showing a developer map. FIG. 5 is a flowchart showing an operation when a process is input. FIG. 6 is a flowchart showing the check-out operation. FIG. 7 is a flowchart showing a request creation operation. FIG. 8A is a flowchart showing the first half of the check-in operation. FIG. 8B is a flowchart showing the second half of the check-in operation. FIG. 9A is a flowchart showing the first half of the operation when a request is received. FIG. 9B is a flowchart showing the second half of the operation when a request is received.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1: Source code update notification system 100: Client apparatus 11: Processing request means 12: Workspace 200: Server apparatus 21: Check-out processing means 22: Check-in processing means 23: Request registration means 24: Notification means 25: Repository access means 26: Dependency access means 27: Request access means 28: Developer map access means 31: Repository 32: Dependency relationship graph 33: Request storage 34: Developer map 40: Request 41: Request ID
42: Reason for change 43: Developer ID
44: Status 45-1 to 45-N: Source code information 46: File name 47: Method name 50: Notification 51: Developer ID
52: Request 53-1 to 53-N: List 54: File name 55: Method name 56: Conflict flag 60: Developer map 61: File name set 62: Developer set

Claims (15)

Request registration means for receiving request information including source code from a client device;
Dependency access means for searching for a corresponding source code corresponding to the source code among the multiple dependency source codes with reference to a dependency graph that associates a plurality of source codes with a plurality of dependent source codes;
A developer that searches a developer map that associates a plurality of file names with a developer identification information set, and searches for the corresponding developer identification information corresponding to a source code file including the corresponding source code from the developer identification information set. Map access means;
A source code update notification device comprising: notification means for notifying the request information to a developer indicated by the developer identification information. In claim 1,
A request storage for storing multiple request information respectively indicating a request source code and a request file name;
Request access means for searching for a corresponding file name indicated by the corresponding request information indicating the source code of the plurality of request information,
A source code update notification device for searching for corresponding developer identification information corresponding to the corresponding file name from the developer identification information set. In claim 2,
The request information further indicates a file name of a file indicating the source code,
The request registration unit is a source code update notification device that updates the request storage so that the plurality of request information includes the request information. In either claim 2 or claim 3,
Each of the plurality of request information further indicates request developer identification information,
The notification means further notifies the developer indicated by the non-update developer identification information not indicated by the corresponding request information of the corresponding developer identification information that the source code does not conflict with the source code update notification device . In any one of Claims 2-4,
Each of the plurality of request information further indicates a status of the request source code,
The request access means searches for update completion request information in which the request source code of the corresponding request information is update completion,
The notification means further notifies the developer indicated by the update completion developer identification information indicated by the update completion request information of the corresponding developer identification information that the source code is not in conflict. apparatus. Receiving request information including source code from a client device;
Searching for a corresponding source code corresponding to the source code among the plurality of dependent source codes with reference to a dependency graph that associates a plurality of source codes with a plurality of dependent source codes;
Searching for a corresponding developer identification information corresponding to a source code file including the corresponding source code from the developer identification information set with reference to a developer map that associates a plurality of file names with the developer identification information set; ,
A source code update notification method comprising: notifying the request information to a developer indicated by the developer identification information. In claim 6,
Searching for a corresponding file name indicated by the corresponding request information indicating the source code of the plurality of request information with reference to a request storage for storing the plurality of request information indicating the request source code and the request file name, respectively;
A source code update notification method further comprising: searching for the corresponding developer identification information corresponding to the corresponding file name from the developer identification information set. In claim 7,
The request information further indicates a file name of a file indicating the source code,
Furthermore,
The source code update notification method further comprising: updating the request storage so that the multiple request information includes the request information. In either claim 7 or claim 8,
Each of the plurality of request information further indicates request developer identification information,
Furthermore,
The source code update notification method further comprising the step of further notifying the developer indicated by the non-updated developer identification information not indicated by the corresponding request information of the corresponding developer identification information that the source code is not in conflict. . In any one of Claims 7-9,
Each of the plurality of request information further indicates a status of the request source code,
Furthermore,
Searching for update completion request information in which the request source code of the corresponding request information is update completion;
And further notifying the developer indicated by the update completion developer identification information indicated by the update completion request information of the corresponding developer identification information that the source code is not in conflict. Notification method. Receiving request information including source code from a client device;
Searching for a corresponding source code corresponding to the source code among the plurality of dependent source codes with reference to a dependency graph that associates a plurality of source codes with a plurality of dependent source codes;
Searching for a corresponding developer identification information corresponding to a source code file including the corresponding source code from the developer identification information set with reference to a developer map that associates a plurality of file names with the developer identification information set; ,
A source code update notification program for causing a computer to execute the step of notifying the request information to a developer indicated by the developer identification information. In claim 11,
Searching for a corresponding file name indicated by the corresponding request information indicating the source code of the plurality of request information with reference to a request storage for storing the plurality of request information indicating the request source code and the request file name, respectively;
A source code update notification program for causing the computer to further execute a step of searching for corresponding developer identification information corresponding to the corresponding file name from the developer identification information set. In claim 12,
The request information further indicates a file name of a file indicating the source code,
Furthermore,
A source code update notification program for causing the computer to further update the request storage so that the multiple request information includes the request information. Either of claim 12 or claim 13,
Each of the plurality of request information further indicates request developer identification information,
Furthermore,
Source code for further causing the computer to further notify the developer indicated by the non-updated developer identification information not indicated by the corresponding request information of the corresponding developer identification information that the source code is not in conflict Update notification program. In any one of Claims 12-14,
Each of the plurality of request information further indicates a status of the request source code,
Furthermore,
Searching for update completion request information in which the request source code of the corresponding request information is update completion;
Further causing the computer to further notify the developer indicated by the update completion developer identification information indicated by the update completion request information of the corresponding developer identification information that the source code is not in conflict. Source code update notification program.

Images