JP2000047865A - Arrow diagram generating device for project management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To correct an arrow diagram in accordance with the problem arising in development and the progress state of operation by newly generating an arrow diagram by providing a model arrow diagram, and relating the concern arising in a developing process to the arrow diagram of the process thereby giving importance to the concern. SOLUTION: An arrow diagram managing means 16 generates the arrow diagram of a new development project according to the recorded template arrow diagram and information of projects recorded in a project information file 11 and records it in an arrow diagram storage file 12. If a problem arises halfway in project developing operation, an operator inputs information on the concern through a terminal device 110. The concern information is weighted according to its effect on the operation and recorded in a problem item file 13. The arrow diagram managing means 16 corrects the arrow diagram according to the importance of the concern.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to a project management system used for planning software development, for example.

[0002]

2. Description of the Related Art Japanese Patent Laid-Open No. 2-196368 discloses a conventional technique relating to the creation of an arrow diagram.

In the above-mentioned prior art, an arrow diagram can be created by recording in advance information necessary for making a work plan, such as the work period and personnel of a project developed in the past.

[0004]

In the above prior art,
An arrow diagram can be created by inputting information necessary for creating an arrow diagram in advance. During development, it is often necessary to update the progress and modify the arrow diagram. However, if a pending issue occurs during development and the progress is delayed, the project leader sorts out the pending issues and their countermeasures, considers the status of the pending countermeasures and the progress of the work, and conducts each process as necessary. The correction of the arrow diagram must be done manually. Usually, since the arrow diagram and the pending issues are often managed separately, this method imposes a heavy load on the project leader and causes a reduction in work efficiency of the entire project.

[0005] It is an object of the present invention to provide an arrow diagram creating apparatus capable of correcting an arrow diagram according to a pending state or a work progress that occurs during development in a project management system.

[0006]

In order to achieve the above object, the arrow diagram creating apparatus of the project management system of the present invention creates a new arrow diagram by having a template arrow diagram.
In addition, an issue generated in the development process is associated with an arrow diagram of the process in which the issue occurred, and the issue is given importance. This makes it possible to modify the arrow diagram.

[0007]

Embodiments of the present invention will be described below in detail with reference to the drawings. The present invention can be used in various fields such as process control using arrow diagrams,
Here, a method of creating and correcting an arrow diagram in software development will be described as an example.

FIG. 1 shows a system configuration for realizing an arrow diagram creating method according to the present invention. Reference numeral 11 denotes a project information file, which records information such as the number of programs, screens, forms, and work staff of a project developed in the past, and the development man-hour of the project, that is, the work time required to achieve the work. ing. This is called template project information.
The project information file 11 can record information such as the number of programs, the number of screens, the number of forms, and the number of workers of a newly developed project.

Reference numeral 12 denotes an arrow diagram storage file which records an arrow diagram of the number of development steps of a previously developed project recorded in the project information file 11. This is called a model arrow diagram. The arrow diagram storage file 12 can also record a newly created arrow diagram.

Reference numeral 13 denotes an issue file, which can record information on an issue that occurred during project development.
Reference numeral 14 denotes a product information file, which can record information on the product created in the project development. Specifically, it is composed of the progress status of documents, source programs, and the like. Reference numeral 15 denotes a project information management unit, which has a function of inputting information such as the number of programs, the number of screens, and the number of forms of a development project and recording the information in the project information file 11.

Reference numeral 16 denotes an arrow diagram management means for creating an arrow diagram for a new development project from the template arrow diagram of the project information file 11 and the arrow diagram storage file 12, and recording the created arrow diagram in the arrow diagram storage file 12.
It has a function of correcting the arrow diagram according to the progress status and pending status of the project under development recorded in the arrow diagram storage file 12 and recording the corrected arrow diagram in the arrow diagram storage file 12. 17
Is a concern management means, and has a function of inputting information such as a concern, a cause, a countermeasure method, and a degree of importance indicating an influence on a project, and recording the information in the concern file 13.

Reference numeral 18 denotes a deliverable management means, which has a function of recording the progress of the deliverable during development of the project. Reference numeral 19 denotes progress information management means, which has a function of displaying the progress of the arrow diagram from the progress of the product. A terminal device 110 is used for inputting, editing, and outputting information of a project information file and an issue file.
Specifically, input devices such as a keyboard and a mouse, and a CR
It is composed of an output device such as a T display and a printer.

FIGS. 5, 6, 7 and 8 illustrate the data structure of each file by way of example. FIG. 5 is an example of the contents of the project information file 11. 51 is a work name. 52 is the number of screens. 53 is the number of forms. 54 is the number of programs. 55 is a scale. Reference numeral 56 denotes a worker. 57 is a man-hour. In the project information file, template project information is recorded. This is information such as the number of programs, the scale, and the standard man-hour of the projects developed in the past. When a new arrow diagram is created, project information of a new development project can be recorded.

FIG. 6 is an image diagram of an arrow diagram. 61 is a time axis. Reference numeral 62 denotes a work period of the work X. 63 is a work period of the work Y. 64
Is the work period of work Z.

FIG. 7 shows an example of the contents of a pending item file. 71 is the name of the generation step. 72 is a problem. Reference numeral 73 denotes a person who is to take measures. 74 is scheduled to take countermeasures. 75 is a countermeasure deadline. 76 is a countermeasure person. 77 is a countermeasure method. Numeral 78 is a measure date.
79 is the importance.

FIG. 8 shows an example of the contents of the product information file. 81 is a work name. 82 is the total number of documents. Reference numeral 83 denotes the planned number of documents to be created. Reference numeral 84 denotes the number of created documents. 85
Is the degree of progress.

FIG. 2 is a flowchart for creating and correcting an arrow diagram. In decision block 21, it is determined whether a new arrow diagram is to be created or an already created arrow diagram is to be modified. In a processing block 22, an arrow diagram management unit is performed based on the template project information recorded in the project information file 11, the project information for a new development project, and the template arrow diagram information recorded in the arrow diagram storage file 12. 16 creates an arrow diagram of the new development project and records it in the arrow diagram storage file 12.

At decision block 23, it is determined whether progress information is to be obtained. In the processing block 24, the progress information management means 19 acquires the progress status. Decision block 2
In 5, it is determined whether or not the pending information is acquired. In the processing block 26, the concern management means 17 acquires the concern information. At decision block 27, it is determined whether to edit the created or modified arrow diagram. In processing block 28, the arrow diagram is edited.

FIG. 3 is a detailed flowchart of the progress status acquisition 24 in FIG. In processing block 31,
The planned creation amount of the product is acquired from the project information file 11. In processing block 32, the progress of the product is obtained from the product information file 14. In the processing block 33, the progress is calculated from the planned production amount of the product and the actual production amount. In the processing block 34, the progress is displayed on the arrow diagram based on the obtained progress and recorded in the arrow diagram storage file 12. At decision block 35, it is determined whether the process is delayed. In processing block 36, the arrow diagram management means 16 displays a message in case of a process delay.

FIG. 4 is a detailed flowchart of the pending information acquisition 26 in FIG. In processing block 41,
The concern management means 17 acquires the countermeasure status of the concern from the concern file 13. In a decision block 42, the concern management means 17 determines which rank the importance of the concern is. In processing block 43, a warning message is displayed when the priority of the concern is high. At decision block 44, it is determined whether to modify the arrow diagram. In a processing block 45, the arrow diagram management means 16 corrects the arrow diagram and records it in the arrow diagram storage file 12.

Next, the details of the processing will be described with reference to FIG. When creating an arrow diagram for a new development project, information necessary for creating an arrow diagram such as the number of programs, the number of screens, the number of forms, the scale, the number of workers, etc. of the project is input from the terminal device 110 from the terminal device 110, and project information management is performed. Means 15 records in project information file 11. The arrow diagram management means 16 records a project arrow diagram created based on the project information of the project developed in the past and the arrow diagram. The arrow diagram management means 16 creates an arrow diagram of the new development project based on the template arrow diagram and the project information recorded in the project information file 11, and records it in the arrow diagram storage file 12.

FIG. 5 shows an example of data of the project information file. In the project information file, data such as the number of screens, the number of forms, the number of programs, the scale, and the number of workers are recorded, and from these information, the estimated man-hours of the new development project can be calculated.

FIG. 6 shows a template arrow diagram, which is recorded in the arrow diagram storage file 12. Here, work A62, work B63, work C64
Has 10 man-hours respectively.

FIGS. 9 to 11 are arrow diagrams created from the project information file of FIG. 5 and the template arrow diagram of FIG.

Since the man-hour of the work A of the new project information file in the lower part of FIG. 5 is 1.5 times the man-hour of the work A of the template project information file in the upper part of FIG.
In the work A91 of the model arrow diagram,
A new arrow diagram operation 92 is created with 1.5 times the operation time.

Since the man-hour of the work B of the new project information file in the lower part of FIG. 5 is twice the man-hour of the work B of the template project information file in the upper part of FIG. 5, the work B101 of the template arrow diagram in FIG. From
The operation B102 of the new arrow diagram is created in a double operation period. Since the man-hour of the work C of the new project information file in the lower part of FIG. 5 is equal to the man-hour of the work C of the template project information file in the upper part of FIG. 5, the work C111 of the template arrow diagram in FIG.
The work C112 of the new arrow diagram is created in the same work period. FIG. 12 is a newly created arrow diagram.

The product in the software development work includes a document and a source program. Here, the document is handled. The created product is stored in the product information file 14. The worker starts the work of creating a product according to the arrow diagram, and stores the created document and the progress of the source program in the product information file 14. Progress information management means 19
Updates the progress from the progress information to the arrow diagram. FIG. 13 is an arrow diagram in which progress is updated from the information in the product information file in FIG.

If an issue occurs during the operation, the issue is input from the terminal device 110 and the
Records in the concerns file 13. The concern management means 17 manages information on the concern. FIG. 7 is an example of the items in the issue file 13, such as an issue, a measure plan, a measure date, and a degree of importance. When an issue occurs during the project development work, the worker inputs information on the issue from the terminal device 110. The input issue information is recorded in the issue file 13 by the issue management unit 17. Issues are weighted according to the impact they have on work.

The degree of influence of the work on the work is ranked, and if a work with a higher rank is input, the arrow diagram can be extended in accordance with the set ratio. In the example of FIG. 7, there are three levels of A, B, and C in the order of higher importance rank. The countermeasure status of the pending item is determined by acquiring the number of countermeasures and the total number of pending items from the pending file. The importance of the issues is ranked in descending order of the impact on the work.

FIG. 7 shows an example of a pending matter file, in which the importance of the pending matter is recorded in addition to the problem, the schedule of the measures, and the like.
In the example of FIG. 7, it is assumed that there are three levels of A, B, and C in descending order of importance, and the importance is set to 20%, 10%, and 0%, respectively. The level of importance and the rate of modification can be modified. Here, the importance of work A is A, and the importance of work B is B. The progress information management means 19 draws a progress line of each process. The arrow diagram management means displays a message for a process whose progress is delayed.

FIG. 14 is an arrow diagram displaying an error message. The pending message of the task B in the pending file in FIG. 7 is displayed in the error message 141. If the operator determines that the arrow diagram needs to be corrected, the arrow diagram management means corrects the arrow diagram according to the importance of the pending item. The correction is made when the importance is A and B, and the correction ratio is 20
% And 10%.

FIG. 15 and FIG. 16 are arrow diagrams in which a correction has been made after issuing a warning message of a process delay due to the effect of pending issues. Step 151 of operation B in FIG.
%, And accordingly, step 1 of operation C in FIG.
The start of 61 has been delayed.

[0033]

According to the present invention, an arrow diagram can be generated from a template by inputting project information, so that the work load for creating an arrow diagram in a project plan can be reduced.

The information on the arrow diagram, pending issues, and deliverables of the project can be centrally managed, and the acquisition of the progress status and the correction of the arrow diagram based on the importance of the pending issues can be automated.
It becomes easy to grasp the degree of delay, and the workload in managing the progress of the project can be reduced.

By leaving information such as project information, arrow diagrams, progress information, concerns, and countermeasures used in past projects, the information can be referred to when planning other projects. Efficiency can be improved.

[Brief description of the drawings]

FIG. 1 is a configuration diagram of an arrow diagram creating method showing an embodiment of the present invention.

FIG. 2 is a flowchart of a processing outline.

FIG. 3 is a flowchart of obtaining progress information.

FIG. 4 is a flowchart of acquiring pending information.

FIG. 5 is a diagram showing an example of a project information file.

FIG. 6 is a diagram illustrating an example of an arrow diagram serving as a template.

FIG. 7 is a diagram illustrating an example of an issue file.

FIG. 8 is a diagram showing an example of a deliverable information file.

FIG. 9 is a diagram showing a first stage of a process of creating an arrow diagram generated from a template using an estimated scale.

FIG. 10 is a diagram showing a second step in the process of creating an arrow diagram generated from the template using the estimated scale.

FIG. 11 is a diagram showing a third step in the process of creating an arrow diagram generated from the template using the estimated scale.

FIG. 12 is a diagram showing a completed example of an arrow diagram generated from a template using an estimated scale.

FIG. 13 is a diagram showing an arrow diagram reflecting progress information.

FIG. 14 is a diagram showing an arrow diagram reflecting pending information.

FIG. 15 is a diagram showing a first stage of an arrow diagram correction process in which correction is performed after reflection of pending information.

FIG. 16 is a diagram showing a second stage of an arrow diagram correction process in which correction is performed after reflection of pending information.

[Explanation of symbols]

11: Project information file, 12: Arrow diagram storage file, 13: Issues file,
14: deliverable information file, 15: project report management means, 16: arrow diagram report management means, 17
... Issue management means, 18 ... Delivery management means, 19 ... Progress information management means, 110 ... Terminal device, 21 ... Arrow diagram creation determination block, 22 ... Arrow diagram creation block, 23 ... Progress information acquisition determination block, 24 ... Progress information acquisition block, 25: pending countermeasures status acquisition determination block, 26: pending countermeasures status acquisition block, 27: editing determination block, 28: editing block, 31: scheduled product creation quantity acquisition block, 32: acquisition of product creation quantity Block, 33: progress calculation block, 34: progress line display block,
35: process delay determination block, 36: warning message display block, 41: pending countermeasure status acquisition block, 42 ...
Importance judgment block, 43 ... warning message display block, 44 ... arrow diagram correction judgment block, 45 ... arrow diagram correction block.

Claims (2)

[Claims] A means for recording project information serving as a template for creating an arrow diagram; a means for inputting project information required for creating an arrow diagram; a means for recording project information input from the input means; Means for recording an arrow diagram as a model for diagram creation, means for creating an arrow diagram from project information serving as a template, input project information and an arrow diagram serving as a template, and means for recording the created arrow diagram An arrow diagram creation device for a project management system, comprising: 2. A means for displaying the progress of a product in the development process on an arrow diagram, a means for inputting information on a concern that has occurred in the development process, and a task and a message on the arrow diagram according to the progress of the work. An arrow diagram creating apparatus for a project management system, comprising: means for displaying, means for modifying an arrow diagram according to the importance of a concern, and means for recording the modified arrow diagram.