KR20160103842A

KR20160103842A - System and Method for managing product using business rule management system

Info

Publication number: KR20160103842A
Application number: KR1020150026736A
Authority: KR
Inventors: 김길곤; 심현섭; 이종호; 김기한; 김성민
Original assignee: 주식회사 이노룰스
Priority date: 2015-02-25
Filing date: 2015-02-25
Publication date: 2016-09-02

Abstract

The present invention relates to a method and system for managing goods using BRMS, the method comprising: generating an object type: creating an object type relationship structure; Generating a meta model for each object type; Creating objects corresponding to a product for each object type; Creating an upper / lower relationship structure of objects for each object type; And receiving the service rule call for the merchandise management data, reading and analyzing the rule from the rule storage unit, reading the merchandise management data from the merchandise management system repository and providing the merchandise management data to the business program, When a metadata service rule call is received, the rule is read and interpreted from the role storage unit, the metadata is read from the product management system storage, and the metadata is provided to the business program.
According to the present invention, even when a management item is added or deleted, the modification of the physical model is not accompanied, and the modification of the program is minimized, thereby shortening the time period for releasing the product.

Description

[0001] The present invention relates to a product management system and method using BRMS,

The present invention relates to a merchandise management system, and more particularly, to a merchandise management system and method using a BRMS (Business Rule Management System).

The conventional product management system goes through a process until the product developer plans and develops the product, applies it to the computer system, and sells it.

1 shows a conventional business system development process. Referring to FIG. 1, when the business department 100 requests a commodity change (①), the IT department 120 understands the work for the commodity commissioned to change (②) (③) Compile (④) Once compiled, it performs IT test (⑤) When the test is completed, it performs the business test in the business department (⑥) The department 120 requests the implementation of the business system (7), and the system operation department 140 performs the change in the business system to reflect the changed part (8)

In the conventional business system development process as shown in FIG. 1, in view of the current market situation in which a variety of products desired by customers are to be sold to the market in a short period of time, when a business launches a new product or requests a change of an existing product, Because it takes a long time until it is applied, there is a limitation that the product can not be released in a timely manner.

Also, when management items are added to or deleted from the product management system, the existing product management system requires a change in the physical model, and therefore it takes much time to change the physical model and change the business logic of the related program.

A problem to be solved by the present invention is to provide a merchandise management system using a BRMS, which can dramatically shorten a product launch period by leading an operating entity of merchandise management in a business department.

Another object to be solved by the present invention is to provide a product management method using a BRMS, which can dramatically shorten a product launch period by leading an operating entity of product management in the business department.

According to an aspect of the present invention, there is provided a method for managing a product using BRMS, the method comprising: (a) creating an object type necessary for managing the object, when a product to be managed by the product management system is an object; (b) setting the generated object type as a node of a tree structure, and creating a hierarchical relationship between the generated object types as an object type relationship structure represented by a tree structure; (c) generating, for each of the generated object types, a metamodel for each object type, the object type being a management factor of the object type and an attribute indicating a property of the item; (d) generating objects corresponding to goods to be served to customers for each object type, with respect to the generated object types; (e) creating a relation structure between the generated object types and the created object to create an upper and lower relationship structure of the objects; (f) generating meta data for each object by combining the generated meta-model for each object type and the generated objects for each object type, Upon receiving a service rule for product management data corresponding to the upper and lower relationship structure, the business rule engine BRE reads the rule from the rule storage unit provided in the business rule management system (BRMS) And provides the business program with the merchandise management data from the store of the merchandise management system. When receiving the metadata service rule corresponding to the metadata generated in the step (f) from the business program of the mission-critical business system, The engine (BRE) is a roll provided in the Business Rule Management System (BRMS) e) reading and analyzing the rule from the storage unit, reading the metadata from the repository of the merchandise management system, and providing it to the business program.

Wherein the store of the goods management system stores metadata about the goods, the metadata includes a rule code, and the business rule engine (BRE) reads the meta data of the goods management system, If the meta data is a rule code, the business rule engine BRE reads a rule corresponding to the rule code from a rule storage unit provided in a business rule management system (BRMS), analyzes and executes the rule And transmits data corresponding to the input condition to the business program.

According to another aspect of the present invention, there is provided a product management system using a BRMS, wherein when a product to be managed is an object and each node classified into a tree structure for managing the object is an object type, An object type management unit for generating and managing the object type; An object type structure management unit for creating and managing a structure between the object types when an object type structure is represented by a tree structure of a hierarchical relationship between the object types; A metamodel management unit for each object type to generate and manage a metamodel for each object type, the metamodel comprising an item that is a management factor of the object type and an attribute that indicates a property of the item; An object management unit for generating and managing objects corresponding to goods to be provided to customers for each object type, with respect to the generated object types; An object structure management unit for creating and managing a top-bottom relationship structure of objects by combining the generated object structure with the generated object structure; A meta data manager for generating and managing meta data for each object by combining the generated meta model for each object type with the generated objects; Product management data including an upper-lower-level relationship structure of objects for each object type generated by the object structure management unit, metamodel information for each object type generated by the metamodel management unit, and a product storing metadata generated by the metadata management unit Managed system repository; And a business rule management system (BRE) that includes a rule storage unit that stores business rules, a rule management unit that manages the business rules, and a business rule engine (BRE) that reads and analyzes rules stored in the rule storage unit (BRMS).

The business rule engine (BRE) receives a service rule for product management data corresponding to an upper-lower-level relationship structure of objects generated by the object structure management unit from a business program of the main system, Reads the product management data from the product management system storage to provide the product management data to the business program, and upon receipt of a metadata service rule call corresponding to the metadata from the business program of the mission system business system, Reads and interprets the rules, reads the metadata from the repository of the merchandise management system, and provides the meta data to the business programs.

The metadata management unit requests the rule management unit to generate a rule. The rule management unit generates a rule, stores it in a rule storage unit, and transmits a rule code corresponding to the rule. The metadata management unit includes a rule code And stores it in the product management system storage unit. When the business rule engine (BRE) receives a metadata service rule call corresponding to the metadata from the business program of the mission service system, the business rule engine (BRE) reads the rule from the role storage unit, analyzes the rule, If the read metadata is a rule code, the rule corresponding to the rule code is read from the rule storage unit provided in the business rule management system (BRMS), interpreted and executed, And transmits the data to the business program.

And a recording medium on which the above-described invention can be read by a processor recording a program executed by the processor.

According to the product management system and method using the BRMS according to the present invention, even when the management item is added or deleted because the product is created using the BRMS, the modification of the work program of the main system is minimized This can dramatically shorten the time-to-market and maximize the profit of the company that sells the product.

In addition, by providing an object pool and a relational object, a new product can be created and released in a short period of time when a product similar to a previously sold product is released by using an object reuse function and an object copy function.

Also, instead of returning only formal quantitative values, Rule can be applied to return values to return variable values according to the conditions, so that the desired values are reflected to the work without modification of the program and applied immediately I can do it.

In addition, the present invention can provide products in a development server even while an operation server is operating, and provide a real-time transfer function that can be transferred to an operation server.

1 shows a conventional business system development process.
FIG. 2 shows a business development process of a product management system using BRMS according to the present invention.
FIG. 3 is a block diagram showing a configuration of a product management system using BRMS according to an embodiment of the present invention.
Figure 4 FIG. 2 is a block diagram illustrating a configuration of a product management system using BRMS according to the present invention, which provides a service based on a meta model.
FIG. 5 shows an example of the type relationship structure of the insurance industry.
6 shows metamodel (attribute) information managed by the metamodel management unit 412. FIG.
FIG. 7 shows an example in which meta model information is defined in the insurance industry.
FIG. 8 shows a process flow chart according to functions in the meta model management unit 412. FIG.
9 shows an example of metadata storage according to a metamodel (attribute).
10 shows an example of object generation by type in the insurance industry.
Figure 11 shows a flow diagram to manage objects in an object type in the object management unit 406. The
FIG. 12 shows an example of object structure creation in the insurance industry.
13 is a flowchart showing that the object structure management unit 408 creates an object structure.
FIG. 14 shows an example of metadata management by object type in the insurance industry.
FIG. 15 shows an example in which a rule is applied in a merchandise management system using BRMS.
FIG. 16 shows an example of collective copying during batch management of metadata in the insurance industry.
FIG. 17 shows an example of conditional retrieval and modification during batch management of metadata in the insurance industry.
FIG. 18 shows an example of comparing object structures among objects in the object comparison unit 434.
FIG. 19 shows an example of comparing item values among objects in the object comparing unit 434.
FIG. 20 shows an example of managing history of changes of objects, meta models, and meta data in the history management unit 432. FIG.
FIG. 21 shows an example of managing the history of the objects, the meta model, and the metadata in the history management unit 432. FIG.
FIG. 22 shows an example of inquiring the entire attribute rule information by the use rule information inquiry unit 438. FIG.
23 shows an example of inquiry of attribute rule information by item in the use rule information inquiry unit 438. [
Fig. 24 shows a user interface screen requesting approval provided by the approval / release unit 436. Fig.
Fig. 25 shows a screen for approval / rejection provided by the approval / transfer unit 436. Fig.
26 shows an approval data escape screen provided by the approval /
Fig. 27 shows an immediate transfer screen provided by the approval / transfer part 436. Fig.
28 is a flowchart of a metadata service using BRMS.
FIG. 29 is a flowchart showing an embodiment of a product management method of a product management system using a BRMS according to the present invention.
30 shows the transfer and approval in the merchandise management system using the BRMS according to the present invention.
FIG. 31 shows a flow of service of the system of the insurance system using the BRMS and the metamodel in the business process flow of the insurance system and the business process flow of the insurance system.
32 shows an example of addition of management items and change processing of business logic in the conventional merchandise management system, and shows a physical model change and a business program change.
FIG. 33 shows a flow of merchandise management in the merchandise management system using the BRMS.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. The embodiments described in the present specification and the configurations shown in the drawings are merely preferred embodiments of the present invention and are not intended to represent all of the technical ideas of the present invention and therefore various equivalents And variations are possible.

FIG. 2 shows a business development process of a product management system using BRMS according to the present invention.

The product management system using the BRMS includes a GUI (Graphic User Interface) for registering and managing the planned products and a tool for supporting the integrated management of the products in order to support the business-led business processing method in the business department 200 to provide. Register the goods and the rules directly in the business department (200), test it in the business, apply for the system, and reflect the system implementation. By doing what the IT department 220 is doing in the business department, it is a factor that can shorten the product launch period drastically.

Also, by providing an object-oriented based product tree that expresses various types of formal structure, service, and attributes of products, it is possible to combine and integrate services according to each element and service, Can be realized.

In addition, the combination and convergence of each item of goods and service can inherit the attribute from the upper product and define the specialized attribute separately, thereby making it possible to quickly and easily create a new product.

In addition, a function of reflecting the developed product in the operating system of the system operation unit 240 in real time is provided, so that the product can be released in a short time.

The data management method of the metadata format can be applied immediately without additionally changing the physical model and the program even when the management item is added or deleted, so that it is possible to drastically shorten the time required to change the physical model and the program.

First, terms used in the present invention will be defined.

An object refers to a product to be managed by the merchandise management system according to the present invention, and is mainly managed as a name of a product to be actually sold, and is divided into an external name and an internal name, and includes a code.

The object type is an object for managing an object. The object type refers to each node classified into a tree structure for managing an object, and refers to a product and configuration information of a product constituting the product. For example, an object type in an insurance product may be a representative product, a commodity, a main contract, a special contract, a security, and the like. And object types in bank products can be loan products (mortgage loans, deposit / deposit loans), receipts (demand deposits, savings deposits, derivatives).

The object type relation structure (structure for each object type) refers to a tree structure in which relationships among object types are expressed in a hierarchical hierarchy. Therefore, each of the nodes constituting the tree structure may be an object type. For example, in an insurance product, a representative product includes a product, a product includes a main contract and a special contract, and the main contract and the special contract include collateral, respectively.

3 is a block diagram showing a configuration of an embodiment of a merchandise management system using BRMS. The merchandise management system according to the present invention includes a merchandise management module 300, a merchandise management system repository 330, and a business rule management system BRMS, 350).

The product management module 300 includes an object type management unit 310, an object type structure management unit 315, a metamodel management unit 320, an object management unit 325, an object structure management unit 330, and a metadata management unit 335 .

The goods management system storage 330 includes a management data storage unit 332, a metamodel storage unit 334, and a metadata storage unit 336. Also, the goods management repository 330 may store management data, meta model information, and meta data in one storage medium physically without having separate storage units for management data, meta model information, and meta data.

The business rule management system (BRMS) 350 includes a business rule engine (BRE) 352, a rule management unit 354, and a rule storage unit 356.

The object type management unit 310 generates and manages object types. Managing the object type includes registering, modifying, deleting and querying the object type. When the object type management unit 310 determines that an object type that a single object can have a plurality of parent objects in the object type relationship structure is a pool, pool type object to create a relationship object, which can be used when setting up a management item associated with the pool.

The object type structure management unit 315 refers to a hierarchical relationship between object types in a tree structure, and generates and manages the structure between the object types. Managing the object type structure includes registering, modifying, deleting and querying the object type structure.

The meta model management unit 320 generates and manages a meta model for each object type. The meta-model for each object type includes an item that is a management factor of the object type for each of the object types and an attribute that indicates the property of the item. Managing the meta-model for each object type includes registering, modifying, deleting, and querying the meta model. The attribute may include a data property indicating whether the value of the item has a single value, a plurality of values, or a value of a specific range, and a data property indicating whether the item is displayed in a text form or a combo box And a shape characteristic displayed on a screen such as a display object. The metamodel management unit 330 assigns the location of the repository where the value of the item is stored according to the size of the stored data, and shares the same with each object type.

The object management unit 325 generates and manages objects corresponding to the goods serviced by the customer for each object type, with respect to the object type. Managing objects for each object type includes registering, modifying, deleting, and querying an object for each object type. Then, the object management unit 325 copies the metadata of the existing object and the upper and lower node structures to create a new object, and only modifies the metadata through the metadata and structure copy or copies the structure of the existing product, And adds the necessary sub-objects to create a new product.

The object structure management unit 330 creates and manages the top-bottom relationship structure of the objects by combining the object structure and the object structure. Managing the object structure includes registering, modifying, deleting and querying the object structure.

Then, the object structure management unit 330 generates the upper and lower relationships of the tree structure by dragging and dropping the generated objects, and the object other than the pool is created in the sub structure by pool division The creation of the subordinate object structure in the tree structure is controlled so that the relation object can not be used. If the relation object exists, the relation object is generated using the relation object code in which the upper and lower order object codes are combined.

The meta data management unit 335 generates and manages meta data for each object by combining the object type meta model and the objects. Managing the meta data includes registering, modifying, deleting and querying the meta data.

The meta data management unit 335 allows the attributes of the items defined in the meta model management to be included in the user interface screen of the product management system. Even if the meta model is changed or added, the user interface screen is not changed, The data input by the user is stored in a repository designated by the meta model, and a single value, a multiple value, and a range value can be processed in one screen, and a rule can be connected to the value.

The metadata management unit 335 also requests the rule management unit 354 to generate a rule and the rule management unit 354 generates a rule and stores the rule in the rule storage unit 356. The rule management unit 354 generates a rule code and stores the rule code in the merchandise management system storage 330, including the rule code, in the metadata.

The object structure management unit 330 provides a product list based on the top-bottom relationship structure of objects for each object type to a business program (a central system) that provides a service to a customer, and the metadata management unit 335, And provides meta model information and meta data information about the selected product.

The management data storage unit 342 stores product management data including a top-bottom relationship structure of objects for each object type generated by the object structure management unit 330. [ The meta model storage unit 344 stores meta model information for each object type generated by the meta model management unit 320. [ The metadata storage unit 346 stores metadata generated by the metadata management unit 335.

A rule storage unit 356 stores business rules necessary for product management. A rule management unit 354 manages business rules necessary for product management such as creation, modification, and deletion of the business rules. The business rule engine (BRE) 352 reads the rules stored in the rule storage unit 356 and interprets and executes them.

When the business rule engine (BRE) 352 receives a service rule for a product management data corresponding to a top-bottom relationship structure of objects generated by the object structure management unit 330 from a business program 390 of the main system, Reads the rules from the storage unit 356 and analyzes the goods, reads the goods management data from the goods management system storage unit 340, and provides the goods management data to the business program 380. When the business rule engine (BRE) 352 receives a metadata service rule call corresponding to the meta data from the work program 390 of the mission-critical service system, the business rule engine (BRE) 352 reads the rule from the rule storage unit 356, Reads the metadata from the repository 340 and provides it to the business program 390.

When the business rule engine (BRE) 352 receives a metadata service rule call corresponding to the meta data from the business program 390 of the mission service system, the business rule engine (BRE) 352 reads the rule from the rule storage unit 356, Reads the meta data from the storage 330, analyzes and executes the rule code if the read metadata is a rule code, and delivers data matching the input condition to the business program 390. [

FIG. 4 is a block diagram illustrating a configuration of providing a meta model and a metadata service based on a BRMS (Business Rule Management System) according to the present invention. The merchandise management system 400, the BRMS 450, and a time system service system 480.

The product management system 400 according to an embodiment of the present invention includes an object type management unit 402, an object type structure management unit 404, an object management unit 406, an object structure management unit 408, a metamodel management unit 412, The metadata management unit 422, the metadata batch management unit 424, the history management unit 432, the object comparison unit 434, the approval / transfer unit 436, the usage rule information inquiry unit 438, (440). The goods management system storage unit 440 includes a management data storage unit 442, a metamodel storage unit 444, and a metadata storage unit 446.

The BRMS 450 includes a BRE 460 and the BRE 460 includes a goods management data service unit 462 and a goods management system metadata service unit 464.

The time-of-business system 480 includes a BRMS API 485, work programs 492, 494, and 496.

The object type management unit 402 will be described.

An object type can be represented by a tree structure, which is called a type relation structure or a type structure. Object detail type refers to the detailed classification of the customer's products and is mainly used in insurance and card business.

The object type management unit 402 enables the product configuration information classified by the customer company to be registered in the product management system.

The object type structure management unit 404 will be described below.

First, the object type relation structure is a tree form of the upper and lower hierarchical structures according to the inclusion relation of object types. For example, as shown in FIG. 5, in an insurance product, a representative product includes a product, a product includes a main contract and a special contract, and the main contract and the special contract include collateral, respectively.

FIG. 5 shows an example of the type relationship structure of the insurance industry. Referring to FIG. 5, the object type in the type relationship structure includes a representative product 510, a product 520, a main contract 530, a special contract 540, and a collateral 550.

The representative product (510) is the unit of the insurance product reported by the insurance company to the FSS. The product (520) is the unit product that the insurance company subdivides the unit reported to the FSS and sells to the actual customer. The main contract (530) is the main guarantees of the insurance unit's sales unit products, and the special insurance (540) is the additional guarantee of the insurance unit's sales unit products.

And the collateral (550) is the standard that separates the details guaranteed by the sales unit products of the insurance company from the management aspect of the company. For example, if the main contract 530 guarantees the death of a holiday traffic accident, the collateral 550 is managed in three ways: death, traffic accident death, and holiday traffic accident death. This will be used as insurance payment, statistics, and new product releases.

Pool refers to the type of object in which an object can have multiple ancestor objects (which does not describe the concept of a general pool and describes the concept of a pool in a product management system using BRMS).

For example, in the example of the structure-based example (insurance industry) reference of FIG. 5, the product 520 that creates a relationship under the representative product 510 is no longer associated with another representative product 510 I can not make a relationship. However, the Reward (540) under Item 520 can relate to any Item as a Pool.

The commodity-main contract 522, the commodity-specific contract 524, the main contract-collateral 532 and the contract-specific collateral 534 are not object types managed by the actual insurance company, and the commodity management system using the BRMS according to the present invention In the present invention, the commodity-main contract 522, the commodity-specific contract 524, the main contract drug collateral 532 and the special contract collateral 534 are referred to as a "relationship object type". In the present invention, the "relationship object type" is an object type that can be generated when a Pool object makes a relation with a parent object under the relationship structure of object types.

And the "Pool object" does not change the item value that it has in relation with any parent object by its nature. For this reason, the relationship object type is used to manage the values that must be changed when parent and pool objects are related.

The object type structure management unit 404 registers and manages the upper and lower relationships of the object types, and is controlled so as not to create an unregistered relationship in the object type relationship (type) structure management in object creation and object structure creation

The meta model management unit 412 will be described.

The meta-model is a term having a limited meaning used in the merchandise management system using the BRMS according to the present invention. It manages the item information of each object for product management and stores the identifier and attribute (data type, value type , Storage area type, value area information of a repository, etc.).

Item refers to a management factor managed for each object. The property refers to various characteristic information such as a data characteristic, a characteristic to be displayed on a screen, and the like, and the information is managed by the attribute. A single is an item type that can have a single value, and a multiple is an item type that can have multiple values. A range is an item type that can have a start value and an end value.

The metamodel management unit 412 defines an item to be used for each object type and manages the attribute of the defined item.

The meta model managing unit 412 automatically assigns the location of the storage where the value of the corresponding item should be stored, according to the size of the stored data, and shares the location of the storage with respect to each object type. The location of the automatically assigned repository is stored in the future location, and when the user requests, the repository information is read from the metamodel, and the value is found and transmitted to the user.

6 shows metamodel (attribute) information managed by the metamodel management unit 412. FIG. Attributes include item name, item alias, data type, screen type, value type, column type, and column 1. The item name is the name of the item used in each type, the item alias is the English name of the item, and the data type has single, multiple, and range valid values. The screen type is a type that appears on the user interface screen, and the value type has a valid value of a character type or a numeric type. The column type has valid values of Small, Middle, and Large, and column 1 represents the location information of the repository according to the column type and is allocated automatically by the system.

FIG. 7 shows an example in which meta model information is defined in the insurance industry. Referring to FIG. 7, the main contract and special agreement represent the object type, and the main contract and the special contract which are the object types are referred to as metamodel (attribute) information, that is, item name, item alias, data type, screen type, And column 1.

FIG. 8 shows a process flow chart according to functions in the meta model management unit 412. FIG. First, an item is registered (S800), and the meta information is registered (S810). Meta information registration is shown in detail in Fig. If the column type is small, the small capacity storage is searched (S830). If the column type is middle, the medium capacity storage is searched (S840). If the column type is large, (S860). When the repository search is completed according to the column type, the meta information is stored (S860)

FIG. 9 shows an example of metadata storage according to a metamodel (attribute), and shows actual metadata storage according to metamodel store information.

When the object type is the main contract, the object name is the driver's insurance and the student insurance. In the storage CHAR01, the main contractor age and the jugging age are stored as the legacy age classification code, and the planned CHAR02 stores the planned interest rate. If the object type is a special case, the object name has the real loss medical expense ration (renewal type) and the traffic accident disorder ration, CHAR01 stores the existence of the lost goods, and CHAR02 stores the renewal period code. Thus, the repository CHAR01 and CHAR02 are logically shared between the main contract and the special contract.

The object management unit 406 will be described.

The object management unit 406 creates an object to be actually used for each object type, and can create a new object or create a new object by copying an existing object.

The object copy function includes a copy structure function. This object copy function is a method that customer's company analyzes and analyzes the pros and cons of existing products rather than develops and sells completely new products. In this method, only the changed metadata is copied through object copy, After copying the existing product structure, it is possible to create a new product by simply deleting unnecessary sub-objects and adding a sub-object to be added, and it is immediately reflected in the operating system so that new products can be released in a short time.

FIG. 10 shows an example of object generation for each type in the insurance industry. FIG. 11 is a flowchart showing the object management for each object type in the object management unit 406. FIG. (S1110). If it is determined to copy the object, the object is copied (S1110) and the metadata is copied (S1120). Then, it is checked whether or not the object structure is copied (S1130). If the object structure is decided to be copied, the object structure is copied (S1140). If the object is not copied, an object is created (S1150)

The object structure management unit 408 will be described.

The object structure management unit 408 generates a hierarchical relationship of the generated objects, and can easily create a structure by dragging and dropping the generated objects. In addition, by controlling the generation of the sub-object structure by the "Pool classification" defined by the object type structure management unit 404, it is possible to prevent an object other than the Pool from being duplicatively created in the sub structure. And a relational object is generated using the relational object code in which codes are combined.

FIG. 12 shows an example of object structure creation in the insurance industry, and includes object structure creation and relationship object creation. 13 is a flowchart showing that the object structure management unit 408 creates an object structure. 13, it is checked whether the object name and code are overlapped (S1300). If not, it is checked whether the object structure is duplicated (S1310). If the object name and code are overlapped, it is checked whether the object is a pool (S1320) (S1330). If the object name and the code are overlapped, the object structure is created as an error (S1350). If the object name and the code are overlapped, the object structure is created as an error (S1350)

The metadata management unit 422 will be described

Metadata refers to the data (value) stored in the storage value area defined in the metamodel, which is a term having a limited meaning used in the merchandise management system using the BRMS according to the present invention.

BRE (Business Rule Engine) is a rule engine that reads, interprets and executes rules stored in BRMS.

The screen is composed by the attributes defined in the metamodel management. Even if a defined metamodel is changed or an additional item occurs, the change of the user interface screen does not occur but is immediately applied to the screen. The data entered by the user is stored in the repository designated by the metamodel. Single values, multiple values, and range values can be processed in one screen, and rules can be linked to values. The metadata of the relationship object can also be processed in one screen.

FIG. 14 shows an example of metadata management by object type in the insurance industry.

In the product management system using BRMS, the rule (rule) can be stored rather than the value is stored in the meta data. When the meta data in which the rule is stored is requested in the business program, the rule (rule) Interpreted and executed, and the executed result is returned to the business program.

FIG. 15 shows an example in which a rule is applied in a merchandise management system using BRMS.

Referring to FIG. 15, it can be seen that a customer who wants to receive a credit returns an amount corresponding to a credit value of a different value to a business program depending on the customer's business type.

This function is available only in the BRMS-based product management system. In the legacy method or the parameter driven method, only the standardized (fixed) value is returned, whereas the BRMS-based product management system uses the BRMS It has the ability to return various values according to the technology, and has a breakthrough technology

The metadata batch management section 424 will be described.

The metadata batch management unit 424 performs batch copy, condition search, and modification. Due to the nature of work, copying objects is often done, so if one object needs to be modified, the value of the object before copying may have to be changed. In this case, you have to open multiple objects repeatedly and modify them one by one.

In order to solve such a problem, the product management system using the BRMS according to the present invention provides a batch metadata management function.

First, the object items are copied in a batch. It is a function that changes the item value of one object to be modified and copies the changed item value to the object to be corrected. Select the item to be copied, specify the original object, specify the object to be copied, and execute the copy

FIG. 16 shows an example of collective copying during batch management of metadata in the insurance industry.

Second, the object item condition is retrieved and modified. It is a function that can inquire the object corresponding to the query condition and collectively modify it in the metadata. View and select the items to modify in the object type. When a query condition is entered and inquired, the list of objects matching the query condition and the selected item are inquired. Modify and save the values you want from the list displayed

FIG. 17 shows an example of conditional retrieval and modification during batch management of metadata in the insurance industry.

The object comparison unit 434 will be described.

The object comparing unit 434 compares the structures of the objects and compares the items. In general, when the object is copied and created and the metadata is changed or the sub-object is changed, it is necessary to check what form the structure or value of the previous product as a copy source and the product after copying has changed.

The object comparison unit 434 compares the structure of the object registered in the goods management system and the meta data value of the object. The object structure and the metadata value comparison in the object comparison unit 434 are used as data for analysis of the change impact. In the merchandise management system using the BRMS according to the present invention, a total of three kinds of change impact analysis related functions are provided.

In addition, there are differences by customer, but if more than 270 meta-models are used in many cases by type and if 270 items are compared in metadata value comparison, the efficiency of business becomes poor. For this purpose, the meta data value comparison function provides a function to search only different values.

FIG. 18 shows an example of comparing object structures among objects in the object comparison unit 434. FIG. 19 shows an example of comparing items among objects in the object comparison unit 434.

The history management unit 432 will be described.

The history management unit 432 is another function for analyzing the change impact, and provides a function of managing and viewing the change history of objects, metamodels, and metadata managed in the product management system and the escape history transferred to the parent server do.

FIG. 20 shows an example of managing history of changes of objects, meta models, and meta data in the history management unit 432. FIG. FIG. 21 shows an example of managing the history of the objects, the meta model, and the metadata in the history management unit 432. FIG.

The use rule information inquiry unit 438 will be described.

As the third part of the change impact analysis, the product management system can use rules (rules) in metadata, and one rule can be used in various objects. The use rule information inquiry unit 438 provides a full attribute rule inquiry and an attribute rule inquiry function for each item, and inquires the rules used in the metadata to identify which rule is being used in which item. This task helps users to decide whether to modify a particular rule, to identify problems that may occur due to modification, and to decide whether to modify the rule or to create a new rule by copying.

FIG. 22 shows an example of inquiring the entire attribute rule information by the use rule information inquiry unit 438. FIG. 23 shows an example of inquiry of attribute rule information by item in the use rule information inquiry unit 438. [

The approval / release unit 436 will be described.

Approval / release includes request for approval, approval / release, transfer of approval data, and immediate transfer. The BRMS-based merchandise management system has its own approval function through the approval / transfer department 436.

The approval / transfer department 436 is configured so that the user can request approval from the upper decision maker for the details of the product created and changed at the product development stage, and the approval person can approve or reject the product using the product management system. Provides the ability to process real-time migration to the upper server or real server for completed transactions.

It also includes an administrator-only immediate transfer function that does not require approval procedures to prepare for emergencies. Immediate transfer function allows the authorized product management system administrator to transfer data to the upper server or the production server in real time at the request of the product developer and the top-level approval authority by the customer's R & R (Role and Responsibilities).

Fig. 24 shows a user interface screen requesting approval provided by the approval / release unit 436. Fig. Fig. 25 shows an approval / rejection screen provided by the approval / transfer unit 436. Fig. 26 shows an approval data escape screen provided by the approval / Fig. 27 shows an immediate transfer screen provided by the approval / transfer part 436. Fig.

30 shows the transfer of the approved data in the merchandise management system using the BRMS according to the present invention. The approved data transfer in the present invention is performed between the development server 3000 and the verification server 3040 and between the verification server 3040 and the operation server 3070. This transfer of the approved data is performed between the development server 3000 and the verification server 3040 by creating object types 3002 and 3042, object type inter-structures 3004 and 3044, object metamodels 3006 and 3046, Generation of objects 3008 and 3048 and the structure of objects 3012 and 3052 for each type under the inter-type structure are performed for the metadata management of objects 3014 and 3054 and BRMSs 3020 and 3060.

The transfer of such approved data may also include object type generation 3042 and 3072, object type inter-structure 3044 and 3074, object metamodels 3046 and 3076, Object generation 3048 and 3078, type structure 3052 and 3082 of objects under the inter-type structure, object metadata management 3054 and 3084 and BRMS 3060 and 3080 are also performed. When the approval and transfer are made to the operation server in this way, it is finally transmitted to the system 3090 of the central system.

On the other hand, the commodity data service using the BRMS will be described.

The service of the present invention includes a function of the product management system to transfer data stored in the repository to a business program. In the business program, request the product data using the service, receive the result, and process the business program

BRE is an abbreviation of Business Rule Engine. It is a rule engine that reads, interprets and executes rules stored in BRMS.

There are two types of commodity data services installed in BRMS: commodity management data service and commodity management system metadata service. The commodity management data service is a service that transfers data not related to a metamodel such as object type, object, object structure, and the like managed by the commodity management system to the period system business system. It refers to the service that is delivered to the business system of the periodical system as a request.

All services of BRMS-based product management system are serviced using BRE (Business Rule Engine) embedded in product management system.

This function allows the service to be immediately applied without changing the product management system and the periodical program even if the metamodel is changed (added, deleted, modified) or the product management data is changed.

FIG. 28 is a flowchart of a goods data service using BRMS. Referring to FIG. 28, when a service request is received from a business program (S2800), the meta model is read (S2810) and the metadata is read (S2820). Whether or not a rule exists is checked (S2830) If there is no rule, it is checked whether the value is a multiple value (S2850). If the value is a multiple value, multiple values are read (S2860) (S2880). The result thus obtained is returned to the business program (S2890)

31 shows the flow of services of the product management system using BRMS in the insurance industry. The method of retrieving the data of the product management system in the periodical work program is as follows. In the periodical work program, the service rule (rule) of the BRMS is called by using the API provided by the product management system, and the service rule It reads the management data, meta model, and meta data of the management system and delivers the requested data to the task program.

Referring to FIG. 31, in a typical workflow for making an insurance subscription 3100 with a customer in a time-based service system, customer information is first input 3110, a product list is inquired 3120, and a product is selected. 3130). Then, the goods item information is inquired (3140), the goods item is inputted (3150), and subscription (3160) is performed.

Here, at the item item inquiry 3120, the goods list 3126 is obtained from the goods management system using the BRMS according to the present invention. That is, the service system of the period system calls the service rule (rule) of the BRMS using API 3122 provided by the product management system, and the service rule (rule) is read and interpreted in the BRE to read the product management data of the product management system The data is transmitted to the work program of the periodical system.

Also, when the item item information is inquired (3140), the item item information 3144 is also obtained from the goods management system using the BRMS according to the present invention. That is, the business system of the service system calls the service rule (rule) of the BRMS using the API 3122 provided by the product management system, and the service rule (rule) is read and interpreted in the BRE, The metadata is read and the data is transmitted to the work program of the periodical business system.

The goods list 3126 is provided by the object structure unit 3105, and the item item information is provided by the metadata management unit 3106. [ The object structure 3105 is generated and managed by combining the inter-type object structure 3102 and the type-specific object 3104. The meta data management 3106 is generated and managed by combining the object meta model 3103 and the type-specific object generation 3104. The inter-type structure 3102, the metamodel 3103, and the object creation 3104 are based on an object type 3102.

FIG. 29 is a flowchart showing an embodiment of a product management method of a product management system using a BRMS according to the present invention.

29, when a product to be managed by the goods management system is an object, an object type necessary for managing the object is created and managed (S2900). The object type is one of the object types A relation object which is an object that is created when an object of a pool object has a plurality of parent objects and a pool object has a relation of an upper object and a lower pool object, And is used to set management items associated with the pool.

The generated object type is set as a node of the tree structure, and the hierarchical relationship between the generated object types is created and managed as an object type relationship structure represented by a tree structure (S2910)

For each of the generated object types, a metamodel for each object type is created and managed, which includes an item that is a management factor of the object type and an attribute that indicates the property of the item. (S2920) . The data characteristic indicates whether the value of the item has one value, has a plurality of values, or has a specific range value. The shape characteristic may be displayed in a text form, a combo box, or a check box form And the like displayed on the screen. The location of the repository in which the value of the property is stored is assigned by the product management system according to the size of the stored data, and the location of the repository can be shared according to the object type.

In the created object type, objects corresponding to the goods to be served to the customer are generated and managed according to the object type (S2930). In the object creation, the metadata and the structure of the existing object are copied to create a new object, It is possible to create a new product by only modifying metadata through copy of data and structure or by copying the structure of an existing product and then deleting unnecessary sub-objects and adding necessary sub-objects.

The upper and lower relationship structure creation of the objects is performed by dragging and dropping the created object. [0216] In step S2940, the object structure is created and managed by combining the generated object structure with the generated object, And controls creation of a sub-object in the tree structure so that an object other than a pool can not be duplicated in the sub-structure due to a pool division. If there is a relation object, A relation object is created using a combination of objects.

The generated meta-model for each object type and the generated objects for each object type are combined to generate and manage metadata for each object type (S2950). The user interface screen for metadata creation includes a meta model Even if the metamodel is changed or added, the user interface screen of the product management system is directly applied to the user interface screen, and the data input by the user is stored in the storage specified by the metamodel, It is possible to process single values, multiple values, and range values and to link rules to values.

It is possible to provide a list of goods by the top-bottom relationship structure of the objects by object type generated in the step S2940 to the business program of the main system providing the service to the customer (S2960). In other words, The business rule engine BRE reads and interprets the rule from a rule storage unit provided in the business rule management system BRMS to manage the product management The product management data can be read from the storage of the system and provided to the business program.

If the merchandise is selected from the merchandise list, the metadata about the selected merchandise is provided using the metadata generated in step S2950 (S2970). In other words, metadata Upon receiving the data service rule call, the business rule engine BRE reads and analyzes the rule from a rule storage unit provided in the business rule management system (BRMS), reads the metadata from the store of the product management system, Can be provided to the program.

When the business rule engine (BRE) 352 receives a metadata service rule call corresponding to the meta data from the business program 290 of the service system of the service system, the business rule engine (BRE) 352 reads the rule from the role storage unit 356, If the read metadata is a rule code, a rule corresponding to the rule code is read from a rule storage unit provided in the business rule management system (BRMS) Interprets and executes the data, and transmits data corresponding to the input conditions to the business program 290.

Hereinafter, an overall characteristic of the present invention will be described as an example in comparison with the prior art.

32 shows a conventional product management flow. Referring to FIG. 32, it is conventionally shown that the business program 3230 adds the update information 3232 and changes the planned interest rate 3234 for each commodity code. As shown in FIG. 32, conventionally, in order to change or update the planned rate for each product code (3234), it is necessary to add 3232 the update or not and add / modify 3234 the planned rate in the business program 3230 . In the product management screen, whether to update or not is also displayed, and in the database 3250, an update item (3252) is added.

33 shows a goods management system using BRMS. In order to add the update information 3312 in the business program 3300, the product management system 3330 using the BRMS according to the present invention is used. That is, the addition of the update information 3312 in the business program 3300 may be performed by adding the update information 3366 to the meta model 3362 and registering the update data corresponding to the update information 3366 in the metadata 3364 .

In addition, the planned rate change 3349 for each commodity code changes the content of the predetermined rate rule 3347 according to the commodity code registered in the rule storage 3346 to the scheduled rate rule 3349 according to the new commodity code using the BRMS (3320) at the request of the business program (3300), and interprets and executes the scheduled interest rate rule (3349) based on the modified commodity code and outputs the result to the business program (3320) And returns.

Therefore, when a management item is added or deleted due to the creation of a product using the meta model, the modification of the physical model is not accompanied by the modification of the physical model. By minimizing the modification of the program, it is possible to dramatically shorten the product launch period. You can maximize the profit of your selling company. Also, instead of returning only formal quantitative values, Rule can be applied to return values to return variable values according to the conditions, so that the desired values are reflected to the work without modification of the program and applied immediately can do.

The present invention can be embodied as a computer readable code on a computer-readable recording medium (including all devices having an information processing function). A computer-readable recording medium includes all kinds of recording apparatuses in which data that can be read by a computer system is stored. Examples of computer-readable recording devices include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and the like.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is evident that many alternatives, modifications and variations will be apparent to those skilled in the art. Accordingly, the true scope of the present invention should be determined by the technical idea of the appended claims.

310: Object type management unit 315: Object type structure management unit
320: meta model management unit 325:
330: Object structure management unit 335: Metadata management unit
340: goods management system storage 342: management data storage unit
344: Meta model storage unit 346: Meta data storage unit
350: BRMS 352: BRE
354: a rule management unit 356: a rule storage unit
400: goods management system 402: object type management unit
404: Object type structure management unit 406:
408: Object structure management unit 412: Metamodel management unit
422: Metadata management unit 424: Metadata management unit
432: history management unit 434: object comparison unit
436: Approval / Relay Unit 438: Use Rule Information Query Unit
440: goods management system storage 442: management data storage unit
444: Meta model storage unit 446: Meta data storage unit
450: BRMS 460: BRE
462: commodity management data service department
464: Product Management System Metadata Service Department
480: Lifecycle business system 485: BRMS API
492, 494, 496: Work program

Claims

(a) generating an object type necessary for managing the object, when a product to be managed by the product management system is an object,
(b) setting the generated object type as a node of a tree structure, and creating a hierarchical relationship between the generated object types as an object type relationship structure represented by a tree structure;
(c) generating, for each of the generated object types, a metamodel for each object type, the object type being a management factor of the object type and an attribute indicating a property of the item;
(d) generating objects corresponding to goods to be served to customers for each object type, with respect to the generated object types;
(e) creating a relation structure between the generated object types and the created object to create an upper and lower relationship structure of the objects; And
(f) generating meta data for each object by combining the generated meta-model for each object type and the generated objects for each object type,
The business rule engine BRE receives a business rule management message from the business rule management system BRMS when receiving a service rule for product management data corresponding to the hierarchical structure of the objects generated in the step (e) Reads out and analyzes the rule from a rule storage unit provided in the product management system, reads product management data from a store of the product management system and provides the product to the business program,
The business rule engine (BRE) receives the metadata service rule corresponding to the metadata generated in the step (f) from the business program of the mission-critical business system, and the business rule engine (BRE) Reading out and analyzing the rule from the storage unit, reading meta data from a repository of the merchandise management system, and providing the meta data to a business program.

The method according to claim 1,
The store of the goods management system stores metadata about the goods, the metadata includes a rule code,
If the metadata is a rule code as a result of the metadata of the goods management system being read by the business rule engine BRE, the business rule engine BRE is provided in the business rule management system (BRMS) And reading and analyzing a rule corresponding to the rule code from a rule storage unit and transmitting data corresponding to the input condition to the business program.

An object type management unit configured to create and manage the object type when a product to be managed is an object and each node classified into a tree structure for managing the object is an object type;
An object type structure management unit for creating and managing a structure between the object types when an object type structure is represented by a tree structure of a hierarchical relationship between the object types;
A metamodel management unit for each object type to generate and manage a metamodel for each object type, the metamodel comprising an item that is a management factor of the object type and an attribute that indicates a property of the item;
An object management unit for generating and managing objects corresponding to goods to be provided to customers for each object type, with respect to the generated object types;
An object structure management unit for creating and managing a top-bottom relationship structure of objects by combining the generated object structure with the generated object structure;
A meta data manager for generating and managing meta data for each object by combining the generated meta model for each object type with the generated objects;
Product management data including an upper-lower-level relationship structure of objects for each object type generated by the object structure management unit, metamodel information for each object type generated by the metamodel management unit, and a product storing metadata generated by the metadata management unit Managed system repository; And
A business rule management system (BRE) having a rule storage unit for storing business rules, a rule management unit for managing the business rules, and a business rule engine (BRE) for reading and interpreting the rules stored in the rule storage unit BRMS)
The business rule engine (BRE)
When receiving a service rule for a product management data corresponding to an upper-lower-level relationship structure of objects generated by the object structure management unit from a business program of a main system, reading the rule from the role storage unit, Reads the goods management data from the store and provides it to the business program,
When the metadata service rule corresponding to the meta data is received from the business program of the mission-critical business system, the rule is read from the role storage unit and interpreted, and the meta data is read from the store of the merchandise management system, Product management system using BRMS.

The apparatus of claim 3, wherein the metadata management unit
The rule management unit requests the rule management unit to generate a rule, stores the generated rule in the rule storage unit, and transmits the rule code corresponding to the rule, and stores the rule code in the metadata, And stores it in a department.

5. The method of claim 4, wherein the business rule engine (BRE)
And reading the metadata from the repository of the merchandise management system by reading and analyzing the rule from the role storage unit when receiving a metadata service rule call corresponding to the meta data from the business program of the mission system business system, And if it is a rule code, reads a rule corresponding to the rule code from a rule storage unit provided in the business rule management system (BRMS), analyzes and executes the rule, and delivers data matching the input condition to the business program Product management system using BRMS.

A computer-readable recording medium storing a program for causing a computer to execute the invention according to claim 1 or 2.