JP2011248590A - Task design support system and task design support method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To facilitate evaluation of consistency of an interface between tasks configuring system software.SOLUTION: Each piece of ID of an input condition and an output condition of a designed task is defined in a task definition table, pieces of ID of information respectively corresponding to input condition ID and output condition ID are defined in a task input condition table and a task output information table respectively, a content of information corresponding to information ID is defined in an input/output information table, and the respective tables are stored in a task database 11, an input condition database 13, an output information database 15, and an input/output information database 17 respectively. Whether other task having information being an input condition or output information for a task as the output information or the input condition exists or not can be verified based on the information ID defined in the task database 11, the input condition database 13, and the output information database 15.

Description

  The present invention relates to a system and method for supporting design of tasks constituting system software.

  In rocket development projects, development of system software for guiding and controlling rockets is indispensable. This system software has an operation system (OS) and a guidance control related module, and these system softwares are mounted on a dedicated guidance control computer that satisfies environmental conditions unique to the aerospace field.

  The system software related to the guidance control is developed uniquely (individually) by dividing into modules (CSU) units by a programmer who is familiar with the specifications and characteristics of the guidance control computer. Each developed module is assembled into a module group (CSC) and further software (CSCI) while manually verifying and verifying the interface between the modules. In such system software, whether the interface between modules, in other words, between tasks is consistent or not is very important in each design, analysis, and verification work.

  As described above, since the system software related to guidance control is uniquely developed for each module, there are very many interface data, commands, etc. for linking between modules. Moreover, this type of system software has a complicated algorithm to meet the demand for high performance and high performance. Such a situation is a cause of the enormous amount of time required for the design that satisfies the consistency of the interface between the modules and the analysis and verification of the validity of the design contents. Therefore, this type of system software requires enormous development costs.

  From the viewpoint of evaluating the interface consistency between the modules described above, no useful technique is found in the conventional proposal. Conventionally known proposals include, for example, software that triggers software to be activated in response to an event occurring in hardware (for example, Patent Document 1), or processing time of a task with high priority. There is a degree (for example, Patent Document 2) that determines a delay allowable time of a task having a low priority based on the priority.

JP 2007-253792 A JP 2000-56989 A

  Due to the circumstances described above, the system software related to rocket guidance and control, which is completed through design, analysis, and verification to ensure the consistency of the interface between modules, is highly specific. .

  On the other hand, when the rocket development project (unit unit or series unit) changes, the content of rocket guidance control also changes. Therefore, system software related to rocket guidance control is basically developed for each rocket development project (unit or series).

  For this reason, when trying to divert highly dedicated system software developed in another development project to another project, it is designed so that the consistency of the interface between modules is guaranteed even if the content of guidance control changes. A large-scale revalidation of the content is required. This is an obstacle to diverting this type of system software to other projects, and is a factor for reducing the system software market size.

  Therefore, it is difficult for rocket guidance control related system software to collect a lot of evaluation data during operation and feed it back to the improvement of the system software. Under such circumstances, it is very difficult to improve the sophistication of system software from the viewpoint of general versatility.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a task design support system and a task design support method capable of facilitating evaluation of interface consistency between tasks constituting system software. There is to do.

In order to achieve the above object, the task design support system of the present invention described in claim 1 includes:
A system that supports the design of tasks that make up system software,
An input condition database in which a task input condition table that defines input conditions necessary for task execution is stored in an identifiable manner for each input condition;
An input / output information database in which an input / output information table defining input / output information of each task is stored so as to be identifiable by information;
An output information database in which a task output information table defining output information output by task execution is stored so as to be identifiable by output information;
A task database in which a task definition table defining the input condition and output information of a task is stored so as to be identifiable for each task;
One of the combinations of the task input condition table and the input / output information table in which the information defined as the input condition in the task input condition table matches the information defined in the input / output information table First extraction means for extracting the other table by designating the table of
One of the combinations of the task output information table and the input / output information table in which the information defined as the output information in the task output information table matches the information defined in the input / output information table Second extraction means for extracting the other table by designating the table of
Defined in the task definition table in which the input conditions defined in the task input condition table extracted by the first extraction means and in the task output information table extracted by the second extraction means Third extraction means for extracting at least one of the task definition tables in which the output information is defined;
The task extraction condition table that defines the input condition defined in the task definition table is extracted as the one table by the first extraction unit, and the other table is the second extraction unit with respect to the second extraction unit. The designation as one table and the other output table extracted by the second extraction means designated as the one table by the task output information table defining the output information defined in the task definition table. Designation means for performing at least one of the designation as the one table for the first extraction means;
It is characterized by providing.

  According to the task design support system of the present invention described in claim 1, each time a task is designed, a task input condition table and a task output information table that respectively define the input condition and output information of the task are an input condition database. And the output information database respectively. Also, an input / output information table that defines information that becomes input conditions and output information of the task is stored in the input / output information database.

  Therefore, when a task input condition table corresponding to the subject task to be verified is specified in the first extraction means, the first extraction means uses the input condition defined in the task input condition table as an input / output information table. Search for the input / output information database. As a result, the first extraction unit extracts an input / output information table that defines information that is an input condition of the own task.

  When the input / output information table extracted by the first extraction unit is designated as the second extraction unit, the second extraction unit searches the task output information table using the information defined in the input / output information table as a keyword. To the output information database. As a result, the second extraction unit extracts a task output information table in which information that is an input condition of the own task is defined as output information.

  The third extraction unit searches the task database for the task definition table using the output information defined in the task output information table extracted by the second extraction unit as a keyword. As a result, the third extraction unit extracts a task definition table in which information that is an input condition of the own task is defined as output information.

  When the second extraction unit cannot extract the task output information table or when the third extraction unit cannot extract the task definition table, there is no other task whose output information is information that is the input condition of the own task. It will be.

  On the other hand, when the task output information table corresponding to the own task is designated as the second extraction means, the second extraction means searches the input / output information table using the output information defined in the task output information table as a keyword, Perform for the I / O information database. As a result, the second extraction means extracts an input / output information table that defines information that is output information of the own task.

  When the input / output information table extracted by the second extraction means is designated as the first extraction means, the first extraction means searches the task input condition table using information defined in the input / output information table as a keyword. To the input condition database. Thereby, the first extraction means extracts a task input condition table in which information that is output information of the own task is defined as an input condition.

  Further, the third extraction unit searches the task database for a task definition table using the input conditions defined in the task input condition table extracted by the first extraction unit as keywords. Thereby, the third extraction unit extracts a task definition table in which information that is output information of the own task is defined as an input condition.

  If the first extraction unit cannot extract the task input condition table, or the third extraction unit cannot extract the task definition table, there is no other task whose information is the output information of the own task. It will be.

  From the above, when a task is designed, there are other tasks that use information that is the input condition of the task from other tasks, and that use the output information of the task as an input condition. It can be verified whether or not. As a result, it is possible to facilitate the consistency evaluation of the interface between tasks constituting the system software.

  The task design support system of the present invention described in claim 2 is the task design support system of the present invention described in claim 1, wherein the input / output information table is information defined in the input / output information table. And the attribute of the information are defined in association with each other, and the first extraction means sets the task input condition table corresponding to the other table to the input / output information table specified as the one table. If extraction is not possible, the second extraction means defines the same attribute as the attribute defined in the input / output information table in association with the information defined in the input / output information table. The other input / output information table is extracted as the other table, and the second extraction means is designated as the one table. When the task output information table corresponding to the other table cannot be extracted from the output information table, the first extraction means associates the input / output information table with the information defined in the input / output information table. The other input / output information table in which the same attribute as the attribute defined in (1) is defined in association with information is extracted as the other table.

  Furthermore, the task design support system of the present invention described in claim 3 is the task design support system of the present invention described in claim 1 or 2, wherein the input / output information table is defined by the input / output information table. The information is defined in association with the attribute of the information, and the third extraction means defines the input conditions defined in the task input condition table extracted by the first extraction means. When the task definition table cannot be extracted, the second extraction means associates the same attribute as the attribute defined in the input / output information table with the information defined in the input / output information table. The other input / output information table defined is extracted as the other table, and the third extraction means extracts the second extraction means. When the task definition table in which the output information defined in the task output information table is defined cannot be extracted, the first extraction means associates the input with the information defined in the input / output information table. The other input / output information table in which the same attribute as the attribute defined in the output information table is defined in association with information is extracted as the other table.

  According to the task design support system of the present invention described in claim 2, in the task design support system of the present invention described in claim 1, when the first extraction means cannot extract the task input condition table, According to the task design support system of the present invention described in Item 3, in the task design support system of the present invention described in Claim 1 or 2, the input defined in the task input condition table extracted by the first extraction means When the third extraction unit cannot extract the task definition table in which the conditions are defined, the following occurs.

  In other words, the second extraction means uses other input / output information in which the same attribute as the attribute defined in association with the information that is the output information of the invoking task is defined in association with the information on the input / output information table extracted earlier. The table is extracted again. Then, the first extraction means, which is designated by the other input / output information table newly extracted by the second extraction means, creates a task input condition table in which information having the same attribute as that of the output information of the own task is defined as an input condition. Will be extracted.

  On the other hand, according to the task design support system of the present invention described in claim 2, in the task design support system of the present invention described in claim 1, when the second extraction means cannot extract the task output information table, According to the task design support system of the present invention described in claim 3, the task design support system of the present invention described in claim 1 or 2 is defined by the task output information table extracted by the second extraction means. When the third extraction unit cannot extract the task definition table in which the output information is defined, the following occurs.

  In other words, the first extraction unit is configured to output other input / output information in which the same attribute as the attribute defined in association with the information that is the input condition of the invoking task is defined in association with the information in the previously extracted input / output information table. The table is extracted again. Then, the second extraction unit, which is designated by another input / output information table extracted by the first extraction unit, creates a task output condition table in which information having the same attribute as that of the input condition of the own task is defined as output information. Will be extracted.

  From the above, when the designed task cannot acquire input conditions from other tasks, verify whether there are other tasks whose output information is alternative information based on the attribute of the information Can do. Also, if the output information of the designed task is not used by other tasks, whether there is another task that can use the output information of the designed task as a substitute for the input condition is based on the attribute of the information Can be verified. Thereby, the consistency evaluation of the interface between the tasks constituting the system software can be made easier by expanding the allowable range of consistency.

  According to a fourth aspect of the present invention, there is provided the task design support system according to the present invention, wherein the task design support system according to the first, second or third aspect of the present invention is a task schedule table for defining execution timing of tasks in time series. Is stored in an identifiable manner for each task, and whether or not there is a time-series inconsistency in using the output information of one task as the input condition of the other task, It further comprises time series determination means for determining by comparing the execution timings defined in the task schedule table corresponding to each task.

  According to the task design support system of the present invention described in claim 4, in the task design support system of the present invention described in claim 1, 2 or 3, the information that is the input condition of the own task is used as output information. Each task is executed at a timing before the invoking task, and whether or not the output information of the task can be used as an input condition for the invoking task is defined in the task schedule table for both tasks. Verification can be performed based on the timing of execution timing.

  Similarly, whether other tasks that use the output information of the invoking task as input conditions are executed at a later timing than the invoking task, and can output the invoking task output information to other tasks as input conditions It can be verified whether or not the execution timing is defined in the task schedule tables of both tasks. As a result, it is possible to more easily evaluate the consistency of the interface between the tasks constituting the system software in consideration of the context of execution timing on the time series between the own task and other tasks.

Furthermore, in order to achieve the above object, a task design support method according to the present invention described in claim 5 includes:
A method for supporting design of tasks constituting system software,
The task input condition table in which the input condition of the invoking task is defined by searching an input condition database in which a task input condition table in which input conditions necessary for executing the task are defined is stored in an identifiable manner for each input condition Extracting the
The input / output information table in which the input / output information table defining the input / output information of each task is stored in an identifiable manner for each information is searched, and the information defined as the input condition in the extracted task input condition table is Extracting the defined input / output information table;
The output information database in which the task output information table defining the output information output by the execution of the task is stored so as to be identifiable for each output information is searched, and the information defined in the extracted input / output information table is Extracting the task output information table defined as output information;
A task definition table in which a task definition table that defines task output information is stored in an identifiable manner for each task, and the output information defined in the extracted task output information table is defined. Extracting the
It is characterized by including.

In order to achieve the above object, the task design support method according to the present invention described in claim 9 includes:
A method for supporting design of tasks constituting system software,
The task output information in which the output information of the invoking task is defined by searching the output information database in which the task output information table defining the output information output by the execution of the task is identifiable for each output information Extracting a table;
The input / output information table in which the input / output information table defining the input / output information of each task is stored in an identifiable manner for each information is searched, and the information defined as the output information in the extracted task output information table is Extracting the defined input / output information table;
A task input condition table in which input conditions necessary for executing a task are defined is stored in an identifiable manner for each input condition, and information defined in the extracted input / output information table is input. Extracting the task input condition table defined as a condition;
The task definition table that defines the input conditions defined in the extracted task input condition table is searched by searching a task database in which a task definition table that defines task input conditions is stored so as to be identifiable by task. Extracting the
It is characterized by including.

  According to the task design support method of the present invention described in claim 5, the task definition table in which information that is the input condition of the own task is defined as output information is extracted by sequentially performing extraction in four steps. If the task output information table or task definition table in which the information that is the input condition of the invoking task is defined as the output information cannot be extracted during the sequential execution of the four steps, the information that is the input condition of the invoking task is output as the output information. There will be no other task. Therefore, when a certain task is designed, it is possible to verify whether or not information that is an input condition for the task can be acquired from another task.

  According to the task design support method of the present invention described in claim 9, by sequentially performing extraction in four steps, a task definition table in which information which is output information of the own task is defined as an input condition is extracted. If the task input condition table or task definition table in which the information that is the output information of the invoking task is defined as the input condition cannot be extracted while the four steps are sequentially performed, the information that is the output information of the invoking task is input to the input condition. There will be no other task. Therefore, when a certain task is designed, it is possible to verify whether there is another task that uses the output information of the task as an input condition. Thereby, the consistency evaluation of the interface between the tasks constituting the system software can be made easier by expanding the allowable range of consistency.

  Furthermore, the task design support method of the present invention described in claim 6 is the task design support method of the present invention described in claim 5, wherein information defined in the extracted input / output information table is used as the output information. In the step of extracting the defined task output information table, when the task output information table cannot be extracted, the input / output information database is searched and defined in the extracted input / output information table. And extracting the other input / output information table in which the same attribute as that defined in association with the information is defined in association with the information.

  The task design support method of the present invention described in claim 7 is the task design support method of the present invention described in claim 5 or 6, wherein the output information defined in the extracted task output information table is In the step of extracting the defined task definition table, when the task definition table cannot be extracted, the task output information database is searched, and the output defined in the extracted task output information table The method further includes the step of extracting the other task output information table in which the same attribute as the attribute defined in association with the information is defined in association with the output information.

  According to the task design support method of the present invention described in claim 6, when the task output information table cannot be extracted in the task design support method of the present invention described in claim 5, the task design support method described in claim 7 is also described. According to the task design support method of the present invention, in the task design support method of the present invention described in claim 5 or 6, a task definition table in which output information defined in the extracted task output information table is defined. If it cannot be extracted:

  In other words, another input / output information table in which the same attribute as the attribute defined in association with the information that is the input condition of the invoking task is defined in association with the information in the previously extracted input / output information table is extracted again. . Then, a task output condition table is defined in which information defined in other input / output information tables extracted anew is defined as output information, that is, information having the same attribute as the input condition of the invoking task is defined as output information. Will be extracted.

  From the above, when the designed task cannot acquire input conditions from other tasks, verify whether there are other tasks whose output information is alternative information based on the attribute of the information Can do. Thereby, the consistency evaluation of the interface between the tasks constituting the system software can be made easier by expanding the allowable range of consistency.

  Furthermore, the task design support method of the present invention described in claim 10 is the task design support method of the present invention described in claim 9, wherein information defined in the extracted input / output information table is used as the input condition. In the step of extracting the defined task input condition table, when the task input condition table cannot be extracted, the input / output information database is searched and defined in the extracted input / output information table. And extracting the other input / output information table in which the same attribute as that defined in association with the information is defined in association with the information.

  The task design support method of the present invention described in claim 11 is the task design support method of the present invention described in claim 9 or 10, wherein the input condition defined in the extracted task input condition table is In the step of extracting the defined task definition table, when the task definition table cannot be extracted, the task input condition database is searched and the input defined in the extracted task input condition table The method further includes the step of extracting the other task input condition table in which the same attribute as the attribute defined in association with the condition is defined in association with the input condition.

  According to the task design support method of the present invention described in claim 10, when the task input condition table cannot be extracted in the task design support method of the present invention described in claim 9, it is described in claim 11 According to the task design support method of the present invention, in the task design support method of the present invention described in claim 9 or 10, the task definition table in which the input conditions defined in the extracted task input condition table are defined. If it cannot be extracted:

  In other words, another input / output information table in which the same attribute as that defined in association with the information that is output information of the invoking task in the previously extracted input / output information table is defined in association with the information is extracted again. . Then, a task input condition table in which information defined in another input / output information table extracted anew is defined as an input condition is extracted.

  From the above, if the output information of the designed task is not used by other tasks, whether the other task that can use the output information of the designed task instead of the input condition exists Can be verified based on Thereby, the consistency evaluation of the interface between the tasks constituting the system software can be made easier by expanding the allowable range of consistency.

  Furthermore, the task design support method of the present invention described in claim 8 is the task design support method of the present invention described in claim 5, 6 or 7, wherein the task schedule table defines execution timings of tasks in time series. Search the schedule database stored in an identifiable manner for each task, the task schedule table corresponding to the task defined in the extracted task definition table, and the task schedule table corresponding to the own task Each execution timing defined in each extracted task schedule table is extracted, and the output information of the task defined in the extracted task definition table is used as the input condition of the own task. Step of determining whether or not a time-series contradiction occurs Characterized in that it comprises further.

  Further, the task design support method of the present invention described in claim 12 is the task design support method of the present invention described in claim 9, 10 or 11, wherein the task schedule table defines the execution timing of tasks in time series. Search the schedule database stored in an identifiable manner for each task, the task schedule table corresponding to the task defined in the extracted task definition table, and the task schedule table corresponding to the own task When the execution timings defined in the extracted task schedule tables are used as the input conditions for the tasks defined in the extracted task definition table, the output information of the own task is used. A step to determine whether or not a time-series contradiction occurs And further comprising a flop.

  According to the task design support method of the present invention described in claim 8, in the task design support method of the present invention described in claim 5, 6 or 7, the information that is the input condition of the own task is used as output information. Each task is executed at a timing before the invoking task, and whether or not the output information of the task can be used as an input condition for the invoking task is defined in the task schedule table for both tasks. Verification can be performed based on the timing of execution timing.

  According to the task design support method of the present invention described in claim 12, in the task design support method of the present invention described in claim 9, 10, or 11, there is another task that uses the output information of its own task as an input condition. Executed at a timing later than the invoking task, and whether or not the output information of the invoking task can be supplied as an input condition to other tasks is determined by the execution timing defined in the task schedule tables of both tasks. Can be verified on the basis of the future. As a result, it is possible to more easily evaluate the consistency of the interface between the tasks constituting the system software in consideration of the context of execution timing on the time series between the own task and other tasks.

  According to the task design support system and the task design support method of the present invention, it is possible to facilitate the consistency evaluation of the interface between tasks constituting the system software.

It is explanatory drawing which shows schematic structure of the task design support system which concerns on one Embodiment of this invention. It is explanatory drawing which shows the memory content of the database of FIG. It is explanatory drawing which shows the outline | summary of the task designed with the client terminal of FIG. It is explanatory drawing which shows the structure of the table registered into the database of FIG. 1 about the task of FIG. It is a flowchart which shows the outline of the task design assistance process performed in the client terminal of FIG. It is a flowchart which shows the specific processing content in the functional module data candidate selection logic and functional module task link time series consistency diagnostic logic of FIG. It is a flowchart which shows the specific processing content in the functional module data candidate selection logic and functional module task link time series consistency diagnostic logic of FIG. FIG. 4 is an explanatory diagram showing verification contents when verifying interface consistency regarding the output information of the task of FIG. 3 by the task design support system of FIG. 1; FIG. 4 is an explanatory diagram showing verification contents when verifying interface consistency regarding the output information of the task of FIG. 3 by the task design support system of FIG. 1; FIG. 4 is an explanatory diagram showing verification contents when verifying interface consistency regarding the output information of the task of FIG. 3 by the task design support system of FIG. 1; FIG. 4 is an explanatory diagram showing verification contents when verifying the consistency of execution timing on the time series of the task of FIG. 3 by the task design support system of FIG. 1. FIG. 4 is an explanatory diagram illustrating verification contents when verifying interface consistency regarding the task input condition of FIG. 3 by the task design support system of FIG. 1; FIG. 4 is an explanatory diagram illustrating verification contents when verifying interface consistency regarding the task input condition of FIG. 3 by the task design support system of FIG. 1; It is explanatory drawing which shows typically the structure at the time of constructing the system software relevant to the guidance control of a rocket using the module which supported task design by the task design support system of FIG.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is an explanatory diagram showing a schematic configuration of a task design support system according to an embodiment of the present invention, and FIG. 2 is an explanatory diagram showing storage contents of the database of FIG.

  As shown in FIG. 1, the task design support system of the present embodiment is configured by an intranet in which a database server 10, a network server 30, and a plurality of client terminals 40, 40,. Some or all of the client terminals 40 may be connected to the network server 30 and the database server 10 via the Internet (not shown). Each client terminal 40 has a CPU, RAM, and ROM (all not shown), and has a display 41, a keyboard 42, and a mouse 43, respectively.

  The database server 10 is a server that holds a database, performs processing when receiving a search or update request from the client terminal 40, and returns the result to an application program executed on the client terminal 40. The database held by (stored in) the database server 10 includes a task database 11, an input condition database 13, an output information database 15, an input / output information database 17, and a schedule database 19 shown in FIG.

  The task database 11 stores a “task definition table (2)” that defines input conditions necessary for task execution and output information output by task execution by ID. This task definition table (2) includes items such as “task ID”, “input condition ID”, and “output information ID”, and attributes such as “task definition version”, “task category ID”, and “task content”. Items related to are defined. The item “task ID” is set to a primary key (PK: PrimaryKey) and a foreign key (FK: ForeignKey, external reference key), and the items “input condition ID” and “output information ID” are foreign keys. Set to key. The task definition table (2) having such a configuration is defined for each task, and assigns a foreign key by referring to task definition information from an external database (not shown) as appropriate.

  The input condition database 13 stores a “task input condition table (6)” that defines information as input conditions by ID. In the task input condition table (6), items such as “input condition ID” and “information ID” are defined. The item “input condition ID” is set as a primary key, and the item “information ID” is set as a foreign key. The task input condition table (6) having such a configuration is defined for each content (information) of the input condition to be defined.

  The output information database 15 stores a “task output information table (7)” that defines information as output information by ID. In the task output information table (7), items such as “output information ID” and “information ID” are defined. The item “output information ID” is set as a primary key, and the item “information ID” is set as a foreign key. The task output information table (7) having such a configuration is defined for each content (information) of the output condition to be defined.

  The input / output information database 17 stores an “input / output information table (8)” that defines information as task input conditions and output information (input / output information) by name or the like. In the input / output information table (8), items related to attributes such as “content” and “version” are defined in addition to items such as “information ID” and “name”. The item “information ID” is set as a primary key. There is no item set to foreign key. The input / output information table (8) having such a configuration is defined for each content of information to be defined.

  The schedule database 19 stores a “task schedule table (3)” that defines the execution timing of tasks in time series. In the task schedule table (3), items such as “task ID”, “start time”, and “end time” are defined. The item “task ID” is set as a primary key. There is no item set to foreign key. The task schedule table (3) having such a configuration is defined for each task.

  FIG. 3 is an explanatory diagram showing an outline of a task designed in the client terminal of FIG. 1, and FIG. 4 is an explanatory diagram showing a configuration of a table registered in the database of FIG. 1 for the task of FIG.

  As shown in FIG. 3, the task A designed using the task design support system of the present embodiment uses information 1 to 4 as input conditions and information A1 to A4 as output information. However, the number of input conditions and output information varies depending on the task.

  As shown in FIG. 4, when a task is designed, a task definition table (2) that defines the designed task (own task), and a task input condition table that defines task input conditions and output information (6) and the task output information table (7) and the input / output information table (8) defining the contents of the task input conditions and specific information of the output information are stored (registered) in the respective databases 11-17. To do. Although not shown in FIG. 4, a task schedule table (3) that defines the execution timing of the designed task is also stored (registered) in the schedule database 19.

  Next, an outline of the interface consistency verification process executed by the CPU according to the program stored in the ROM of the client terminal 40 when registering various tables related to the task designed in the client terminal 40 in each database is shown in FIG. This will be described with reference to the explanatory diagram and the flowchart of FIG. FIG. 5 is a flowchart showing an outline of task design support processing executed in the client terminal of FIG.

  The processing described below proceeds by operating the keyboard 42 and the mouse 43 in accordance with the display on the display 41 and inputting necessary information. In addition, a part of the process of searching the contents of the tables of each of the databases 11 to 19 and extracting a specific table is performed by the CPU of the database server 10 according to a program stored in a ROM (none of which is shown).

  As shown in FIG. 5, first, the CPU confirms that a flag indicating completion of the consistency check is not set for the designed task (self task) (step S1). Next, data check logic is executed (step S3). In this logic, a NULL check, task ID diagnosis, invalid data diagnosis, and contradiction data diagnosis are performed on the tables stored in the respective databases 11 to 17 of the database server 10 with respect to the designed task.

  In the NULL check, it is confirmed whether or not the item relating to the attribute of the task definition table (2) relating to the target task is “NULL (no entry)”. If it is “NULL”, an alert is displayed on the display 41.

  In task ID diagnosis, is the ID assigned as the “task ID” in the task definition table (2) related to the target task duplicated with the ID already used in the task definition table (2) related to other tasks? Check if. If it overlaps with another task, a message prompting the change of the ID is displayed on the display 41.

  In the invalid data diagnosis, information IDs indicating input conditions and output information related to the target task are defined in the task input condition table (6) and the task output information table (7), respectively, and the information ID is correct. Make sure that

  In the contradiction data diagnosis, the input / output categories respectively defined as items relating to the attributes of the task input condition table (6) and the task output information table (7) referring to the same information ID of the input / output information table (8). Confirm that the contents of the IDs match each other. In the contradiction data diagnosis, it is confirmed that a plurality of task output information tables (7) referring to the same information ID in the input / output information table (8) do not exist.

  Next, the CPU confirms whether there is a problem in the results of the above four checks and diagnosis, and the contents of each table are abnormal, or whether there is no problem in the results of diagnosis and the contents of each table are normal (step). S5). If it is abnormal (“abnormal” in step S5), after performing abnormal termination processing such as displaying an abnormality on the display 41 (step S19), the series of processing is terminated. In this case, after correcting the contents of the table causing the abnormality, the processing from step S1 is performed again. If it is normal (“normal” in step S5), a function module list creation process is executed (step S7). In this process, each table confirmed to be normal in step S5 is stored in each database 11-19 of the database server 10.

  As a result, the input / output information table (8) -task input condition table (6) -task definition table (2) -task output information table (7) related to the designed task input conditions is stored in each database 11-17 of the database server 10. -The input / output information table (8) related to the output information is stored in the respective databases 11 to 17 with the contents having the interrelation shown in the explanatory diagram of FIG.

  Subsequently, the CPU executes a functional module data link diagnosis logic (step S9). In this logic, task input condition diagnosis and task output information diagnosis are performed.

  In the task input condition diagnosis, an input / output information table (8) whose information ID is the same as the information ID defined as an item of the task input condition table (6) is stored in the input / output information database 17 Confirm. That is, in the left half of the explanatory diagram of FIG. 4, the input / output information table (8) -task input condition table (6) -task definition table (2) relating to the input conditions correspond to each other with the contents ensuring the mutual relationship. 17, 13 and 11 are confirmed.

  Similarly, in the task output information diagnosis, the input / output information table (8) including the same information ID as the information ID defined as the item of the task output information table (7) is stored in the input / output information database 17. Make sure. That is, in the right half of the explanatory diagram of FIG. 4, the task definition table (2) -task output information table (7) -the input / output information table (8) related to the output information correspond to each other with the contents ensuring the mutual relationship. 17, 13 and 11 are confirmed.

  Next, the CPU confirms whether either one of the diagnosis results of the task input condition diagnosis and the task output information diagnosis has a problem and is abnormal, or both diagnosis results are normal with no problem (step S11). . In the confirmation in step S11, the input / output information table (8) including the same information ID as the information ID of the task input condition table (6) in the item and the same information ID as the information ID of the task output information table (7) If at least one of the input / output information table (8) included in is not stored in the input / output information database 17, the confirmation result is abnormal, and if both are stored, the confirmation result is normal.

  If the diagnosis result is abnormal (“abnormal” in step S11), an abnormal termination process such as displaying an abnormality on the display 41 is performed (step S19), and the series of processes is terminated. In this case, each table stored in the database server 10 of the designed task is corrected so as to have the contents shown in the explanatory diagram of FIG. 4, and the processing from step S1 is performed again. . If the diagnosis result is normal (“normal” in step S11), the function module data candidate selection logic (step S13) and the function module task link time series consistency diagnosis logic (step S15) are executed.

  The function module data candidate selection logic extracts and selects other tasks that output information used as input conditions in the designed task as output information. In the same logic, another task is extracted and selected using the information of the output information output by the designed task as an input condition.

  Here, specific processing contents in the functional module data candidate selection logic in step S13 and the functional module task link time series consistency diagnosis logic in step S15 will be described with reference to the flowcharts of FIGS. 6 and 7 and FIGS. This will be described with reference to the drawings.

  6 and 7 are flowcharts showing specific processing contents in the functional module data candidate selection logic and the functional module task link time series consistency diagnosis logic of FIG. 8 to 10 are explanatory diagrams showing verification contents when verifying the consistency of the interface related to the output information of the task of FIG. 3 by the task design support system of FIG. FIG. 11 is an explanatory diagram showing the contents of verification when the task design support system of FIG. 1 verifies the consistency of execution timing on the time series of the task of FIG. 12 and 13 are explanatory diagrams showing the contents of verification when the task design support system of FIG. 1 verifies the interface consistency regarding the task input conditions of FIG.

  6 and 7 exemplify the case where the functional module data candidate selection logic and the functional module task link time series consistency diagnosis logic are executed as a series of processes. Of course it is also good.

  As shown in FIG. 6, the CPU outputs a task output defined by setting the output information ID (set in the foreign key FK5) defined in the task definition table (2) of the designed task (own task) as the primary key. The information table (7) is extracted from the output information database 15 (step S21). Next, the CPU sets the input / output information table (8) defined by setting the information ID (set in the foreign key FK1) defined in the task output information table (7) extracted in step S21 as the primary key. Extracted from the input / output information database 17 (step S23).

  Then, the CPU sets the task input condition table (6) defined by setting the information ID defined in the input / output information table (8) extracted in step S23 in the foreign key (FK1) in the input condition database 13. It is confirmed whether or not it is stored (step S25). That is, as shown in FIG. 8, the presence / absence of the task input condition table (6) in which the same information ID as the information ID defined in the input / output information table (8) is defined, and the input condition database 13 using the information ID. Confirm by searching for. This information ID is an information ID of information (for example, information A1) which is defined in the input / output information table (8) relating to the output information and becomes the output information of the designed task.

  If the corresponding task input condition table (6) is not stored in the input condition database 13 (NO in step S25), the content that matches the input / output information table (8) extracted in step S23 in the attribute item is defined. It is confirmed whether the other input / output information table (8) is stored in the input / output information database 17 (step S27). That is, as shown in the upper part of FIG. 10, the presence / absence of another input / output information table (8) that defines information having the same attribute as the output information of the designed task is determined based on the input / output information database using the attribute. Confirm by searching 17.

  If another input / output information table (8) is not stored in the input / output information database 17 (NO in step S27), the process proceeds to step S37 described later. If it is stored (YES in step S27), it is confirmed whether or not the corresponding other input / output information table (8) is selected instead of the input / output information table (8) extracted in step S23 ( Step S29). If not selected (NO in step S29), the process proceeds to step S37. If so (YES in step S29), the process returns to step S25.

  In this way, by selecting another input / output information table (8) in step S29 and returning to step S25, as shown in the lower part of FIG. 10, the input information defining the output information of the designed task is defined. Instead of the output information table (8), another input / output information table (8) is associated with the task output information table (7) defining the output information of the designed task. Also, in step S25 returned from step S29, the task input condition table (6) defined by setting the information ID defined in the input / output information table (8) selected in step S29 to the foreign key (FK1) is provided. Whether or not it is stored in the input condition database 13 is confirmed.

  If the corresponding task input condition table (6) is stored in the input condition database 13 in step S25 (YES), the stored task input condition table (6) is extracted from the input condition database 13. Further, the task definition table (2) defined by setting the input condition ID defined by setting the primary key in the extracted task input condition table (6) to the foreign key (FK4) is stored in the task database 11. It is confirmed whether or not (step S31).

  That is, as shown in FIG. 9, the task database 11 is searched using the information ID for the presence or absence of the task definition table (2) that defines the same information ID as the information ID defined in the task input condition table (6). Confirm by. This information ID is an information ID of information (for example, information A1) that becomes output information of the designed task.

  If the corresponding task definition table (2) is not stored in the task database 11 (NO in step S31), the process returns to step S27, and if stored (YES in step S31), it is stored in step S31. It is confirmed whether or not the task defined in the task definition table (2) that has been confirmed and the designed task (own task) are consistent in time series (step S33).

  In step S33, the output information output by the task defined in the task definition table (2) confirmed to be stored in step S31 is determined based on whether or not the designed task can be used as an input condition. This is done by checking the task execution timing.

  Specifically, each of the task definition table (2) confirmed to be stored in step S31 and the task definition table (2) of the designed task are defined in each task definition table (2). The task schedule table (3) defined by setting the current task ID (set to PK and FK1 to 3) as the primary key is extracted from the schedule database 19 respectively.

  Next, items such as “start time” and “end time” defined in each extracted task schedule table (3) are compared, and the task definition table (2) confirmed as being stored in step S31 is stored. Whether or not the output information of the designed task is output prior to the execution timing of other tasks defined in (1). When the output information of other tasks is output prior to the designed task execution timing, the confirmation result in step S33 is time-series consistent (YES). Otherwise, the process proceeds to step S33. The confirmation result is not consistent in time series (NO).

  When output information is output earlier than the execution timing of a task designed by another task and time-series consistency is obtained, the relationship between the other task and the designed task is, for example, the task of FIG. There is a context such as 1 (other task) and task 2 (designed task).

  If time-series consistency is obtained (YES in step S33), a normal determination is made (step S35), and the series of processing ends. On the other hand, if consistency in time series is not achieved (NO in step S33), the process proceeds to step S37, where an abnormality is determined, and the series of processes is terminated. If no other input / output information table (8) is stored in the input / output information database 17 in step S27 (NO), or another input / output information table (8) is extracted in step S23 in step S29. Even when the selection is not made in place of the input / output information table (8) (NO), the abnormality determination in step S37 is performed and the series of processes is terminated.

  Also, as shown in FIG. 7, the CPU first sets the input condition ID (set in the foreign key FK4) defined in the task definition table (2) of the designed task (own task) as the primary key. The defined task input condition table (6) is extracted from the input condition database 13 (step S41). Next, the CPU sets the input / output information table (8) defined by setting the information ID (set in the foreign key FK1) defined in the task input condition table (6) extracted in step S41 as the primary key. Extracted from the input / output information database 17 (step S43).

  Then, the CPU sets the task output information table (7) defined by setting the information ID defined in the input / output information table (8) extracted in step S43 in the foreign key (FK1) in the output information database 15. It is confirmed whether or not it is stored (step S45). That is, as shown in FIG. 12, the presence or absence of the task output information table (7) in which the same information ID as the information ID defined in the input / output information table (8) is defined, and the output information database 15 using the information ID. Confirm by searching for. This information ID is an information ID of information (for example, information 1) which is defined in the input / output information table (8) regarding the input condition and which becomes the input condition of the designed task.

  If the corresponding task output information table (7) is not stored in the output information database 15 (NO in step S45), the content that matches the input / output information table (8) extracted in step S43 in the attribute item is defined. It is checked whether the other input / output information table (8) is stored in the input / output information database 17 (step S47).

  If another input / output information table (8) is not stored in the input / output information database 17 (NO in step S47), the process proceeds to step S57 described later. If it is stored (YES in step S47), it is confirmed whether or not the corresponding other input / output information table (8) is selected instead of the input / output information table (8) extracted in step S43 ( Step S49). If not selected (NO in step S49), the process proceeds to step S57. If so (YES in step S49), the process returns to step S45.

  In this way, by selecting another input / output information table (8) in step S49 and returning to step S45, the input / output information table (8) defining the information that is the input condition of the designed task is replaced. The other input / output information table (8) is associated with the task output information table (7) that defines the input conditions of the designed task. In step S45 returned from step S49, the task input condition table (6) defined by setting the information ID defined in the input / output information table (8) selected in step S49 to the foreign key (FK2) is provided. Whether or not it is stored in the input condition database 13 is confirmed.

  If the corresponding task output information table (7) is stored in the output information database 15 in step S45 (YES), the stored task output information table (7) is extracted from the output information database 15. Further, the task definition table (2) defined by setting the output information ID defined by setting the primary key in the extracted task output information table (7) to the foreign key (FK5) is stored in the task database 11. It is confirmed whether or not (step S51).

  That is, as shown in FIG. 13, the task database 11 is searched using the information ID for the presence or absence of the task definition table (2) that defines the same information ID as the information ID defined in the task output information table (7). Confirm by. This information ID is an information ID of information (for example, information 1) which is an input condition for the designed task.

  If the corresponding task definition table (2) is not stored in the task database 11 (NO in step S51), the process returns to step S47, and if stored (YES in step S51), it is stored in step S51. It is confirmed whether the task defined in the task definition table (2) that has been confirmed and the designed task (own task) are consistent in time series (step S53).

  In step S53, the output information output by the task defined in the task definition table (2) confirmed to be stored in step S51 is used to determine whether the designed task can be used as an input condition. This is done by checking the task execution timing.

  Specifically, first, the task definition table (2) confirmed to be stored in step S51 and the task definition table (2) of the designed task are defined in each task definition table (2). The task schedule table (3) defined by setting the current task ID (set to PK and FK1 to 3) as the primary key is extracted from the schedule database 19 respectively.

  Next, items such as “start time” and “end time” defined in each extracted task schedule table (3) are compared, and stored in step S51 prior to the execution timing of the designed task. It is confirmed whether or not output information of other tasks defined in the task definition table (2) confirmed to be output is output. If the output information of the designed task is output prior to the execution timing of other tasks, the confirmation result in step S53 is consistent in time series (YES). If not, the result of step S53 The confirmation result is not consistent in time series (NO).

  When the designed task outputs output information before the execution timing of other tasks and the consistency in time series is maintained, the relationship between the designed task and other tasks is, for example, the task of FIG. There are contextual relationships such as 2 (designed task) and 3 (other tasks).

  If time-series consistency is obtained (YES in step S53), normality is determined (step S55), and the series of processes is terminated. On the other hand, if time-series consistency is not achieved (NO in step S53), the process proceeds to step S57, where an abnormality is determined, and the series of processes is terminated. If no other input / output information table (8) is stored in the input / output information database 17 at step S47 (NO), or another input / output information table (8) is extracted at step S43 at step S49. Even when not selecting (NO) instead of the input / output information table (8), the abnormality determination of step S57 is performed and the series of processes is ended.

  If the function module data candidate selection logic in step S13 in FIG. 5 and the function module task link time series consistency diagnosis logic in step S15 are executed by the processing in FIGS. 6 and 7 described above, the CPU It is confirmed whether the diagnosis result of the data candidate selection logic and the function module task link time series consistency diagnosis logic is abnormal or normal (step S17). When normal determination is performed in step S35 of FIG. 6 or step S55 of FIG. 7, the confirmation result of step S17 is normal, and when abnormality determination is performed in step S37 of FIG. 6 or step S57 of FIG. The confirmation result in step S17 becomes abnormal.

  If it is abnormal (“abnormal” in step S17), after performing abnormal termination processing such as displaying an abnormality on the display 41 (step S19), the series of processing is terminated. In this case, after correcting the contents of the table causing the abnormality, the processing from step S1 is performed again. If it is normal (“normal” in step S17), the series of processing ends.

  As is clear from the above description, in the task design support system of this embodiment, steps S25 and S27 in the flowchart of FIG. 6 and step S43 in the flowchart of FIG. It is processing corresponding to. Moreover, in this embodiment, step S23 and step S27 in FIG. 6, and step S45 in FIG. 7 are the processes corresponding to the 2nd extraction means in a claim.

  Furthermore, in this embodiment, step S31 in FIG. 6 and step S51 in FIG. 7 are processing corresponding to the third extraction means in the claims. Further, in the present embodiment, step S25 in FIG. 6 and step S45 in FIG. 7 are processes corresponding to the designation means in the claims. Furthermore, in this embodiment, step S33 in FIG. 6 and step S53 in FIG. 7 are processing corresponding to the time-series determination means in the claims.

  As described above, according to the task design support system of this embodiment, whether or not the input conditions of the designed task can be acquired from the output information from other tasks, and the output information of the designed task is input to the input condition. It is possible to check and verify whether or not there are other tasks to be used, including the time series context with other tasks. For this reason, it is possible to facilitate the consistency evaluation of the interface between the tasks constituting the system software.

  In addition, according to the task design support system of the present embodiment, when there is no output information that can be acquired as an input condition for the designed task and other tasks as the output source, the designed task can be used as an input condition. It is possible to extract a task that uses the above information as output information. Similarly, according to the task design support system of the present embodiment, when there is no other task that uses the output information output by the designed task as an input condition, the output information of the designed task can be used as an input condition. Other tasks can be extracted.

  Therefore, in the task design support system of this embodiment, another input / output information table in which information having the same attribute as the attribute defined in the input / output information table is defined in association with information to be input conditions and output information is input. A search can be made from the stored contents of the output information database 17. Therefore, the consistency evaluation of the interface between the tasks constituting the system software can be made easier by expanding the allowable range of consistency.

  And since the consistency evaluation of the designed task interface can be facilitated, even if the contents of some of the modules that make up the system software change, the task design that ensures the interface consistency between modules Therefore, it is possible to avoid the analysis and verification of the validity of the design contents from being performed manually by a large number of man-hours. Therefore, the module (task) in the system software developed for guidance control of a certain rocket can be easily used for guidance control of other rockets, and the versatility of the module can be enhanced.

  In addition, since the versatility of the module will increase, a general-purpose operation system (OS) will be used, and the consistency of the interface between the operation system and the module related to the guidance control will be designed, analyzed, It can be easily evaluated at each stage of verification.

  Therefore, as schematically shown in FIG. 14, a rocket is used by using a general-purpose operation system having a higher degree of completeness in operation performance on hardware than a dedicated operation system developed as part of conventional system software. It is possible to construct system software related to guidance control.

  Further, as a module related to guidance control, a module having an interface function between a general-purpose operation system and application software can be used, so that application software independent of the platform can be easily used for guidance control of the rocket.

  Due to the effects as described above, according to the task design support system of the present embodiment, it is possible to reduce the development cost related to rocket guidance control.

  In the present embodiment, the case of using the system software for rocket guidance control has been described as an example. However, the task design support system of the present invention can be widely applied when designing a task that needs to evaluate the consistency of an interface with another task. For example, other tasks between operation system function tasks and interface function modules (tasks), between interface function modules (tasks) and application function tasks, or between tasks within one of the function tasks. The present invention is applicable when designing a task that needs to be evaluated for interface consistency.

DESCRIPTION OF SYMBOLS 10 Database server 11 Task database 13 Input condition database 15 Output information database 17 Input / output information database 19 Schedule database 30 Server 30 WEB server 40 Client terminal 41 Display 42 Keyboard 43 Mouse

Claims (12)

A system that supports the design of tasks that make up system software,
An input condition database in which a task input condition table that defines input conditions necessary for task execution is stored in an identifiable manner for each input condition;
An input / output information database in which an input / output information table defining input / output information of each task is stored so as to be identifiable by information;
An output information database in which a task output information table defining output information output by task execution is stored so as to be identifiable by output information;
A task database in which a task definition table defining the input condition and output information of a task is stored so as to be identifiable for each task;
One of the combinations of the task input condition table and the input / output information table in which the information defined as the input condition in the task input condition table matches the information defined in the input / output information table First extraction means for extracting the other table by designating the table of
One of the combinations of the task output information table and the input / output information table in which the information defined as the output information in the task output information table matches the information defined in the input / output information table Second extraction means for extracting the other table by designating the table of
Defined in the task definition table in which the input conditions defined in the task input condition table extracted by the first extraction means and in the task output information table extracted by the second extraction means Third extraction means for extracting at least one of the task definition tables in which the output information is defined;
The task extraction condition table that defines the input condition defined in the task definition table is extracted as the one table by the first extraction unit, and the other table is the second extraction unit with respect to the second extraction unit. The designation as one table and the other output table extracted by the second extraction means designated as the one table by the task output information table defining the output information defined in the task definition table. Designation means for performing at least one of the designation as the one table for the first extraction means;
A task design support system characterized by comprising:   The input / output information table defines information defined in the input / output information table in association with attributes of the information, and the first extraction unit specifies the input / output specified as the one table. When the task input condition table corresponding to the other table cannot be extracted from the information table, the second extraction means associates the information defined in the input / output information table with the input / output information table. The other input / output information table in which the same attribute as the defined attribute is defined in association with information is extracted as the other table, and the second extraction means is designated as the one table. When the task output information table corresponding to the other table cannot be extracted from the input / output information table, the first extraction procedure is performed. The other input / output information table in which the same attribute as the attribute defined in the input / output information table is defined in association with the information defined in the input / output information table, 2. The task design support system according to claim 1, wherein the task design support system is extracted as the other table.   The input / output information table defines information defined in the input / output information table in association with attributes of the information, and the third extraction unit extracts the task input extracted by the first extraction unit. When the task definition table in which the input condition defined in the condition table is defined cannot be extracted, the second extraction unit associates the input / output information with the information defined in the input / output information table. The other input / output information table in which the same attribute as the attribute defined in the table is defined in association with information is extracted as the other table, and the third extracting means is the second extracting means. When the task definition table in which the output information defined in the task output information table extracted by cannot be extracted, the first extraction method The other input / output information table in which the same attribute as the attribute defined in the input / output information table is defined in association with the information defined in the input / output information table, 3. The task design support system according to claim 1, wherein the task design support system is extracted as the other table.   A schedule database in which a task schedule table that defines the execution timing of tasks in a time series is stored so as to be identifiable for each task, and the output information of one task is used as the input condition of the other task. Further comprising time series determination means for determining whether or not a contradiction arises by comparing the execution timings defined in the task schedule table corresponding to each of the one task and the other task, respectively. The task design support system according to claim 1, 2 or 3. A method for supporting design of tasks constituting system software,
The task input condition table in which the input condition of the invoking task is defined by searching an input condition database in which a task input condition table in which input conditions necessary for executing the task are defined is stored in an identifiable manner for each input condition Extracting the
The input / output information table in which the input / output information table defining the input / output information of each task is stored in an identifiable manner for each information is searched, and the information defined as the input condition in the extracted task input condition table is Extracting the defined input / output information table;
The output information database in which the task output information table defining the output information output by the execution of the task is stored so as to be identifiable for each output information is searched, and the information defined in the extracted input / output information table is Extracting the task output information table defined as output information;
A task definition table in which a task definition table that defines task output information is stored in an identifiable manner for each task, and the output information defined in the extracted task output information table is defined. Extracting the
A task design support method comprising:   If the task output information table cannot be extracted in the step of extracting the task output information table in which the information defined in the extracted input / output information table is defined as the output information, the input / output Search the information database and extract the other input / output information table in which the same attribute defined in association with the information defined in the extracted input / output information table is defined in association with the information. 6. The task design support method according to claim 5, further comprising a step of:   If the task definition table cannot be extracted in the step of extracting the task definition table in which the output information defined in the extracted task output information table is defined, the task output information database is searched. And extracting another task output information table in which the same attribute as that defined in association with the output information defined in the extracted task output information table is defined in association with the output information. The task design support method according to claim 5, further comprising a step.   The task schedule table corresponding to the task defined in the extracted task definition table is searched by searching the schedule database in which the task schedule table defining the task execution timing on the time series is stored so as to be identifiable by task. And the task schedule table corresponding to the own task, and the execution timings defined in the extracted task schedule tables are the execution timings of the tasks defined in the extracted task definition table. 8. The task design support method according to claim 5, further comprising a step of determining whether or not a time-series contradiction occurs when the output information is used as the input condition of the own task. A method for supporting design of tasks constituting system software,
The task output information in which the output information of the invoking task is defined by searching the output information database in which the task output information table defining the output information output by the execution of the task is identifiable for each output information Extracting a table;
The input / output information table in which the input / output information table defining the input / output information of each task is stored in an identifiable manner for each information is searched, and the information defined as the output information in the extracted task output information table is Extracting the defined input / output information table;
A task input condition table in which input conditions necessary for executing a task are defined is stored in an identifiable manner for each input condition, and information defined in the extracted input / output information table is input. Extracting the task input condition table defined as a condition;
The task definition table that defines the input conditions defined in the extracted task input condition table is searched by searching a task database in which a task definition table that defines task input conditions is stored so as to be identifiable by task. Extracting the
A task design support method comprising:   When the task input condition table cannot be extracted in the step of extracting the task input condition table in which the information defined in the extracted input / output information table is defined as the input condition, the input / output Search the information database and extract the other input / output information table in which the same attribute defined in association with the information defined in the extracted input / output information table is defined in association with the information. The task design support method according to claim 9, further comprising a step of:   In the step of extracting the task definition table in which the input conditions defined in the extracted task input condition table are defined, the task input condition database is searched when the task definition table cannot be extracted. To extract another task input condition table in which the same attribute defined in association with the input condition defined in the extracted task input condition table is defined in association with the input condition. The task design support method according to claim 9, further comprising a step.   The task schedule table corresponding to the task defined in the extracted task definition table is searched by searching the schedule database in which the task schedule table defining the task execution timing on the time series is stored so as to be identifiable by task. And the task schedule table corresponding to the own task, and the execution timings defined in the extracted task schedule tables are the task definition table from which the output information of the own task is extracted. 12. The task design support method according to claim 9, further comprising a step of determining whether or not a time-series contradiction occurs when the input condition of the task defined in (1) is used.

Images