JP3611178B2 - Program development management support device - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a program development management support apparatus that supports management of software software development and management of products such as source code and documents.
[0002]
[Prior art]
Conventionally, in program development, Japanese Patent Laid-Open No. 9-16391 (Title of Invention: Software Development Support / Maintenance Support System) and Japanese Patent Laid-Open No. 9-258966 (Title of Invention: Software Providing System, Software Providing Device, and Software Providing) As disclosed in (Apparatus), there is a configuration management apparatus for a plurality of developers in a project developing a program to share and use a product.
[0003]
These are used to centrally manage the difference information between versions of shared products (source code, documents, etc.) in a directory hierarchy called a repository. The contents of the product are taken out, and the product is changed and distributed and the repository is updated based on the exclusive control in which the take-out destination and the repository are associated with each other.
[0004]
The main challenge of these technologies is to distribute and provide the products updated by each developer to the work areas of other developers, and the production to be distributed and provided to the work areas of each developer. Things are always kept up-to-date by the administrator managing the repository centrally.
[0005]
On the other hand, unlike these techniques, there is a technique for grasping the state of the product taken out in the work area of each developer by comparing the product in the work area with the repository from the person in charge.
There is also an apparatus for managing the progress of work in program development. This device manages schedules and results in units of work contents of each developer.
Also, there is an apparatus (Japanese Patent Laid-Open No. 9-16391) that supports work instructions and reports using a mail function in program development.
[0006]
[Problems to be solved by the invention]
By the way, in the program development using the configuration management device disclosed in the above publication, the product taken out to the work areas of a plurality of developers is repeatedly corrected and taken out. May not be uniform.
[0007]
In addition, because the purpose of the correction and the work situation do not generally correspond to the version of the product, the checked-in product may be a personal backup of the developer, or it may be a test product. Therefore, it is difficult to grasp from the version information whether the product is in a state that can be safely used by a non-developer in charge (administrator).
[0008]
Therefore, it is required to be able to grasp the state and work status of the product in a work area different from that of the self and all work areas, and to perform product management synchronized with the work situation.
[0009]
For example, the project manager knows the version and status of the products used by all developers, and “unused old products” or “unnecessary products are taken out” And whether the product to be taken out has been taken out, and the presence / absence of the product being corrected before release, etc. Sex can be maintained.
[0010]
In addition, the developer can check whether other developers have made corrections, check the work status, and the purpose of the work, so that safe products that have been tested can be retrieved from the repository and used. .
[0011]
However, in the above prior art, the administrator cannot grasp the status of each developer's work area until each developer updates the repository. There is a problem that it is not possible to grasp whether or not it is corrected.
Also, in the conventional technology that grasps the state of the product taken out to the work area of each developer by comparing the product in the work area with the repository from the person in charge, the state of his / her product As in the prior art disclosed in JP-A-9-16391 and JP-A-9-258966, the state of the product in the work area of other developers cannot be understood. There is a problem.
[0012]
On the other hand, in large-scale program development, work instructions from the administrator to each person in charge of development become enormous. Therefore, managers and developers in charge of receiving instructions must efficiently understand, implement, and report instructions. In program development, work and products are closely related, and it is necessary to manage the work contents and the state of the product in correspondence.
[0013]
However, in the conventional device that manages the progress of work and the conventional device that supports work instructions and reports using the mail function, the management and work instructions and reports corresponding to the work contents and the state of the product are sent. There is a problem that it cannot be managed in association with the product.
[0014]
The present invention has been made to solve these problems, and a first object of the present invention is to compare the state of products in each developer's work area by comparing all retrieval destinations with repositories. It is to provide a program development management support apparatus that can grasp the above collectively.
[0015]
The second object of the present invention is to store the work status of each developer in charge for the product in a centrally managed database, and use the stored work status information and product version information stored in the repository. Provides a program development management support device that can realize program development management that combines product management for managing product versions and work status management for managing the status of work performed on products. It is to be.
[0016]
The third object of the present invention is to simultaneously manage work instructions from the manager to each developer in charge at the manager side and at the developer side. It is an object to provide a program development management support apparatus capable of grasping the situation of a person who has a problem and capable of effectively allocating resources.
[0017]
[Means for Solving the Problems]
In order to achieve the above object, the present invention provides a program development management support apparatus that supports management when a program is developed using a product such as a source code and a document that can be shared by a plurality of program developers. ,
Product storage means for storing the product in a directory structure; work storage means for each person in charge for storing the product taken out from the product storage means by a client computer used by each program development person in charge; The directory of the product taken out from the product storage means by the program development person, the state table for storing the state of the product at the take-out destination and the take-out destination in the product unit, and when instructed by the administrator or at a predetermined time Collecting the work status of the product taken out in the work storage means for each person in charge at intervals and registering it in the status table, and specified by all products or managers in the product storage means Product tube for processing the display location of the product and the working state on the display device screen in a directory structure Characterized in that it comprises a means.
[0018]
Also, a work status management table for storing each product development person in the product unit and the state of the product stored in the work storage means for each person in charge and the current work situation of the program development person for the product. In response to the work status notification from the client computer used by each program developer, the process of registering the status and work status of the corresponding product in the work status management table, and the inquiry request from each program developer On the other hand, it is characterized by comprising a work status management means for performing processing for returning the requested product state to the client computer used by the program developer in charge and displaying it.
[0019]
Also, the work instruction storage means for storing the work instructions for each program development person input from the administrator's client computer, and the corresponding program development person uses the work instructions stored in the work instruction storage means. All of the work instructions stored in the work instruction storage means or a work instruction addressed to a designated program development person in response to a request sent from the client computer by the administrator or the program development person in charge. And a work instruction management means for performing processing for returning and displaying information including the contents of the current work number and the current remaining work number to the request source.
[0020]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a system configuration diagram showing an embodiment of a program development management support system to which the present invention is applied.
[0021]
The program development management support system of this embodiment includes a server 101 managed by an administrator, a client computer 102 used by the administrator, and client computers 103-105 used by users A to C who are project developers. It is composed of However, the client computer 105 used by the user C is connected to a server 107 connected to the server 101 via the network 106.
[0022]
The server 101 managed by the administrator incorporates a program constituting the program development management support apparatus 109 in the memory 108, and stores a repository 110, history management information 111, and work status management information 112 as data. It is like that. A program development management support apparatus 120 similar to that of the server 101 is also incorporated in the memory 119 of the server 107 connected via the network 106.
[0023]
The program development management support apparatus 109 includes a product management unit 113, a work status management unit 114, and a work instruction management unit 115. These product management unit 113, work status management unit 114, and work instruction management unit 115 are configured in detail by programs. The program development management support apparatus 120 in the server 107 is similarly configured.
[0024]
User A and user B are project developers who can access the server 101 from the client computers 103 and 104, and have a work area 116 for the user A and a work area 117 for the user B in the storage device of the server 101. The product taken out from the repository 110 can be stored. In addition, the user C has a work area 118 of the user C in the storage device of the server 107 connected by the network 106, and can store the product taken out from the repository 110. Here, when a computer on the network that cannot directly access the repository 110 such as the server 107 (here, the server 107) accesses data such as the repository 110, or conversely, a computer that has the repository 110 (here, the server 101). When accessing the work area of a computer (here, the server 107) on the network, the program development management support apparatuses 109 and 120 incorporated in the respective computers can access the program development management support apparatuses 120 and 109 of the other computer. Request remote processing and receive results.
[0025]
In the above configuration, first, the processing flow of the product management unit 113 will be described with reference to FIGS.
[0026]
2 is a flowchart showing the processing flow of the product management unit 113, FIG. 3 is a configuration example of the product take-out destination information table 301, FIG. 4 is a configuration example of the state database table 401, and FIG. Example, FIG. 6 shows the meaning of status symbols used in the present embodiment, FIG. 7 shows an example of a display screen of product distribution status, FIG. 8 shows an example of a detailed screen of analysis contents of product distribution status, and FIG. It is a figure which shows the example of a detailed screen of a distribution condition.
[0027]
In the work environment shown in FIG. 5, the server “cet” 101 can be accessed via two developers “Nishi” and “shin” who are local users A and B and the network 106. The development person “suga” on the server “cygnus” 107 is currently extracting “nishi.mem” 510, 511, 512 as a product from “Doc / patent / vw.921” of the repository 110. Is shown.
[0028]
In such a working environment, the product management unit 113 of the program development management support apparatus 109 in the server 101 receives each instruction of the project from the repository 110 when instructed by the administrator or at predetermined time intervals. Extraction destination information is extracted from the history management information 111 in order to grasp the state of the products 510 to 512 taken out to the work areas 116, 117, 118 of the developers “nishi”, “shin”, and “suga” (Step 201), and is registered in the extraction destination information table 301 shown in FIG. Here, the state of the product, which will be described later with reference to FIG. 6, is, for example, a state such as latest, being corrected, scheduled to be registered, scheduled to be deleted, or old.
[0029]
The take-out destination information table 301 is provided in the product management unit 113, and includes information on a product take-out destination server name 302 and a directory 303 in the server, as shown in FIG. . In the example of the work environment in FIG. 5, there are “cet” and “cygnus” as the extraction destination server name 302, and “/pj/ooplus/us.shin” and “/ pj /” are stored in the directory 303 of the extraction destination server, respectively. "ooplus / us.nish""and" /pj/ooplus/us.suga "are registered.
[0030]
Next, all directory structures of the repository 110 are analyzed and registered in the state database table 401 shown in FIG. 4 (step 202).
[0031]
The state database table 401 is data having a tree structure similar to a repository structure in which one table corresponds to one directory and one product, and in the case of a directory, has data of a pointer 405 to a subdirectory. Each state database table 401 includes a type 402 indicating whether the table is a file or a directory, a product name 403, a repository path 404, and a pointer 405 (pointing to a subdirectory table when the type 402 is a directory). Data), the status symbol 406 of the product at each destination, and the detailed status 407 of the product at each destination.
[0032]
In the example of FIG. 5, the type 402 is “file”, the product name 403 is “nishi.mem”, the repository path 404 is “Doc / patent / VW.H921”, the status symbols 406 are “=”, “LM”. ”,“ NC ”, and the detailed status 407 of each status stores information indicating that the revision is“ 1.3 ”and the reference branch is the main series. Here, the reference branch is a revision that becomes a reference for a new transition when a revision transition flow is branched. The main sequence is a flow of revisions made first.
In this example, since there is no subdirectory, information on the pointer 405 to the subdirectory is not registered.
[0033]
In step 202, after the state database table 401 is initialized, the repository structure is analyzed and registered in the state database table 401 based on the analysis result. The symbol 406 and the detailed status 407 are not set.
[0034]
When the initialization of the state database table 401 and the analysis of the repository structure are completed (step 202), each extraction destination 1. . . Analyze the status of the product at n. The product status has a meaning 62 as shown in FIG. 6, and a corresponding code 61 is assigned to each status. For example, “=” indicates that the product is in the latest state, “LM” indicates that the product is being corrected, “LA” indicates that the product is scheduled to be registered, “LR” indicates that the product is scheduled to be deleted, and “NP” indicates that the product is old. There is a status to indicate that it exists.
[0035]
Next, it is determined whether or not the server name 302 of the extraction destination information table 301 is a computer that is accessed via the network 106 (step 204), and if the server name 302 is the server 107 that is accessed via the network 106, A remote processing request for status acquisition is made to the program development management support apparatus 120 incorporated in the server 107, and the status of the product stored in the work area 118 of the user C is acquired (step 205).
[0036]
Next, the acquired status is analyzed. The analysis is divided into a case where the detailed analysis is performed and a case where the detailed analysis is not performed in consideration of the processing speed (step 206). In status analysis processing (step 207) for the purpose of high-speed processing, only the status of the product at the take-out destination is analyzed and registered in the state database table 401 (step 208). On the other hand, in status analysis processing that does not require high-speed processing (step 209), detailed data such as revision numbers and reference branch names are also analyzed and registered in the state database table 401 (step 210). In the status analysis process of step 207, the status of the product is replaced with the code 61 shown in FIG.
[0037]
In the status code 61 of FIG. 6, the status codes “=” and ““ ”“ latest ”mean that the state of the product being taken out is exactly the same as the repository.
Further, the status code “LM” of “under correction” means that the revision of the product being taken out is the same as that registered in the repository, but the content of the product has been corrected.
Further, the status code “LA” “scheduled for registration” means that the product is scheduled to be registered in the repository.
The status code “LR” “scheduled to be deleted” means that the extracted product is scheduled to be deleted from the repository.
The status code “NC” “not here” means that the product is registered in the repository but not taken out to the work area.
In addition, the status code “NM” of “old & being modified” means that the revision of the product being taken out is older than the one already registered in the repository, and the contents have been corrected at the takeout destination. is there.
In addition, the status code “UC” of “Old & Duplicate Correcting” indicates that the product that has been retrieved as a result of checking in the product in the “Old & Correcting” state is the latest registered in the repository. It means that the difference information with the content is changed to the embedded information.
The status code “AT” of “deleted” means that the extracted product has already been deleted from the repository and the extraction destination.
Further, the status code “EI” “abnormal registration” means that there is a contradiction between the state of the repository and the extraction destination, and the product is not correctly registered.
A status code “?” Of “unregistered” means that the product has not yet been registered in the repository and is not under version control.
Further, status codes “??” and “-” of “unrelated” mean that the extraction destination directory corresponds to a different repository, or that the extraction destination directory does not exist.
A status code “I” of “ignore” means that the file is not related to product version management (link file, binary file, etc.).
A status code “ERR” of “error” means that the analysis has failed for some reason.
Further, the status code “R” of “register” means that the directory is the extraction destination directory designated when the product is extracted.
In addition, the status code “A & =” of “deleted & up-to-date” indicates that the product being taken out is in the “latest” state at the take-out destination, but has already been deleted from the repository by another user. It means that.
In addition, the status code “A & LM” of “deleting & modifying” indicates that the product being taken out exists in the state of “modifying” at the retrieval destination, but has already been deleted from the repository by another user. It means that
In addition, the status code “A & LA” of “scheduled for deletion & registration” indicates that the product being taken out is in the “scheduled to be registered” state at the destination, but has already been deleted from the repository by another user. It means that
In addition, the status code “A & LR” of “scheduled for deletion & deletion” indicates that the product being taken out is in the state of “scheduled for deletion” at the destination, but has already been deleted from the repository by another user. It means that
The status code “A & NP” of “deleted & old” means that the product being taken out is in the “latest” state at the takeout destination, but has already been deleted from the repository by another user. Meaning.
In addition, the status code “A & NM” of “deleted & old & amending” exists, but the product being taken out is present in the state of “old & amending” at the takeout destination, but it has already been deleted from the repository by another user. Means deleted.
In addition, the status code “A & UC” of “Deleted & Old & Duplicate Correcting” indicates that the product being taken out exists in the state of “Old & Duplicate Corrected” at the takeout destination, but it has already been changed by another user. It means that it has been deleted from the repository.
In addition, the status code “A & EI” of “delete & abnormal registration” indicates that the product being taken out exists in the “abnormal registration” state at the extraction destination, but has already been deleted from the repository by another user. It means that
In addition, the status code “A &?” Of “deleted & unregistered” indicates that the product that has been extracted exists in the “unregistered” state at the extraction destination, but has already been deleted from the repository by another user. It means that
FIG. 7 is a diagram showing an example of a product distribution status display screen 701 represented by using data obtained by status analysis processing (step 207) in the work environment illustrated in FIG. Is visually expressed using the state database table 401, and the status at each take-out destination is collectively displayed under the product name registered in the repository 110.
[0038]
In the example of FIG. 7, four products “nishi.mem” 702, “suga.mem” 703, “tok.mem” 704, and “tok meisai.fmt” 705 are displayed together with the status at the extraction destination. . In other words, for the product “nishi.mem” 702, three statuses “= LM NC” are displayed. The fact that three statuses are displayed means that three statuses have been taken out. The state at each take-out destination indicates that it is the latest (=), being modified (LM), or not (NC). In addition, for the product “suga.mem” 703, three statuses “== NC” are displayed, indicating that they have been taken out to three destinations. The statuses at the respective extraction destinations are latest (=), latest (=), and not (NC) here. In addition, for the product “tok.mem” 704, three statuses “== NP” are displayed, indicating that the product has been extracted to three extraction destinations. The states at the respective extraction destinations indicate the latest (=), latest (=), and old (NP). Since the status is “old” at the third extraction destination of the “tok.mem” 704, it can be seen that the old version of the product is being used. In addition, for the product “tok meisai.fmt” 705, three statuses “===” are displayed, indicating that they have been taken out to three take-out destinations. The states at the respective extraction destinations are latest (=), latest (=), and latest (=).
[0039]
In the above display state, when it is desired to know detailed analysis information about each product, when a file for which detailed analysis information is desired is selected by a mouse click operation, detailed analysis on the selected product is performed. For example, when it is desired to know detailed analysis information of the product “nishi.mem” 702, the display position of the product “nishi.mem” 702 is selected by a mouse click operation, and the product management unit 113 displays the designated product. The revision number, reference branch name, and the like are analyzed for “nishi.mem” 702 (step 209). Then, after the information obtained by the detailed analysis processing is additionally registered as a character string in the detailed status 407 of the state database table 401, the product distribution status (detail) screen 801 as shown in FIG. Display detailed analysis results.
[0040]
In the product distribution status (details) screen 801 in FIG. 8, the status code (=, LM, NC) at each take-out destination of the designated product “nishi.mem” 702, the revision number (1.3), the size, The branch name and modification date are displayed.
[0041]
Further, on the product distribution status display screen 701 shown in FIG. 7, for example, when the directory name “Doc /” is selected by a mouse click operation and the analysis button 706 is operated, the product management unit 113 is selected. The status of all products belonging to the directory “Doc /” is recursively analyzed, and if there is an extraction destination whose status is not “latest”, an “x” mark 711 is added to the right of the directory name in the directory unit, If all are up-to-date, a “◯” mark 710 is added and displayed. Further, when the directory name with the “x” mark 711 is selected and the detail button 707 is operated, the analysis content detail display screen 708 is opened and the status symbols of all products under the designated directory are displayed. Display a list of products that have a quantity and status that is not “latest”. An enlarged view of the analysis content detail display screen 708 is shown in FIG.
[0042]
Thus, by displaying the “x” mark 711 in the vicinity of the directory name for a product whose status is not “latest”, it is very easy to grasp which product is not “latest”. .
[0043]
Note that when the product reference button 802 is operated by a mouse click operation on the product distribution status detail screen 801 in FIG. 8, the contents of each designated product at the take-out destination can be referred to.
Further, when the status reference button 803 is operated by a mouse click operation, the status information of the designated product can be referred to.
Further, when the log reference button 804 is operated by a mouse click operation, the log information of the designated product can be referred to.
Further, when the difference reference button 805 is operated by a mouse click operation, it is possible to refer to difference information obtained by comparing the contents of the designated products at the respective extraction destinations.
Further, when the branch reference button 806 is operated by a mouse click operation, it is possible to refer to the branch state of the current revision transition of the designated product.
[0044]
FIG. 10 is a flowchart showing the process of the work status management unit 106 and the work flow of the developer.
The developer (users A and B) uses the client computers 103 and 104 to check the program development management support apparatus 109 before correcting or testing the product taken out in the respective work areas 116 and 117. Then, a notification for recording the work situation to be performed is performed (step 1001).
[0045]
Upon receiving this work status notification, the work status management unit 114 updates the work status management information 112 in the work status management table 1101 configured as shown in FIG. 11 (step 1002). The work status table 1101 has an ID number 1102 which is a serial number of the table, and a product name 1103 for recording the work status. Each time a new work status is notified and the table 1101 is updated, the name of the person in charge notified 1104, a notification date and time 1105, a work status code 1106 representing the work status, and a comment 1106 regarding the work are added. The update process in step 1002 will be described in detail later.
[0046]
Here, as shown in FIG. 12, the work status code 1106 includes “1”, “2”, “2”, “work in progress” units such as “coding”, “testing”, “test completed”, and “bug fixing”. Numerical codes such as “3”, “4”... Are assigned. A work situation is a state that occurs during work.
[0047]
The developer in charge who has notified the work status in step 1001 confirms that the update processing (step 1002) of the work status management table 1001 has been completed, and then performs the notified work (step 1003). Then, when the notified work is completed, the developer in charge performs a work completion notification for recording the completion of the work in the work status management table 1101 (step 1004). Upon receiving the work completion notification, the work situation management unit 114 additionally registers in the work situation management table 1101 a record including data indicating that the work has been completed.
[0048]
Other developers in charge who share and use the finished product refer to the work status management table 1101 (step 1005), and the test for the product to be used has been completed and can be used safely. After confirming that the product can be obtained, the product is taken out to the respective work area (step 1006).
[0049]
FIG. 13 is a flowchart showing details of the update process (step 1002) of the work status management table 1101 of FIG.
The work status management unit 114 is a table for checking whether the product work status management table 1101 notified by each developer (users A, B, C) exists in the storage device of the work status management information 112. A search is performed (step 1301). If the work status table 1101 exists (step 1302), it is checked whether or not another developer is using the product from the work status code 1106 and the person-in-charge name 1104 in the final record of the work status table 1101 (step 1302). 1303). If another developer is working (step 1303), the notified developer cannot perform the work, and the update of the work status is regarded as failure (step 1304). However, if another developer is not working, the notified developer name 1104, the notification date 1105, the work status code 1106, and the comment 1107 are additionally registered in the work status management table 1101 (step 1306).
[0050]
If the work status table 1101 does not exist in step 1302, a new work status table 1101 is created in the storage device of the work status management information 110 (step 1305), and the ID number 1102 and the product name 1103 are newly set. Record in the created work status table 1101. Then, the notified developer name 1104, notification date and time 1105, work status code 1106, and comment 1107 are additionally recorded (step 1306), and the update is completed.
[0051]
FIG. 14 is a diagram showing an example of the work status display screen 1401, in which items such as “work in progress” such as “Bug Fixing”, person in charge, notification date, file name, size, attribute, date of last modification, etc. are displayed. .
[0052]
Next, processing of the work instruction management unit 115 will be described.
FIG. 15 is a flowchart showing the process of the work instruction management unit 115 and the work flow of the administrator and the developer. FIG. 16 shows an example of the work instruction status display screen 1601 and FIG. 17 shows an example of the work instruction detail display screen 1701. FIG.
[0053]
The work instruction status display screen 1601 shown in FIG. 16 displays a work instruction code 1602, work person 1603, work instruction date 1604, work status 1605, number of completed work instructions 1606, and number of unfinished work instructions 1607. ing.
[0054]
The work instruction detail screen 1701 of FIG. 17 includes a work instruction code 1702, a work instruction date 1703, a worker in charge 1704 who receives the instruction, an instruction content 1705, a related item description field 1706, a work instruction field 1710. A completion date entry field 1707 is displayed. 15, the administrator first creates a work instruction column 1710 having items as shown in FIG. 17 by using the client computer 102 and stores it in the work instruction storage area in the repository 110 (steps). 1501). When the work instruction is stored in the work instruction storage area in the repository 110, the work instruction management unit 115 sends the work instruction by e-mail to the developer in charge designated by the “instructor in charge” 1704 in the work instruction. (Step 1502). The sent work instructions are stored in the work areas 116, 117, 118 of each developer (step 1503). In the example of FIG. 17, “nishi” is designated as the person in charge of instruction, so that it is stored in the work area 116 of “nishi” who is the user A.
[0055]
In this state, if necessary, the administrator or the developer in charge shows the contents of the work instructions to all the developers in charge or the designated developers in charge stored in the work instruction storage area in the repository 110 in FIG. The number of remaining work instructions is grasped from the number of uncompleted work instructions 1607 (step 1504). When a detail button 1608 in the work instruction status display screen 1601 is selected by a mouse operation, a work instruction detail screen 1701 shown in FIG. 17 is displayed, and the detailed contents of the work instruction can be confirmed. Furthermore, if necessary, the members of the project can be designated to display only the status of work instructions held by the designated members.
[0056]
The developer in charge carries out work such as creating or changing a product such as a source document in accordance with a work instruction from the administrator (step 1505). When the work is completed and the product is checked into the repository 110, input to the log entry column is made with reference to the displayed work instruction status display screen 1601 (step 1506).
[0057]
FIG. 18 is a diagram showing an example in which a work instruction is selected from the work instruction status display screen 1601 and entered in the log entry column.
When the corresponding work instruction code 1602 is selected in the work instruction status display screen 1601 shown in FIG. 16, the product check-in screen 1801 shown in FIG. 18 is displayed, and the work instruction content is set in the log entry field 1802. Is done. When the product is updated, the manager can grasp what is newly created or changed by referring to the log information in the log entry column 1802.
[0058]
The work instruction stored in the work area on the developer side is deleted when the product corresponding to the work instruction is checked in (step 1507). After deleting the work instruction, the administrator side is notified that the work has been completed (step 1508).
[0059]
When the work completion is notified, it is recorded in the corresponding work instruction in the work instruction storage area on the administrator side (step 1509). Then, the number of remaining work is subtracted by one.
When the instruction reference button 1803 in FIG. 18 is selected by operating the mouse, a work instruction list 1901 as shown in FIG. 19A is displayed. When the work instruction code 1903 in the work instruction list 1901 is selected by a mouse operation, the detailed contents of the work instruction as shown in FIG. 19B are displayed.
[0060]
As described above, according to the present embodiment, since it is possible to perform product management corresponding to the work situation in which the state of the product and the work situation in the distributed work area can be grasped collectively, The development staff can be efficiently managed in the progress of work, and the development staff can easily identify a file whose safety is guaranteed.
[0061]
In addition, since the work instructions and reports can be managed in correspondence with the products, the manager and the development staff each support efficient management of the execution status of the work instructions and support the effective use of resources. Can do.
[0062]
【The invention's effect】
As described above, according to the present invention, by comparing all the retrieval destinations with the repositories, it is possible to collectively grasp the state of the product in the work area of each developer.
[0063]
Also, the work status of each developer in charge for the product is stored in a centrally managed table, and the product status information stored in the repository is used by using the stored work status information and the product version information stored in the repository. It is possible to realize program development management in which product management for managing versions of the software and work status management for managing the status of work performed on the products are integrated.
[0064]
In addition, the management instructions from the administrator to each developer are managed at the same time by the administrator and the developer, and the administrator determines the number of remaining work instructions and the status of the person who has the work instructions based on the presence or absence of work instructions. It is possible to grasp this, and it is possible to effectively perform resource allocation.
[Brief description of the drawings]
FIG. 1 is a system configuration diagram showing an embodiment of a program development management support system to which the present invention is applied.
FIG. 2 is a flowchart showing processing of a product management unit.
FIG. 3 is a configuration diagram of a product take-out destination information table.
FIG. 4 is a configuration diagram of a state database table.
FIG. 5 is a diagram illustrating a specific example of a work environment.
6 is an explanatory diagram showing the meaning of status symbols used in the embodiment of FIG. 1;
FIG. 7 is a diagram showing an example of a display screen of product distribution status;
FIG. 8 is a diagram illustrating a detailed screen example of analysis contents of product distribution status;
FIG. 9 is a diagram showing a detailed screen example of product distribution status;
FIG. 10 is a flowchart showing a process of a work status management unit and a work flow of a developer.
FIG. 11 is a diagram illustrating a configuration example of a work status management table.
FIG. 12 is an explanatory diagram illustrating an example of a work status code.
FIG. 13 is a flowchart showing details of a work status management table update process;
FIG. 14 is a diagram illustrating an example of a work status display screen.
FIG. 15 is a flowchart illustrating a process of a work instruction management unit and a work flow of a manager and a developer.
FIG. 16 is a diagram illustrating an example of a work instruction status display screen.
FIG. 17 is a diagram illustrating an example of a work instruction detail screen.
FIG. 18 is a diagram illustrating an example of entering a log on a work instruction status display screen.
FIG. 19 is a diagram illustrating an example of a work instruction list screen.
[Explanation of symbols]
DESCRIPTION OF SYMBOLS 101,107 ... Server, 102-105 ... Client computer, 106 ... Network, 108 ... Memory, 109 ... Program development management apparatus, 110 ... Repository, 111 ... History management information, 112 ... Work condition management information, 113 ... Product management 114, work status management unit, 115 ... work instruction management unit, 301 ... product take-out destination information table, 401 ... status database table, 701 ... product distribution status display screen, 1601 ... work command status display screen.

Claims (3)

In a program development management support device that supports management when developing programs using products such as source code and documents that can be shared by multiple program developers,
Product storage means for storing the product in a directory structure; work storage means for each person in charge for storing the product taken out from the product storage means by a client computer used by each program development person in charge; The directory of the product taken out from the product storage means by the program development person, the state table for storing the state of the product at the take-out destination and the take-out destination in the product unit, and when instructed by the administrator or at a predetermined time Collecting the work status of the product taken out in the work storage means for each person in charge at intervals and registering it in the status table, and specified by all products or managers in the product storage means Product tube for processing the display location of the product and the working state on the display device screen in a directory structure And means,
The product management means analyzes the working state of the product in the directory belonging to the directory under the selection operation of any directory among the product directories displayed on the display device screen, A program development management support apparatus for performing a process of displaying information that is not up-to-date in an identifiable manner . 2. The program development management according to claim 1, wherein the product management means performs processing for displaying a current state in a list format in response to a product selection operation and a detailed information display instruction operation that are not in the latest state. Support device. A work status management table that stores the status of the product stored in the work storage means for each program developer and the current work status of the program developer for the product in units of products; In response to the work status notification from the client computer used by each program developer, registering the status and work status of the corresponding product in the work status management table, and the inquiry request from each program developer, 3. The work status management means for performing a process of returning and displaying the requested product status on a client computer used by a program developer in charge of the request source. Program development management support device.

Images