JPH06348720A - Production development control display device - Google Patents

Abstract

PURPOSE:To easily grasp the progress state of a software development project by displaying the progress state. CONSTITUTION:This device consists of an input part 31 for inputting scheduled update date quantity data, plan data, and actual result data information regarding the production developing process of software, a storage part 37 which stores them respectively, an editing part 38 which edits the data stored in the storage part 37, and a display part 313 which puts the respective edited data together and displays the composite data.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a production development management display device in a computer system for collecting and analyzing information for each production development process and managing it.

[0002]

2. Description of the Related Art Managing the progress of each production development process is an important factor for efficiently determining whether production development is proceeding. Conventionally, there is no display device made especially for progress management, and if you dare to display it,
Mainly, there were many charts such as the following Inazuma chart and Gantt chart.

A case where a display is made by using an outline chart will be described with reference to FIG. Here, the schedule of the process a is set as "October 1 to October 30", the schedule of the process b is set as "From October 1 to October 25", and the schedule of the process c is set. It is set as "from October 10th to November 10th".

The horizontal axis represents the date and time, the vertical axis represents the process, and the schedule of the process a is represented by a horizontally long rectangle such as schedule 10, the schedule of the process b is represented by a horizontally long rectangle such as schedule 11, and the schedule of the process c. The schedule is represented by a horizontally long rectangle like Schedule 12.

Here, the results as of October 25 are displayed, but the process a is as of October 25, and it is possible to give only the results up to October 15 out of the initially planned. To do.

Similarly, it is assumed that the process b has achieved the results up to October 20, and the process c has achieved the results up to October 30. Here, October 15 on schedule 10 of process a
The point of day and the point of October 20 on schedule 11 of process b,
A diagram showing the results as of October 25 by connecting the points on October 30 on schedule 12 of process c with a straight line (solid line 13) is the Inazuma chart.

This lightning chart was effective in knowing what percentage of one process was completed at a certain time. A case of displaying using a Gantt chart will be described with reference to FIG. Here, the schedule of process d is "1.
From 1st October to 30th October "and" 5th November to 1st
It will be set separately for two tasks, "until January 10th.""1
Schedule from October 10th to October 30th, schedule 2
0, "Schedule from November 5th to November 10th" is set with a stick like Schedule 21. Similarly, steps e and f
The schedule is set with a bar like schedule 22, schedule 23, and schedule 24.

The actual results for the schedule are displayed in a rectangular box indicated by a horizontally long diagonal line. Process d, “From October 1st to 10th
If it actually takes until October 30 for the schedule of "20th of a month", extend the rectangular box indicated by the horizontal diagonal line from the day when the work started to the point of October 30 (box 25 ). Similarly, the work record is shown by a rectangular box indicated by a horizontally long diagonal line like the box 26. As of November 10, when the progress was checked, the work of process d and process f was performed. The progress status at this time is represented by a symbol ("A" in the figure). The progress status is set in the alphabetic symbol, and the progress status is expressed using the symbol. For example, "A: work in progress, B:
Waiting for preparatory work ". In this way, the Gantt chart is a collection of plans, implementation statuses, and work statuses for a certain period of time.

[0009]

In the conventional display device as described above, in the case of the lightning chart, it is possible to see at a glance how much the entire process is completed and how many days are delayed. In the case of Gantt chart, the gap between the schedule and the performance can be seen at a glance because the schedule and the performance are parallel.

However, since these conventional devices are not created for progress management, when a project is divided into a plurality of subsystems for production development, the plurality of subsystems are collectively displayed as one project. However, there was a problem that it was not suitable for the current production development. Further, regarding the quantitative grasp of the progress, there is a problem that it is impossible to judge whether the progress of the work is advanced or delayed compared to the time of the last check, when regularly checking. Further, for example, in the Gantt chart shown in FIG. 2, regarding the box 25 of the step d, it is not easy to grasp at a glance whether or not the work is completed.

Therefore, the present invention has been made in consideration of the above-mentioned circumstances, and displays the progress status of the entire project by collecting the progress status of each production development process in which the project is divided into a plurality of subsystems. By doing so, it is possible to easily manage progress without burdening the manager and to show more accurate progress management by showing quantitative indicators that can easily judge the progress / delay of work. The purpose is to enable.

[0012]

According to the present invention, a project is divided into a plurality of subsystems, and data information relating to a production development process input for each subsystem is analyzed.
In the production / development management display device for displaying, the data on the production / development process is composed of scheduled update days data, plan data and actual data, and displays the plan process of each subsystem of the project based on the plan data. Display means, second display means for comparing and displaying the actual result data in correspondence with the planned process, and making the planned update days data correspond to the planned process, and adding the result data in a distinguishable manner for comparison. It is a production and development management display device comprising a third display means for displaying.

[0013]

According to the present invention, it is possible to grasp quantitatively and visually the information as to how much the work result is advanced or delayed with respect to the schedule. Furthermore, by summarizing the progress status of each of the divided subsystems and displaying the progress status of the entire project, it is possible to grasp the bottleneck of production development delay with higher accuracy. This makes it possible to easily manage production development without burdening the administrator.

[0014]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A production development management display device for displaying the progress status of a software development project according to an embodiment of the present invention will be described with reference to the drawings. FIG. 3 is an overall configuration diagram of a production development management display device according to an embodiment of the present invention.

When the input unit 31 receives a progress check request from the display request input unit 32, the process is transferred to the analysis execution unit 33. The analysis execution unit 33 analyzes the display request,
The planned update days data, the plan data, and the actual data of the target project are respectively input using the planned update days input means 34, the plan data input means 35, and the actual data input means 36, and accumulated in the storage unit 37. The data is collected from the magnetic disk and is passed to the scheduled update days editing means 39, the plan data editing means 310, and the actual data editing means 311 of the editing unit 38. Then, the data edited by each editing unit is collected by the display data synthesizing unit 312, and the progress status corresponding to the display request set by the display request input unit 32 is displayed on the display unit 313.

A production development management display device for displaying the progress status of a software development project, which is an embodiment of the present invention, will be specifically described below. In Figure 4,
The outline of the project is shown. Here, it is assumed that the software development project name is “X system”. The target system "X system" is divided into subsystem X-1 and subsystem X-2.
The schedule of this project consists of five processes: "Basic design process", "Function design process", "Test specification creation process", "Program creation process" and "Test process".
Person A will be in charge of "basic design" from April 1st to May 10th. The "functional design" for each subsystem is divided between the person in charge B and the person in charge C from 6th May to 6th.
Responsible during the 15th of the month, the person in charge of "test specification creation" is divided between the person in charge B and the person in charge of C, and is in charge of from May 20th to July 20th. Person in charge C will be divided and will be in charge from July 20th to August 15th.
The "test" is performed by the person in charge A from September 1 to September 30. In addition, the planned deliverables and deliverables for each process are fixed.

The user who is the production development manager uses the plan data input means 35 of the input unit 31 shown in FIG.
Enter the schedule information for this project described above. Figure 5
Is an example of data input using the scheduled update days input means 34 shown in FIG. Here, the developer in charge of the subsystem X-1 of the X system, on the progress check date 51, the process name 52 that is currently working, the amount of deliverables at the time of the check date in the process, and the current product amount. It shows an example of inputting the scheduled update days 53 of the process. The scheduled renewal number of days is to input the number of remaining days of the process reporting the progress status on a daily basis.

FIG. 6 shows an example in which the actual data input means 36 shown in FIG. 3 is used. Here, an example is shown in which the developer in charge of the subsystem X-1 of the X system inputs the progress check date 61, the target process name 62, and the deliverable amount 63 of the target process deliverable on the progress check date. There is.

As shown in FIGS. 5 and 6, it is assumed that the input data 31 of the present system is used to input the plan data, the scheduled update date data, and the actual data. Here, a process when a progress display request is issued will be described below. In addition,
Here, the system in charge of the person in charge B is defined as subsystem X.
-1, the system subsystem X-2 in charge of the person C
And

When the display request input means 32 of the present system accepts the progress display request, the process proceeds to the analysis executing section 33. In the execution analysis unit 33, the display request is analyzed, and the scheduled update days data, the plan data, and the actual data of the target project use the scheduled update days input means 34, the plan data input means 35, and the actual data input means 36. Is input and collected from the magnetic disk stored in the storage unit 37 composed of a magnetic disk or the like, and each of the above-mentioned data is passed to the scheduled update days editing means 39, the plan data editing means 310, and the display data editing means 311. Then, the data edited by each editing unit is combined by the display data combining unit 312, and the progress status is displayed on the display unit 313. FIG. 7 is a flowchart showing this procedure in more detail.

When the system is activated, the display request is accepted (menu screen) (STEP 71). Then, the editorial department reads the data accumulated so far (ST
EP72-74), and based on the result, the user selects the project whose progress is to be displayed via the input unit (STEP 75). When the selection is completed, the process moves to the display data synthesizing unit. If the selected project has multiple subsystems (persons in charge), calculate the start date and end date of the process for each subsystem. When the calculation of the start date and the end date is completed, the progress status is displayed. The display is performed by the following procedure. The planned process of the target project is displayed with a horizontal bar (STEP 77). The actual information before the check date is displayed in a horizontally long box with diagonal lines (S
TEP78). The number of scheduled update days input on the check day is displayed in a blank horizontal box (STEP 79). The scheduled renewal days are displayed next to the blank oblong box (STEP7
10). Display the date checked before with a vertical bar (ST
EP 711). The progress coefficient of this check date and the progress coefficient of the previous check date are displayed (STEP 712).

FIG. 8 shows a method of calculating the start date and end date of each process when the target process is divided into subsystems. This corresponds to STEP 76 in FIG. First, initialization is performed (STEP 81), and the number of subsystems of the target project is read (STEP 8).
2). Import information as many as the number of subsystems (STE
P83), check progress (STEP 8)
4). If there is a difference in the work process on the check day between the subsystems (STEP 85), the progress of the process that is the latest is set as the overall progress (STEP 86). If there is no difference, the progress of the process of the most delayed subsystem is set as the overall progress (STEP 87).

9 and 10 are diagrams showing a method of calculating the progress coefficient and a simulation example. A work schedule 91 of a certain process is set by a horizontal bar. The scheduled start date 92 for this process is October 1. The scheduled end date 93 is 1
It's 30th of October. At this time, the progress coefficient as of the progress check date 94 of October 15 is calculated. 10
The work record 95 as of the 15th day of the month is indicated by a horizontally elongated box. Then, the planned renewal day count data 96 indicating how many days the work process will be completed is shown by a horizontally long blank box. Here, the scheduled update days are 10
Is the day. The progress coefficient at this time is (actual work days + planned renewal days at the check date) /
Calculated by planned work days. In this embodiment, the progress coefficient 97 is
It becomes 0.83. This means that the process ends in 0.83 times the planned work days. There are various patterns in how performance is displayed for an appointment. Here, FIG. 9 shows a method of calculating the progress coefficient of 6 patterns from (a) to (f). FIG. 9A shows a case where the work starts as planned and the work ends earlier than planned. That is, on the progress check date 94, the work record 95 is 15 days, and the remaining work days 96 is 10 days. Therefore, the progress coefficient 97 is (15 + 10) /30=0.83. The same applies to the progress coefficient in FIGS. 9B to 9F.

FIG. 10 is a result of simulating the transition of the progress coefficient of a certain process. The work schedule for a certain process is from October 1st to November 1st. here,
When checked on October 15, the progress coefficient is 1, indicating that the work is progressing on schedule. Next time I checked on November 1,
The number of scheduled renewal days is 5, and the progress coefficient is 1.16. Furthermore, when checked as of November 15, the number of scheduled renewal days is also 5 here, and the progress coefficient has increased to 1.67. In this way, by evaluating the progress coefficient for each check date, it becomes possible to quantitatively judge the progress / delay of the work, and efficient progress management becomes possible.

FIG. 11 shows an example in which the actual progress is graphically displayed. The schedule of each process is indicated by a horizontal bar 111. Horizontal slanted box 112 showing the actual information before the check date
Display with. The number of scheduled update days input to the check date 113 is displayed in a horizontally long blank box 114. Blank box 11
Next to 4, the scheduled update days 115 are displayed. The previous check date including the current check date is displayed by the vertical bar 116. Further, the progress coefficient of the current check date and the progress coefficient of the previous check date are displayed (“1.14” and “1.57” in the figure). Here, as of May 1, the work was supposed to be completed 1.14 times the schedule,
As of June 1, it can be seen at a glance that it will take 1.57 times as many days as planned. That is,
It will be easy to understand that the delay in progress is increasing.

As described above, according to the present invention, by displaying the progress status graphically, it is possible to easily confirm the actual result of the schedule, the number of scheduled update days, and the progress / delay of the progress.

[0027]

As described above, in the production start-up management display device of the present invention, the progress status of each of the plurality of divided subsystems and the progress status of each of the plurality of divided subsystems are summarized, and the entire project is completed. It is possible to display the progress status as. Further, it is possible to calculate the progress coefficient indicating the progress / delay of progress. By graphically displaying this information, the progress of the entire production development can be grasped with higher accuracy, and the production development management including the progress management can be easily performed without imposing a burden on the manager.

[Brief description of drawings]

FIG. 1 is a diagram for explaining an outline chart.

FIG. 2 is a diagram for explaining a Gantt chart.

FIG. 3 is a diagram showing an overall configuration of a production development management display device according to the present invention.

FIG. 4 is a diagram showing project schedule information according to an embodiment of the present invention.

FIG. 5 is a diagram showing a result of setting scheduled update days on a progress check date according to an embodiment of the present invention.

FIG. 6 is a diagram showing a result of setting work performance values on a progress check date in an embodiment of the present invention.

FIG. 7 is a flowchart showing an outline of processing of the present invention.

FIG. 8 is a flowchart showing a method for setting progress of a plurality of subsystems as overall progress.

FIG. 9 is a diagram for explaining a progress coefficient.

FIG. 10 is a diagram for explaining a progress situation by simulation of a progress coefficient.

FIG. 11 is a diagram showing the progress status of a project in one embodiment of the present invention.

[Explanation of symbols]

 31 ... Input part 33 ... Analysis execution part 37 ... Storage part 38 ... Editing part 312 ... Display data synthesizing means 313 ... Display part

Claims (1)

[Claims] 1. A production development management display device for dividing a project into a plurality of subsystems, analyzing and displaying data information relating to the production development process input for each subsystem, wherein the data relating to the production development process is: First display means for displaying planned process days of each subsystem of the project based on the planned data and scheduled display update date data, plan data, and actual data, and comparative display of the actual data in correspondence with the planned process. And a third display means for making the scheduled update days data correspond to the planned process and additionally displaying the result data in a distinguishable manner for comparison display. Development management display device.