JP2010176255A - System for evaluation and management of development process - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system for evaluation and management of a development process for finding a difference between planned manhours in each development phase and actual results based on an input of progress information by a person in charge, to be evaluated, and for informing automatically a concerned person of the difference, when the difference is large. <P>SOLUTION: A daily report processing unit 11 processes the project progress information input by the person in charge, as a daily report, and calculates the actual result manhours in each development phase, based on management information of a project stored in a project management table 1. An evaluation processing monitor 12 executes an evaluation processing monitoring task, based on an abnormal condition monitoring method on progress evaluation of the project set in an operation setting table 5. An evaluation processing unit 13 conducts evaluation processing, based on the information processed by the daily report processing unit 11, and based on the results of the evaluation processing monitoring task executed by the evaluation processing monitor 12. Abnormal condition decision results are notified to the concerned person from an evaluation processing executing part 14 via a network 15, when the occurrence of abnormal conditions and restoration thereof are recognized. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a development process evaluation management system capable of performing progress management on an extension of a conventionally known progress management technique, not a complicated progress management technique such as earned value.

  Conventionally, a progress management method using earned value has been adopted as a progress management method for the construction industry and software development. This method is a method for predicting the future and grasping the progress of the project by converting time and progress into monetary value.

  Examples of applying the progress management method based on the earned value include, for example, “progress management device” disclosed in Patent Literature 1 below, “project prediction device based on risk” disclosed in Patent Literature 2 below, and A “work progress management system” disclosed in Patent Document 3 below is known.

  In patent document 1, the result of each process is expressed using a bubble chart. Moreover, in patent document 2, a risk is added to earned value management and project prediction is performed. Patent Document 3 describes a method for realizing earned value in work progress management.

JP 2007-018163 A JP-A-2005-004461 JP 2004-272624 A

  Progress management by earned value is complicated, and it is difficult for the administrator himself to take time for management work, such as an embedded software development system. There is a need for a simple progress management method.

  However, the progress management device disclosed in Patent Document 1 expresses the results of each process using a bubble chart, and the judgment of abnormality detection in progress management is entrusted to a person. There is a problem that it is ambiguous and sometimes misjudged.

  Further, the risk-based project prediction apparatus disclosed in Patent Document 2 performs project prediction by adding risk to earned value management, but the method is different from the development process evaluation management method of the present invention related to project prediction. However, there exists a subject that the effect like this invention cannot be expected.

  Further, the work progress management system disclosed in Patent Document 3 discloses a method for realizing a known earned value in work progress management, but the method is different from the development process evaluation management method aimed by the present invention. Thus, there is a problem that the effect as in the present invention cannot be expected.

  The present invention evaluates a development process by obtaining a difference between a planned man-hour for each development phase and a result based on progress information input by a person in charge, and automatically notifies a related person when the difference is large. The purpose is to provide a management system.

In order to solve the above problems, the present invention relates to a development process evaluation management system for evaluating and managing program development in an embedded device product, wherein the development process evaluation management system is constructed by a client and a server, and the server includes project management information. A project management table that stores a threshold, a project evaluation table that stores several levels of determination thresholds such as an upper limit, a lower limit, an upper upper limit, and a lower and lower limit for a work plan for evaluating the project, and a contact address when an abnormality occurs A contact registration table for storing information, a contact determination table for determining the contact according to the content of the abnormality, and an operation setting table for setting the abnormality monitoring method, and a person in charge of the project Development phase based on project progress information input by project managers The actual work man-hour calculating means for calculating the actual work man-hours, the abnormal occurrence / recovery checking means for checking the occurrence / recovery of abnormality in the progress of the project, and the new occurrence when the abnormality is newly generated / recovered An abnormality determination notification means for making a contact determination with reference to the contact determination table according to the content of the abnormality, and notifying the determined contact,
The client includes progress information input means for inputting project progress information in accordance with the progress of the project, and progress status display means for displaying a progress status up to the present along with the progress of the project. .

  According to the present invention, the project evaluation process is executed in the server based on the daily progress information input from the client, so that the personnel are smoothly input, and the development phase proceeds as scheduled. Since it is possible to automatically determine whether or not it is in contact with the parties concerned, the burden on the administrator who manages the development process can be reduced. When the person in charge does not input the progress information, an error about the lower limit defined in the project evaluation table occurs, so that the progress information not input can be automatically monitored. Furthermore, the location of the problem can be visualized by graphing the development process plan and results (eg, a stacked graph), and the problem can be easily grasped.

It is a figure which shows the structure outline | summary of the development process evaluation management system concerning embodiment of this invention. It is a figure which shows the structure of the project management table concerning embodiment of this invention. It is a figure which shows the structure of the project evaluation table concerning embodiment of this invention. It is a figure which shows the structure of the contact address table concerning embodiment of this invention. It is a figure which shows the structure of the contact determination table concerning embodiment of this invention. It is a figure which shows the structure of the operation | movement setting table concerning embodiment of this invention. It is a figure which shows the progress input screen concerning embodiment of this invention. It is a figure which shows the preparation example (the 1) of the evaluation graph concerning embodiment of this invention. It is a figure which shows the preparation example (the 2) of the evaluation graph concerning embodiment of this invention. It is a figure which shows the calculation result of the evaluation data concerning embodiment of this invention. It is a display example which shows the 1st evaluation method concerning embodiment of this invention. It is a display example which shows the 2nd evaluation method concerning embodiment of this invention. FIG. 13 is a partially enlarged view of a display example showing a second evaluation method shown in FIG. 12. It is a figure which shows the processing flow explaining the whole operation | movement of the development process evaluation management system which concerns on embodiment of this invention. It is a figure which shows the processing flow of the evaluation process starting task concerning embodiment of this invention. It is a figure which shows the flow of the evaluation process of the project progress information unit concerning embodiment of this invention.

Hereinafter, embodiments of the present invention will be described in detail.
FIG. 1 is a diagram showing a configuration outline of a development process evaluation management system according to an embodiment of the present invention. 1, the development process evaluation management system according to the embodiment of the present invention is constructed by a server (for management) 10, an administrator terminal 20 that is a client, and a person-in-charge terminal 30. And the client are communicably connected. The network can be an existing public network, LAN, WAN or the like regardless of wired or wireless.

  In FIG. 1, a server (for management) 10 includes a project management table 1 for storing project management information and several stages such as an upper limit, a lower limit, an upper upper limit, and a lower lower limit for a work plan for evaluating a project. A project evaluation table 2 for storing a determination threshold, a contact registration table 3 for storing an address of a contact at the time of occurrence of an abnormality, a contact determination table 4 for determining a contact according to the content of the abnormality, The database 7 includes an operation setting table 5 for setting an abnormality monitoring method and a project progress information holding unit 6 for holding project progress information input by a person in charge.

  Further, the server (for management) 10 processes the project progress information input from the person in charge of the project as a daily report, and calculates the work performance man-hours for each development phase based on the project management information stored in the project management table 1. The daily report processing unit 11 to be calculated, the evaluation process monitoring unit 12 that executes the evaluation process monitoring task based on the abnormality monitoring method related to the progress evaluation of the project set in the operation setting table 5, and the daily report processing unit 11 are processed. And an evaluation processing unit 13 for performing an evaluation process based on the result of the evaluation process monitoring task executed by the evaluation process monitoring unit 12, and the evaluation process execution unit 14 is constituted by these. Then, when the occurrence / recovery of the abnormality is recognized by the progress evaluation of the project performed by the evaluation processing unit 13, a predetermined contact is determined with reference to the contact determination table 4, and evaluation is performed according to the determination result. The process execution unit 14 automatically notifies the parties concerned via the network 15 of the occurrence / recovery of an abnormality based on the address registered in the contact registration table 3. Although not shown, the hardware resources for realizing the server function include, for example, a CPU, a storage device, an input / output device, various interfaces, and the like as well-known configurations. A program for realizing the functions as described above is stored in the storage device. The database 7 is realized by the above-described storage device, and each component in the evaluation processing execution unit 14 is realized by the above-described hardware resources such as the CPU, the storage device, and various interfaces, and various programs that execute a processing flow described later. Is done.

  On the other hand, the manager terminal 20 as a client displays a setting screen 21 for inputting information (project initial information) to the above-described predetermined table, and a screen for displaying the progress status up to the present as the project progresses (see FIG. 11, evaluation method 1 of FIG. 13, and evaluation method 2 of FIG. 13) 22, and a terminal 30 for a person in charge as a client includes an input screen 31 for inputting progress information of the project, and the progress of the project And a screen (see Evaluation Method 1 in FIG. 11, Evaluation Method 2 in FIG. 13, etc.) 32 that displays the progress state up to the present. Although not shown, hardware resources for realizing the client function include, for example, a CPU, a storage device, an input / output device, various interfaces, and the like as well-known configurations. A program for realizing the functions is stored in the storage device.

  FIG. 2 is a diagram showing a configuration of a project management table provided in the server of FIG. In FIG. 2, the project management table is composed of the following expansion items. That is, it comprises a development phase 41, a development step 42, a scheduled start date 43 for each development phase, a scheduled end date 44 for each development phase, and the number of users (MP: manpower) 45 for each development phase. Here, if the number of participants changes in the same development step, enter the phases separately. Since the information in the project management table overlaps with the information in the plan (planned) column of the project progress information, the information in the plan (planned) column of the project progress information is generated based on the information in this project management table. May be.

  FIG. 3 is a diagram showing a configuration of a project evaluation table provided in the server of FIG. In the project evaluation table shown in FIG. 3, a check range for each phase 51 (in this example, for each phase 1 to 6) is registered in order to perform MP (manpower) input evaluation. As the check range, in this example, there are five types of warning ranges for the plan (plan): an upper limit 52, an upper limit 53, a lower limit 54, a lower limit 55, and a plan achievement rate 56. The number may be increased or decreased as necessary. The set value for the plan (plan) is obtained from past similar development data, and is displayed as a percentage “%” in order to correspond to projects with different development scales.

  FIG. 4 is a diagram showing a configuration of a contact address table provided in the server of FIG. In the contact address table shown in FIG. 4, a name 61, a registrant type 62, a contact mail address 63, and a telephone number 64 are provided as items. When this contact is determined to be abnormal, an e-mail address, a telephone number, and the like are registered as the contact information of the person to be notified of the abnormality. As the registrant type 62, a system for executing this project is used.

  FIG. 5 is a diagram showing a configuration of a contact determination table provided in the server of FIG. In the contact determination table shown in FIG. 5, for each development phase, for example, in phase 1 (F-1) 71, senior manager 72, PM (project manager) 73, person in charge A74, person in charge B75 are contacted. On the other hand, as described with reference to FIG. 3, the occurrence 76 in the five warning ranges of the upper limit 52, the upper limit 53, the lower limit 54, the lower limit 55, and the plan achievement rate 56 for the plan (plan) 76. Recovery 77 items are provided. When the input data of the project progress information is determined to be abnormal by the project evaluation table shown in FIG. 3 and the occurrence of the abnormality is recognized, the necessity for notification is determined according to the content of the abnormality. It is a determination table. In FIG. 5, ◯ indicates that notification is required, and − indicates that notification is not possible.

FIG. 6 is a diagram showing a configuration of an operation setting table provided in the server of FIG. In FIG. 6, the operation setting table is used for designating the execution time of the evaluation process for evaluating the project in the server 10 from the “project progress information” (daily report) input from the terminal 30 for the person in charge shown in FIG. 1. Is. Specifically, as shown in FIG.
1. As the evaluation process starting method 81, the following three types of designation are provided. That is,
(1) Flag = 0: Do not execute evaluation process (2) Flag = 1: Execute when input is completed (3) Flag = 2: Execute at evaluation process execution time 1 time / day Evaluation processing execution time 82: Specify hours and minutes. This time is also used for checking daily report input.
3. Plan achievement rate evaluation day 83: Designates the day of the week to evaluate the plan achievement rate. Setting range: 0 to 6, but 0: Sunday, 1: Monday, 2: Tuesday, 3: Wednesday, 4: Thursday, 5: Friday, 6: Saturday Daily change flag 84: Designates whether the current day of the evaluation process execution time is the check date or the previous day is the check date. Flag = 0 is the previous day and flag = 1 is the current day. For example, if the evaluation process execution time is 01:00, the previous day (flag = 0) is designated. When setting 18:00 in the evening, specify the current day (flag = 1).
5). Daily report input delay monitoring day 85: Defines how many days later when the person in charge is notified of the presence or absence of notification of input delay.
6). Daily report input delay monitoring day 86: Defines how many days later to contact the PM (project manager) when there is an input delay notification.
7). Daily report input delay monitoring day 87: Defines the number of days to be notified when the senior manager is notified of the presence or absence of input delay.

FIG. 7 is a diagram showing a progress input screen for inputting project progress information from the terminal (client). In FIG. 7, the items to be input are as follows. That is,
1. At the time of planning, a development phase corresponding to a small item, a person in charge, a planned man-hour, and a scheduled MP (time) for each day (eg, scheduled time for each day from April 1 to 30) are input. When working with multiple people, such as coding, enter the item (NO.) Separately.
2. 2. Enter the actual work man-hours (hours) and progress once a day during operation. The actual work total “work” is automatically calculated from the actual work man-hours (hours) in person days in order to represent the planned man-hours and units.
4). The progress rate is entered manually.

  FIG. 8 is a diagram showing an example (part 1) of creating an evaluation graph. In FIG. 8, an example of creating an evaluation graph (part 1) is the development phase (F-1 to 7), development step (design item), scheduled start date for each development phase in the project management table shown in FIG. Based on the scheduled completion date for each development phase and the number of users (MP: manpower) for each development phase, it is created based on the progress information of the project in FIG. 7 (daily report: input of person in charge on progress input screen). In FIG. 8, the horizontal axis (X coordinate) indicates the development period, the vertical axis (Y coordinate) indicates the number of people (MP: manpower) to be input to the development step (design item), and the plan 90 related to the project is shown as a whole. I have to.

  FIG. 9 is a diagram illustrating a creation example (part 2) of the evaluation graph. In FIG. 9, an evaluation graph creation example (part 2) is created by adding a warning range set by the project evaluation table of FIG. 3 based on the plan 90 of FIG. That is, it is created by adding four types of warning (check) ranges of an upper limit 91, an upper limit 92, a lower limit 93, and a lower limit 94 to the project plan 90 of FIG.

  FIG. 10 is a diagram showing the calculation result of the evaluation data. In the progress input screen shown in FIG. 7, the results created based on the project progress information input are displayed in a graph. In FIG. X coordinate) shows the development period, vertical axis (Y coordinate) shows the number of people (MP: manpower) input in each development phase, and the performance graph shows the amount of input (MP: manpower) input in each development phase. This is shown as a trajectory.

  FIG. 11 is a display example showing the first evaluation method, in which FIGS. 9 and 10 are superimposed and displayed. In the display example showing the first evaluation method shown in FIG. 11, the performance line shown in FIG. 10 indicates the lower limit, upper limit, upper upper limit and upper limit shown in FIG. At the time of crossing the upper and upper limit graphs, the person to be contacted is determined from the contact determination table shown in FIG. 5, and the fact that a difference worth a warning has occurred is notified to the plan. In the example shown, the performance line is expressed as if it follows a continuous curve, but it actually changes and changes in a staircase shape. It is approximated by a smooth curve.

In FIG. 11, abnormality notification processing is executed in the following state.
[1. Time of occurrence]
Lower limit error: A- (1), A- (2)
Upper limit error: A- (3), A- (5)
Upper / lower limit error: A- (4), A- (6)
[2. During recovery]
Lower limit error: B- (1), B- (2)
Upper limit error: B- (3)
Upper / lower limit error: B- (4)
12 and 13 are display examples showing the second evaluation method. In the examples shown in FIGS. 12 and 13, the plan achievement rate is calculated once a week, that is, once / week. It is displayed for evaluation. FIG. 13 is an enlarged view of portion A shown in phases 1 and 2 in FIG. On the other hand, FIGS. 8 to 11 show an image of the first evaluation method, and the results of the input amount of personnel (MP: manpower) for a preset development period are shown once a day, that is, The project progress is evaluated by calculating only once per day and judging whether the result exceeds the threshold.

  The method of calculating the plan achievement rate by performing the once / week calculation shown in FIG. 12 and FIG. 13 may be strictly one time / day calculation, but if a delay occurs, the delay corresponding to that In some cases, personnel (MP: manpower) may be thrown in to recover the power. In this example, the input of personnel (MP: manpower) is a form that is normally performed, and if recovery can be performed in a short period (for example, within 2 to 3 days), it is not necessary to place importance on the problem. In order to level out the input of personnel (MP: manpower), the calculation is performed on a weekly basis.

  FIG. 12 corresponds to a superposition of FIG. 8 and FIG. Then, as shown in FIG. 13 in which the A portion shown in Phases 1 and 2 of FIG. 12 is enlarged, the ratio (area ratio) of the overlapping portion of the planned man-hour (see FIG. 8) and the actual man-hour (see FIG. 10) for each phase. If the development is progressing as planned (planned), the result is below the planned achievement rate defined in the “plan achievement rate” 56 item of the project evaluation table shown in FIG. The person to be contacted is determined in the occurrence and recovery in the plan achievement rate item of the contact determination table shown in FIG. 5, and a warning is sent to the determined person. In this example, the plan achievement rate for determination is one stage, but it may be determined by providing a plurality of stages of plan achievement rate.

  FIG. 14 is a diagram showing a processing flow for explaining the overall operation of the development process evaluation management system according to the embodiment of the present invention. The processing flow shown in FIG. 14 will be described together with the configuration outline of the development process evaluation management system shown in FIG. In the processing flow of FIG. 14, the processing flow (a) shown on the left side shows the project initial setting (step 20) by the PM (project manager) using the manager terminal 20 shown in FIG. The manager sets the various tables in the database 7 in the server 10 shown in FIG. 1 at the start of the project (step 21). That is, a project management table 1 for storing project management information, a project evaluation table 2 for storing determination thresholds in several stages such as an upper limit, a lower limit, an upper upper limit, and a lower lower limit for a work plan for evaluating a project, A contact registration table 3 for storing the address of the contact at the time of occurrence, a contact determination table 4 for determining a contact according to the content of the abnormality, and an operation setting table 5 for setting an abnormality monitoring method, Register settings for each of these.

  Next, as shown in the processing flows (b) and (c) shown in the center and right side of FIG. 14, in the server processing (step 10), first, the server 10 is a client of progress data (screen) (the person in charge shown in FIG. 1). To the terminal 30) (step 11). In the person-in-charge terminal process (step 30), the person in charge calls the progress input screen using the terminal 30 for person in charge (step 31). These processes correspond to a logon process in a normal client / server system. Then, after performing the work on that day, the person in charge inputs the work time (daily report) corresponding to the work on that day, and transmits the input data to the evaluation processing execution unit 14 in the server 10 (step 32).

  In response to this, in the processing flow (b), the daily report transmitted from the terminal 30 for the person in charge is registered in the daily report processing unit 11 in the evaluation process execution unit 14 (step 12). In this processing, data is registered in the project progress information holding unit 6 in the database 7. When the daily report is registered, the evaluation process monitoring unit 12 in the evaluation process execution unit 14 refers to the setting contents of the operation setting table 5 (see FIG. 6) to determine whether the evaluation process can be executed. When the flag in the execution method of the evaluation process shown in FIG. 6 is set to “execute when input is completed” (step 13: Yes), the evaluation process unit 13 in the evaluation process execution unit 14 [Evaluation processing] is executed (step 14). This [evaluation process] will be described later. If a new abnormality occurs as a result of the execution of [evaluation processing] (step 15: Yes), an abnormality is detected from the evaluation processing unit 13 in the evaluation processing execution unit 14 via the network 15 to the client (person in charge terminal). Notification is performed (step 16). This abnormality notification will also be described later. On the other hand, in the person in charge terminal (client) process in the process flow (c), when the evaluation process result is transmitted from the evaluation process execution unit 14, the transmission result is displayed on the terminal screen (step 33).

  FIG. 15 is a diagram illustrating a process flow of an evaluation process activation task that is a component 12 of the evaluation process execution unit. The process flow (a) shown on the left side of FIG. 15 shows the main flow of the evaluation process activation task, which is activated when the server 10 is activated, and constantly monitors the activation of the evaluation process. The evaluation process activation task process is performed by the evaluation process monitoring unit 12 in the evaluation process execution unit 14 as described above. That is, the evaluation process monitoring unit 12 refers to the operation setting table 5, and if the evaluation process is other than invalid (= not evaluated) (step 41: Yes), waits until the evaluation process execution time is reached (step 42). ). If it is invalid (= not evaluated) (step 41: No), the processing is stopped (sleep) for a predetermined time and it is checked again whether there is a definition (step 43). This is because the evaluation process is executed even if the setting of the operation setting table 5 is changed after the server 10 is started.

  When the evaluation process execution time has arrived (step 42), it is shown in the processing flow (b) on the right side of FIG. 15 whether or not all target daily reports ("project progress information") have been input. (Input check of “Project progress information”) Check by the process. Thereafter, it is checked whether the “operation setting” defined in the operation setting table 5 is “executed at the evaluation processing execution time” (step 46). If the execution is confirmed (step 46: Yes), [ Evaluation process] is called (step 47). This [evaluation process] will be described later.

The “daily report (“ project progress information ”) input check” process shown in the processing flow (b) on the right side of FIG. 15 is the final input delay specified for each senior manager, PM (project manager), and person in charge. The date is checked, and if it is not input, a notification of non-input is made according to the following procedure (step 51). That is, if the monitoring is valid, the “date of input confirmation” to be completed is determined from the current date and the “daily date designation flag” 84 defined in the operation setting table 5. In "Daily day designation flag" 84,
Daily date designation flag = 0 (previous day designation): “input confirmation date” for checking the previous day of the current day (step 52)
Daily date designation flag = 1 (current day designation): “input confirmation date” for checking the current date (step 53)
Next, go back to the past from the “input confirmation date” where the input of “project progress information” should be completed, and the month and day that are entered in the second column of the column for entering the work day of the month shown in FIG. The last input date is found (step 54), and the difference between the “input confirmation date” and the “last input date” excluding the actual work day (excluding work days, work days) is obtained (step 55). The actual working day may be determined based on the date when the scheduled time for each day of the “project progress information” is not input, or a table for setting the working day and the non-working day may be provided separately. If the difference is greater than or equal to the delay date specified by the senior manager, PM (project manager), or person in charge (see the operation setting table definitions 85 to 87 shown in FIG. 6), contact the subject. Perform (step 56 to step 64).

  FIG. 16 is a diagram showing a flow of evaluation processing for each project progress information unit. The process flow (a) shown on the left side of FIG. 16 shows the main flow of the evaluation process in units of project progress information. The evaluation process is executed by the evaluation processing unit 13 in the evaluation processing execution unit 14 described above. The evaluation process is called by “server process” or “evaluation process monitoring task”, and the evaluation process determines two call sources (step 71). In the case of “server processing” (step 71: No), an evaluation process is performed on the corresponding daily report (“project progress information”) (steps 72 to 74). On the other hand, the call by the “evaluation process monitoring task” (step 71: Yes) executes the evaluation process for all the project progress information registered in the server 10 (steps 75 to 78).

  The process flow (b) shown in the center of FIG. 16 shows the flow of “evaluation process 1”, and “evaluation process 1” is called every day. Also, the processing flow (c) shown on the right side of FIG. 16 shows the flow of “evaluation processing 2”, and “evaluation processing 2” is the plan achievement rate evaluation day of the week (the operation setting table definition 83 shown in FIG. 6). Called).

  Next, the process flow (b) of “evaluation process 1” shown in the center of FIG. 16 will be described. The process flow (b) of “evaluation process 1” performs determination based on a threshold value, and this process flow (b) called from the main process flow (a) shown on the left side of FIG. 16 is registered in the project evaluation table 2. The threshold value is obtained from all the threshold values (%) and the actual man-hours of the project, and the previous value and the current value cross the threshold value, and occurrence / recovery is determined at that time (steps 82 to 89).

Then, as described with reference to FIG. 11, it is determined that it has occurred in the following case.
(A) When the threshold value is the upper limit and upper limit, it is determined that it has occurred: Previous value <Threshold value <Determined that the current value has been restored: Current value <Threshold value <Previous value (b) Occurs when the threshold value is the lower limit and lower limit It is determined that the current value <threshold value <the previous value has been restored: the previous value <threshold value <current value (c) when a plurality of threshold values are simultaneously crossed (step 85).
If it is determined that an abnormality has occurred (step 86: Yes), a high level alarm is notified of the corresponding abnormality (step 87). For example, when the upper limit error is exceeded from normal, the upper limit threshold is crossed, but only the upper limit abnormality is notified. If it is not determined that an abnormality has occurred (step 86: No), it is determined to be recovered and the recovered error The alarm of a low level or normal is notified (step 89). For example, when the upper limit abnormality becomes normal, the upper limit threshold is crossed, but only normal is notified.

Next, the process flow (c) of “evaluation process 2” shown on the right side of FIG. 16 will be described. The process flow (c) of “evaluation process 2” is a determination based on the plan achievement rate, and is called from the main process flow (a) shown on the left side of FIG. 16, and the determination is performed according to the following procedure. That is,
(A) A personnel (MP) input plan for one week for each development phase is calculated (step 91).
(B) The number of personnel (MP) inputs in one week unit for each development phase is calculated (step 92).
(C) For each development phase, find the absolute difference between the weekly personnel (MP) input plan within the planned period and the weekly personnel (MP) input results, and the number of personnel (weekly) until the day ( MP) The difference from the input plan is calculated, and the ratio is calculated by the sum of the entire development phase up to the day (steps 93 to 95).

Plan achievement rate = Σ (MP input plan-| MP input plan-MP input results |) / Σ MP input plan (d) Determine whether the execution rate is lower than the threshold, which is the planned execution rate in the project evaluation table. If the rate is low, notification is made (steps 96 to 97).

DESCRIPTION OF SYMBOLS 1 Project management table 2 Project evaluation table 3 Contact registration table 4 Contact determination table 5 Operation setting table 6 Project progress information 7 Database 10 Server 11 Daily report processing part 12 Evaluation process monitoring part 13 Evaluation processing part 14 Evaluation process execution part 15 Network 20 Administrator terminal (client)
21 Setting screen 22 Evaluation screen 30 Terminal for the person in charge (client)
31 Input screen 32 Evaluation screen

Claims (7)

In a development process evaluation management system for evaluating and managing program development in an embedded device product, the development process evaluation management system is constructed by a client and a server,
The server
A project management table for storing project management information;
A project evaluation table that stores determination thresholds in several stages such as an upper limit, a lower limit, an upper upper limit, and a lower lower limit for a work plan for evaluating the project;
A contact registration table that stores the address of the contact in the event of an abnormality,
A contact determination table for determining the contact according to the content of the abnormality;
An operation setting table for setting the abnormality monitoring method;
With
Work performance man-hour calculating means for calculating work performance man-hours for each development phase based on project progress information input from a person in charge of the project,
Abnormality occurrence / recovery checking means for checking occurrence / recovery of abnormality in the progress of the project,
An abnormality determination notifying means for determining a contact by referring to the contact determination table according to the content of the new abnormality and notifying the determined contact when the abnormality newly occurs / recovers; ,
Have
The client
Means for inputting project progress information in accordance with the progress of the project;
Means for displaying the progress status to date as the project progresses;
A development process evaluation management system characterized by comprising: The server
According to the contents set in the operation setting table, either the evaluation process is executed when the data input from the person in charge is completed, or the evaluation process is executed once / day at a designated time. The development process evaluation management system according to claim 1, further comprising an evaluation process activation method selection unit that can be selected by a manager of the project. The server
An input confirmation date determination means for determining an input confirmation date from the value of the daily change date designation flag set in the operation setting table and the current date;
A difference calculation means for calculating a difference between an actual operation date obtained from the project progress information input from the person in charge and an input confirmation date determined by the input confirmation date determination means;
Non-input notification means for notifying the person in charge that the project progress information has not been input if the difference is equal to or greater than the delay date specified in the operation setting table for each party involved in the progress of the project. The development process evaluation management system according to claim 1, further comprising: The abnormality occurrence / recovery checking means is:
Based on the input project progress information, read out several levels of judgment thresholds such as upper limit, lower limit, upper upper limit, lower lower limit and the like for the work plan for evaluating the project stored in the project evaluation table. 2. The development process according to claim 1, wherein an occurrence or recovery of an abnormality is detected by detecting whether the actual work man-hour calculated by the actual man-hour calculating means exceeds the determination threshold or falls within the determination threshold. Evaluation management system. The contact determination table stores notification necessity determination information for determining necessity of abnormality notification set for each person concerned in the project,
The abnormality determination notification means determines whether or not abnormality notification is necessary for each person concerned in the project by referring to the contact determination table according to the content of the new abnormality when the abnormality newly occurs or recovers. The development process evaluation management system according to claim 1, wherein notification is made to related parties determined to be necessary. The server
Plan achievement rate calculation means for calculating the plan achievement rate for each development phase from the degree of overlap between time and input personnel,
The difference between the plan achievement rate and the plan achievement rate registered in advance in the project evaluation table is evaluated, and when the calculated plan achievement rate is low, each person concerned in the project is referred to the contact determination table. An unsuccessful notification means for determining whether or not an abnormality notification is necessary and notifying the determined parties
The development process evaluation management system according to claim 1, comprising: The plan achievement rate calculating means obtains the difference between the weekly personnel input plan and the weekly personnel input result for each development phase as an absolute value, and the weekly personnel input plan up to the current day. And calculate the ratio as the sum of all development phases up to the day,
The development process evaluation management system according to claim 6.