JP2010049439A - System construction method using software model and modeling device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem that since it is not possible for a conventional modeling device to fetch information related with a structure necessary for using mounting information as model information and information related with a behavior from mounting information such as a source code or binary to a modeling device in case of model base development, it is not possible to express the interrelation of the model information and the mounting information as model description. <P>SOLUTION: A modeling device is provided with a model interface information addition means 201 for generating model interface information described in model description language based on the interface information of a module specified by mounting information and interface information and mounting link information for specifying the association of the corresponding processing or variables in the mounting information. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention provides a technique related to a software construction method.

  Conventionally, a software specification / system design method based on a model-based development method using a model description language such as Unified Modeling Language (UML) (registered trademark) has been used for software development. In addition, related development tools (modeling devices) such as UML tools for performing software development using such a development technique are widely provided.

  In system development, a function module (type 1) developed using a model description language and a function module (type 2) provided in the form of source code or binary code without using a model description language are type 1 By converting the function modules into the source code using a model compiler or the like and then integrating them at the level of the type 2 function module and the source code or binary code, it is possible to construct a system in which both types of function modules are mixed.

  As another system construction method, the type 2 function module provided in the source code is converted into the function module described in the model description language and integrated with both types of function modules at the level of the model description language. Is possible.

  Furthermore, in order to improve the accuracy of function modules developed using a model description language, a method for improving the consistency between different UML notations is proposed for the functions of the same function module described in a plurality of UML notations. Has been.

JP 2006-235899 A

  In model-based development, the function / structure of a module to be designed is described in a model description language such as UML (this is referred to as model information). In the model description language, it is possible to describe the relationship between model information of a plurality of modules. For example, by using UML class diagrams, it is possible to describe model information such as class names and method names to be provided for a single class. It is possible to describe the relationship.

  The above conventional method is an effective method for describing the relationship between model information. However, in the type 2 function module developed without using a model description language such as source code or binary code, the function of the module is specified. All information related to structure and behavior cannot be converted into model information using a model description language.

  Specifically, it is difficult to convert binary code into model information that developers can understand and use. Regarding source code, some information can be converted into model information, for example, model information related to the structure of the corresponding model is generated from class definition information such as the class name of the source code and the method name provided. However, it is generally not possible to convert all information provided by module functions including operations such as processing contents of individual functions described as source code into a model description language. For example, in a case where individual processes are executed sequentially, it is difficult to describe this in a higher-level model description language instead of the source code.

  Furthermore, the granularity of the type 1 functional module described in the model description language is often different from the granularity of the type 2 functional module defined by the source code or binary code. For example, the type 1 and type 2 functional modules are different from each other. In a mixed system, care must be taken when replacing the module A1 defined in the model description language with another module A2 defined in the model description language.

For example, the module A1 is replaced with the module A2 on the condition that the module A1 refers to the functional modules B1 and B2 defined by the binary code and the module A2 refers to the functional module B3 defined by the binary code. Determines whether the binary code B1 or B2 is used by another module,
(1) When not used: Since the binary codes B1 and B2 can be replaced with the binary code B3, interface information that enables the module A2 and the binary code B3 to be used mutually is described using a model description language ( The following model interface information).
(2) When used: Since the functions of the three function modules obtained by adding the binary code B3 to the binary codes B1 and B2 are necessary, the functions of the three function modules can be used from other function modules. Describes model interface information.
Such a response is required.

  As described above, the granularity of type 1 functional modules generally defined in the model description language is different from the granularity of type 2 functional modules defined in the implementation language such as source code and binary code. Since each reference relationship is also different, the addition / deletion / replacement of the type 1 function module is complicated for the replacement / addition of the function module and the model interface information associated therewith in order to keep the reference relationship of the type 2 function module correct. Description correction is required.

  Source code, binary code, etc. in a model editor that can create and edit model information using a model description language that describes functional modules, and a modeling device that has a model compiler that converts model information generated by the model editor into source code The type 1 model interface information described in the model description language from the interface information of the type 2 function module defined in the implementation language, and the binary code necessary for function execution or variable access using the model interface information Model interface information adding means for generating mounting link information to be specified is provided.

  As for “function execution” and “variable access”, “function” and “variable” are defined as broad terms. The meaning includes not only a function / variable in a functional language such as C language but also a method / attribute in an object-oriented language such as C ++ language.

  In addition, the modeling apparatus is provided with a division integration unit that divides a functional module defined by an implementation language such as source code or binary code into a plurality of modules, or integrates a plurality of function modules into a single module.

  The model interface information added by the model interface information addition means of the modeling apparatus of the present invention, the model interface information described in the modeling description language in the type 2 module A specified in the implementation language, the model interface information and the function module specified in the implementation language, It is possible to generate and add mounting link information that prescribes the correspondence. As a result, the modeling apparatus can take in information necessary for using the module A in combination with type 1 model information from the mounting information. Further, using the model information regarding the type 2 module A that has been taken in, modeling of function execution and variable access between the type 1 module B defined by the model information and the module A defined by the mounting information. It can be realized with the device.

  As described above, for example, when performing operation verification of model information of type 1 at the model description language level, verification including operation of type 2 model information used by type 1 model information can be performed.

  Further, the modeling device of the present invention divides the module A in the source code or binary code format defined by the mounting information into the module A1 and the module A2 using the dividing means and the model interface information adding means, and the modules A1 and A2 It is possible to generate and add model interface information and mounting link information described in a modeling description language. As a result, the modeling apparatus can divide the module into an appropriate granularity, and can import information on the structure and behavior necessary for using the divided modules A1 and A2 as models from the mounting information.

  As described above, according to the present invention, in the model-based development, it is possible to mix and use the function module defined by the implementation information such as the source code and the binary code and the function module defined by the model description language, thereby improving the software development efficiency. It becomes possible.

  Embodiments of the present invention will be described below with reference to FIGS.

  1 is a system schematic diagram showing the relationship between the structure of a conventional modeling device (hereinafter referred to as a modeling tool) and data such as model data generated by modeling, FIG. 2 is a system schematic diagram of the modeling device of the present invention, and FIG. 3 is modeling. FIG. 4 is a diagram illustrating the operation of model interface information adding means (denoted as model I / F information adding means in the drawing) of the apparatus, and FIG. 4 is a diagram showing the relationship of input / output information of the model interface information adding means.

  In FIG. 1, reference numeral 101 denotes a model editor for generating model data as model information by a user designing using a modeling language, and reference numeral 106 denotes a model compiler for converting model data generated by the model editor 101 into source code as mounting information. , 100 is a modeling tool that is a modeling device including the model editor 101 and the model compiler 106, 110 is a source editor that performs design using a mounting language by a user and generates source code that is mounting information, and 114 is a modeling tool 100. And a source compiler that converts the source code generated by the source editor 110 into binary code that is data in an intermediate format that can be executed by the CPU targeted for execution. 117 is a binary code generated by the source compiler 114. Is a linker which converts the executable final form on Tsu preparative CPU.

  The model data 102 includes model interface information 103 (denoted as model I / F information in the figure) that defines the structure of model information, functions to be provided and functions to be used, and details of processing of the functions to be provided and calls to the functions to be used. Model processing information 104 that defines conditions and the like, and model attribute information 105 that defines other attribute information such as model version numbers.

  For example, in model data using UML, model interface information 103 includes class inheritance / reference relationships of class diagrams, methods (functions) defined by classes, and the like. Further, for example, the processing contents of the function described in the action language in association with each function, the state transition condition of the state diagram, and the like become the model processing information 104.

  The source code 107 includes source interface information 108 (denoted as source I / F information in the figure) that defines a function to be provided and a function to be used, and processing of the function described in an implementation language in association with each function, for example. Similarly, it is composed of source processing information 109 that defines function calling processing described in the implementation language.

  Hereinafter, a software development procedure using a conventional modeling tool will be described with reference to FIG. The user creates a modeling function as model data 102 described in a modeling language using the model editor 101. The created model data 102 is converted into source code 107 by a model compiler 106.

  In addition, the user uses the source editor 110 to create the source code 111 described in an implementation language such as C language. The source code 107 and the source code 111 are converted into binary code 115 that is data in an intermediate format that can be executed by the CPU to be executed by the source compiler 114. The binary code 115 is combined with the other binary code 116 and converted into executable code 118 that can be executed on the target CPU by the linker 117. The source code 111 and the binary code 116 are defined by mounting information and do not have model information.

  On the other hand, the model data 102 is defined by model information and does not have mounting information. The source code 111 and the binary code 116 which are the implementation information are combined with the source code 107 which is the implementation information generated by the modeling tool 100 and finally become an executable code 118.

  As described above, in the conventional modeling apparatus, the mounting information is not taken into the modeling tool as model information but is combined as mounting information.

  In conventional modeling devices, for example, it is possible to generate model information related to the structure of the corresponding model from class definition information such as the class name of the source code and the method name to be provided. All information that is valid as all model information including operations cannot be imported from the implementation information.

  Next, the operation of the embodiment of the present invention will be described with reference to FIG. In FIG. 2, the model interface information adding means 201 corresponds to the interface information described in the model description language based on the interface information of the module specified by the mounting information, and the corresponding processing and variables in the mounting information. Implementation link information that specifies

  In the modeling tool 200 shown in FIG. 2, the binary interface information 202 of the binary code 116 having no model information that has been processed by the linker 117 is fetched into the modeling means as model interface information using the model interface information adding means 201.

  Further, mounting link information that defines the correspondence between the model interface information and the corresponding process or variable of the binary processing information 203 is generated. For example, it is assumed that the binary code 116 has the interface definition / actual processing of the function f () in the binary interface information 202 and the binary processing information 203, respectively.

  The model interface information adding unit 201 generates corresponding model interface information based on information such as the function name, the number of arguments, the type, the type of return value, and the like regarding the function f () of the binary interface information 202. By using this model interface information, for example, the binary code 116 can be used as model information on the class diagram as a component / class that provides the function f () on the model editor 101.

  Further, the binary code 116 defined using the modeling tool 200 is generated by using the mounting link information that defines the correspondence between the model interface information and the binary processing information 203 corresponding to the function implementation generated by the model interface information adding unit 201. The function f () call process can be executed.

  As described above, the model interface information adding unit 201 can use the model interface information adding unit 201 to import the binary code 116 having no model information that has been processed by the linker 117 into the modeling unit and use it as a modeling target. It becomes possible.

  FIG. 3 shows the operation of the model interface information adding unit 201 described above. The binary code 302 having no model information is generated by processing the source code 301 by the source compiler 114. However, it is assumed that only the binary code 302 can be used and the source code 301 cannot be used for some reason.

  The definition and implementation of the function funcA () defined in the source code 301 is held in the binary code 302 as intermediate format data that can be executed by the CPU that is the execution target. In the binary interface information 308, the function funcA () is registered together with information on arguments and return values. In addition, the function funcB () is registered as a function to be referenced together with arguments and return value information. Further, the processing content of the function funcA () is registered in the binary processing information 309.

  The model interface information adding unit 201 generates model interface information 305 from the binary code 302. Information for calling information necessary for executing the function funcA () registered in the binary processing information 309 is generated and stored in the model processing information 306.

  FIG. 4 is a diagram showing the operation of the present embodiment as the relationship of the input / output information of the model interface information adding means 201. By converting the binary code 302 by the model interface information adding unit 201, model information 402 usable by the modeling tool 200 is generated. Information on the function provided or referred to by the model information 402 is generated from the model interface information 305. Processing when the function funcA () is actually called is determined using the model processing information 306. In this example, the implementation of the function funcA () of the binary code 302 is called.

  FIG. 4 shows an example in which model information is handled as graphical model information such as UML. For example, by using the model editor 101, it is possible to define a reference relationship with model information that calls the function funcA () of the model information 402 and a reference relationship with model information that provides processing of the function funcB () as a model. The binary code 302 made up of the mounting information can be used as model information using the modeling tool 200.

  Hereinafter, another embodiment of the present invention will be described with reference to FIGS. FIG. 5 is a system schematic diagram of the modeling apparatus of the present invention, FIG. 6 is a diagram for explaining the operation of the division integration means, FIG. 7 is a diagram for explaining the operation of another embodiment of the present invention having no division integration means, FIG. 8 is a diagram for explaining the operation of another embodiment of the present invention having division integration means, FIG. 9 is an example of using the mounting information in another embodiment of the present invention having no division integration means, and FIG. It is an example of mounting information use in another embodiment of the present invention having a division integration means.

  The operation of another embodiment of the present invention will be described below with reference to FIG. In FIG. 5, the division integration unit 502 inputs the source code 111 defined by the mounting information and provides the division integration result to the model interface information addition unit 501.

  Hereinafter, the details of the operation of the division integration unit 502 will be described with reference to FIG. The division integration designation information 601 is information for designating a method for dividing and integrating the mounting information. In this example, the user specifies that the functions funcA (), funcB (), funcC () are divided and integrated into a group of funcA () and a group consisting of funcB () and funcC ().

  The division integration unit 502 obtains source codes 602 and 603 that define the implementation of funcA (), funcB (), and funcC (), and source code 604 including processing of the function funcA () according to instructions of the division integration designation information 601 The source code 605 including the processing of the functions funcB () · funcC () is generated.

  The effects of the modeling tool 500 having the division integration unit 502 will be described with reference to FIGS. FIG. 7 shows an example in which the division integration unit 502 is not provided.

  In FIG. 7, processing of functions funcA () · funcB () is described in the source code P701 defined by the mounting information. The source code Q702 describes the processing of the function funcC (). The source code 701 and 702 are converted into binary code P703 and binary code Q704 by the source compiler 114, respectively.

  The binary codes 703 and 704 are added with model interface information and the like by the model interface information adding means 501 to become model data 705 and 706, respectively.

  In the above processing without the division integration unit 502, the functions defined by the source codes 701 and 702 are functions that can be used as they are in the model data 705 and 706, respectively.

  An example of using the generated model data is shown in FIG. The model data 901 and 903 are model data generated from the model information, and the model data 705 and 706 are model data generated from the mounting information by using the model interface information adding unit 502 in the processing of FIG.

  In FIG. 9, since the model data 705 is used from both the model data 901 and the model data 903, for example, the model data 903 is corrected, and functions funcB () · funcC () used in association with the correction are, for example, When it is necessary to exchange a new version of the function having the same name, it is necessary to exchange both the model data 705 and the model data 706, and the processing is complicated.

  Further, if the model data 901 requires processing of the conventional function funcA () and the operation becomes inappropriate in the processing of the replaced new function funcA (), the function name of the model data 705 is further duplicated. It is necessary to take measures such as having an old version and a new version after making changes so that there is no change.

  Next, the operation when the division integration unit 502 is provided will be described with reference to FIG. Source code 701 and 702 are input in the same way as in FIG. 7, but by setting the same division integration condition as the division designation information 601 shown in FIG. 6 in the division integration unit 502, it is further generated via the source compiler unit 114. The binary code to be processed has a processing description of the function funcA () in the binary code 803 and a processing description of the functions funcB () · funcC () in the binary code 804.

  As a result, the model data 805 and 806 generated through the model interface information adding unit 502 includes the processing description of the function funcA () in the model data 805 and the processing of the functions funcB () and funcC () in the model data 806. It becomes a structure with description.

  An example of use of the generated model data is shown in FIG. The model data 901 and 903 are model data generated from the model information, and the model data 805 and 806 are model data generated using the model interface information adding unit 502 from the mounting information in the processing of FIG.

  In FIG. 10, for example, when the model data 903 is corrected, and the functions funcB () and funcC () used in connection with the correction must be replaced with, for example, a new version of the function having the same name, the model data 806 is replaced. The model data 805 need not be exchanged.

  As in this example, the modeling tool 500 can capture modules as model information after dividing and integrating modules into an appropriate granularity.

  In the above-described embodiment, the example of dividing and integrating source code as mounting information in the dividing and integrating means has been described. However, binary code can be divided and integrated as mounting information with the same configuration. Yes, the type of mounting information to be divided / integrated is not particularly limited.

  The function defined by the model information by the function of describing the mutual relationship between the type 2 function module defined by the mounting information and the type 1 function module defined by the model information of the model interface information adding means of the present invention Operation cooperation such as mutual call at the model design level using the model description language of the function module defined by the module and the mounting information becomes possible.

  Further, in the operation verification of the type 1 functional module defined by the model information, it is possible to confirm the operation in combination with the type 2 functional module information defined by the mounting information. This is expected to expand the scope of model-based development and improve the accuracy of model operation verification.

  Further, the module structure restructuring function by dividing / integrating the modules specified by the mounting information of the dividing / integrating means of the present invention enables the mounting information having the same granularity as the type 1 function module specified by the model information. Can be used together with the function module of type 2 defined in the above. This simplifies management when replacing type 2 function modules specified in the relevant implementation language in accordance with system configuration changes such as replacement or addition of type 1 function modules specified in the model information. Improvement of construction reliability is expected.

System schematic diagram of conventional modeling equipment System schematic diagram of modeling apparatus in an embodiment of the present invention The figure explaining operation | movement of a model interface information addition means The figure which shows the relationship of the input / output information of a model interface information addition means System schematic diagram of modeling apparatus in an embodiment of the present invention The figure explaining operation | movement of a division | segmentation integration means The figure explaining the operation | movement in the Example of this invention which does not have a division | segmentation integration means. The figure explaining operation | movement in the Example of this invention which has a division | segmentation integration means. Example of use of mounting information in an embodiment of the present invention having no division integration means Example of use of mounting information in an embodiment of the present invention having division integration means

Explanation of symbols

100: Modeling tool 101: Model editor 106: Model compiler 201: Model interface information adding means 502: Division integration means

Claims (16)

A model editor that creates and edits model information using a model description language that describes the structure or behavior of software modules;
In a software system construction method using a model compiler that converts the model information generated by the model editor into source code,
Information that specifies how to execute a function of a binary code that operates on a target device, or information that specifies a method of accessing a variable, and generates model interface information that is interface information described in a model description language. Characteristic system construction method The system construction method according to claim 1,
Information describing a function using the model interface information, or information describing a variable access method, and generating a mounting link information for specifying the binary code. A model editor that creates and edits model information using a model description language that describes the structure or behavior of software modules;
In a software system construction method using a model compiler that converts the model information generated by the model editor into source code,
Reconstruction including source code division / combination,
A system construction method characterized by generating a binary code based on the reconstructed source code and generating model interface information described in a model description language as interface information of the binary code In the system construction method of Claim 3,
Information describing a function using the model interface information or information describing a method of accessing a variable, and generating mounting link information for specifying the binary code for specifying the binary code Construction method A model editor that creates and edits model information using a model description language that describes the structure or behavior of software modules;
In a software system construction method using a model compiler that converts the model information generated by the model editor into source code,
A system construction method characterized by performing reconstruction including division and combination of binary codes, and generating model interface information described in a model description language which is interface information of the reconstructed binary code The system construction method according to claim 5,
Information describing a function using the model interface information, or information describing a variable access method, and generating a mounting link information for specifying the binary code. A model editor that creates and edits model information using a model description language that describes the structure or behavior of software modules;
In a software system construction method using a model compiler that converts the model information generated by the model editor into source code,
Reconstruction by dividing and combining source code,
A system construction method characterized by generating model interface information described in a model description language, which is interface information of reconstructed source code In the system construction method of Claim 7,
Information describing a function using the model interface information, or information describing a variable access method, and generating a mounting link information for specifying the binary code. A model editor that creates and edits model information using a model description language that describes the structure or behavior of software modules;
In a modeling apparatus having a model compiler that converts the model information generated by the model editor into source code,
Model interface information adding means for generating a model interface information described in a model description language, the information specifying a method for executing a function of a binary code operating on a target device or a method for accessing a variable Modeling device characterized by providing The modeling device according to claim 9, wherein
The model interface information adding means is information describing a function using the model interface information or information describing a variable access method, and generates mounting link information for specifying the binary code. Modeling equipment A model editor that creates and edits model information using a model description language that describes the structure or behavior of software modules;
In a modeling apparatus having a model compiler that converts the model information generated by the model editor into source code,
Split / join means for restructuring including source code split / join,
Model interface information adding means for generating a binary code based on the source code reconstructed by the dividing and coupling means and generating model interface information described in a model description language as interface information of the binary code is provided. Characteristic modeling device The modeling device according to claim 11, wherein
The model interface information adding means is information describing a function using the model interface information or information describing a variable access method, and generates mounting link information for specifying the binary code. Modeling equipment A model editor that creates and edits model information using a model description language that describes the structure or behavior of software modules;
In a modeling apparatus having a model compiler that converts the model information generated by the model editor into source code,
Split / join means for performing reconstruction including split / join of binary code,
A modeling apparatus comprising: model interface information adding means for generating model interface information described in a model description language, which is binary code interface information reconstructed by the division and coupling means The modeling device according to claim 13, wherein
The model interface information adding means is information describing a function using the model interface information or information describing a variable access method, and generates mounting link information for specifying the binary code. Modeling equipment A model editor that creates and edits model information using a model description language that describes the structure or behavior of software modules;
In a modeling apparatus having a model compiler that converts the model information generated by the model editor into source code,
Split / join means for restructuring including source code split / join,
A modeling apparatus comprising: model interface information adding means for generating model interface information described in a model description language which is interface information of the source code reconstructed by the division coupling means The modeling device according to claim 15, wherein
The model interface information adding means is information describing a function using the model interface information or information describing a variable access method, and generates mounting link information for specifying the binary code. Modeling equipment

Images