Model transformation device, model equivalence verification device, model transformation method, and model transformation program

Abstract

To make it possible to highly accurately and automatically convert a model to a model in a different computer modeling environment.SOLUTION: A model conversion device 10 includes a derivation unit 30A, and a generation unit 30B. The derivation unit 30A derives a piece of function specification connection information 52 in which an element B specified in SysML model 50 and a specification element SB as the requirement specification corresponding to the function are associated based on a SysML model 50 (first model), which is generated in a first computer modeling environment of model-based systems engineering and expresses the function of the system by combining multiple elements B. The generation unit 30B generates model generation specification information 54 that is input to an automatic conversion tool 32 that generates a Simulink model 56 (second model) of a second computer modeling environment based on the function specification connection information 52.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present disclosure relates to a model transformation device, a model equivalence checking device, a model transformation method, and a model transformation program. [Background technology]

[0002] Models created in a computer modeling environment are converted into models for a different computer modeling environment. For example, modeling tools such as EA (Enterprise Architect) that have a function for automatically converting models into Simulink models are known. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 4988811 [Patent Document 2] Patent No. 5147952 Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the conventional technology, since the user inputs the mathematical expression definitions, specification definitions, etc. for model conversion, there is a possibility that erroneous conversion may occur due to misinterpretation or incorrect input.

[0005] One aspect of the present disclosure contributes to providing a model conversion device, a model equivalence verification device, a model conversion method, and a model conversion program that enable highly accurate automatic conversion to a different model in a computer modeling environment. [Means for solving the problem]

[0006] The model conversion device according to the present disclosure includes a derivation unit and a generation unit. The derivation unit generates a first model that represents a system function by combining a plurality of elements and is generated in a first computer modeling environment of model-based systems engineering (hereinafter referred to as model-based development). a system specification diagram written in accordance with a predetermined requirements specification description method; and deriving functional specification connection information that associates the elements defined in the first model with requirement specifications corresponding to the functions based on the functional specification connection information. The generation unit generates model generation specification information, based on the functional specification connection information, to be input to an automatic conversion tool that generates a second model in a second computer modeling environment. [Effects of the Invention]

[0007] The model transformation device, model equivalence verification device, model transformation method, and model transformation program according to the present disclosure enable highly accurate automatic transformation to a model in a different computer modeling environment. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an example of a configuration of a model transformation device. [Figure 2] FIG. 2 is a diagram illustrating a hardware configuration of an example of a model transformation device. [Figure 3] FIG. 3 is a detailed configuration diagram of an example of the automatic model generation unit. [Figure 4] Figure 4 is a schematic diagram showing an example of a SysML model and a system specification diagram. [Figure 5] FIG. 5 is a detailed configuration diagram of an example of the verification unit. [Figure 6] FIG. 6 is a flowchart illustrating an example of the flow of the automatic model generation process. [Figure 7] FIG. 7 is a flowchart illustrating an example of the flow of the verification process. DETAILED DESCRIPTION OF THE INVENTION

[0009] Hereinafter, embodiments of a model transformation device, a model equivalence verification device, a model transformation method, and a model transformation program according to the present disclosure will be described with reference to the accompanying drawings.

[0010] FIG. 1 is a diagram showing an example of the configuration of a model transformation device 10 according to this embodiment.

[0011] The model conversion device 10 is an information processing device that automatically converts a first model into a second model.

[0012] The first model is a model generated in the first computer modeling environment of model-based development, which represents the system's functions as a combination of multiple elements. Model-based development is a development method in systems engineering development that improves the visibility of system functions by utilizing models.

[0013] The second model is a model generated by a second computer modeling environment that is different from the first computer modeling environment.

[0014] In this embodiment, the first computer modeling environment is a SysML (Systems Modeling Language) (registered trademark) environment established by the OMG (Object Management Group), and the first model is a SysML model. Also, in this embodiment, the second computer modeling environment is a MATLAB (registered trademark) Simulink (registered trademark) environment, and the second model is a Simulink model.

[0015] The first computer modeling environment and the second computer modeling environment may be different computer modeling environments and are not limited to a SysML environment and a Simulink environment, and the first model and the second model may be models generated in different computer modeling environments and are not limited to a SysML model and a Simulink model.

[0016] FIG. 2 is a diagram showing an example of the hardware configuration of the model transformation device 10. As shown in FIG.

[0017] The model conversion device 10 has a hardware configuration that utilizes a computer, with a CPU (Central Processing Unit) 11A, a ROM (Read Only Memory) 11B, a RAM (Random Access Memory) 11C, an I / F 11D, etc. interconnected by a bus 11E.

[0018] The CPU 11A is a computing device that controls the model conversion device 10 of this embodiment. The ROM 11B stores programs and the like that realize various processes by the CPU 11A. The RAM 11C stores data used for various processes by the CPU 11A. The I / F 11D is an interface for sending and receiving data.

[0019] The program for executing information processing executed by the model transformation device 10 of this embodiment is provided by being pre-installed in the ROM 11B etc. The program executed by the model transformation device 10 of this embodiment may also be provided by being recorded on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a digital versatile disk (DVD) in the form of a file that can be installed or executed by the model transformation device 10.

[0020] Returning to Figure 1, the description will continue. The model conversion device 10 includes a storage unit 12, a UI (user interface) unit 14, a communication unit 16, and a control unit 20. The storage unit 12, the UI unit 14, the communication unit 16, and the control unit 20 are connected to each other so as to be able to communicate with each other via a bus 18 or the like.

[0021] The storage unit 12 stores various types of data. The storage unit 34 is, for example, a semiconductor memory device such as a RAM or a flash memory, a hard disk, or an optical disk.

[0022] The UI unit 14 has an input function for accepting input from a user and a display function for displaying various information. The input function is realized by, for example, a pointing device such as a mouse, a keyboard, etc. The display function is realized by, for example, a display, a projection device, etc. The communication unit 16 communicates with an external information processing device by wireless or wired communication via a network, etc.

[0023] The control unit 20 executes various information processes. For example, the CPU 11A reads a program from the ROM 11B onto the RAM 11C and executes it, thereby realizing each processing unit of the control unit 20, which will be described later, on the computer.

[0024] The control unit 20 includes an automatic model generation unit 30 and a verification unit 40. Some or all of the automatic model generation unit 30 and the verification unit 40 may be implemented, for example, by causing a processing device such as a CPU 11A to execute a program, or may be implemented by software, or by hardware such as an IC (Integrated Circuit), or may be implemented using a combination of software and hardware. Furthermore, at least one of the automatic model generation unit 30 and the verification unit 40 may be mounted on an external information processing device communicatively connected to the model conversion device 10 via a network or the like.

[0025] The automatic model generation unit 30 automatically generates a Simulink model, which is a second model, from a SysML model, which is a first model.

[0026] FIG. 3 is a detailed configuration diagram of an example of the automatic model generation unit 30.

[0027] The automatic model generation unit 30 includes a derivation unit 30A and a generation unit 30B.

[0028] Based on the SysML model 50, the derivation unit 30A derives functional specification connection information 52 that associates elements defined in the SysML model 50 with requirement specifications corresponding to the functions represented by the elements. Specifically, the derivation unit 30A derives the functional specification connection information 52 based on the SysML model 50 and a system specification diagram 50C. The SysML model 50 and the system specification diagram 50C are generated by a SysML modeling tool 28. The SysML modeling tool 28 is a modeling tool for the SysML environment. In this embodiment, the SysML modeling tool 28 is pre-installed in the model conversion device 10. Also, in this embodiment, the SysML modeling tool 28 is implemented as a limited add-in for Enterprise Architect (by Sparks Systems). The SysML modeling tool 28 may be installed in an information processing device external to the model conversion device 10.

[0029] FIG. 4 is a schematic diagram showing an example of a SysML model 50 and a system specification diagram 50C.

[0030] The SysML model 50 is a model generated by the SysML modeling tool 28, which represents the system functions according to the target specifications by combining multiple elements B. The system functions according to the target specifications will sometimes be referred to as the system specification model below.

[0031] The SysML model 50 includes multiple diagrams. As examples, a block definition diagram 50A and an internal block diagram 50B are shown in FIG. The block definition diagram 50A and the internal block diagram 50B are examples of diagrams included in the SysML model 50.

[0032] The block definition diagram 50A is a diagram that describes the hierarchical structure of a system represented by a system specification model. The block definition diagram 50A includes multiple elements B, such as function blocks FB, activities AC, functional requirements FD, and requirement specification elements RB. The function blocks FB are elements B that represent functions. The activities AC are elements B that represent activities realized by connected function blocks FB. The functional requirements FD are elements B that represent requirements for a function. The requirement specification elements RB are elements B that represent specific specifications that satisfy requirements corresponding to a function. The requirement specification elements RB may be written in natural language, or may be written in accordance with the Universal Specification Describing Manner (USDM), which defines how to write requirements and specifications.

[0033] The internal block diagram 50B is a diagram that describes the connection relationships between part properties PP, which are elements B that represent functions.

[0034] The system specification diagram 50C is a diagram generated from the SysML model 50 by the SysML modeling tool 28. The system specification diagram 50C is a diagram that describes the details of the requirement specification element RB for each function in accordance with the Requirements Description Method (USDM). The system specification diagram 50C may also be referred to as a USDM diagram or USDM. The system specification diagram 50C includes multiple specification elements SB. The specification elements SB are elements B that represent the details of the requirement specification for each function, corresponding to the requirements expressed by the requirement specification element RB.

[0035] Continuing the explanation by returning to Fig. 3, the derivation unit 30A derives the functional specification connection information 52 by searching for the part property PP in the internal block diagram 50B and the specification element SB corresponding to its processing from the connection between the function block FB and the requirement specification element RB in the block definition diagram 50A.

[0036] In this embodiment, the derivation unit 30A includes a BDD (Block Definition Diagram) search unit 30C, a required specification element search unit 30D, and a specification search unit 30E.

[0037] The processes performed by the BDD search unit 30C, the required specification element search unit 30D, and the specification search unit 30E will be described in detail with reference to FIG.

[0038] For example, the control unit 20 accepts the selection of an internal block diagram 50B for which a Simulink model 56 is to be generated. The user operates the UI unit 14 to select the internal block diagram 50B for which a Simulink model 56 is to be generated. When the control unit 20 accepts the user's selection of the internal block diagram 50B, it starts the program of the automatic model generation unit 30. The BDD search unit 30C of the automatic model generation unit 30 searches for a block definition diagram 50A included in the SysML model 50 and in the same package as the selected internal block diagram 50B.

[0039] For example, the BDD search unit 30C reads "Type" information from the part property PP included in the internal block diagram 50B whose selection has been accepted. For example, the BDD search unit 30C uses a Type command, which is a command for reading the contents of a file, to read information defined in the part property PP as "Type" information. Then, the BDD search unit 30C uses the read "Type" information to search for a block definition diagram 50A that is in the same package as the internal block diagram 50B whose selection has been accepted.

[0040] The requirement specification element search unit 30D searches for a requirement specification element RB that corresponds to the part property PP included in the internal block diagram 50B and has a connection relationship with the function block FB included in the block definition diagram 50A searched for by the BDD search unit 30C.

[0041] In detail, the requirement specification element search unit 30D searches for function blocks FB and activities AC among the elements B included in the block definition diagram 50A that match the "Type" information read by the BDD search unit 30C from the part property PP and the element name of element B. Then, the requirement specification element search unit 30D searches for elements B among the elements B included in the internal block diagram 50B that are connected to each of the searched function blocks FB and activities AC. Furthermore, the requirement specification element search unit 30D identifies, among the searched elements B, an element B that is a requirement specification element RB.

[0042] Through these processes, the requirement specification element searching unit 30D searches for a requirement specification element RB that corresponds to the part property PP included in the internal block diagram 50B and has a connection relationship with the function block FB included in the block definition diagram 50A.

[0043] The specification search unit 30E searches the system specification diagram 50C for a specification element SB that corresponds to the requirement expressed by the requirement specification element RB searched for by the requirement specification element search unit 30D. Then, the specification search unit 30E derives function specification connection information 52 that associates the part property PP with the searched specification element SB.

[0044] Continuing the explanation, returning to Fig. 3, the generation unit 30B generates model generation specification information 54 based on the function specification connection information 52 generated by the derivation unit 30A, and outputs it to the automatic conversion tool 32.

[0045] The automatic conversion tool 32 is an automatic conversion tool that generates a Simulink model 56 from model generation specification information 54. For example, the automatic conversion tool 32 is a tool that receives the model generation specification information 54 as input and outputs the Simulink model 56.

[0046] The generation unit 30B generates model generation specification information 54 that defines information represented by the correspondence between a part property PP, which is element B included in the functional specification connection information 52, and a specification element SB of the requirement specification. The model generation specification information 54 may be specification information according to the automatic conversion tool 32. The automatic conversion tool 32 is, for example, "AI-Modeling" by AZAPA Corporation, but is not limited to this tool. When the automatic conversion tool 32 is "AI-Modeling," the generation unit 30B generates, as the model generation specification information 54, one or more pieces of specification information used in "AI-Modeling" for the automatic generation of a Simulink model 56.

[0047] The automatic conversion tool 32, which has received the model generation specification information 54 from the generation unit 30B, automatically converts the model generation specification information 54 into a Simulink model 56 and outputs the Simulink model 56. In this embodiment, the automatic conversion tool 32 is described as being installed in advance in the model conversion device 10 as an example. Note that the automatic conversion tool 32 may be configured to be mounted on an information processing device external to the model conversion device 10.

[0048] 1, the description will be continued. The verification unit 40 verifies the Simulink model 56 output from the automatic conversion tool 32 by inputting the model generation specification information 54 generated by the automatic model generation unit 30. The verification unit 40 corresponds to the model equivalence verification device of this embodiment.

[0049] FIG. 5 is a detailed configuration diagram of an example of the verification unit 40. As shown in FIG.

[0050] The verification unit 40 includes a timing diagram acquisition unit 40A, a verification target model acquisition unit 40B, an input signal block generation unit 40C, a combination unit 40D, an execution instruction unit 40E, and an equivalence verification unit 40F.

[0051] For example, when a user selects an equivalence checking program with a timing diagram 50D selected on the SysML modeling tool 28, for example, through an operation instruction from the UI unit 14, the control unit 20 starts the equivalence checking program. The starting of the equivalence checking program starts the verification unit 40. The timing diagram acquisition unit 40A of the verification unit 40 receives the selected timing diagram 50D. The timing diagram acquisition unit 40A also acquires the input signal names, waveform information, and expected output values ​​from the selected timing diagram 50D.

[0052] Timing diagram 50D is a diagram generated by SysML modeling tool 28 based on SysML model 50. Timing diagram 50D is a timing diagram that represents the state transitions of a system realized by SysML model 50, described in, for example, Unified Modeling Language (UML).

[0053] The verification target model acquisition unit 40B acquires a Simulink model 56 to be verified. Specifically, the verification target model acquisition unit 40B acquires, as the verification target model, a Simulink model 56 output from the automatic conversion tool 32 to which the model generation specification information 54 generated by the automatic model generation unit 30 has been input. Note that the verification target model acquisition unit 40B may acquire, as the verification target model, a Simulink model 56 selected by a user's operation instruction on the UI unit 14 from among multiple Simulink models 56 generated by the automatic conversion tool 32 using the model generation specification information 54 generated by the automatic model generation unit 30.

[0054] Based on the timing diagram 50D, the input signal block generation unit 40C generates input signals and input signal blocks for defining the waveforms of the input signals used in the Simulink model 56. For example, a SignalBuilder block is used as the input signal block. In the following description, the input signal block may be referred to as a SignalBuilder block.

[0055] The input signal block generator 40C generates a SignalBuilder block of the Simulink model 56 by reading the input signal names, which are the names of the lifelines included in the timing diagram 50D, and waveform information.

[0056] The combining unit 40D combines and connects the SignalBuilder block with the Simulink model 56 of the verification target acquired by the verification target model acquisition unit 40B to generate a combined model 58. The combining unit 40D generates the combined model 58 by automatically connecting the SignalBuilder block with the Simulink model 56 based on the signal names and port names included therein.

[0057] The execution instruction unit 40E outputs an instruction to execute a simulation of the combined model 58 generated by the combining unit 40D to the Simulink 42. The Simulink 42 is a simulation program in the Simulink environment, which is a simulation environment.

[0058] Upon receiving the instruction to execute the simulation, the Simulink 42 executes a simulation of the combined model 58 and outputs the execution result of the simulation to the equivalence checking unit 40F.

[0059] The equivalence checking unit 40F checks the equivalence between the results of the simulation of the combined model 58 and the expected output values ​​of the SysML model 50 obtained from the timing diagram 50D.

[0060] The equivalence checking unit 40F outputs the equivalence verification results. Specifically, the equivalence checking unit 40F stores the equivalence verification results in the storage unit 12. The equivalence checking unit 40F may output and store the equivalence verification results in an Excel file or the like. The equivalence checking unit 40F also displays the equivalence verification results on the UI unit 14. For example, the equivalence checking unit 40F displays the timing diagram 50D and the execution results of the simulation superimposed on the same graph. By outputting the verification results by the equivalence checking unit 40F, the verification results can be easily provided to the user.

[0061] Next, an example of the flow of information processing executed by the model transformation device 10 of this embodiment will be described. First, an example of the flow of automatic model generation processing executed by the model transformation device 10 will be described.

[0062] FIG. 6 is a flowchart showing an example of the flow of the automatic model generation process executed by the model conversion device 10.

[0063] The control unit 20 of the model conversion device 10 receives a selection of an internal block diagram 50B for which a Simulink model 56 is to be generated (step S100). Next, the control unit 20 starts a program of the automatic model generation unit 30 (step S102). The automatic model generation unit 30 is started by the processing of step S102.

[0064] Next, the BDD search unit 30C of the automatic model generation unit 30 reads "Type" information from the part property PP included in the internal block diagram 50B whose selection was accepted in step S100 (step S104).The BDD search unit 30C then uses the "Type" information read in step S104 to search for a block definition diagram 50A that is in the same package as the internal block diagram 50B whose selection was accepted in step S100 (step S106).

[0065] Next, the requirement specification element searching unit 30D searches for function blocks FB and activities AC that match the "Type" information and the element name of element B read in step S104 among the elements B included in the internal block diagram 50B (step S108).The requirement specification element searching unit 30D then searches for elements B that are connected to the function blocks FB and activities AC found in step S108 among the elements B included in the internal block diagram 50B (step S110).Next, the requirement specification element searching unit 30D identifies an element B that is a requirement specification element RB among the elements B found in step S110 (step S112).

[0066] Through the processing of steps S108 to S112, the requirement specification element searching unit 30D searches for a requirement specification element RB that corresponds to the part property PP included in the internal block diagram 50B and has a connection relationship with the function block FB included in the block definition diagram 50A.

[0067] Next, the specification search unit 30E searches the system specification diagram 50C for a specification element SB corresponding to the requirement represented by the requirement specification element RB found by the processing of steps S108 to S112 (step S114).The specification search unit 30E then derives function specification connection information 52 that associates the part property PP with the specification element SB found in step S114 (step S116).

[0068] The generation unit 30B generates model generation specification information 54 based on the function specification connection information 52 derived in step S116 (step S118). The automatic conversion tool 32 generates a Simulink model 56 from the model generation specification information 54 generated in step S118 (step S120). Then, this routine ends.

[0069] Next, an example of the flow of the verification process executed by the model transformation device 10 will be described.

[0070] FIG. 7 is a flowchart showing an example of the flow of the verification process executed by the model transformation device 10.

[0071] When an equivalence checking program is selected with timing diagram 50D selected on SysML modeling tool 28, for example, by a user operating UI unit 14 (step S200), control unit 20 starts the equivalence checking program (step S202). Starting the equivalence checking program starts verification unit 40, and timing diagram acquisition unit 40A of verification unit 40 receives the selected timing diagram 50D.

[0072] The verification target model acquisition unit 40B acquires the Simulink model 56 of the verification target (step S204).

[0073] Input signal block generator 40C generates a SignalBuilder block of Simulink model 56 based on timing diagram 50D selected in step S200 (step S206).

[0074] The combining unit 40D combines the SignalBuilder block generated in step S206 with the Simulink model 56 acquired in step S204 to generate a combined model 58 (step S208).

[0075] The execution instruction unit 40E outputs an instruction to execute a simulation of the combined model 58 generated in step S208 to the Simulink 42 (step S210). By the processing of step S210, the Simulink 42 executes a simulation of the combined model 58 generated in step S208, and outputs the execution result of the simulation to the equivalence checking unit 40F.

[0076] The equivalence checking unit 40F checks the equivalence between the execution result of the simulation of the combined model 58 and the expected output value of the SysML model 50 obtained from the timing diagram 50D received in step S200 (step S212).

[0077] Then, the equivalence checking unit 40F outputs the result of the equivalence check in step S212 (step S214), and then ends this routine.

[0078] As described above, the model conversion device 10 of this embodiment includes a derivation unit 30A and a generation unit 30B. Based on a SysML model 50 (first model) generated in a first computer modeling environment of model-based development and representing the functions of a program by combining multiple elements B, the derivation unit 30A derives functional specification connection information 52 that associates elements B defined in the SysML model 50 with specification elements SB, which are requirement specifications corresponding to the functions. Based on the functional specification connection information 52, the generation unit 30B generates model generation specification information 54 to be input to an automatic conversion tool 32 that generates a Simulink model 56 (second model) in a second computer modeling environment.

[0079] Here, when converting from a SysML model 50 to a different model such as a Simulink model 56, the user may need to input mathematical definitions or specification definitions for the model conversion, which may result in incorrect conversion due to misinterpretation or incorrect input.

[0080] In particular, modeling tools such as EA that have an automatic model conversion function are known. However, when using such known modeling tools to convert, for example, a SysML model 50 into a Simulink model 56, the conversion work is performed by a user with the same workload and skills as when generating the Simulink model 56. Also, when using an automatic conversion tool such as AI-Modeling (manufactured by AZAPA Corporation) that generates a Simulink model 56 from system specifications, the user must create a conversion specification to input into the automatic conversion tool. For example, in conventional technology, the user manually inputs specifications, mathematical formulas, specifications, and the like.

[0081] As described above, in the conventional technology, conversion from a SysML model 50 to a different model such as a Simulink model 56 requires the user to input mathematical formula definitions, specification definitions, etc. for the model conversion, which can result in reduced accuracy and increased workload due to misinterpretation, incorrect input, etc. Furthermore, in the conventional technology, the equivalence of the converted model cannot be guaranteed in some cases due to misinterpretation, incorrect input, etc. by the user.

[0082] Furthermore, with the conventional technology, it was difficult to find out which specifications were linked to the part property PP in the internal block diagram 50B included in the SysML model 50, and it was difficult to extract information used to generate the Simulink model 56 from the SysML model 50.

[0083] On the other hand, in the model conversion device 10 of this embodiment, the derivation unit 30A derives functional specification connection information 52 from the SysML model 50, and the generation unit 30B generates model generation specification information 54 from the functional specification connection information 52. Therefore, by inputting the automatic conversion tool 32 generated by the generation unit 30B into the automatic conversion tool 32, a Simulink model 56 can be easily automatically generated from the SysML model 50.

[0084] For example, the model conversion device 10 of this embodiment can automatically generate a second model such as a Simulink model 56 from a first model such as a SysML model 50 without requiring the user to input mathematical formula definitions, specification definitions, and the like.

[0085] Therefore, the model conversion device 10 of this embodiment can enable equivalent automatic conversion to a different model of the computer modeling environment.

[0086] Furthermore, the model conversion device 10 of this embodiment can be easily incorporated into a system development process that applies a first model such as the pre-conversion SysML model 50, without providing an additional process for generating a second model such as the Simulink model 56.

[0087] The model conversion device 10 of this embodiment also includes a verification unit 40. An equivalence verification unit 40F of the verification unit 40 verifies the equivalence of a combined model 58 of a Simulink model 56 and a Signalbuilder block output from an automatic conversion tool 32 to which model generation specification information 54 generated by the automatic model generation unit 30 has been input, and an expected output value of a SysML model 50 obtained from a timing diagram 50D.

[0088] Here, it is desirable to verify the equivalence between the Simulink model 56 generated by the automatic conversion tool 32 and the original specifications using different algorithms, but such verification technology has not existed in the past. Furthermore, even when a correct model generation process is performed using a known automatic conversion tool such as AI-Modeling, the equivalence of the generated model may not be guaranteed due to tool malfunctions or other reasons. Furthermore, for example, in circuit conversion using logic synthesis in semiconductor design, it is known that equivalence is guaranteed by using a logic synthesis tool in combination with an equivalence verification tool using a different algorithm. However, an equivalence verification tool used in semiconductor design has not been provided as an automatic model conversion tool.

[0089] On the other hand, in this embodiment, the verification unit 40 verifies the equivalence between the combined model 58 and the output expected value through the above process.

[0090] Therefore, in addition to the above-mentioned effects, the model transformation device 10 of this embodiment can easily verify the equivalence of the model before and after transformation.

[0091] Although the embodiments have been described above, they are presented as examples and are not intended to limit the scope of the invention. The novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. The above embodiments are included within the scope and spirit of the invention, and are also included in the scope of the inventions and their equivalents as defined in the claims. [Explanation of symbols]

[0092] 10 Model conversion device 30 Automatic model generation section 30A lead-out part 30B Generation part 30C BDD Search Department 30D Requirement specification element search section 30E Specification Search Department 40 Verification Department 40A Timing diagram acquisition section 40B Verification target model acquisition section 40C Input signal block generation unit 40D joint 40E Execution instruction section 40F Equivalence Verification Unit

Claims

1. a derivation unit that derives functional specification connection information that associates the elements defined in a first model with requirement specifications corresponding to the functions, based on a first model that represents a system function by combining a plurality of elements and that is generated in a first computer modeling environment of model-based systems engineering, and a system specification diagram that is described in accordance with a predetermined requirement specification description method; a generation unit that generates model generation specification information based on the functional specification connection information, the model generation specification information being input to an automatic conversion tool that generates a second model in a second computer modeling environment; A model transformation device comprising:

2. A derivation unit that derives functional specification connection information that associates the elements defined in a first model that is generated in a first computer modeling environment of model-based systems engineering and represents the functions of a system by combining multiple elements, with requirement specifications that correspond to the functions; a generation unit that generates model generation specification information based on the functional specification connection information, the model generation specification information being input to an automatic conversion tool that generates a second model in a second computer modeling environment; Equipped with The first model is a block definition diagram that is a diagram describing a hierarchical structure of a system represented by the functions of the system generated in the first computer modeling environment, the block definition diagram including function blocks that are the elements indicating the functions and requirement specification elements that are the elements indicating requirements corresponding to the functions; an internal block diagram that is a diagram describing the connection relationships between part properties that are the elements that represent the functions; Including, The lead-out portion is a requirement specification element searching unit that searches for the requirement specification element that has a connection relationship with the function block included in the block definition diagram, which corresponds to the part property included in the internal block diagram; a specification search unit that searches a system specification diagram described in accordance with a predetermined requirement specification description method for specification elements that represent details of the requirement specifications for each of the functions and correspond to the requirements represented by the requirement specification elements, and derives the function specification connection information that associates the part properties with the searched specification elements; A model transformation device comprising:

3. The generation unit generating the model generation specification information that defines information expressed by the correspondence between the elements included in the functional specification connection information and the requirement specification; 3. The model transformation device according to claim 1.

4. a verification target model acquisition unit that acquires, as a verification target model, a second model output from an automatic conversion tool to which the generated model generation specification information has been input; an input signal block generation unit that generates input signals used in the second model and input signal blocks for defining waveforms of the input signals, based on a timing diagram that is generated based on a first model, is described in a unified modeling language, and represents state transitions of a system realized by the first model; an equivalence verification unit that verifies equivalence between an execution result of simulating a combined model of the input signal block and the model to be verified in a second computer modeling environment that is a simulation environment and an expected output value of the first model obtained from the timing diagram; A model equivalence verification device comprising:

5. A model transformation device according to any one of claims 1 to 3, comprising the model equivalence verification device according to claim 4.

6. the first model is a SysML® model; the second model is a Simulink® model; 4. The model transformation device according to claim 1.

7. A step in which a derivation unit of a model conversion device derives functional specification connection information that associates the elements defined in a first model, which represents the functions of a program by a combination of multiple elements and is generated in a first computer modeling environment of model-based development, with the requirements specification corresponding to the functions, based on a system specification diagram described in accordance with a predetermined requirements specification description method; generating, by a generation unit of the model conversion device, model generation specification information to be input to an automatic conversion tool that generates a second model in a second computer modeling environment, based on the functional specification connection information; A model transformation method including:

8. A model transformation program executed by a model transformation device, a step of deriving functional specification connection information that associates the elements defined in a first model with requirement specifications corresponding to the functions, based on a first model that represents a program function by combining a plurality of elements and that is generated in a first computer modeling environment of model-based development, and a system specification diagram that is described in accordance with a predetermined requirement specification description method; generating model generation specification information based on the functional specification connection information, the model generation specification information being input to an automated conversion tool for generating a second model in a second computer modeling environment; A model transformation program including:

Images