JP4988367B2 - Business system development method related to the agreement - Google Patents

Description

  The present invention relates to a method for developing a business system according to a contract, which is a contract clause for performing a routine processing of a contract.

  In order to develop a business system related to the clauses, which are contract clauses for executing the routine processing of contracts, a business system developer analyzes the clauses, and has a business system that definitely reflects the contents of the clauses. Need to develop. However, the agreement is a document that is difficult for business system developers to understand, and it is difficult to correctly analyze the contents of the agreement and develop a business system that accurately reflects the contents of the agreement.

  In Patent Document 1, the terms and rules related to the terms in the insurance policy are defined, and the specifications are created in the format defined using the terms defined by the user. A method by which a program can be generated is disclosed. However, in the method disclosed in Patent Document 1, it is necessary to create specifications in a format different from the structure of the terms and conditions, and it is difficult to accurately reflect the contents of the terms and conditions.

JP2003-30424

  There is an insurance business system as an example of a business system related to the contract. In the insurance business, when a new insurance product is sold, it is necessary to prepare an insurance policy for a new insurance product contract and to maintain the insurance business system accordingly. As described above, the contents of the terms and conditions are difficult for business system developers to understand, which makes maintenance of the insurance business system difficult.

  An object of the present invention is to provide a method of developing a business system according to a contract that can easily reflect the contents of the contract accurately.

  The present invention reads information on designated element parts, such as chapters, articles, clauses, and numbers related to the clauses from the clause information database on the storage device, and information on the designated connected parts indicating the connection relationship between the element parts, Create a table with the designation information of element parts and coupling parts that express the logical structure of the clause and store them in the clause information database, and refer to the designation information table from the element parts to other elements via the coupling parts. By tracing to the part, information on the element part that matches the predetermined condition is extracted, and information on the extracted series of element parts is generated as a conceptual model and stored in the conceptual model database on the storage device. Reads a conceptual model from the system, and embeds information on element parts contained in the conceptual model into a template of a predetermined program. Generate management program, and wherein the business system development technology according to clause storing business processing program generated in the storage device.

  According to the present invention, a unit component part that is a constituent element of a contract such as a chapter, article, paragraph, or number and a combined part that indicates a relationship in the contract including a hierarchical structure of the contract are prepared. By specifying these parts, the contract information having the same structure as the contract can be defined. Furthermore, since the business processing program is generated using the defined terms and conditions information, it is possible to create a business processing program that accurately reflects the contents of the terms and conditions. Also, by generating a conceptual model system in the process of generating a business processing program from the contract information, it is possible for the user to easily understand the relationship between the conceptual model that appears in the contract and the conceptual model. In this way, it is possible to develop a business system related to the contract that accurately reflects the contents of the contract.

Hereinafter, embodiments of the present invention will be described in detail.
As shown in FIG. 1, a program generation apparatus 120 based on a contract according to an embodiment of the present invention includes a contract processing unit 102, a contract information database 104, a conceptual model generation unit 106, a conceptual model database 108, and a business processing program generation. Unit 110 and a business processing program generation rule database 112. The arrows in the figure indicate the flow of data between components. As shown in FIG. 2, the program generation device 120 according to the contract is realized by using a computer having a CPU 201, a main storage device (memory) 202, an input device 203, a display device 204, and an external storage device 205. The The clause information database 104, the conceptual model database 108, and the business process program generation rule database 112 are stored in the external storage device 205, and data is read from and written to the main storage device 202 as the program is executed. The clause processing unit 102, the conceptual model generation unit 106, and the business process program generation unit 110 are programs stored in the main storage device 202 and executed by the CPU 201.

  The covenant processing unit 102 inputs the text of the covenant 100 stored in the external storage device 205, etc., and disassembles it into the element parts and the element coupling parts of the covenant wording such as chapters, articles, items, and issues, etc. into the covenant information database 104. The information specified by the user is read out from this database, product information, component designation information, and coupled component designation information are created and stored in the clause information database 104. The conceptual model generation unit 106 reads the created component designation information and combined component designation information, creates a conceptual model, and stores it in the conceptual model database 108. The business process program generation unit 110 refers to the created conceptual model and the business process program generation rules stored in the business process program generation rule database 112 to generate the business process program 114 and stores it in the external storage device 205 or the like To do.

  As shown in FIG. 3, the clause information database 104 includes a clause element component table 300, a clause element combination component table 302, a product information table 304, a clause element component designation information table 306, and a clause element combination component designation information table. 308. The name shown in the upper square (for example, 310) of each table represents the table name. The name shown in the lower square (for example, 312) of each table is the attribute name of each table. The attribute underlined in the attribute name of each table (for example, 314) represents an identifier for uniquely identifying attribute data defined by the table. The arrows in FIG. 3 represent such a reference relationship between identifiers.

  The contract element parts table 300 is a table that defines the parts of the contract elements, such as chapters, articles, sections, and issues. The contract element part table 300 includes a contract element part ID 402 and a contract for uniquely identifying data defined by the contract element part table 300 as shown in FIG. It has an element part name 404, and further has a clause text 406 that defines the components of the clause such as a chapter, an article, a section, and an item, and a clause logic 408 corresponding to the clause text. The example clause logic 408 listed here shows the clause text that is added when the conceptual model is created.

  The contract element combination parts table 302 is a table that defines parts indicating relationships in the contract including the hierarchical structure of the contracts. As shown in an example of data defined by the clause element structure component table 302 in FIG. 5, the clause element combination component table 302 is a clause element combination component for uniquely identifying data defined by the clause element combination component table 302. It has an ID 502 and a contract element combined part name 504 for expressing the relationship between the contract element parts. The relations defined as the relations between the contract element parts include, for example, “comprehensive” indicating the hierarchical relationship of the document hierarchy such as the clauses, articles, sections, and issues of the contract, and other contract element parts depending on the contents defined in one contract element part. There is "Apply" that represents the relationship to change the contents defined in. “Inclusive” is a connected part that connects an element part in an upper hierarchy and an element part in a hierarchy immediately below the element part. “Applied” and “applied mutatis mutandis” are joint parts that indicate the relationship between element parts in accordance with the meaning of legal terms.

  The article information table 304, the clause element component designation information table 306, and the clause element combination component designation information table 308 to be described below are referred to by the clause processing unit 102 with reference to the data of the clause element component table 300 and the clause element combination component table 302. The table is created for the user to define the clause information defined in the same structure as the clause.

  As shown in FIG. 6 as an example of data defined by the product information table 304, the product information table 304 includes a product ID 602 for uniquely identifying data defined by the product information table 304, and a product defined by the user. A name 604 and a contract element parts designation information ID 606; The contract element component designation information ID 606 is data representing the entire contract of the contract element component designation information table 306 so that the data of the contract element component table 300 representing the entire contract can be referred to from the data of the product information table 304. The contract element part designation information ID 702 is set.

  The clause element component designation information table 306 is a clause for uniquely identifying data defined by the clause element component designation information table 306 as shown in FIG. 7 as an example of data defined by the clause element component designation information table 306. The element part designation information ID 702, the article ID part 704 for enabling the data of the article information table 304 to be referred to from the data of the clause element part designation information table 306, and the clause element part from the data of the clause element part designation information table 306 It has a clause element part ID 706 for making it possible to refer to the data of the table 300.

  The contract element coupling component designation information table 308 uniquely identifies data defined by the clause element coupling component designation information table 308 as shown in FIG. 8 as an example of data defined by the clause element coupling component designation information table 308. Clause element binding component designation information ID 802, clause element binding component ID 804 for enabling reference to data in the clause element binding component table 302 from the data in the clause element binding component designation information table 308, and clause element binding In order to make it possible to refer to the data in the contract element part specification information table 306 by the data in the part specification information table 308, the source contract element part specification information ID 806 indicating the data in the source contract element part specification information table 306 and And a combined contract element component designation information ID 808 indicating data in the combined contract element component designation information table 306.

  The conceptual model database 108 includes a conceptual model generation rule table 900 that defines rules for generating a conceptual model from the contract information defined by the contract processing unit 102 described below, and a conceptual model definition table that stores the generated conceptual model. 110.

  The conceptual model generation rule table 900 has a model generation ID 902 for uniquely identifying data defined by the conceptual model generation rule table 900, as shown in FIG. 9 as an example of data defined by the conceptual model generation rule table 900. A model generation logic 906 and a generation source contract element part ID 904 that defines information for enabling specification of data of the contract element part table 300 to which the model generation logic 906 is applied. The model generation logic 906 is a processing procedure for generating the concept model described below. An example of the processing flow of the model generation logic 906 is shown in FIG. The processing procedure will be described later.

  The conceptual model data is defined in a conceptual model definition table 1100 as shown in FIG. The conceptual model definition table 1100 includes a concept ID 1102 for uniquely identifying data defined by the conceptual model definition table 1100, a product ID 1104 for identifying a product in which the concept is defined, and a risk collateral in which the concept is defined. Between the conceptual model, the risk collateral agreement element component designation information ID 1106 that identifies the data in the agreement element component designation information table 306 that specifies the data in the defined agreement element component table 300, the conceptual content 1108 that defines the content of the concept, and the conceptual model In order to represent the relationship, a relationship concept ID 1120 indicating a relationship with data in another conceptual model definition table 1100 is included. Note that the type of concept model can be identified by the alphabet in the ID of the concept ID 1102. In the related concept ID 1120, specifically, a concept ID 1102 of data in another conceptual model definition table 1100 is entered. In the following example, “insured person” is taken up and the conceptual model is explained.

  The business process program generation rule database 112 has a business process program generation table 1200. The business process program generation table 1200 includes a program generation ID 1202 for uniquely identifying data defined by the business process program generation table 1200, as shown in FIG. 12 as an example of data defined by the business process program generation table 1200. And a program generation logic 1204 for defining logic for generating a program from the conceptual model. An example of the processing flow of the program generation logic 1204 is shown in FIG. The processing procedure will be described later.

  The clause processing unit 102 will be described according to the processing flow of FIG.

  In step 1502, the clause processing unit 102 outputs the clause information editing screen 1800 shown in FIG. 18 to the display device 204, and the user inputs a product ID 1804 and a product name 1806 from the input device 203. If it is determined that the new creation button 1801 has been pressed, the data of the product information table 304 in which the input product ID 1804 is set to the product ID 602 and the product name 1806 is set to the product name 604 is newly created. The product name is information that represents the entire contract. Next, a new clause element part designation information table 306 is created, and a new clause element part designation information ID is generated and set in the clause element part designation information ID 702 as the first data of the created clause element part designation information table 306. Then, the product ID 1804 input by the user is set in the product ID 704 of the data in the terms and conditions element part designation information table 306, and the data in the terms and conditions element part table 300 representing the entire terms and conditions is obtained from the data in the terms and conditions element part designation information table 306. In order to be able to refer to it, the contract element part ID of the data of the contract element part table 300 representing the entire contract is set in the contract element part ID 706, and the data of the contract element part designation information table 306 thus created is stored in the contract information database. Write to 104. Furthermore, the newly created contract element part designation information ID 702 is set in the contract element part designation information ID 606 of the data of the newly created product information table 304, and a new product is obtained from the newly created clause element part designation information table 306 data. The data in the information table 304 can be referred to. Finally, the data of the new product information table 304 is written into the clause information database 104. In addition, a symbol of an element part name representing the entire contract is displayed on the screen part 1808.

  Note that 1850, 1851, 1852, 1853, and 1854 shown in the screen part 1808 are symbols representing the contract element part name 404 of the contract element part table 300 pointed to by the data of the contract element part designation information table 306, Reference numerals 1861, 1862, and 1863 are symbols representing the contract element combined component name 504 of the contract element combined component table 302 pointed to by the data of the contract element combined component designation information table 308. For example, 1850 is an element part name that represents the entire contract, 1851 and 1852 are element part names that represent chapters, and 1853 and 1854 are element part names that represent articles. 1850-1854 are displayed one by one when step 1522 is executed, and 1860-1863 are displayed one by one when step 1516 is executed.

  In step 1504, the clause processing unit 102 first waits for a user operation, and upon receiving an instruction from the input device 203 by a user operation, determines whether the instruction is to move to step 1506 and add a clause element part. . If it is an instruction to add a clause element part, the process proceeds to step 1518; otherwise, the process proceeds to step 1508. The instruction to add a clause element part represents the clause element combination part name 504 of the clause element combination part table 302 pointed to by the data of the clause element combination part designation information table 308 through the input device 203 on the clause information edit screen 1800. Occurs when it is determined that the symbol has been pressed.

  In step 1508, the clause processing unit 102 determines whether or not it is an instruction to add a clause element coupling part. If it is an instruction to add a clause element combination part, the process proceeds to step 1512, and if not, the process proceeds to step 1510. Note that the instruction to add a clause element combination part represents the clause element part name 404 of the clause element part table 300 indicated by the data of the clause element part information table 306 through the input device 203 with respect to the clause information editing screen 1800 in step 1504. Occurs when it is determined that the symbol has been pressed.

  In step 1510, the clause processing unit 102 determines whether the instruction is that the edit end button 1802 has been pressed. If the edit end button 1802 has not been pressed, the process moves to step 1504. If the button has been pressed, the process of the clause processing unit 102 ends, and the process moves to the conceptual model generation unit 106. When the processing is transferred to the conceptual model generation unit 106, the product ID displayed on the screen part 1804 of the clause information editing screen 1800 is transferred to the conceptual model generation unit 106.

  In the following steps 1518, 1520, and 1522, processing procedures for adding data in the contract element component designation information table 306 to create the contract information in accordance with the contract will be described.

  In step 1518, the clause processing unit 102 first outputs a clause element parts selection screen 1900 shown in FIG. At this time, the data of the contract element binding component designation information table 308 corresponding to the symbol pressed in step 1504 is detected, and the contract element binding component designation information ID 802 of the detected data of the contract element coupling component designation information table 308 is displayed on the screen part. Displayed in 1901. Next, when it is determined that the user inputs a clause text into the screen part 1902 using the input device 203 and the search start button 1908 is pressed, the data in the clause element part table 300 including the clause text input from the user from the clause information database 104. Is read, and a list of the contract element part names 404 of the data of the corresponding contract element part table 300 corresponding to the search is output to the display device 204 and displayed on the screen part 1904. At this time, if the user designates one of the contract element part names displayed on the screen part 1904 using the input device 203 and determines that the contract element part selection button 1906 is pressed, the process proceeds to step 1520.

  In step 1520, the clause processing unit 102 first creates data relating to the specified element part in the clause element part designation information table 306. As new data of this clause element component designation information table 306, a new clause element component designation information ID is created and set in the clause element component designation information ID 702, and the product ID displayed on the screen part 1804 of the clause information edit screen 1800 is set. In step 1518, data of the contract element part table 300 having the contract element part name designated by the user is read from the contract information database 104, and the contract element part ID 402 of this data is set in the contract element part ID 706. The data of the clause element component designation information table 306 created in this way is written into the clause information database 104. Further, the data of the contract element binding component specification information table 308 having the binding source contract element binding component specification information ID displayed on the screen part 1901 is read from the contract information database 104, and the read data of the contract element binding component specification information table 308 is read. The newly created contract element component designation information ID 702 is set in the combined contract element component designation information ID 808. The updated data in the contract element combination component designation information table 308 is written in the contract information database 104.

  In step 1522, the clause processing unit 102 outputs a symbol representing an element part name corresponding to the data in the clause element part designation information table 306 created in step 1520 to the display device 204, and the output symbol is pressed in step 1504. The arrow line connecting the symbol representing the element coupling part name corresponding to the data in the contract element coupling part designation information table 308 is output to the display device 204 and displayed on the screen part 1808 of the contract information editing screen 1800. Finally, the process proceeds to step 1504.

  In the following steps 1512, 1514, and 1516, a method for adding the data of the contract element coupling component designation information table 308 to create the contract information in accordance with the contract will be described.

  In step 1512, the clause processing unit 102 first outputs a clause element combined component selection screen 2000 shown in FIG. 20 to the display device 204. At this time, data in the contract element component designation information table 308 is detected from the symbol pressed in step 1504, and the contract element component designation information ID of the detected data in the contract element component designation information table 308 is displayed on the screen part 2001. Next, all the data in the clause element combined component table 302 stored in the clause information database 104 is read, and a list of the clause element combined component names 504 is output to the display device 204 and displayed on the screen portion 2002. A contract element coupling part is designated by the user from the name of the contract element coupling part displayed on the screen portion 2002 according to the contract by using the input device 203. Finally, it is determined whether or not the clause element combination component selection button 2004 has been pressed. If it is determined that the clause has been pressed, the process proceeds to step 1514. If it is determined that the button has not been pressed, the process stays at step 1512.

  In step 1514, the clause processing unit 102 creates data related to the specified element combination component in the new contract element combination component designation information table 308. As the new data in this clause element binding component designation information table 308, the newly created clause element coupling component designation information ID is set in the clause element coupling component designation information ID 802, which is designated by the user in the clause element coupling component ID 804 in step 1512. The data of the contract element combined component table 302 having the name of the contract element combined component is read from the contract information database 104 and the contract element component ID 502 of this data is set. Further, the source contract element component designation information ID displayed on the screen part 2001 of the contract element combined component selection screen 2000 is set in the source contract element component designation information ID 804 of the data of the clause element linked component designation information table 308. The data of the clause element combined component designation information table 308 created in this way is written into the clause information database 104.

  In step 1516, the clause processing unit 102 outputs a symbol representing the element coupling part corresponding to the data in the clause element coupling part designation information table 308 created in step 1514 to the display device 204, and presses the outputted symbol and step 1504. The arrow line connecting the symbol representing the element part name corresponding to the data of the contract terms and parts designation information table 306 is output to the display device 204 and displayed on the screen part 1808 of the terms and conditions information editing screen 1800. Finally, the process proceeds to step 1504.

  As described above, the clause processing unit 102 creates the clause element component designation information table 306 and the clause element combination component designation information table 308 representing the logical structure of the clause from the clause element component table 300 and the clause element combination component table 302. And stored in the clause information database 104.

  The conceptual model generation unit 106 will be described according to the processing flow of FIG.

  In step 1604, the conceptual model generation unit 106 reads one piece of data in the conceptual model generation rule table 900 registered in advance. For example, the model generation ID 902 is ms0001, the generation contract clause element part ID 904 is t, and the model generation logic 906 is model generation logic for executing the processing flow shown in FIG. The data 910 of the rule table 900 is read.

  In step 1606, the conceptual model generation unit 106 reads the data of the clause element part table 300 to which the conceptual model generation rule read in step 1604 is applied. In order to achieve this, in the data of the created contract terms component part designation information table 306, it has the same product ID 602 as the product ID passed from step 1510 of the clause processing section 102, and in the conceptual model generation rule table 900 Data including the data generation source contract element part ID 904 in the contract element part ID 706 is read from the contract information database 104. For example, if the source contract element ID 904 is t, the contract element part specification information ID 702 is aa0171 and the product ID 704 is shn5678 from the data in the contract element part specification information table 306. Data 720 having ID 706 of t01235, data 721 having contract element component designation information ID 702 of aa0172, product ID 704 of shn5678, and contract element component ID 706 of t01236 are read.

  In step 1608, the conceptual model generation unit 106 stores the data in the contract element part table 300 having the same contract element part ID 402 as the contract element part ID 706 with respect to one of the data in the contract element part designation information table 306 read in step 1606. By specifying the data, the data of the clause element part table 300 to which the read conceptual model generation rule is applied is specified. For example, if the contract element part ID 706 of one piece of data in the contract element part designation information table 306 read in step 1606 is t01235, the contract element part ID is t01235 from the data of the contract element part table 300. The clause logic 408 identifies data that is “add (named insured person)”. Next, the model generation logic 906 included in the data of the conceptual model generation rule table 900 specified in step 1604 is used from the data of the specified contract element component specification information table 306 and the data of the contract element component table 300. Generate a conceptual model. An example of generating a conceptual model using the model generation logic 906 is shown in a processing flow in FIG. Details of the processing flow of FIG. 10 will be described later. The conceptual model generation unit 106 writes the created conceptual model in the conceptual model database 108.

  In step 1610, the conceptual model generation unit 106 determines whether the data in all the clause element component designation information table 306 read in step 1606 has been processed in step 1608, and if all have been processed, the process proceeds to step 1612. If all the processes have not been processed, the process proceeds to step 1608.

  In Step 1612, the conceptual model generation unit 106 determines whether all the conceptual model generation rules stored in the conceptual model database 108 read in Step 1604 have been processed, and has processed all the model generation rules Terminates the process of the conceptual model generation unit 106, moves the process to the business process program generation unit 110, and shifts the process to step 1604 if all the processes are not processed. One of the conceptual models shown in the present embodiment corresponds to the whole element part having the t symbol in the clause element part ID 706, and corresponds to one or more element parts.

  As described above, the conceptual model generation unit 106 refers to the clause element component designation information table 306 and the clause element combination component designation information table 308, and traces from the component component to another element component via the combination component. Information on element parts that match the conditions indicated by the data in the conceptual model generation rule table 900 is extracted, and the extracted information on the series of element parts is stored in the conceptual model database 108 as a conceptual model.

  An example of conceptual model generation by the model generation logic will be described according to the processing flow of FIG. The processing flow of FIG. 10 represents a model generation logic for generating a conceptual model corresponding to the concept of insurance insured as a processing flow. The insured means a person who receives the insurance money, and the insured is defined for each risk collateralized by the insurance. Therefore, it is necessary to specify which risk collateral insured is the insured to be defined. The insured person concept model generation logic shown in the processing flow of FIG. 10 uses the clause element parts that define the insured person specified in step 1606, and performs step 1002, step 1004, step 1006, step 1008, and step 1010. The data of the contract element component designation information table 306 created by the clause processing section 102 is repeated with the data of the contract element combination component designation information table 308 and the data of the contract element combination component table 302. By specifying the data of the contract element part specification information table 306 that specifies the data of the contract element part table 300 that defines the risk guarantee clause indicating the risk collateral in the contract 100, A conceptual model corresponding to the insured is generated.

  In step 1002, the model generation logic specifies a contract element combination part specification including the same contract element part specification information ID 808 as the contract element part specification information ID 702 in the data of the contract element part specification information table 306 identified in step 1606 or step 1006. Read the data in the information table 308. For example, when the contract element component designation information ID 702 in the data of the contract element component designation information table 306 identified in step 1606 is aa0171, the contract element combination component designation information ID 802 in the data of the clause element combination component designation information table 308 is displayed. Is bb0031, the data 820 is read in which the clause element combination component ID 804 is ka0001, the source clause element component designation information ID 806 is aa0170, and the destination clause element component designation information ID 808 is aa0171. Next, the processing moves to step 1004.

  In step 1004, the model generation logic reads the data of the contract element combined component table 302 having the same contract element combined component ID 502 as the general contract element combined component ID 804 of the data of the contract element combined component designation information table 308 read in step 1002. . For example, when the data 820 of the contract element coupling component designation information table 308 is read in step 1002, the data 510 of the contract element coupling component specification table 302 is read.

  In step 1006, the model generation logic sets the contract element combination component name 504 of the data in the contract element combination component table 302 read in step 1004 from the data in the contract element combination component designation information table 308 read in step 1002. Select the item that is “inclusive”, and read the data of the contract element part specification information table 306 having the same contract element part specification information ID 702 as the source contract element part specification information ID 806 of the selected contract element connection part specification information table 308 . For example, since the contract element combination part name 504 of the data 510 of the contract element combination part table 302 in step 1004 is “inclusive”, the source contract element of the data 820 of the contract element combination part designation information table 308 read in step 1002 Data 722 of the contract element component designation information table 306 having the same contract element component designation information ID 702 as the component designation information ID 806 is read.

  In step 1008, the model generation logic reads the data of the contract element part table 300 specified by the data of the contract element part specification information table 306 read in step 1006, and determines whether this data defines the risk collateral clause. . In order to determine the type of data, for example, 'd' indicating the risk guarantee clause is attached to the clause element part ID of the data in the clause element part table 300, and it can be determined from the clause element part ID whether or not it is a risk guarantee clause. Keep it like that. For example, it is assumed that the data 722 is read as data of the clause element component designation information table 306 in step 1006. In this case, since ‘d’ is not included in the clause element part ID 706 of the data 722, it can be seen that the data in the clause element part table 300 specified by the data 722 is not data defining the risk collateral clause. Further, for example, it is assumed that data 723 is read as data in the clause element component designation information table 306 in step 1006. In this case, since ‘d’ is included in the contract element part ID 706 of the data 723, it can be seen that the data of the contract element part table 300 specified by the data 722 is data defining the risk guarantee clause.

  In step 1010, the model generation logic defines the risk collateral clause based on the determination result in step 1008 and the data in the contract element component table 300 specified by the data in the contract element component specification information table 306 read in step 1006. If it is the data to be processed, the process proceeds to step 1012. If the data does not define the risk collateral clause, the process proceeds to step 1002.

  In step 1012, the model generation logic creates the data of the conceptual model definition table 1100 shown in FIG. 11 on the memory based on the processing results from step 1002 to step 1010, and writes it in the conceptual model database 108. First, the clause logic 408 of the data in the clause element component table 300 specified by the data in the clause element component designation information table 306 read in step 1006 is read, and the contents shown in parentheses of “add ()” are created The data is set in the conceptual contents 1108 of the data in the conceptual model definition table 1100. Next, the product ID 704 of the data in the contract element component designation information table 306 identified in step 1606 is set in the product ID 1104 of the data in the created conceptual model definition table 1100. Further, the contract element component designation information ID 702 of the data of the contract element component designation information table 306 read in step 1006 is set in the risk collateral agreement element component designation information ID 1106 of the data of the created conceptual model definition table 1100. Further, a new concept ID is generated and set in the data concept ID 1102 of the created conceptual model definition table 1100. Finally, the data of the conceptual model definition table 1100 created in this way is written into the conceptual model database 108. For example, since the contract logic of the data 420 of the contract element component table 300 specified by the data 723 of the contract element component specification information table 306 read in step 1006 is “add (named insured person)”, this conceptual model definition “Registered insured person” is set in the conceptual contents 1108 of the data 1110 in the table 1100. Next, shn5678, which is the product ID 704 of the data 720 in the clause element component designation information table 306 identified in step 1606, is set in the product ID 1104 of the data 1110. Further, d706, which is the contract element component designation information ID 702 of the data 723 of the contract element component designation information table 306 read in step 1006, is set in the risk collateral agreement element component designation information ID 1104 of the data 1110. Further, hh0001 is generated as a new concept ID, and is set in the concept ID 1102 of the data 1110. Data 1110 of the conceptual model definition table 1100 created in this way is written into the conceptual model database 108.

  The business processing program generation unit 110 will be described according to the processing flow of FIG.

  In step 1702, the business process program generation unit 110 reads the data of the conceptual model definition table 1100 from the conceptual model database 102. At this time, only the data including the product ID input in the part 1804 of the clause information editing screen 1800 is read. For example, when the product ID input to the part 1804 of the clause information editing screen 1800 is shn5678, data 1110 and data 1112 of the conceptual model definition table 1100 shown in FIG. 11 are read.

  In step 1704, the business process program generation unit 110 displays the conceptual model display screen 2100 shown in FIG. The part 2102 displays the product ID input in the part 1804 of the contract information editing screen 1800, and the part 2104 displays the product name input in the part 1806 of the contract information editing screen 1800. The conceptual model is displayed on the part 2108 using the data of the table defining the conceptual model read in Step 1702. The notation of the conceptual model is represented by symbols such as a part 2110 and a part 2111, and the relationship between the conceptual models is represented by an arrow such as a part 2112. The symbol of the part 2110 represents the insured person's conceptual model, and displays the data 1110 and data 1112 of the conceptual model definition table 1100 shown in FIG. The arrow of the part 2112 indicates the relationship between the concept models, and is displayed with reference to the relationship concept ID 1120. In this way, the user can visually confirm the system of the conceptual model generated from the clause information. When the user confirms the displayed conceptual model system and determines that it is appropriate, the user presses the program generation button 2106 through the input device 203. It is determined that the program generation button 2106 has been pressed, and the process proceeds to step 1706.

  In step 1706, the business process program generation unit 110 reads one piece of data of the business process program generation table 1200 shown in FIG. 12 from the business process program generation rule database 112.

  In step 1708, the business process program generation unit 110 executes the program generation logic 1204 of the data of the business process program generation table 1200 shown in FIG. 12 read in step 1706 to generate the business process program 114, and the generated business process The processing program 114 is stored in the external storage device 205. For example, in step 1706, the data 1210 of the business process program generation table 1200 shown in FIG. 12 is read, and the program generation logic 1204 of the data 1210 is executed to generate the program shown in FIG. 14b. An example of generating a business processing program from a conceptual model using the program generation logic 1204 is shown in FIG. 13 as a processing flow. Details of the processing flow of FIG. 13 will be described later.

  In step 1710, the business process program generation unit 110 determines whether all the data of the business process program generation table 1200 shown in FIG. 12 stored in the business process program generation rule database 112 has been processed. If not, the process ends. If not, the process moves to step 1706.

  An example of generating a business process program from a conceptual model using program generation logic will be described according to the process flow of FIG. The processing flow of the program generation logic shown in FIG. 13 is to generate an example of the program shown in FIG. 14B from the data of the conceptual model definition table 1100 shown in FIG. 11 created by the conceptual model generation unit 106.

  In step 1302, the program generation logic reads the data of the conceptual model definition table 1100 shown in FIG. At this time, only data including the product ID input to the part 2102 of the conceptual model display screen 2100 is read. For example, when the product ID input to the part 2102 of the conceptual model display screen 2100 is shn5678, data 1110 and data 1112 of the conceptual model definition table 1100 shown in FIG. 11 are read.

  In step 1304, the program generation logic is prepared in advance for each program generation logic 1204 of the business process program generation table 1200 in order to generate a business process program reflecting the data content of the conceptual model definition table 1100 read in step 1302. A business process program is generated using the business process program generation template to be executed. FIG. 14A shows a business process program generation template corresponding to the program generation logic 1210 that is data of the business process program generation table. Business processing including a function (insured person judgment function) for judging whether or not the judgment target 1402 as an argument shown in FIG. 14B is an insured person (true or false) by this business process program generation template A program is generated. Products that define locations such as 1410 product IDs enclosed in parentheses in the business process program generation template in FIG. 14 (a), 1412 contract element component designation information ID, and 1414 target insured persons in the conceptual model definition table 1100, respectively. The business processing program shown in FIG. 14B is generated in place of the values of ID 1104, risk collateral agreement element component designation information ID 1106 and concept content 1108. That is, shn5678, aa0123 and “named insured person” and “named insured person's spouse” in the business program of FIG. 14B are obtained from the conceptual model definition table 1100 and embedded in the program template. It is. Data of each transaction is input to “determination target” 1402.

  When selling a new insurance product in the insurance business, an insurance policy for a new insurance product contract is created. New insurance policies may be created by modifying the contents of existing insurance policies. In this case, according to the present invention, as long as it is possible to identify the changed portion of the insurance policy, it is possible to easily establish an insurance business system related to the new policy by simply exchanging a part of the parts constituting the existing policy information. Can be developed. In this way, maintenance of the insurance business system can be facilitated.

  Thus, according to the business system development method according to the contract of the present invention, it is possible to develop the business system according to the contract that accurately reflects the contents of the contract.

  In the above-described embodiment, insurance has been described as an example. However, the present invention is not limited to insurance, and can be applied to the development of a business system related to a contract, which is a contract clause for performing a routine processing of a contract.

It is a system configuration figure showing an example of the system configuration of the present invention. It is a system configuration figure showing an example of a computer system configuration concerning the present invention. It is a figure which shows an example of the table structure of a clause information database. It is a figure which shows an example of a structure and data of a clause element component table. It is a figure which shows an example of a structure and data of a clause element coupling | bond part table. It is a figure which shows an example of a structure and data of a merchandise information table. It is a figure which shows an example of a structure and data of a clause element component designation | designated information table. It is a figure which shows an example of a structure and data of a clause element joint component designation | designated information table. It is a figure which shows an example of a structure and data of a conceptual model generation rule table. It is a figure which shows an example of the processing flow of a model generation logic. It is a figure which shows an example of the structure and data of a conceptual model definition table. It is a figure which shows an example of the structure and data of a business process program generation table. It is a figure which shows an example of the processing flow of a program generation logic. It is a figure which shows an example of the business processing program generation template and the generated business processing program. It is a processing flow figure in a contract processing part which shows an example of a processing procedure. It is a processing flow figure in a conceptual model generation part which shows an example of a processing procedure. It is a processing flow figure in the business processing program generation part which shows an example of a processing procedure. It is an example of an agreement information edit screen. It is an example of a contract element component selection screen. It is an example of a contract element joint component selection screen. It is an example of a conceptual model display screen.

Explanation of symbols

  100: Covenant, 102: Program generating device based on the covenant, 104: Covenant information database, 106: Conceptual model generating unit, 108: Conceptual model database, 110: Business processing program generating unit, 112: Business processing program generating rule database, 114: Business processing program, 120: Program generation device, 300: General contract element part table, 302: General contract element connection part table, 304: Product information table, 306: General contract element part specification information table, 308: General contract element connection part specification information table

Claims (4)

Read out the information on the element parts that are constituent elements of the clauses from the clause information database on the storage device and the information on the specified connected parts that indicate the connection relationship between the element parts , Create a contract element coupling part designation information table having designation information of coupling parts between element parts expressing the logical structure of the clause, and store it in the clause information database;
For pre-Symbol Conditions component parts are registered in the specified information table component parts, by following from component parts through the coupling parts to other component parts with reference to the clause element coupling component indication information table, predetermined conditions Information relating to element parts that match the above, and generating information relating to the extracted series of element parts as a conceptual model and storing it in a conceptual model database on the storage device,
The conceptual model is read from the conceptual model database, information on element parts included in the conceptual model is embedded in a template of a predetermined program to generate a business processing program, and the generated business processing program is stored in the storage device A business system development method according to the general terms and conditions.   The business system development method according to claim 1, wherein the element part includes a word of the clause.   2. The business system development method according to the clause of claim 1, wherein a symbol indicating the element part and the joint part designated by a user is displayed on a display device.   2. The business system development method according to claim 1, wherein a system of a conceptual model representing a relationship between the conceptual model and another conceptual model is displayed on a display device.

Images