KR100813013B1 - Odx-based frame work for software development - Google Patents

Abstract

A transaction processing software framework using ODX(Operation Document eXchange) data is provided to facilitate business modification or extension through combination of unit services and batch application of the related services by linking and processing transactions based on the unit service. A client module(10) converts data received from a user into ODX data, and transfers the ODX data to a server module. The server module includes an application service module(40) formed for respective unit services, and a transaction controlling module(30) processing a transaction request of a channel managing module(20) and a response of the application service module. The transaction controlling module operates the application service module according to the ODX data and transfers a processing result to the channel managing module. The ODX data is structured to separately point transaction data and a control command. A connection structure between the ODX data has a hierarchical structure in which one transaction includes more than one unit transaction and the unit transaction includes more than one unit service, and is formed to process a plurality of data with one control command and generate various transactions with combination of the unit services.

Description

Transaction processing software framework using ODX data {ODX-based Frame work for software development}

1 is a configuration example of a framework according to the present invention

2 is a diagram illustrating a hierarchical structure of ODX data according to the present invention.

3 is an exemplary diagram of OPERATION_CONTROL of ODX data according to the present invention.

4 is an exemplary view of OPERATION_DETAIL of ODX data according to the present invention.

5 illustrates an example of TRANSACTION_CONTROL of ODX data according to the present invention.

6 is an exemplary diagram of Tx_CONTROL of ODX data according to the present invention.

7 is an exemplary view of Service_CONTROL of ODX data according to the present invention.

<Description of Major Symbols in Drawing>

10: client module 20: channel management module

30: transaction control module 40: application service module

50: DB

The present invention relates to a software framework for transaction processing, and more specifically, to support transaction processing of an ODX data format based on a client module which is a user terminal, an application service module that processes a transaction, a transaction channel management module, and a database. It's about a software framework.

With the development of information technology, the software for transaction processing is being developed to integrate the resources distributed in the network base such as internet banking, ERP, CRM, ITSM, etc.

However, the conventional transaction processing software develops a separate business logic, data set, and transaction screen for a predictable transaction, and when the transaction occurs, a closed structure in which the business logic is executed by the data set input through the transaction screen. Provided.

개의 비지니스 로직, 데이타 셋 및 거래화면을 개발해야 한다는 것이다.In other words, if there are n unit services,

You have to develop three business logic, data sets and transaction screens.

Such a conventional implementation method has a problem in that it is difficult to change or expand the software due to an increase in development period and cost, and to configure an inefficient system because the flexibility of the system or the compatibility between other systems cannot be expected.

The present invention was created to solve the above-mentioned problems of the prior art, and can be easily changed or expanded through a unit service-based transaction interworking process through a combination of unit services and batch application of data on related services. It is intended to provide a software framework.

In order to solve the above technical problem, the present invention provides a client module which is a user terminal, an application service module for processing a transaction requested by the client module, a software including a channel management module and a database for performing a basic operation for transaction processing In the framework, the client module converts the data input by the user into ODX (Operation Document eXchange) data and transmits the data. The application service module is divided into a plurality of unit service logics, and the transaction of the channel management module is performed. And a transaction control module for processing a request and a response of the application service module, wherein the transaction control module drives an application service module according to ODX data and transmits a processing result to a channel management module. Is structured to separate transaction data and control commands, and the connection structure between ODX data is a hierarchical structure in which one transaction includes a plurality of unit transactions and a unit transaction includes a plurality of unit services. It provides a software framework that can be processed and configured to generate various transactions by combining unit services.

According to another aspect of the present invention, the ODX data is configured to allow preprocessing control commands and hash value designation so that the channel management module preferentially performs a preprocessing procedure for the client module to reconfirm the transaction data for the requested transaction. It also provides a software framework to verify the integrity of data verified by preprocessing procedures.

According to another feature of the present invention, the ODX data allows a reservation service control command specification of a transaction, and the transaction control module provides a software framework configured to execute a transaction, which is reserved and stored in a database, at a reserved time point. .

According to another feature of the present invention, the ODX data allows a payment service control command designation, and the transaction control module stores the transaction to be paid in a database and transmits the transaction data to the payer to execute the transaction when the payment is completed. Provide a software framework that is structured to allow

According to another feature of the present invention, the ODX data allows the specification of a Store And Forwarding (SAF) service control command, and the transaction control module stores a transaction for which SAF processing is requested in a database to execute after the pre-transaction is terminated. Provide a software framework that is structured to allow

According to another feature of the present invention, the ODX data provides a software framework, characterized in that it comprises a control command for transmitting the transaction data about the transaction processing result and the result before and after the transaction to the user.

According to another feature of the present invention, the ODX data gives a serial number to the preprocessing and the main processing, and the client module and the transaction control module can check the sequential increase of the serial number so that the double processing or randomly inserted transaction can be excluded. Provide a configured software framework.

According to another feature of the present invention, when the ODX data allows the specification of an encryption service control command and stores the ODX data in the DB for processing, the channel management module generates a password conversion table using a hash value and a master key value. It provides a software framework configured to encrypt and store passwords based on them, decrypt them at runtime, and delete and store them when logging after transaction processing.

According to another feature of the invention, the application service module provides a software framework, characterized in that consisting of a thin server (Thin Server).

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

1 is a diagram illustrating a system configuration according to the present invention, and includes a client module 10, a channel management module 20, a transaction control module 30, an application service module 40, and a DB 50.

The client module 10 is a device capable of requesting a transaction desired by a user such as a user PC, a PDA, a CA, various mobile devices, etc., and confirming the processing result. The client module 10 displays data input by the user through a transaction screen. It is converted into ODX (Operation Document eXchange) data and transmitted to the channel management module 20.

ODX (Operation Document eXchange) data according to the present invention is a hierarchical structure as shown in the example of FIG. 2 as XML data of a structure promised between modules, and is executed in the order of OPERATION-> TRANSACTION-> Tx-> SERVICE. This is processed.

The depth of the layer may vary depending on the degree of specific and combination of unit services.

One transaction required by the user is one OPERATION, which can be composed of CONTROL, DETAIL, TRANSACTION, and WORK.

Here, CONTROL is a control unit for OPERATION as shown in the example of FIG. 3 may include basic information such as date, serial number, user ID, approval information, and processing result.

Transaction data including the data entered by the user is sent back to the user to check the integrity of the contents for the safety of transactions. For this purpose, the ODX data allows the specification of preprocessing control commands and the channel management module 20 Recognizes the preprocessing control command of OPERATION_CONTROL before processing the transaction and performs user verification of the transaction data.

In addition, the ODX data contains a hash value to ensure that the original ODX data has not been modified during the preprocessing verification procedure.

At this time, OPERATION_CONTROL can prevent the double processing or random operation of the transaction by combining the serial number which is automatically increased sequentially in the order in which the preprocessing and the main processing occur.

In addition, if there are a plurality of transaction requests, the transaction control module 30 may accept a new transaction request and store it in the DB 50 and then execute it immediately after the previous transaction ends, even if the current transaction is not terminated. To this end, SAF (Store And Forwarding) control command is specified in OPERATION_CONTROL, which has the advantage of improving responsiveness.

DETAIL is a variable definition area for a user and an interface, and is used by redefining by command code type as shown in FIG.

The TRANSACTION may include CONTROL, PreTx, PreTx, Tx, and PostTx. As shown in FIG. 5, TRANSACTION_CONTROL is transaction information, reservation information, and payment information. May be included.

That is, the reservation or payment function can be easily implemented by including reservation or payment information about the content to be processed in Tx in the TRANSACTION_CONTROL.

In the case of reservation, transaction control module 30 stores the contents of Tx in DB 50 and executes Tx at the time of reservation.

In the case of payment, the transaction control module 30 stores the contents of Tx in the DB 50 and transmits the transaction data to the designated payer so that the payment is made, and then executes the corresponding Tx when the payment is completed.

According to the present invention, one TRANSACTION may include one or more Tx. When a plurality of Txs are included, one transaction may simultaneously execute, reserve, or renew a payment in a single operation. That is, it is possible to implement a mass processing function that can process a large number of transaction data at the same time with one control command of OPERATION_COTROL, which has the advantage that batch processing of data constructed by existing Excel work is possible.

When a plurality of Tx is executed as described above, the transaction control module stores the Tx in the DB 50 and executes each Tx.

At this time, it may be implemented to inform the user of the progress and processing result before and after the transaction processing, including a control command for transmitting the transaction data about the transaction processing result and the processing result to the user before and after Tx.

Conventionally, the result notification function is included in the Tx itself. Thus, when an error occurs during transaction processing, the notification of the processing result is not performed.

Therefore, the present invention includes PreTx and PostTx at the same level as Tx before and after Tx processing to detect the progress of Tx and normal or abnormal end of Tx to inform the user of the processing result to enhance the integrity of transaction processing. There are advantages to it.

Tx may include a CONTROL (control unit), a DETAIL (single transaction related user input data), SERVICE (service) and WORK (execution work area) as shown in FIG.

In this case, the SERVICE may also include a plurality of SERVICEs. The SERVICE may include a CONTROL (control unit), a DETAIL (service related user input data), and a WORK (execution work area) as shown in FIG.

As described above, the ODX data according to the present invention can be divided into a service of a minimum unit which can no longer be divided into transactions, and can be implemented as a unit service or a combination of these as necessary. It's very easy to change and expand.

The SERVICE indicates a unit service, and the Tx can be said to be a combination of unit services in the form of a transaction with one characteristic.

As described above, the ODX data structure is hierarchized as TRANSACTION and SERVICE between ODX data, and internally, transaction data and control commands are designated separately so as to exclude the interdependence of data and logic.

In addition, transaction data that can be commonly or proactively applied at the corresponding ODX data level is included in CONTROL and DETAIL, and data that is applied separately is included in COTROL and DETAIL of ODX data of subordinate subordinate classification. It is easy to set up and easy to enhance the integrity of transaction processing.

Therefore, data change can be applied to the related unit service collectively, and the universality of the unit service logic can be secured, thereby dramatically reducing the development cost of transaction processing software according to the user's request.

The client module 10 transmits the ODX data as described above to the channel management module 20, and the channel management module 20 performs a preprocessing procedure to ensure the integrity of the transaction data. In addition, the channel management module 20 performs session management, user management, authorization verification, encryption and decryption, certificate confirmation, payment information management, and screen information management.

In particular, in the case of encryption / decryption, the encryption command is assigned to the ODX data, and when the ODX data is stored in the DB for processing, the channel management module encrypts the password based on a password conversion table using a hash value and a master key value. After storing and decrypting it, it is decrypted when it is executed, and during the logging operation of the transaction control module after transaction processing, the password is deleted and stored.

 Transaction control module 30 controls the processing of the actual transaction based on the transaction data confirmed by the channel management module 20, which controls the operation of the application service module 40 including a plurality of unit service logic will be.

The application service module 40 processes a transaction using the data of the DB 50, and is divided into the logic of the minimum unit that can no longer be divided as described above, and includes a reservation, payment, and SAF service module.

When server expansion is needed due to the increase in transaction volume, the present invention is suitable to use a low-cost thin server that minimizes unnecessary functions because the unit service logic is simple, so the system throughput is maximized through thin server clustering. The cost can be minimized.

The DB 50 may be integrated or separated according to a service module and a processing environment.

The software framework using the ODX data structure according to the present invention maintains the association with other services and data even if only the unit service logic is implemented when developing a new service architecture, thereby dramatically improving the accuracy, reusability, and development productivity of the application service module. It can be improved.

In addition, the ODX data structure according to the present invention can easily implement the bulk processing, the combination of unit services, reservation and payment functions by separating the transaction data and the control command, and the components such as CONTROL, DETAIL, TRANSACTION (Tx, SERVICE), etc. Easy to operate bar has the advantage that can be utilized immediately for education or testing.

Claims (9)

In the software framework comprising a client module which is a user terminal, an application service module for processing a transaction requested by the client module, a channel management module for performing the basic work for transaction processing, and a database, The client module converts the data input by the user into ODX (Operation Document eXchange) data and transmits the same. The application service module is divided into a plurality of logic for each unit service, and further comprises a transaction control module for processing a transaction request and response of the application service module of the channel management module, The transaction control module drives the application service module according to the ODX data and transmits the processing result to the channel management module. The ODX data is structured to separately designate the transaction data and the control command, and the connection structure between the ODX data is one transaction. A software framework that includes more than one unit transaction, which is a hierarchical structure that includes one or more unit services, can process multiple data with a single control command, and is configured to generate various transactions by combining unit services. The method according to claim 1, wherein the ODX data is configured to allow preprocessing control commands and hash value designation so that the channel management module preferentially performs a preprocessing procedure for the client module to reconfirm the transaction data for the requested transaction. Software framework for verifying the integrity of data identified by preprocessing procedures. The software framework of claim 1, wherein the ODX data permits the specification of a reservation service control command for a transaction, and wherein the transaction control module is configured to execute a transaction that is reserved and stored in a database at a scheduled time. According to claim 1, The ODX data allows the payment service control command designation, the transaction control module stores the transaction to be paid in the database to send the transaction data to the payer to execute the transaction when the payment is completed Configured software framework. The method according to claim 1, wherein the ODX data allows the specification of a Store And Forwarding (SAF) service control command, and the transaction control module stores a transaction for which SAF processing is requested in a database so that it can be executed after the pre-transaction is terminated. Configured software framework. The software framework of claim 1, wherein the ODX data includes a control command for transmitting transaction data about whether the transaction is processed and a result of the processing before and after the transaction to the user. The software framework of claim 1, wherein the application service module comprises a thin server. The software of claim 2, wherein the ODX data assigns serial numbers to the preprocessing and the main processing, and the client module and the transaction control module confirm the sequential increase of the serial numbers so as to exclude double processing or randomly inserted transactions. Framework. The password management method according to claim 1 or 2, wherein the ODX data permits the specification of an encryption service control command, and when the ODX data is stored in the DB for processing, the channel management module uses a hash value and a master key value. A software framework configured to encrypt and store a password based on a conversion table, decrypt it at runtime, and delete and store the password when logging after transaction processing.

Images