KR101407987B1 - Program rebuilding method of enterprise resource plan based on additional property - Google Patents

Abstract

The present invention relates to a method of rebuilding a program based on additional attributes of an enterprise resource management system.
In the method of the present invention, when registering the attributes of the control property, the method attribute, the event attribute, the service attribute, and the standard screen information into the business logic, the software architecture that separately manages the existing code and the change code, .
The method of the present invention manages the existing code and the added code separately so that unnecessary development resources are not invested by using the additional property of the program re-builder, thereby managing the existing code without affecting the added code to shorten the development period And it is easy to change the program according to the needs of the user.

Description

[0001] PROGRAM REBUILDING METHOD OF ENTERPRISE RESOURCE PLAN BASED ON ADDITIONAL PROPERTY [0002]

The present invention relates to an enterprise resource planning (ERP) system, and more particularly to a program rebuilder for a client.

Today, the ERP system efficiently manages all the human and material resources within the enterprise used for business activities, ultimately enhancing the competitiveness of the enterprise. The ERP system functions as an integrated application package consisting of several modules to help manage key processes in various business sectors, including manufacturing, purchasing, inventory, ordering, supplier transactions, and customer service provision. The ERP system also includes software modules for human resources. This software package is widely used today because it can increase the efficiency of enterprise business by using ERP software composed of several modules when computer business is incorporated into computer system.

However, the business activities of companies are to be variously reconfigured in response to changes in corporate goals or organizational structure. There is a need to reconfigure or newly build optimized business programs in response to changes in the business flow of the enterprise.

The problem is that when additional commercial programs are developed, the existing code is further developed by including existing code. According to the prior art, existing code is copied and used at the time of such additional development. Most of the additional development is similar to existing code, but only to the extent that the items to be managed are added or slightly changed for the client's business logic.

Since we are developing new code based on existing code like this, if there is an error in the code, the same error is repeated in addition or modification. Therefore, the task of correcting errors in existing code is very troublesome in the field of program development because it involves the task of analyzing and modifying newly added code.

The inventors of the present invention have made a long effort to solve the above problems and propose a new approach.

It is an object of the present invention to provide a method for minimizing the spread of an existing code to an added code by separately managing an existing code and an added code.

The method of the present invention is structured to work with added code at the same time without copying existing code. Another object of the present invention is to make changes to existing programs to be applied to programs using existing code.

On the other hand, other unspecified purposes of the present invention will be further considered within the scope of the following detailed description and easily deduced from the effects thereof.

To achieve these and other advantages and in accordance with the purpose of the present invention, as embodied and broadly described herein, there is provided a method for re-

Configuring a software architecture for separately managing an existing code and a change code by distinguishing a standard item from an add / replace item in registering attributes of a control property, a method property, an event property, a service property, and standard screen information as business logic;

Providing a user interface for the standard item and a user interface for the add / replace item to the user terminal; And

When the user terminal registers a user interface for an add / replace item for any one of the control attribute, the method attribute, the event attribute, the service attribute, and the standard screen information attribute, And executing the software by preferentially applying the substitute item, and registering the logic change of the user terminal without modifying the standard screen.

According to the method of the present invention, the program development period can be shortened and the program can be easily changed in accordance with the user's demand.

According to the present invention, since the existing code and the added code are separately managed in the present invention, even if there is a problem with the existing code, the problem can be prevented from spreading to the added code. This has the advantage of preventing a development environment in which unnecessary development resources are invested.

On the other hand, even if the effects are not explicitly mentioned here, the effect described in the following specification, which is expected by the technical features of the present invention, and its potential effects are treated as described in the specification of the present invention.

1 is a diagram schematically showing a configuration of a software architecture of a program re-builder according to an embodiment of the present invention.
2 is a diagram showing an example of a program re-building scenario when executing a function of adding a new control attribute according to the method of the present invention.
3 is a diagram showing an example of a program re-building scenario when executing a function of replacing existing control attributes according to the method of the present invention.
4 is a diagram showing an example of a program re-building scenario when executing a function of adding a new method attribute according to the method of the present invention.
5 is a diagram showing an example of a program re-building scenario when executing a function of replacing existing method attributes according to the method of the present invention.
6 is a diagram showing an example of a program re-building scenario when executing a function of adding and replacing a new event according to the method of the present invention.
7 is a diagram showing an example of a program re-building scenario when executing a function of replacing existing event attributes according to the method of the present invention.
8 is a diagram showing an example of a program re-building scenario when executing a function of adding a new service attribute according to the method of the present invention.
9 is a diagram showing an example of a program re-building scenario when executing a function of replacing existing service attributes according to the method of the present invention.
10 is a diagram showing an example of a program re-building scenario when executing a function of replacing the attribute of the standard screen information according to the method of the present invention.
* The accompanying drawings illustrate examples of the present invention in order to facilitate understanding of the technical idea of the present invention, and thus the scope of the present invention is not limited thereto.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may obscure the subject matter of the present invention.

<Software Architecture>

1 shows a schematic system configuration of a program development architecture using the program re-builder of the present invention. Software having the same structure in this architecture is installed in the client computer terminal, and resources for executing the software are built in a database to constitute an ERP system.

As shown in FIG. 1, the ERP system of the present invention may include a presentation layer 110, a service layer 120, and a DB 130. The presentation layer 110 is an area where a screen operated by a user terminal exists. The service layer 120 is a server area for processing business logic. The DB 130 is an area for processing data in a data base.

The service layer 120 may be divided into a business service 120a and a data service 120b. The business service 120a is typically an area for processing business logic in a middle server, and the data service 120b is a business logic for configuring a business service. The business service 120a and the data service 120b may be variously structured. In order to increase the reuse of program modules, it is preferable to divide the business logic into smaller units. A small unit of business logic divided in this way can be defined as a data service 120b and a service in which a plurality of the data services 120b are arranged can be defined as a business service 120a.

The data service 120b exchanges data with the DB 130. [ I / O functions as an item for exchanging data between the data service 120b and the business service 120a. The data service 120b is processed in a series of bundles in order. The flow of this process becomes WF (Workflow). The metadata is data expressing the structure of the workflow and method I / O constituting the data service.

The presentation layer 110 includes logic for executing various user interfaces and programs. The control 111 performs functions such as inputting a text or receiving a date and a date, such as a button or a text box. The sheet 113 has an Excel-shaped control function. The method 117 is a unit of logic to be processed like a function, and the event 115 calls an ordinary method 117 that occurs when a button is clicked.

In FIG. 1, a part denoted by &quot; &quot; denotes a part for modifying the attribute of a standard item to be applied to a specific client (replacement processing), and a part denoted by &quot; And the part marked with the "☆" tabular represents the part added for the specific client. According to the program structure of the present invention, the specific logic is replaced and / or added to each layer (□, ▨), and these portions are selectively applied at execution time, thereby providing an environment for reusing most codes.

Meanwhile, the data service 120b is executed in a SQL (Structured Query Language) sentence and is connected to a database.

<Implementation of main functions>

1. Ability to add new control properties

The function of adding a new control attribute by the method of the present invention is realized by adding screen information to be added by a client to information of a screen used as a standard. That is, the function of adding the control requested by each client without modifying the standard screen can be implemented.

Figure 2 presents a preferred example of such a function. The control interface 1110 allows the additional control 1112 to be placed in the screen information composed of the standard control 1111. [ The standard control 1111 is represented by a dotted line so that it can not be changed by the user terminal, and the arranged additional control 1112 can be configured to be managed independently by the user terminal.

2. Ability to replace existing control properties

The function of replacing the existing control attribute by the method of the present invention is to allow the client to change some of the screen information used as the standard to the screen information desired by the client but to provide the control information desired by the client without modifying the standard screen . &Lt; / RTI &gt;

Figure 3 presents a preferred example of such a function. The existing attribute may be changed to the new attribute 1114 in the standard control pop-up menu 1113 of the control interface 1110. [ For example, when the background color of the control interface 1110 is developed as black, only the attribute with gray background is additionally registered when the client requests gray, and the additional registered attribute is defined to have priority over the existing attribute.

3. Ability to add new method attributes

The function of adding a new method attribute by the method of the present invention may include a function of managing a method by adding a method desired by a customer in addition to a screen method used as a standard such as a query storage without modifying the standard screen .

In a more specific embodiment, an existing standard method registration menu 1170 is extended and used as shown in FIG. 4. A menu composed of standard methods (area indicated by a dotted line, 1171) restricts editing of the user terminal, The added methods can be managed separately for each client.

4. Ability to replace existing method attributes

The function of replacing an existing method property by the method of the present invention is a function of changing part of a method property of a screen used as a standard to method information desired by a client. In this embodiment, the client can provide desired method information without modifying the standard screen.

This embodiment is conceptually the same as the function of replacing the existing control attribute described above. There is a case where the existing specific method needs to be changed according to the necessity of the client terminal. As shown in FIG. 5, the standard method menu 1173 is changed to a new attribute 1174. When a necessary method is created and a program is loaded, the added method 1174 among the two methods can be preferentially used to configure a desired screen for each client.

Alternative attributes of standard methods can be managed by extending the standard input window. That is, according to the present invention, an existing method attribute is replaced and managed by using a screen for managing an attribute of the substitute method.

5. Ability to replace new events

The function of adding and replacing a new event by the method of the present invention means a function of generating a new event on a screen used as a standard and extending existing user interface information by connecting it to a user interface event such as an existing inquiry and storage . The function of replacing the existing method attribute is a function of changing an existing method, but the additional substitution of this embodiment corresponds to a function of adding an event not existing.

As shown in FIG. 6, the standard event list 1175 is replaced with an additional event list 1176, at which time the function of linking the added event list 1176 to the standard method 1171 is executed. The newly added event list can be managed for each client.

6. Ability to replace existing event attributes

A function of replacing an existing event attribute by the method of the present invention can be implemented. The client can change some attributes of existing events of the screen used as standard. At this time, instead of modifying the standard screen, the client executes the function of replacing the existing attribute with the desired event attribute.

As shown in FIG. 7, a new list 1175a is added to the standard event list 1175 connected to the standard method 1171, and is managed on the standard event list input screen. That is, in this embodiment, a new event list is added to the existing event list.

7. Ability to add new service attributes

A function of celebrating a new service attribute can be implemented by the method of the present invention. The ability to add new logic to a standard service and extend it to the business logic requested by the client without changing the standard service can be performed.

As shown in FIG. 8, it is possible to add a new service, without changing the standard service, by adding a new service 1211 to the standard service list 1210 that represents the business logic of the standard service 1200.

8. Ability to replace existing service attributes

The function of replacing an existing service attribute by the method of the present invention can be implemented. In this embodiment in which some items of the standard service are changed to attributes desired by the client, the standard service is not modified as in the above-described functions.

As shown in FIG. 9, one of the standard service attributes 1220 included in the standard service 1200 is changed to a new attribute 1221, and the modified attribute is used first.

9. Ability to replace attributes of standard screen information

The function of replacing the attribute of the standard screen information by the method of the present invention can be implemented. This function replaces attributes that depend on the screen, such as screen name or screen type, which is the attribute of the screen information used as a standard, with the attribute desired by the client without modifying the standard service.

It is possible to replace some of the attributes included in the attribute list 1250 of the standard screen 1230 with new attributes 1251 as shown in FIG.

The scope of protection of the present invention is not limited to the description and the expression of the embodiments explicitly described in the foregoing. It is again to be understood that the scope of protection of the present invention can not be limited by obvious alterations or permutations of the present invention.

Claims (1)

Configuring a software architecture for separately managing an existing code and a change code by distinguishing a standard item from an add / replace item in registering attributes of a control property, a method property, an event property, a service property, and standard screen information as business logic;
Providing a user interface for the standard item and a user interface for the add / replace item to the user terminal; And
When the user terminal registers a user interface for an add / replace item for any one of the control attribute, the method attribute, the event attribute, the service attribute, and the standard screen information attribute, And executing the software by preferentially applying the substitute item, and registering the logic change of the user terminal without modifying the standard screen.

Images