JP7735026B2 - Model transformation device, model equivalence verification device, model transformation method, and model transformation program - Google Patents

Description

This disclosure relates to a model transformation device, a model equivalence verification device, a model transformation method, and a model transformation program.

Models created in one computer modeling environment are often converted into models for a different computer modeling environment. For example, modeling tools such as EA (Enterprise Architect) are known that have the ability to automatically convert to Simulink models.

Patent No. 4988811 Patent No. 5147952

However, with conventional technology, users are required to input mathematical formula definitions and specification definitions for model conversion, which can lead to incorrect conversions due to misinterpretation or incorrect input.

One aspect of the present disclosure contributes to the provision of 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.

A model conversion device according to the present disclosure includes a derivation unit and a generation unit. The derivation unit 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 generated in a first computer modeling environment of model-based systems engineering (hereinafter referred to as model-based development) and representing a system function by combining multiple elements, and a system specification diagram described in accordance with a predetermined requirement specification description method. The generation unit generates model generation specification information based on the functional specification connection information, which is input to an automatic conversion tool that generates a second model in a second computer modeling environment.

The model conversion device, model equivalence verification device, model conversion method, and model conversion program disclosed herein enable highly accurate automatic conversion to a model in a different computer modeling environment.

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

Embodiments of a model transformation device, model equivalence verification device, model transformation method, and model transformation program according to the present disclosure will be described below with reference to the accompanying drawings.

Figure 1 is a configuration diagram of an example of a model conversion device 10 according to this embodiment.

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

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.

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

In this embodiment, an example is described in which the first computer modeling environment is a SysML (Systems Modeling Language) (registered trademark) environment developed by the OMG (Object Management Group), and the first model is a SysML model. Also, in this embodiment, an example is described in which the second computer modeling environment is a MATLAB (registered trademark) Simulink (registered trademark) environment, and the second model is a Simulink model.

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. Furthermore, 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.

Figure 2 is a hardware configuration diagram of an example of a model conversion device 10.

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

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 performed by the CPU 11A. The RAM 11C stores data used for various processes performed by the CPU 11A. The I/F 11D is an interface for sending and receiving data.

The program for executing information processing executed by the model conversion device 10 of this embodiment is provided pre-installed in ROM 11B or the like. The program executed by the model conversion device 10 of this embodiment may also be provided recorded on a computer-readable recording medium such as a CD-ROM, flexible disk (FD), CD-R, or DVD (Digital Versatile Disk) in a format that can be installed or executed by the model conversion device 10.

Returning to Figure 1, we will continue the explanation. The model conversion device 10 comprises a memory unit 12, a UI (user interface) unit 14, a communication unit 16, and a control unit 20. The memory unit 12, UI unit 14, communication unit 16, and control unit 20 are connected to each other so that they can communicate with each other via a bus 18 or the like.

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

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

The control unit 20 executes various types of information processing. For example, the CPU 11A reads a program from the ROM 11B onto the RAM 11C and executes it, thereby realizing each of the processing units of the control unit 20 (described below) on the computer.

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 a processing device such as a CPU 11A executing a program, by software, by hardware such as an IC (Integrated Circuit), or by 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.

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.

Figure 3 is a detailed configuration diagram of an example of the automatic model generation unit 30.

The automatic model generation unit 30 has a derivation unit 30A and a generation unit 30B.

Based on the SysML model 50, the derivation unit 30A derives functional specification connection information 52, which 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. This embodiment also illustrates the SysML modeling tool 28 as a modeling tool implemented as a limited add-in for EnterPrise Architect (Sparks Systems). The SysML modeling tool 28 may be installed in an information processing device external to the model conversion device 10.

Figure 4 is a schematic diagram showing an example of a SysML model 50 and a system specification diagram 50C.

The SysML model 50 is a model generated by the SysML modeling tool 28, which represents the system functions corresponding to the target specifications by combining multiple elements B. Hereinafter, the system functions corresponding to the target specifications may be referred to as the system specification model.

The SysML model 50 includes multiple diagrams. Figure 4 shows, as an example, a block definition diagram 50A and an internal block diagram 50B. The block definition diagram 50A and the internal block diagram 50B are examples of diagrams included in the SysML model 50.

Block definition diagram 50A is a diagram that describes the hierarchical structure of a system represented by a system specification model. Block definition diagram 50A includes multiple elements B, such as function blocks FB, activities AC, functional requirements FD, and requirement specification elements RB. A function block FB is an element B that represents a function. An activity AC is an element B that represents an activity realized by connected function blocks FB. A functional requirement FD is an element B that represents a requirement required for a function. A requirement specification element RB is an element B that represents a specific specification that satisfies the requirement corresponding to a function. The requirement specification element RB may be written in natural language, or may be written in accordance with the Universal Specification Describing Manner (USDM), which defines how to describe requirements and specifications.

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

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 elements RB for each function in accordance with the Requirements Description Method (USDM). The system specification diagram 50C is sometimes 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 specifications for each function, corresponding to the requirements expressed by the requirement specification elements RB.

Returning to Figure 3, the explanation continues. 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.

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.

The processing performed by the BDD search unit 30C, the required specification element search unit 30D, and the specification search unit 30E will be explained in detail using Figure 4.

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.

For example, the BDD search unit 30C reads "Type" information from the part properties PP included in the internal block diagram 50B whose selection was accepted. For example, the BDD search unit 30C uses the Type command, which is a command for reading the contents of a file, to read the information defined in the part properties 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 was accepted.

The requirement specification element search unit 30D searches for requirement specification elements RB that have a connection relationship with the function blocks FB included in the block definition diagram 50A searched for by the BDD search unit 30C and that correspond to the part properties PP included in the internal block diagram 50B.

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 and element name of element B read by the BDD search unit 30C from the part property PP. The requirement specification element search unit 30D then 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.

Through these processes, the requirement specification element search unit 30D searches for requirement specification elements RB that have a connection relationship with the function blocks FB included in the block definition diagram 50A and correspond to the part properties PP included in the internal block diagram 50B.

The specification search unit 30E searches the system specification diagram 50C for specification elements SB that correspond to the requirements represented by the requirement specification elements RB found by the requirement specification element search unit 30D. The specification search unit 30E then derives functional specification connection information 52 that associates the part properties PP with the found specification elements SB.

Returning to Figure 3, the explanation continues. The generation unit 30B generates model generation specification information 54 based on the functional specification connection information 52 generated by the derivation unit 30A, and outputs it to the automatic conversion tool 32.

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 model generation specification information 54 as input and outputs a Simulink model 56.

The generation unit 30B generates model generation specification information 54, which defines information represented by the correspondence between part properties PP, which are elements B included in the functional specification connection information 52, and specification elements SB of the requirements specification. The model generation specification information 54 may be specification information compatible with 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 model generation specification information 54, one or more pieces of specification information used by "AI-Modeling" to automatically generate a Simulink model 56.

The automatic conversion tool 32 receives 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 pre-installed in the model conversion device 10 as an example. Note that the automatic conversion tool 32 may also be installed in an information processing device external to the model conversion device 10.

Returning to Figure 1, the explanation continues. 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.

Figure 5 is a detailed configuration diagram of an example of the verification unit 40.

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.

For example, when a user operates the UI unit 14 to select an equivalence checking program while a timing diagram 50D is selected on the SysML modeling tool 28, the control unit 20 launches the equivalence checking program. The launch of the equivalence checking program launches the verification unit 40. The timing diagram acquisition unit 40A of the verification unit 40 accepts 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.

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

The verification target model acquisition unit 40B acquires the Simulink model 56 to be verified. Specifically, the verification target model acquisition unit 40B acquires, as the verification target model, the 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, the Simulink model 56 selected by the user's operation instruction via 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.

The input signal block generator 40C generates input signal blocks that define the input signals and input signal waveforms used in the Simulink model 56 based on the timing diagram 50D. For example, a SignalBuilder block is used as the input signal block. Below, the input signal block may be referred to as a SignalBuilder block.

The input signal block generator 40C generates a SignalBuilder block for the Simulink model 56 by reading the input signal name, which is the name of the lifeline, and waveform information contained in the timing diagram 50D.

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.

The execution instruction unit 40E outputs a simulation execution instruction for the combined model 58 generated by the combination unit 40D to Simulink 42. Simulink 42 is a simulation program for the Simulink environment, which is a simulation environment.

When Simulink 42 receives a simulation execution instruction, it executes a simulation of the combined model 58 and outputs the results of the simulation to the equivalence verification unit 40F.

The equivalence verification unit 40F verifies 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.

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

Next, we will explain an example of the flow of information processing executed by the model conversion device 10 of this embodiment. First, we will explain an example of the flow of automatic model generation processing executed by the model conversion device 10.

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

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

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 selected in step S100 (step S104). Then, using the "Type" information read in step S104, the BDD search unit 30C searches for a block definition diagram 50A in the same package as the internal block diagram 50B selected in step S100 (step S106).

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

By processing steps S108 to S112, the requirement specification element search unit 30D searches for requirement specification elements RB that have a connection relationship with the function blocks FB included in the block definition diagram 50A and correspond to the part properties PP included in the internal block diagram 50B.

Next, the specification search unit 30E searches the system specification diagram 50C for a specification element SB that corresponds 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 functional specification connection information 52 that associates the part property PP with the specification element SB found in step S114 (step S116).

The generation unit 30B generates model generation specification information 54 based on the functional 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). This routine then ends.

Next, we will explain an example of the flow of the verification process executed by the model conversion device 10.

Figure 7 is a flowchart showing an example of the flow of the verification process executed by the model transformation device 10.

When the user selects an equivalence checking program with timing diagram 50D selected on the SysML modeling tool 28, for example by operating the UI unit 14 (step S200), the control unit 20 launches the equivalence checking program (step S202). Launching the equivalence checking program launches the verification unit 40, and the timing diagram acquisition unit 40A of the verification unit 40 accepts the selected timing diagram 50D.

The verification target model acquisition unit 40B acquires the Simulink model 56 to be verified (step S204).

The input signal block generator 40C generates a SignalBuilder block for the Simulink model 56 based on the timing diagram 50D selected in step S200 (step S206).

The combining unit 40D generates a combined model 58 by combining the SignalBuilder block generated in step S206 with the Simulink model 56 acquired in step S204 (step S208).

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

The equivalence verification unit 40F verifies 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 received in step S200 (step S212).

Then, the equivalence verification unit 40F outputs the results of the equivalence verification performed in step S212 (step S214). Then, this routine ends.

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 for model-based development and representing the functions of a program as a combination of 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 that is input to an automatic conversion tool 32 that generates a Simulink model 56 (second model) in a second computer modeling environment.

When converting from a SysML model 50 to a different model, such as a Simulink model 56, the user may need to enter mathematical definitions or specification definitions for the model conversion, which could result in incorrect conversion due to misinterpretation or incorrect input.

For example, modeling tools such as EAs that have automatic model conversion functions 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 a Simulink model 56. Furthermore, even 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 conversion specifications to input into the automatic conversion tool. For example, in conventional technology, users manually input specifications, formulas, specifications, etc.

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

Furthermore, with conventional technology, it was difficult to determine which specifications were linked to the part properties PP in the internal block diagram 50B included in the SysML model 50, and it was difficult to extract information from the SysML model 50 to use in generating the Simulink model 56.

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 and automatically generated from the SysML model 50.

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, etc.

Therefore, the model conversion device 10 of this embodiment enables equivalent automatic conversion to a different model in a computer modeling environment.

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 the need for an additional process for generating a second model, such as the Simulink model 56.

The model conversion device 10 of this embodiment also includes a verification unit 40. The 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 that receives model generation specification information 54 generated by the automatic model generation unit 30, and the expected output value of the SysML model 50 obtained from the timing diagram 50D.

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 normal 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, etc. 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 conjunction with an equivalence verification tool that uses a different algorithm. However, no equivalence verification tools used in semiconductor design have been provided as automatic model conversion tools.

In contrast, in this embodiment, the verification unit 40 verifies the equivalence between the combined model 58 and the output expected value through the above processing.

For this reason, in addition to the above-mentioned effects, the model conversion device 10 of this embodiment can easily verify the equivalence of models before and after conversion.

Although the above describes an embodiment, the above embodiment is presented as an example and is not intended to limit the scope of the invention. The above novel embodiment can be embodied in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. The above embodiment is included within the scope and spirit of the invention, and is also included in the invention and its equivalents as set forth in the claims.

10 Model conversion device 30 Automatic model generation unit 30A Derivation unit 30B Generation unit 30C BDD search unit 30D Required specification element search unit 30E Specification search unit 40 Verification unit 40A Timing diagram acquisition unit 40B Verification target model acquisition unit 40C Input signal block generation unit 40D Combination unit 40E Execution instruction unit 40F Equivalence verification unit

Claims (8)

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: a derivation unit that derives, based on a first model that is generated in a first computer modeling environment of model-based systems engineering and represents a function of a system by a combination of a plurality of elements, functional specification connection information that associates the elements defined in the first model with requirement specifications corresponding 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 the 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: 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. 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: A model transformation device according to any one of claims 1 to 3, equipped with the model equivalence verification device according to claim 4. the first model is a SysML® model;
the second model is a Simulink® model;
4. The model transformation device according to claim 1. a step of deriving, by a derivation unit of a model conversion device, 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 a combination of a plurality of elements, and a system specification diagram that is described in accordance with a predetermined requirement specification description method , the first model being generated in a first computer modeling environment of model-based development;
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: 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: