JP5111308B2 - Model-oriented development support device, model-oriented development support method, and model-oriented development support program - Google Patents

Description

  The present invention relates to a model-oriented development support apparatus, a model-oriented development support method, and a model-oriented development support program that support design and development by model-oriented development.

In recent years, model-oriented development for developing a software system based on a standardized modeling method (Model-Driven Architecture (MDA)) has been performed. In such model-oriented development, the function of the program included in the software system to be developed is modeled based on UML (Unified Modeling Language). Then, the upstream process model described abstractly according to the requirements is converted into a downstream process model step by step according to a predetermined model conversion rule, and source code is automatically generated. In such model conversion, when the model element or model conversion rule of any process is changed, it is necessary to perform all model conversions in the following processes again.
Therefore, in Patent Document 1, the generator means divides model elements into predetermined units and assigns a version at the time of model conversion, and at the time of model conversion again, only model elements having different versions are converted. A technique for efficiently performing remodeling by updating has been proposed.
JP 2006-139472 A

  However, the model element of the downstream process generated by the model conversion based on the model element of the upstream process is subjected to the model conversion by the generator means, and then finely adjusted according to the operation information input from the user or additional information May be added. When such information update is performed on the model element in the downstream process, the version by the generator means is not given. For this reason, when the model conversion is performed again by the generator means after the change of the model element based on the operation information input from the user, the change based on the operation information input from the user is overwritten and lost. Will end up.

  The present invention has been made in view of such circumstances, and is model-oriented development support that enables model conversion based on whether or not a model element has been changed according to operation information from a user. An apparatus, a model-oriented development support method, and a model-oriented development support program are provided.

  In order to solve the above-described problem, the present invention provides a plurality of model elements obtained by modeling each function constituting a software system to be developed from an upstream process represented by an abstract concept to a downstream process represented by a source code. A model-oriented development support apparatus that supports design and development of a software system that is performed in a hierarchy of processes, each model element included in the first process among a plurality of processes, and a downstream process corresponding to the first process, Each model element included in the second step and a model storage unit that stores an update date and time indicating the date and time when the model element is stored for each model element are included in the first step. Based on each model element in the first step based on each model element in the first step, a copy model storage unit in which a copy model in which each model element is duplicated is stored. An input unit that accepts an input of a model conversion request to be formed; a model duplication unit that duplicates each model element of the first step and stores the model element in the copy model storage unit when the model conversion request is input to the input unit; Generating each model element of the second step corresponding to each model element of the first step stored in the copy model storage unit based on the determined model conversion rule, and storing it in the copy model storage unit; and Upstream model element identification information for identifying each model element in the first step, downstream model element identification information for identifying a model element in the second step generated based on each model element in the first step, A model element conversion unit that generates a trace element that is associated with an update date and time that indicates the date and time when the model element of step 2 is generated, and a trace that stores the trace element generated by the model element conversion unit Contents of each model element of the second step generated in the element storage unit and the model element conversion unit and stored in the copy model storage unit, and contents of each model element of the second step stored in the model storage unit When the model content comparison unit and the model content comparison unit that determine whether the content is different determine that the content is different, each model element of the first process stored in the model storage unit An update date and time comparison unit that compares the update date and time, the update date and time of each model element in the second step, and the update date and time included in the trace element corresponding to the model element, and determines whether the update date and time are different; If the update date and time comparison unit determines that the update date and time are different, the model elements stored in the copy model storage unit and the model elements stored in the model storage unit are integrated based on a predetermined procedure. In the model storage And a model update unit to be stored.

In the present invention, when the update date and time comparison unit determines that the update date and time are different, the model element stored in the model element and the model element stored in the copy model storage unit are given priority. An integrated procedure storage unit that stores an integration procedure indicating whether to integrate model elements;
The model update unit integrates each model element stored in the copy model storage unit and the model element stored in the model storage unit based on the integration procedure stored in the integration procedure storage unit. It is memorized in.

  Further, according to the present invention, the input unit accepts input of change information for changing the content of the model element stored in the model storage unit, and is stored in the model storage unit according to the change information input to the input unit. A model editing unit that changes the content of the model element and associates and stores the date and time of the change as the update date and time corresponding to the model element in the model storage unit.

  In the integrated procedure storage unit, the present invention provides a condition determined based on the presence or absence of each trace element corresponding to the model element and the update date / time of each model element stored in the model storage unit. The model update unit determines whether or not there is a trace element corresponding to the model element or whether each update date / time matches the condition for each model element. If they all match, each model element stored in the copy model storage unit based on a predetermined procedure and the model element stored in the model storage unit are integrated, and if there is a model element that does not match, The integration is performed according to the change information of the model element input to the input unit.

In addition, the present invention is a software that performs by layering each model element that models each function constituting a software system to be developed into a plurality of processes from an upstream process represented by an abstract concept to a downstream process represented by a source code. Supporting system design and development, each model element included in the first process among the plurality of processes, each model element included in the second process that is a downstream process corresponding to the first process, For each model element, a model storage unit in which an update date and time indicating the date and time when the model element is stored is stored in advance, and a copy model in which a copy model in which each model element included in the first step is duplicated is stored A trace in which a trace element indicating a relationship between the storage unit and each model element included in the second process corresponding to each model element included in the first process is stored is stored. A model-oriented development support method using a model-oriented development support device having a storage element storage unit, wherein the input unit generates each model element in the second step based on each model element in the first step Receiving a model conversion request to be input,
When a model conversion request is input to the input unit, the model replication unit replicates each model element in the first step and stores it in the copy model storage unit; and the model element conversion unit includes a predetermined model Based on the conversion rule, each model element of the second step corresponding to each model element of the first step stored in the copy model storage unit is generated and stored in the copy model storage unit, and Upstream model element identification information for identifying each model element of the process, downstream model element identification information for identifying the model element of the second process generated based on each model element of the first process, and A step of generating a trace element associated with an update date and time indicating the generation date and time of the model element and storing the trace element in the trace element storage unit, and a model content comparison unit are generated in the model element conversion unit. -The contents of each model element of the second step stored in the model storage unit and the contents of each model element of the second step stored in the model storage unit are compared to determine whether the contents are different. When the step and the update date and time comparison unit determine that the content is different by the model content comparison unit, the update date and time of each model element of the first process stored in the model storage unit and each model of the second process The step of comparing the update date / time of the element and the update date / time included in the trace element corresponding to the model element to determine whether the update date / time is different from the update date / time of the model update unit differs from the update date / time comparison unit. Is determined, the model element stored in the copy model storage unit and the model element stored in the model storage unit are integrated and stored in the model storage unit based on a predetermined procedure. Characterized in that it comprises a and.

In addition, the present invention is a software that performs by layering each model element that models each function constituting a software system to be developed into a plurality of processes from an upstream process represented by an abstract concept to a downstream process represented by a source code. Supporting system design and development, each model element included in the first process among the plurality of processes, each model element included in the second process that is a downstream process corresponding to the first process, For each model element, a model storage unit in which an update date and time indicating the date and time when the model element is stored is stored in advance, and a copy model in which a copy model in which each model element included in the first step is duplicated is stored A trace in which a trace element indicating a relationship between the storage unit and each model element included in the second process corresponding to each model element included in the first process is stored is stored. Accepting an input of a model conversion request for generating each model element of the second process based on each model element of the first process to a computer of a model-oriented development support apparatus having a storage element storage unit; When a conversion request is input, a step of copying each model element of the first step and storing it in the copy model storage unit, and a second stored in the copy model storage unit based on a predetermined model conversion rule Upstream model element identification information for generating each model element of the second process corresponding to each model element of the first process and storing it in the copy model storage unit, and identifying each model element of the first process; Downstream model element identification information for identifying the model element of the second process generated based on each model element of the first process, and update date and time indicating the date and time when the model element of the second process is generated Is generated and stored in the trace element storage unit, the contents of each model element in the second step stored in the copy model storage unit, and the second stored in the model storage unit of comparing the content of each model element step, determining whether the content is different, if the contents are determined as different, each model elements of the first step which is stored in the model storage unit and Modified, and update date and time of each model element of the second step is compared with the update date and time included in the trace elements corresponding to the model element, determining whether the update date and time are different, update When it is determined that the date and time are different, each model element stored in the copy model storage unit and the model element stored in the model storage unit are integrated and stored in the model storage unit based on a predetermined procedure. Make A model-oriented development support program that executes steps.

  As described above, according to the present invention, model-oriented development support for generating each model element of the second process that is the downstream process based on each model element of the first process that is the upstream process in model-oriented development. The apparatus duplicates each model element of the first step in response to an input model conversion request, stores a copy model, and each of the first steps of the copy model based on a predetermined model conversion rule Each model element of the second process corresponding to the model element is generated, and generated based on upstream model element identification information for identifying each model element of the first process and each model element of the first process A trace element in which downstream model element identification information for identifying a model element of the second process and an update date and time indicating the date and time when the model element of the second process is generated is generated, and based on the copy model The content of each model element of the generated second step is different from the content of each model element of the second step stored in advance, and the update date and time of the model element of the second step and the model element When the update date and time of the corresponding trace element is different, the model elements stored based on the copy model and the model elements generated based on the copy model are integrated based on a predetermined procedure. By comparing the update date / time of the element and the update date / time of the trace element, it is possible to determine whether or not the model element stored in advance is generated by model conversion. For example, an operation input from the user It is possible to perform model conversion depending on whether or not an updated change is made according to information or the like.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
<Configuration>
FIG. 1 is a block diagram illustrating a configuration of a model-oriented development support apparatus 100 according to the present embodiment. The model-oriented development support device 100 is a computer device that supports design and development of a software system by model-oriented development based on a standardized modeling technique. The model-oriented development support apparatus 100 includes an input unit, an output unit, a control unit, a calculation unit, and a storage unit, and a so-called PC (personal computer) or server dedicated hardware device can be applied. The model-oriented development support apparatus 100 includes an input unit 110, a model editing unit 120, a model storage unit 130, a control unit 140, and a copy model storage unit 150.

  Model-oriented development is a program development method that divides each model element that constitutes a program included in the software system to be developed into a plurality of hierarchical processes from the upstream hierarchy represented by the abstract concept to the downstream hierarchy represented by the source code. It is. The model element is information indicating the function of the software system to be developed. First, the developer models the function of the software system to be developed by UML (Unified Modeling Language) based on the system requirements. For example, the model-oriented development support apparatus 100 has a function such as a UML editor and generates UML information according to operation information input from a development user. The model-oriented development support apparatus 100 converts each model element of the upstream process model in which the system requirements are modeled into a model element of the downstream process model based on a predetermined model conversion rule such as QVT (Queries / Views / Transformations). Convert to

  Here, when a downstream process model element is generated from an upstream process model element, the upstream process model element identification information, the generated downstream process model element identification information, and model conversion are performed. A trace element that is information associated with the date and time of the generation is generated. Here, for example, the model element in the upstream process model is a model (platform independent model (PIM)) that does not depend on the system operating environment or the program language. Conversion into model elements of a downstream process model (platform specific model (PSM (Platform Specific Model))) in which the program language is realized is performed.

  Model elements of each hierarchical process in the model-oriented development are stored in the model-oriented development support apparatus 100 for each process. Even after generation of the model element of the downstream process is performed based on the model element of the upstream process and the model conversion is performed, the model element of the upstream process is stored in the model-oriented development support apparatus 100, and thus the model conversion is performed. It is also possible to edit the model elements of the upstream process afterwards. In this way, in model-oriented development, the software system to be developed is represented by model elements in each process from the upstream process to the downstream process such as business modeling, requirement definition, external design, internal design, program implementation, and testing. The software system is developed by converting the model element of the upstream process into the model element of the downstream process model based on a predetermined model conversion rule. This makes it possible to automate software system development, reduce development man-hours, prevent system requirements from being separated from implementation, and develop an efficient software system.

The input unit 110 is an input device that accepts information input from a user, and for example, a keyboard or a mouse can be applied.
The model editing unit 120 edits model elements of each hierarchical process in model-oriented development according to operation information input from the user to the input unit 110 and stores the model elements in the model storage unit 130. The model editing unit 120 may have different editing functions for each process in model-oriented development. For example, in the present embodiment, model-oriented development hierarchized into three processes of a requirement examination process, a detailed design (external design) process, and a program design (internal design) process is described as an example. For example, a model creation tool such as a UML editor can be applied to the model editing unit 120 in the requirement study process and the detailed design (external design) process. Further, a program editor, a text editor, etc. can be applied in the program design process and the mounting process.

  2 and 3 are diagrams showing an example of design of model elements in the present embodiment. For example, three model elements of “entity” (a-1), “screen structure” (a-2), and “screen transition” (a-3) are shown as model elements of the detailed design process (a). The entity (a-1) is a model element indicating data used in the software system to be developed. Based on the entity (a-1) which is a model element of the detailed design process, a DB access class (b-1) which is a model element of the program design process (b) which is a downstream process is determined by a predetermined model conversion rule 1. ) Is generated. Here, one DB access class element is generated for each entity element. The entity attribute is converted into a DB access class parameter.

  Similarly, it is a model element of the program design process which is a downstream process based on the model conversion rule 2 determined in advance based on the model element of the detailed design process indicating the screen structure (a-2) of the software system to be developed. A bean class (b-3) and a JSP (Java (registered trademark) Server Pages) element (b-4) are generated. Here, one JSP element is generated for each screen structure element in the detailed design process. JSP is a web service technology using JAVA (registered trademark), and a JSP element is a model element corresponding to a function of a web service based on JSP. The attribute of the screen structure element of the detailed design process is set as an input / output tag of the JSP element. One bean class element is generated for each screen structure element in the detailed design process. Here, the attribute of the screen structure element in the detailed design process is set as the attribute of the bean class element.

  Similarly, it is a model element of a program design process which is a downstream process based on a model conversion rule 3 determined in advance based on a model element of a detailed design process indicating screen transition (a-3) of the software system to be developed. A command class (b-2) is generated. Here, one command class element is generated for each screen transition element included in the detailed design process model. Here, the reference converted from the entity element is set as an attribute of the command class. The bean class element generated from the boundary element that refers to the screen transition element is set as the input / output parameter attribute of the command class element.

  Returning to FIG. 1, the model storage unit 130 stores information indicating a model in model-oriented development, and stores a model element storage unit 131 in which information indicating a model element of each hierarchical process in model-oriented development is stored. A trace element storage unit 132 in which trace elements indicating the relevance of model elements for each hierarchical process stored in the storage unit 131 are stored.

  FIG. 4 is a diagram illustrating an example of model element data stored in the model element storage unit 131. The model elements are “process”, “model element name”, “model element ID”, “parent element ID”, “upstream trace”, “downstream trace”, “model element type”, “ It includes information associated with “model last update time”.

  “Process” is information indicating a hierarchical process of model elements. For example, “basic design”, “detailed design”, “program design”, and the like are applied. Here, model elements with the process as “whole” are defined, and the model elements of each hierarchical process constitute a tree structure with the “whole” model element as a root. Here, the entire tree structure is referred to as a project, and a model element that becomes the root of each hierarchical process belongs to a lower level of the model element that becomes the root of the project. The model elements included in the hierarchical process belong to the lower level of each model element serving as the process route.

“Model element name” is a name indicating the contents of the model element. For example, the model element that is the root of the tree structure is “development project”, the model element that is the root of the basic design process is “basic design process”, and the model element that shows a screen sample in the basic design process is “screen mock A name such as “UP_A” is applied.
“Model element ID” is identification information of a model element. For example, identification information such as “P_PRJ — 0001” is associated with the model element that is the apex of the project, “A_DP — 0001” is associated with the model element that is the apex of the basic design process, and “A_CSD_MDES — 0001” is associated with the screen mockup.

  “Parent element ID” is information indicating the belonging relationship between model elements in each hierarchical process, and constituting the model elements in a tree structure. For example, the model element “A_DP_0001” of the root of the basic design process is associated with the “parent element ID” of the model element “A_CSD_MDES_0001” of the basic design process, and the screen mockup “A_CSD_MDES_0001” belongs to the basic design process. Shown to be a model element.

  “Upstream trace” is identification information of a trace element generated when the model element is generated when the model element is a model element generated based on a model element in an upstream process. The trace element identification information corresponds to a trace ID stored in a trace element storage unit 132 described later. Thus, when the downstream process model element is generated based on the upstream process model element, a trace element indicating the relationship between the upstream process model element and the downstream process model element is generated, and the trace element is generated. Stored in the storage unit 132. For example, the model element “B_SSD_SDES_0001” of the detailed design process is associated with “TR_0000” as the trace ID of the upstream trace.

  The “downstream trace” is identification information of a trace element indicating a relationship with the generated model element of the downstream process when the model element of the downstream process is generated based on the model element. The trace element identification information corresponds to the trace ID stored in the trace element storage unit 132. For example, the model element “A_CSD_MDES_0001” of the basic design process is associated with “TR_0000” as the trace ID of the downstream trace.

“Model element type” is information indicating the type of the corresponding model element. For example, information such as “project” is associated with the model element that is the root of the tree structure of the model element in the project, and information such as “mockup” is associated with the screen mockup.
The “model last update time” is information indicating the update date and time when the corresponding model element is generated or the content is changed and stored in the model element storage unit 131 after the generation. For example, the model last update time is expressed in the format of “yyyy: mm: dd: hh: mn: ss”, and “(4 digits of the year): (2 digits of the month): (2 digits of the day): (2 digits of the hour) ): (2 digits for minutes): (2 digits for seconds) ”.

FIG. 5 is a diagram illustrating an example of trace element data stored in the trace element storage unit 132. The trace element includes information in which “trace ID”, “upstream element”, “downstream element”, and “trace last update time” are associated with each other.
“Trace ID” is identification information of a trace element. “Upstream element” is identification information of an upstream process model element associated with the trace information, and corresponds to the model element ID stored in the model element storage unit 131. The “downstream element” is identification information of the model element of the downstream process associated with the trace information, and corresponds to the model element ID stored in the model element storage unit 131. The “trace last update time” is information indicating the time when the trace process is generated when the model element of the downstream process is generated based on the model element of the upstream process and the model conversion is performed. If the model conversion is performed again from the model element of the same upstream process to the model element of the same downstream process, and the content of the model element of the downstream process is changed and stored in the model element storage unit 131, the trace The content of the model element in the downstream process is updated and updated to information indicating the time stored in the model element storage unit 131 at the final update time.

  FIG. 6 is a diagram conceptually showing the relationship between each model element and each trace element shown in FIG. 4 and FIG. As shown in FIG. 6, model elements of the modeled software system include a model element “P_PRJ — 0001” indicating a project as a root, a model element “A_DP — 001” serving as a root of a basic design process, a route of a detailed design process, and The model element “B_DP — 001” and the model element “C_DP — 001” serving as the root of the program design process belong to the lower level. In addition, each model element belongs to the lower level of the root of each hierarchical process. Here, in this embodiment, the relationship between the basic design process, the detailed design process, and the program design process is called a hierarchy, and is expressed as upstream and downstream. For example, the basic design process is a hierarchy of the upstream process with respect to the detailed design process, and the detailed design process is a hierarchy of the downstream process with respect to the basic design process. In this embodiment, the relationship between model elements belonging to the lower order of the root of each hierarchical process is referred to as belonging, and is expressed as higher order and lower order. For example, the model element “A_DP_0001” that is the root of the basic design process is a higher-order model element than the model element “A_CSD_MDES_0001” of the basic design process, and the model element “A_CSD_MDES_0001” of the basic design process is the same as the basic design process. The model element “A_DP — 0001” that is the root of the process is a lower model element.

  For example, in the example of FIG. 6, the model element “B_SSD_SDES_0001” of the detailed design process that is the downstream process is generated based on the model element “A_CSD_MDES_0001” of the basic design process, and the relationship is indicated by the trace element “TR_0000”. Has been. Further, for example, two model elements of a model element “C_DCD_JSP_0001” and a model element “C_DEC_BEAN_0001” of the program design process are generated based on the model element “B_SSD_SDES_0001” of the detailed design process, and the relationship is a trace element. It is indicated by “TR — 0001” or trace element “TR — 0004”. Further, for example, the model element “A_CSD_MDES_0001” belongs to the lower order in the model element “A_DP_0001” that is the route of the basic design process. Further, the model element “C_DCD_BPRO_0003” of the program design process is a model element generated by the model editing unit 120 or the like, for example, without the model conversion by the model element conversion unit 143 because there is no corresponding trace element.

  FIG. 7 is a diagram illustrating detailed data examples of model elements and trace elements in the detailed design process stored in the model storage unit 130. As described above, the model elements stored in the model element storage unit 131 correspond to the model element type for each hierarchical process corresponding to the function of the software system to be developed in addition to the information shown in the data example of FIG. Various design information etc. are included. In FIG. 7, the design information corresponding to the model element type is underlined. For example, (a) shows a data example of a model element of the screen structure “B_SSD_SDES_0001” of the detailed design process. The model element “B_SSD_SDES_0001” is a model element corresponding to one screen to be displayed on the display in the software system. In addition to the common information shown in FIG. 4, a “screen” indicating one or a plurality of screen items included in this screen is displayed. Information of “Item list”, “Screen transition list (in)” indicating the transition source screen that transitions to this screen, and “Screen transition list (out)” indicating the transition destination screen that transitions from this screen are included It is.

  FIG. 7B illustrates a data example of the model element of the screen item “B_SSD_SPRO_0001” of the detailed design process. The model element “B_SSD_SPRO_0001” indicates the contents of the screen item included in the screen indicated by the screen structure “B_SSD_SDES_0001”. In addition to the common information shown in FIG. 4, both the physical data type and the display data type of the screen item are included. It is a character string, the data length of the character string is 16 (characters), and the character string “user name” is displayed as a display label.

  FIG. 8 is a diagram illustrating a detailed data example of model element information of the program design process stored in the model storage unit 130. For example, (a) shows a data example of a model element of a JSP element “C_DCD_JSP_0001” which is a program of a detailed design process. The model element “C_DCD_JSP_0001” is a model element generated based on the screen structure “B_SSD_SDES_0001” of the detailed design process, and is information representing the screen structure based on JSP. In addition to the common information shown in FIG. 4, the model element “C_DCD_JSP_0001” includes the “physical name” of the model element, the “attribute list” indicating the model element as an attribute included in the JSP, and the transition to this screen Information of “bean class (in)” indicating the original software component and “bean class (out)” indicating the software component of the transition destination from this screen is included.

  FIG. 8B shows a data example of the model element of the input attribute item “C_DCD_JSPAT_0001” in the program design process. The model element “C_DCD_JSP_0001” is a model element generated based on the screen structure “B_SSD_SPRO_0001” of the detailed design process, and is information representing an input item on the screen. In addition to the common information shown in FIG. 4, the model element “C_DCD_JSPAT_0001” has a physical name “ATTRIBUTE_1” in the program, a physical data type “String” (character string), and a display data type is a character string. Yes, and the display label is “user name”.

Returning to FIG. 1, the control unit 140 generates a model element for the downstream process based on the model element for the upstream process stored in the model storage unit 130 and performs model conversion. The control unit 140 includes a model acquisition unit 141, a model replication unit 142, a model element conversion unit 143, a model content comparison unit 144, an update date / time comparison unit 146, a model update unit 146, and a merge method determination unit 147. It has.
When the model conversion execution instruction is input to the input unit 110, the model acquisition unit 141 reads the model elements stored in the model storage unit 130.

  The model duplication unit 142 duplicates the model element read from the model storage unit 130 by the model acquisition unit 141 and stores the model element in the copy model storage unit 150 as a copy model. FIG. 9 is a diagram illustrating a concept of model conversion processing by the control unit 140. Here, as shown in the column (a) of FIG. 9, the model duplicating unit 142 calculates the project root (“P_PRJ_0001”) from each model element (hereinafter referred to as a real model) stored in the model storage unit 130. Only the model element (“A_DP_0001” and “A_CSD_MDES_0001”) of the most upstream process and the model element (“B_DP_0001”) of the root of each hierarchical process are stored in the copy model storage unit 150 as a copy model.

  Returning to FIG. 1, the model element conversion unit 143 performs conversion processing of each model element of the copy model copied by the model copy unit 142 and stored in the copy model storage unit 150. The model element conversion unit 143 uses a model conversion rule stored in advance in its own storage area from each model element in the upstream process of the copy model stored in the copy model storage unit 150 by the model duplication unit 142 to perform the downstream process. A model element is generated, stored in the copy model storage unit 150, and model conversion is performed. As the model transformation rule, for example, QVT (Queries / Views / Transformations) which is a standard of model transformation defined by OMG (Object Management Group) can be applied. For example, as illustrated in FIG. 9B, the model element conversion unit 143 generates a model element “B_SSD_SDES_0001” for the downstream process based on the model element “A_CSD_MDES_0001” for the upstream process in the copy model.

Returning to FIG. 1, the model content comparison unit 144 compares the content of each model element of the downstream process stored in the model storage unit 130 with the model element of the corresponding downstream process stored in the copy model storage unit 150. Then, it is determined whether there are model elements having different information contents.
The update date and time comparison unit 146 determines that the model content comparison unit 144 determines that there are model elements having different information contents in the model elements of the actual model and the copy model. Read the last update date / time of the model element and the last update date / time of the trace element whose downstream trace is the model element or the last update date / time of the model element of the upstream process corresponding to the model element, and whether the update date / time is different Determine. As shown in FIG. 9C, the actual model and the copy model are compared.

  Returning to FIG. 1, the merging method determination unit 147 performs a merging process for integrating the comparison result of the model content comparison unit 144, the comparison result of the update date / time comparison unit 146, and the model elements stored in the merging method storage unit 160. Based on the method, the merge method between the actual model and the copy model is determined. The merging method storage unit 160 stores in advance a merging method corresponding to a difference condition between the actual model and the copy model. For example, when the model elements of the upstream process and the downstream process are different, for example, “Upstream addition is reflected”, “Upstream change is reflected”, “Upstream deletion is reflected”, and “Downstream addition is maintained”. , “Keep downstream changes”, “Keep downstream deletions”, etc. Among the merge methods determined by the merge method determination unit 147, the merge performed by the merge method stored in the merge method storage unit 160 is referred to as automatic merge, and on the contrary, the merge method is presented to the user, Merging performed by letting the user select a merging method is called manual merging.

"Upstream addition reflected" is an automatic function that generates model elements for downstream processes corresponding to the model elements of the added upstream processes and reflects them in the actual model when model elements are added to the upstream processes after model conversion. Indicates to perform a merge.
“Upstream changes reflected” means that if changes are made to the model element contents of the upstream process after model conversion, the model elements of the downstream process are generated based on the changed model elements of the upstream process, and the actual model Indicates that automatic merging will be performed.
"Upstream deletion reflected" performs automatic merging to delete the model element of the downstream process of the actual model corresponding to the deleted model element of the upstream process when the model element of the upstream process has been deleted after model conversion It shows that.

“Keep downstream addition” does not delete the model element added to the downstream process in the actual model and keeps the memory of the added model element when the model element is added to the downstream process after model conversion Indicates that automatic merging is performed.
“Keep downstream changes” means that if the model element of the downstream process has been changed after model conversion, the model of the downstream process in the actual model is used regardless of the model element generated based on the model element of the corresponding upstream process. Indicates that automatic merging is performed to preserve element changes.
“Keep downstream deletion” means that if the model element of the downstream process has been deleted after model conversion, the model of the downstream process in the actual model is used regardless of the model element generated based on the model element of the corresponding upstream process. Indicates that automatic merging is performed to maintain element deletion.

The merge method storage unit 160 stores information indicating whether each of these merge methods is valid (ON) or invalid (OFF) in association with each other. The merge method determination unit 147 performs a merge process between the actual model and the copy model based on such a merge method stored in the merge method storage unit 160. Further, the merge method determination unit 147 is in the case where there is a difference in the model element contents between the actual model and the copy model, and there is a model element that does not satisfy the merge method condition stored in the merge method storage unit 160. Performs the merging of the actual model and the copy model based on the operation information input from the input unit 110.
The model update unit 145 performs merge processing between the actual model stored in the model storage unit 130 and the copy model stored in the copy model storage unit 150 based on the determination result of the merge method by the merge method determination unit 147. . Also, as illustrated in FIG. 9, the model update unit 145 deletes the copy model stored in the copy model storage unit 150 when the merge process is completed.

<Operation example>
Next, with reference to FIG. 10, first, an outline of an operation example of model conversion processing performed by the model-oriented development support apparatus 100 according to the present invention will be described. When an execution instruction for model conversion processing is input to the input unit 110, the model acquisition unit 141 reads the model elements stored in the model storage unit 130. The model duplication unit 142 duplicates the model element read by the model acquisition unit 141 and stores it in the copy model storage unit 150 as a copy model (step S1).

  The model element conversion unit 143 generates a model element for the downstream process based on the model element for the upstream process stored in the copy model storage unit 150 (step S2). The model content comparison unit 144 compares the model element of the downstream process of the copy model stored in the copy model storage unit 150 with the model element of the downstream process of the actual model stored in the model element storage unit 131, and the difference is It is determined whether or not there is (step S3). In step S <b> 3, the model content comparison unit 144 makes a difference between the model element of the downstream process of the copy model stored in the copy model storage unit 150 and the model element of the downstream process of the actual model stored in the model element storage unit 131. If it is determined that there is no data (step S3: No), the model update unit 145 ends the process without updating the actual model stored in the model storage unit 130 (step S4).

  On the other hand, in step S <b> 3, the model content comparison unit 144 includes the model element of the downstream process of the copy model stored in the copy model storage unit 150, and the model element of the downstream process of the actual model stored in the model element storage unit 131. If it is determined that there is a difference between them (step S3: Yes), the merge method determination unit 147 performs a merge method determination process of whether to perform automatic merging or manual merging based on the comparison result of each model element. (Step S5).

  The merge method determination unit 147 determines whether or not the comparison results of all model elements match the merge method conditions stored in the merge method storage unit 160, and automatically calculates all the differences extracted in step S5. If it is determined that the merging is not possible (step S6: No), after executing the executable automatic merging, the model updating unit 145 accepts the editing of the model element having a difference by the model editing unit 120, and manually The model element merging process is performed (step S7). On the other hand, if the merge method determination unit 147 determines that it is possible to perform automatic merging for all the differences extracted in step S5 (step S6: Yes), the model update unit 145 determines that the copy model storage unit 150 The model element generated by the model conversion is merged based on the merging method stored in (Step S8).

Next, with reference to FIGS. 11, 12, and 13, the merge method determination process performed by the model-oriented development support apparatus 100 in step S <b> 5 described above will be described in detail.
The model content comparison unit 144 converts the copy model downstream process model element stored in the copy model storage unit 150 in step S3 and the actual model downstream process model element stored in the model element storage unit 131. When it is determined that there is a difference, information indicating the state of the difference is input to the merge method determination unit 147 (step S10).

  When the merge method determination unit 147 determines that the difference between the actual model and the copy model is a difference in which no model element exists in any model (step S11: Yes), the model that does not exist is the actual model. Or a copy model is determined (step S12). When the merge method determination unit 147 determines that a model element having a difference does not exist in the actual model but exists in the copy model (step S13: No), the trace element having the model element as a downstream element is the trace element. It is determined whether it is stored in the storage unit 132 (step S14).

  When the merge method determination unit 147 determines that a trace element having a different model element as a downstream element is not stored in the trace element storage unit 132 (step S15: No), only the copy model does not exist in the actual model. The model element existing in the model element is a model element generated for the first time in the model conversion process by the model element conversion unit 143 (step S16). Therefore, the merge method determination unit 147 reads the merge method stored in the merge method storage unit 160, and determines that automatic merging is performed if "reflect upstream addition" is ON (step S17: Yes). If “Upstream addition is reflected” is OFF (step S17: No), it is determined that manual merging is performed.

  On the other hand, when the merge method determination unit 147 determines in step S15 that a trace element having a different model element as a downstream element is stored in the trace element storage unit 132 (step S15: Yes), The model element of the downstream process is deleted after the model conversion in which the model element of the downstream process is generated based on the model element. Therefore, the update date / time comparison unit 146 reads the last update date / time of the model element in the upstream process and the last update date / time of the corresponding trace element. The merge method determination unit 147 compares the last update date / time of the model element in the upstream process with the last update date / time of the corresponding trace element, and determines which last update date / time is newer (step S18).

  When the merge method determination unit 147 determines that the last update date and time of the model element in the upstream process is newer than the last update date and time of the corresponding trace element (step S19: Yes), the model element in the upstream process is changed after the model conversion. (Step S20). The merge method determination unit 147 reads the merge method stored in the merge method storage unit 160, and determines that automatic merging is performed if “maintain downstream deletion” is ON (step S21: Yes). If “maintain downstream deletion” is OFF (step S21: No), it is determined that manual merging is performed.

  On the other hand, when the merge method determination unit 147 determines in step S19 that the last update date and time of the model element in the upstream process is not newer than the last update date and time of the corresponding trace element (step S19: No), the upstream process after the model conversion. No change has been made to the model element (step S22). The merge method determination unit 147 reads the merge method stored in the merge method storage unit 160, and determines that automatic merging is performed if “maintain downstream deletion” is ON (step S23: Yes). If “maintain downstream deletion” is OFF (step S23: No), it is determined that manual merging is performed.

  If the merge method determination unit 147 determines in step S11 that the difference between the actual model and the copy model is not a difference in which no model element exists in any model (step S11: No), the process proceeds to step S30 in FIG. move on. In this case, there is a model element of the downstream process corresponding to both the actual model and the copy model. When the update date and time comparison unit 146 reads the last update date and time of the model element in the downstream process and the last update date and time of the corresponding trace element from the model storage unit 130, the merge method determination unit 147 Is determined (step S30).

  When the merge method determination unit 147 determines that the last update date and time of the model element in the downstream process is not newer than the last update date and time of the corresponding trace element (step S31: No), after the model conversion, only the model element in the upstream process Has been changed. Therefore, the merge method determination unit 147 reads the merge method stored in the merge method storage unit 160, and determines that automatic merging is performed if "reflect upstream changes" is ON (step S32: Yes). On the other hand, if “reflect upstream changes” is OFF (step S33: No), it is determined that manual merging is performed.

  On the other hand, when the merge method determination unit 147 determines in step S31 that the last update date and time of the model element in the downstream process is newer than the last update date and time of the corresponding trace element (step S31: Yes), after model conversion Downstream process model elements have changed. The merge method determination unit 147 determines which of the latest update date / time of the model element in the upstream process and the latest update date / time of the trace element is new (step S34).

  When the merge method determination unit 147 determines that the last update date and time of the model element in the upstream process is newer than the last update date and time of the trace element (step S35: Yes), after the model conversion, the model element and the downstream process in the upstream process Both model elements have been changed. In this case, since automatic merging based on the setting of the merging method cannot be performed, the merging method determination unit 147 determines that manual merging is performed (step S36).

  On the other hand, if the merge method determination unit 147 determines in step S35 that the last update date / time of the model element in the upstream process is not newer than the last update date / time of the corresponding trace element (step S35: No), after the model change Only the model elements of the downstream process are changed. In this case, the merge method determination unit 147 reads the merge method stored in the merge method storage unit 160, and determines that automatic merging is performed if “maintain downstream changes” is ON (step S38: Yes). . On the other hand, if “maintain downstream changes” is OFF (step S38: No), it is determined that manual merging is performed.

  If the merge method determination unit 147 determines in step S13 that the model element having the difference exists in the actual model and does not exist in the copy model (step S13: Yes), the process proceeds to step S40 in FIG. The merge method determination unit 147 determines whether or not the trace element corresponding to the model element in the downstream process is stored in the trace element storage unit 132 (step S40). When the merge method determination unit 147 determines that the trace element corresponding to the model element in the downstream process is not stored in the trace element storage unit 132 (step S41: No), the model element is a model by the model element conversion unit 143. For example, model elements generated according to operation information input to the model editing unit 120 instead of conversion. The merge method determination unit 147 reads the merge method stored in the merge method storage unit 160 (step S42), and determines that automatic merging is performed if “maintain downstream addition” is ON (step S43: Yes). To do. On the other hand, if “maintain downstream addition” is OFF (step S43: No), it is determined that manual merging is performed.

  On the other hand, when the merge method determination unit 147 determines that the trace element corresponding to the model element in the downstream process is stored in the trace element storage unit 132 (step S41: Yes), the model element in the upstream process after the model conversion. Has been deleted. In this case, it is determined which of the latest update date / time of the model element in the downstream process and the last update date / time of the corresponding trace element is newer (step S44). When the merge method determination unit 147 determines that the last update date and time of the model element in the downstream process is not newer than the last update date and time of the corresponding trace element (step S45: No), the model element in the downstream process is converted after the model conversion. It has not changed. The merge method determination unit 147 reads the merge method stored in the merge method storage unit 160 (step S48), and determines that automatic merging is to be performed if “reflect upstream deletion” is ON (step S49: Yes). To do. On the other hand, if “reflect upstream deletion” is OFF (step S49: No), it is determined that manual merging is performed.

  On the other hand, when the merge method determination unit 147 determines in step S45 that the last update date and time of the model element in the downstream process is newer than the last update date and time of the corresponding trace element (step S45: Yes), the model element in the downstream process Has been changed after model conversion. The merge method determination unit 147 reads the merge method stored in the merge method storage unit 160 (step S46), and determines that automatic merging is performed if “maintain downstream changes” is ON (step S47: Yes). To do. On the other hand, if “maintain downstream changes” is OFF (step S47: No), it is determined that manual merging is performed.

  Next, with reference to FIG. 14 to FIG. 18, an example of a model conversion merge process will be described. FIG. 14 shows that the operation process transitions in the order of (a), (b), and (c). As shown in the column (a), the actual model in which the model element “A” (0) exists is shown in the initial state. Here, “A” is the model element ID, and (0) indicates the last update date and time. Here, for the sake of convenience, the last update date and time is indicated by an integer that increases by one according to before and after the date and time. For example, (0) indicates that the last update date is older than (1), (1) indicates that the last update date is older than (2), and (1) and (1) indicate that the last update date is Indicates simultaneous. In the column (b), the copy model is generated from the actual model, the model element “A ′” of the downstream process is generated from the model element “A” of the upstream process of the copy model, and the trace element is generated. Yes. Also, the actual model and the copy model are compared. In the column (c), the state of the real model after the automatic merging is performed is shown. Thus, the model element (a) represented by a rectangle is the model element of the upstream process, the model element (a) represented by a circle is the trace element, and the model element (c) represented by an octagon is It is a model element for downstream processes.

  In FIG. 14, when a model conversion execution instruction is input to the input unit 110 in the state of (a), the model elements stored in the model storage unit 130 are read by the model acquisition unit 141 as illustrated in (b). Then, it is copied to the copy model storage unit 150, and the model element “A ′” (1) and the trace element (0) of the downstream process are automatically generated based on the model element “A” (0) of the copy model. Then, the model update unit 136 compares the actual model with the copy model, and merges them. As shown in (c), the model element “A” (0) in the upstream process and the model element “A ′” in the downstream process are displayed. "(1)" is stored in the model storage unit 130 as an actual model. This case is a case through step S16 in the above-described processing example, and is a case where a model element for the downstream process is generated for the first time. Thereafter, editing may be performed so that either the model element “A” (0) in the upstream process or the model element “A ′” (1) in the downstream process is deleted.

  In FIG. 15, as shown in FIG. 15A, the model element “A” (0) of the upstream process and the model element “A ′” of the downstream process generated based on the model element “A” (0) of the upstream process. (1) and the trace element (1) generated simultaneously when the model element “A ′” of the downstream process is generated. When an execution instruction for model conversion is input to the input unit 110, the model elements stored in the model storage unit 130 are read by the model acquisition unit 141 and copied to the copy model storage unit 150, as shown in FIG. The model element “A ′” (2) in the downstream process is automatically generated again based on the model element “A” (0) in the copy model. Then, the model update unit 136 compares the actual model with the copy model. Here, as shown in (c), as a result of the comparison, there is no difference in the contents of model elements, and the model conversion process is completed without updating the actual model stored in the model storage unit 130. Indicated.

  In FIG. 16, as shown in FIG. 16A, the model element “A” (0) of the upstream process and the model element “A ′” of the downstream process generated based on the model element “A” (0) of the upstream process. (1) and the trace element (1) generated simultaneously when the model element “A ′” of the downstream process is generated. Then, as shown in (b), the model element “A ′” (1) of the downstream process is changed in accordance with the operation information input to the model editing unit 120, and the model element “A ′” (2) is changed. Is stored in the model storage unit 130. Here, as shown in (c), the conditions do not match the merge method by automatic merging, and as shown in (d), the merge is performed manually, and the model elements in the downstream process are updated. Here, if the condition matches the merge method by automatic merging, merging is automatically performed, and the model element of the downstream process is not updated.

  In FIG. 17, as shown in FIG. 17A, the model element “A” (0) of the upstream process and the model element “A ′” of the downstream process generated based on the model element “A” (0) of the upstream process. (1) and the trace element (1) generated simultaneously when the model element “A ′” of the downstream process is generated. Then, as shown in (b), the model element “A ′” (1) in the downstream process is deleted. Here, as shown in (c), the model element conversion unit 143 generates the model element “A ′” (2) of the copy model based on the model element “A” (0) of the upstream process. As shown in (d), the addition of the model element of the downstream process newly generated manually is reflected.

  In FIG. 18, as shown in FIG. 18A, the model element “A” (0) of the upstream process and the model element “A ′” of the downstream process generated based on the model element “A” (0) of the upstream process. (1) and a trace element (1) generated simultaneously when the model element “A ′” (1) of the downstream process is generated. As shown in (b), the model element “A” of the upstream process is deleted. Here, when the model conversion process is performed as shown in (c), the model element is not generated in the copy model because the model element in the upstream process of the actual model is deleted. Here, if the merge method “reflect upstream deletion” is ON, as shown in (d), the model element in the upstream process and the model element in the downstream process are both deleted in the model storage unit 130. Remembered. Also in this case, if necessary, the downstream process model “A ″” (2) can be manually generated as shown in (e).

  As described above, according to the present embodiment, after automatic model conversion by the model-oriented development support apparatus 100 is performed and a model element is generated, the generated model element is subjected to operation information from the user. Even if there is a manual change, model conversion can be performed according to the change. For example, when the model element of the upstream process is changed, when the model element of the downstream process is changed, when the model element of the upstream process and the downstream process is changed, etc. And the last update date / time of the trace element. In addition, when there is a change in the model elements of the upstream process and the downstream process, there is a case where there is an intention that the merging cannot be performed automatically, so that manual merging by the user can be performed.

  Further, according to the present embodiment, (1) the model element modified by the user is retained without being overwritten by the model conversion process, and (2) the model element intentionally deleted by the user is converted into the model (3) The model added intentionally by the user is not deleted by the model conversion process. (4) The model is not modified by the user. (5) List the conditions corresponding to (1) to (3) above, overwritten by processing, and let the user confirm whether there is a contradiction by leaving it to editing by the user (6) Regardless of (1) to (3) above, it is possible to perform model conversion processing such as forcibly performing model conversion processing and overwriting model elements. .

  Note that a program for realizing the function of the processing unit in the present invention is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read into a computer system and executed to perform model conversion processing. You may go. Here, the “computer system” includes an OS and hardware such as peripheral devices. The “computer system” includes a WWW system having a homepage providing environment (or display environment). The “computer-readable recording medium” refers to a storage device such as a flexible medium, a magneto-optical disk, a portable medium such as a ROM and a CD-ROM, and a hard disk incorporated in a computer system. Further, the “computer-readable recording medium” refers to a volatile memory (RAM) in a computer system that becomes a server or a client when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. In addition, those holding programs for a certain period of time are also included.

  The program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the “transmission medium” for transmitting the program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line. The program may be for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, and what is called a difference file (difference program) may be sufficient.

It is a figure which shows the structure of the model orientation development assistance apparatus by one Embodiment of this invention. It is a figure which shows the example of conceptual data of the model-oriented development by one Embodiment of this invention. It is a figure which shows the example of a conversion rule of model-oriented development by one Embodiment of this invention. It is a figure which shows the example of data memorize | stored in the model element memory | storage part by one Embodiment of this invention. It is a figure which shows the example of data memorize | stored in the trace element memory | storage part by one Embodiment of this invention. It is a figure which shows the concept of the tree structure of the model element by one Embodiment of this invention. It is a figure which shows the example of data of the model element of the detailed design process by one Embodiment of this invention. It is a figure which shows the example of data of the model element of the program design process by one Embodiment of this invention. It is a figure which shows the concept of the model conversion process by one Embodiment of this invention. It is a flowchart which shows the operation example outline | summary of the model orientation development assistance apparatus by one Embodiment of this invention. It is a flowchart which shows the operation example of the model orientation development assistance apparatus by one Embodiment of this invention. It is a flowchart which shows the operation example of the model orientation development assistance apparatus by one Embodiment of this invention. It is a flowchart which shows the operation example of the model orientation development assistance apparatus by one Embodiment of this invention. It is a figure which shows one type of merge processing by one Embodiment of this invention. It is a figure which shows one type of merge processing by one Embodiment of this invention. It is a figure which shows one type of merge processing by one Embodiment of this invention. It is a figure which shows one type of merge processing by one Embodiment of this invention. It is a figure which shows one type of merge processing by one Embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 100 Model oriented development support apparatus 110 Input part 120 Model edit part 130 Model memory | storage part 131 Model element memory | storage part 132 Trace element memory | storage part 140 Control part 141 Model acquisition part 142 Model duplication part 143 Model element conversion part 144 Model content comparison part 146 Update Date and time comparison unit 145 Model update unit 147 Merge method determination unit 150 Copy model storage unit 160 Merge method storage unit

Claims (6)

Design and development of the software system in which each model element that models each function constituting the software system to be developed is hierarchized into a plurality of processes from an upstream process represented by an abstract concept to a downstream process represented by a source code A model-oriented development support device that supports
For each model element included in the second process, which is a downstream process corresponding to the first process, and each model element included in the first process among the plurality of processes. A model storage unit in which an update date and time indicating the date and time when the model element is stored is stored in advance;
A copy model storage unit for storing a copy model in which each model element included in the first step is copied;
An input unit that receives an input of a model conversion request for generating each model element of the second step based on each model element of the first step;
When the model conversion request is input to the input unit, a model duplication unit that duplicates each model element of the first step and stores it in the copy model storage unit;
Based on a predetermined model conversion rule, the copy model storage unit generates each model element of the second step according to each model element of the first step stored in the copy model storage unit And identifying the model element of the second step generated based on the upstream model element identification information for identifying each model element of the first step and each model element of the first step A model element conversion unit that generates a trace element in which downstream model element identification information is associated with an update date and time indicating a date and time when the model element of the second step is generated;
A trace element storage unit that stores the trace elements generated by the model element conversion unit;
Contents of each model element of the second step generated in the model element conversion unit and stored in the copy model storage unit, and contents of each model element of the second step stored in the model storage unit And a model content comparison unit that determines whether or not the content is different,
When the model content comparison unit determines that the content is different, the update date and time of each model element of the first step stored in the model storage unit and the model element of the second step An update date and time comparison unit that compares the update date and time and the update date and time included in the trace element corresponding to the model element and determines whether or not the update date and time are different;
When the update date and time comparison unit determines that the update date and time are different, based on a predetermined procedure, the model elements stored in the copy model storage unit and the model storage unit stored in the model storage unit A model update unit that integrates model elements and stores them in the model storage unit;
A model-oriented development support apparatus characterized by comprising: When the update date and time comparison unit determines that the update date and time are different, the model element stored in the model element and the model element stored in the copy model storage unit are given priority. An integrated procedure storage unit in which an integration procedure indicating whether to integrate the model elements is stored;
The model update unit includes the model elements stored in the copy model storage unit and the model elements stored in the model storage unit based on the integration procedure stored in the integration procedure storage unit. The model-oriented development support apparatus according to claim 1, wherein the model storage unit is integrated and stored in the model storage unit. The input unit receives an input of change information for changing a content of the model element stored in the model storage unit;
The content of the model element stored in the model storage unit is changed in accordance with the change information input to the input unit, and the date and time of the change is associated as the update date and time corresponding to the model element A model editing unit to be stored in the model storage unit,
The model-oriented development support apparatus according to claim 1, further comprising: In the integrated procedure storage unit, each of the model elements stored in the model storage unit, the presence / absence of the trace element corresponding to the model element, or a condition determined based on the difference in the update date / time And the integration procedure is stored according to
The model update unit determines, for all of the model elements, whether or not the trace element corresponding to the model element exists or whether each of the update dates / times matches the condition, and all match Then, the model elements stored in the copy model storage unit based on the predetermined procedure are integrated with the model elements stored in the model storage unit, and there is a model element that does not match. The model-oriented development support apparatus according to claim 3, wherein the integration is performed according to the change information of the model element input to the input unit. Design and development of the software system in which each model element that models each function constituting the software system to be developed is hierarchized into a plurality of processes from an upstream process represented by an abstract concept to a downstream process represented by a source code The model elements included in the first process among the plurality of processes, the model elements included in the second process which is a downstream process corresponding to the first process, and the respective processes. For each model element, a model storage unit in which an update date and time indicating the date and time when the model element is stored is stored in advance, and a copy model in which each model element included in the first step is duplicated is stored. Between the copy model storage unit and the model elements included in the second step corresponding to the model elements included in the first step The A model-oriented development support method using a model-oriented development tool and a tracing element storage unit which trace elements are stored indicating,
An input unit receiving an input of a model conversion request for generating each model element of the second process based on each model element of the first process;
When the model duplication unit inputs the model conversion request to the input unit, the model duplication unit duplicates each model element of the first step and stores it in the copy model storage unit;
The model element conversion unit generates each model element of the second step according to each model element of the first step stored in the copy model storage unit based on a predetermined model conversion rule. The second model generated based on the upstream model element identification information that is stored in the copy model storage unit and identifies each model element of the first process, and each model element of the first process A step of generating a trace element in which downstream model element identification information for identifying the model element is associated with an update date and time indicating a date and time when the model element of the second step is generated and stored in the trace element storage unit When,
A model content comparison unit is generated in the model element conversion unit and stored in the copy model storage unit. The content of each model element in the second step and the second step stored in the model storage unit Comparing the content of each model element to determine whether the content is different;
When the update date and time comparison unit determines that the content is different by the model content comparison unit, the update date and time of each model element of the first step stored in the model storage unit and the second step Comparing the update date and time of each model element with the update date and time included in the trace element corresponding to the model element, and determining whether or not the update date and time are different;
When the model update unit determines that the update date / time is different by the update date / time comparison unit, based on a predetermined procedure, each model element stored in the copy model storage unit, and the model storage unit Integrating and storing the model elements stored in the model storage unit;
A model-oriented development support method characterized by comprising: Design and development of the software system in which each model element that models each function constituting the software system to be developed is hierarchized into a plurality of processes from an upstream process represented by an abstract concept to a downstream process represented by a source code The model elements included in the first process among the plurality of processes, the model elements included in the second process which is a downstream process corresponding to the first process, and the respective processes. For each model element, a model storage unit in which an update date and time indicating the date and time when the model element is stored is stored in advance, and a copy model in which each model element included in the first step is duplicated is stored. Between the copy model storage unit and the model elements included in the second step corresponding to the model elements included in the first step The computer model-oriented development tool and a tracing element storage unit which trace elements are stored indicating a
Receiving an input of a model conversion request for generating each model element of the second process based on each model element of the first process;
When the front SL model transformation request is input, the steps of replicating each model element of the first step is stored in the copy model storage unit,
Based on a predetermined model conversion rule, the copy model storage unit generates each model element of the second step according to each model element of the first step stored in the copy model storage unit And identifying the model element of the second step generated based on the upstream model element identification information for identifying each model element of the first step and each model element of the first step Generating a trace element in which downstream model element identification information is associated with an update date and time indicating a date and time when the model element of the second step is generated, and storing the trace element in the trace element storage unit;
Comparing the content of each model element before Symbol copy model storage unit on the stored second step, the content of each model element of the model stored the second memory in the unit step, said content Determining whether they are different, and
If the contents is determined that different, said the update date and time of each model element of the model storage said first stored in the unit step, and the update date and time of each model element of the second step, the model Comparing the update date and time included in the trace element corresponding to an element to determine whether the update date and time are different;
If update date is determined to differ, based on a predetermined procedure, and integrated with said copy model memory each model element stored in the unit, and the model elements stored in the model storage unit Storing in the model storage unit;
A model-oriented development support program that runs

Images