JP2004213447A - Support device, support method and support program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To reduce time for collecting performance information by automatically collecting a document creation state. <P>SOLUTION: A document creating part 44 lets a terminal select a task to create the document out of a plurality of tasks stored in a project database 20. A template document corresponding to the selected task is acquired from a document database 30. The document is created by displaying the acquired template document on the terminal, and a progress measurement part 46 supports a project staff member and a project manager by calculating a progress percentage for the project using information of each database. <P>COPYRIGHT: (C)2004,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a support apparatus and method for supporting development management of a product development project.
[0002]
[Prior art]
The conventional development management method has the following problems.
In a conventional project management tool, when a task is disassembled into all tasks to be progress-managed, the load of inputting actual results increases.
Further, with the conventional project management tool, a created document can be linked to a task, but a task cannot be linked to a document being created.
In addition, since there is no mechanism for automatically collecting the progress from the task deliverable (document), the creator has to report (or input) the creation status of the document at any time.
Also, there is no mechanism to support the task setting and disassembly of the project manager.
[0003]
As a conventional development management method, for example, Patent Literature 1 discloses a mechanism for collecting results from a project product and defining a work process, thereby facilitating development management.
However, in the definition of work processes, means for editing from standard processes and diverting from similar projects are presented, but means for dynamically (rule-based) presentation of work processes according to the specifications are shown. Not.
For this reason, a great deal of effort was required for the project manager to perform the task selection.
[0004]
Patent Document 2 discloses a mechanism for collecting results from software development products (documents and source codes) in accordance with object-oriented development and design theory. No method for collecting progress information is disclosed.
[0005]
[Patent Document 1]
JP-A-10-154310
[Patent Document 2]
JP 2001-209530 A
[0006]
[Problems to be solved by the invention]
As described above, in the conventional development management method, when the project manager grasps the progress of the project, it is necessary to inquire the progress of the project to the person in charge of the project. Further, in the conventional development management system, when an administrator plans a project, an enormous amount of labor is required for disassembling it into tasks.
[0007]
SUMMARY OF THE INVENTION It is an object of the present invention to automatically collect document creation status and reduce the time required to collect performance information.
[0008]
Another object of the present invention is to automatically generate a task in accordance with project information (mainly product specifications) input at the time of project planning, thereby realizing labor saving in task setting work of a project manager.
[0009]
[Means for Solving the Problems]
The present invention provides a task database that stores a plurality of tasks belonging to each project of a plurality of projects in association with each project, with each work step of a project including a plurality of processes as a task,
A project including a task corresponding to the project specification information by selecting a task belonging to a project that satisfies the project specification information from a plurality of tasks stored in the task database based on the project specification information transmitted from the terminal. And a project generation unit for generating a project.
[0010]
BEST MODE FOR CARRYING OUT THE INVENTION
Embodiment 1 FIG.
FIG. 1 is an overall configuration diagram of a system when the present invention is implemented. The development management support device 40 is an example of a support device, and is connected to the terminals of a project manager and a project staff who are members of the project team via a network such as a LAN 50, and is connected to the task database 10, the project database 20, and the document database 30. The project manager and the project manager are supported by using the stored information.
[0011]
First, the outline of each database is described.
The task database 10 according to the first embodiment is a database that stores data relating to a basic task for automatically generating a project.
The project database 20 is a database for managing data related to a project.
The document database 30 is a database that stores documents and template documents created in the project. The document database 30 stores, for example, an XML file.
[0012]
Next, the internal configuration of the development management support device 40 of FIG. 1 will be described.
The development management support device 40 has, as interfaces, a database interface unit 41 for exchanging data with each of the above databases and a terminal interface unit 42 for interfacing with a terminal.
The development management support device 40 also has units having the following functions.
The project generation unit 43 selects a task belonging to the project that satisfies the above-described project specification information from a plurality of tasks stored in the task database 10 based on the project specification information transmitted from the terminal at the time of project planning by the project team. Generates a project including tasks according to the project specification information, and supports project planning.
The document creation unit 44 creates and edits a document based on the input from the terminal of the project staff.
The project change unit 45 changes the project plan based on the input from the terminal of the project manager.
The progress measuring section 46 measures the progress of the project and displays it on the terminal of the project manager.
The task database maintenance unit 47 performs maintenance of the task database 10 based on the input from the terminal of the project manager.
The alarm display section 48 displays an alarm (warning) on the terminal of the project manager.
The storage unit 49 temporarily stores various data input from the terminal.
[0013]
FIG. 2 shows an example of tasks managed in this project.
Tasks are represented in a tree structure. It is assumed that the tasks are decomposed into smaller tasks (work contents) in order from the upper layer. In FIG. 2, the higher the level, the higher the hierarchy.
Assume that the tree structure has the following restrictions.
1. There is no limit on the number of layers.
2. If there is no node at a lower level than a certain node, the node always has a document template (template document). That is, the task database 10 hierarchically stores a plurality of tasks belonging to each project in a tree-like manner, and stores a template document name of a task having no task associated with a lower level together with the task. The template document itself is stored in the document database 30 in the XML format, and always has at least one chapter, section, or item therein. This node, including the task that holds the template document, is hereinafter referred to as a "minimal task node".
3. A node including a task other than 1 (a task having a task associated with a lower level than itself) does not hold a document. This node is hereinafter referred to as an “intermediate task node”.
Here, a task refers to each step of a project including a plurality of work steps. Specifically, each block shown in FIG. 2 is a task. A document is a document that is a product obtained as a result of executing a task. Further, the template document is a document indicating an initial value of the processing content of the task, and specifically corresponds to each XML file shown in FIG.
For example, the task “development plan” is a task that has a task “creation of the organization table” that is associated with a lower level than the task itself, and the task “creation of the organization table” is a task that does not have a task associated with a level lower than the self. is there. An XML file (template document) having a template document name “organization table” is linked to the task “create organization table”. That is, the task database 10 stores the task configuration shown in FIG. 2 as an initial value, stores a template document name for a task having no task associated with a lower level than itself, and stores the template document name in the document database 30. By storing the XML file (template document) having the template document name, the task and the template document corresponding to the task are linked, and the development management support device 40 supports the development management by using the database. It becomes.
[0014]
First, a task generation support function performed by the project generation unit 43 at the time of project planning will be described.
An outline of the work flow of the project plan is shown in FIG.
Specifically, first, the project generation unit 43 causes the terminal to display the project registration screen shown in FIG. 4 (S31), and causes the project manager to input product specification information (project specification information) of a model to be developed in the project ( S32). Next, the project generation unit 43 uses the data stored in the task database 10 based on the product specification information input in S32 to automatically generate a task and construct a task tree (S33), and It is displayed on the project-specific task tree editing screen shown in FIG. 5 (S34). The project manager selects tasks necessary for the current project from the displayed task tree editing screen (S35). In FIG. 5, the task trees for the outline design, detailed design, first article management, and initial flow management at the bottom are omitted.
In the example of FIG. 5, in the current project, the check is removed because the project manager has decided not to perform “life cycle DR” and “first article management”. After the project manager selects a task to be performed in the current project, the project generation unit 43 causes the project manager to click the “Save” button in FIG. The task of the project selected by the project manager is stored in the project database 20 together with the corresponding template document if there is a corresponding template document name (S36).
[0015]
Conventionally, task generation has been based on tasks from a similar project or tasks of a reference project.
However, in the present embodiment, a plurality of tasks belonging to each project of a plurality of projects are stored in the task database 10 in association with each project, and a template corresponding to at least one of the plurality of tasks belonging to each project is stored. Store the document name with the task. Further, a template document indicating the initial value of the processing content of the task is stored in the document database 30. The project generation unit 43 selects a task belonging to a project that satisfies the project specification information from a plurality of tasks stored in the task database 10 based on the project specification information transmitted from the terminal, thereby responding to the project specification information. Generate a project containing the tasks Further, the project generation unit 43 obtains the template document name corresponding to the task included in the generated project from the task database 10 and obtains the template document having the obtained template document name from the document database 30 to generate the template document. Generate a project containing the task and the corresponding template document. Further, the project generation unit 43 generates a project including a plurality of tasks, causes the terminal to select a plurality of necessary tasks from among the plurality of tasks included in the generated project, and causes the terminal to select the project generation unit 43. The plurality of tasks and the template document names stored in the task database 10 corresponding to the plurality of tasks are stored in the project database 20.
As described above, in the development management support device 40 of the present embodiment, the task database 10 is utilized, and the project generation unit 43 that automatically generates a project including the tasks required for the project is used to convert product specifications (project specification information). Since a project including the corresponding task is automatically generated, the task setting task can be made more efficient.
[0016]
Next, an outline of automatic generation of tasks included in the project executed by the project generation unit 43 in S33 will be described.
FIG. 6 shows a flow of the task automatic generation included in the project. The project generation unit 43 temporarily sets the product specification information input in S32 in the storage unit 49 (S61). Next, using the product specification information (project specification information) set in the storage unit 49 as a search condition, the project generation unit 43 searches all the tasks stored in the task database 10 based on the search condition ( (S62) Only tasks that match the search conditions are stored in the storage unit 49 (S63), and after all searches, the search results stored in the storage unit 49 are stored in the project database 20 (S64). The details of the search will be described later.
[0017]
Next, details of data stored in the task database 10 will be described.
Information such as tasks is stored in the task database 10 in the format shown in FIG. FIG. 7 shows the maximum task tree format assumed to be performed in a project, and the tasks of each project are selected from these.
Each node is classified into an intermediate task node and a minimum task node as described above. The intermediate task node has a task 11 and a task extraction rule 12 as attributes. The minimum task node has a task 11, a task extraction rule 12, a template document 13, and progress determination information 14 as attributes.
The task database 10 stores all these information. An example of an actual table of the task database 10 will be described later.
[0018]
The details of the search of the task database 10 performed by the project generation unit 43 will be described.
When the search is executed, the search for the task 11 is executed in order from the upper hierarchy of the task tree. The project generation unit 43 searches for each task 11 based on the task extraction rule 12 attached to each node of the task tree and the input product specification information (project specification information), and extracts tasks required for the project. . For example, it is assumed that there is project specification information of “customer = XX power” in the project specification information (search condition) input from the terminal. It is also assumed that there is a task 11 in the task database 10 which is an intermediate task node or a minimum task node and whose task extraction rule 12 is "IF customer = OO power".
In this case, the project generation unit 43 recognizes that the task 11 whose task extraction rule 12 is “IF customer = XX power” matches the project specification information.
As described above, the project generation unit 43 searches the task database 10 for a task 11 that matches the input product specification information (project specification information), and extracts only the task 11 that matches the current project specification information. And store it in the project database 20.
[0019]
Next, a description will be given of a method in which each project staff creates and edits a document with the support of the document creating unit 44 during the progress of the project.
The document creation unit 44 allows the project staff to select a project to be assigned from the project list screen of FIG. 8 and clicks the “edit project” button. As a result, a task tree screen for the project staff is displayed.
FIG. 9 shows a task tree screen for the project staff. When the project staff selects the document name 15 to be edited, a document editing screen shown in FIG. 10 is displayed, and the document can be edited. After finishing editing the document, the project staff clicks the "Save" button.
The document creation unit 44 receives this and stores the document in the document database 30. To add a chapter or section, click the "Chapter / section" add button to add a chapter or section.
[0020]
As described above, the document creation unit 44 of the development management support device 40 according to the present embodiment causes the terminal to select a task for creating a document from a plurality of tasks stored in the project database 20, and corresponds to the selected task. A template document having a template document name is acquired from the document database 30, and the acquired template document is displayed on a terminal to support a project staff who creates a document. The document database 30 is supported by the document creation unit 44. By storing the document including the created document name in association with the template document, the development of the project can be promoted even when the document is created.
[0021]
Next, a method in which the project manager reviews the project plan when the project is in progress with the support of the project changing unit 45 will be described.
When reviewing the project plan while the project is in progress, the project change unit 45 activates the project change screen shown in FIG. On this screen, the project manager performs addition / deletion of the task 11, change of the scheduled completion date 16, change of the progress determination information 14, and completion processing.
[0022]
A method for adding / deleting the task 11 on the screen of FIG. 11 will be described.
When a task 11 to be added / deleted occurs, the task to be added or deleted is selected in the task tree of FIG. 11, and the “task addition” or “task deletion” button is clicked to add or delete. The nodes that can be added are limited to the minimum task nodes.
[0023]
The details of the addition of the task 11 after clicking the “add task” button will be described.
FIG. 12 shows a task addition screen for adding a task 11. In FIG. 12, the project changing unit 45 adds a task by causing a project person to designate a task name 51 and a document name 52 to be added. Here, the progress determination information 53 is made to select one from the number of pages, the number of lines, and the size. At this time, the measurement target range which is the target range for measuring the progress rate is the entire document. As the measurement reference 54, a numerical value serving as a reference is input to the above-described progress determination information 53, or the project changing unit 45 sets a reference value serving as a reference. For example, if the progress determination information 53 is the number of pages and the measurement criterion 54 is 20, the project changing unit 45 measures the progress rate based on how many pages of the document have been written for 20 pages. Further, for example, when the progress determination information 53 is a size and the measurement criterion 54 is 100, the progress rate is measured based on how many bytes of the document stored in the file are created for 100 bytes. When it is desired to change the progress determination information 53 or the measurement target range, the change is performed by a method described later.
[0024]
A method of changing the scheduled completion date 16 shown in FIG. 11 will be described.
When changing the scheduled completion date 16, the project manager or the person in charge of the project directly changes the scheduled completion date column in the front part of the project change screen in FIG.
[0025]
Describes how to perform completion processing when document creation is completed.
When determining that the creation of the document has been completed, the document creation unit 44 performs a completion process on the task. The document creation unit 44 allows the project manager to select a task for performing the completion processing in FIG. 11 and clicks a “complete” button. Thus, the task change is considered completed. The document of the task for which the completion processing has been performed cannot be edited.
[0026]
A method for changing the progress determination information or the measurement target range by the project changing unit 45 will be described.
When the progress determination information or the measurement target range is to be changed, the project changing unit 45 causes the project manager to select the task 11 to be changed in the task tree of FIG. 11 and clicks the “change measurement method” button.
FIG. 13 shows a screen for changing progress determination information or progress determination information for changing the measurement target range. The document structure 61 in FIG. 13 displays the result of analyzing the structure of chapters, sections, and items of the document (XML file) set for the task. The project change unit 45 causes the project manager to select a chapter, section, or item to be measured from the chapter, section, or item and click the “Add >>” button to change the measurement object to the right of the measurement range. 62, the progress determination information 53 and the measurement reference 54 are set for the added chapter, section, and item. When all settings are completed, click the "Change" button to complete the change of the progress judgment information.
[0027]
Next, a method in which the progress measuring unit 46 displays the progress status will be described.
The progress measuring unit 46 first displays the project list screen of FIG. 8 on the terminal of the project manager who wants to display the progress. The project manager clicks the “display progress” button on the project list screen. By this operation, the progress measuring unit 46 acquires the document creation status in real time, and displays the task tree for progress display shown in FIG. 14 on the terminal of the project manager. At this time, a progress rate 65 indicating the document creation status is displayed. The method of calculating the progress rate 65 will be described later.
[0028]
Describes how to display tasks that are scheduled to be completed later.
When displaying a task that has already passed the scheduled completion date 16, the project manager clicks the “Scheduled completion date delayed” button in FIG. 14. As a result, all nodes having the task 11 with a scheduled completion date delay in the lower layer are displayed in red. By using this function, the project manager expands the tree displayed in red from the upper hierarchy instead of expanding and displaying all the trees when searching for tasks that are past the scheduled completion date 16. Just get to the desired task.
[0029]
A method for displaying a task 11 that has not been completed will be described.
When displaying the task 11 that has not been completed, the project manager clicks the “completed view” button in FIG. Thus, the task 11 having the task 11 that has not been completed is displayed in red. By using this function, instead of expanding and displaying all the trees when searching for tasks 11 that have not been completed by the project manager, simply expand the nodes displayed in red from the upper hierarchy, You can reach the desired task.
[0030]
The calculation method of the above-mentioned progress rate 65 will be described in detail.
The progress measuring unit 46 collects the creation information of the currently created document and the progress of the entire project. FIG. 15 shows the flow of the progress information collection.
First, the progress measuring unit 46 causes the project manager to set a project number for which progress information is to be collected (S71).
Next, the progress measuring unit 46 acquires the task tree of the project from the project database 20 (S72), and executes the next loop processing for the nodes of the task tree.
When the node is the minimum task node, in other words, when there is no task associated with a lower level than itself (S73), since the XML format document always exists, the progress measuring unit 46 The structure of the document is analyzed (S74).
At the same time, progress determination information and a measurement target range are acquired (S75). When a plurality of measurement target ranges are set, each measurement target range is measured based on the progress determination information (S76), and finally merged to calculate a progress rate 65 for the document (S77). In this way, all the progress rates 65 of the documents attached to the minimum task node are calculated.
As a result, the progress rate 65 is calculated for each intermediate task node (a task having a task associated with a lower level than itself), so that the progress rate 65 of the entire project can be calculated (S78).
Here, when calculating the progress rate 65 of the upper task based on the progress rate 65 of the lower task, an average is taken. For example, assuming that there are three lower tasks and the respective progress rates 65 are 10%, 30%, and 50%, the progress rates of the upper tasks are averaged to 30% (S78).
[0031]
As described above, the progress measuring unit 46 acquires the document having the document name stored in correspondence with the task stored in the project database 20 from the document database 30 and predicts the information amount of the acquired document and the completion of the task processing. The task progress rate 65 is measured by comparing it with a measurement criterion that is the final information amount of the document. Further, the progress measuring unit 46 analyzes the structure of the document stored in the document database 30, specifies a plurality of measurement target ranges for which the progress rate is to be measured from the analyzed structure of the document, and specifies the plurality of specified measurement targets. The terminal selects one or more measurement target ranges from the range, and determines the information amount of the document corresponding to the selected measurement target range and the measurement reference of the measurement target range expected at the completion of the processing of the task of the measurement target range. The progress rate 65 of the measurement target range of the task is measured by comparison. Further, the progress measuring unit 46 measures the task progress rate by comparing the measurement standard transmitted from the terminal with the information amount of the document, using the progress determination information for determining the progress rate transmitted from the terminal. Then, the progress measuring unit 46 acquires a plurality of tasks for which there is no task associated with a lower level from the project database 20, measures the progress rate of each of the acquired tasks, and By measuring the progress rate of the project from the progress rate, the progress rate for each task, the progress rate for an arbitrary range within the task, and the progress rate of the entire project can be displayed to the project manager and project staff. , Making it easier to manage the progress of the project.
[0032]
Next, details of the maintenance function of the task database 10 performed by the task database maintenance unit 47 will be described.
The task database 10 stores the contents described above, and manages the tasks serving as the bases of all the projects.
However, tasks change from moment to moment, and the resulting documents and progress judgment information methods also change constantly depending on procurement requests and systems.
To cope with this, the development management support apparatus 40 includes a task database maintenance unit 47 having a maintenance function of the task database 10 so as to be able to respond to a change in a base task.
FIG. 16 shows a task database maintenance screen displayed by the task database maintenance unit 47. FIG. 16 shows the task tree and the attributes attached to the task nodes, so that addition, change, and deletion of the task tree nodes are possible.
[0033]
FIG. 17 shows a screen for adding or changing a node in the task tree. In FIG. 17, an extraction condition 72, a document name 73, a measurement target range 74, progress determination information 75, a measurement reference 76, and an area 77 can be set for each task.
A setting example of the task extraction condition 72 is shown below.
If "customer" is set as the specification item and "XX electric power" is set as the specification input value, this task is extracted only when the customer of the specification information of the product of the project is XX electric power. The conditions “and” and “or” are used when creating an extraction condition by combining a plurality of specifications. For example, “customer” is set as the specification item on the first line, “XX power” is set as the specification input value, and “and” is set as the condition. Next, “standard” is set to the specification item on the second line, and “JEC” is set to the specification input value. In this case, the customer of the project specification information is XX power, and this task is extracted when the standard is JEC. FIG. 18 shows an example of specification input value candidates.
[0034]
The setting method of the document name 73 and the setting of the measurement target range 74, the progress determination information 75, and the measurement reference 76 will be described. When an XML file serving as a form is specified in the document name 73, the structure of the document is analyzed and chapters, sections, and items are displayed. Select the chapter / section / section to be measured from the chapter / section / section and click the "Add >>" button to add it to the measurement range 74 on the right. To set the progress determination information 75 and the measurement reference 76. Here, in the case of the measurement reference of the measurement target range, it means the amount of information expected when the processing is completed for the measurement target range 74 in the task, and in the case of the measurement reference, when the processing of the task is completed Means the amount of information expected.
Finally, the area 77 to which the task belongs is set. FIG. 19 shows an example of area selection candidates.
[0035]
As described above, the task database 10 stores the task extraction rules 12 for extracting tasks for each task, and the task database maintenance unit 47 extracts the task extraction conditions transmitted from the terminal and the tasks that match the extraction conditions. A task having the task extraction rule 12 corresponding to the task extraction condition is extracted from the task database 10 based on the change content, and the extracted task is changed based on the change content of the task. , The task database 10 can be maintained.
[0036]
Next, details of the alarm function of the alarm display unit 48 will be described.
The alarm display section 48 determines in advance the alarm condition when an alarm mail is transmitted by the project manager under what kind of situation the project is, and stores the determined alarm condition in the storage section 49. Keep it.
The alarm display unit 48 collects project information, for example, by activating a monitoring program once a day, and sends an alarm mail to the project manager's terminal when the project is ready to send an alarm. I do. However, monitoring by the monitoring program may be performed several times a day, or may be performed once every several days. The warning method may be any method that can warn the project manager by a method other than sending a mail.
[0037]
FIG. 20 shows the alarm setting screen.
By setting the area 100, the number of tasks 101, and the condition 102 in FIG. 20, the alarm display unit 48 can transmit an alarm mail according to the condition for transmitting the alarm mail. For example, assume that “review” is set in the area of the first line, “5” is set in the number of tasks, “and” is set in the condition, “target cost” is set in the area of the second line, and “2” is set in the number of tasks. As a result, the number of tasks with an area code of "review" was reduced to 5 or less in all the tasks in a project, and the number of tasks with the area code of "target cost" was reduced to 2 or less in all the tasks. At this time, an alarm mail is transmitted by the alarm display unit 48.
[0038]
As described above, the alarm display unit 48 causes the terminal to select a task necessary for the project from the generated project, stores the selected task in the project database 20, and issues a warning to the project of the task stored in the project database 20. The warning condition to be issued is stored in the storage unit 49, the task stored in the project database 20 is monitored, and a warning is issued to the terminal when the project satisfies the warning condition stored in the storage unit based on the state of the monitored task. This can alert the project stakeholders.
[0039]
FIG. 21 shows a configuration diagram of the functions of each unit of the development management support device 40 described above.
[0040]
FIGS. 22 (a) to (d) and FIGS. 23 (d) to (g) show the configuration of each table stored in the task database 10 for realizing the development management support device 40 described above in each table format. Show.
The information on the tree configuration of the basic task 11 registered in FIG. 16 is stored in the basic task tree table 81 in FIG. Further, the document name, the storage location of the document, and the area code of the area 70 registered in FIG. 17 are also stored in the basic task tree table 81 in FIG.
The measurement target range 74, the progress determination information 75, and the measurement reference 76 registered in FIG. 17 are stored in the basic measurement method table 82 in FIG. The task extraction rules (task extraction conditions 72) registered in FIG. 17 are stored in the extraction rule table 83 in FIG.
The specification item table 84 in FIG. 23D, the specification input value table 85 in FIG. 23E, and the area code table 86 in FIG. 23F need to be determined in advance, and these tables are fixed. .
The alarm formula registered in FIG. 20 is stored in the alarm formula table 87 in FIG.
[0041]
Next, FIG. 24 shows a configuration of each table stored in the table format of the project database 20 for realizing the development management support device 40 described above.
The project name 22, the project number 23, the creation department 24, the creator 25, and the scheduled completion date 16 registered in FIG. 4 are stored in the project data table 88 in FIG.
Further, although the development section 26, environment (temperature) 27, environment (humidity) 28, and the like registered in FIG. 4 are not shown, they are stored in the project data table 88 in FIG.
The task information registered in FIG. 5 is stored in the project task tree table 89 in FIG. At this time, the task name, document name, template URL, and area code correspond to those in the basic task tree table 81 of FIG. The initial value completion flag is all set to 0 in the initial state, and is set to 1 when the corresponding task is completed. The date of completion is assumed to be the date of completion.
The task name, document name, and document URL registered in FIG. 12 are stored in the project task tree table 89 in FIG.
The progress determination information 53 and the measurement reference 54 registered in FIG. 12 are stored in the project measurement method table 90 in FIG. The measurement object 62, the progress determination information 53, and the measurement reference 54 registered in FIG. 13 are stored in the project measurement method table in FIG.
[0042]
FIG. 25 shows an example of a document (XML) template for realizing the development management support device 40 described above. For the template document, the structure of the document such as chapters, sections, and sections is created in advance by the project manager, and registered on the screen shown in FIG. 12 or FIG. By registering this template document, the document structure is clarified and recognized as a progress measurement target. The template document is stored in the document database 30.
[0043]
FIG. 26 shows an example of a document (XML) for realizing the development management support device 40 described above. This is the entity of the document including the contents of the document in the template document. When the project staff edits the document, the document (XML file) is edited through an interface provided by the terminal interface unit 42 as shown in FIG. The document is stored in the document database 30.
[0044]
In the development management support device 40 according to this embodiment, by searching for a task from the task database 10 according to the product specification, the task can be automatically generated and the development plan can be facilitated.
Further, the development management support apparatus 40 according to the present embodiment automatically collects the creation status from the document by managing the document created in the project as an XML (extensible Markup Language) file, thereby enabling the project person in charge. Without reporting the document creation status one by one, the project manager can grasp the document creation status.
The development management support device 40 according to this embodiment classifies tasks, analyzes the tasks according to the classification, and issues an alarm when the task deviates from a predetermined task tendency, thereby decomposing the tasks. It is possible to support the work and reduce the management work of the project manager.
[0045]
According to the invention of this embodiment, a task, a created document, and a schedule can be automatically set based on development model information, specifications, and hold points. This can provide a development plan support mechanism.
Further, according to the management level of the manager, it is possible to follow the progress of the task and the created document at each hold point. In this way, a system that complies with the development schedule is realized, and delays in delivery are prevented.
In addition, it is possible to share documents created in each development step, and it is possible to use the documents in the development of similar models and to refer to the documents in downstream development processes, thereby contributing to shortening the development period and improving the design quality.
[0046]
FIG. 27 is a computer basic configuration diagram of the development management support device 40.
27, a CPU 140 for executing a program is connected to a monitor 141, a keyboard 142, a mouse 143, a communication port 144, a magnetic disk device 146, and the like via a bus 138.
The magnetic disk device 146 stores an OS 147, a program group 149, and a file group 150. However, an embodiment in which the program group 149 and the file group 150 are integrated to form the object-oriented program group 149 is also considered as one embodiment. The program group 149 stores programs executed by the project generation unit 43, the document creation unit 44, the project change unit 45, the progress measurement unit 46, the task database maintenance unit 47, the alarm display unit 48, and the like. In the file group 150, each table stored in the task database 10, each table stored in the project database 20, a document stored in the document database 30, and the like are stored.
A program group 149 executed by each unit of the development management support device 40 is executed by the CPU 140 and the OS 147.
In each of the above embodiments, the development management support device 40 communicates with the terminal used by the project manager or the project staff via the LAN 50 using the function of the communication port 144.
[0047]
The terms "store", "register", "store", "display", and "save" described above mean to save in a recording medium.
[0048]
In all embodiments, each operation of each component is related to each other, and the operation of each component can be replaced as a series of operations while taking into account the relation of the operations described above. Then, by substituting in this way, an embodiment of the method invention can be obtained.
Further, by replacing the operation of each of the above components with the processing of each of the components, an embodiment of a program can be realized.
In addition, by storing the program on a computer-readable recording medium on which the program is recorded, an embodiment of the computer-readable recording medium on which the program is recorded can be provided.
[0049]
The embodiment of the program and the embodiment of the computer-readable recording medium recorded in the program can all be constituted by a computer-operable program.
Each process in the embodiment of the program and the embodiment of the computer-readable recording medium on which the program is recorded is executed by the program, and the program is recorded in the recording device, and is transmitted from the recording device to the central processing unit ( CPU) and each flowchart is executed by the central processing unit.
Also, the software and programs of each embodiment may be implemented by firmware stored in a ROM (READ ONLY MEMORY). Alternatively, each function of the above-described program may be realized by a combination of software, firmware, and hardware.
[0050]
【The invention's effect】
ADVANTAGE OF THE INVENTION According to this invention, the mechanism of a development plan support is provided and a development period can be shortened.
[Brief description of the drawings]
FIG. 1 is a configuration diagram showing an entire embodiment 1;
FIG. 2 shows an example of a project task.
FIG. 3 is a project generation work flow.
FIG. 4 is a project registration screen.
FIG. 5 is a task tree selection screen.
FIG. 6 is a task automatic generation flow.
FIG. 7 is a task database.
FIG. 8 is a project list screen.
FIG. 9 is a task tree screen.
FIG. 10 is a document editing screen.
FIG. 11 is a project change screen.
FIG. 12 is a task addition screen.
FIG. 13 is a screen for changing progress determination information.
FIG. 14 is a task tree for progress display.
FIG. 15 is a progress rate calculation flow.
FIG. 16 is a task database maintenance screen.
FIG. 17 is a task database maintenance detail screen.
FIG. 18 is a specification input selection candidate.
FIG. 19 shows area selection candidates.
FIG. 20 is an alarm setting screen.
FIG. 21 is a functional configuration diagram.
FIG. 22 is a configuration diagram of a task database.
FIG. 23 is a configuration diagram of a task database.
FIG. 24 is a configuration diagram of a project database.
FIG. 25 shows an example of a template document (XML).
FIG. 26 is a document example (XML).
FIG. 27 is a computer basic configuration diagram of a development management support device.
[Explanation of symbols]
10 Task database, 11 tasks, 14 Progress judgment information, 15 Document name, 16 Scheduled completion date, 20 Project database, 22 Project name, 23 Project number, 24 Creation department, 25 Creator, 26 Development category, 27 Environment (temperature) , 28 environment (humidity), 30 document database, 40 development management support device, 41 database interface unit, 42 terminal interface unit, 43 project generation unit, 44 document creation unit, 45 project change unit, 46 progress measurement unit, 47 task database Maintenance section, 48 alarm display section, 49 storage section, 50 LAN, 51 task name, 52 document name, 53 progress judgment information, 54 calculation basis, 62 measurement target range, 65 progress rate, 70 area, 72 task extraction condition, 7 Document name, 74 Measurement target range, 75 Progress judgment information, 76 Measurement criteria, 81 Basic task tree table, 82 Basic measurement method table, 83 Extraction rule table, 84 Specification item table, 85 Specification input value table, 86 Area code table, 87 alarm type table, 88 project data table, 89 project task tree table, 90 project measurement method table, 138 bus, 140 CPU, 141 monitor, 142 keyboard, 143 mouse, 144 communication port, 146 magnetic disk device, 147 OS, 149 Programs, 150 files.

Claims (13)

A task database that stores a plurality of tasks belonging to each project of a plurality of projects in association with each project, with each work step of a project including a plurality of processes as a task;
A project including a task corresponding to the project specification information by selecting a task belonging to a project that satisfies the project specification information from a plurality of tasks stored in the task database based on the project specification information transmitted from the terminal. And a project generation unit for generating a project. The support device further includes:
A document database that stores a template document indicating the initial value of the processing content of the task,
The task database stores a template document name corresponding to at least one of a plurality of tasks belonging to each project together with the task,
The project generation unit obtains a template document name corresponding to a task included in the generated project from the task database, and obtains a template document having the obtained template document name from the document database together with the generated task. The support device according to claim 1, wherein the support device generates a project including a corresponding template document. 3. The task database according to claim 2, wherein the task database stores a plurality of tasks belonging to each project in a tree-like manner and hierarchically stores the tasks, and stores a template document name of a task having no task associated with a lower level than the task itself. Assisted equipment. The project generation unit generates a project including a plurality of tasks, and causes the terminal to select a necessary plurality of tasks among a plurality of tasks included in the generated project,
The support device further includes:
3. The support according to claim 2, further comprising a project database that stores a plurality of tasks selected by the project generation unit by the terminal and template document names stored in the task database corresponding to the plurality of selected tasks. 4. apparatus. The support device further includes:
The terminal selects a task for creating a document from the plurality of tasks stored in the project database, obtains a template document having a template document name corresponding to the selected task from the document database, and stores the obtained template document in the terminal. A document creation unit that supports creation of documents by displaying them on
The support apparatus according to claim 4, wherein the document database stores a document including a document name created by the assistance of the document creation unit in association with a template document. The support device further includes:
A document having a document name stored in correspondence with the task stored in the project database is acquired from the document database, and the information amount of the acquired document and the final information amount of the document expected when the processing of the task is completed are measured. The support device according to claim 5, further comprising a progress measurement unit that measures a task progress rate by comparing with a reference. The progress measurement unit analyzes the structure of the document stored in the document database, specifies a plurality of measurement target ranges for which a progress rate is to be measured from the analyzed document structure, and specifies a plurality of measurement target ranges from the specified plurality of measurement target ranges. One or more measurement target ranges are selected by the terminal, and the task is performed by comparing the information amount of the document corresponding to the selected measurement target range with the measurement standard of the measurement target range expected when the processing of the measurement target range is completed. 7. The support device according to claim 6, wherein a progress rate of the measurement target range is measured. 7. The progress measuring unit according to claim 6, wherein the progress measuring unit measures a task progress rate by comparing a measurement criterion transmitted from the terminal with the information amount of the document using the progress determination information for determining the progress rate transmitted from the terminal. The support device described in. The progress measuring unit obtains a plurality of tasks for which there is no task associated with a lower level from the project database, measures a progress rate of each of the obtained tasks, and calculates a progress rate of each of the measured tasks. The support device according to claim 6, which measures a progress rate of the project. The task database stores task extraction rules for extracting tasks for each task,
The support device further includes:
A task having a task extraction rule corresponding to the task extraction condition is extracted from the task database based on the task extraction condition transmitted from the terminal and the task change content that matches the extraction condition, and the extracted task is referred to the terminal interface. The support device according to claim 1, further comprising a task database maintenance unit that changes the task based on the content of the change of the task received by the unit. The support device further includes:
A project database that allows the terminal to select a task necessary for the project from the generated project, and stores the selected task,
A storage unit for storing a warning condition for issuing a warning for the task project stored in the project database,
2. The alarm display unit according to claim 1, further comprising: an alarm display unit that monitors a task stored in the project database and issues a warning to a terminal when a project satisfies a warning condition stored in the storage unit based on a state of the monitored task. The described support device. Each work process of a project including a plurality of processes is set as a task, and a plurality of tasks belonging to each project of the plurality of projects are stored in the task database in association with each project,
A project including a task corresponding to the project specification information by selecting a task belonging to a project that satisfies the project specification information from a plurality of tasks stored in the task database based on the project specification information transmitted from the terminal. A support method to support a project by generating a. A process of storing a plurality of tasks belonging to each project of a plurality of projects in a task database in association with each project, with each work process of a project including a plurality of processes as a task;
A project including a task corresponding to the project specification information by selecting a task belonging to a project that satisfies the project specification information from a plurality of tasks stored in the task database based on the project specification information transmitted from the terminal. A support program for causing a computer to execute a process for supporting a project by generating a program.

Images