KR101851256B1 - Method of testing contract, server performing the same and storage medium storing the same - Google Patents

Abstract

The present invention relates to a contract testing method, and a computer-executable contract testing method for testing a contract management agent, the method comprising: receiving a payment from a customer according to a period during a first period managed by the contract management agent; Generating contract condition test data by virtually generating a contract event generated during the second period and a payment event generated during the first period of the contract condition test data; To the contract management agent, and checking whether there is an abnormality in the contract. Therefore, it is possible to verify whether there is an abnormality in the contract related data.

Description

TECHNICAL FIELD [0001] The present invention relates to a contract testing method, a contract test server, and a recording medium storing the contract test server.

The present invention relates to a contract test technique, and more particularly, to a contract test method capable of verifying whether there is an abnormality in contract related data, a contract test server performing the contract test method, and a recording medium storing the same.

Generally, the company develops a product management system to make products in a timely manner and launch them, and tests the products. The test on the product can be performed by comparing the result obtained by processing the program actually used on the basis of the test data created by the auditor and the result of aggregating the data in advance. For example, insurance is a system in which many people who are at risk of the same kind of accidents in capitalist society form a common reserve asset by making money in advance, and an economic system in which an accidental person receives a property benefit, Data on non-arriving tasks such as maintenance and payments that occur after the sale are needed.

Korean Patent Laid-Open No. 10-2009-0079085 discloses a real-time dynamic insurance rate management method, a real-time dynamic insurance rate management system, and a real-time dynamic insurance rate management system that can apply a real-time dynamic insurance rate of a subscriber based on statistics collecting existing events and accident occurrence information Discloses an insurance rate management server. These technologies can enable real-time insurance rates to be applied according to the lifestyle of each subscriber, such as the movement of each subscriber, the place of visit, and the location of the time zone.

Korean Patent Laid-Open No. 10-2014-0081994 discloses an insurance product quality verification system that can verify the quality of an insurance product. This technology registers detailed test scenario information for verifying the insurance product and then accesses and inspects the product basic information and the product detailed information for the at least one insurance product selected by the manager from the insurance company server according to the test scenario detailed information, By inquiring, it is possible to automatically process product information verification for new products and revised products.

Korea Patent Publication No. 10-2009-0079085 Korean Patent Publication No. 10-2014-0081994

One embodiment of the present invention is to provide a contract testing method that can verify whether there is an abnormality in the contract related data.

An embodiment of the present invention is to provide a contract test method capable of generating virtual test data to test a contract condition. To this end, one embodiment of the present invention provides a contract test method capable of generating virtual test data according to a contract related event occurring during a specific period.

One embodiment of the present invention is to provide a contract test method capable of detecting the error data in the contract-related data based on the test data and ensuring the completeness of the contract-related data.

In one embodiment, the contract testing method is a computer-executable contract testing method for testing a contract management agent, the method comprising: receiving a payment from a customer for a first period of time managed by the contract management agent, Generating contract condition test data by virtually generating a contract event related to a contract event generated during the first period and a payment event generated during a first period of the contract condition test data; To the contract management agent, and checking whether there is an abnormality in the contract.

In one embodiment, receiving the contract terms for the contract may include receiving test data generation criteria for each contract type of the new contract, maintenance contract, and multi-contract.

The step of receiving the contract terms for the contract may include receiving subcontract conditions and subcontract condition elements according to the contract type of each of the new contract, maintenance contract and multi-contract. The step of receiving the contract condition for the contract may include checking whether the contract is a multi-contract based on the date of birth and gender of the customer associated with the contract.

The step of receiving the contract condition for the contract may include generating a customer care associate for the customer based on the customer's date of birth, sex, and contract date, and associating the customer management associator with the contract.

In one embodiment, the delivery event may include a first delivery event occurring in accordance with the period and a second delivery event occurring in addition to the period. The step of generating the contract condition test data may include the step of determining whether to terminate the contract according to the occurrence time of the second payment event.

The step of generating the contract condition test data may include determining a first contract related event based on the first payment event and a second contract related event based on the second payment event.

In one embodiment, generating the contract condition test data may include generating the contract condition test data based on the first and second payment events, the first and second contract related events. have.

The step of generating the contract condition test data may include checking whether the contract condition test data is consistent based on the test data generation criterion.

In one embodiment, the step of checking for anomalies of the contract may comprise generating a contract validation query for validating the existence of an anomaly in the contractual terms for the contract based on the contractual condition test data.

The step of checking for the abnormality of the contract may include the step of providing the contract validation query to the contract management agent to detect an error identification code for the contract. The step of checking for the abnormality of the contract may include analyzing the error identification code and updating the contract condition for the contract.

Among the embodiments, the contract testing server comprises a processor and a non-transitory computer readable storage medium for storing instructions that cause the processor to perform the following method: when the processor executes the instructions, A computer-executable contract testing method for testing an agent, the method comprising: receiving a payment from a customer according to a period during a first period managed by the contract management agent and receiving a contract term for a contract maintained during a second period; Generating a contract condition test data by virtually generating a payment event generated during the first period and a contract related event generated during the second period and providing the contract condition test data to the contract management agent, Check It includes.

Among the embodiments, a computer-readable recording medium on which a program for implementing the contract test method is recorded includes a computer-readable recording medium storing a program for implementing a computer-executable contract test method, The method comprising the steps of: receiving a payment from a customer according to a period during a first period managed by the contract management agent and receiving a contract condition for a contract maintained during a second period; Generating contract condition test data by virtually generating contract-related events generated during the second period, and providing the contract condition test data to the contract management agent to check whether there is an abnormality in the contract.

The contract test method according to an embodiment of the present invention can verify whether there is an abnormality in the contract related data.

The contract testing method according to an embodiment of the present invention can generate the virtual test data and test the contract condition. To this end, the contract test method according to an embodiment of the present invention can generate virtual test data according to a contract related event occurring during a specific period.

The contract testing method according to an embodiment of the present invention can detect the error data in the contract related data based on the test data to ensure the completeness of the contract related data.

1 is a block diagram illustrating a contract testing system in accordance with an embodiment of the present invention.
2 is a block diagram illustrating the contract testing server in FIG.
3 is a diagram showing the hardware configuration of the contract test server shown in FIG.
4 is a flowchart illustrating a contract test process performed in the contract test server shown in FIG.
5 is a diagram illustrating the type of contract received at the contract testing server in FIG.

The description of the present invention is merely an example for structural or functional explanation, and the scope of the present invention should not be construed as being limited by the embodiments described in the text. That is, the embodiments are to be construed as being variously embodied and having various forms, so that the scope of the present invention should be understood to include equivalents capable of realizing technical ideas. Also, the purpose or effect of the present invention should not be construed as limiting the scope of the present invention, since it does not mean that a specific embodiment should include all or only such effect.

Meanwhile, the meaning of the terms described in the present application should be understood as follows.

The terms "first "," second ", and the like are intended to distinguish one element from another, and the scope of the right should not be limited by these terms. For example, the first component may be referred to as a second component, and similarly, the second component may also be referred to as a first component.

It is to be understood that when an element is referred to as being "connected" to another element, it may be directly connected to the other element, but there may be other elements in between. On the other hand, when an element is referred to as being "directly connected" to another element, it should be understood that there are no other elements in between. On the other hand, other expressions that describe the relationship between components, such as "between" and "between" or "neighboring to" and "directly adjacent to" should be interpreted as well.

It is to be understood that the singular " include " or "have" are to be construed as including the stated feature, number, step, operation, It is to be understood that the combination is intended to specify that it does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

In each step, the identification code (e.g., a, b, c, etc.) is used for convenience of explanation, the identification code does not describe the order of each step, Unless otherwise stated, it may occur differently from the stated order. That is, each step may occur in the same order as described, may be performed substantially concurrently, or may be performed in reverse order.

The present invention can be embodied as computer-readable code on a computer-readable recording medium, and the computer-readable recording medium includes all kinds of recording devices for storing data that can be read by a computer system . Examples of the computer-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage, and the like. In addition, the computer-readable recording medium may be distributed over network-connected computer systems so that computer readable codes can be stored and executed in a distributed manner.

All terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs, unless otherwise defined. Commonly used predefined terms should be interpreted to be consistent with the meanings in the context of the related art and can not be interpreted as having ideal or overly formal meaning unless explicitly defined in the present application.

1 is a block diagram illustrating a contract testing system in accordance with an embodiment of the present invention.

Referring to FIG. 1, the contract testing system 100 includes a user terminal 110 and a contract testing server 120.

The user terminal 110 may correspond to a computing device that is connected to the contract testing server 120 and is capable of transmitting and receiving data on the performance of the contract testing process. For example, the user terminal 110 may correspond to a desktop, a laptop, a smart phone, or a tablet personal computer. In one embodiment, the user terminal 110 may send a contract term for the contract to the contract test server 120. [

The contract testing server 120 can test the contract management agent. The contract test server 120 can check the consistency and error of the contract received from the user terminal 110 by being connected to the user terminal 110 through the contract management agent. Here, the contract test server 120 can be implemented with a plurality of computing devices that are not limited to a single computing device but can be distributed processing.

In one embodiment, contract test server 120 may include a contract condition test data database that stores contract condition test data and a test data generation criteria database that stores test data generation criteria. For example, the contract testing server 120 may be used for insurance business. The contract test server 120 can generate contract condition test data that can be tested for each insurance contract life cycle and can be used to timely test contract conditions, maintenance and payment tasks associated with a virtual customer. Hereinafter, the contract test server 120 will be described in detail with reference to FIG.

2 is a block diagram illustrating the contract testing server in FIG.

Referring to FIG. 2, the contract test server 120 includes a contract condition receiving unit 210, a contract condition test data generating unit 220, a contract anomaly check unit 230, and a control unit 240.

The contract condition receiving unit 210 receives the payment from the customer according to the period during the first period managed by the contract management agent and receives the contract condition for the contract maintained during the second period. The first period corresponds to a period of receiving a down payment for the contract from the customer at a specific period. The second period corresponds to the period during which the contract is maintained based on the down payment paid by the customer during the first period. The first period may be set to be the same as the second period or shorter than the second period, and may be dependent on the second period. A contract may be included in a contract type of a new contract, a maintenance contract, or a multiple contract.

The contract condition receiving unit 210 can receive test data generation criteria for the contract type of each of the new contract, maintenance contract, and multi-contract. The test data generation criterion is the reference data for checking the consistency of the contract condition test data, and can be inputted by the manager before receiving the contract condition for the contract.

The contract condition receiving unit 210 can receive the sub contract conditions and the sub contract condition elements according to the contract types of the new contract, the maintenance contract, and the multi contract, respectively. New contracts may include customers and new contracts on the terms of the subcontract. Maintenance contracts may include contract status and billing receipts as a subcontract condition. A multi-agent contract may include a multi-agent reservation of the same person on a sub-contract basis.

In one embodiment, the new contract sets basic information (e.g., resident number, contractor name, wire / wireless number, address) for generating customer information and checks whether the customer is already registered based on basic information about the customer If there is no registered basic information, the customer can be registered as a new customer. The new contract is a process of generating new contract data for a customer based on a test data generation criterion or generating new contract data for a customer based on key information of a product table (for example, a product period, a product period classification code, a payment period, , Gender, and commodity subscription amount) of the new contract data.

In one embodiment, the maintenance contract generates the goods payment information of the target period (i.e., the cycle) for the first period from the past through the generation of the billing receipt data, generates the maintenance contract in a state where the contract is maintained from the past, (For example, at least one of expiration, full payment, expiration, delinquency and resurrection) necessary to generate contract-state data. The maintenance contract may generate the billing receipt data by continuously performing the payment of the commodity if the contract date is past and by paying the contract until the specified target time.

In one embodiment, a multi-contract is a method of associating various contracts with a customer. After creating a new contract, the user can inquire previously registered customer information and create another contract in addition to previously registered customer information.

The contract condition receiving unit 210 can check whether there is a contract or not based on the date of birth and gender of the customer associated with the contract. The contract condition receiving unit 210 can determine whether the customer is related to the pre-registered customer through a part of the customer management associate created based on the date of birth and sex of the customer. In one embodiment, the contract condition receiving unit 210 may generate a customer management associate for the customer based on the customer's date of birth, gender, and contract date, and associate the customer management associator with the contract. For example, a customer care associate can generate a prefix based on the date of birth and create a backorder based on gender and contract date. If the customer care associate is 800106-2141118, the customer may be a woman born on January 6, 1980 and contracted on November 18, 2014.

The contract condition test data generation unit 220 virtually generates the contract event generated during the second period and the payment event generated during the first period to generate contract condition test data. The payment event corresponds to the event that occurs due to the payment of the down payment by the customer. The payment event includes a first payment event that occurs according to the cycle and a second payment event that occurs outside the cycle. A contract-related event corresponds to an event that occurs when a down payment is provided to a customer in accordance with the terms of the contract. The contract related event may include a first contract related event based on the first delivery event and a second contract related event based on the second delivery event.

The contract condition test data generation unit 220 can determine whether to terminate the contract according to the generation time of the second payment event. In one embodiment, the contract condition test data generator 220 may change the information on the contract to a delinquency if the first payment event does not occur according to the period. The contract condition test data generation unit 220 can change the information about the contract to be effective when the information on the contract is changed in an overdue and the second payment event occurs after a specific period (for example, three months) from the contract date . The contract condition test data generation unit 220 changes the information about the contract to revive when the second payment event occurs after a specific period (for example, two months) from the date when the information on the contract is changed to the effective period, If the delivery event does not occur, the contract can be terminated. Here, the contract condition test data generation unit 220 can determine that the contract related event occurring during the period from when the information on the contract is valid to when it is resurrected is invalid.

The contract condition test data generation unit 220 determines the first contract related event based on the first payment event and the second contract related event based on the second payment event to generate the first and second payment events, Contract condition test data can be generated based on contract related events. Contract Terms Test data can be generated for each contract type of new contract, maintenance contract and multi-contract.

In one embodiment, the contract condition test data generator 220 may determine whether the contract condition test data is valid based on the following equation.

[Mathematical Expression]

CD_effect = {(Per1 X Pay1_count) / Con1_count} / {(Per1 X Pay2_count) / Con2_count}

Here, Per1 corresponds to the first period, Pay1_count corresponds to the number of the first paying events, Con1_count corresponds to the number of the first contract related events, Pay2_count corresponds to the number of the second paying events, Con2_count Corresponds to the number of second contract related events, and if it exceeds 5.0, it can be determined to be valid.

(즉, 6.6)로 산출되어 유효성이 있는 것으로 결정될 수 있다. 다른 예를 들어, 계약 조건 테스트 데이터에 대한 유효성은 제1 기간이 60개월, 제1 납입 이벤트의 개수가 45, 제1 계약 관련 이벤트의 개수가 5, 제2 납입 이벤트의 개수가 15, 제2 계약 관련 이벤트의 개수가 2에 해당하면,

(즉, 1.2)로 산출되어 유효성이 없는 것으로 결정될 수 있다.For example, the validity of the contract condition test data is such that the first period is 60 months, the number of first delivery events is 55, the number of first contract related events is 5, the number of second delivery events is 5, If the number of related events equals 2,

(I.e., 6.6) and may be determined to be valid. In another example, the validity of the contract condition test data is such that the first period is 60 months, the number of first payment events is 45, the number of first contract related events is 5, the number of second payment events is 15, If the number of contract related events is 2,

(I. E., 1.2) and may be determined to be non-effective.

The contract condition test data generation unit 220 can check whether or not the contract condition test data is consistent based on the test data generation criterion. The contract condition test data generation unit 220 can check whether all items of the contract condition test data are generated for each of the new contract, maintenance contract, and multi-contract according to the test data generation criterion.

The contract anomaly check unit 230 provides the contract condition test data to the contract management agent to check whether or not the contract is abnormal. The contract anomaly checker 230 can generate a contract validation query for verifying the abnormality of the contract condition for the contract based on the contract condition test data. In one embodiment, the contract validation query can be generated in SQL (Structured Query Language). The contract anomaly checker 230 may provide a contract validation query to the contract management agent to detect an error identification code for the contract. The error identification code can be stored in advance in association with the error information on the contract.

The contract anomaly check unit 230 can analyze the error identification code and update the contract condition for the contract upon detecting the error identification code for the contract. The contract anomaly check unit 230 may store the contract and the error identification code in the database as an error history in association with each other, and provide an inquiry function for the contract in which the error occurred.

The control unit 240 controls the overall operation of the contract test server 120 and controls the operation and data flow between the contract condition receiving unit 210, the contract condition test data generating unit 220, do.

3 is a diagram showing the hardware configuration of the contract test server shown in FIG.

Referring to FIG. 3, the contract testing server 120 includes a processor 310 (or CPU) that communicates with the various components via a bus 320. The processor 310 may control the operation of various components and may control operations of the contract condition receiving unit 210, the contract condition test data generating unit 220, and the contract anomaly check unit 230. The processor 310 may also generate contractual condition test data via instructions stored in the memory 330 that are electrically coupled to the memory 330. [ The contract testing server 120 includes a memory 330 and a storage device 340. The memory 330 includes a ROM 331 and a random access memory . Here, the memory 330 corresponds to a temporary or permanent computer-readable recording medium, and the storage device 340 corresponds to a computer-readable recording medium permanently. At least one of the memory 330 and the storage device 340 stores computer code including instructions for generating contract condition test data.

The contract testing server 120 includes a network interface 370 for communicating with the network 130. The network interface 370 provides an environment in which information, data and signals between the contract test server 120 and the network 130 can be transmitted.

The user may access the contract testing server 120 (e. G., Via the user interface input device 350) (e. G., A mouse, trackball, touchpad, graphic tablet, scanner, barcode scanner for item barcode scanning, touch screen, keyboard, pointing device, ). ≪ / RTI > User interface input device 350 includes all the mechanisms by which information (e.g., transactions) can be entered into contract testing server 120 or network 130.

The user may receive information from the contract test server 120 via the user interface output device 360. [ The user interface output device 360 may include, but is not limited to, a visual output device such as a display screen. The user interface output device 360 may include any mechanism capable of outputting information to a user and may be combined with an output device such as a video output device or a speaker. In one embodiment, the display screen may display information received from the contract test server 120 and receive input from a user. That is, the display screen may be implemented as a user interface input device 350 and a user interface output device 360.

The components of the contract test server 120 of FIG. 2 may be performed using the components of the contract test server 120 of FIG.

4 is a flowchart illustrating a contract test process performed in the contract test server shown in FIG.

4, the contract condition receiving unit 210 receives the payment from the customer according to the period during the first period managed by the contract management agent, and receives the contract condition for the contract maintained during the second period (step S401) .

In one embodiment, the contract condition receiver 210 may receive test data generation criteria for the contract type of each of the new contract, maintenance contract, and multi-contract. For example, the test data generation standard includes a test data generation ID, a test task classification code, a test type code, the number of contracts, a date of birth, a gender code, a contract date, a product code, , The commodity period identification code, the commodity period classification value, the pension commencement age, the commodity occupation code, the transit day code, the delivery number, the additional payment period code, the supplementary payment, and the free payment.

The contract condition receiving unit 210 can receive the sub contract conditions and the sub contract condition elements according to the contract types of the new contract, the maintenance contract, and the multi contract, respectively.

The contract condition test data generation unit 220 generates the contract condition test data by virtually generating the contract event generated during the second period and the payment event generated during the first period (step S402).

The contract condition test data generation unit 220 determines the first contract related event based on the first payment event and the second contract related event based on the second payment event to generate the first and second payment events, Contract condition test data can be generated based on contract related events.

The contract anomaly checker 230 provides the contract condition test data to the contract management agent to check whether the contract is abnormal (step S403).

The contract anomaly checker 230 can generate a contract validation query for verifying the abnormality of the contract condition for the contract based on the contract condition test data. The contract anomaly checker 230 may provide a contract validation query to the contract management agent to detect an error identification code for the contract.

5 is a diagram illustrating the type of contract received at the contract testing server in FIG.

Referring to FIG. 5, the contract condition receiving unit 210 may receive a sub contract condition and a sub contract condition element according to a contract type of a new contract, a maintenance contract, and a multi-contract, respectively.

The new contract includes subcontracting customers and new contracts, and subcontracting conditions include contract date, gender and corresponding contract date, product code, insurance (commodity) period, payment period, Age, occupation code, and insurance coverage.

The maintenance contract includes the contract status and the billing receipt under the subcontract condition. The subcontract condition element is a transfer date corresponding to expiration, full payment, expiration, delinquency, resurrection and bill payment corresponding to the contract status, number of payment, · Insurance premiums, free payment cycles, and insurance premiums may be included.

A multi-contract may include a multi-contract of the same person as a sub-contract condition, and may include a multi-contract type corresponding to a multi-contract of the same person as a sub-contract condition element.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit and scope of the present invention as defined by the following claims It can be understood that

100: contract testing system
110: User terminal
120: Contract testing server
210: Contract condition receiver
220: contract condition test data generation unit
230: Contract Abnormality Check Section
240:

Claims (9)

A contract testing method performed by a contract testing server connected to a user terminal and testing contracts managed at a contract management agent,
A sub contract according to a contract type of a new contract, a maintenance contract, and a multi-contract contract for the contract, which receives the payment from the customer during the first period of the contract lifecycle managed by the contract management agent and is maintained for the second period, Receiving a contract condition including a condition and a sub contract condition element and receiving a test data generation criterion for a contract type including a new contract, a maintenance contract and a multi-contract;
A payment event generated during or after the period during the first period and a contract related event generated during the second period to generate contract terms, maintenance and payment tasks of the contract associated with the virtual customer, Contract condition test data to be tested for each life cycle, determines whether to terminate the contract according to the occurrence time of a payment event occurring in the period other than the period, and determines whether the contract is terminated, Changing a contract status defined through at least one of an effective, delay, and revival, and checking whether the contract condition test data is consistent based on the test data generation criterion; And
A contract validation query for verifying whether or not the contract condition for the contract is erroneous is registered on the basis of the contract condition test data by registering an error type that is not normal with the contract condition test data generated for each transaction type in advance as a verification condition And providing the contract validation query to the contract management agent to detect an error identification code for the contract to check for consistency and error in the contract.
delete 2. The method of claim 1, wherein receiving the contract terms for the contract comprises:
And checking whether there is a multi-party contract based on the date of birth and sex of the customer associated with the contract.
2. The method of claim 1, wherein receiving the contract terms for the contract comprises:
Generating a customer management associate for the customer based on the customer's date of birth, gender, and contract date, and associating the customer management associator with the contract.
2. The method of claim 1, wherein generating the contract condition test data comprises:
Determining a first contract related event based on the first payment event generated according to the period and a second contract related event based on the second payment event generated during the period other than the period.
6. The method of claim 5, wherein generating the contract condition test data comprises:
And generating the contract condition test data based on the first and second payment events and the first and second contract related events.
The method of claim 1, wherein the step of checking for an abnormality
And analyzing the error identification code to update a contract condition for the contract.
A processor; And
Comprising: a non-transitory computer readable storage medium having stored thereon instructions for causing the processor to perform the following method: when the processor executes the instructions,
A computer-executable contract test method for testing a contract managed by a contract management agent,
A sub contract according to a contract type of a new contract, a maintenance contract, and a multi-contract contract for the contract, which receives the payment from the customer during the first period of the contract lifecycle managed by the contract management agent and is maintained for the second period, Receiving a contract condition including a condition and a sub contract condition element and receiving a test data generation criterion for a contract type including a new contract, a maintenance contract and a multi-contract;
A payment event generated during or after the period during the first period and a contract related event generated during the second period to generate contract terms, maintenance and payment tasks of the contract associated with the virtual customer, Contract condition test data to be tested for each life cycle, determines whether to terminate the contract according to the occurrence time of a payment event occurring in the period other than the period, and determines whether the contract is terminated, Changing a contract status defined through at least one of an effective, delay, and revival, and checking whether the contract condition test data is consistent based on the test data generation criterion; And
A contract validation query for verifying whether or not the contract condition for the contract is erroneous is registered on the basis of the contract condition test data by registering an error type that is not normal with the contract condition test data generated for each transaction type in advance as a verification condition And providing the contract validation query to the contract management agent to detect an error identification code for the contract to check for consistency and error in the contract.
A computer-readable recording medium on which a program for implementing a computer-executable contract testing method for testing a contract managed by a contract management agent is recorded,
A sub contract according to a contract type of a new contract, a maintenance contract, and a multi-contract contract for the contract, which receives the payment from the customer during the first period of the contract lifecycle managed by the contract management agent and is maintained for the second period, Receiving a contract condition that includes a condition and a subcontract condition element and receiving a test data generation criterion for a contract type including a new contract, a maintenance contract, and a multiple contract;
A payment event generated during or after the period during the first period and a contract related event generated during the second period to generate contract terms, maintenance and payment tasks of the contract associated with the virtual customer, Contract condition test data to be tested for each life cycle, determines whether to terminate the contract according to the occurrence time of a payment event occurring in the period other than the period, and determines whether the contract is terminated, Changing the contract status defined through at least one of the validity, overdue, and resurrected, and checking whether the contract condition test data is consistent based on the test data generation criterion; And
A contract validation query for verifying whether or not the contract condition for the contract is erroneous is registered on the basis of the contract condition test data by registering an error type that is not normal with the contract condition test data generated for each transaction type in advance as a verification condition And a function of providing the contract validation query to the contract management agent to detect an error identification code for the contract and checking whether the contract is consistent and errory, Readable recording medium.

Images