JP5336906B2 - Design process management device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide various pieces of information usable for comprehending whether or not there is any futility or problem in an actually performed operation including an operation process, which has been already finished, in form easy as possible to understand in a development project having a plurality of design processes. <P>SOLUTION: A design process management device includes: a process management database in which the creation plan of specification to be created in each design process is registered; and a drawing management database in which the created specifications to which unique figure numbers are attached are registered with their update history, and configured to retrieve the process management database and the drawing management database in response to a request from a client terminal, and to diagram-display the creation and update results of the respective specifications on a coordinate plane with one axis as a time and the other axis as a design process by using the creation start time of the respective specifications as a start point. <P>COPYRIGHT: (C)2011,JPO&amp;INPIT

Description

  The present invention relates to a design process management apparatus for a development project having a plurality of design processes.

  In recent years, the importance of project management has increased with the increasing complexity of systems and products. Conventionally, several project management techniques useful for development models such as a waterfall type, a spiral type (iteration type), and a parallel type have been disclosed.

  For example, Patent Document 1 discloses a technique for performing production management using a production process management chart obtained by extending a Gantt chart. Patent Document 2 discloses a project management and work management technique suitable for a spiral type development model, and Patent Document 3 discloses a technique for minimizing rework of a work in a parallel type development model. It is disclosed.

JP 2004-178150 A JP 2006-338309 A JP-A-9-190460

  However, all of these conventional project management technologies are focused on grasping the progress of the project in real time, so how the work processes that have already been completed are actually performed, and those operations are wasted. It was difficult to figure out if there was a problem.

  The present invention has been made to solve the problems of the prior art, and is useful for grasping whether there is no waste or problem in the work actually performed, including work processes that have already been completed. The purpose is to provide various kinds of information in an easy-to-read form.

In order to achieve the above-mentioned object, in the present invention, in a design process management apparatus for managing a development project having a plurality of design processes, between the creation plan of specifications and specifications to be created in each design process A process management database in which the dependency relationship is registered, and a drawing management database in which a unique drawing number is assigned to the created specification and registered together with the update history, and the process is performed according to a request from a client terminal. A coordinate plane in which a management database and a drawing management database are searched and the creation and update results of each specification are displayed on the display unit of the client terminal, with one axis as time and the other axis as a design process above, the a start point of the production start time of each specification, together to the diagram indicated by lines that create end time as an end point Referring to the dependency relationship between the specifications registered in the process management database, connect the end point of the line corresponding to the upper specification in the dependency relationship and the start point of the line corresponding to the lower specification. The line was displayed on the coordinate plane .

  According to the present invention, the creation and update history of specifications that are the product of each design process in a development project including a plurality of design processes is displayed in a diagram with the time as an axis. It is possible to easily grasp whether there is no waste or problem in the completed work.

It is a block diagram which shows the whole structure of a design process management system. It is a detailed block diagram of a process management processing part and a process management database. It is explanatory drawing of a waterfall type development model. It is explanatory drawing of a spiral type (iteration type) development model. It is a structure and data example of a specification preparation plan table. It is a detailed block diagram of a drawing management processing unit and a drawing management database. It is a structure and data example of a drawing management table. It is a structure and data example of a drawing history table. It is an example of a display of a specification creation plan diagram. It is a display example of a drawing history diagram display screen. It is a display example of a drawing creation results diagram. It is a display example of a drawing update history diagram. It is an example of a display of a high-order drawing connection diagram. It is a display example of a detailed display diagram. It is a display example of a diagram at the time of troubleshooting. It is a flowchart which shows operation | movement of a design process management apparatus.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, preferred embodiments for implementing a design process management apparatus according to the invention (hereinafter referred to as “this embodiment”) will be described in detail with reference to the drawings as appropriate. In the present embodiment, the “diagram” refers to the entire diagram representing the progress status of the process such as the design work with the time axis as the diagram representing the operation status of the transportation facility.

[System configuration]
FIG. 1 is a block diagram showing the overall configuration of a design process management system including a design process management apparatus according to the present invention. The design process management system 100 is constructed as a client server type computer system in which a design process management server 1 as a design process management apparatus according to the present invention and a plurality of client terminals 2 are connected by a LAN (Local Area Network) 3. Has been.

  The design process management server 1 is a computer including a CPU, a memory, a hard disk, and the like, and includes a communication interface 11 that performs communication with the client terminal 2 via the LAN 3, a process management processing unit 12, a process management database 13, and drawing management. A processing unit 14 and a drawing management database 15 are provided.

  Each of the process management processing unit 12 and the drawing management processing unit 14 represents a function realized by a predetermined program recorded on a hard disk or the like being loaded into a memory and executed by the CPU. 12 manages the plan and results of the entire design process, and the drawing management processing unit 14 manages the specifications and drawings that are created as the output of the design process and are input to the next design process.

  The process management database 13 and the drawing management database 15 are constructed so that various types of information can be systematically stored and searched. In the process management database 13, information for managing the entire design process is stored in the drawing management database 15. The main body of specifications and drawings and information for managing them are registered respectively.

  The client terminal 2 is a personal computer including a CPU, a memory, a hard disk, an input device, a display device, and the like. The client terminal 2 transmits instructions and requests input by the input device to the design process management server 1 via the LAN 3, and the design process. A screen to be displayed on the display device is generated based on the information received from the management server 1.

[Registration of process plan and specification creation plan]
As shown in FIG. 2, the process management processing unit 12 includes a process plan registration unit 21 and a specification creation plan registration unit 22, and the process management database 13 includes a process plan table 31 and a specification. And a creation plan table 32.
First, an outline of a method for registering process plan information in the process plan table 31 by the process plan registration unit 21 will be described.

As a standard model for product development, a waterfall type development model and a spiral type (iteration type) development model are mainly used.
As shown in the Gantt chart in FIG. 3, the waterfall type development model is the entire development process, for example, “basic design”, “functional design”, “detailed design”, “test design”, “manufacturing / testing”. ”Is a model in which the standard unit is divided into several steps, and the work of each step is performed based on the product of the previous step. The processes are executed in order from the upstream process, and no return to the previous process is performed.

  On the other hand, the spiral type (repetitive type) development model is a model in which prototype development consisting of the same processes as described above is repeated several times, and the results are fed back to the final product development. . FIG. 4 is a Gantt chart display of an example of a development plan in the case of performing a total of 3 iterations in a spiral type (iteration type) development model. In the example of FIG. 4, step 1 is omitted in the third iteration (cycle 3), and the iteration starts from step 2. As described above, in a spiral type (repetitive type) development model, each step is repeatedly executed a plurality of times. Therefore, normally, a product created in each step is reviewed each time it is repeated, and corrected or supplemented. Is done.

  The process plan registration unit 21 provides the client terminal 2 with a function of creating a Gantt chart of a process plan based on the development model, for example, and registers the created Gantt chart in the process plan table 31. In the process, the specification creation plan registration unit 22 is called from the process plan registration unit 21, and the specification creation plan registration unit 22 generates a specification creation plan to be created at each step constituting the process plan. A function of registering in the creation plan table 32 is provided.

  As shown in FIG. 5, the specification creation plan table 32 has a “specification ID” column 321, a “cycle” column 322, a “step” column 323, a “category” column 324, and a “specification name” column 325. , “Scheduled start date” field 326, “scheduled completion date” field 327, “number of created pages” field 328, “others” field 329, and “higher specification list” field 330, each line being It represents a specification record corresponding to each specification to be created.

  In each of the specifications records except for the “specification ID” field 321, information input to the input field displayed on the client terminal 2 corresponding to each field and transmitted to the design process management server 1 is stored. It is registered by the specification creation plan registration unit 22. These input fields may be data input from a keyboard or the like, or may be selected and input using radio buttons, check boxes, drop-down lists, or the like.

  The “specification ID” column 321 stores identification information for uniquely identifying each specification given by the specification creation plan registration unit 22 when a specification to be created is newly registered. The The “cycle” column 322, “step” column 323, and “category” column 324 store the cycle number, step number, and category type of the process in which the specification is created as a product. Here, the “category” is a predetermined character string indicating the type of specification such as “basic specification” and “detailed specification”.

  The “specification name” column 325 stores the specification name input from the client terminal 2. Although it is preferable that the name of this specification document does not overlap with other already registered specification documents, the duplicated name may not be excluded. In the “scheduled start date” column 326 and the “scheduled completion date” column 327, the scheduled start date and scheduled completion date of the specification are stored. In the “number of created pages” column 328, an integer value indicating the number of scheduled creation pages of the specification is stored. A character string indicating other information is stored in the “other” column 329 (no input is required).

  Further, the “upper specification list” column 330 needs to be referred to when creating the specification, and information that specifies the upper specification that cannot be created unless the specification is completed. Stored as a list of specification IDs. The data in the “upper specification list” column 330 is used to display a list of specifications registered so far, for example, on the input screen of the client terminal 2 when registering a creation plan of a certain specification. Generated by selecting and inputting items to be registered in the specification list. As will be described later, the data in the “upper specification list” column 330 is used to display the dependency relationship between specifications or drawings and to estimate the influence range when a change is made to the drawing.

  The data example shown in FIG. 5 shows a state of data registration of a specification creation plan corresponding to the spiral type (iteration type) development plan illustrated in FIG. 4, and this data example is as follows. Contains information on a specific specification creation plan.

In step 1 of cycle 1, a 10-page specification document named “XXX basic” is created (see the specification ID line: d1).
In step 2 of cycle 1, a 30-page specification document named “XX function A” and a 50-page specification document named “XX function B” are created (specification IDs: d2 and d3). Line).
In step 3 of cycle 1, a 100-page specification document named “XX details α” and a 200-page specification document named “XX details β” are created (specification IDs: d4 and d5). Line).
In step 4 of cycle 1, a 300-page specification document named “XXX test” is created (see the specification ID line: d6).
In step 1 of cycle 2, the 10-page specification “XXX basic” created in step 1 of cycle 1 is upgraded (refer to specification ID: d21 line).
・ In step 2 of cycle 2, the specifications “XX function A” and “XX function B” created in step 2 of cycle 1 are upgraded and updated to specifications of 50 pages and 70 pages, respectively (specifications (Refer to the lines of document IDs: d22 and d23).
In step 3 of cycle 2, the specification “XXX details α” created in step 3 of cycle 1 is upgraded and updated to a 300-page specification (see specification ID: line d24).
・ In step 2 of cycle 3, the specifications “XX function A” and “XX function B” created in step 2 of cycle 2 are upgraded and updated to specifications of 70 pages and 90 pages, respectively (specifications (Refer to the rows of the document IDs: d31 and d32.)

  Note that the “V” at the end of the data value in the “category” column 324 indicates that this is an upgraded version of an existing specification with the same name. Therefore, for example, for the specification “XX function A”, a new version is created with the specification ID: d2, the first version is upgraded with the specification ID: d22, and the second version is created with the specification ID: d31. Indicates that the plan is to create an up-version.

[Registering and updating drawing of specifications]
Subsequently, after the registration of the process plan is completed and each design process of the development project is started, the specification, which is the product, is registered or updated in the drawing management database 15 by the drawing management processing unit 14. A method will be described.

  6, the drawing management processing unit 14 includes a drawing management unit 41, a drawing number numbering unit 42, a drawing history registration unit 43, and a drawing history search unit 44, and includes a drawing management database. 15 includes a drawing management table 51, a drawing history table 52, and a drawing data file group 53.

  As shown in FIG. 7, the drawing management table 51 includes a “drawing number” column 511, a “specification ID” column 512, a “version” column 513, a “revision” column 514, a “status” column 515, “ The file name ”column 516 and the“ other attribute ”column 517 each have a drawing record corresponding to each updated version of the specification registered with the drawing number assigned to the drawing. .

  In the “drawing number” column 511, a drawing number assigned by the drawing number numbering unit 42 and used to uniquely identify the specification registered in the drawing is stored. In the data example of FIG. 7, the figure numbers are represented as fn1, fn2,..., But these values are automatically assigned by the figure number numbering unit 42 in the order in which the numbers are assigned. is there. The “specification ID” column 512 stores identification information for uniquely identifying each specification given when the creation plan is registered in the specification creation plan table 32.

  The “version” column 513 and the “revision” column 514 store the version number and revision number of the specification registered in the drawing. This version number is “01” at the time of initial registration, and the value is incremented by 1 every time the specification is upgraded. The revision number is “00” at the time of initial registration of each version. Each time the specification is revised, the value increases by one. Here, version upgrade refers to a planned major update such as updating the specifications created in the previous cycle when the same steps are repeated in a spiral development plan. Update means revision update means any other update that was not previously planned. Therefore, in the waterfall type development plan, there is no version upgrade, and only the revision upgrade is performed. In the spiral type (repetitive type) development plan, in principle, each specification is only the number of times planned. Version upgrade is performed.

  The “status” column 515 stores a status indicating whether each specification registered in the drawing is in a “not registered”, “waiting for approval”, “incoming”, or “out” state. The status of each specification can be obtained from a screen (not shown) displayed on the client terminal 2 by the drawing management unit 41 by “numbering”, “registration”, “approval”, “entry”, “exit”, “re-registration”. By performing operations such as “re-entry”, transition is made in the following order.

(1) By assigning a figure number, a drawing record is added as a status of “unregistered” (refer to the line of specification ID: d32).
(2) When the person in charge creates a drawing file of the specification and registers the file in the drawing management database 15, the status is updated from “unregistered” to “waiting for approval” (row of specification ID: d31) See).
(3) After the approver who has the authority to approve the drawing approves the specification in the status of “Waiting for approval”, the person in charge enters the warehouse to complete the registration of the drawing, which can be referenced from other departments. The status is “Receiving” (see specification IDs: d1, d21 and other lines).
(4) In order to update the drawing (version up or revision up), the person in charge makes a reservation to update the drawing, and the status becomes “exit” (the lines of specification IDs: d22 and d29 are changed). reference).
(5) Creating a drawing file of the specification updated by the person in charge and re-registering the file in the drawing management database 15 adds a drawing record whose status is “waiting for approval” (specification ID: d31 Line).
(6) After the approver who has the authority to approve the drawing approves the updated specification in the “Waiting for approval” status, the person in charge re-enters the drawing, and the re-registration of the drawing is completed and updated. The status of the record of the specified specification is changed from “Waiting for approval” to “Receiving”, and at the same time, the record of the pre-updated specification whose status is “Outgoing” returns to the status of “Receiving” (specification ID: d22, (See line d31).

  The “file name” column 516 stores the drawing file name input from the client terminal 2 when the drawing file is registered. This drawing file name must not be duplicated in the same directory as other drawing file names that have already been registered. Further, the “other attributes” column 517 stores information such as the name of the warehousing person, the name of the issuing person, the name of the approver, and the numberer of the number registered in the drawing.

  The data example shown in FIG. 7 shows a state when cycle 3 of the specification creation plan illustrated in FIG. 5 is started.

  As shown in FIG. 8, the drawing history table 52 includes a “date and time” column 521, an “event type” column 522, a “diagram number” column 523, a “version” column 524, a “revision” column 525, and “ Each of the lines represents an event record corresponding to an event that has occurred with respect to the specification registered in the drawing. These event records are added and registered at the end of the drawing history table 52 by the drawing history registration unit 43 every time a corresponding event occurs.

  The “date and time” column 521 stores the date and time when the event occurred. In the “event type” column 522, “numbering”, “registration”, “approval”, “receipt”, “exit”, “re-registration”, “re-approval”, “re-receipt” are shown as the types of events that have occurred. Is stored. The “drawing number” column 523, the “version” column 524, and the “revision” column 525 store the drawing number, version number, and revision number of the specification subject to the event, respectively. The “others” column 526 stores information such as the numberer name, the registrant name, the approver name, the warehousing name, and the issuing name.

  The data example illustrated in FIG. 8 represents a data example corresponding to the data in the drawing management table 51 illustrated in FIG.

[Diagram display]
Hereinafter, a method for displaying various diagrams useful for design process management from the specification creation plans and the history information of the creation results accumulated in the process management database 13 and the drawing management database 15 as described above will be described. To do.

  FIG. 9 is a display example of a specification creation plan diagram displayed on the client terminal 2 by the specification creation plan registration unit 22. In the specification creation plan diagram, the horizontal axis is time and the vertical axis is each step of the design process, and the date to start creating the specification (“planned start date” column 326 in FIG. 5) and the specification are created. FIG. 6 is a diagram in which a completion date (“scheduled completion date” field 327 in FIG. 5) is connected by a hatched line 91. When a plurality of specifications are created in the same step, a plurality of oblique lines corresponding to each specification are drawn.

  Further, in a slightly narrow space between steps, when there is a dependency relationship between specifications, a solid line 92 is drawn between the end points of the hatched lines 91 indicating the corresponding specifications. Further, by selecting the slanted line 91 with the mouse cursor 93 or the like, detailed information on the corresponding specification is displayed in the balloon 94.

  In the data example shown in FIG. 9, the specification ID is attached to the hatched line 91 for the sake of convenience in order to distinguish each specification, but the specification ID may be displayed on the actual screen. It does not have to be displayed.

The display example of FIG. 9 represents the dependency state between the following specifications registered in the “upper specification list” column 330 of the specification creation plan table 32 of FIG.
-Both specifications d2 and d3 depend on specification d1.
The specification d4 depends on the specification d2.
The specification d5 depends on the specification d3.
Specification d6 depends on both specifications d4 and d5.
From such a specification creation diagram, it becomes easy to understand the dependency of each design process that constitutes the development project, and if a delay occurs in a certain design process, it is estimated which process downstream it will affect. can do.

  FIG. 10 shows a basic configuration of a drawing history diagram display screen displayed on the client terminal 2 by the drawing history search unit 44. The drawing history diagram display screen is divided into a detailed data display unit 101 and a diagram display unit 102 in the vicinity of the center of the screen. The detailed data display unit 101 displays detailed information regarding the diagram displayed on the diagram display unit 102. The “single” button 103 and the “link” button 104 are buttons for selecting and inputting whether to display the diagram for only one step (design process) or to link and display the upper steps. The display content of the diagram display unit 102 is switched according to the selection result.

  The “detail” button 105 is a button for displaying a detailed display diagram screen to be described later in a separate window, and the “plan” button 106 and the “result” button 107 respectively display only the plan diagram, This button is used to select and input whether to display the plan diagram superimposed.

  As shown in FIG. 10, when the plan diagram is displayed with a broken line and the actual diagram is displayed with a solid line, when the plan and the actual result are matched, the broken line diagram indicating the plan is hidden in the solid line diagram indicating the actual result. Cannot be determined. In such a case, if the “plan” button 105 is selected and inputted, only the diagram of the hidden plan can be displayed.

  FIG. 11 is a diagram for explaining a method of analyzing the difference between the plan and the actual result from the diagram displayed on the diagram display unit 102, where the horizontal axis represents time and the vertical axis represents the start and end of steps. This is a diagram in which the actual result is drawn with a broken line 113 and with a solid line 114. Further, the symbol 111 indicates the planned start date, and the symbol 112 indicates the planned completion date.

  It should be noted that when starting the creation of the specification, it is assumed that numbering is performed first, and the actual start time is the time when the numbering is performed, and the completion time is the time when the warehousing is completed.

  First, in FIG. 11A, the planned broken line 113 and the actual solid line 114 coincide (for convenience of explanation, they are drawn close to each other in the figure), and the specifications are created as planned. Is a display example. From such a diagram, it can be estimated that the design work is being executed without any particular problem.

  In FIG. 11B, the actual solid line 114 is drawn on the right side of the broken line 113 of the plan with a substantially constant interval. From such a diagram, it can be inferred that the start of specification creation is delayed, and therefore the completion of the specification is delayed.

  In FIG. 11C, the starting point of the plan dashed line 113 and the actual solid line 114 are substantially coincident, and the end point of the actual plan is considerably more right than the plan. From such a diagram, it can be presumed that the work has been delayed due to, for example, more man-hours than expected or lack of personnel.

  In FIG. 11 (d), the starting point of the broken line 113 of the plan and the solid line 114 of the results are almost the same, and the end point is closer to the left than the plan. From such a diagram, it can be estimated that, for example, the estimated man-hours were excessive or the work was completed ahead of schedule as a result of adding more personnel than necessary.

  Further, FIG. 11E shows only the actual solid line 114 without the planned broken line 113. From such a diagram, specifications were created that were not in the original plan, and the plan itself was inadequate, or due to an unexpected cause, it was necessary to review the structure of the specification. It can be estimated.

  FIG. 12 shows an example in which the update history of a specification with a single figure number is displayed as a single diagram. FIGS. 12A and 12B show a case where different performance diagrams are drawn for the same plan diagram consisting of cycles 1 to 3. In FIG. 12 (a), the version upgrade plan of three specifications indicated by broken lines 113a, 113b, and 113c is actually executed only twice as indicated by thick solid lines 114a and 114b. There is an unscheduled revision upgrade work indicated by the thin solid line 115, and the number of repetitions of the originally planned step has been reduced from 3 to 2 due to the influence, and the product development is somehow scheduled. It can be estimated that it has been completed.

  In FIG. 12B, four upgrades indicated by solid lines 114a to 114d are actually executed for the same three-time version upgrade plan, and three times for some reason. It can be presumed that the product specification cannot be converged by repeating this step, and that the entire process is delayed as a result of repeating the step one more time.

  FIG. 13 shows an example in which the creation result of a certain specification is connected to a higher specification and displayed as a diagram. Since the broken line 113i of the plan of step i in FIG. 13A is connected to the broken line 113h of the plan of step i-1 which is the upper step, the specification of step i is the same as that of step i-1. It can be seen that the creation can only be started after completion. For this reason, the actual solid line 114i is also connected to the end point of the actual solid line 114h of the upper step, and since the start of this step is delayed by the delay of the upper step from such a diagram, the specification of this step is consequently obtained. It can be estimated that the completion of the book was also delayed.

  Also, in FIG. 13B, there is a dependency on the creation of the specification as well, as shown by the thin solid line 114j after the two specifications are created, as indicated by the solid lines 114h and 114i. The case where the revision of the unscheduled specification is performed in step i-1 for some reason is shown. In this way, when the upper specification is updated among the two specifications having the dependency relationship, it is usually necessary to reflect the change contents of the higher specification in the lower specification. In this example, since the update operation of the lower specification is not performed, a warning message such as “the upper drawing has been corrected” is displayed on the balloon 116 to clearly indicate that the update operation is necessary. Alternatively, a similar message may be distributed by e-mail to the person in charge of the specification, or the same message may be displayed on the screen of the client terminal 2 where the person in charge is logged in. .

  FIG. 14 shows a display example of a detailed display diagram screen displayed in another window when the “detail” button 105 in FIG. 10 is selected and input. This detailed diagram display screen is obtained by selecting and inputting one of the solid line and the broken line in the diagram displayed on the diagram display unit 102 in FIG. Information corresponding to the solid line or broken line in the selected state is displayed in a separate window.

  Such a detailed display diagram is created by extracting an event record related to the specification stored in the drawing history table 52, and in order to create a detailed display diagram as shown in FIG. In addition to adding a function for performing operations such as “check by team leader” and “return” to the drawing management unit 41, it is necessary to additionally register the history of those events in the drawing history table 52. Further, the process management processing unit 12 needs a function for registering information such as a person in charge, a team leader, and a project manager. In addition, the standard work man-hours in each standard work procedure must be registered in the design process management server 1 in advance.

  The detailed display diagram display screen is a diagram in which a horizontal line is drawn in the column of a person who performs work, with the horizontal axis representing time and the vertical axis representing the person involved in creating the specification. In the example of FIG. 14, the vertical axis indicates that the project manager, the team leader, and the person in charge are involved in the creation of the specification. The standard work procedure shown by the broken line 141 is that the person in charge first drafts the specification. It is assumed that the person in charge performs the “warehousing” work after the team leader checks it and obtains the approval of the project leader. On the other hand, from the actual diagram shown by the solid line 142 in FIG. 14 (a), the team leader checks the team leader again after the team leader makes a correction and the person in charge makes corrections. Therefore, it can be understood that the actual completion date indicated by the symbol 144 is delayed from the standard scheduled completion date indicated by the symbol 143.

  Further, from the actual diagram shown by the solid line 142 in FIG. 14B, it can be seen that there is a time loss between the completion of the check by the team leader and the start of the approval work by the project manager. For example, it can be estimated that a delay has occurred due to the absence of the project manager for some reason.

FIG. 15 shows a display example of a diagram in the case where an unexpected failure occurs in the development process and the specification is revised to cope with it. In FIG. 15A, a failure occurs at the time indicated by the Δ symbol 151 after completion of the specification indicated by the solid line 114, and the revision of the unscheduled specification indicated by the solid line 115 is executed as a countermeasure. It represents that it was done. 15 (b) and 15 (c) show that the team leader or the project manager actually compares the standard work procedure indicated by the broken line 141 in which the trouble countermeasure is completed by the correction of the specification by the person in charge. Since the review of the specifications has occurred, the actual work procedure is as shown by the solid line 142, indicating that it took a long time to deal with the failure.

  By using such a detailed display diagram, an actual work procedure performed in a certain design process can be analyzed in more detail, which helps to grasp waste and problems.

  FIG. 16 is a flowchart showing an outline of the operation of the design process management server 1. Hereinafter, an outline of the operation of the design process management server 1 will be described with reference to the flowchart of FIG.

  First, the design process management server 1 determines whether or not there is a specification creation plan registration request from the client terminal 2 in step S1, and if there is no registration request (No in step S1), the process proceeds to step S3. If there is a registration request (Yes in step S1), in step S2, the specification creation plan registration unit 22 executes a specification creation plan display / registration process, and the input specification creation plan is displayed in the specification creation plan table 32. Register with.

  Next, in step S3, the design process management server 1 determines whether or not there is a drawing information registration / update request from the client terminal 2. If there is no registration request (No in step S3), the design process management server 1 proceeds to step S6, If there is (Yes in step S3), in step S4, the drawing management processing unit 14 executes drawing management information display / registration processing, and the drawing management information and the drawing data file are stored in the drawing management table 51 and the drawing data file group 53. In addition to registration, in step S5, registration of an event that has occurred with respect to the specification registered in the drawing history table 52 is executed.

  Next, in step S6, the design process management server 1 determines whether or not there is a drawing history search request from the client terminal 2. If there is no search request (No in step S6), the process proceeds to step S8, and there is a search request. In step S7 (Yes in step S6), the drawing history search unit 44 executes drawing history search processing and displays various diagrams in accordance with requests from the client terminal 2.

  Next, in step S8, it is determined whether or not there is an end instruction from the client terminal 2. If there is no end instruction (No in step S8), the process returns to step S1 and the above processing is repeated, and if there is an end instruction (in step S8). Yes) The process ends.

  As described above, according to the design process management system according to this embodiment, the work results of each design process constituting the development project are displayed in a diagram in contrast to the plan. It is possible to easily grasp whether there was any waste or problem in the work performed. Furthermore, improvement in productivity of development projects can be expected by taking measures against such waste and problems.

  Although description of this embodiment is finished above, the aspect which implements this invention is not limited to these. For example, the process management processing unit 12 and the drawing management processing unit 14 may be executed by different computers, or various diagrams can be displayed from a Web client terminal by adding a Web service function to the design process management server 1. You may do it. In addition, the display forms of various screens, table configurations, and the like can be changed as appropriate without departing from the spirit of the present invention.

1 Design process management server (design process management device)
2 Client terminal 3 LAN
DESCRIPTION OF SYMBOLS 11 Communication interface 12 Process management processing part 13 Process management database 14 Drawing management processing part 15 Drawing management database 21 Process plan registration part 22 Specification preparation plan registration part 31 Process planning table 32 Specification preparation plan table 41 Drawing management part 42 Figure number Numbering unit 43 Drawing history registration unit 44 Drawing history search unit 51 Drawing management table 52 Drawing history table 53 Drawing data file group 100 Design process management system

Claims (6)

A design process management device for managing a development project having a plurality of design processes,
A process management database in which the creation plan of specifications to be created in each design process and dependencies between specifications are registered;
It has a drawing management database in which a unique drawing number is assigned to the created specification and registered together with its update history.
According to the request from the client terminal, the process management database and the drawing management database are searched, and the creation and update results of each specification are displayed on the display unit of the client terminal. On the coordinate plane with one of the axes as the design process, a diagram is displayed with a line starting from the creation start time of each specification and the end time being the creation end time, and the specification registered in the process management database. Referring to the dependency relationship between the books, a line connecting the end point of the line corresponding to the upper specification in the dependency relationship and the start point of the line corresponding to the lower specification is displayed on the coordinate plane. <br/> Design process management device characterized by this. The creation start time of each specification is the time when the drawing number of each specification is assigned or the time when each specification is issued, and the creation end time is the time when each specification is received. The design process management apparatus according to claim 1. A plan diagram in which a creation start time and a completion time of the specification are connected with a line is displayed on the coordinate plane together with a diagram showing the creation and update results of the specifications. The design process management apparatus according to claim 1 or 2. When drawing a diagram showing the creation and update results of each specification, use different types of lines between the specification registered in the specification creation plan and the specification not registered The design process management apparatus according to any one of claims 1 to 3. Of the two the specification at dependencies, higher specifications are updated, when the lower specification has not been updated, the claim 1, characterized in that display or mailing a warning message The design process management apparatus according to claim 4. Work performed by members involved in the creation of the specifications by searching the drawing management database for the history of work performed on the specifications corresponding to the line selected from the diagram showing the creation and update results of each specification. The history is displayed on a coordinate plane having one axis as a time and the other axis as a member by a line connecting the start time and end time of each work in time series order. The design process management apparatus according to any one of claims 1 to 5.

Images