KR20040083624A - Component sharing and managing system and its method - Google Patents

Abstract

PURPOSE: A system and a method for sharing/managing components are provided to offer a basic infrastructure for an enterprise system or a charged site through the EC(Electronic Commerce) to share the components with users by systematically managing the components. CONSTITUTION: A user client PC(20) requests a request for searching, registering, modifying, and downloading the components by connecting to a central server(10). A manager client PC(30) processes component registration/modification request items registered by the user client PC and judges/manages a test and the registration of the components by connecting to the central server. The central server is equipped with a communication part(11) performing communication with the user/manager client PCs, a storing part(12) storing the components, and a controller(13) controlling the communication part and the storing part, processing the request of the user/manager client PCs by a component sharing/managing program, and managing/storing the stored components.

Description

Component sharing and managing system and its method

The present invention relates to a component sharing management system and method. More specifically, to maximize the reusability of the components that make up the program, the client / manager manages the registration, modification, and deletion of the components, and also enables the change history and version management, and the use of component resources through testing and download. A system and method for managing component sharing in a server environment.

In general, the term 'component' refers to a single unit of execution that constitutes a software program, which is further evolved from the conventional concept of object, module, and class. From the programmer's point of view, the term refers to a single, independent unit of execution.

Since Windows was introduced as the main operating system, the introduction of dynamic programming eliminates conventional sequential programming and separates the program into object modules according to specific functions. It became a function.

As a result, programmers can implement programming more conveniently by simply linking with components that have already been verified, without having to program all the source code for a basic interface with the user. .

For example, in a communication network programming where a user executes an executable exe program on a PC, enters his ID and password, and connects to a network server, a user configures a login and an input window display with an image file as a background. The programmer can freely create a login input display program for accessing the server in e-commerce, home banking, office management programs, etc., by changing only the attributes of the image file and the login input window. This is just one example, and components can be freely configured.

Such a component has the advantage that a user can easily program the software even without the specific programming language and the development tool, and has the advantage that even components written in different languages can be bundled together to create an executable program.

1 shows a conventional component management system 1, in which an existing system is focused on a storage function for component reuse. The users who use the component become programmers, and the shared component resources are retrieved from the centrally located component management tool in the usage process P1, evaluated to meet the conditions, and used for download. In the generation process P2, a new component is completed using the selected component. This completed component is tested, documented and reviewed by the administrator in the management process (P3), and is then decided whether to be accepted or rejected by the component management tool.

The existing component management system 1 has been focused on the storage function of the component in terms of reuse or the storage and management functions in terms of component distribution. Therefore, there was a problem that the interface at the point of contact with the user for component sharing was only a simple search function or a simple recommendation based on usage priority.

In more detail, when looking at the information providing function that allows the user to select the desired component, it provides only basic information about the general component and the user's utilization rate or ranking, and provides a simple keyword search degree. Support grouping of components.

However, this fragmentary function did not allow the user to properly select the desired function of the component, and could not provide practical information related to the use of the component, causing the component reuse to slow down.

Component sharing management system according to the present invention for solving the problems of the conventional component sharing management system and method as described above, the system or electronic commerce in the company organization that can share the component to users by systematically managing the component It aims to provide basic infrastructure of monetization site through.

In addition, the component sharing management method according to the present invention is to improve the efficiency of component reuse through the management (registration, modification, deletion), change management, bug report, test, component search and user management of the component.

1 is a schematic structural diagram of a component sharing management system in a conventional environment.

2 is a schematic block diagram of a component sharing management system according to an embodiment of the present invention.

3 is a functional block diagram of a component sharing management system according to an embodiment of the present invention.

4 is a schematic processing structure diagram of a component sharing management system according to an embodiment of the present invention.

5 is a processing flowchart of a user client PC in the component sharing management method according to an embodiment of the present invention.

6 is a processing flowchart of the manager client PC in the component sharing management method according to an embodiment of the present invention.

7 is a general functional diagram of a central server in a component sharing management method according to an embodiment of the present invention.

Explanation of symbols on the main parts of the drawings

1: conventional system P1: process used

P2: Creation Process P3: Management Process

2: this system 10: central server

11: communication unit 12: storage unit

13: control unit 14: search engine

15: registry 16: query adapter

20: user client PC

30: Administrator Client PC

The component sharing management system and method according to the present invention for achieving the above object is a component sharing management system of a client server environment through a network, and accesses the server to request a search, registration, modification and download of a component. User client PC; An administrator client PC connected to the server to process a request for registration and modification of a component registered by the user client PC and to determine and manage the test and registration of the component; And a communication unit for communicating with the user and administrator client PCs, a storage unit for storing components, a control unit for the communication unit, and a storage unit, and processing a request for the user and administrator client PCs by a predetermined component sharing management program. It comprises a; central server having a control unit for managing and controlling the user client PC and the manager client PC characterized in that the component stored in the central server to share and reuse.

According to a preferred feature of the present invention, a method of managing component sharing in a client server environment through a network, wherein a user client PC accesses a central server to request a download through a component search function, and the central server provides the requested component. First step; A second step of the user client PC using the component received in the first step and requesting registration and modification of a new component to the central server; The manager client PC accesses the central server, creates a component registered and modified by the user client PC in the second step, tests a component that is registered or newly registered by adding a new component or modifying an existing component. Creating a bug report; And the central server provides an interface for registering, modifying, and deleting components from the user and administrator client PCs through a communication unit, and manages the components by controlling and versioning the components stored in the storage unit under the control of the controller. And a fourth step, wherein the user client PC and the manager client PC share and manage the components stored in the central server for reuse.

Component sharing management system and method according to the present invention configured as described above, by building a component sharing system in the central server to mediate the user client PC and the administrator client PC, the management (registration, modification, deletion of the component according to the component sharing method) ), Change management, bug report, test, component search, and user management to support component reuse by multiple user client PCs.

1 is a schematic structural diagram of a component sharing management system in a conventional environment, FIG. 2 is a schematic structural diagram of a component sharing management system according to an embodiment of the present invention, and FIG. 3 is a functional block diagram of the component sharing management system. 4 is a schematic process structure diagram of the component sharing management system, FIG. 5 is a process flowchart of a user client PC in the component sharing management method according to an embodiment of the present invention, and FIG. Fig. 7 is a general function diagram of a central server in the component sharing management method.

Hereinafter, a preferred embodiment of the present invention including the above components will be described in more detail with reference to the accompanying drawings.

1 shows a schematic structure of a component sharing management system 1 in a conventional environment. The conventional system 1 was simply an environment where components were stored in a database and shared by multiple users.

In the conventional environment, the user has downloaded the component through a search on the use process P1 for the centrally located component management tool. The downloaded component is used by users and newly configured in the creation process P2 to request a new registration. In the management process (P3), it is determined whether or not the new component requested to be registered is registered by the component management tool by the administrator.

In the conventional system 1, only the resource sharing provides a function of a common repository, but functions in terms of work efficiency, such as an interface for actual component resource sharing, version management, change management, and history user management. I couldn't finish it.

2 shows a schematic configuration of a component sharing management system 2 according to an embodiment of the present invention. The system 2 according to the invention consists of a central server 10, a user client PC 20 and an administrator client PC 30.

The central server 10 transmits and receives components and data with the user client PC 20 and the manager client PC 30 through the communication unit 11. The storage unit 12 stores components as shared resources. The control unit 13 controls the communication unit 11 and the storage unit 12 according to the component control method according to the present invention and manages the components so that they can be reused.

3 is a block conceptual diagram illustrating various functions and configurations of a component sharing management system according to an embodiment of the present invention.

The communication unit 11 interfaces web services of the user client PC 20 and the manager client PC 30 connected via a network. The web service also supports interfacing with external case tools or development tools.

The storage unit 12 is a space in which components and related files are physically stored, and various media such as a database, LDAP, and a file system may be used. The module accessing the storage unit 12 may include a registry 15. This allows access to be managed via the same interface, regardless of the particular medium. The registry 15 is a module that provides an interface for accessing the storage unit 12, which is a physical store. The module for accessing the storage 12 in which the component and related files are stored allows transparent access regardless of the media characteristics of the storage because the module must be through the registry 15.

The framework 13 corresponds to the control unit 13 as a main core of the component sharing management system 2 of the present invention, and controls and manages each component to perform its function.

The search engine 14 is a search engine providing a component search function and is provided in a structure in which various products can be added-in through the search adapter 16. The query adapter 16 is a module that provides an interface to add-in various search engines 14, and provides a same interface to a module using the search engine 14 even if any search engine is add-in. to be.

3 shows a total of nine functions in the component sharing management system 2. The main functions as shown are described as follows.

The component management function is a module that manages a component and is a module that is responsible for registering / modifying / deleting a component. The registered data is all related to the component, such as a component executable file, a specification, and related outputs, and the registered data is stored in the storage unit 12 through the registry 15.

The change management function is a module that manages the change history of the registered component. The change management function of the registered component manages the change request and the approval and processing of the registered component, and the change history and the change requestor of the changed component.

The statistics function is a module that handles statistics on components and users, and provides statistical information such as component registration status, user download status, user upload status, bug occurrence status by component, and bug processing status.

The bug report function is a module that reports and handles bugs on registered components. Reported bugs are determined and notified by the administrator's approval of the bug fix schedule and schedule. Bugs accepted as errors will be registered as change requests and will go through the fix process for the component.

The community function provides various bulletin boards as a module for exchanging information about components and how to use the component management system.

The user management function is a function for managing effective users. When the system 2 is built as an infrastructure system model in a company organization, it becomes a company employee. In the e-commerce model, it corresponds to a paid user. Because a component must be protected as a shared resource, only authorized effective users can access and use the component. To this end, this module manages information and permissions for users.

4 illustrates a schematic processing flow in a component sharing management system according to an embodiment of the present invention. The user client PC 20 and the manager client PC 30 are serviced through the communication unit 11 of the central server 10. These client PCs can create components through the design and implementation of components in an integrated development environment, but only the client client PCs have final approval of the components.

The user client PC 20 accesses the central server 10 through the communication unit 11 and searches whether a desired component is registered. At this time, the search target is a component specification and related output. If you find a component you want, you can download it or download it after testing. In particular, the test may execute the component under the control of the control unit 13 on the central server without receiving a download. If you do not find the component you want, you can request new development for the desired component functionality. In addition, the user client PC 20 may request to correct bugs, add or change a function found while using the component, and request development and registration of a new component.

The administrator client PC 30 approves the user's request. For new and change requests, the manager assigns a schedule with a person in charge, approves and responds to bugs, and reviews and approves the requested components so that they are registered in the storage unit 12. In addition, all such requests and approvals are documented.

The system 2 constructed according to the present invention can be executed in conjunction with an external modeling tool, and can be expanded to the component market by adding a component distribution system in a plug-in form. That is, the system 2 can be implemented internally by building an in-house infrastructure system model, and can also be built as an e-commerce system model and implemented as a paid business.

5 is a flowchart illustrating an operation process on a user client PC 20 in a method of managing component sharing according to an embodiment of the present invention.

In the user client PC login step (S20), the user client PC 20 connects to the central server 10 through the communication unit 11. In the component search step S21, the user client PC 20 searches for a desired component. When the desired component is searched in the search OK step S22, the execution of the component is tested on the central server 10 in the test step S23, and then the searched component is downloaded through the download step S24. If the desired component is not found, the registration or modification request step (S25) requests the registration or modification of the desired component.

6 illustrates an operation process on the manager client PC 30 in the component sharing management method according to an embodiment of the present invention.

In the manager client PC login step (S30), the manager client PC 30 connects to the central server 10 through the communication unit 11. The administrator searches for a requirement for a component from the user client PC 20 in the registration or modification request step (S32). If there is no requirement, it is terminated. If there is a requirement, the component is modified or newly created according to the user's needs. In addition, the test step (S33) is tested whether the component operates as intended according to the user's request, and in the report creation step (S34) to create a report, such as the test results and specifications of the component. If there is no abnormality in the report creation result registration, it is determined whether to register in the component registration step S35, and the component is stored in the storage unit 12 in the component storage step S36.

7 illustrates a general function of a central server in a component sharing management method according to an embodiment of the present invention.

In the component retrieval function F10, the component is retrieved from the storage unit 12 under the control of the control unit 13 with respect to the component requested by the user client PC 20.

Since the component test function F20 may be dissatisfied with the test result after the user downloads it to his client PC, the component test function F20 may test the central server 10 before downloading and determine whether to download.

The management function F30 of the usage history increases the reuse rate of the shared resources by managing the usage history. That is, the stability of the component can be secured through the usage history of the component usage frequency and the user's usage.

The change history management function F40 can know the user in more detail by managing how the component is modified by whom.

The version management function (F50) maintains the interface and compatibility between the components of the module to be the ultimate program. In addition, the version management function enables to manage the upgrade information of the component in detail like the change history management function (F40).

The bug report function F60 improves the quality reliability of shared component resources by checking that components perform well and reporting the results to component users.

As described above, embodiments of the component sharing management system and method according to the present invention are constructed. The technical scope of the present invention is not necessarily limited to the above-described embodiment, and various modifications and applications can be made without departing from the technical scope of the present invention.

In the component sharing management system and method according to the present invention, a component sharing management tool is installed on a central server so that a user client PC requests a component search, download, registration, and modification, and an administrator client PC tests, evaluates, and reports a component. By creating and publishing it to users, the verified component is registered to provide the effect of component quality management.

In addition, the central server is operated by the component sharing management method according to the present invention to increase the efficiency of component reuse through component management (registration, modification, deletion), change management, bug report, test, component search and user management functions. Provide effect.

Claims (3)

A component sharing management system in a client server environment over a network. A user client PC which accesses the server and requests for searching, registering, modifying and downloading components; An administrator client PC connected to the server to process a request for registration and modification of a component registered by the user client PC and to determine and manage the test and registration of the component; And The communication unit for communicating with the user and the manager client PC, the storage unit for storing the component, the communication unit and the storage unit is controlled and processes the request for the user and the manager client PC by a predetermined component sharing management program and stored components It comprises; a central server having a control unit for management control And the user client PC and the manager client PC share and reuse components stored in the central server. A method of managing component sharing in a client server environment over a network. A first step in which a user client PC accesses a central server to request a download through a search function of a component, and the central server provides the requested component; A second step of the user client PC using the component received in the first step and requesting registration and modification of a new component to the central server; The manager client PC accesses the central server, creates a component registered and modified by the user client PC in the second step, tests a component that is registered or newly registered by adding a new component or modifying an existing component. Creating a bug report; And The central server provides an interface for registering, modifying, and deleting components from the user and administrator client PCs through a communication unit, and under the control of the control unit, manages components by changing and versioning the components stored in the storage unit. Including four steps; And managing the user client PC and the administrator client PC to share and reuse the components stored in the central server. The method of claim 2, The first step, And testing the data retrieved by the user client PC at the central server and downloading the data according to a request of the user client PC.