KR100327904B1 - System and Method for Component Customization - Google Patents

Abstract

The present invention relates to a component-based software development support system, and more particularly, to a component browser module showing a user a component or package to be edited while browsing all packages in an arbitrary component repository, and a component currently being edited through the component browser module. In addition to the designer module, which allows you to assemble components when you create a new application, the Project Explorer displays multiple information about the module, the components selected in the designer module or the Project Explorer module, and allows you to edit dual-option attributes. Property Editor module, and a custom module that contains the necessary functions for customization with the main window, and stores customized components and creates new project applications. Provides a component redefinition tool system and a method of operating the component redefinition, and allows the user to redefine the property in the desired form by searching for the component from the component package built in the component repository. It is reflected in the properties of client components to maintain connectivity with each other, solves the dependency problem between components when assembling and deleting components, and can effectively support the application of business components to the application area.

Description

System and Method for Component Customization

The present invention relates to a component-based software development support tool and its operation method, and more particularly, to a support tool and method for selecting and redefining a built component according to a user's needs and assembling and deleting a component in a component package.

As the demand for software development is increasing, the complexity and size of development software is increasing, and the time-to-market is shortening, the component-based software development method is an optimal alternative to cope with this. Is developing rapidly.

Microsoft's 'VBX', 'ActiveX', and 'SUN''s 'JavaBean', which are widely used, are mainly used as simple components included in the GUI, and most of them have no consideration of connection or dependencies between components. to be.

Because business components in the server sector contain business logic, it was not often possible to use them as they were designed to meet user needs.

Therefore, the component redefinition process has to go through, resulting in a dependency problem between client and server components. Furthermore, existing component tools such as 'Visual Basic' or 'Visual Cafe' simply include components in the application system. Since it provides only functions, it cannot deal with such dependency problem caused by coupling between components.

An object of the present invention for solving the above problems is to handle the dependency between the client component and the server component when redefining the component in order to solve the dependency problem caused by the component combination generated in the prior art, the assembly of the component And a component combining tool and method for managing an interface for maintaining dependencies between components upon deletion.

1 is a block diagram of a component redefinition tool system according to the present invention

2 is a component property display screen in the component redefinition tool system according to the present invention;

3 is an example of component property display in a component redefinition tool system according to the present invention;

4 is a component property redefinition method when set to Auto in the component redefinition tool system according to the present invention;

5 is a component property redefinition method when set to Manual in the component redefinition tool system according to the present invention;

6 is a method for deleting a component in a component redefinition tool system according to the present invention.

7 is a dependency checking method when deleting a component in the component redefinition tool system according to the present invention.

8 is a candidate component selection method for maintaining dependency upon component deletion in a component redefinition tool system according to the present invention.

9 is an example of restoring a dependency after deleting a component in the component redefinition tool system according to the present invention.

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

110: customizer 120: component browser

130: Property Editor 140: Designer

210: Properties screen 220: Selection Properties screen

230: provided interface screen 240: reference properties screen

250: Request interface screen 310: User selection screen

320: User Properties Screen 410: Property Change Screen

420: property change result 510: change property selection

520: Property change method 610: Component removal screen

620: Example of a group that is a permission setting unit

710: How to check dependencies 720: Check client component deletion

730: Check for component replacement 810: Check for replacement component of dependent component

820: Define new dependencies

A feature of the present invention for achieving the above object is a component-based software development support system, comprising: a component browser module for showing a user a component or package to be edited while browsing all packages in any component repository; A designer module for visually representing a component currently being edited through the component browser module; A project explorer module that enables component assembly when creating a new application; A property editor module for displaying various information (Provided Interface, Required Interface, Attribute, Option Attribute, Reference Attribute) of the selected component in the designer module or the project explorer module and allowing the dual option attribute to be edited; And a main window is provided with a function required for customization, and includes a customizer module for storing customized components and creating a new project application.

Another feature of the present invention for achieving the above object is a component browser module that shows the user a component or package that you want to edit while browsing all packages in any component repository, and visually displays the component currently being edited through the component browser module. The designer module, the project explorer module that allows the assembly of components when creating a new application, and the various information of the components selected from the designer module or the project explorer module (Provided Interface, Required Interface, Attribute, Option Attribute, Reference Attribute), a property editor module that allows you to edit dual-option attributes, and the main window contains the necessary features to store customized components and save new In the component redefinition tool system, which has a customizer module that creates a custom application, a component imported into the designer module is selected in various tabs of the property editor module to check various properties of a 'user' component. A first process of doing; A second step of displaying a property of a 'user' component by selecting 'customization> test component' of the customizer module; After closing the execution of the user component, select 'Auto' as the property of 'Propagate To GUI' in the property editor module and enable the attribute (for example, date of birth, home address, home phone number, hobby, etc.) of the optional attribute. C) generating false as false; And a fourth process of displaying execution of the customized user component by selecting 'Customization> Test Component' of the customizer module.

An additional feature of the present invention for achieving the above object is that the property 'Propagate To GUI' of the property editor module is set to 'Auto'. When the property of the server component is edited, the user interface, which is a client component, is automatically set. It's about getting edited.

An additional feature of the present invention for achieving the above object is that when editing the option attribute in the property editor module, the property of the 'Propagate To GUI' is set to 'Manual' and the client component ' When editing the UI 'directly, the properties in the property editor module are properties of the' TextBox 'that enters the selected name, eliminating the part where false setting of the enable property is not used when editing the server component. To adjust the layout.

An additional feature of the present invention for achieving the above object is to open the Project Explorer module by selecting 'Project> New Project' of the customizer module and then opening the organizational package in the component browser module. A first step of preparing to create a new application by dragging and dropping; The way to set the permissions of the organization package is basically to grant authority in the 'group' unit. A company that will use the new application does not need to separate the 'organization' and the 'group'. The method may further include a fifth process of removing unnecessary components in the component package when creating a new application of the component having a second step of deleting the component.

An additional feature of the present invention for achieving the above object is the 'checkAthority' interface and the 'permission' component of the 'group' component that would have selected 'Show Dependency' from the pop-up menu in the Project Explorer module. A first step of indicating that 'checkAuthority' has a dependent relationship; A second step of deleting a 'group' component through a pop-up menu by selecting a 'group' component in the project explorer module when the user has confirmed the dependency relationship through the first step; And a third step of performing component replacement by detecting a dependency relationship between components to be deleted in the project of the customizer module. When a subject to set authority is deleted by deleting a 'group' component, a new dependency definition is defined. It involves six more steps.

The above objects and various advantages of the present invention will become more apparent from the preferred embodiments of the invention described below with reference to the accompanying drawings by those skilled in the art.

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

1 is a basic screen configuration diagram of a component redefinition tool, and as shown in FIG. 1, the component redefinition tool is displayed in four large windows: a customizer 110 and a component browser. 120), Property Editor 130, and Designer 140;

The customizer 110 has all menus required for customization as a main window, and can store customized components and generate new projects.

In addition, the component browser 120 browses all the packages of the Component Repository and browses the component or package to be edited while the designer or the project explorer (Project). To the user by dragging or dropping to Explorer.

In addition, the property editor 130 shows various information (Provided Interface, Required Interface, Attribute, Option Attribute, Reference Attribute) of the component selected in the designer or the Project Explorer. Allows you to edit the (Option Attribute).

Lastly, the designer 140 is a window for visually expressing a component currently being edited. In addition, Project Explorer allows you to assemble Component f when creating a new application.

Referring to the basic screen diagram of the component redefinition tool configured as described above, the operation is briefly described. First, a user is selected from the server components of the organization package in the component browser 120 on the initial screen. Drag and drop onto the designer window.

Then, it becomes as shown in FIG. 1 and is ready to customize the server component.

Attached FIG. 2 shows that the properties imported to the designer 140 in FIG. 1 are clicked on various tabs of the property editor 130 to check various properties of the 'user' component. Attributes include basic attribute 210, optional attribute 220, provision interface 230, reference attribute 240, request interface 250, and the like.

3 is a screen showing how the 'user' component is executed by selecting 'Customize> Test Component' from the menu of the customizer window. That is, a user is selected 310 from an organization component and attributes 320 of the selected component are shown.

In addition, Figure 4 attached shows a process of editing the properties of the user component.

After closing the execution of the user component, select the property of 'Propagate To GUI' in the property editor 130 as 'Auto', and then select the date of birth, home address, home phone number, and hobby enablement among the properties of the option attribute. Enable is false (410).

Thereafter, if the user selects 'Customization> Test Component' from the menu of the customizer window, the execution state 420 of the customized user component can be seen. At this time, the property 'Propagate To GUI' of the property editor 130 is set to 'Auto', which is an attribute that automatically edits the user interface which is a client component when the property of the server component is edited.

In addition, FIG. 5 shows that when editing an option attribute in the property editor 130, the attribute of 'Propagate To GUI' is set to 'Manual' and the server component is directly edited. The screen 510 to edit.

That is, the properties shown in the property editor 130 (reference numeral 520 in FIG. 5) are properties of 'TextBox' for inputting the selected name. When editing server components, you can tweak the layout or disable the setting of the Enable property to False.

6 shows a process of removing an unnecessary component in a component package when creating a new application of the component. The process of solving the dependency problem between components through the customizer 110 is as follows.

First, as indicated by reference number 610, select 'Project> New Project' from the menu of the customizer window to open the Project Explorer window, and then organize in the component browser 120. Drag and drop the package and prepare to create a new application.

Subsequently, as shown in 620, the method for setting the authority of the organization package is basically granted in the unit of 'group'. The companies that will use the new application are 'organization' and ' You don't need to have a group, so you want to delete a component called a group. The problem that occurs is the dependency problem. If you delete the 'group' component, there is no subject to set the authority. Therefore, an administrator who edits a component solves this problem by deleting the component and defining a new dependency in the following way.

FIG. 7 is a window 710 shown when 'Show Dependency' is selected from a menu that pops up when a right mouse button is clicked in the Project Explorer.

As you can see in this window, you can see that the 'checkAthority' interface of the 'group' component and the 'checkAuthority' of the 'authority' component have a dependency relationship.

When the dependency relationship is confirmed, the window indicated by reference numeral 710 is closed, the 'group' component is selected in the Project Explorer, and the 'group' component is deleted through the pop up menu.

Then, a dialog box such as 720 appears. At this time, the component is deleted by selecting 'Yes'.

Then, as shown by reference numeral 730, the customizer 110 finds a dependency relationship between components to be deleted in the project and performs component replacement.

FIG. 8 shows an interface of a 'permission' component dependent on the deleted component and shows a candidate component to replace the interface provided by the 'group' component (810). The administrator selects a dual 'user' component. 820 shows interfaces provided by the selected 'user' component, among which the interface named 'getUserID' is selected and added.

This completes the definition of the new dependency and ends the component deletion.

9 shows that the method of setting a permission by selecting the 'Permission GUI' component and testing it through the 'Pop Up' menu has changed from a group to a user.

While the invention has been shown and described in connection with specific embodiments thereof, it will be appreciated that various modifications and changes can be made without departing from the spirit and scope of the invention as indicated by the claims. Anyone who owns it can easily find out.

As described above, according to the present invention, a component can be searched from a component package built in a component repository to redefine a property in a desired form, and the redefined server components are reflected in the properties of the client component to connect each other. It provides a method and tool that can apply component-based development methods to business applications by supporting methods and tools that can solve dependency problems between components when assembling and deleting components. It can effectively support the application in the application area.

Claims (6)

In the component-based software development support system, A component browser module that shows the user the components or packages that they want to edit while browsing all packages in any component repository; A designer module for visually representing a component currently being edited through the component browser module; Project Explorer, which allows for assembly of components when creating new applications, includes modules; A property editor module for displaying various information (Provided Interface, Required Interface, Attribute, Option Attribute, Reference Attribute) of the selected component in the designer module or the project explorer module and allowing the dual option attribute to be edited; And A component redefinition tool system comprising a customizer module for storing customized components and creating a new project application. When you create a new application, a component browser module that shows the user the components or packages that you want to edit while browsing all packages in any component repository, a designer module that provides a visual representation of the component currently being edited through the component browser module. The Project Explorer, which allows you to assemble components, displays a module and various information (Provided Interface, Required Interface, Attribute, Option Attribute, Reference Attribute) of the component selected in the designer module or the Project Explorer module. A property editor module that allows you to customize the main window, plus a custom module that stores your customized components and creates new project applications. Equipped and operated in the manner in which financial tool system components: A first step of identifying various properties of a 'user' component by selecting various tabs of the property editor module from the component imported into the designer module; A second step of displaying a property of a 'user' component by selecting 'customization> test component' of the customizer module; After closing the execution of the user component, select 'Auto' as the property of 'Propagate To GUI' in the property editor module, and enable the date of birth, home address, home phone number, and hobby enablement among the properties of the optional attribute. A third process of generating; And The method of operating a component redefinition tool system comprising the fourth step of displaying the execution state of the customized user component when selecting 'Customize> Test Component' of the customizer module. The method of claim 2, In the property editor module, the property 'Propagate To GUI' is set to 'Auto'. When the property of a server component is edited, the user interface, which is a client component, is automatically edited. How to operate. The method of claim 2, When editing the option attribute in the property editor module, if the property of 'Propagate To GUI' is set to 'Manual', the server component is edited, and the client component 'UI' is directly edited, the properties appearing in the property editor module are Properties of the 'TextBox' that enters the selected name, which removes the false setting of the Enable property from being used when editing the server component or adjusts the screen layout. How it works. The method of claim 2, A first step of opening a project explorer module by selecting 'Project> New Project' of the customizer module and dragging and dropping an organization package in the component browser module to prepare for creating a new application; The way to set the permissions of the organization package is basically to grant authority in the 'group' unit. A company that will use the new application does not need to separate the 'organization' and the 'group'. And a fifth step of removing unnecessary components in the component package when creating a new application of the component comprising a second step of deleting the component. The method of claim 5, A first that indicates that the 'checkAthority' interface of the 'group' component and the 'checkAuthority' of the 'permission' component have a dependent relationship among the pop-up menus in the Project Explorer module; Steps; A second step of deleting a 'group' component through a pop-up menu by selecting a 'group' component in the project explorer module when the user has confirmed the dependency relationship through the first step; And The third step of detecting a dependency between components to be deleted in the project of the customizer module and performing component replacement is performed. When a subject to set authority is deleted by deleting a 'group' component, a sixth defining new dependency relationship is performed. A method of operating in a component redefinition tool system, further comprising a process.