KR100456623B1 - Apparatus and method to support simultaneous round-trip engineering for maintaining consistency between source code and corresponding design model - Google Patents

Abstract

The present invention relates to an apparatus and method for supporting simultaneous circular engineering by maintaining a consistency between a design model and a source code, while providing a user with an environment in which a UML model can be edited. UML model builder for providing the change message information is edited when the software design model information is edited by the; A UML model manager for packaging change message information provided from the UML model builder and providing the packaged message information through a design model gateway; After receiving the packaged change message information from the UML model manager, it manages the grammar tree to maintain program source code information up to the comment information by linking the source code parser. A source code manager for updating the structure; Located in the UML model manager and source code management period, while providing the environment for editing the source code, if the source code is changed by the user, the changed source is determined while determining the synchronization point to reflect the change of the source code. It has a source code editor that provides code to the source code manager. Therefore, it provides a message exchange procedure between the software design model and the source code model, and also suggests how to use the source code manager to support the Undo / Redo function. It is organically connected, so that the consistency between design and corresponding code in software development is automatically maintained, and software design and code reuse and software maintenance can be easily performed.

Description

Apparatus and method for supporting concurrent cyclic engineering by maintaining design model and source code consistency {APPARATUS AND METHOD TO SUPPORT

The present invention relates to an apparatus and a method for supporting Simultaneous Round-trip Engineering (SRE) by maintaining a consistency between a design model and source code, and in particular, a design generated in the process of designing and implementing object-oriented software. The present invention relates to an apparatus and a method for consistently managing a model and source code.

In general, SRE is a technology for designing and implementing object-oriented software. After generating source code from a model to be designed, the designer can change the generated source code or design model. (Or the implementor) is a technique that directly changes the design model.

That is, when developing object-oriented software, there is a high possibility of inconsistency between the design model and the source code, and there is a problem that there is a considerable difficulty in maintaining the design model and the source code when a substantially inconsistent case occurs.

As such, known techniques for designing and implementing object-oriented software include "automatic generation of program code using patterns and components" registered at 10-2000-0055378 and "URCA" published in OOPSLA in 2000. Approach to Scenario-based Round-trip Engineering. "

Referring to the prior art disclosed in detail as described above, the program code automatic generation method using the pattern and the components registered as 10-2000-0055378 is provided in advance by providing a pattern of the program to be generated and a component source connected thereto, It is a technology that connects selected patterns and components, loads database information already established, designs a database, and automatically generates program sources based on the selected patterns and databases.

Next, the URCA Approach to Scenario-based Round-trip Engineering technology, published in OOPSLA in 2000, proposed a scenario-based cyclic engineering method to minimize the overhead of existing static cyclic engineering techniques. It is a use case-centered model reconstruction method using formal concept analysis to remove inconsistencies of behavioral modeling elements in the cyclic engineering process to maintain reverse engineering between model and code.

In other words, the formal concept analysis method is used to obtain the behavioral elements in the process of creating the initial model through reverse engineering from the code, and the use case-oriented model restoration work is performed based on the script obtained from the analysis. In this work, dynamic elements are grouped around a use case in a layer, and analyzed system functions are analyzed in a hierarchical structure to obtain behavioral elements and use them in circular engineering.

In other words, the URCA method proposed in this paper is a method of grouping and hierarchizing functions of analyzed systems with a focus on formal conceptual analysis and classifying them into categories of common behavior. By linking functions and each use case and using them in the cyclic engineering process, the behavior model is circulated through the analysis of the use case-oriented system as well as the static information analysis used in the existing cyclic engineering. Technology to support engineering.

As described above, when looking at the technology disclosed in the prior patent, the existing patent (No. 10-2000-0055378) associated with the present invention may propose a source code generation technology related to forward engineering, which is a function of simultaneous circular engineering of patterns and components. However, it does not include the automatic change of the design model according to the actual generated code change, and the most relevant paper (the paper published in OOPSLA, 2000) includes static models and dynamics from source code. A technique for supporting cyclic engineering based on dynamic model by extracting model information, but a technique regarding message format or message exchange procedure between design model and source code model for supporting cyclic engineering defined in the present invention The problem is that there is still no progress in that it is not included.

Accordingly, the present invention has been made to solve the above-mentioned problems, the object of which is to reuse and maintain the software by consistently managing and maintaining the design model and source code generated in the process of designing and implementing the object-oriented software The present invention provides an apparatus and a method for easily performing SRE.

In the present invention for achieving the above object to maintain the consistency of the design model and the source code to support the simultaneous circular engineering (SRE) device for an environment that can edit UML (Unified Modeling Language (UML)) model to the user During providing, a UML model builder for providing the change message information to be edited when the software design model information is edited by the user; A UML model manager for packaging change message information provided from the UML model builder and providing the packaged message information through a design model gateway; After receiving the packaged change message information from the UML model manager, it manages the grammar tree to maintain program source code information up to the comment information by linking the source code parser. A source code manager for updating the structure; Located in the UML model manager and source code management period, while providing the environment for editing the source code, if the source code is changed by the user, the changed source is determined while determining the synchronization point to reflect the change of the source code. And a source code editor for providing the code to the source code manager.

In the present invention for achieving the above object, a method for supporting simultaneous circular engineering (SRE) by maintaining the consistency of the design model and the source code is a case where the software design model is changed, and the UML model builder can edit the UML model. Providing the UML model manager with changed message information when the software design model is changed by the user while providing the user with an environment that can be used; The UML model manager provided with the changed message information by the UML model builder packages the changed message information and provides the packaged message information to the source code manager through the design model gateway; The packaged change message information is received from the UML model manager. The provided source code manager includes a step of managing a grammar tree so that the source code parser can be linked with the source code parser to maintain program source code information as well as annotation information.

When the source code is changed, if the source code is changed by the user, after determining the synchronization time to reflect the change of the source code in the source code editor, providing the changed source code to the source code manager; The source code manager receiving the changed source code from the source code editor includes packaging the source code in the form of message information, and providing the packaged message information to the UML model manager through the source code model gateway.

1 is a block diagram of an apparatus for supporting simultaneous cyclic engineering by maintaining consistency of a design model and source code according to the present invention;

2 is a detailed description of a method for supporting simultaneous cyclic engineering by maintaining consistency between a design model and source code according to the present invention.

3 is a diagram for managing the overall design model and source code model for the object-oriented software according to the present invention in a tree form, respectively.

<Description of the symbols for the main parts of the drawings>

10: UML Model Builder 20: UML Model Manager

30: design model gateway 40: source code manager

50: source code model gateway 60: source code parser

70: source code editor

S1: user

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram of an apparatus for supporting simultaneous cyclic engineering by maintaining a consistency between a design model and a source code according to the present invention. The UML (Unified Modeling Language: UML) model builder 10 and a UML model manager 20, a design model gateway 30, a source code manager 40, a source code model gateway 50, a source code parser 60, and a source code editor 70.

The UML model builder 10 continuously provides the user S1 with an environment in which the UML model can be edited, and the software is edited when the software design model is edited, ie added, deleted, or changed from the user S1. The UML model manager 20 provides change message information about the design model.

The UML model manager 20 packages the change message information provided from the UML model builder 10 and provides the change message information packaged to the source code manager 40 through the design model gateway 30. Here, the design model gateway 30 is located between the UML model manager 20 and the source code manager 40 to serve as a passage for transmitting a model change message.

At this time, the UML model manager 20 is a problem that inconsistency occurs between the design model and the physical source code model when the change occurs by means other than the change by the tool included in the source code manager 40 In order to solve the call to the source code manager 40 to provide a forced synchronization function to input the location of the source code.

The source code manager 40 receives the packaged change message information from the UML model manager 20, and then links the source code parser 60 with the grammar tree to maintain program source code information up to the annotation information. Manage and update the grammar tree structure including comments when changing the code model.

In addition, the source code manager 40 performs all management functions for the source code provided from the source code editor 70, receives the source code information changed by the source code editor 70, and packages the packaged information. It provides to the UML model manager 20 through the source code model gateway 50. Here, the source code model gateway 50 is located between the source code manager 40 and the UML model manager 20 and serves as a path for transmitting a model change message.

The source code editor 70 is located between the UML model manager 20 and the source code manager 40. When the source code is changed by the user S1 while providing an environment for editing the source code, The changed source code is provided to the source code manager 40 while the synchronization point for reflecting the change of the source code is determined. Here, the synchronization point of time regards the point of time when the user S1 starts editing using the UML model builder 10 and forcibly stores the source code as the synchronization point.

Referring to the flow chart of Figures 2a to 2b, based on the above-described configuration, as a method for supporting simultaneous cyclic engineering by maintaining the consistency of the design model and the source code according to the present invention, the software design by the user (S1) For each case where the model changes and the source code changes, explain in more detail how the changes are reflected in the other model.

First, as a case where the software design model is changed, referring to FIG. 2A, the UML model builder 10 basically provides the user S1 with an environment in which the UML model can be edited. If the software design model is changed by the method, the changed message information is provided to the UML model manager 20 (step 201).

Here, the message information type includes a message number representing the type of the message in the message structure because various types of change information are possible, and the elements included in the message information include the message sender information, the message number representing the type of change, The position of the model to be changed, the details of the model to be changed, and the information before / after the change of the model to be changed are listed in order (step 202).

Of these, the message sender information is set by the UML model manager 20 or the source code manager 40. The message sender information indicates that the message is infinitely repeated between the source code manager 40 and the UML model manager 20. Information needed to prevent. That is, when the source code model changes, the software design model always changes the same. Also, when the software design model changes, when the source code model changes constantly, the message sender information and the message are exchanged as infinitely many message information are exchanged. By checking the status of the message information by using the number, it is possible to eliminate the message exchanged indefinitely.

In particular, if the change in the UML model builder 10 is related to deletion, the deletion-related information should be extracted in advance for undo / repeat so that the UML model manager 20 can manage separately ( Step 203).

That is, in this deletion process, when the unit to be deleted immediately before deletion is limited to one file, the UML model manager 20 transmits the corresponding source code information through the design model gateway 30 to the source code manager 40. (Step 204), on the other hand, when the unit to be deleted is not limited to one file, the file or package is kept in a separate location or compressed and temporarily stored in a database (not shown). (Step 205).

After the deletion is completed by the UML model manager 20, when the deletion cancellation (Undo, in this case 'addition' message) occurs, when sending the necessary information in the message to the source code manager 40, Since the undelete is eventually an additional message, the information previously stored in the above-described database is provided to the source code manager 40 in the previous information of the change message which should be empty (step 206).

The source code manager 40 checks the information included in the information before the change provided from the UML model manager 20 and cancels the information using the information included in the message rather than newly added information (Undo, in this case, 'add'). Mean message transmission) to restore the deleted portion (step 207).

At this time, the cancellation / repeat (Undo / Redo) for the deletion in the source code editor 70 passes through the source code manager 40 after the cancellation (Undo) of the source code editor 70 itself, Because it is automatically reflected, it is executed without any separate work unlike deletion from software design model.

The UML model manager 20 packages the changed message information provided from the UML model builder 10 into the above-described message information form, and provides the packaged message information to the source code manager 40 through the design model gateway 30. (Step 208).

The source code manager 40 receives the packaged change message information from the UML model manager 20, and then links the source code parser 60 with the grammar tree to maintain program source code information up to the annotation information. It manages, and updates the grammar tree structure including the comment when changing the code model (step 209).

At this time, when the change is generated by means other than the change by the tool included in the source code manager 40, UML model manager 20 is a problem that inconsistency between the design model and the physical source code model In order to solve the problem, the source code manager 40 is called to provide a forced synchronization function of inputting the location of the corresponding source code so as to match the design model with the physical source code model (step 210).

Next, when the source code is changed, referring to FIG. 2B, when the source code is changed by the user S1, the source code editor 70 must determine a synchronization time point to reflect the change of the source code. (Step 301).

Thus, the source code editor 70 regards the point of time when the user S1 starts editing using the UML model builder 10 and forcibly saves the source code as a synchronization point, and thus changes the source to the source code manager 40. Provide the code (step 302).

The source code manager 40 receives the changed source code from the source code editor 70 and packages the source code manager 70 in the form of the message information described above, and packages the packaged message information to the UML model manager 20 through the source code model gateway 50. Provide (step 303).

On the other hand, Figure 3 is a diagram for managing the overall design model and source code model of the object-oriented software according to the present invention in a tree form, respectively, the entire design model and source code model for the object-oriented software being implemented in a tree form Managed separately, each tree node is a model unit and targets an object-oriented model.

Therefore, leaf information expresses object information about the structure of the object, and non-leaf node expresses model information of the model. The model tree is managed separately from the design model and the source code model, but the structure and the information exchanged with each other must be included on both sides.

As described above, the present invention provides consistent management and maintenance between the design model and the source code model generated in the process of designing and implementing the object-oriented software, thereby facilitating reuse and maintenance of the software. It provides a message exchange procedure between the software design model and the source code model, and suggests how to use the source code manager to support the Undo / Redo function. The process is organically linked, which automatically maintains the consistency between the design and the code in software development, and facilitates software design, code reuse, and software maintenance.

Claims (18)

In order to maintain the consistency of the design model and the source code to support concurrent circular engineering, A UML model builder which provides the changed message information when the software design model information is edited by the user while providing a user with an environment capable of editing a UML model; A UML model manager for packaging change message information provided from the UML model builder and providing the packaged message information through a design model gateway; After receiving the packaged change message information from the UML model manager, it manages a grammar tree to maintain program source code information up to annotation information by linking a source code parser. A source code manager for updating the tree structure; Located in the UML model manager and the source code management period, while providing an environment for editing the source code, when the source code is changed by the user, while determining the synchronization time to reflect the change of the source code And a source code editor for providing the modified source code to the source code manager, thereby maintaining the consistency of the design model and the source code. The method of claim 1, The design model gateway and the source code model gateway are located in the UML model manager and the source code management period, and serve as a passage for transmitting a model change message. Device to support engineering. The method of claim 1, The UML model manager is a source corresponding to the source code manager so that when a change is made by a means other than a tool included in the source code manager, the design model and the physical source code model can be matched. Apparatus for supporting concurrent cyclic engineering by maintaining coherence with the design model and source code, characterized by calling to provide a forced synchronization function with the location of the code as an input. The method of claim 1, The source code manager performs all management functions for the source code provided from the source code editor, receives and packages the source code information changed by the source code editor, and packages the packaged information through a source code model gateway. Device for supporting concurrent cyclic engineering by maintaining consistency of design model and source code, which is provided to UML model manager. The method of claim 1, The synchronization point of time is to maintain the consistency of the design model and the source code, characterized in that the user starts to edit using the UML model builder and forcibly storing the source code as the synchronization point to achieve simultaneous cyclic engineering Device to support. It maintains the consistency of the design model and the source code in a concurrent cyclic engineering system with a UML model builder, a UML model manager, a source code manager, a source code editor, and a source code parser. In the case where the source code is changed, the changes are reflected in the relative model, respectively. When the software design model is changed and the software design model is changed by the user while providing the environment in which the UML model builder can edit the UML model, the changed message information is sent to the UML model. Providing to the manager; Receiving the changed message information by the UML model builder, packaging the changed message information and providing the packaged message information to the source code manager through a design model gateway; The source code manager receiving the packaged change message information from the UML model manager includes managing the grammar tree to maintain program source code information up to annotation information by interworking the source code parser. A method for supporting concurrent cyclic engineering by maintaining consistency between design model and source code. The method of claim 6, When the source code is changed and the source code is changed by the user, the source code editor determines the synchronization point to reflect the change of the source code, and then provides the changed source code to the source code manager. step; The source code manager receiving the modified source code from the source code editor further comprises packaging the source code in the form of message information and providing the packaged message information to the UML model manager through a source code model gateway. A method for supporting concurrent cyclic engineering by maintaining the consistency of the design model and the source code, characterized in that. The method of claim 6, As the source code manager must maintain the program source code information being implemented, including the annotation information, a design model for managing a grammar tree using a source code parser that considers the comments about the corresponding source code. A way to support concurrent circular engineering by keeping source code consistent. The method of claim 7, wherein The synchronization point of time is that the user starts editing using the UML model builder and forcibly saves the source code as a synchronization point. Way. The method of claim 6, Since the message information type is capable of various kinds of change information, the message structure includes a message number representing the type of the message. Way. The method of claim 10, The element included in the message information is designed to list the message sender information, the message number representing the type of change, the location of the model to be changed, the details of the model to be changed, and the information before / after the change of the model in order. A way to support concurrent circular engineering by keeping models and source code consistent. The method of claim 11, The message sender information is information required to prevent the message from repeating infinitely between the source code manager and the UML model manager. The method of claim 6, If the change in the UML model builder is related to the deletion, the design model and source, characterized in that the UML model manager can be separately managed by extracting the deletion-related information in advance for undo / repeat (Undo / Redo) A method for supporting concurrent circular engineering by keeping code consistent. The method of claim 13, In the deleting process, when the unit to be deleted immediately before the deletion is limited to one file, the UML model manager of the design model and source code, characterized in that to obtain the corresponding source code information to the source code manager in advance A way to support co-rotational engineering by maintaining consistency. The method of claim 13, In the deleting process, when the unit to be deleted is not limited to one file, the UML model manager maintains or compresses a corresponding file or package in a separate location and temporarily stores the file or package. A method for supporting concurrent circular engineering by keeping code consistent. The method of claim 13, After the deletion is completed by the UML model manager, when the deletion cancellation occurs, when the necessary information is included in the message and provided to the source code manager, the information previously stored in the message before the change of the message to be empty should be temporarily included. Provided to the source code manager, wherein the source code manager checks the information included in the information before the change, and restores the deleted part by canceling using the information included in the message, not the newly added information. A method for supporting concurrent cyclic engineering by maintaining consistency between the design model and the source code. The method of claim 6, When a change is generated by a means other than a tool included in the source code manager, the UML model manager corresponds to the source code manager so that the design model and the physical source code model match. To support simultaneous cyclic engineering by maintaining the consistency of the design model and the source code, by calling to provide a forced synchronization function to input the position of the to match the design model and the physical source code model Way. The method of claim 6, The entire design model and source code model for the object-oriented software are managed in tree form, and the tree node is a unit of model, and as the object-oriented model is targeted, the leaf node has object information about the structure of the object. The non-leaf node expresses the package information of the model. The method for supporting concurrent cyclic engineering by maintaining the consistency of the design model and the source code.