JP2022047714A - Model generation system - Google Patents

Abstract

To solve a disadvantage that it is difficult to understand an intent of a program and improve an efficiency of a development in a model base development.SOLUTION: A model generation system 100 reads specification data 11 that recites a content of a program with text, and generates a model by replacing a keyword included in the specification data into a block while referring to a conversion database 107. Several models including the generated model are combined and connected based on model layout data 12 defining an execution order of the models to generate a combination model in a model base development. By doing this, a development efficiency of the program can be improved by taking advantage of a model base development that while making it easy to understand an intent of a developer based on the specification data for each model that builds the combination model, it is easy to visually grasp the execution order and inputs/outputs for combination among the entire models.SELECTED DRAWING: Figure 1

Description

The present invention relates to a model creation system that creates a model that represents the contents of a control program by combining blocks that indicate predetermined processing contents.

Conventionally, model-based development is often used in the development of programs for controlling vehicles. Model-based development is a method in which a developer does not describe a program in the form of source code, but describes the program in a highly visible manner by combining blocks indicating predetermined processing contents. In model-based development, for example, MATLAB (registered trademark), Simulink (registered trademark) and the like exist. In order to improve the efficiency of such model-based development, for example, Patent Document 1 provides a technique for confirming the consistency of input / output data between models when automatically combining the input / output of a plurality of models. ..

Japanese Unexamined Patent Publication No. 2014-186565

Model-based development has the advantage of high visibility and easy understanding of the contents of the program, but since individual models are not explained, detailed models can be used when the entire complex control program is represented by a model. On the contrary, it had the disadvantage that it was difficult to understand. Previously, no method has been proposed to solve these shortcomings while taking advantage of model-based development.
The present invention has been made to solve such a problem, and an object of the present invention is to provide a technique capable of improving the efficiency of model-based development while solving the disadvantage that it is difficult to understand the intention of the program.

The present invention
It is a model creation system that creates a model that expresses the contents of a control program by combining blocks that indicate predetermined processing contents.
A specification input unit that reads specification data that describes the contents of the control program in text, and
A conversion database that stores the correspondence between a plurality of keywords used in the specification data and the block, and
It is provided with a model creation unit that creates the model by referring to the conversion database based on the specification data.
The model creation unit
A plurality of the keywords are sequentially extracted from the beginning of the specification data and replaced with the plurality of blocks.
By connecting the corresponding input / output between the blocks, it can be configured as a model creation system that creates the model.

Since the specification data in the present invention describes the contents of the program in text, there is an advantage that the intention of the program can be easily understood if it is a small-scale program such as an individual module. According to the present invention, a model can be automatically created by reading such specification data and replacing it with a block. If the models created in this way are combined to construct the entire program, the development of the specification data that makes it easy to understand the intention is applied to each module, and the entire program is highly visible. The model can be utilized, and efficient development that takes advantage of both can be realized.

Arrangement on a block in the present invention means creating data representing a model according to the environment used in model-based development, for example, Matlab (registered trademark), Simulink (registered trademark), and the like. Similarly, the notation rules of the model may be those according to the environment. In the present invention, the keyword is replaced with a block by using the conversion database, and at this time, the notation rule according to the block is also applied. The notation rules may be stored in the conversion database together with the block, or when replaced with a block, the environment used in model-based development can be called to use the functions provided under that environment. You may do it.
The description content and description format of the specification data can be determined arbitrarily. It may be written in a natural language that is easier for developers to understand. Further, it may be described in a format such as a highly objective logical formula or mathematical formula. The correspondence between blocks and keywords can also be determined arbitrarily. The keyword can take various forms such as one character, a plurality of character strings, and a specific symbol.

Further, the model creation unit may have a function of determining the arrangement of the plurality of blocks according to the notation rules of the model so that the processing contents corresponding to the blocks are realized. For example, if a rule that represents the flow of processing from input to output is set as a notation rule of the model from left to right, it is visually understood by arranging each block according to the flow. You can create an easy model.
The arrangement of this block may be performed after replacing the block with a block based on the specification data and before the connection, or may be performed after the connection is completed.

In the model creation system of the present invention,
The keyword may be hierarchically configured based on the processing content.

Hierarchical means a structure consisting of keywords in the upper layer corresponding to the processing content of the upper layer and keywords or processing contents belonging to the lower layer of each keyword or processing content. The hierarchy may be two layers or three or more layers. By making it hierarchical in this way, it is possible to express even if the contents of the program are complicated.

In the model creation system of the present invention,
It has a keyword database that associates standard keywords for the processing content with keywords in other notations.
Prior to the creation of the model, or in parallel with the creation of the model, a standardization processing unit for adjusting the keywords of the specification data into standard keywords by referring to the keyword database may be provided.

By doing so, the specification data can be flexibly described. In addition, by adjusting the specification data to standard keywords, it becomes possible to easily and stably create a model.
The keyword database can have various correspondences. For example, if the standard keyword is English and the other keywords are Japanese, it is possible to describe the specification data in Japanese, which is easier for the developer to understand. As another aspect, a notation that is easy to make an error or a fluctuation of the notation may be associated with the standard keyword as another keyword. By doing so, it is possible to create a model even when the specification data does not match the specified notation.

In the model creation system of the present invention,
The specification data includes a predetermined descriptor for defining the unit for creating the model.
The model creation unit may create the model as a unit model for each unit specified in the descriptor.

By doing so, even if the program has complicated contents, the specification data can be created by dividing it into units. Further, by dividing into units, model creation can be performed easily and stably.
The descriptor for defining the unit can be arbitrarily determined. It may be a single character or a character string.

In the mode of creating the unit model described above,
The model creation unit further
Prioritize a plurality of the unit models based on the description of the specification data, and set the priority.
The corresponding input / output may be connected between the unit models to create a model corresponding to the entire specification data.

By doing so, it is possible to automate the connection between the unit models, and there is an advantage that the model can be efficiently created without error.
As the priority, for example, the beginning of the text of the specification data may have a higher priority, and the priority may be lowered in order toward the end of the sentence. The reverse may also be true. Further, a number, a letter, and a symbol indicating a priority may be attached to each unit model, and the priority may be determined based on the numbers, letters, and symbols.

In the model creation system of the present invention,
A join instruction data input unit that reads join instruction data that defines the execution order of a plurality of the models, and a join instruction data input unit.
It is also possible to include a model joining unit that creates a joining model representing a control process corresponding to the joining instruction data by relating the models specified in the joining instruction data to each other according to the joining instruction data. good.

The join instruction data is data that indicates the execution order of a plurality of models. The difference from the specification data is that the order is specified for each model. As the join instruction data, a model layout diagram, that is, the model may be represented by a predetermined figure such as a rectangle, and the parent-child relationship between the models and the execution order may be defined by the layout. Further, as in the specification data, the name and execution order of the models to be combined may be specified by text. Further, instead of the model layout diagram, the coordinates and sizes of the figures represented therein may be used to represent the positional relationship between them by text data. By using the join instruction data, particularly the model layout diagram, as described above, there is an advantage that the entire program such as input / output between models, which is an advantage of model-based development, can be easily grasped visually. According to the above aspect, it is possible to efficiently create a binding model according to the binding instruction data.
The model to be combined may include not only the model generated by the model generation system but also the model read from the outside.

In the aspect of creating a joint model,
The join instruction data input unit also inputs an interface list that defines an external input to the join model and an output from the join model to the outside.
The modeling system further
Based on the input / output of each model specified in the join instruction data, an input / output list representing the input / output as the join model is created, and by comparing this with the interface list, the join instruction data can be obtained. It may be provided with a list creation unit for determining an abnormality.

By doing so, it is possible to easily find the input / output to the combined model or the error of each model included in the combined model.

In the aspect of creating a joint model,
It is equipped with a trigger generator that creates a trigger signal creation block for activating each model specified in the join instruction data.
The trigger generator is
A trigger signal for activating each model is extracted from the input of each model specified in the join instruction data.
Based on the extraction result, a trigger signal creation block is added to the coupling model so as not to overlap.
The trigger signal creation block may be connected to the corresponding model.

Each model has a fixed start timing, such as every 16 ms. Each model is activated by inputting a trigger signal at such a timing. According to the above aspect, the trigger signal creation block can be automatically created according to the trigger signal.

In the aspect of creating a joint model,
It is provided with a connection part for connecting the corresponding input / output between each model specified in the connection instruction data.
The connection part is
The execution order of each model is specified based on the join instruction data, and the execution order is specified.
If the output of the model is the input of another model that is executed after the model, connect the two directly.
When the output of the model becomes the input of another model executed before the model, the two may be connected by interposing a block indicating to input the contents in the previous process.
When the join instruction data is a model layout diagram, the execution order is specified based on the positional relationship of each model represented therein.

According to the above aspect, each model can be connected, and a model including input / output between connected models can be created. Further, when connecting, the processing contents can be appropriately executed by interposing a block indicating that the contents in the previous processing are input in consideration of the execution order of the model.

The present invention does not necessarily have all of the above-mentioned features, and some of them may be omitted or combined as appropriate. The above-mentioned model creation may be configured as a model creation method executed by a computer, or may be configured as a computer program for causing the computer to perform such a method. Further, it may be configured as a recording medium that can be read by a computer that has recorded such a computer program.

It is explanatory drawing which shows the structure of the model making system. It is explanatory drawing which shows the example of the specification data. It is explanatory drawing which shows the example of a model. It is a flowchart (1) of a model creation process. It is a flowchart (2) of a model creation process. It is explanatory drawing which shows the example of the conversion database. It is explanatory drawing which shows the example of the connection between a subsystem. It is explanatory drawing which shows the example of a combination process of a model. It is a flowchart (1) of a model combination process. It is a flowchart (2) of a model combination process. It is a flowchart of a connection process.

Hereinafter, a model creation system as an embodiment of the present invention will be described.
FIG. 1 is an explanatory diagram showing a configuration of a model creation system. The model creation system 100 reads the input data 10 including the specification data 11 and the model layout data 12, and creates a model from the input data 10.

A: Specification data and model contents:
First, the contents of the specification data and the model in this embodiment will be described.
FIG. 2 is an explanatory diagram showing an example of specification data. The specification data of the embodiment is composed of text data. The leftmost lines L1 to L18 in the example of FIG. 2 are line numbers assigned for convenience of explanation. The "■" in line L1 represents the unit of the program for control. Paragraphs (a) (lines L2 to L7), paragraphs (b) (lines L8 to L15), and paragraphs (c) (lines L16 to L18) represent conditions and processing when the conditions are satisfied. In the example of FIG. 2, the lines L3 to L5 following "(a) [Condition] startup" indicate the condition in paragraph (a). Then, when this condition is satisfied, the content is such that the processing indicated by "[processing]" (row L6) and the next row (row L7) is realized.
Further, paragraph (b) (lines L8 to L15) is a processing content when the condition of paragraph (a) is not satisfied. Similar to paragraph (a), lines L9 to L13 following "(b) [Condition] start-up" (line L8) indicate the condition in paragraph (b). Then, when this condition is satisfied, the content is such that the processing shown in "[Process]" and the next line is realized.
Further, the paragraph (c) is a processing content when the conditions of the paragraphs (a) and (b) are not satisfied. Since "[Process]" is described in the line following "(c) [Condition] Other than the above", it means that paragraph (c) is applied unconditionally.
The description of the specification data shown in FIG. 2 is an example, and the rules for describing the specification data can be arbitrarily determined.

FIG. 3 is an explanatory diagram showing an example of a model. An example of a model corresponding to the specification data shown in FIG.
“(A) [Condition] start-up” in line L2 represents a conditional branch, and in the model of FIG. 3, the block b12 corresponds to this. That is, the line representing the conditional branch can be replaced with the block b12 to create a model. Since the conditions in the conditional branch of row L2 are represented by rows L3 to L5, they may be arranged so as to be inputs to block b12 while replacing each of them with blocks as shown below.
Block b1 corresponds to "accel_request_flag" in the condition of "accel_request_flag == 1" in line L3 indicating the content of the condition. The code "1" is displayed in the block b1, which is associated with "accel_request_flag" by a variable table prepared separately. “==” Corresponds to block b3, and “1” of “accel_request_flag == 1” corresponds to block b2. Further, the "AND" portion is represented by replacing it with the block b7.
Block b4 corresponds to "accel_opening" in line L4. The code "2" is associated with "accel_opening" by the variable table. “>” Corresponds to block b6, and “ACCEL_OPEN_THR” corresponds to block b5. Then, since the result of the row L4 constitutes a part of the condition of "AND" of the row L3, it is input to the block b7.
Since "OR" in row L4 represents the logical sum of the output of the "AND" condition represented by rows L3 and L4 and the condition in row L5, it is replaced with block b8 and blocked. The output of b7 and the output of blocks b9 to b11 representing the line L5 are input.

In the process (line L6) when the above conditions are satisfied, among "accel_command_flag = 1", "accel_command_flag" corresponds to the code "6" of the block b14, and "1" corresponds to the block b13. “==” Corresponds to the point that the block b13 is input to the content representing the processing when the condition is satisfied in the block b12 of the conditional branch.
Similarly, a model can be created by substituting the rows L8 to L18 of the specification data (FIG. 2) with the corresponding blocks.

B. Configuration of modeling system:
Returning to FIG. 1, the configuration of the model creation system 100 will be described.
The model creation system 100 can be configured by installing a computer program that realizes each functional block shown in the figure on a computer having a CPU and a memory. The modeling system 100 may be configured by software in this way, or at least a part or all of the functional blocks may be configured by hardware.
The contents of each functional block will be described below.

The specification input unit 101 reads the specification data 11 in the format shown in FIG. The read data is stored in the input data storage unit 111 set in the storage unit 110.
The model layout drawing input unit 102 reads the model layout drawing data 12. The model layout data 12 is data for instructing specifications for creating one model by combining a plurality of models as shown in FIG. 3, and is the data for instructing the combination instruction data of the present invention. It is a kind. The specific contents will be described later. The read model layout data 12 is stored in the input data storage unit 111 in the storage unit 110.

The standardization processing unit 103 standardizes the keywords included in the input specification data 11. The keyword refers to a notation for specifying a block to be replaced, for example, "[condition]" in line L2 of the specification data in FIG. In this embodiment, various expressions are allowed for some keywords while using the notation in English as a standard. For example, for the notation [condition], [IF] can be used as the standard notation. The keyword database 104 is a database that stores a standard notation (for example, [IF]) in association with another notation (for example, [condition]). The standardization processing unit corrects the keywords of the specification data 11 to the standard notation while referring to the keyword database 104. However, it does not mean that the specification data replaced with the standard notation is newly created, but the content of the specification data read into the input data storage unit 111 may be modified.
As the standardization process, as described above, in addition to the mode of conversion from Japanese to English or vice versa, fluctuation of notation may be included. For example, regarding the processing content of "preserving the previous value" in line L18 of FIG. 2, while using this notation as a standard, "retaining the previous value", "value of the previous step", etc. are used as fluctuations in the notation in the keyword database 104. You may remember it.
As described above, by performing the standardization process, it is sufficient to prepare the model described later on the premise of the standardized notation, and the process can be simplified and stabilized.

The model creation unit 106 performs a process of creating a model based on the specification data 11. As shown in FIG. 2, the specification data 11 includes various keywords indicating the processing contents. The correspondence between the blocks constituting the model and the keywords is stored in the conversion database 107. The model creation unit 106 creates a model by replacing the keywords included in the specification data 11 with a model according to the conversion database 107. The created model is stored in the model storage unit 112 provided in the storage unit 110.

When the model is created, a plurality of models are combined to construct a more complicated control program based on the model layout data 12. The following functional blocks are for combining models.
First, the list creation unit 105 creates an input / output list for the combined model created by combining a plurality of models. Specifically, this input / output list can be created by aggregating the input / output of each model used in the combined model. The created input / output list is stored in the storage unit 110.

The input / output list may be created by the developer together with the model layout data 12 and input to the model creation system 100. In such a case, the list creation unit 105 may create an input / output list based on the model layout diagram and determine whether the list input by the developer has an error.

The model coupling unit 115 combines a plurality of models based on the model layout data 12. The combined model is stored in the model storage unit 112.
The trigger generation unit 116 specifies the timing at which each model used for the coupling model is activated, and sets a block for transmitting a trigger signal according to each timing in the model. By doing so, it becomes possible to start a plurality of models at appropriate execution timings.
The connection unit 117 extracts the input / output of a plurality of models, and connects the inputs and outputs having the same name to each other. This allows the transfer of appropriate variables between models. In addition, the connection unit 117 considers the execution order of each model, and when the output value of the model executed earlier is input to the model to be executed after that, both are directly connected. On the contrary, when the output value of a certain model is input to the model executed earlier than that, the connection is made with a block indicating that the value of the previous step is input.

The display control unit 118 performs various displays in the model creation system 100. For example, display of specification data 11 and model layout data 12, display of created model, display of various information necessary for model creation, display of screen for developer to make various specifications. And so on. Further, the display control unit 118 may be able to switch the display mode of the connection of the connection model according to the instruction of the developer. For example, in the model, the input / output may be connected by a visible line, or the line connecting the corresponding input / output may be omitted, and both may be displayed in the same color, symbol, etc. to show the correspondence. You may do it. Such switching may be switchable for each input / output variable, may be switchable as a whole, or may be switchable only for input / output display for the model in units of models used for the combined model. good. By making it possible to realize such various displays, it is possible to display the model or the combined model in a state that is easy for the developer to understand, and it is possible to improve the development efficiency.

The model creation system 100 can have various configurations other than those shown in FIG. Functional blocks other than those shown in FIG. 1 may be used, some of them may be realized by a plurality of functional blocks, or a plurality of functional blocks may be integrated into one. Further, in this embodiment, an example using a computer operating standalone is shown, but some of the illustrated functions may be provided by a plurality of servers connected by a network.

C. Modeling process:
Hereinafter, the processing executed by the model creation system 100 will be described.
4 and 5 are flowcharts of the model creation process. This is the process of creating a model based on the specification data. This process is mainly executed by the standardization processing unit 103 and the model creation unit 106 of FIG. 1, and is a process executed by the CPU of the computer constituting the model creation system 100 in terms of hardware.

When the process is started, the model creation system 100 selects the specification data to be created (step S10). When a plurality of specification data are read in advance, the model creation system 100 may present a list of these specification data to the developer so that the developer can select from them, or the model. May automatically select uncreated specification data. Further, the developer may instruct "new reading" to select the specification data to be newly read as the target of model creation.

Next, the model creation system 100 reads the selected specification data (step S11). If it is already stored in the input data storage unit 111, it may be read from there.

Then, the model creation system 100 creates a database of constants based on the specification constant table (step S12). In the example of the specification data in FIG. 2, "ACCEL_OPEN_THR" in row L4 is a constant, that is, a threshold value for determining a condition. The constant table is a list in which the names of the constants used in the specification data and specific values are associated with each other. The constant table is data created by the developer together with the specification data and input to the model creation system 100.

Next, the model creation system 100 standardizes the description of the specification data based on the keyword database 104 (step S13). The standardization process is as described above as a function of the standardization process unit 103. For example, for a keyword such as "[condition]" in line L2 of the specification data in FIG. 2, refer to the keyword database 104 and replace it with the notation registered as a standard notation (for example, [IF]). To do. If the notation used in the specification data is already the standard notation, the processing is skipped and the process proceeds to the processing of the next keyword.
As standardization, as described above, it is possible to replace languages such as Japanese and English, and to correct fluctuations in notation.

Note that standardization is not an essential process, and it is possible to omit it. In that case, if various keyword notations such as [Condition] and [IF] are allowed for the same process in the specification data, the program is constructed so that each of these is appropriately replaced with a block. There is a need to. Similarly, if this is allowed for notational fluctuations, it is necessary to construct a program so that each notational fluctuation is appropriately replaced with a block. If the notation is not allowed to fluctuate, it is necessary to describe the specification data as specified, which results in inflexibility.
In this embodiment, by performing the standardization process, such a problem can be avoided, and it is possible to simplify and stabilize the replacement process with a block.

When the standardization process is completed, the model creation system 100 performs a process of dividing the specification data into chapters (step S14). A chapter is one of the units that make up a program. In this embodiment, the chapter is defined by the descriptor "■". In the example of FIG. 2, only one place is described at the beginning of the sentence of line L1, but one chapter is composed until "■" is described next. By dividing the program into chapters in this way, there is an advantage that even complicated programs can be described in an easy-to-understand manner.
The descriptor that defines the chapter is not limited to "■" and can be arbitrarily determined. Further, it does not have to be a single character and may be defined by a character string.

Moving to FIG. 5, the model creation system 100 selects a chapter (subsystem) to be processed (step S15). Basically, the unprocessed chapters may be selected in order from the beginning of the specification data, but the developer may be able to specify them individually.
The subsystem represents a unit model created based on the chapter.

When the chapter to be processed is determined, the model creation system 100 reads the unprocessed top sentence of the specification data in that chapter (step S16). Then, the processing methods are classified according to the keywords included in the read sentence (step S17).

The classification of the processing method will be described with reference to FIG.
FIG. 6 is an explanatory diagram showing an example of a conversion database. As shown in the figure, the conversion database stores the keywords and the processing contents in association with each other. A block representing the process is stored in the process content according to the environment of model-based development.
In the example of the figure, a series of character strings "[condition]" is a keyword, and the processing content for this keyword is a conditional branch. Therefore, when this keyword appears, a block representing a conditional branch is prepared as in the block b12 in FIG. In the classification of the processing method (step S17 in FIG. 5), the replacement process with the block corresponding to the keyword is performed in this way.

The keywords of this embodiment have a hierarchical structure. For example, the second keyword "=" in FIG. 6 is associated with the processing content of four arithmetic operations, but the lower layers of the four arithmetic operations are further constant maps, keywords such as abs, and keywords for them. The processing contents are associated. By doing so, it is possible to express various four arithmetic operations by combining keywords.
In order to use the keywords prepared in the hierarchical structure in this way, after finding the keyword for the four arithmetic operations "=", it is necessary to move the keyword to be referred to to the lower layer. In the classification of the processing method (step S17 in FIG. 5), the layer of the keyword to be referred to is transferred according to the previously processed keyword, and then the block is replaced with the block according to the conversion database.

The contents of the keywords in the lower layers of the four arithmetic operations will be further described.
The keyword (library function name) means that the function name of the library is described, for example, when "sin" (character string representing a sine function) is described in the specification data. do. In this way, even if the character string is not registered as a keyword in the conversion database, if a function name prepared as a library appears, the corresponding library function is read and the block for processing is read. Will be replaced.

Further, in the conversion database, the keyword and the processing content may be associated with each other on a one-to-many basis. For example, the four arithmetic operators include "/" indicating division, which is associated with two processes: (1) division as four arithmetic operations and (2) multiplication of reciprocals. .. In general, multiplication processing is faster than division processing, so if it is possible to replace it with multiplication in advance, such as division with a constant, use multiplication to improve the speed. Because it can be done. Therefore, as the conversion database, the two processing contents are associated with "/", and one of them is used properly when replacing with a block.
As a keyword for associating a plurality of processing contents in this way, for example, "==" shown in line L3 of the specification data (FIG. 2) can be mentioned. "==" Is a keyword that expresses the condition that the left side and the right side are equal. For example, in a floating point type comparison such as a floating point type variable on the left side and a floating point constant on the right side, a rounding error is used. Due to the influence, the two may not exactly match. In consideration of these circumstances, "==" may be associated with a process of determining whether the left side and the right side match, and a process of assuming that they match if they are within an error range of a predetermined range. ..

In the example of FIG. 6, the keyword is composed of two layers, but three or more layers may be provided. Further, the conversion database may be prepared with a different number of layers depending on the keyword.

Returning to FIG. 5, the model creation process will be described. When the classification of the processing method is completed (step S17 in FIG. 5), the model creation system 100 adds a block based on the variable / constant database. For example, the variable "accel_request_flag" in line L3 of FIG. 2 corresponds to the block b1 of the model of FIG. 3, but the block b1 only represents the reference numeral 1 and the above-mentioned variable name is represented. Not. The variable table associates the variable name with the symbol 1. Further, the constant table is as described for "ACCEL_OPEN_THR" in row L4 of FIG. 2 in step S12 of FIG. The variable / constant database represents a variable table and a constant table. The model creation system 100 adds blocks such as block b1 and block b5 in FIG. 3 based on the variable / constant database.

When the necessary blocks are prepared by the processing of steps S17 and S18 in this way, the model creation system 100 performs the wiring processing between these blocks and corrects the block arrangement (step S19). The wiring process is a process of connecting the corresponding blocks according to the specification data. In addition, the modification of the block arrangement is a process of arranging or aligning the blocks so that the developer can easily see them.

The model creation system 100 repeatedly executes the above steps S16 to S19 until all the statements included in the chapter are completed (step S20). Further, the processes of steps S15 to S20 are repeatedly executed until all the chapters included in the specification data are completed (step S21).

Finally, the model creation system 100 performs wiring processing between chapters (subsystems) and corrects the arrangement between chapters (subsystems) (step S22). The model thus created is stored in the model storage unit 112 shown in FIG.

Here, the connection processing between the subsystems (step S22) will be described.
FIG. 7 is an explanatory diagram showing an example of wiring between subsystems. On the left side of the figure, Chapters 1-1 to 1-3 in the specification data are shown, and on the right side, the corresponding models, that is, the subsystems ss1 to ss3 are shown. The contents of each of the subsystems ss1 to ss3 are represented by a plurality of blocks as shown in FIG. 3, but are shown in a simplified manner in FIG.

In the example of FIG. 7, the input to the subsystem ss1 is two, the “clutch SW signal state” and the “clutch execution flag”, and the output is the “clutch ON flag”. The "clutch ON flag" is an input to the subsystem ss2 together with the "neutral state flag", and the output of the subsystem ss2 is a "clutch release flag". Therefore, the model creation system 100 connects the "clutch ON flag" which is the output of the subsystem ss1 and the "clutch ON flag" which is the input of the subsystem ss2 as the connection processing between the subsystems.
Similarly, the "clutch release flag" which is the output of the subsystem ss2 and the "clutch release flag" which is the input of the subsystem ss3 are also connected.

In the connection processing between the subsystems, the corresponding input / output between the subsystems is found and connected in this way. However, the model creation system 100 switches the mode of connection as follows in consideration of the execution order of each subsystem.

In this embodiment, the specifications are described in the order in which they are executed. That is, in the example of FIG. 7, the execution is performed in the order of Chapter 1-1, Chapter 1-2, and Chapter 1-3. The execution order can be expressed in various ways. For example, a number that regulates the execution order is described together with the descriptor "■" that represents the chapter, such as "■ 01", and this number part is It may be executed in ascending order. According to such an embodiment, there is an advantage that the execution order can be freely changed without moving the specification data in chapter units.

Based on the above-mentioned execution order, the model creation system 100 makes a connection as it is when the output of the chapter executed earlier becomes the input of the chapter executed after that. In the example of FIG. 7, since the output of Chapter 1-1 is the input of Chapter 1-2, these are directly connected. Further, since the output of Chapter 1-2 is the input of Chapter 1-3, these are also directly connected. Even if the output of Chapter 1-1 becomes the input of Chapter 1-3, since Chapter 1-3 is a chapter executed after Chapter 1-1, it may be directly connected.

On the other hand, although not illustrated in FIG. 7, for example, when the output of Chapter 1-2 is the input of Chapter 1-1, the model creation system 100 inputs the value at the time of executing the previous step. The two are connected by interposing a block indicating that the device is to be used. This is because Chapter 1-2 is executed after Chapter 1-1. The same applies when the output of Chapter 1-3 is input to Chapter 1-1 or Chapter 1-2. This makes it possible to enter appropriate values for each chapter (subsystem).

D. Model join processing:
Next, the model joining process will be described. The model combination process is a process of creating a model corresponding to a more complicated program by mutually combining a plurality of models created in the model creation process (FIGS. 4 and 5). The model to be combined can include various models such as a model created by another developer and a model prepared in advance as a general processing content. It is assumed that the model to be combined is stored in the model storage unit 112 of FIG. 1 in advance.

In the following description, in order to avoid confusion due to the content of the term "model", the model to be combined is referred to as a "module", and the combined result is referred to as a "combined model". It shall be.

First, an example of the model combination process is shown, and then the flowchart will be described.
FIG. 8 is an explanatory diagram showing an example of model joining processing. Model layout data is used instead of specification data for instructions to combine modules to create a combined model. FIG. 8A shows an example of model layout data. The rectangles shown in the model layout data represent the models to be combined, that is, the modules m1 to m18. Modules m1 to m18 are predetermined by their names as shown in FIG. 3 with a "model reference module" associated with a model stored in the model storage unit 112, regardless of such association. Includes modules with other functions.

Further, the modules m1 to m12 are included in the rectangle M1, and the modules m13 to m18 are included in the rectangle M2. Such a group including a plurality of modules is referred to as a coupling subsystem M1 and M2 in this embodiment. Further, a relationship in which the coupling subsystems M1 and M2 include modules m1 to m12 and joules m13 to m18, respectively, is referred to as a "parent-child relationship".

The model layout data further defines the execution order by the positional relationship between the modules m1 to m18. In this embodiment, it is assumed that the execution is performed in the order of top to bottom and left to right. For example, for modules m1 to m8, modules m1 to m4 are sequentially executed from the top to the bottom of the left column, and then modules m5 to m8 are executed from the top to the bottom of the right column. .. After that, the modules m9 and m10 on the right side are executed, and the modules m11 and m12 on the right side are further executed. Modules m9 and m10 are slightly shifted to the left and right only so that the developer can easily understand them visually. Even if the left ends of modules m9 and m10 are aligned and represented. The order of module execution does not change.

FIG. 8B shows an example of model combination processing. A rectangle corresponding to the modules m1 to m18 of the model layout data is drawn. The size of each rectangle changes from FIG. 8A because the modules m1 to m18 are adjusted to the size according to the contents of the corresponding model.
In addition, modules m19 and m20 that do not exist in the model layout data have been added. This is a model that generates a trigger signal for activating modules m1 to m18.
Further, based on the input / output of the modules m1 to m18, an input from the outside as the coupling subsystems M1 and M2, an output out to the outside, and the like are added.

FIG. 8C shows the result of performing the wiring process. The corresponding input / output is connected for each module m1 to m20. Similar to the wiring process between subsystems (FIG. 7), the corresponding input / output is found between the modules, and the wiring is performed in consideration of the execution order. That is, when the output of the module executed first becomes the input of the module executed after that, both are directly connected. Further, when the output of the module to be executed later becomes the input of the module to be executed first, the two are connected with a block indicating that the value in the previous step is input in between.

In addition, two modes were prepared for displaying the connection state. The first aspect is, as shown in FIG. 8C, a mode in which a line is drawn and displayed between the corresponding input / outputs. The second aspect is a mode in which the marks attached to the input / output to be connected are displayed in the same shape, color, etc. as shown in sg1 and sg2 in FIG. 8C. The two modes can be freely switched according to the instructions of the developer. By preparing the two modes in this way, it is possible to suppress the complexity of displaying the combined model and make it easier to visually grasp.

Hereinafter, the flowcharts of the model connection process and the connection process will be described.
9 and 10 are flowcharts of model combination processing. It is a process mainly executed by the list creation unit 105, the model coupling unit 115, and the trigger generation unit 116 in FIG. 1, and is a process executed by the CPU of the model creation system 100 in terms of hardware.

When the process is started, the model creation system 100 reads the model layout data and the interface list (step S30), and sets the parent-child relationship of the module (step S31). In the example of FIG. 8, the parent-child relationship between the coupling subsystem M1 and the modules m1 to m12 and the parent-child relationship between the coupling subsystem M2 and the modules m13 to m18 are set. The interface list is a list of inputs and outputs for the entire join model, created by the developer.

Next, the model creation system 100 creates an input / output list of the combined model based on the input / output of each module (step S32). An example of listing is shown in the figure. In the example of the figure, the inputs a and b of the module A, the inputs b and c of the module B, and the inputs d and e of the module C are extracted so as not to overlap, and the inputs are a, b, c and d. , E are extracted. Further, by extracting the output d of the module A, the output e of the module B, and the output f of the module C so as not to be extracted, d, e, and f are extracted as the outputs.

Next, the model creation system 100 checks the consistency between the input / output list created in step S32 and the interface list (step S33). In this embodiment, first, it is checked whether the inputs of both are the same. If there is a shortage in the input / output list input with respect to the interface list input, it is judged to be abnormal. On the other hand, if there is a surplus in the input / output list input with respect to the interface list input, it is not necessarily an abnormality. This surplus input may be a variable used only in the join model. Therefore, the model creation 100 refers to the output of the module in the combined model, and if the same variable as the surplus input exists, it is determined that there is no abnormality. By doing so, it is determined whether or not there is an abnormality in the input.
Next, regarding the output, the model creation system 100 compares the output of the interface list with the output of the input / output list. If the output of the input / output list is insufficient for the output of the interface list, it means that the output is not output from any module, so it is judged to be abnormal. On the other hand, if the output of the input / output list is excessive with respect to the output of the interface list, it is not possible to specify whether it is normal or abnormal. If this surplus output is used only as an input of another module, it is normal because it is a variable used only in the join model. Therefore, in the embodiment, it is determined that the input / output is abnormal when the input / output output is insufficient.

When an abnormality is found by the above check (step S34), the model creation system 100 outputs an error (step S35) and ends the model combination process. By doing this, it is possible to reduce the possibility of overlooking any abnormalities in the binding of the models.
The processes of steps S32 to S35 are not essential and may be omitted.

Next, the model creation system 100 creates a parent join subsystem (step S36). In the example of FIG. 8, the coupling subsystems M1 and M2 will be created.
However, at this point, since the contents of the combined subsystems M1 and M2 have not been created yet, the combined subsystem M1 can be said on the output diagram of the combined model (FIG. 8 (b)). , A rectangle representing M2 will only be drawn.

Next, the model creation system 100 associates a model with each module (step S37). In the output diagram of the combined model (FIG. 8 (b)), blocks of the corresponding model (such as the example shown in FIG. 3) may be drawn in the rectangle representing the module, or simply in the memory of the computer. It may be associated with. By making this association, the size of the model corresponding to each module, that is, the two-dimensional area of the area occupied by the model or the like shown in FIG. 3 can be specified. Therefore, in step S37, the size of each module may be modified according to this area. Since the size of the area indicated by the model is considered to reflect the complexity of the model to some extent, it is easier to intuitively recognize the complexity of each module by modifying the size of the module in this way. There is an advantage.

The model creation system 100 then adds an input / output block based on the input / output list (step S38). The input / output block for the entire join model can be specified by referring to the interface list. Inputs and outputs for the entire combined model are added, such as input in and output out in the output diagram (FIG. 8 (b)).

Further, the model creation system 100 extracts a trigger signal from the inputs of each module (step S39). Various start timings are defined for each module, such as one that starts every 4 ms and one that starts every 16 ms. This activation timing may be specified by the specification data or the model layout data. In addition to these data, a list that defines the startup timing of each module may be prepared. Since the input block of the trigger signal corresponding to the activation timing is added to each module in step S38, the model creation system 100 extracts this.

Then, the model creation system 100 avoids duplication based on the trigger signal and creates a trigger signal generation block (step S40). For example, if only the trigger signal of 4 ms is extracted in the process of step S39, only the trigger signal generation block that generates the trigger signal of 4 ms may be created. If two types of trigger signals, 4 ms and 16 ms, are extracted, two types of trigger signal generation blocks corresponding to these will be created.
The trigger signal generation block is created for each of the coupling subsystems M1 and M2. In the output diagram (FIG. 8 (b)), the modules m19 and m20 each represent a trigger signal generation block. The trigger signal generation block may be created as a block common to the coupling subsystems M1 and M2.
With the above, the model combination process is completed, and the model creation system 100 then shifts to the connection process for connecting the modules.

FIG. 11 is a flowchart of the connection process. It is a process mainly executed by the connection portion 117 of FIG. 1, and is a process executed by the CPU of the model creation system 100 in terms of hardware.
When the process is started, the model creation system 100 reads the combined model (step S50). Then, the input / output is listed for each module (step S51). In the example in the figure, the inputs a, b and the output d are extracted for the module A, the inputs b, c and the output e are extracted for the module B, and the inputs b, d, e and the output f are extracted for the module C. It is extracted and a list is created.

Based on this list, the model creation system 100 searches for and connects an output having the same name for each input (step S52). However, the wiring is made in the following manner in consideration of the execution order of each module.
If the execution order is forward, that is, the output of the module executed first is the input of the module to be executed after that, both are directly connected. On the other hand, when the execution order is in the opposite direction, that is, when the output of the module executed later is used as the input of the module to be executed first, the wiring is connected with the 1 / z block interposed therebetween. The 1 / z block is a block that means to input the value of the previous step. By doing so, it is possible to realize an appropriate input for each module.
The model creation system 100 repeatedly executes the process of step S52 (step S53) until all the connections are completed, and ends the connection process.

As described in FIG. 8C, in this embodiment, as the display of the connection state, a mode of drawing a line between the input / output and displaying the marks attached to the input / output to be connected have the same shape and color. Two modes of display such as are prepared. Both can be freely switched according to the instructions of the developer. For example, individual inputs or outputs may be specified to switch the display mode, or the entire display mode may be collectively switched from one display to the other. Further, the entire display may be collectively unified into one of the display modes. Further, a certain range such as the coupling subsystem M1 may be specified to switch or unify the input / output display modes for the specified range.

The connection process can be used not only for connection in the connection model but also for connection between chapters (subsystems) between models. In this embodiment, a model is created for each chapter (subsystem) based on the specification data, and an example of performing a process of connecting input / output to each other (see FIG. 7) is shown. However, the model handled by the model creation system 100 is not limited to such an embodiment. For example, as a model corresponding to a chapter (subsystem), an existing model or a model created by another system may be read and processed. The wiring process can also be applied in such a case. Specifically, the read target in step S50 may be changed to a subsystem.

E. Effects and variants:
According to the model creation system 100 described above, a model can be created based on the specification data. In addition, models can be connected and connected using model layout data. As the specification data is displayed as text as illustrated in FIG. 2, there is an advantage that the intention of the developer can be easily understood. On the other hand, the model layout data has an advantage in model-based development, that is, an advantage that it is easy to visually understand the input / output and execution order of each model.
As described above, according to the model creation system 100 of this embodiment, by providing the function of creating a model based on the specification data, the defect of the model-based development that it is difficult to grasp the intention of the developer is compensated for. It is possible to realize program development that also takes advantage of it.

The various features described in this embodiment do not necessarily have all of them, and some of them may be omitted or combined as appropriate. Further, the model creation system 100 of this embodiment is only an example, and various modified examples can be configured.

The present invention can be used to create a model representing the contents of a control program by combining blocks indicating predetermined processing contents.

10 Input data 11 Specification data 12 Model layout data 100 Model creation system 101 Specification input unit 102 Model layout input unit 103 Standardization processing unit 104 Keyword database 105 List creation unit 106 Model creation unit 107 Conversion database 110 Storage unit 111 Input Data storage unit 112 Model storage unit 115 Model coupling unit 116 Trigger generation unit 117 Connection unit 118 Display control unit

Claims (11)

It is a model creation system that creates a model that expresses the contents of a control program by combining blocks that indicate predetermined processing contents.
A specification input unit that reads specification data that describes the contents of the control program in text, and
A conversion database that stores the correspondence between a plurality of keywords used in the specification data and the block, and
It is provided with a model creation unit that creates the model by referring to the conversion database based on the specification data.
The model creation unit
A plurality of the keywords are sequentially extracted from the beginning of the specification data and replaced with the plurality of blocks.
A model creation system that creates the model by connecting the corresponding inputs and outputs between the blocks. The model creation system according to claim 1.
The keyword is a model creation system that is hierarchically configured based on the processing content. The model creation system according to claim 1 or 2.
It has a keyword database that associates standard keywords for the processing content with keywords in other notations.
A model creation system including a standardization processing unit that prepares keywords of the specification data into standard keywords by referring to the keyword database before or in parallel with the creation of the model. The model creation system according to any one of claims 1 to 3.
The specification data includes a predetermined descriptor for defining the unit for creating the model.
The model creation unit is a model creation system that creates the model as a unit model for each unit specified in the descriptor. The model creation system according to claim 4.
The model creation unit further
Prioritize a plurality of the unit models based on the description of the specification data, and set the priority.
A model creation system that connects the corresponding input / output between the unit models and creates a model corresponding to the entire specification data. The model creation system according to any one of claims 1 to 5.
A join instruction data input unit that reads join instruction data that defines the execution order of a plurality of the models, and a join instruction data input unit.
A model creation system including a model join unit that creates a join model representing a control process corresponding to the join instruction data by relating the models specified in the join instruction data to each other according to the join instruction data. .. The model creation system according to claim 6.
The join instruction data input unit also inputs an interface list that defines an external input to the join model and an output from the join model to the outside.
The modeling system further
Based on the input / output of each model specified in the join instruction data, an input / output list representing the input / output as the join model is created, and by comparing this with the interface list, the join instruction data can be obtained. A model creation system equipped with a list creation unit that determines abnormalities. The model creation system according to claim 6 or 7.
It is equipped with a trigger generator that creates a trigger signal creation block for activating each model specified in the join instruction data.
The trigger generator is
A trigger signal for activating each model is extracted from the input of each model specified in the join instruction data.
Based on the extraction result, a trigger signal creation block is added to the coupling model so as not to overlap.
A model creation system that connects the trigger signal creation block to the corresponding model. The model creation system according to any one of claims 5 to 8.
It is provided with a connection part for connecting the corresponding input / output between each model specified in the connection instruction data.
The connection part is
The execution order of each model is specified based on the join instruction data, and the execution order is specified.
If the output of the model is the input of another model that is executed after the model, connect the two directly.
When the output of the model is the input of another model executed before the model, a model creation system that connects the two with a block indicating that the contents of the previous process are input. This is a model creation method in which a computer creates a model that represents the contents of a control program by combining blocks that indicate predetermined processing contents.
As a step performed by the computer
A specification input step for reading specification data in which the contents of the control program are described in text, and
A reference step that refers to a conversion database that stores the correspondence between a plurality of keywords used in the specification data and the block, and
A model creation step for creating the model by referring to the conversion database based on the specification data is provided.
The model creation step is
A plurality of the keywords are sequentially extracted from the beginning of the specification data and replaced with the plurality of blocks.
A model creation method, which is a step of creating the model by connecting the corresponding input / output between the blocks. It is a computer program for creating a model representing the contents of a control program by combining blocks indicating the processing contents predetermined by a computer.
A specification input function that reads specification data that describes the contents of the control program in text, and
A reference function that refers to a conversion database that stores the correspondence between a plurality of keywords used in the specification data and the block, and
A computer realizes a model creation function that creates the model by referring to the conversion database based on the specification data.
The model creation function is
A plurality of the keywords are sequentially extracted from the beginning of the specification data and replaced with the plurality of blocks.
A computer program that is a function of creating the model by connecting the corresponding input / output between the blocks.

Images