JP5831385B2 - Model comparison device and model comparison tool - Google Patents

Description

  The present invention relates to a model comparison device used for program development using a model for automatically generating source code.

  Conventionally, in the development of a program for a vehicle engine ECU, for example, the developer may not describe the source code directly, but may describe the function of the target program in the form of a model that is easier to create and has better visibility. is there. This model represents processing by a combination of blocks, which are functional units that perform various operations, and connections that indicate data input / output between blocks, and program development that automatically generates source code based on such models Is called model-based development.

  Here, Patent Document 1 describes a program inspection apparatus that replaces a block that realizes a specific operation process in a model with an inspection block that executes the operation process and can output an intermediate result of the operation process. ing. According to this program inspection apparatus, the intermediate result of the arithmetic processing obtained by executing the program generated from the model before replacement and the intermediate result of the arithmetic processing obtained by simulating execution of the model after replacement are obtained. Can be compared. For this reason, it is possible to detect an abnormality in a model or a program with high accuracy.

JP 2008-310513 A

  By the way, a comparison tool for comparing two models and detecting a difference is known. By using such a comparison tool, when a new model is created by changing an existing model, the changes between these models can be easily grasped. It becomes easy to do.

  On the other hand, with an increase in the scale of a model, for example, a change (subsystemization) may be performed on an existing model, for example, by combining a plurality of blocks and their connection lines into one block (subsystem). . In addition to this, for example, when a subsystem is eliminated, when one block group (a plurality of blocks connected directly or indirectly by connection) is divided, or when a plurality of block groups are Sometimes they are integrated into one.

  However, the conventional comparison tool simply compares the types and number of blocks constituting the two models, the parameters of the same type of block, the connection destination of the connection, and the like. For this reason, for example, when a subsystem is formed, the subsystem and the blocks constituting the subsystem can be changed even if the types of blocks constituting the subsystem, the parameters of the blocks and the connection are not changed, etc. And connections were mistakenly detected as new additions.

  In other words, the conventional comparison tool cannot compare the two models with high accuracy, and in the case of subsystemization, etc., even if the comparison result is referred to, the processing realized by these models is not possible. I couldn't figure out how it changed.

  This invention is made | formed in view of the said subject, and it aims at providing the model comparison apparatus etc. which can show the substantial difference in two models.

A model comparison apparatus according to an aspect of the present invention includes a block indicating a predetermined processing procedure and a connection representing input / output of data between the blocks by connecting the blocks, and the configuration An original model, which is a model in which a program is described using elements and a unique identifier is set for each component, and a change is made to the original model. The diverted component includes a reading unit that reads a change model in which the same identifier is set.

  In addition, two constituent elements having the same identifier are detected from the constituent elements included in the original model and the constituent elements included in the change model, and the parameters set in these constituent elements are compared. Comparing means is provided. In addition, with respect to the original model and the changed model, based on identifiers set for the components of these models, detection means for detecting a component used only in one of these models, and a comparison result by the comparison means And presenting means for presenting the detection result by the detecting means.

  According to such a configuration, it is possible to accurately specify a component diverted from the original model to the changed model, a newly added component in the changed model, or a component deleted from the original model.

  For diverted components, the comparison results of the parameters in the original model and the parameters in the modified model are presented, and the newly added components in the modified model and the components deleted from the original model are presented. Is done.

  For this reason, even if subsystemization, subsystem elimination, block group division, integration, etc. are performed, the process that is substantially the same as the original model in the changed model is performed from the presented content. It is possible to easily discriminate between parts that are to be processed and parts that are subjected to substantially different processing.

Therefore, according to the model comparison apparatus according to one aspect of the present invention, it is possible to grasp a substantial difference between the original model and the changed model.
In addition, there may be a case where a plurality of model creation devices that create models used in such a model comparison device are used, and one model is created by integrating the models created by these model creation devices.

The identifier generation device according to one aspect of the present invention is created by these model creation devices in response to requests from a plurality of model creation devices for creating a model used in the model comparison device described above. An identifier generating means for generating an identifier set for each model component so as to be unique in these models, and a model that has issued a request for generating the identifier generated by the identifier generating means. Providing means for providing to the creating apparatus;

  By using such an identifier generation device, it is possible to prevent an identifier set in a component from being duplicated in a model created by a plurality of model creation devices. For this reason, even when a plurality of models created by a plurality of model creation devices are integrated to create a single model, the same identifier is repeatedly set for the constituent elements of the model. Can be prevented. Therefore, when a change is made to the integrated model, it is possible to grasp a substantial difference between the change before and after the change using the model comparison apparatus described above.

Further, the model creation device according to one aspect of the present invention includes a block indicating a predetermined processing procedure and a connection representing input / output of data between these blocks by connecting the blocks, Model generating means for generating a model in which a program is described using the constituent elements according to an instruction from the user, and setting means for setting a unique identifier for the constituent elements.

  When a model is created using such a model creation device, when a change is made to the model once created, the above-mentioned model comparison device is used to make a substantial difference before and after the change. Can be grasped.

It is a block diagram about a PC that operates as a development support apparatus and a server that operates as an identifier generation apparatus. It is a block diagram about a development support tool and an identifier generation tool. It is a flowchart of the difference detection process in 1st embodiment. It is a flowchart of the difference detection process in 1st embodiment. It is a flowchart of the identifier setting process in 1st embodiment, and the flowchart of an identifier update process. It is a block diagram which shows an example of the original model in 1st embodiment, and an example of the parameter information of the connection in an original model. It is a block diagram which shows an example of the change model in 1st embodiment. It is an example of the comparison result of the original model in 1st embodiment, and a change model. It is a flowchart of the difference detection process in 2nd embodiment. It is a flowchart of the difference detection process in 2nd embodiment. It is an example of the comparison result of the original model in 2nd embodiment, and a change model.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. The embodiment of the present invention is not limited to the following embodiment, and can take various forms as long as they belong to the technical scope of the present invention.

[Description of configuration]
FIG. 1A shows personal computers (A to CPC) 1 a to 1 c and a server 2 connected to a network 5. The PC 1 operates as a development support apparatus in model-based development, and includes a display 10, an HDD 20, a CPU 30, a ROM 40, a RAM 50, an input device 60, and the like (see FIG. 1B).

The display 10 displays the video signal received from the CPU 30 as a video to the user.
The input device 60 includes a keyboard, a mouse, and the like, and outputs a signal corresponding to the operation to the CPU 30 when operated by the user.

  The RAM 50 is a readable / writable volatile memory, the ROM 40 is a read-only nonvolatile memory, and the HDD 20 is a readable / writable nonvolatile memory. In the ROM 40 and the HDD 20, programs that are read and executed by the CPU 30 are stored in advance.

  When the CPU 30 executes a program stored in the ROM 40 or the HDD 20, the RAM 50 is used as a storage area for temporarily storing the program and a storage area for temporarily storing work data. .

  The CPU 30 reads the OS from the HDD 20 and executes it, and executes various programs recorded in the HDD 20 as processes on the OS. In this process, the CPU 30 receives a signal input from the input device 60 as necessary, outputs a video signal to the display 10, and controls data read / write to the RAM 50 and the HDD 20.

  On the other hand, the server 2 operates as an identifier generation device that generates an identifier (details will be described later) used in the development support device connected to the server 2 via the network 5 and has the same configuration as the PC 1. doing.

  Next, the development support tool 100 installed in the PC 1 will be described with reference to the block diagram shown in FIG. The development support tool 100 is one of the applications stored in the HDD 20 and executed as a process on the OS. The PC 1 operates as the development support tool 100 and operates as a development support apparatus that creates and compares models. Operate. The development support apparatus can be used for developing a program for an embedded system such as an in-vehicle apparatus. However, the development support apparatus is not limited to this and can be used for developing a program for any application.

The development support tool 100 includes a model creation unit 110, an identifier setting unit 120, and a model comparison unit 130, and is activated by an operation of the input device 60.
The model creation unit 110 creates a model in accordance with an operation on the input device 60, and generates source code from the model.

  Here, a model is an expression form of a program created based on a model language specification that is defined for the purpose of making description easier than the source code and improving human readability.

  An example of the model is a Simulink model created by Simulink (registered trademark). By inputting the Simulink (registered trademark) model into the Real Time Workshop (registered trademark) operating on Matlab (registered trademark), source code corresponding to the model is generated.

  The model in the present embodiment is described as a combination of functional units called blocks indicating a specific processing procedure, and the blocks constituting the model are input / output of data between the blocks and connections indicating the order of the corresponding processing procedures. Connected together.

  Components such as blocks and connections that make up the model have parameters. As a specific example, the block has parameters indicating various setting values such as initial values and threshold values used in the processing procedure, and the connection indicates a data output source block or a data input destination block. It has connection destination parameters.

  An aggregate of a plurality of blocks and connections can be defined as a kind of block called a subsystem. This subsystem is equivalent to a function in programming, and it is allowed to create a nested subsystem in which the subsystem is included in the block. By providing the subsystem, the processing procedure represented by the block, etc. A hierarchical structure is formed. In the source code generated from a model having a subsystem, processing in the subsystem is described as a subroutine.

  Data input / output between blocks (internal blocks) constituting the subsystem and other blocks (external blocks) arranged outside the subsystem is an import block or export block arranged within the subsystem. Is described through The import block and the export block are collectively referred to as a port block.

  That is, when describing the output of data from the external block to the internal block, the external block and the subsystem in which the internal block is arranged are connected by a connection, and the import block and the internal block are connected by a connection. .

  In addition, when describing output of data from the internal block to the external block, the external block and the subsystem in which the internal block is arranged are connected by a connection, and the export block and the internal block are connected by a connection. .

  Note that parameters such as an import block and an export block can specify which connection is connected to the subsystem for data input / output.

  Further, the identifier setting unit 120 sets an identifier for a component (block, connection, etc.) in the model generated by the model creation unit 110. This identifier is unique and does not overlap with an identifier used for a model created by the model creation unit 110 or another development support device, and is generated by the identifier generation device (server 2). .

  Specifically, when a new component is generated by the model creation unit 110, the identifier setting unit 120 issues a generation request for requesting generation of an identifier to the identifier generation device via the network 5. Then, the identifier generated by the identifier generation device in response to the generation request is acquired via the network 5, and the identifier is set as a component.

  The identifier setting unit 120 sets the identifier generated by the identifier generation device as the identifier for the block, and also sets the identifier generated from the identifier set for the block connected to the connection as the identifier for the connection. good. Specifically, for example, an identifier such as “A-B” may be set for a connection connecting a block in which the identifier A is set and a block in which the identifier B is set.

  By doing so, it is possible to more easily generate the identifier set for the connection, and it is possible to prevent the identifier from being exhausted when a large-scale model is created.

  The identifier set for each component is stored in the same file as the identifier information together with information indicating the configuration of the created model. When the file is read, the model and each configuration of the model The identifier set for the element is reproduced. The model creation unit 110 modifies the model reproduced according to the operation on the input device 60, and the identifier setting unit 120 assigns a unique identifier acquired from the server 2 to the newly added component. Set.

  Further, the model creation unit 110 can provide a user with a library subsystem that is a subsystem for performing predetermined arithmetic processing and the like, and a custom subsystem created by the user. A library subsystem or a custom subsystem is used to create a model in response to an operation on the input device 60.

  Further, the model comparison unit 130 compares the two models created by the model creation unit 110, and detects a difference between these models based on identifiers set for each component (details will be described later). ). In the difference detection process, it is conceivable to compare the original model with a modified model generated by modifying the original model.

  Next, the identifier generation tool 200 installed in the server 2 will be described with reference to the block diagram shown in FIG. The identifier generation tool 200 is one of applications that are stored in the HDD and executed as a process on the OS. The server 2 operates as an identifier generation device by operating the identifier generation tool 200.

The identifier generation tool 200 includes an identifier generation unit 210 and a transmission / reception unit 220, and is activated by an operation of the input device.
In response to a generation request from a development support apparatus connected to the own apparatus, the identifier generation unit 210 is a unique identifier of a model component so as not to overlap with an identifier already used in these development support apparatuses. Is generated.

  Specifically, for example, a combination of unique information and a number may be generated as an identifier. The specific information is generated based on, for example, specific information of the development support apparatus (for example, IP address of the development support apparatus) or specific information of the user who uses the development support apparatus (for example, user name). It may be.

  That is, for example, for a model component created by a development support apparatus whose IP address is X, with X as unique information, “X1”, “X2”, “X3”,... The identifiers may be generated in numerical order. Further, for example, “Y1”, “Y2”, “Y3”,..., With Y as unique information for a model component created by a user whose name is Y by any development support apparatus. For example, the identifiers may be generated in numerical order. Of course, a combination of the unique information of the development support apparatus and the unique information of the user may be used as the unique information.

By doing so, it is possible to easily generate a unique identifier used for a model created by a plurality of development support apparatuses.
In addition to this, the identifier generation unit 210 performs an identifier update process (details will be described later) for resetting an identifier set in a model component in response to an update request from the development support apparatus.

  On the other hand, the transmission / reception unit 220 receives an identifier generation request from the development support apparatus via the network 5, and sends the identifier generated by the identifier generation unit 210 via the network 5. Provide to the support device.

[First embodiment]
[Description of operation]
Next, operations of the development support apparatus and the identifier generation apparatus in the first embodiment will be described in detail.

(1) Difference Detection Process First, the difference detection process executed by the model comparison unit 130 of the development support tool 100 will be described using the flowcharts shown in FIGS. This process is executed in response to an operation on the input device 60.

  In the following description, it is described that the process is executed by a specific part constituting the development support tool 100 or the identifier generation tool 200. This is executed by a CPU that operates according to the part. Means that.

In S305, the model comparison unit 130 reads two models (original model and changed model) to be compared from the HDD 20, and shifts the processing to S310.
The original model and the changed model may be configured as one or a plurality of block groups (a group of a plurality of blocks connected directly or indirectly by connection). In addition, the original model and the modified model may include a library subsystem and a custom subsystem. By doing so, it is possible to detect differences between various models.

  In S310, the model comparison unit 130 identifies one of the components of the original model that has not been compared with the component of the changed model as a comparison target, and proceeds to S315. The specified comparison target is also described as a target component.

  In S315, the model comparison unit 130 arranges the target component and the component set with the same identifier as the target component in the changed model (also referred to as a corresponding component) arranged in different layers of each model. Is cleared, and the process proceeds to S320.

  As already mentioned, in the model, a hierarchical structure of the processing procedure is formed by providing a subsystem, and when the subsystem is made in the change from the original model to the changed model, or when the subsystem is eliminated The hierarchical structure changes. The change flag is set when the target component is arranged in a different hierarchy due to subsystemization or subsystem cancellation.

Note that the elimination of a subsystem means that blocks and connections constituting the subsystem are directly arranged in the hierarchy where the subsystem is arranged, instead of the subsystem.
In S320, the model comparison unit 130 determines whether or not the comparison has been performed on all the components in the original model. If an affirmative determination is obtained (S320: Yes), the process proceeds to S325. If a negative determination is obtained (S320: No), the process proceeds to S335.

  In S325, the model comparison unit 130 identifies a component that has not been compared from the changed model, sets “add” as the comparison result of the identified component, and shifts the processing to S330.

  In S330, the model comparison unit 130 saves the comparison result for each component in the original model and the changed model as a file in the HDD 20, and displays the comparison result on the display 10, and the process ends.

  The comparison results for port blocks that exist in one of the original model and the modified model, or that connect to port blocks or subsystems that exist in one of these models and that exist in one of these models May not be displayed.

  Since such components do not make a substantial difference between the original model and the modified model, the display of the comparison results for such components is omitted, so that the user can change the original model and the modified model. Substantial differences in models can be presented.

  On the other hand, in S335, the model comparison unit 130 analyzes the changed model, specifies the same hierarchy as the hierarchy in which the target component is arranged in the original model, searches for the corresponding component from the hierarchy, and proceeds to S340. Migrate processing.

  In S340, the model comparison unit 130 determines whether a corresponding component is detected. If an affirmative determination is obtained (S340: Yes), the process proceeds to S365. If a negative determination is obtained (S340: No), the process proceeds to S345.

In S345, the model comparison unit 130 searches for a corresponding component from a layer other than the same layer in the changed model, and proceeds to S350.
In S350, the model comparison unit 130 determines whether a corresponding component has been detected. If an affirmative determination is obtained (S350: Yes), the process proceeds to S360. If a negative determination is obtained (S350: No), the process proceeds to S355.

In S355, the model comparison unit 130 sets “delete” as the comparison result of the target component, and the process proceeds to S310.
In S360, the model comparison unit 130 sets a change flag, and proceeds to S365.

  In S365, the model comparison unit 130 compares parameters between the target component and the corresponding component. Then, in S370, it is determined whether there is a difference. If the parameters are different (S370: Yes), the process proceeds to S375, and if not different (S370: No), the process proceeds to S420.

  In S375 to S415, whether the connection destination of the target constituent element and the corresponding constituent element that are connected is substantially different, or is it merely different in appearance due to subsystemization or cancellation of the subsystem? Consider and set the comparison result.

  That is, in S375, the model comparison unit 130 determines whether or not the target component and the corresponding component are connected. Furthermore, based on the connection destination parameter, only one connection destination of these components that are connected is different, and the different connection destination is a subsystem or a port block in one component, but the other It is determined whether or not the component is a normal block. The normal block means a block other than the subsystem and the port block.

  If an affirmative determination is obtained in both determinations (S375: Yes), the process proceeds to S380, and if a negative determination is obtained in either determination (S375: No), S405 is performed. The process is transferred to.

  Of the target constituent elements that are connected and the corresponding constituent elements, those in which the different connection destinations are subsystems or port blocks are referred to as indirect connections, and those that are not indirect connections are referred to as direct connections. Also, a normal block that is a different connection destination that is directly connected to the connection is defined as a different block.

In S380, the model comparison unit 130 compares the parameters of the target component and the corresponding component in consideration of the port block and other blocks connected to the subsystem.
In other words, when the connection destination that is different in the indirect connection is a port block, based on the port block parameters, etc., among the connections connected to the subsystem in which the port block is arranged, the connection that inputs and outputs data with the port block Is identified.

  When the connection destination block of the connection is specified and a different block is specified as the block, the indirect connection is considered to be connected to the different block instead of the port block. Make a comparison.

  In addition, when the different connection destination in indirect connection is a subsystem, the indirect connection and data input / output of the connections arranged in the subsystem are performed based on the port block parameters etc. arranged in the subsystem. Identify the connection to be made.

  When the connection destination block of the connection is specified and a different block is specified as the block, the indirect connection is regarded as being connected to the same block instead of the subsystem, and the connection destination parameter Make a comparison.

  In S385, the model comparison unit 130 determines whether or not the parameters are the same, and when an affirmative determination is obtained (S385: Yes), the process proceeds to S390 and a negative determination is obtained. (S385: No), the process proceeds to S405.

  In S390, the model comparison unit 130 determines whether or not the change flag is set. If an affirmative determination is obtained (S390: Yes), the process proceeds to S395. If a negative determination is obtained (S390: No), the process proceeds to S400.

In S395, the model comparison unit 130 sets “subsystem changed and not changed” as a comparison result between the target component and the corresponding component, and the process proceeds to S310.
In S400, the model comparison unit 130 sets “no change” as a comparison result between the target component and the corresponding component, and the process proceeds to S310.

  On the other hand, in S405, the model comparison unit 130 determines whether or not the change flag is set. If an affirmative determination is obtained (S405: Yes), the process proceeds to S410. If a negative determination is obtained (S405: No), the process proceeds to S415.

In S410, the model comparison unit 130 sets “subsystem changed, changed” as the comparison result between the target component and the corresponding component, and the process proceeds to S310.
In S415, the model comparison unit 130 sets “changed” as the comparison result between the target component and the corresponding component, and the process proceeds to S310.

  On the other hand, in S420 that is shifted when the parameters of the target component and the corresponding component match, the model comparison unit 130 determines whether or not the change flag is set. If an affirmative determination is obtained (S420: Yes), the process proceeds to S425. If a negative determination is obtained (S420: No), the process proceeds to S430.

In S425, the model comparison unit 130 sets “subsystem changed and not changed” as the comparison result between the target component and the corresponding component, and the process proceeds to S310.
In S430, the model comparison unit 130 sets “no change” as the comparison result between the target component and the corresponding component, and the process proceeds to S310.

(2) Identifier resetting process Next, an identifier resetting process for resetting the identifier set in each component of the model will be described with reference to the flowchart shown in FIG. This process is executed by the identifier setting unit 120 in the development support tool 100 according to an operation on the input device 60.

  In S505, the identifier setting unit 120 reads identifier information indicating the identifier set for each component of the model from the file in which the model is stored. Then, the identifier information and an update request for the identifier indicated by the identifier information are transmitted to the server 2 via the network 5, and the process proceeds to S510.

  In S <b> 510, the identifier setting unit 120 acquires update information indicating the correspondence between the identifier before update and the identifier after update from the server 2. Then, based on the update information, the regenerated identifier is set for each component for which the pre-update identifier is set, and this process ends.

(3) Identifier Update Process Next, an identifier update process for updating the identifier set for each component of the model will be described with reference to the flowchart shown in FIG. This process is executed by the identifier generation unit 210 in the identifier generation tool 200 in response to the update request received from the development support apparatus.

  In step S <b> 605, the identifier generation unit 210 acquires identifier information indicating the identifier set for each component of the model along with the update request from the development support apparatus via the transmission / reception unit 220.

In subsequent S610, the identifier generation unit 210 updates each identifier indicated by the acquired identifier information.
More specifically, for example, in the case where a combination of a number and predetermined unique information is used as an identifier, among these numbers, an empty number is packed (empty The number may be updated so that there is no number.

  That is, a plurality of identifiers that specify a range of numbers included in each identifier indicated by the identifier information and include numbers arranged in order starting from any number in the range (for example, the number that forms the top of the range) May be regenerated. Then, each identifier indicated by the identifier information may be replaced with a regenerated identifier.

  More specifically, for example, if the identifier information indicates identifiers “X1”, “X10”, “X25”,... With X as unique information, “X1”, The identifiers “X2”, “X3”,... May be regenerated. Then, “X1” may be replaced with “X1”, “X10” may be replaced with “X2”, “X25” may be replaced with “X3”, and the original identifiers may be replaced with regenerated identifiers in numerical order.

  In addition, when the connection identifier is generated based on the identifier of the connection destination block of the connection, the connection block identifier is regenerated along with the regeneration of the connection block identifier. May be.

  Specifically, for example, an identifier “X10-> X20” is set to a connection connecting two blocks in which identifiers “X10” and “X20” are set, and “X10” is “X5”. Assume that “X20” is replaced with “X7”. In such a case, “X5-> X7” may be regenerated as the connection identifier, and “X10-> X20” may be replaced with “X5-> X7”.

By doing so, it is possible to prevent the exhaustion of identifiers while maintaining the uniqueness of the identifiers.
Then, update information indicating the identifier before update and the regenerated identifier that replaces the identifier is generated, and the process proceeds to S615.

In S615, the identifier generation unit 210 transmits the update information to the development support apparatus that has issued the update request via the transmission / reception unit 220, and ends this process.
[Specific examples]
Next, a specific example of the comparison result between the original model and the changed model in the first embodiment will be described. Note that the model in the following description conforms to the Simulink (registered trademark) model.

  FIG. 6A shows an example of an original model 700 created using the development support apparatus of the first embodiment. The original model 700 includes a pulse generation block 710 (Discrete Pulse Generator 1) that generates pulses and an addition / subtraction block 730 (Sum1) that performs addition / subtraction. Further, it has a hold block 750 (Unit Delay 1) for delaying the signal and a signal display block 770 (Scope 1) for displaying the signal (note that the parenthesis indicates an identifier set for each block).

  The original model 700 has a connection 720 for outputting data from the pulse generation block 710 to the addition / subtraction block 730 and the signal display block 770, and a connection 740 for outputting data from the addition / subtraction block 730 to the hold block 750. Further, a connection 760 for outputting data from the hold block 750 to the addition / subtraction block 730 and the signal display block 770 is provided. For these connections, identifiers based on the connection destination block are set (for example, the identifier of the connection 720 is Discrete Pulse Generator1-> Sum1 + Scope1, and the identifier of the connection 740 is Sum1-> Unit. Delay1).

  FIG. 6B shows parameter information 721 indicating each parameter set in the connection 720. The parameter information 721 indicates a connection destination parameter that is an output source of data output via the connection 720, a connection destination parameter that is an output destination of the data, and the like.

  FIG. 7 shows a changed model 800 created by changing the original model 700. This modified model 800 is obtained by substituting the addition / subtraction block 730, hold block 750, and connections 740, 760 in the original model 700, and adding a plurality of blocks for outputting data to the signal display block 770 in the original model 700. is there. Further, the initial parameters for setting the initial conditions of the hold block 750 in the original model 700 are changed.

  That is, the change model 800 includes a pulse generation block 810 (Discrete Pulse Generator 1) and a signal display block 830 (Scope 1) that are diverted from the original model 700. Further, it has a subsystem 820 (Subsystem 1), a fixed value block 840 (Constant 1) for generating and outputting a fixed value, an addition / subtraction block 850 (Sum 2), and a hold block 860 (Unit Delay 2).

  This subsystem 820 is newly added by the above-mentioned subsystemization, and a fixed value block 840, an addition / subtraction block 850, and a hold block 860 are newly added.

  Further, the change model 800 includes a connection 811 for outputting data from the pulse generation block 810 to the subsystem 820 and the signal display block 830, and a connection 831 for outputting data from the subsystem 820 to the signal display block 830. Further, a connection 841 for outputting data from the fixed value block 840 to the addition / subtraction block 850 and a connection 851 for outputting data from the addition / subtraction block 850 to the hold block 860 are provided. Further, a connection 861 for outputting data from the hold block 860 to the addition / subtraction block 850 and the signal display block 830 is provided.

  Further, the subsystem 820 includes an import block 821 (In1) that receives data input from the pulse generation block 810 to the subsystem 820. Further, an addition / subtraction block 823 (Sum1) and hold block 825 (Unit Delay1) diverted from the original model 700 and an export block 827 (Out1) for outputting data from the subsystem 820 to the signal display block 830 are provided.

  Further, the subsystem 820 has a connection 822 for outputting data from the import block 821 to the addition / subtraction block 823 and a connection 824 for outputting data from the addition / subtraction block 823 to the hold block 825. Further, a connection 826 for outputting data from the hold block 825 to the addition / subtraction block 823 and the export block 827 is provided.

  Of course, as in the original model 700, identifiers based on blocks to be connected are set in these connections. Of these connections, the connections 811, 824, and 826 are diverted from the original model 700, and the same identifiers as those of the original model are set.

  FIG. 8 shows a table showing a comparison result between the original model 700 and the changed model 800 by the difference detection process. In the table, each component is indicated by an identifier, and comparison results are omitted for components set without change.

  As shown in the table, the comparison result of the newly added subsystem 820 (Subsystem1) is “added”. In addition, the addition / subtraction block 823 (Sum1) that has only been sub-systemized is “subsystem changed and not changed”, and the hold block 825 (Unit Delay1) whose initial parameters have been changed along with the sub-system is “subsystem “There is a change, there is a change”.

  In addition, the comparison result of the connection connecting the added blocks is “addition”. Further, the connection 811 (Discrete Pulse Generator1-> Sum1 + Scope1) is “not changed” and is not described in the table. In addition, the connection lines 824 and 826 (Sum1-> Unit Delay1, Unit Delay1-> Sum1 + Scope1) connecting the subsystemized blocks are “subsystem changed, not changed”.

The original model 700 and the modified model 800 are composed of one block group, but needless to say, they may be composed of a plurality of block groups.
[Second Embodiment]
[Description of operation]
Next, the operation of the development support apparatus in the second embodiment will be described in detail. In the second embodiment, the content of the difference detection process is different from that of the first embodiment, and the original model and the changed model are compared without considering the subsystemization or the cancellation of the subsystem. Below, the difference detection process of 2nd embodiment is demonstrated using the flowchart as described in FIG. This process is executed in response to an operation on the input device 60.

Since S905 to S955 are the same as S305, S310, S320 to S355, and S365 in the difference detection process of the first embodiment, description thereof is omitted.
In S960, the model comparison unit 130 determines whether there is a parameter difference between the target component and the corresponding component. If the parameters are different (S960: Yes), the process proceeds to S965. If they are not different (S960: No), the process proceeds to S990.

In S965 to S985, as in S375 to S415 in the difference detection process of the first embodiment, a comparison result is set in consideration of subsystemization and subsystem elimination.
That is, in S965, the model comparison unit 130 performs the same determination as S375 in the difference detection process of the first embodiment. If an affirmative determination is obtained (S965: Yes), the process proceeds to S970. If a negative determination is obtained (S965: No), the process proceeds to S985.

  In S970, the model comparison unit 130 compares the parameters of the target component and the corresponding component in consideration of the port block and other blocks connected to the subsystem, similarly to S380 in the difference detection process of the first embodiment. . If these parameters are the same (S975: Yes), the process proceeds to S980. If they are not the same (S975: No), the process proceeds to S985.

In S980, the model comparison unit 130 sets “no change” as the comparison result between the target component and the corresponding component, and the process proceeds to S910.
In S985, the model comparison unit 130 sets “changed” as the comparison result between the target component and the corresponding component, and the process proceeds to S910.

In S990, the model comparison unit 130 sets “no change” as the comparison result between the target component and the corresponding component, and the process proceeds to S910.
[Specific examples]
Next, a specific example of the comparison result between the original model and the changed model by the difference detection process in the second embodiment will be described.

  FIG. 11 shows a table showing the comparison results between the original model 700 and the modified model 800 described above. In the table, each component is indicated by an identifier, and the description of the comparison result is omitted for the component set without change.

  In addition, a description of the comparison results for port blocks that exist in one of these models, or connections that connect to port blocks or subsystems that exist in one of these models and that exist in one of these models Is omitted.

  As shown in the table, the comparison result of the newly added subsystem 820 (Subsystem) is “added”. Also, the addition / subtraction block 823 (Sum1) that has only been sub-systemized is “not changed” and is not described in the table. Is “changed”.

  In addition, the comparison result of the connection connecting the added blocks is “addition”. Also, the connections 811, 824, and 826 (Discrete Pulse Generator1-> Sum1 + Scope1, Sum1-> Unit Delay1, Unit Delay1-> Sum1 + Scope1) connecting subsystems or subsystemized blocks are " Since there is no change, it is not described in the table.

[effect]
According to the development support devices of the first and second embodiments, for the connection in which the connection destination block is changed due to the subsystemization or the cancellation of the subsystem, the connection is made in consideration of the block connected via the port block. A comparison of the destination parameters is performed. Then, it is determined whether the connection destination block has substantially changed.

  For this reason, when the processing is maintained and the subsystem is made or the subsystem is eliminated, and the connection destination of the apparent connection is simply changed, such a change is presented to the user as a difference. There is no. On the other hand, when the processing is changed into a subsystem and the connection destination is substantially changed, such a change is presented to the user.

Therefore, only the substantial differences that have occurred as a result of sub-systemization or sub-system elimination can be presented to the user.
Further, in the development support apparatus of the first embodiment, blocks and connections that are arranged at different levels due to sub-systems or sub-systems are presented to the user as “sub-system changed”. For this reason, the component by which subsystemization etc. were made | formed can be shown separately from the presence or absence of a substantial difference, and the user can grasp | ascertain the difference of an original model and a change model more correctly.

  In addition, since the identifier generated by the identifier generation device is set in the model component created by the development support device of the first and second embodiments, each model created by a plurality of development support devices It is possible to prevent the identifiers of the constituent elements in FIG. For this reason, when an original model is created by combining the models created by each development support apparatus, and when a modified model is created by changing the original model, the substantial model in these models The difference can be presented to the user.

[Other Embodiments]
(1) In the first and second embodiments, an identifier is generated by the identifier generation tool 200 installed in the server 2. However, the identifier generation tool 200 may be installed on the PC 1 on which the development support tool 100 is installed, and the identifier of the model created on the PC 1 may be generated by the identifier generation tool 200 installed on the PC 1.

  Further, the identifier generation tool 200 installed in the PC 1 updates the identifier set in the model component created by the development support tool 100 installed in the PC 1 in the same manner as the identifier update processing. Also good.

Even in such a case, the same effect can be obtained.
(2) In the first and second embodiments, the model creation unit 110, the identifier setting unit 120, and the model comparison unit 130 are configured as a development support tool 100 that is a single application. An example of such an application is Matlab (registered trademark).

  However, other than this, the model comparison unit 130 may be an add-on to the development support tool 100 including the model creation unit 110 and the identifier setting unit 120. Alternatively, the model comparison unit 130 may be configured as a single application and started as an external tool from the development support tool 100.

  In addition, the model comparison unit 130, the model creation unit 110, and the identifier setting unit 120 may each be an add-on to the development support tool 100 that is an application for performing model-based development. In addition, the model comparison unit 130, the model creation unit 110, and the identifier setting unit 120 may be configured as a single application and started as an external tool from the development support tool 100.

Even in such a case, the same effect can be obtained.
[Correspondence with Claims]
The correspondence between the terms used in the description of the above embodiment and the terms used in the description of the claims is shown.

The development support device corresponds to a model comparison device and a model creation device, and the development support tool 100 corresponds to a model comparison tool and a model creation tool.
The model creation unit 110 of the development support tool 100 corresponds to a model generation unit, and the identifier setting unit 120 corresponds to a setting unit.

The identifier generation unit 210 of the identifier generation tool 200 corresponds to an identifier generation unit and replacement unit, and the transmission / reception unit 220 corresponds to an addition unit, an acquisition unit, and a provision unit.
The port block corresponds to a communication block, and the library subsystem and custom subsystem correspond to a common subsystem.

  Further, S305 of the difference detection process of the first embodiment corresponds to reading means, S325, S335, and S345 correspond to detection means, S330 corresponds to presentation means, and S365 and S380 correspond to comparison means. In addition, S905 of the difference detection process of the second embodiment corresponds to reading means, S920, S930, and S940 correspond to detection means, S925 corresponds to presentation means, and S955 and S970 correspond to comparison means.

  DESCRIPTION OF SYMBOLS 1 ... PC, 2 ... Server, 5 ... Network, 10 ... Display, 20 ... HDD, 30 ... CPU, 40 ... ROM, 50 ... RAM, 60 ... Input device, 100 ... Development support tool, 110 ... Model creation part, 120 ... identifier setting unit, 130 ... model comparison unit, 200 ... identifier generation tool, 210 ... identifier generation unit, 220 ... transmission / reception unit.

Claims (6)

A block indicating a predetermined processing procedure and a connection representing data input / output between these blocks by connecting the blocks are used as components, and a program is described using these components. An original model that is a model in which a unique identifier is set for each component, and a modification of the original model, the same component being used from the original model Reading means (S305, S905) for reading the change model in which the identifier is set;
Two constituent elements having the same identifier set are detected from the constituent elements included in the original model and the constituent elements included in the change model, and are set in these constituent elements. A comparison means (S365, S380, S955, S970) for comparing parameters;
Detection means (S325, S335) for detecting the component used for only one of these models based on the identifier set for the component of these models with respect to the original model and the modified model S345, S920, S930, S940),
Presenting means (S330, S925) for presenting the comparison result by the comparison means and the detection result by the detection means,
As the block, a subsystem that executes the processing procedure described by the component can be used.
A unique hierarchy is formed by the processing procedure described by the subsystem and the other block connected to the subsystem by the connection and the processing procedure described in the subsystem, respectively.
The detecting means further detects that the component set with the same identifier in the original model and the modified model is used in the description of the processing procedure forming the different hierarchies. (S345),
Model comparison device (1) characterized by The model comparison device according to claim 1,
A plurality of the blocks connected directly or indirectly by the connection as a block group, and the model is composed of one or a plurality of the block groups;
A model comparison device. In the model comparison device according to claim 1 or 2 ,
As the block, a subsystem that executes the processing procedure described by the component can be used.
Used to describe the processing procedure in the subsystem, the block for inputting / outputting data to / from other blocks other than the subsystem is an internal block, and data is transferred to / from the internal block. The other blocks other than the subsystem that performs input / output of
The input / output of data between the external block and the internal block is the connection that connects the external block and the subsystem, the communication block that is the block used in the subsystem, and the internal block It is represented by the connection that leads to
As the parameter of the connection, a connection destination parameter indicating the block connected to the connection is provided,
When the connection destination parameter of the connection indicates the communication block, the comparison means indicates any of the blocks connected to the subsystem related to the communication block. The connection destination parameter is compared, and if the connection destination parameter indicates the subsystem, the connection destination parameter is connected to the communication block used in the subsystem. And comparing the connection destination parameters (S380, S970).
A model comparison device. In the model comparison apparatus according to claim 3 ,
The presenting means, when the communication block is detected as the component used only in one of the original model and the modified model by the detection means, Not present as detection results,
A model comparison device. In the model comparison device according to any one of claims 1 to 4,
A common subsystem in which the predetermined processing procedure is described is used as the subsystem.
A model comparison device. A block indicating a predetermined processing procedure and a connection representing data input / output between these blocks by connecting the blocks are used as components, and a program is described using these components. An original model that is a model in which a unique identifier is set for each component, and a modification of the original model, the same component being used from the original model Reading means (S305, S905) for reading the change model in which the identifier is set;
Two constituent elements having the same identifier set are detected from the constituent elements included in the original model and the constituent elements included in the change model, and are set in these constituent elements. A comparison means (S365, S380, S955, S970) for comparing parameters;
Detection means (S325, S335) for detecting the component used for only one of these models based on the identifier set for the component of these models with respect to the original model and the modified model S345, S920, S930, S940),
A computer is operated as a presentation means (S330, S925) for presenting the comparison result by the comparison means and the detection result by the detection means ,
As the block, a subsystem that executes the processing procedure described by the component can be used.
A unique hierarchy is formed by the processing procedure described by the subsystem and the other block connected to the subsystem by the connection and the processing procedure described in the subsystem, respectively.
The detecting means further detects that the component set with the same identifier in the original model and the modified model is used in the description of the processing procedure forming the different hierarchies. (S345),
A model comparison tool (100) characterized by:

Images