JP2006134181A - Project management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a project management system capable of achieving the promptness of approval work for fruit data and reducing a burden on a project manager or the like and of monitoring in real time an approval state by a customer for the fruit data by a high-level manager or the like. <P>SOLUTION: The project management system is provided with a shared server 100 accessible through a network 140 such as the Internet from respective client terminals 110, 120, 130 for the project manager, the customer, and the high-level manager. The shared server 100 stores the fruit data presented to the customer from the project manager in a given shared folder 101 to provide an access restriction by authentication processing by an authentication means 102. A registration means 103 and an approval information writing means 105 write presentation information or approval identification information on the fruit data stored on the shared folder and register presentation fruit information on a project management information database 107. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a management system for a software development project (hereinafter, simply referred to as “project”), and in particular, a product, such as a design document, a contract, and a source code, to be submitted to a customer by a project manager. The present invention relates to a configuration that enables unified management of approval information.

In general, in a software development project, interaction with a customer is an important factor along with development work by a developer and progress management by a project manager.
As a system for supporting exchanges with customers in such software development projects, conventionally, progress management information is centrally managed on a Web server, and from a client terminal on the customer side via a network such as the Internet. The structure which enabled browsing is publicly known (for example, refer to patent documents 1).
JP 2003-308208 A

However, the system described in Patent Literature 1 allows only the progress management information to be browsed by the customer, and does not allow browsing of other information, particularly product data of development work. .
Here, in the software development project, the customer needs to approve the deliverable. Conventionally, the deliverable data etc. is submitted to the customer by electronic or paper media by the project manager, and by the customer's seal etc. It was approved. In this case, since the product data cannot be browsed even in the system described in Patent Document 1, it is necessary to submit the product data and the like by the same method as before.
Therefore, the work for exchanging deliverable data with the customer is time-consuming, and it is possible to shorten the delivery time in the recent software development project and to improve the work efficiency corresponding to the cost reduction. There wasn't.
In this case, it may be possible to simplify the work in the approval process by sending and receiving deliverable data using an e-mail system, but there are cases where the files that can be sent and received in the e-mail system are limited, It was not possible to use all product data.
In addition, when product data is approved by a conventional method including an e-mail system, a person other than the project manager (especially a senior manager who manages all projects) can make progress on the customer's approval process. I could not grasp the situation directly. Accordingly, there is a problem that unless the progress information is registered by the project manager, it is not possible to manage the submission status, approval status, etc. regarding the product approval process.

  The present invention is to solve the above-mentioned problems, and by sharing the product data in a security-ensured environment, the work for approving the product data is accelerated and the burden on the project manager is reduced. An object of the present invention is to provide a project management system that enables senior managers to monitor the approval status of customers for deliverable data in real time.

In order to solve the above-described problems, the present invention stores product data of the software development project in a shared server that is connected to the software development project manager client and customer client via a network. A project management system comprising: a shared folder for managing a project management information storing means for storing management information relating to each project; and responding to an authentication request from the client for project manager or the client for customer With respect to permission to access the shared folder, authentication processing means for performing authentication processing based on preset authentication information, and the deliverable data by the client for clients permitted to access the shared folder by the authentication processing Accepting an input of authorization information against writes the authorization identification information to the product data, characterized by comprising a authorization information writing means for registering authorization information to the project management information storage means.
In addition, the project management system detects a storage of the deliverable data in the shared folder by the project manager client permitted to access, and sends a notification mail to the customer client. It is further provided with the feature.
Further, the notifying means has means for transmitting a notice mail to the manager client terminal when approval information is registered in the project management information storing means by the approval information writing means. And
The project management system further includes a totalization processing unit that totals the product approval information stored in the project management information storage unit, and generates submission product approval progress information totaled for each project. And

With the above configuration, according to the present invention, it is possible to reduce and speed up the burden of the product approval work by the customer by sharing the product data with the customer on the shared server whose access is restricted by the authentication unit. Become.
In addition, by accepting the input of approval information from the client terminal for customers and registering it in the project management information storage means, it is possible for senior managers other than the project manager to grasp the progress in the approval process in real time. Become.
In addition, since the approval identification information is written on the product data, the approval status can be easily grasped by checking the product data itself.
In addition, when the deliverable data is stored on the shared server, the client client is notified, and the approval information registration is notified to the project manager client. It becomes possible.
In addition, since the means for counting the approval information for the product data is provided, it is possible to manage the progress information of the software development project including the approval status regarding the product in real time.

Hereinafter, a project management system according to an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram showing a schematic configuration of a project management system according to an embodiment of the present invention.
The project management system according to the present embodiment can be accessed via the network 140 such as the Internet from the client terminals 110, 120, and 130 for project managers (hereinafter referred to as “PM”), customers, and senior managers. A shared server 100 is provided. In this case, each client terminal 110, 120, 130 may be controlled to connect to the Internet by an in-house proxy server.
The shared server 100 stores product data submitted from the project manager to the customer in a predetermined shared folder 101, and is installed in an extranet in which security is ensured. Here, the secured environment refers to an environment that can be accessed only by PM, customers, senior managers, and related programs. For example, access restriction can be set by authentication processing based on ID and password. In the access restriction setting in this case, for example, the project manager client terminal 110 is permitted to read, write, and execute the deliverable data of the project in charge, and the customer client terminal 120 accepts the deliverable to be approved. Only reading data is allowed.
Here, the deliverables include design documents, means, contracts, specification changes, minutes, etc. The design document refers to, for example, a basic design document that describes the basic architecture of the system, an external specification document that defines screen specifications, a database table structure, and the like. The specification change document is a document exchanged between the PM and the customer, and is for mutually confirming the specification change requested by the customer or the specification change proposed by the PM side. The minutes are used for confirming whether there is no omission in the mutual understanding of the contents of the meetings and meetings based on the minutes of meetings and meetings held between the PM and the customer.
The shared server 100 includes, in addition to the shared folder 101, each processing means such as an authentication means 102, a registration means 103, a notification means 104, an approval information writing means 105, a counting means 106, a project management information database 107 as an information storage means, It has.
The authentication unit 102 performs authentication processing for access requests from the client terminals 110, 120, and 130.
In response to a registration request from each of the client terminals 110, 120, and 130, the registration unit 103 displays a project information registration screen, a submitted product information registration screen, and an approval information registration screen, and the input information is displayed in the project management information database 107. To store. In addition, the submission information is written in the product data stored in the shared folder and registered in the project management information database 107.
The notification unit 104 transmits a notification mail to each of the client terminals 110 and 120 when product data is stored in the shared folder 101 or approval information is registered.
The approval information writing means 105 writes the approval identification information in the product data and registers the approval information in the project management information database 107 in response to the registration of the approval information by the client terminal for customer 120.
The aggregation means 106 aggregates registration information in the project management information database 107 and displays a project status list screen on the senior manager client terminal 130.

FIG. 2 is a diagram illustrating an access authentication processing procedure performed by the authentication unit 102 in the shared server 100.
The authentication unit 102 in the shared server 100 receives an access request from each client terminal (step 201), and refers to an authentication information table included in the project management information database 106 for an ID and a password included in the access request. (Step 202). In this case, in the authentication information table, the access authority is registered in advance together with the user ID and password, and when the ID and password acquired from each client terminal match those registered in the authentication information table. The access to the shared folder is permitted based on the access authority registered in advance as authentication OK. On the other hand, if the user ID and password are not registered in the authentication information table, an inaccessible screen is displayed on each client terminal.
Through the above processing, the shared server 100 performs access to the shared folder, registration of information in the project management information database, and the like in response to a request from the client terminals 110, 120, and 130 that have been authenticated (step 203). .

Hereinafter, a specific example of processing performed by the project management system according to the present embodiment will be described.
First, registration processing of project information and submitted product information related to product data stored in the shared folder 101 of the shared server 100 in advance is performed.
On the project information registration screen, the project name, project manager name, customer name, project start date, end date, and other profile information, the number of bugs that occurred in the project, the number of bugs resolved, etc. Accepts input such as quality information, cost information such as target cost, actual cost, project system, scale of deliverables created in the project, current issues, progress of each process (progress rate, number of days delayed, etc.) . Project information is registered by the project manager whenever the profile changes, and other information is registered periodically, such as weekly.
On the submitted deliverable information registration screen, input the name of the deliverable to be submitted to the customer, the expected submission date of the deliverable, the expected approval date of the deliverable by the customer, the number of deliverables (number of designs, number of rows for means, etc.) Accept.
In each registration screen, the user name acquired by the authentication unit 102 based on the user ID during the authentication process is displayed as a processor.

FIG. 3 is a diagram showing a profile information registration screen as one of the project information registration screens.
The profile information registration screen 300 includes a project number 301 for uniquely identifying each project, a project name 302, a customer name 303, a project information registration date 304, a project start date 305, and an end date 306. Product field 307, inspection category 308, business category 309, work place 310, project summary 311, target business field 312, scope of responsibility 313, development language 314, scale (Ks) 315, summary Each input item includes a design department 316, a project manager name 317, a responsible SE department 318, and a responsible design department 319.
The registration number 102 is given to the project number 301 when registering new project information. The inspection section 308 indicates what inspection is performed on the project. The business category 309 is a business category targeted by the project and includes business software development and basic software development. As the work place 310, either in-house or a customer is input. The target business field 312 is a business form to which a system created by a project belongs, and corresponds to C / S (client / server), Web application, and the like. The assigned range 313 indicates which range the project is responsible for in the entire system construction. The scale 315 indicates the scale of the means of the system created in the project, and a planned value is input at the stage of the process where no means is created. In the step of creating the means, the actual value is input.

FIG. 4 is a diagram showing a project quality information registration screen as one of the project information registration screens.
The project quality information registration screen 400 is for registering information relating to the quality, cost, system, scale, and pending matters of the project. The project number 401, report date 402, quality management information 410, cost management information 420, system Each input item includes management information 430, scale management information 440, and pending matter management information 450.
Information on quality, cost, and concerns is collected regularly, such as weekly, and is managed in time series based on information on the reporting date. It should be noted that the system and the scale are normally managed only when there is a change in the data, but in the present invention, for the sake of convenience, the system and the scale are managed in the same manner as the quality, cost, and concerns.
The quality management information 410 includes input items for the number of bugs to be extracted 411 and the number of unresolved cases 412 among the extracted bugs.
The cost management information 420 includes input items of a target cost 421, an estimated cost 422, an actual cost 423 at the present time, and an estimated cost 424 assumed from the remaining period.
The system management information 430 includes input items for the head office employee number 431 and the subcontractor employee number 432.
The scale management information 440 includes input items for a newly developed portion 441 and a modified portion 442 in the means creation amount.
The pending matter management information 450 includes input items for the total number of pending matters 451 and the number of outstanding issues 452.

FIG. 5 is a diagram showing a progress management information registration screen as one of the project information registration screens.
As with quality, process progress should be managed on a regular basis, such as weekly. In the progress management information registration screen 500 shown in this example, input items are set in time series for each of the multiple processes in the software development project. ing.
The progress management information registration screen 500 is displayed for each project identified by the project number, and an information registration date 501 is shown as a report date.
On the progress management information registration screen 500, for each process, the process name 510, the scheduled start date 511, the scheduled start date 512, the scheduled finish date 513, the scheduled finish date 514, the planned deliverable amount value 515, the actual deliverable amount record. Each input item includes a value 516, a progress rate 517, and a delay days 518.

FIG. 6 is a diagram illustrating an example of a submission product information registration screen displayed by the registration unit 103 of the shared server 100.
The submitted product information registration screen 600 is displayed for each project identified by the project number.
The submitted product information input items include data items of a planned storage location 601 of the product file, a submitter 602, a scheduled submission date 603, a scheduled customer approval date 604, and a planned deliverable amount value 605. The planned storage location 601 indicates a location in the shared folder 101 with a full path. The submitter indicates a person who has stored the deliverable in the shared folder 101 of the shared server 100. The scheduled submission date 603 indicates a scheduled date to be stored in the shared folder 101 of the shared server 100. The customer approval scheduled date 604 is determined in advance between the customer and the project manager as a scheduled date for the customer to approve the deliverable. The planned deliverable value 605 indicates how much the deliverable is to be created, and the unit is, for example, the number of sheets in the case of a design document.

In each of the above registration screens, the registration unit 103 registers each piece of project information in the project management information database 107 based on the input information.
When the deliverable is stored in a predetermined storage location in the shared folder 101 via the project manager terminal 110, the registration unit 103 describes the submission date and the submitter name in the stored deliverable. The result submission date and the result deliverable amount are registered as the deliverable product information in the project management information database 107.
When the submitted product information is registered in the project management information database 107, the notification unit 104 transmits an e-mail indicating the product name, the project name, and the like to the address of the client terminal 120 for customer set in advance.

Upon receiving the e-mail, the client terminal for customer 120 accesses the shared server 100 according to the operation of the customer, performs the authentication process, displays the approval information registration screen, and displays the selected deliverable file. .
FIG. 7 is a diagram illustrating an example of an approval information registration screen displayed on the client terminal for customer 120.
The approval information registration screen 700 includes a display of a product file name (full path) 701, a submitter 702, a submission date 703, a planned product amount 704, and a result product amount 705, an approval column 706, a comment column 707, and an approver column. 708, and each input item of the approval date column 709.
When the product file is confirmed by the customer, input is made in the approval field 706, the comment field 707, the approver field 708, and the approval date field 709, and the registration button 710 is pressed, the approval information writing unit 105 outputs the product data. Describes the approval date and the approver as approval identification information, and registers the approval information in the project management information database 107.
When the approval information is registered in the project management information database 107, the notification means 104 displays an approval registration notification mail displaying the project number, product file name, etc. at the address of the client terminal 110 for the project manager set in advance. Send.

FIG. 8 is a flowchart showing an approval information description processing procedure by the approval information writing means 105.
When the registration button 710 is pressed on the approval information registration screen 700 (step 801), the approval information writing unit 105 acquires the input approval information (step 802) and creates a file based on the product file name (full path). Is determined (step 803).
When the file type is document data such as a design document, contract, specification change document, minutes, etc., approval identification information (approval date, approver) is added to a predetermined description part of the deliverable data in the shared folder 101. Describe (step 804).
On the other hand, when the file type is a program (module), information of approval identification information (approval date, approver) is described in the header part of the product data source in the shared folder 101 (step 805).

Hereinafter, specific examples of description of approval identification information for each product data will be described with reference to FIGS.
9 shows an example of a design document as one of the deliverables, FIG. 10 shows an example of a contract, FIG. 11 shows an example of a specification change document, and FIG. 12 shows an example of a minutes. FIG. 13 shows an example of the module source code.
As shown in FIGS. 9 to 12, in the case of document data such as a design document, a contract document, a specification change document, and minutes, in addition to a text part 901, 1001, 1101, 1201, a submission date description part 911, 1011, 1111, 1211, submitter name description units 912, 1012, 1112, 1212, approval date description units 913, 1013, 1113, 1213, and approver name description units 914, 1014, 1114, 1214.
The submission date description units 911, 1011, 1111, and 1211 and the submitter name description units 912, 1012, 1112, and 1212 are described by the registration means 103 when the deliverable is stored in the shared folder 101 by the project manager. .
When the approval information is registered by the customer, the approval information writing unit 104 describes the approval date description part 913, 1013, 1113, 1213 and the approver name description part 914, 1014, 1114, 1214.
On the other hand, as shown in FIG. 13, the module has a header part 1310 and a body part 1320. The header part 1310 includes a module name, a submission date description part 1311 and a submitter name description part 1312 and an approval date description. A section 1313 and an approver name description section 1314.
In each of the description units 1311 to 1314, the registration unit 103 or the approval information writing unit 105 describes predetermined information as described above.

FIG. 14 is a diagram showing an example of the data structure of the submitted product information table constituting the project management information database 107.
The submission product information table 1400 stores information registered in the submission product information registration screen 600 and the approval information registration screen 700. The project number 1401, the product name 1402, the submitter 1403, and the scheduled submission date 1404 are stored. , Actual submission date 1405, scheduled product amount 1406, actual product amount 1407, approval 1408, comment 1409, approver 1410, approval information registration date 1411, scheduled approval date 1412, and actual approval date 1413.
In the submitted product information table 1400, the contents of the approval 1408 and the comment 1409 are managed in chronological order for each registration date 1411, and the presence or absence of approval for the product data with the same file name and the content of the comment are all recorded.

The tabulation means 106 of the shared server 100 displays a project status list screen based on the tabulation result of each registered information in the project management information database 107 in response to a request from the senior manager client terminal 130.
FIG. 15 is a flowchart showing a processing procedure in a case where periodic aggregation is set in advance as processing performed by the aggregation means 106.
The totaling means 106 starts at the set time (step 1501), reads the project management information database 107, collects project information and submitted product information based on the project number, totals (step 1502), and lists the total results. In summary, the project status list display screen is displayed on the Web screen in response to a request from the senior manager client terminal 130 (step 1503).

FIG. 16 is a diagram showing a screen for displaying registered profile information and quality information as one of the project status list display screens.
In the project status list display screen shown in FIG. 16, information such as the project number, project name, and customer name is displayed corresponding to the input items on the profile information registration screen and the quality information registration screen shown in FIGS. The
FIG. 17 is a diagram showing a screen for displaying process progress information and submitted product approval information as one of the project status list display screens.
The project status list display screen shown in FIG. 17 includes a process progress information display section corresponding to the input items on the process progress information registration screen shown in FIG. Part 1710.
When the project number 1711 is specified in the submitted product progress information display unit 1710, the totaling unit 106 of the shared server 100 displays a list of information registered in the submitted product information table 1400 shown in FIG.

As described above, in the project management system according to the present embodiment, by sharing the deliverable data with the customer on the shared server whose access is restricted by the authentication unit, the burden on the work of approving the deliverable by the customer can be reduced. It is possible to speed up.
In addition, by accepting the input of approval information from the client terminal for customers and registering it in the project management information storage means, it is possible for senior managers other than the project manager to grasp the progress in the approval process in real time. Become.
In addition, since the approval identification information is written on the product data, the approval status can be easily grasped by checking the product data itself.
In addition, when the deliverable data is stored on the shared server, the client client is notified, and the approval information registration is notified to the project manager client. It becomes possible to manage the approval progress in real time.
In addition, since the means for counting the approval information for the product data is provided, it is possible to manage the progress information of the software development project including the approval status regarding the product in real time.
Since approval information including customer comments is managed in chronological order, it is possible to grasp the specific approval progress status by checking the approval status and the content of the comments.

Note that the present invention is not limited to the above-described embodiment, and the configuration of the server device, each database, and the table configuration may be changed as long as similar processing is possible. Therefore, each processing means and the like may be provided in a server device different from the shared server that stores the product data.
Further, although the authentication process related to access restriction is based on a combination of ID and password, the authentication process may be performed using other information.
In addition, the project manager stores the product data in the shared folder. However, the present invention is not limited to this, and means for copying and storing the product data from the storage destination of the product data designated in advance is stored. It is good also as providing.

It is a block diagram which shows schematic structure of the project management system which concerns on one embodiment of this invention. It is a flowchart which shows the outline | summary of the access permission determination process by an authentication means. It is a figure which shows an example of a project information registration screen. It is a figure which shows an example of a project information registration screen. It is a figure which shows an example of a project information registration screen. It is a figure which shows an example of a submission product information registration screen. It is a figure which shows an example of an approval information registration screen. It is a flowchart which shows the approval information writing process procedure by the approval information writing means. It is a figure which shows an example of the deliverable data in which approval identification information was written. It is a figure which shows an example of the deliverable data in which approval identification information was written. It is a figure which shows an example of the deliverable data in which approval identification information was written. It is a figure which shows an example of the deliverable data in which approval identification information was written. It is a figure which shows an example of the deliverable data in which approval identification information was written. It is a figure which shows an example of the data structure of a submission product information table. It is a flowchart which shows the project information totaling process procedure by a totaling means. It is a figure which shows an example of a project status list screen. It is a figure which shows an example of a project status list screen.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Shared server, 101 Shared folder, 102 Authentication means, 103 Registration means, 104 Notification means, 105 Approval information writing means, 106 Aggregation means, 107 Project management information database, 110 Client terminal for project manager, 120 Client terminal for customer , 130 Client terminal for senior managers.

Claims (4)

A project management system comprising a shared folder for storing deliverable data of the software development project in a shared server that is connected via a network from a client for a software development project administrator and a client for a customer. And
The project management system includes:
Project management information storage means for storing management information related to each project;
In response to an authentication request from the client for the project manager or the client for the client, an authentication processing means for performing an authentication process based on authentication information set in advance with respect to permission to access the shared folder;
Accepting input of approval information for the deliverable data by the client for clients permitted to access the shared folder by the authentication processing, writing approval identification information in the deliverable data, and approving to the project management information storage means A project management system comprising: an approval information writing means for registering information.   The project management system further comprises notification means for detecting storage of deliverable data in the shared folder by a project manager client permitted to access and transmitting a notification mail to the client client. The project management system according to claim 1.   The notification means includes means for transmitting a notification mail to the manager client terminal when approval information is registered in the project management information storage means by the approval information writing means. The project management system according to claim 2. The project management system further includes a totalization processing unit that totals the product approval information stored in the project management information storage unit, and generates submitted product approval progress information totaled for each project. The project management system according to claim 1.

Images