JP2008262542A - Task management device, task management method, and task management program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a task management device, a task management method, and a task management program to enable a user to add and register a task by simple operation in task management to manage a plurality of tasks hierarchical structures. <P>SOLUTION: This task management device 100 which manages the plurality of tasks with the hierarchical structures stored and registered in a storage unit has an input means 21 to input task definition data 31, a task generation means 22 to generate task information 32 from the task definition data 31, a storage means 23 to store the task information 32 into the storage unit 23, and a reception means 41 to receive an instruction to generate a lower-level task from the task information 32, and the task generation means 22 generates the lower-level task information 32 from the task information 32 based on the result of an analysis of the task definition data 31 of the task information 32 in accordance with task definition rules when accepting the lower-level task generation instruction by the reception means 41. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a task management apparatus that manages a plurality of tasks by a hierarchical structure.

  In recent years, projects such as product development have been complicated by being composed of many tasks (work processes) and involving persons in charge from a plurality of departments / departments. It is important for companies to manage and execute such projects efficiently.

  Against this background, a task management system that manages a project as a hierarchy of tasks to be executed is used as a system that supports the management of the project.

  These task management systems are, for example, functions that generate detailed work items unique to a project based on pre-defined and common task configurations and configuration information of development objects (for example, see Patent Document 1). In addition, a function for generating a list of deliverables to be created and corresponding task information based on a process definition that defines a basic process of system development that has been created in advance (see, for example, Patent Document 2) Etc., each function for managing tasks.

As described above, in the conventional task management system, efficient information management is realized by defining information related to the tasks constituting the project in advance and performing centralized management.
JP 2004-110102 A JP 2000-215038 A

  However, the conventional task management disclosed in Patent Documents 1 and 2 assumes a routine work that allows a task to be clearly defined to some extent when planning a project, and determines the overall task configuration at the start of the project. It is a premise to keep.

  For example, in the method disclosed in Patent Document 1, in order to generate detailed work items unique to a project, a common task configuration and development target configuration information must be defined in advance. Further, in the method disclosed in Patent Document 2, in order to generate a list of deliverables to be created and corresponding task information, a process definition that defines a basic process of system development is created in advance. There must be.

  Therefore, in the conventional task management, when the task configuration is changed during the execution of the project, such as an atypical business, it is necessary to partially redefine the task configuration.

  In fact, considering projects that consist of a large number of tasks and involve persons in multiple departments / departments, the proportion of atypical tasks that need to be handled more flexibly than routine tasks is high.

  In such an atypical business, it is difficult to foresee and grasp the entire business, and the task configuration is gradually changed according to the progress of the project. Therefore, the task configuration is changed during the execution of the project.

  Therefore, as in conventional task management, it is not practical to manage a project including an atypical task, because the task configuration of the entire project must first be strictly defined. In addition to task registration (before starting a project), creating a definition relating to a task has a great psychological burden (anxiety about task management) for the task manager.

  In the present invention, in view of the above-mentioned problems of the prior art, in task management for managing a plurality of tasks by a hierarchical structure, a task management device, a task management method, and a task that allow a user to add / register a task by a simple operation The purpose is to provide a management program.

  In order to achieve the above object, a task management device according to the present invention is a task management device that manages a plurality of tasks having a hierarchical structure stored and registered in a storage device, the task describing the task contents. Task definition data input means for inputting definition data, task information generation means for generating task information from the task definition data input by the task definition data input means, and the task information generated by the task information generation means Task information storage means for storing in the storage device, and accepting means for accepting an instruction to generate a lower task from the task information, the task information generating means When the instruction to generate is accepted, the task definition data of the task information should be generated as the lower task Based on the result of analysis according to a predetermined prescribed rules defining the volume, and generating a subordinate task information of the task from the task information.

  As described above, the task management device according to the present invention generates task information of a subordinate task of a registered task from the contents described in the task definition data, adds or registers it, or keeps the contents described in the task definition data as it is. Based on the input task definition data, task information for managing tasks is generated by different generation processes, and the generated task information is stored in the storage device in response to user instructions for adding / registering task information. To do.

  As a result, the task management device includes information that may become a lower-level task in the future, regardless of the phase of the project, in task management for atypical tasks where it is difficult to foresee and grasp the entire business. In this state, it is possible to provide a user with a task management environment in which task contents can be added / registered in a free data format (for example, free text).

  Therefore, the task management device allows the user to add and register tasks flexibly, and can reduce the burden of task definition creation work.

In order to achieve the above object, the task management device of the present invention, the task information generation means extracts the character string indicating the content of the subordinate task from the task definition data and generates the task information before registration, Information for specifying the lower task is added, and task information of the lower task is generated.
In order to achieve the above object, in the task management device of the present invention, the predetermined rule includes information indicating a hierarchical relationship between the lower tasks, and the task information generation unit includes the task information before registration. Are generated, the information indicating the hierarchical position of the lower task is added based on the information indicating the hierarchical structure between the lower tasks, and the task information of the lower task is generated.
In order to achieve the above object, in the task management device according to the present invention, the accepting unit accepts specification of a range in which the lower task is generated in the task definition data, and the task information generating unit is the specified The analysis is performed according to the predetermined rule for the range.

  As described above, the task management device according to the present invention receives the notification that the task information of the subordinate task of the registered task is generated from the contents described in the task definition data, and is added / registered. The definition data is parsed based on a predetermined rule that defines information indicating the content of the lower task and the hierarchical relationship of the lower tasks, and task information of the lower task is generated from the result of the syntax analysis.

  As a result, the task management apparatus can sequentially add and register the lower tasks of the registered tasks whose contents are fixed.

  In order to achieve the above object, a task management method of the present invention is a task management method for managing a plurality of tasks having a hierarchical structure stored and registered in a storage device, wherein the task contents are described. Task definition data input procedure for inputting definition data, task information generation procedure for generating task information from the task definition data input by the task definition data input procedure, and the task information generated by the task information generation procedure Task information storage procedure stored in the storage device, and a reception procedure for receiving an instruction to generate a lower task from the task information, the task information generation procedure, the lower task by the reception procedure When the instruction to generate is accepted, the task definition data of the task information should be generated as the lower task Based on the result of analysis according to a predetermined prescribed rules defining the volume, and generating a subordinate task information of the task from the task information.

  As a result, the task management method of the present invention generates task information of a subordinate task of the registered task from the contents described in the task definition data and adds / registers it, or uses the contents described in the task definition data as it is. In response to a user instruction whether to add or register as information, task information for managing the task is generated by different generation processing based on the input task definition data, and the generated task information is stored in the storage device. In the task management of atypical business where it is difficult to foresee and grasp the entire business, the task including the contents that may become a lower task in the future regardless of the phase of the project It is possible to provide a user with a task management environment in which the contents can be added and registered in a free data format.

  Therefore, the task management method allows the user to add and register tasks flexibly, and can reduce the burden of task definition creation work.

  In order to achieve the above object, a task management program according to the present invention is a task management program for managing a plurality of tasks having a hierarchical structure stored and registered in a storage device, wherein the contents of the task are described. Task definition data input means for inputting the task definition data, task information generation means for generating task information from the task definition data input by the task definition data input means, and generated by the task information generation means The task information is stored in the storage device and registered as a task information storage unit, and an accepting unit that accepts an instruction to generate a subordinate task from the task information. When an instruction to generate a subordinate task is received, the task definition data of the task information is The data, on the basis of the result of analysis according to a predetermined rule which is predetermined to define the contents to be generated as a subordinate tasks, are performed to generate a subordinate task information of the task from the task information.

  As a result, the task management program of the present invention generates the task information of the subordinate task of the registered task from the contents described in the task definition data and adds / registers it, or the contents described in the task definition data The task information for managing the task by different generation processing is generated based on the input task definition data in accordance with the user instruction whether to add / register the task information as it is, and the generated task information is stored in the storage device. In the task management of atypical work where it is difficult to foresee and grasp the entire work, contents that may become a lower-level task in the future regardless of the phase of the project, etc. Provide a user with a task management environment that can add and register task contents in any data format, including Door can be.

  Therefore, the task management program of the present invention can realize a task management function that allows a user to add and register tasks flexibly in a computer and reduce the burden of task definition creation work.

  According to the present invention, a task management device, a task management method, and a task management program that allow a user to add and register a task by a simple operation in task management for managing a plurality of tasks by a hierarchical structure are provided. can do.

  DESCRIPTION OF EMBODIMENTS Hereinafter, preferred embodiments of the present invention (hereinafter referred to as “embodiments”) will be described in detail with reference to the drawings.

  First, the task management device according to the embodiment described below is assumed to be used in the task management in a simple manner, taking user operations at the time of executing an atypical business project as an example. explain.

(Usage example of task management device)
When a task occurs in a project to be executed, the user registers the generated task as a new task via a UI provided by the task management device.

  At this stage, that is, when a new task occurs, the task content is often unclear, and even if the task is actually a collection of subordinate tasks, it is divided into several subordinate tasks. In many cases, it is not possible to determine whether or not each subtask is concretely created and whether it is really appropriate to create it as a subtask.

  Even in such a case, in the present embodiment, contents that may become a lower task in the future can be included in the contents of the new task that is to be registered and registered. Then, as the project progresses, the contents of the previously registered task become clear, or the task is changed and the user registers when the task needs to be broken down into several subtasks. From the completed task, one or more subordinate tasks can be generated from the task based on “content that may become a future subordinate task” included at the time of registration of the task.

  Therefore, the task management apparatus according to the present embodiment has a function of generating task information of a task to be registered from various data input via a user interface (UI: User Interface (hereinafter referred to as “UI”)). And a function of generating task information of a subordinate task of a registered task from various input data in accordance with an instruction from the user.

  As described above, in the task management device according to the present embodiment, in the task management of the atypical business where it is difficult to foresee and grasp the entire business, there is a possibility that it may become a lower-level task in the future regardless of the phase of the project. It provides a user with a task management environment in which task contents such as certain contents can be added and registered in a free data format.

[First Embodiment]
<Hardware configuration of task management device>
First, the hardware configuration of the task management apparatus 100 according to the present embodiment will be described with reference to FIG.

  FIG. 1 is a diagram illustrating an example of a hardware configuration of a task management apparatus 100 according to the first embodiment of the present invention.

  As shown in FIG. 1, the task management device 100 according to the present embodiment includes a control unit 11, a main storage unit 12, an auxiliary storage unit 13, a network I / F 14, an external storage device I / F 15, an external device I / F 16, An output device I / F 17 and an input device I / F 18 are included.

  A control unit (CPU: Central Processing Unit) 11 controls each device included in the task management device 100 according to the present embodiment, such as a main storage unit 12, an auxiliary storage unit 13, and a network I / F 14 described below. . The control unit 11 is a device that executes a program stored in the main storage unit 12. The control unit 11 receives data from the input device or the storage device, calculates and processes the data, and outputs the data to the output device or the storage device ( (For example, display characters entered on the keyboard on the display).

  A main storage unit (ROM: Read Only Memory or RAM: Random Access Memory) 12 is a device for storing (including temporarily holding) a program executed by the control unit 11 and related data. The ROM stores a program executed by the control unit 11 and related data, and the stored program and related data are read (loaded) onto the RAM as necessary by the control unit 11. The read program and related data are calculated and processed by the control unit 11.

  The auxiliary storage unit (HD: Hard Disk) 13 is a device that stores basic software such as an OS (Operating System) and application software together with related data. The auxiliary storage unit 13 stores various information (for example, task information) managed by the task management apparatus 100 according to the present embodiment, and a database (DB: database (hereinafter referred to as “DB”). ) And file system (FS: File System).

  The network I / F 14 includes peripheral devices having a communication function connected via a network such as a LAN (Local Area Network) or a WAN (Wide Area Network) constructed by a data transmission path such as a wired and / or wireless line. It is an interface with the task management apparatus 100 according to the present embodiment.

  The external storage device I / F 15 is an interface between an external storage device (for example, a storage media drive) connected via a data transmission path such as USB (Universal Serial Bus) and the task management device 100 according to the present embodiment. It is.

  The external device I / F 16 is an interface between an external input device (for example, an external HD or a USB memory) connected via a data transmission path such as USB and the task management device 100 according to the present embodiment.

  The task management apparatus 100 according to the present embodiment exchanges various data (transmission / reception and reading / writing) with the outside via these interfaces.

  The output device I / F 17 includes an output device (for example, CRT (Cathode Ray Tube) or LCD (Liquid Crystal Display)) connected via a data transmission line such as a dedicated cable, and the task management device according to the present embodiment. 100 interface.

  The input device I / F 18 is an interface between an input device (for example, a keyboard and a mouse) connected via a data transmission path such as USB and the task management device 100 according to the present embodiment.

  As described above, the task management device 100 according to the present embodiment executes the program stored in the storage device such as the main storage unit (ROM) 12 or the auxiliary storage unit 13 and controls each device to execute the present embodiment. The “task management function” is provided that provides the user with the task management environment described first in describing the form.

<Main function configuration of task management function of task management device>
The main functional configuration of the “task management function” of the task management apparatus 100 according to the present embodiment realized by the hardware configuration described in FIG. 1 will be briefly described.

  The “task management function” of the task management apparatus 100 according to the present embodiment is a task definition data input unit that is a function that provides a UI for a user to input task definition data in which the contents of a task to be registered are described. , A task information generation unit which is a function for generating task information for managing tasks in the task management apparatus 100 from task definition data input via the UI, and the generated task information is stored in the auxiliary storage unit 13 or the like And a task information storage unit which is a function to be stored in the non-volatile storage device.

  As described above, the “task management function” included in the task management apparatus 100 according to the present embodiment reads the program for realizing each functional unit described above onto the main storage unit (RAM) 12, and the control unit 11 By executing, task management for managing a plurality of tasks in a hierarchical structure is realized.

<Means for configuring the main functions of the task management function of the task management device>
Then, each means which comprises the main function of the "task management function" which the task management apparatus 100 which concerns on this embodiment has is demonstrated using FIGS.

  FIG. 2 is a block diagram showing an example of means constituting main functions of the task management apparatus 100 according to the first embodiment of the present invention.

  The “task management function” of the task management apparatus 100 according to the present embodiment is realized by the functions (task definition data input, task information generation, and task information storage functions) of the task management apparatus 100.

  The “task management function” of the task management apparatus 100 according to the present embodiment includes a task definition data input unit 21, a task information generation unit 22, and a task information storage unit 23.

  The task definition data input unit 21 is a unit included in the task definition data input unit, and provides a UI (accepting unit) for a user to input task definition data 31 in which the contents of a task to be registered are described.

  FIG. 3 is a diagram showing an example (part 1) of task definition data input according to the first embodiment of the present invention.

  The task definition data input means 21 displays the input UI 41 as shown in FIG. 3 on an output device such as a display, so that the task definition data 31 can be managed by the user via the input device such as a keyboard or a mouse. An environment for inputting to the apparatus 100 is provided.

  For example, the input UI 41 shown in FIG. 3 includes a “task name” indicating a task name, a “task content” describing the task content, a “person name” indicating a person in charge of executing (implementing) the task, a task Each text box for inputting items such as “completion date” indicating the completion date and “task state” indicating the task status.

  Figure 3 shows a task called "Study on a new schedule management system" where "Mr. Tanaka" is scheduled for a number of tasks that may become future subtasks such as "Technological Survey". This is an example when the schedule to be completed by the 31st "is entered in each text box via an input device such as a keyboard.

  In this way, in the item “task content”, in addition to the task content indicated by “task name”, content that may become a lower-level task in the future can be input.

  The text data (character string data) of each item input in this way becomes the task definition data 31 of the task indicated by “task name”.

  As a result, the task management apparatus 100 according to the present embodiment allows the user to register a task or the like, and contents that may become a lower-level task in the future regardless of the phase of the project. It is possible to provide an environment in which task contents can be defined by a simple method such as text input.

  The task definition data 31 input as described above is displayed as task information by selecting the [Save] button 41b or the [Disassemble lower task] button 41a on the input UI 41 via a pointing device such as a mouse. Registered as

  For example, when the user selects the [Save] button 41b on the input UI 41 via a pointing device such as a mouse, an instruction to generate and register task information of a task to be registered based on the task definition data 31 Accept. Also, when the user selects the [lower task decomposition] button 41 a on the input UI 41, an instruction to generate and register task information of each lower task of the registered task is received based on the task definition data 31. The task registration instruction received in this way is passed to a task information generation unit (a task information generation unit 22 described later).

  Returning to FIG. 2, the task definition data input means 21 transmits the task definition data 31 together with the task information registration instruction received from the input UI 41 to the task information generation means 22 (to be described later). Stored in the main memory (RAM) 12).

  The task information generation unit 22 is a unit included in the task information generation unit, and generates task information of a task to be registered in accordance with a task registration instruction based on the task definition data 31 received from the task definition data input unit 21. .

  Among them, the task information generation means 22 generates task information from the task definition data 31 by different generation processes in accordance with the received task registration instruction. That is, the task information generation process performed by the task information generation unit 22 is performed when the [Save] button 41b of the input UI 41 is selected and when the [Lower task decomposition] button 41a is selected, as described above. And different.

  The task information generation process performed by the task information generation unit 22 will be described below.

<< When the lower task disassembly button is selected >>
The task definition data input means 21 transmits a lower task registration instruction to the task information generation means 22 when the [lower task decomposition] button 41a on the input UI 41 is selected. That is, an instruction to generate task information 32 of the lower task defined in the task definition data 31 is transmitted.

  The task information generating unit 22 performs syntax analysis of the task definition data 31 input by the task definition data input unit 21 in accordance with the received registration instruction of the lower task, and the content of the lower task extracted based on the syntax analysis result is Task information is generated by adding identification information for specifying a lower-level task and information indicating the hierarchical position of the lower-level task in the hierarchical structure (hereinafter referred to as “hierarchical structure information”) to the described character string data. .

  The task information generation means 22 adds means (information extraction means) for extracting character string data indicating the contents of the lower task from the task definition data 31 based on a predetermined rule, and adds identification information and hierarchical structure information of the lower task. Means (information adding means).

  The task information generation means 22 first parses the task definition data 31 based on a predetermined rule when defining the contents of the lower task (here, “syntactic analysis” refers to a sentence including a character string). Means analysis of the configuration).

  FIG. 4 is a diagram showing an example of task content data and task definition rules in the task definition data 31 according to the first embodiment of the present invention.

  In the task definition data 31, information indicating the contents of the lower tasks and the hierarchical relationship between the lower tasks is defined according to a predetermined rule as shown in the “task definition rule” in FIG. For example, as shown in FIG. 4, the user inputs the contents of the lower tasks and the information indicating the hierarchical relationship between the lower tasks based on the task definition rules from the input UI 41 shown in FIG. Each piece of information is defined.

  As is clear from FIG. 4, the task definition rule defines not only the task content itself but also a rule that when extracting a lower task from the task definition data 31, it should be extracted by regarding that portion as a lower task. It can be said that the template defines the text structure and the character string format. This task definition rule is stored in advance in the auxiliary storage unit 13 by the user or the administrator of this system. The task information generation unit 22 reads the task definition rule from the auxiliary storage unit 13 onto the main storage unit (RAM) 12, and then parses the task definition data 31 based on the read task definition rule.

The example of “task definition rule” shown in FIG. 4 (lower) shows the following rule.
[Task definition rules]
(1) The contents of the lower task (1-A) are expressed by a character string 51a shown below starting from the character “■” whose head is determined.
■ Task name (person in charge: Name, completion date: Date)
(1-B) One task is expressed by a line feed of the character string 51a.
(1-C) The character string 51a is composed of a character string 51c including only “task name”,
It may be 51d.
(1-D) “■” is not used in the character string 51b so that it can be determined that it is a comment sentence explaining a lower task.
(2) Hierarchical relationship between lower tasks (2-A) A hierarchical structure between lower tasks is expressed by regular indentation by a space (in FIG. 4, a space is indicated by “→”).

  For example, when the task content data in the task definition data 31 in FIG. 4 (upper row) is parsed based on the task definition rule shown in FIG. 4 (lower row), the content of the lower task possessed by the task information generating means 22 is shown. The means for extracting the character string data is the above (1-A) with respect to the character string 51a that is positioned at the first line and until the line feed is “■ Technical survey (person in charge: Yamada, completion date: September 30)”. ) And (1-B), based on the task definition rules, "Technical Survey" for "Task Name", "Yamada" for "Person Name", and "September 30" for "Completion Date" Extract column data. As a result, it is possible to extract character string data indicating the contents of a task called “technical survey”, which is a task name “Technical Survey” that “Mr. Yamada” plans to work by “September 30”. The task of “technical investigation” is explained based on the task definition rule (1-D) above for the character string 51b “ZZZ of the new schedule management system in detail” on the next line. Character string data that is a comment sentence can be extracted.

  The means for extracting the character string data indicating the contents of the subordinate task possessed by the task information generating means 22 is the character string 51c that says “■ Survey of existing system” and the characters that say “■ AAA system” and “■ BBB system”. For the column 51d, based on the task definition rules (1-A) to (1-C) above, the “task name” “existing system check”, “AAA system”, and “BBB system” character strings, respectively. As a result, it is possible to extract character string data indicating task contents such as task names “existing system”, “AAA system,” “BBB system”.

  Returning to FIG. 2, the task information generating means 22 holds character string data indicating the contents of the extracted lower task on the main storage unit (RAM) 12. At this stage, the task information generating unit 22 extracts character string data extracted by the above method, “task name”, “person name”, “completion date”, “task state”, and the like input from the input UI 41. Each piece of data constituting the task information such as the data of each item is stored, and task information before registration is generated on the main storage unit (RAM) 12.

  Further, the task information generating unit 22 adds identification information for specifying a lower task to the task information before registration generated on the main storage unit (RAM) 12 (for example, a task number issued when a task is added). .) Is added. Further, the task information generation means 22 parses the task definition data 31 based on a task definition rule that defines information indicating a hierarchical relationship between lower tasks as shown in FIG. When task information is generated and it is determined that a hierarchical relationship exists between each lower task, the hierarchical structure information of the lower task is added (for example, the task of another task corresponding to the parent of the generated lower task) Add a number, etc.).

  First, a method for adding identification information for specifying a lower task by the task information generating means 22 will be described.

  For example, when the task content data in the task definition data 31 in FIG. 4 (upper row) is parsed based on the task definition rule shown in FIG. 4 (lower row), the identification information of the lower task possessed by the task information generating means 22 is obtained. The adding means adds task numbers to the pre-registration task information generated on the main storage unit (RAM) 12 in the order of extraction. At this time, the task number to be added is the number next to the task number assigned to the last lower task extracted by parsing the task definition data 31 last time.

  The means for adding the identification information of the lower task is that the task definition data 31 is parsed last time, and if the task number assigned to the last extracted lower task is “1”, it is extracted first by the current syntax analysis. The task number “2” is added as identification information to the task information of the task called “technical survey”. Also, the task name “3” is added to the task information of the task named “Investigation of existing system” and the task name “4” is added to the task information of the task named “AAA system” and the task name is “BBB”. Task number “5” is added as identification information to the task information of the task “system”. Then, the last task number “5” is stored in a nonvolatile storage device such as the auxiliary storage unit 13. Accordingly, the task number to be added to the lower task extracted first by parsing the task definition data 31 next time is “6”.

  Next, a method for adding hierarchical structure information by the task information generation means 22 will be described.

  For example, when the task content data in the task definition data 31 in FIG. 4 (upper row) is parsed based on the task definition rules shown in FIG. 4 (lower row), the hierarchical structure information possessed by the task information generating means 22 is added. The means is analyzed based on the task definition rule of (2-A) above, and a task corresponding to a parent to a certain lower task is generated based on the information indicating the hierarchical relationship between the extracted and generated lower tasks. It is determined whether or not the subordinate task exists, and if it is determined that the parent task exists, the identification information of the parent task is added as the hierarchical structure information of the subordinate task.

  Since there is no space at the beginning of the character string 51a, the means for adding the hierarchical structure information includes the task name “technical survey” first extracted by parsing among the plurality of subordinate tasks defined in the task definition data 31. It is determined that there is no parent task for the task to be called, and the task name of the task name “Technical Survey” is the task name “Technical Survey” with the task name “Study New Schedule Management System” as the registered task. Append to Also, since there is one space at the beginning of the character string 51c and it is indented, it is determined that there is a task that is the parent for the task that is the next extracted task name "existing system check". The task number “2” of the task with the task name “technical survey” is added to the task information of the task with the task name “existing existing system”. In addition, since there are two spaces at the beginning of the character string 51c and it is indented, it is determined that there is a parent task for each of the extracted task names "AAA system" and "BBB system". Then, the task number '3' of the lower task called the task name “existing system check” corresponding to the parent is added to the task information of each task called the task names “AAA system” and “BBB system”.

  Returning to FIG. 2, at this stage, the task information generation means 22 is registered with identification information data (eg, task number) and hierarchical structure information data (eg, task number of the parent task). The previous task information is held on the main storage unit (RAM) 12.

  FIG. 5 is a diagram showing an example of the data structure of the task information 32 according to the first embodiment of the present invention.

  The task information generation unit 22 generates the task information 32 as shown in FIG. 5 by the method described above, and transmits the generated task information 32 to the task information storage unit 23 described later (the generated task Information 32 is passed to the task information storage unit).

  As a result, the task management apparatus 100 according to the present embodiment registers the information based on the information indicating the contents of the lower tasks included in the task definition data 31 in which the contents of the registered tasks are described and the hierarchical relationship between the lower tasks. Task information 32 of subordinate tasks of completed tasks can be generated and registered together.

<< Task information generation process when save button is selected >>
Next, task information generation processing by the task information generation unit 22 when the [Save] button 41b is selected will be described. Further, in the following description, a difference from the generation process when the “decompose lower task” button 41a described above is selected will be described.

  When the “save” button 41 b on the input UI 41 is selected, the task definition data input unit 21 transmits a task registration instruction to the task information generation unit 22. In other words, the task definition data 31 is transmitted as an instruction to generate task information 32 as a part of “task contents” of the task to be registered.

  The task information generation unit 22 generates task information 32 of a task to be registered from the task definition data 31 in accordance with the received task registration instruction. At this time, unlike the case where the [lower task decomposition] button 41a is selected, the task information generating means 22 does not change the lower task even if the task definition data 31 describes contents that may be lower tasks. The task information 32 is generated as part of the “task contents” of the task to be registered without generating the task information 32.

  As described above, in the task management device 100 according to the present embodiment, when the [disassemble lower task] button 41a is selected, the task information generation unit 22 performs a lower order from the content of the lower task defined in the task definition data 31. When the task information 32 of the task is generated and the [Save] button 41b is selected, the task information 32 of the task to be registered including the contents of the lower task is generated.

  Returning to FIG. 2, the task information storage unit 23 is a unit included in the task information storage unit, and stores the task information 32 generated by the task information generation unit 22 in a nonvolatile storage device such as the auxiliary storage unit 13. To do.

  The task information storage unit 23 stores data of each item included in the task information 32 in a predetermined area in a nonvolatile storage device such as the auxiliary storage unit 13. The “predetermined area” referred to here is, for example, “task number (identification information)”, “task name”, “task content”, “name of person in charge” that constitutes data in a table format as shown in FIG. , “Completion date”, “task state”, and “parent task number (hierarchical structure information)”.

  As described above, the task management apparatus 100 according to the present embodiment uses the above-described “task management function” to determine in what phase the project is in the task management of the atypical business where it is difficult to foresee and grasp the entire business. Even if there are, it is possible to manage multiple tasks in a hierarchical structure by providing users with a task management environment that can add and register task contents in a free data format, such as contents that may become subordinate tasks in the future. In task management, users can flexibly register tasks with simple operations without feeling burden of task definition creation work even when the task configuration changes according to the progress of the project in atypical work. Is realized.

<About task management operations in the task management device>
A user operation example of task management assumed by the task management apparatus 100 according to the present embodiment that has been briefly described before the description of the present embodiment will be described with reference to FIGS. In the following explanation, when a new task is registered, the task is registered without confirming the content of the task, and the content that may become a lower-level task for the registered task in the future as the project progresses As an example, a user operation of registering a subordinate task when the contents of the registered task (subordinate task contents) are confirmed is registered / edited as the contents of the registered task.

<< Operation Example (Part 1) >>
In the operation example (part 1), an operation example of task management in “when the user registers a new task” is described.

  FIG. 6 is a diagram showing an example (part 1) of the task management operation (input of the task definition data 31) according to the first embodiment of the present invention. FIG. 7 is a diagram showing an example (part 1) of the task information 32 generated after the input according to the first embodiment of the present invention. FIG. 8 is a diagram showing an example (part 1) of the task management operation (viewing the task information 32) according to the first embodiment of the present invention.

  As shown in FIG. 6, the task management apparatus 100 according to the present embodiment provides an input UI 41 to the user by the task definition data input unit 21.

  As shown in FIG. 6, when the user inputs the content of a new task in the “task content” item, the user selects the [Save] button 41b. In this example, since the content of the task to be newly registered has not yet been confirmed, only the comment text explaining the content of the task to be registered is entered in the text box in the “task content” item. ing. Further, at this time, it is not necessary to input all the input items including “task contents”, and the user only has to input contents that are known to some extent.

  As described above, when the [Save] button 41b is selected by the user, the task management device 100 is based on the task definition data 31 held on the main storage unit (RAM) 12 by the task information generation unit 22. For example, task information 32 as shown in FIG. 7 is generated. At this time, the task management apparatus 100 adds task identification information (for example, task number “1” in FIG. 7) to the task information 32 before registration by the task information generation unit 22. That is, identification information of a task number assigned when registering a new task is added.

  Next, the task management device 100 stores the task information 32 generated by the task information storage unit 23 in a predetermined area in a nonvolatile storage device such as the auxiliary storage unit 13, and the task information 32 of the new task. Register.

  Thereafter, the user browses the task information 32 of the registered task through the browsing UI 61 as shown in FIG. 8 provided by the task management apparatus 100.

  As a result, the user confirms the content of the task information 32 of the new task registered as described above, for example, via the browsing UI 61 and, if necessary, the [edit] button on the browsing UI 61 By selecting 61a, the task information 32 of the registered task can be updated.

<< Operation example (2) >>
In the operation example (No. 2), an example of task management operation “when the user edits the contents of a registered task and registers it again according to the progress of the project” will be described.

  FIG. 9 is a diagram showing an example (part 2) of the task management operation (input of the task definition data 31) according to the first embodiment of the present invention. FIG. 10 is a diagram showing an example (part 2) of the task information 32 generated after the input according to the first embodiment of the present invention. FIG. 11 is a diagram showing an example (part 2) of the task management operation (viewing the task information 32) according to the first embodiment of the present invention.

  In an atypical business, it is difficult to foresee and grasp the entire business, and the task content is gradually determined according to the progress of the project, so the task configuration is changed during the execution of the project.

  In such a case, the user browses the registered task via the browsing UI 61 shown in FIG. 8, and the task needs to be changed in the content (in the example of FIG. 8, the task name “examination of new schedule management system”). Is selected, the [Edit] button 61a is selected, and the contents of the task information 32 are changed. As shown in FIG. 9, the user inputs a rough task configuration plan as an informal draft in the “task contents” field of the input UI 41, and clicks the [Save] button 41 b on the input UI 41. By selecting, as shown in FIG. 10, contents that may become a lower-level task in the future with respect to the registered task are registered as part of the “task contents” in the task information 32 of the registered task. I can keep it.

  As described above, when the [Save] button 41b is selected by the user, the task management device 100 is based on the task definition data 31 held on the main storage unit (RAM) 12 by the task information generation unit 22. For example, the task information 32 having the data structure shown in FIG. 10 is generated, and the generated task information 32 is stored in a non-volatile storage device such as the auxiliary storage unit 13 by the task information storage unit 23 and registered. The task information 32 of the completed task is updated.

  Thereafter, as shown in FIG. 11, the user can view the updated task information 32, check the contents of the task information 32 according to the progress of the project, and the task contents (contents of the lower tasks) Gradually).

<< Operation Example (Part 3) >>
The operation example (No. 3) will be described with reference to an example of task management “when a user registers a lower task when the content of a registered task (the content of a lower task) is confirmed”.

  FIG. 12 is a diagram illustrating an example (part 2) of the task management operation (decomposition into lower tasks) according to the first embodiment of the present invention. FIG. 13 is a diagram showing an example (part 2) of the task information 32 generated after the decomposition according to the first embodiment of the present invention. FIG. 14 is a diagram showing an example (part 2) of the task management operation (viewing the task information 32) according to the first embodiment of the present invention.

  For example, in a task with a registered task name “examination of a new schedule management system”, when a project progresses and the content of a subordinate task is confirmed, first, the user clicks an “edit” button 61 a on the browsing UI 61. Select and move from the browsing UI 61 to the input UI 41 shown in FIG.

  After the user moves to the input UI 41, the user defines the character string data indicating the content to be decomposed as the lower task input in the “task content” item, that is, the range in which the lower task after the definition is defined as the task definition data 31 is selected (in FIG. 12, the black / white inverted area indicates the selected range).

  The user selects a range in which the lower-level task is defined and then selects the [lower-level task disassembly] button 41a on the input UI 41, thereby defining the contents defined in the task definition data 31 selected in the range. Can be registered as a subordinate task of the task with the task name “Examination of new schedule management system”.

  As described above, when the “disassemble lower task” button 41 a is selected by the user, the task management apparatus 100 defines the contents of the lower task and information indicating the hierarchical relationship between the lower tasks by the task information generation unit 22. The task definition data 31 is parsed based on the current task definition rule.

  As a result, the task management apparatus 100 uses the task information generation means 22 to generate character string data indicating the contents of the lower-level task based on the syntax analysis result (in FIG. 12, the task name “technical survey” and other tasks 10 Task information) is extracted, and task information 32 of the lower task is generated.

  Further, the task management device 100 adds the identification information of the lower task to the generated task information 32 based on the result of the syntax analysis by the task information generation unit 22 and determines whether there is a parent task in the lower task. Judgment is made (whether there is a hierarchical relationship between lower tasks), and if there is a task corresponding to the parent, the hierarchical structure information is added to the extracted data.

  Next, the task management apparatus 100 stores the generated task information 32 of the lower-level task in a nonvolatile storage device such as the auxiliary storage unit 13 by the task information storage unit 23, and stores the lower-level task group (" The task information 32 of the task number (identification number) “2” to “11” added task group) is registered.

  Thereafter, the user browses the task information 32 of the registered subordinate tasks via the browsing UI 61 as shown in FIG. 14 provided by the task management apparatus 100.

  As a result, the user can confirm the contents of the subordinate tasks after registration and the hierarchical structure between the subordinate tasks by selecting the [hierarchy display ▽] button 61b on the browsing UI 61.

  As described above, the task management apparatus 100 according to the present embodiment is difficult to foresee and grasp the entire business, and takes into account the atypical business composed of tasks gradually as the project progresses. The user can flexibly register a task by a simple operation without feeling the burden of task definition creation work.

<Processing procedure of “task management function” in the task management device>
A specific processing procedure of the “task management function” of the task management apparatus 100 according to the present embodiment described so far will be described.

  FIG. 15 is a flowchart illustrating an example of a basic processing procedure for task management according to the first embodiment of the present invention.

  The task management apparatus 100 according to the present embodiment reads, for example, a task management program that performs processing of a “task management function” stored in the auxiliary storage unit 13 onto the main storage unit (RAM) 12 and executes it by the control unit 11. To do. At this time, the following processing procedures (S101 to S104) are executed.

  In the task management apparatus 100 according to the present embodiment, the task definition data 31 describing the contents of the task to be registered is input to a text box on the input UI 41 (S101).

  The task management apparatus 100 determines whether one of the [lower task disassembly] button 41a or the [save] button 41b on the input UI 41 is selected (S102), and until either button is selected. , And wait for data input (when S102 is NO).

  When either button is selected (when S102 is YES), the task management apparatus 100 uses the task definition data input means 21 together with the task registration instruction received when the button is selected, together with the main storage unit ( The task definition data 31 is passed to the task information generation process (task information generation means 22) via the (RAM) 12. That is, the task management apparatus 100 holds the task definition data 31 on the main storage unit (RAM) 12 when the processing procedure of S102 is completed.

  Next, the task management apparatus 100 performs a task information generation process for generating the task information 32 based on the task definition data 31 by the task information generation unit 22 (S103). A specific processing procedure of the task information generation processing will be described with reference to FIG.

  The task management device 100 stores the task information 32 generated by the task information generation process by the task information storage unit 23 in a nonvolatile storage device such as the auxiliary storage unit 13 (S104).

<Processing procedure of task information generation processing in task management device>
Of the processing procedures of the “task management function” of the task management apparatus 100 according to the present embodiment, a specific processing procedure of task information generation processing for generating task information 32 from the task definition data 31 will be described.

  FIG. 16 is a flowchart illustrating an example of a processing procedure of task information generation processing according to the first embodiment of the present invention. Also, the task information generation process shown in FIG. 16 is a processing procedure performed in S103 of FIG.

  When the [Save] button 41b on the input UI 41 is selected in the processing procedure of S102 (when S1031 is NO), the task management apparatus 100 according to the present embodiment uses the task information generation unit 22 to register a task. In accordance with the instruction, the task definition data input means 21 generates task information 32 of the task to be registered based on the task definition data 31 held on the main storage unit (RAM) 12. The task information generation unit 22 holds the generated task information 32 on the main storage unit (RAM) 12 (S1032).

  In addition, in the processing procedure of S102, the task management device 100 inputs task definition data by the task information generation unit 22 when the [lower task disassembly] button 41a on the input UI 41 is selected (when S1031 is YES). The means 21 performs syntax analysis of the task definition data 31 held on the main storage unit (RAM) 12. At this time, the task information generation unit 22 reads out task definition rules that define the contents of the subordinate tasks from the auxiliary storage unit 13 onto the main storage unit (RAM) 12, and based on the read task definition rules, the task definition data 31 is read out. Is parsed.

  First, the task management apparatus 100 reads the task definition data 31 held on the main storage unit (RAM) 12 (S1033). At this time, in the case of the first data reading, the task management apparatus 100 reads a character string from the beginning of the data to a line feed code (for example, CR or LF). In addition, in the case of reading data for the second time and thereafter, the task management apparatus 100 reads a character string from the data destination after the line feed to the next line feed code.

  When the task management device 100 reads the task definition data 31, for example, it determines whether or not there is data (character string) to be read next based on the end code (EOF) of the file in the data ( S1034) When there is no data to be read (when S1034 is NO), the task information generation process is terminated, assuming that the parsing of the task definition data 31 is completed.

  When there is data to be read (when S1034 is YES), the task management apparatus 100 determines the contents of the lower task that is the object of parsing and the hierarchical relationship between the lower tasks for the read data, that is, the character string. Parsing is performed based on the task definition rule that defines the information to be indicated (S1035).

  Based on the result of analyzing a character code from the beginning of the character string (for example, indentation such as a space), the task management apparatus 100 is information indicating a hierarchical relationship between lower tasks (for example, information indicating a hierarchical position). Etc.). Further, the task management apparatus 100, based on the result of analyzing a character string pattern (for example, “■ task name (person in charge: Name, completion date: Date)”, etc.), a character string indicating the contents of the lower task. Data is extracted (S1036). The extracted character string data is held on the main storage unit (RAM) 12 as task information 32 of the lower task before registration together with other various data.

  The task management device 100 adds a task number, which is identification information for identifying the lower task, to the generated task information 32 of the lower task before registration (S1037).

  The task management apparatus 100 holds the task number added by the processing procedure of S1037 on the main storage unit (RAM) 12 as the last added task number (holds the last added task number at the present time) ( S1038).

  The task management apparatus 100 determines whether or not the lower task is the highest task in the hierarchical structure between the lower tasks based on the information indicating the hierarchical relationship between the lower tasks obtained by performing the syntax analysis. (S1039).

  Only when the lower task is not the highest task (when S1039 is NO), the task management apparatus 100 assigns the highest task number among the tasks (parent tasks) located one level higher than the lower task. Then, it is added to the generated task information 32 of the lower task before registration as hierarchical structure information of the lower task (S1040).

  As a result, the task management apparatus 100 holds the task information 32 of the lower task before registration, to which the lower task identification information and the hierarchical structure information are added, on the main storage unit (RAM) 12 (S1041).

  The task management apparatus 100 repeats the processing procedure from S1033 to S1041 that has been described so far until there is no data to be read from the task definition data 31 (object of syntax analysis) (the processing procedure proceeds from S1041 to S1033).

  As described above, the task management apparatus 100 according to the present embodiment inputs the task definition data 31 in which the contents of the lower-level task are described according to the task definition rule by the processing procedure illustrated in FIGS. 15 and 16, and the input task A processing procedure is realized in which task information 32 is generated by adding identification information and hierarchical structure information of the lower task to the task information 32 of the lower task generated based on the syntax analysis result of the definition data 31.

<Summary>
As described above, according to the first embodiment of the present invention, the task management device 100 according to the present embodiment generates or registers the task information 32 of the lower task from the input task definition data 31. In response to the user instruction, the task definition data 31 is used to generate task information 32 for managing the task by different generation processes, and the generated task information 32 is stored in the storage device.

  Further, the task management device 100 according to the present embodiment determines the task definition data of the registered task information when the information of the indeterminate lower task is confirmed and an instruction to generate the lower task is received from the user. 31 is parsed based on a predetermined rule that defines information related to the lower tasks and information indicating the hierarchical relationship of the lower tasks, and based on the analysis result, information related to the lower tasks extracted from the registered task information. Then, the task information 32 of the lower task to which information related to the hierarchical structure is added is generated.

  As a result, the task management apparatus 100 registers, for example, one task including its contents even if the task to be registered is expected to be divided into a plurality of lower tasks in the future. The task information 32 of the confirmed lower task can be generated from the registered task information 32 at a timing when the information of the lower task that has been uncertain is confirmed at a later date, and the lower tasks can be registered in a batch.

  As described above, the task management apparatus 100 according to the present embodiment is difficult to foresee and grasp the entire business in the task management that manages a plurality of tasks by a hierarchical structure, and the tasks are gradually configured according to the progress of the project. In consideration of atypical tasks, the user can flexibly register tasks by simple operations without feeling the burden of task definition creation work even during the execution of the project.

  So far, the present invention has been described based on the above embodiment, but the “task management function” of the task management apparatus 100 according to the present embodiment uses each processing procedure described in the embodiment as an operating environment ( It can be realized by running a program coded in a programming language suitable for the platform. Therefore, the program (task management program) for executing the “task management function” of the task management apparatus 100 according to the present embodiment can be stored in a computer-readable recording medium.

  FIG. 17 is a diagram illustrating an example of task definition data input according to a modification of the first embodiment of the present invention.

  The task definition rule described in the above embodiment is an example of a rule that defines the content of the lower task and information indicating the hierarchical relationship between the lower tasks in the task definition data 31. Is not limited. For example, according to the rule based on the paragraph number as shown in FIG. 17, the contents of the lower tasks and the information indicating the hierarchical relationship between the lower tasks may be defined as long as the rules can be analyzed by the task information generating unit 22.

  FIG. 18 is a diagram illustrating an example of the generated task information 32 according to the modification of the first embodiment of the present invention.

  In the task management apparatus 100 according to the modification, when task definition data 31 according to a rule as shown in FIG. 17 is input, task information 32 as shown in FIG.

  The “input method of the task definition data 31 via the input UI 41” described in the above embodiment is an example of the task definition data input means 21 for inputting the task definition data 31, and its data input The present invention is not limited to the method.

  For example, the task definition data input unit 21 according to the present embodiment may input the task definition data 31 to the task management apparatus 100 by the following data input method.

  A task definition file that defines the contents of subordinate tasks in units and information indicating the hierarchical relationship between subordinate tasks according to the task definition rules, such as a task group that a user wants to add as a subordinate task of a registered task Are created in advance, and the created task definition file is stored in a non-volatile storage device such as the auxiliary storage unit 13. As a result, the task definition data input means 21 stores the stored task definition file in a nonvolatile storage device such as the auxiliary storage unit 13 based on the file name specified when registration or addition becomes necessary. And the task definition data 31 is input by reading the data of the corresponding task definition file.

  FIG. 19 is a diagram illustrating an example of a task management system according to a modification of the first embodiment of the present invention.

  In FIG. 19, for example, the user can easily perform the task based on the “task procedure manual” in which the contents of the lower tasks and the information indicating the hierarchical relationship between the lower tasks are described according to a predetermined rule such as memo writing during work. 1 shows an example of a task management system that can register a task by operation.

  The task management system shown in FIG. 19 has a task management apparatus 100 (for example, an image forming apparatus such as a copying machine) having a scanner function for reading a document (task procedure manual), and a DB function for storing task information 32. The server 200 is a system connected to the network 90.

  In the task management system according to the modified example, first, the “task procedure manual” in which the contents of the lower tasks and the information indicating the hierarchical relationship between the lower tasks is described is read by the scanner function of the task management device 100 and read. A text task definition file is automatically generated from image data using OCR (Optical Character Reader) function.

  Next, in the task management system, the task management apparatus 100 reads data from the task definition file, generates task information 32 based on the syntax analysis result, and generates the generated task information 32 via the network 90 on the server 200. Send to.

  As a result, in the task management system, the task information 32 transmitted from the task management apparatus 100 is stored in a predetermined area of the DB function that the server 200 has.

  As described above, in the task management system according to the modified example, the user can register the contents of the lower tasks described on a paper medium such as memos and the information indicating the hierarchical relationship between the lower tasks by a simple operation. It can be performed.

  Finally, the present invention is not limited to the requirements shown here, such as combinations of other elements with the shapes listed in the above embodiments. With respect to these points, the present invention can be changed within a range that does not detract from the gist of the present invention, and can be appropriately determined according to the application form.

It is a figure which shows an example of the hardware constitutions of the task management apparatus which concerns on the 1st Embodiment of this invention. It is a block diagram which shows an example of the means which comprises the main functions which the task management apparatus which concerns on the 1st Embodiment of this invention has. It is a figure which shows an example (the 1) of task definition data input which concerns on the 1st Embodiment of this invention. It is a figure which shows an example of the task content data in the task definition data which concern on the 1st Embodiment of this invention, and a task definition rule. It is a figure which shows an example of the data structure of the task information which concerns on the 1st Embodiment of this invention. It is a figure which shows an example (the 1) of task management operation (input of task definition data) which concerns on the 1st Embodiment of this invention. It is a figure which shows an example (the 1) of the task information produced | generated after the input which concerns on the 1st Embodiment of this invention. It is a figure which shows an example (the 1) of task management operation (browsing of task information) which concerns on the 1st Embodiment of this invention. It is a figure which shows an example (the 2) of task management operation (input of task definition data) which concerns on the 1st Embodiment of this invention. It is a figure which shows an example (the 2) of the task information produced | generated after the input which concerns on the 1st Embodiment of this invention. It is a figure which shows an example (the 2) of task management operation (browsing of task information) which concerns on the 1st Embodiment of this invention. It is a figure which shows an example (the 2) of task management operation (it decomposes | disassembles into a low-order task) which concerns on the 1st Embodiment of this invention. It is a figure which shows an example (the 2) of the task information produced | generated after the decomposition | disassembly which concerns on the 1st Embodiment of this invention. It is a figure which shows an example (the 2) of task management operation (browsing of task information) which concerns on the 1st Embodiment of this invention. It is a flowchart which shows an example of the basic processing procedure of the task management which concerns on the 1st Embodiment of this invention. It is a flowchart which shows an example of the process sequence of the task information generation process which concerns on the 1st Embodiment of this invention. It is a figure which shows an example of the task definition data input which concerns on the modification of the 1st Embodiment of this invention. It is a figure which shows an example of the produced | generated task information which concerns on the modification of the 1st Embodiment of this invention. It is a figure which shows an example of the task management system which concerns on the modification of the 1st Embodiment of this invention.

Explanation of symbols

11 Control unit (CPU)
12 Main memory (ROM, RAM)
13 Auxiliary memory (HD)
14 Network I / F
15 External storage device I / F
16 External device I / F
17 Output device I / F
18 Input device I / F
21 Task definition data input means 22 Task information generation means 23 Task information storage means 31 Task definition data 32 Task information 41 Input UI
41a Subordinate task decomposition button 41b Save button 51a Character string (Part 1)
51b Character string (Part 2)
51c string (part 3)
51d string (part 4)
61 UI for browsing
61a Edit button 90 Network 100 Task management device (information processing device)
200 servers (task information storage location by remote access: information processing device)

Claims (6)

A task management device for managing a plurality of tasks having a hierarchical structure stored and registered in a storage device,
Task definition data input means for inputting task definition data in which the contents of the task are described;
Task information generating means for generating task information from the task definition data input by the task definition data input means;
Task information storage means for storing the task information generated by the task information generation means in the storage device;
Receiving means for receiving an instruction to generate a lower-order task from the task information,
The task information generating means includes
When an instruction to generate the lower task is received by the receiving means,
Generating lower task information of the task from the task information based on a result of analyzing the task definition data of the task information according to a predetermined rule that defines contents to be generated as the lower task A task management device characterized by the above. The task information generating means includes
Adding information for identifying the lower task to the task information before registration generated by extracting a character string indicating the content of the lower task from the task definition data, and generating task information of the lower task. The task management device according to claim 1, wherein: The predetermined rule has information indicating a hierarchical relationship between the lower tasks,
The task information generating means includes
When a plurality of task information before registration is generated,
3. The task management apparatus according to claim 2, wherein information indicating a hierarchical position of the lower task is added based on information indicating a hierarchical structure between the lower tasks, and task information of the lower task is generated. The accepting means accepts designation of a range for generating the lower task in the task definition data,
The task information generating means includes
4. The task management apparatus according to claim 1, wherein an analysis according to the predetermined rule is performed on the specified range. 5. A task management method for managing a plurality of tasks having a hierarchical structure stored and registered in a storage device,
A task definition data input procedure for inputting task definition data in which the contents of the task are described;
A task information generation procedure for generating task information from the task definition data input by the task definition data input procedure;
A task information storage procedure for storing the task information generated by the task information generation procedure in the storage device;
An acceptance procedure for accepting an instruction to generate a subordinate task from the task information,
The task information generation procedure includes:
When an instruction to generate the subordinate task is received by the reception procedure,
Generating lower task information of the task from the task information based on a result of analyzing the task definition data of the task information according to a predetermined rule that defines contents to be generated as the lower task A task management method characterized by: A task management program for managing a plurality of tasks having a hierarchical structure stored and registered in a storage device,
Computer
Task definition data input means for inputting task definition data in which the contents of the task are described;
Task information generating means for generating task information from the task definition data input by the task definition data input means;
Task information storage means for storing and registering the task information generated by the task information generation means in the storage device;
Function as an accepting means for accepting an instruction to generate a subordinate task from the task information;
The task information generating means is
When an instruction to generate the lower task is received by the receiving means,
Based on the result of analyzing the task definition data of the task information according to a predetermined rule that defines the contents to be generated as the subordinate task, subordinate task information of the task is generated from the task information. Task management program to be executed in the future.

Images