KR100283099B1 - Object-Oriented Modeling Tool and Its Logical and Graphical Information Processing Methods - Google Patents

Abstract

The present invention relates to an object-oriented modeling tool and a method for processing logical and graphical information thereof.

The present invention provides a model object processor for synchronously processing graphical elements input from a diagram editor and logical components contemplated therein while providing functions related to creation, deletion, and diagram generation and deletion of objects; A graphic component manager for managing graphic component objects expressed in diagram units by exchanging information with the model object processor; A logical component manager for managing logical component objects by exchanging information with each of the model object processor and the graphical component manager; It receives the information from the model object processor and displays various graphic element objects on the screen, and at the same time holds the information limited to the window, and includes a diagram window manager for providing a user-modified function. We present an object-oriented modeling tool that can secure the synchronization between managed objects and logical objects managed in the system, and its logical and graphical information processing methods.

Description

Object-Oriented Modeling Tool and Its Logical and Graphical Information Processing Methods

The present invention relates to an object-oriented modeling tool capable of securing synchronization between an object manipulated by a user and a logical object managed in the system, and a method for processing the logical information and the graphic information thereof.

The software system can be modeled in various forms according to the view of the system, and the model must be integrated into one during system development, so modeling and integrating the software system according to the perspective are indispensable technologies.

Unified Modeling Language (UML) is the standard of analytic design notation for object-oriented software development. It is an object modeling technique (defined by OMT, Rumbaugh), a case-oriented object. Conventional object-oriented software development methodologies, such as oriented design (defined by Jacobson) and object-oriented design (defined by Booch), lack integration methods between models that represent the system to be developed. Models that represent systems include functional models that model the system in terms of service to the user, interaction models that model the system in terms of operating with the user, and model in terms of the structure of the system to be developed. It can be roughly classified into a structural model. UML is preparing a way to integrate each model in terms of meaning and notation through metamodel. Therefore, in developing a tool that fully supports the meaning and notation of UML, mutual information sharing between models and creation and management of visual graphic information are essential functions for users.

In modeling a software system, the user's unit of work is a diagram. And since there are model elements in the diagram, graphic objects, that is, model elements, form a hierarchical relationship with the diagram. The problem here is that certain model elements that form a hierarchical relationship with a particular diagram can exist together in other diagrams. Or, certain model elements in one diagram can be transformed in another diagram.

As described above, the UML-supported modeling tool described in the related art is represented by the same layer without showing the hierarchical relationship between the diagram and the model elements. This is inconsistent with your diagram-based system modeling.

Accordingly, an object of the present invention is to provide an object-oriented modeling tool that can separate and manage the external objects displayed on the screen manipulated by the user and the logical objects that exist only in the system, and can be represented hierarchically to the user. To provide. Another object of the present invention is to secure the concurrency between the graphic object and the logical object information and the update of the attributes of the object when creating and deleting the object manipulated by the user through this object-oriented modeling tool. The present invention provides a method for processing logic information and graphic information of an object-oriented modeling tool.

The object-oriented modeling tool according to the present invention for achieving the above object is associated with the creation, deletion and diagram creation and deletion of objects while synchronously processing graphical components input from the diagram editor and internally managed logical components. A model object processor for providing a function; A graphic component manager for managing graphic component objects expressed in diagram units by exchanging information with the model object processor; A logical component manager for managing logical component objects by exchanging information with each of the model object processor and the graphical component manager; It comprises a diagram window manager for receiving information from the model object processor to display a number of graphic component objects on the screen, at the same time to hold information limited to the window, and to provide a user-modified function.

In addition, the logical information and graphic information processing method of the object-oriented modeling tool according to the present invention for achieving the above object, when a user inputs a graphic component object through a graphic editor, a new graphic component object at the bottom of the diagram Generating a first step; A second step of determining whether there is a logical element object matching the name given to the graphic element object from the first step; If the logical component object does not exist from the second step, the logical component object is created based on the current graphic component object, and the diagram on which the graphic component object is created is added to the parent property to base the graphic component object. A third step of outputting the object creation completion screen after designating as the graphic component object; And if the logical component object exists from the second step, adding the graphic component object as a clone-graphic component object of the logical component object, and outputting an object creation completion screen. It is done.

In addition, the logical information and graphical information processing method of another object-oriented modeling tool according to the present invention for achieving the above object is a base-graphic configuration that is the basis of the logical component object in response to the request to delete the graphical component object Determining whether it is an element object; In the case of the base-graphic component object from the first step, it is determined whether the clone-graphic component object exists. If the base-graphic component object is not, the graphic component object is deleted and the deletion completion screen is output. Performing a second step; If the clone-graphics component object exists from the second step, it is determined whether all the clone-graphics component objects are deleted. If the clone-graphics component object does not exist, the graphic component object is deleted after the deletion. A third step of outputting a completion screen; In the case of the delete command of all the clone-graphic component objects from the third step, after deleting all the clone-graphic component objects, a deletion completion screen is output; And a fourth step of deleting only the selected clone-graphic component object.

In addition, the present invention for achieving the above object comprises a first step of creating a new graphical component object at the bottom of the diagram when the user inputs the graphical component object through the graphical editor; A second step of determining whether there is a logical element object matching the name given to the graphic element object from the first step; If the logical component object does not exist from the second step, the logical component object is created based on the current graphic component object, and the diagram on which the graphic component object is created is added to the parent property to base the graphic component object. A third step of outputting the object creation completion screen after designating as a graphic component; If there is a logical component object from the second step, add a graphic component object as a clone-graphic component object of the logical component object, and then execute a program for executing the fourth step of outputting an object creation completion screen. And a recording medium that can be read by a computer.

In addition, the present invention for achieving the above object is a first step of determining whether, based on the request to delete the graphical component object is a base-graphic component object underlying the logical component object; In the case of the base-graphic component object from the first step, it is determined whether the clone-graphic component object exists. If the base-graphic component object is not, the graphic component object is deleted and the deletion completion screen is output. Performing a second step; If the clone-graphics component object exists from the second step, it is determined whether all the clone-graphics component objects are deleted. If the clone-graphics component object does not exist, the graphic component object is deleted after the deletion. A third step of outputting a completion screen; In the case of the delete command of all the clone-graphic component objects from the third step, after deleting all the clone-graphic component objects, a deletion completion screen is output; And a computer readable recording medium having recorded thereon a program for executing the fourth step of deleting only the selected clone-graphic component object.

1 is a logical component derivation diagram applied to the present invention.

2 is a diagrammatic representation of graphical components applied to the present invention.

3 is a correlation diagram of a logical component manager and a graphical component management period applied to the present invention.

4 is a block diagram of an object-oriented modeling tool according to the present invention.

5 is a flowchart of a graphic information input processing process according to the present invention;

6 is a flowchart of a graphic information deletion processing process according to the present invention;

<Description of Signs of Major Parts of Drawings>

1: Diagram Editor 2: Model Object Handler

3: diagram window manager 4: logical component manager

5: Graphic Component Manager

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

1 is a diagram illustrating a logical component derivation applied to the present invention, FIG. 2 is a diagram illustrating a derivation of a graphical element applied to the present invention, and FIG. 4 is a block diagram of an object-oriented modeling tool according to the present invention, FIG. 5 is a flowchart of a graphic information input processing process according to the present invention, and FIG. 6 is a flowchart of a graphic information deletion processing process according to the present invention. Indicates.

1. Logical Components

Logical Component (hereinafter referred to as LC) is a basic object that represents a UML object. It has only a very simple interface because it has only semantic parts unlike graphic elements (GCs) displayed on the screen. It has a separate property.

Each LC is defined as a class. When the characteristics of the LC are largely divided, there are independent LCs such as UML classes and actors, and LCs that can include other objects at the bottom, such as class diagrams or packages. Accordingly, the entire LC is derived from the TLC Element class, which is the base of LC objects that exist independently from the TLC Base type, which is the base base class, and the TLC Container class, which may include another object as shown in the diagram.

All LC classes actually used are derived from these two classes (TLC Element, TLC Container). The base base class, TLC Base, is used as the base type to refer to all LC objects. This specific LC class derivative is shown in FIG. 1.

2. Graphics component

The Graphic Component (hereinafter referred to as GC) is a part of the UML object that is actually displayed on the screen, and serves to express the contents of the LC. Multiple GCs may be connected to one LC, and each GC may have a separate property because separate GCs may be used.

Like the LC, each GC is defined as a class. There are two types of GC, rectangular GC and linear GC, depending on the operation method and basic form.

In general, rectangle objects may exist independently of other GCs. However, a linear object can exist only with a connected GC.

The basic type of GC is defined as TGC Base. This type is used for references to all GCs. The base class for rectangular objects is of type TGC Rect, derived from TGC Base. The base class for linear objects is of the TGC Line class type, derived from TGC Base. From this TGC Rect and TGC Line class types, all GC objects actually used are defined. This GC class derivation is shown in FIG.

3. Graphical Component Manager

Graphical Component Manager (hereinafter referred to as GC Manager) is a module that manages GCs expressed in units of diagrams and is generated in a 1: 1 correspondence to diagrams. Internally, the method of managing GC objects uses a tree structure consisting of a list structure and a list. Among the GC objects, there are GCs that work together because they are internal to the location. A tree structure is used to express this, and a list structure that manages all objects separately from the tree structure is used to search for GC objects quickly in relation to mouse movement. The order in which GCs are listed in the entire List structure varies according to the type or state of the object. A linear object is placed first in the List prior to all other objects. This is to allow linear objects to be selected first if they are to be selected by the mouse. The GC objects in the parent-child relationship have their own order, and the child GC objects are placed higher on the list than the parent GC objects.

4. Logical Component Manager

Logical Component Manager (hereinafter referred to as "LC Manager") is a module that manages all LC objects used in the project. The data structure for managing objects uses a tree. This is to properly express the hierarchical relationship between LCs. Positioning a node below a tree means that it is a child of that object.

In general, only LC objects exist in the LC Tree. However, in case of TLC Container such as class diagram or use case diagram, GC Manager is included one by one, and GC existing in diagram is included accordingly. For this reason, GC and GC Manager exist as a partial tree in the entire LC tree. The relationship between such LC Manager and GC Manager is shown in FIG.

5. Diagram Window Manager

The diagram is represented by one LC object containing logical information. However, it can display multiple GC objects on the screen, while at the same time providing user-specific modifications while retaining information specific to windows, such as diagram colors or text fonts used in diagrams, scaling ratios of diagrams, etc. It is represented internally as a special component named Diagram Window Manager (hereinafter referred to as DW Manager), and actually provides a function that a user can visually check.

Since most of the user's input is a window, processing of input devices such as a mouse and a keyboard is the main function of the user.

This DW Manager is not created when the project is initially loaded from a file. When the user selects a specific diagram and commands 'Open' on the screen, the DW Manager is created and displayed on the screen based on the information in the LC Diagram. Table 1 shows the types of diagrams.

Diagram Type Equivalent diagram window class Usecase Diagram UML Diagram Window Class Diagram UML Class Diagram Window Sequence Diagram UML Sequence Diagram Window Collaboration Diagram UML Collaboration Diagram Window State Diagram UML State Diagram Window Component Diagram UML Diagram Window Deployment Diagram UML Diagram Window

Duplicate diagram window classes for each diagram type means that the diagrams do not need to be separated into separate classes because they do not have special behavior.

Each diagram window manager is designed to respond appropriately to events as shown in Table 2 below according to a user's input.

Event handler meaning Add GC Object New GC objects have been added to the diagram. Delete GC Object The GC object is about to be deleted. Set place object The location of the GC object has changed. Drag Object The GC object is being dragged by the mouse. Link Object The GC object is trying to connect to two other GC objects. Update Object The contents of the GC object have changed. Set Parent GC The parent GC object of the GC object has changed (containment relationship).

Depending on the type of these events, DW Manager can perform different actions to support special actions for each diagram.

6. Model Object Handler

The GC Manager and LC Manager manage GC and LC separately. In addition to this, it is necessary to ensure the linkage between LC and GC to prevent the occurrence of GC not connected to LC. It is a model object processor (2: Diagram-Component Interface; called DC Interface). The DC interface is used to synchronously process the LC and GCs involved in various operations by user input. DC Interface provides a wide variety of functions for creating and deleting objects and creating and deleting diagrams.

4 is a block diagram of the model object processor system described above.

Next, a method of integrating graphic components and logical components using a model object processor will be described.

First, referring to FIG. 5, a process of generating GC and LC objects will be described. When a user inputs a graphic object through the graphic editor 11, a new GC object is generated 12 below the current diagram. Find the LC object that matches the name given to the GC (13). If there is no LC object satisfying the condition, the LC object is created based on the current GC object (14). The LC object adds the diagram from which the GC object was created to its parent attribute and designates the GC object as base-GC (15 and 16). If there is an LC object that satisfies the condition and you want to treat the GC object just created as a clone, add the GC object as clone-GC of the LC object (13 and 16). In this case, the parent diagrams of the LC and clone-GC objects are different. In operation 17, the object creation completion screen is output.

Referring to FIG. 6, the deletion processing procedure of the GC and LC objects is described. When a request for deleting the GC object is received (21), it is checked whether this is a base-GC object that is the basis of the LC object (22). If the GC object is the basis of the LC object, the user is asked if he wants to delete all other clones, clone-GC as well (23). The LC object and all GC objects are deleted or not at the discretion of the user (24, 25 and 26). On the other hand, if it is not the base-GC object underlying the LC object, only the selected clone-GC object is deleted (27). This process is performed to output a deletion completion screen (28).

Types of object retrieval by the model object handler include LC object retrieval by object name, LC object retrieval by object type (Class, Actor, Usecase etc.), name and type integration LC object retrieval, and all descendant objects. LC search (primary child only), LC search for all descendant objects (including all descendant objects), search for clone-GCs associated with a specific LC, LC search for diagrams that belong to a particular GC, Base-GC search by LC, base-GC search by clone-GC, search for all LC objects that have a link by a specific LC and a linear object, search all linear LC objects that are linked to a specific LC in the starting direction, Search for all linear LC objects connected in an end direction.

The present invention described above is capable of various substitutions, modifications, and changes without departing from the spirit of the present invention for those skilled in the art to which the present invention pertains. It is not limited.

As described above, the present invention can be applied to the CASE tool to reduce the logical errors in the modeling work through the immediate confirmation of the diagram and the relationship between the components to the CASE tool user. You can configure a more friendly user interface.

In addition, the present invention provides a logical object that uniquely embraces the meaning of UML for drawing information based on the semantics and notation of the unified modeling language UML among object-oriented modeling methods, and can be manipulated by a user. Simultaneously manage external objects that display the characteristics of logical objects.

Claims (5)

A model object processor for providing functions related to creation, deletion, diagram generation, and deletion of an object while synchronously processing a graphic component input from a diagram editor and a logical component managed internally; A graphic component manager for managing graphic component objects expressed in diagram units by exchanging information with the model object processor; A logical component manager for managing logical component objects by exchanging information with each of the model object processor and the graphical component manager; Receiving information from the model object processor to display a number of graphical component objects on the screen, at the same time to hold information limited to the window, and comprises a diagram window manager for providing a user-modified function Modeling tool. A first step of creating a new graphical component object at the bottom of the diagram when the user enters the graphical component object via the graphical editor; A second step of determining whether there is a logical element object matching the name given to the graphic element object from the first step; If the logical component object does not exist from the second step, the logical component object is created based on the current graphic component object, and the diagram on which the graphic component object is created is added to the parent property to base the graphic component object. A third step of outputting the object creation completion screen after designating as a graphic component; And if the logical component object exists from the second step, adding the graphic component object as a clone-graphic component object of the logical component object, and outputting an object creation completion screen. Logical and graphical information processing method of object-oriented modeling tools. Determining, according to the deletion request of the graphic component object, whether it is a base-graphic component object which is the basis of the logical component object; In the case of the base-graphic component object from the first step, it is determined whether the clone-graphic component object exists. If the base-graphic component object is not, the graphic component object is deleted and the deletion completion screen is output. Performing a second step; If the clone-graphics component object exists from the second step, it is determined whether all the clone-graphics component objects are deleted. If the clone-graphics component object does not exist, the graphic component object is deleted after the deletion. A third step of outputting a completion screen; In the case of the delete command of all the clone-graphic component objects from the third step, after deleting all the clone-graphic component objects, a deletion completion screen is output; And a fourth step of deleting only the selected clone-graphic component object. A first step of creating a new graphical component object at the bottom of the diagram when the user enters the graphical component object via the graphical editor; A second step of determining whether there is a logical element object matching the name given to the graphic element object from the first step; If the logical component object does not exist from the second step, the logical component object is created based on the current graphic component object, and the diagram on which the graphic component object is created is added to the parent property to base the graphic component object. A third step of outputting the object creation completion screen after designating as a graphic component; If there is a logical component object from the second step, add a graphic component object as a clone-graphic component object of the logical component object, and then execute a program for executing the fourth step of outputting an object creation completion screen. Recordable computer-readable recording media. Determining, according to the deletion request of the graphic component object, whether it is a base-graphic component object which is the basis of the logical component object; In the case of the base-graphic component object from the first step, it is determined whether the clone-graphic component object exists. If the base-graphic component object is not, the graphic component object is deleted and the deletion completion screen is output. Performing a second step; If the clone-graphics component object exists from the second step, it is determined whether all the clone-graphics component objects are deleted. If the clone-graphics component object does not exist, the graphic component object is deleted after the deletion. A third step of outputting a completion screen; In the case of the delete command of all the clone-graphic component objects from the third step, after deleting all the clone-graphic component objects, a deletion completion screen is output; A computer-readable recording medium having recorded thereon a program for executing the fourth step of deleting only selected clone-graphic component objects.