JP2004303117A - Name sorting database design support method and system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To design in a short time an extendable name sorting database corresponding to desired requirements by inputting basic data item definitions and requirements related to name sorting. <P>SOLUTION: This system comprises a means for defining table configuration before name sorting; a means for setting management requirements of data after name sorting; a means for defining table configuration after name sorting and link configuration related to a table after name sorting, referring to a data configuration pattern after name sorting corresponding to the management requirements of data after name sorting, with the set management requirements of data after name sorting as a retrieval key; a means for setting the management requirements of name sorting related data; and a means for defining name sorting related table configuration and link configuration related to a name sorting related table, referring to a name sorting related data configuration pattern corresponding to the management requirements of the name sorting related data and the management requirements of data after name sorting, with the management requirements of the name sorting related data and the management requirements of data after name sorting as a retrieval key. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a method and system for supporting the design of a name identification database in the construction of an information system of a company.
[0002]
[Prior art]
Name identification refers to associating a plurality of pieces of customer information managed by different numbers under predetermined conditions. Representative examples of merging include merging multiple pieces of customer information of the same customer and merging multiple pieces of information of another related customer.
[0003]
Name identification of the same customer is performed when the company has a plurality of transactions with the same customer at a plurality of sales offices, and the customer number and the customer information / transaction information are separately managed. If the name identification is not performed, the users in the company may not be able to handle customers appropriately because each customer information is treated as a separate customer. For example, mailing of merchandise information or the like to the same customer is duplicated, or a case where the customer is a good customer with a large transaction volume as a whole is overlooked.
[0004]
By identifying the same customer, the transaction status and attributes of the separately managed customers can be grasped in an integrated manner, which can be reflected in providing accurate sales and services.
[0005]
Examples of the name identification of related customers include household name identification for associating family members with individual customers, and associated company name association with related companies for corporate customers. Further, as an example of identifying individuals and corporate customers, there is a company name identification. The related customer name identification is effective for accurately grasping the customer's asset status, for example, when a financial institution makes a deposit or loan transaction with the customer.
[0006]
In recent years, in the business field, a concept called CRM (Customer Relationship Management) for managing a relationship with a customer in an integrated manner within a company and providing appropriate customer service has been emphasized, and the importance of name identification is increasing. I have.
[0007]
Usually, the name identification process is performed using an information system including a database in order to handle a large amount of customer data. Specifically, for the customer information stored in the database, using data items such as the customer name, address, and telephone number included in the customer information, the item values such as names and addresses of a plurality of customer records are used. After performing automatic comparison mechanically and merging customer records having the same item, the merging result is added to the customer information and stored in the database. Alternatively, there is a case where the operator operates the terminal and refers to the customer information on the screen to sequentially input a name identification instruction of a plurality of customer records in record units.
[0008]
As a software product related to merging of the prior art, a merging processing tool "Trillium (Trillium Software System is a registered trademark of Hart-Hanks Data Technologies, Inc.) developed by Hart-Hanks Technologies of the United States and developed by Agrex in Japan as a sales agent in Japan. Trademark or trademark) ". According to this product, data standardization and unification of items such as name and address can be performed, data matching can be performed, and name matching can be performed.
[0009]
Japanese Patent Application Laid-Open No. H11-191124 discloses a system configuration having a personal identification / household identification file identified by name or address (see Patent Document 1).
[0010]
[Patent Document 1]
JP-A-11-191124
[0011]
[Problems to be solved by the invention]
As a result of the name identification, in the database, it is necessary to additionally manage the data after the name identification and the data before the name identification and further manage the related data between the data after the name identification and the data before the name identification.
[0012]
Without the name identification database, it is impossible to collectively grasp the transaction status and attributes of the customer based on the name identification result. Further, unless the name identification-related data such as when and by what means the name identification is performed is used, the name identification cannot be used for an appropriate purpose. For example, if the system name was merged mechanically, it could not be used directly for contract affairs because the customer has not confirmed it. There is.
[0013]
If the name identification database is not designed as an appropriate structure according to the management requirements of the name identification data, there is a possibility that data may be duplicated or wasted, or that necessary data may not be managed. For example, if a configuration is adopted in which a parent customer number serving as a name identification destination is added as an item to a table for managing data before name identification and data after name identification is also managed in the same table, only one name identification destination can be specified. When two items are added to the same table so that two parent customer numbers can be held so that two name identification destinations can be specified, data items without two name identification destinations are not only wasteful, When the number of identification destinations increases to three or more, it is necessary to change the table configuration, and there is no extensibility.
[0014]
To enhance the accuracy of customer name identification processing, the conventional name identification processing tool "Trillium" provides a standardization function for item values used for name identification and a function to support comparison and evaluation of item values. There is no stipulation for the structure of the database that stores the.
[0015]
Another prior art "customer management system" states that the system configuration includes a contract master, a personal information creation unit, a personal information file, a personal name identification unit, a personal name identification information file, a household name identification unit, and a household name identification information file. However, it does not disclose a file or table configuration for storing the name identification result.
[0016]
The database structure depends on the unique requirements of the name identification process, such as whether you want to manage the post-name identification data as one of the data before the name identification, and whether the data before the name identification belongs to only one name identification. You need to be familiar. Further, even after the requirements have been clarified, it is necessary to be familiar with the database design in order to make the database structure corresponding to the requirements, which makes the work of designing the name identification database time-consuming and difficult. Further, if the design is made without considering this point, there is a possibility that data duplication or waste may occur as described above, or a data structure with poor expandability may be obtained.
[0017]
An object of the present invention is to provide a supporting method and system for designing a scalable collation database in a short time in response to a desired requirement only by inputting a basic item definition and a requirement by a designer. It is in.
[0018]
[Means for Solving the Problems]
The present invention associates a plurality of different records managing information on customers and contracts under predetermined conditions such as the same customer and related customers, and stores data related to name identification processing. A system for designing and supporting a name identification database comprising a table for storing related records and a link indicating the relation of items between the tables, and defines a pre-name identification table configuration for storing a name identification record which is a source of the name identification. Means for setting management requirements for post-name identification data, which is data relating to the name of the pre-name identification record after the name identification, and post-name identification data management previously stored in the storage device using the set management requirements for the name identification data as a search key. A name that stores records related to data after name identification by referring to the data configuration pattern after name identification according to requirements Means for defining a post-comparison table configuration and a link configuration for the post-comparison table; means for setting management requirements for data related to the pre-comparison data, which is data representing pre-comparison data and post-comparison data; Using the data management requirements and the post-comparison data management requirements as search keys, refer to the merging-related data management requirements stored in the storage device in advance and the merging-related data configuration patterns corresponding to the post-comparison data management requirements, and perform And a means for defining a link configuration related to the name identification related table for storing records related to data.
[0019]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, embodiments of the present invention will be described with reference to the drawings.
[0020]
FIG. 1 shows a processing flow of the present embodiment.
[0021]
FIG. 2 illustrates a configuration example of a name identification database design support system 200 that executes the processing flow of the present embodiment. The name identification database design support system 200 is an example implemented by a combination of a computer and a program.
[0022]
The computer includes an arithmetic processing device 201, an input device 202, a storage device 203, and an output device 204.
[0023]
The program of the name identification database design support system of the present invention is stored in a storage medium such as a CD-ROM, a semiconductor memory, or a hard disk or the storage device 203, and is called and executed by the arithmetic processing unit 201 during processing. The screen of the present invention is output to the output device 204, and information is input to the screen using the input device 202. Intermediate data and design result information during the processing are stored in the storage device 203.
[0024]
Since the program configuration, screen configuration, and storage data configuration of the name identification database design support system 200 are the same as those in FIG. 1, the description will be made according to the processing flow in FIG.
[0025]
Next, a processing flow according to the embodiment of the present invention will be described with reference to FIGS. An example used in the embodiment of the present invention is an example of designing a name identification database of an individual customer.
<Step 101> Definition of table configuration before merging
Define a table configuration of a pre-name identification table that stores customer records before the name identification to be identified. Specifically, the system outputs a definition screen 300 of the pre-name comparison table configuration to the output device 204, and acquires and defines the pre-name comparison table configuration input from the input device 202 on the screen 300.
[0026]
FIG. 3 shows an example of a definition screen of the pre-name comparison table configuration. The pre-comparison table configuration definition screen 300 includes a table name input area 301 for storing pre-comparison customer records, a name input area 302 for defining each item of pre-comparison data, presence / absence of a primary key, type, and number of digits. Input areas 303 to 305, an input completion button 306, and an input cancel button 307. The primary key is an item in which each record of the table can be identified by the value of the item, and at least one item in the table needs to be the primary key. The type indicates whether the item stores a character value or a numeric value.
[0027]
By using the input device 202, for example, “customer” is entered in the table name input area and “customer number”, “customer name” and “customer name” are entered in the item definition areas 302 to 305 on the pre-name comparison table configuration definition screen 300. An address, etc., its type and the number of digits are input, and an input completion button 306 is pressed, thereby inputting the definition of the pre-name identification table configuration. The input pre-name comparison table configuration is stored in the storage device 203 as a name comparison DB definition 400 which is name comparison database design information.
[0028]
The storage format of the name identification DB definition 400 may be, for example, a table format output on the definition screen 300 of the pre-name identification table configuration, but may be a general SQL language format or an ER diagram format as a description format of the database design information. You may. The SQL language is a relational database language that can describe queries for database definition and operation. Since the SQL language is adopted as a standard by the International Organization for Standardization, and most relational database management systems are equipped with functions, the database is defined for the relational database management system by storing the name identification DB definition in the SQL language format. It becomes easier. 401 shows an example in which the name identification DB definition 400 is described in the SQL language format. CREATE TABLE indicates that the table is defined, and includes a table name “customer” and a definition of an item belonging to the table “customer number CHAR (10) PRIMARY KEY,...”. PRIMARY KEY indicates that the item is a primary key.
[0029]
The ER diagram format is a schematic representation for making the data structure intuitively understandable, and can be converted to a SQL language format. Reference numeral 402 denotes an example in which the name identification DB definition 400 is described in the ER diagram format. In the ER diagram, the table is represented by a rectangle, and the rectangle is separated by a line, and the upper section describes the primary key item definition, and the lower section describes the item definitions other than the primary key.
[0030]
The storage format of the name identification DB definition 400 may be a format other than the SQL language format or the ER diagram format as long as it can express the database structure. Hereinafter, in the drawings of the present description, the data structure is described in the ER diagram format with emphasis on visual clarity.
<Step 102> Setting of data management requirements after name identification
Set the management requirements for post-name identification data, which is data after name identification of pre-name identification records. The post-name identification data is information managed in common by the post-name identification group, such as the total number of pre-name identification records identified in the post-name identification record, and in the case of household identification, the household head name.
[0031]
The system outputs a post-name identification data management requirement setting screen 500 to the output device 204, and sets the post-name identification data management requirement 510 on the screen 500 based on the input from the input device 202.
[0032]
FIG. 5 shows an example of a setting screen 500 for data management requirements after name identification. The setting screen 500 of the post-name identification data management requirement includes, as management conditions of post-name identification data, a form in which post-name identification data is not managed, a form in which one of the pre-name identification records is used as a parent after name identification, and There is an area 501 for selecting a form for creating a new post-name record and managing post-name data. Further, an input completion button 502 and an input cancel button 503 are provided.
[0033]
By using the input device 202, a requirement is selected and input from an input area 501 of a post-name identification data management requirement setting screen 500, and an input completion button 502 is pressed, thereby setting the name identification data management requirement 510. The set post-name identification data management requirement 510 is stored in the storage device 203.
<Step 103> Definition of table configuration and link configuration related to data after name identification
A table configuration relating to post-name identification data, with reference to the post-name identification data management requirement 510 set in step 102 as a search key, and referring to the post-name identification data configuration pattern 600 for each post-name identification data management requirement stored in the storage device 203 in advance, A link configuration from the pre-name comparison table set in step 101 to the post-name comparison table is defined.
[0034]
FIG. 6 shows an example in which a post-name identification data configuration pattern 600 for each data management requirement is expressed in a table format. The post-name identification data configuration pattern 600 includes a post-name identification data management requirement field 601, a generation table type field 602, a generation link type field 603, a generation link start point table field 604, and a generation link end point table field 605.
[0035]
The post-comparison data management requirement field 601 stores a value corresponding to the post-comparison data management requirement 510 set in step 102 in each record. The generation table type field 602 stores a value indicating no if there is no table to generate, and stores a value indicating the table type if there is a generation table. The table type is one of two before and after the name identification. The generated link type field 603 stores a value indicating no link if there is no link to be generated, and stores a value indicating the link type if there is a generated link. A link is a means for associating two tables. There are three types of links according to the format in which the primary key item of the table serving as the starting point is used as an item of the table serving as the ending point. The subtype format used as the same primary key item even in the table where the primary key item is the end point, and the dependency where the primary key item of the start point table is used as one of the primary key items of the end point table There are a format and a non-dependent format in which the primary key item of the starting table is used as an item that is not the primary key of the ending table. 604 and 605 store values indicating the table type serving as the starting point of the generated link and the table type serving as the ending point, respectively.
[0036]
The post-name identification data management requirement field 601 of the post-name identification data configuration pattern 600 is searched using the post-name identification data management requirement 510 set in step 102 as a search key, and the generation link type is generated from the generation table type field 602 of the record corresponding to the requirement. The values up to the end point field 605 are referred to. Define the table configuration and link configuration related to the post-name identification data according to the referenced values.
[0037]
For example, assuming that the value is “1” when the post-name identification data management requirement 510 has no post-name identification data, the record 610 of the post-name identification data configuration pattern 600 corresponds to the example of FIG. In the record 610, the value of the generation table type field 602 is “none”, and the value of the generation link type field 603 is “none”. In other words, the record 610 expresses that if the post-name identification data management requirement 510 has no post-name identification data, the table and link related to the post-name identification data are not generated.
[0038]
Similarly, when the post-name identification data management requirement 510 manages data of one of the pre-name identification records as a parent after the name identification, the record 620 generates a post-name identification table and links the subtype format from the pre-name identification table. It expresses that it is created in the table after name identification. The record 630 indicates that when the post-name identification data management requirement 510 creates a new post-name identification record and manages the post-name identification data, a post-name identification table is generated and no link is generated.
[0039]
In the patterns of the records 620 and 630, in order to generate the post-name comparison table, the definition screen 700 of the post-name comparison table configuration is output to the output device 204, and the post-name comparison table configuration input from the input device 202 is displayed on the screen 700. Get and define.
[0040]
FIG. 7 shows an example of a definition screen of the table configuration after name identification. The post-comparison table configuration definition screen 700 includes a table name input area 701 for storing post-comparison customer records, and a name input area 702 for defining each item of post-comparison data. It comprises input areas 703 to 705 relating to numbers, an input complete button 706, and an input cancel button 707. Each input area is the same as that of the pre-name comparison table configuration definition screen 300, and thus the description is omitted.
[0041]
However, the difference from the pre-comparison table configuration definition screen 300 is that when the post-comparison data management requirement 510 manages data of one of the pre-comparison records as the parent after the comparison, as described above, In order to generate a link in the subtype format to the table after the name identification, the definition of the primary key item is that the primary key item of the pre-name identification table of the name identification DB definition 400 defined in step 101 is defined as it is. In other words, it is impossible to change the definition of the pre-merge table defined in step 101 for the presence or absence of the primary key, the type of the primary key, and the number of digits. For the primary key item, only the item name can be changed from the item name input area 702 of the screen 700.
[0042]
The items other than the primary key and the definition of the table name are input to each of the input areas 701 to 705 of the post-name comparison table configuration screen 700 using the input device 202, and the input completion button 706 is pressed. Enter the configuration definition.
[0043]
The input post-comparison table configuration and the link configuration referred to from the post-comparison data configuration pattern 600 are additionally stored in the companion DB definition 400, which is the companion database design information, and stored in the storage device 203 as the companion DB definition 800. The name identification DB definition 800 and the definition of the table configuration and link configuration relating to post-name identification data are added to the name identification DB definition 400, and may be overwritten and updated.
[0044]
The name identification DB definition 800 has a structure according to the three data management requirements after name identification. In accordance with the post-name identification data management requirements, the database structure in the case where the post-name identification data is not managed is designated by reference numeral 801, the name comparison database structure in which one of the records before the name identification is managed as the parent after the name identification is designated by reference numeral 802, and the record after the name identification is newly designated A reference numeral 803 shows a structure of a name identification database in which data is created and data after name identification are managed. Reference numeral 801 includes only a pre-name comparison table “customer”. Reference numeral 802 denotes a pre-comparison table “customer” and a post-comparison table “comparison parent customer”, and a subtype link from the pre-comparison table to the post-comparison table. Reference numeral 803 includes a table “customer” before the name identification and a table “household” after the name identification, and has no link.
[0045]
As described in step 101, the name identification DB definition 800 is described in the ER diagram format, but can also be described in the SQL language format. In the example of the subtype 802, the link can be expressed in the SQL language format as follows.
Alter Table Name Matching Parent Customer
ADD FOREIGN KEY (customer number)
REFERENCES Customers
ON DELETE CASCADE;
In the case of a link of a dependent format, “RESTRICT” may be used instead of “CASCADE”, and in the case of a link of a non-dependent format, “SET NULL” may be used instead of “CASCADE”.
<Step 104> Setting management requirements for name identification related data
A management requirement for name-related data, which is data representing the name-related data between the pre-name record and the post-name record, is set. The name identification-related data is information relating to the date when each record before name identification was merged with the record after name identification, the name identification method, and the like.
[0046]
The system outputs a name-related data management requirement setting screen 900 to the output device 204, and sets the name-related data management requirement 910 on the screen 900 based on the input from the input device 202.
[0047]
FIG. 9 shows an example of a setting screen 900 for setting the name-related data management requirements. The setting screen 900 of the data management requirement after the name identification includes, as management requirements of the data related to the name identification, a form in which the record before the name identification is merged into only one record after the name identification, and a form in which the record before the name identification is merged into a plurality of records after the name identification. There is an area 901 for selecting one of the above. Further, an input completion button 902 and an input cancel button 903 are provided.
[0048]
An example in which a pre-name record is merged into a single post-name record is a case where individual customers are merged in one household and not in other households. An example in which a pre-name record is merged into a plurality of post-name records is an affiliate company name of a corporate customer, in which one company is funded by a plurality of companies and is merged with a plurality of affiliate companies.
[0049]
The input device 202 is used to select and enter a requirement from the input area 901 of the setting screen 900 of the name-related data management requirement, and press the input completion button 902 to set the name-related data management requirement 910. The set name identification related data management requirement 910 is stored in the storage device 203.
<Step 105> Definition of Table Configuration and Link Configuration Related to Merging Related Data With reference to the merging related data management requirement 910 set in step 104 as a search key, reference is made to the merging related data configuration pattern 1000 stored in the storage device 203 in advance. A table configuration related to the name identification related data and a link configuration from the pre-name comparison table set in step 101 and the post-name comparison table set in step 103 to the name identification related table are defined.
[0050]
FIG. 10 shows an example in which a name identification related data configuration pattern 1000 for each name identification related data management requirement is expressed in a table format. The name identification related data configuration pattern 1000 includes a name identification related data management requirement field 1001, a post-name identification data management requirement field 1002, a generation / storage table type field 1003, a generation link type field 1004, a generation link start point table field 1005, and a generation link. And an end point table field 1006.
[0051]
The name-related data management requirement field 1001 stores a value corresponding to the name-related data management requirement 910 set in step 104 in each record, and the post-name data management requirement field 1002 stores the value after the name management set in step 102. The value corresponding to 510 is stored in each record. The generation / storage table type field 1003 stores a value indicating “none” if there is no table to generate / store, and indicates the table type if there is a generation / storage table.
[0052]
As shown in FIG. 10, the generation / storage table type field 1003 may take two types of values other than “none”, that is, “before name identification” and “name identification related”. If the value is “name-related”, a name-related table is generated. If the value is “before name”, the name-related table is already generated in step 101. It will be stored in the previous table.
[0053]
The generated link type field 1004 stores a value indicating no link if there is no link to be generated, and stores a value indicating the link type if there is a generated link. Reference numerals 1005 and 1006 store values indicating the table type as the start point of the generated link and the table type as the end point, respectively. The table type is any one of three before, after and after name identification.
[0054]
Using the name-related data management requirement 910 set in step 104 as a search key, the name-related data management requirement field 1001 of the name-related data configuration pattern 1000 is searched, and the post-name data management requirement 510 set in step 102 is used as a search key. First, the values from the generation / storage table type field 1003 to the generation link end point field 1006 of the record corresponding to the post-name management requirement field 1002 are referred to. Define the table configuration and link configuration related to the post-name identification data according to the referenced values.
[0055]
For example, the value “1” when the value of the form in which the record before the name identification is merged into the only record after the name identification is “a” and the data management requirement 510 after the name identification has no data after the name identification is “1”. Then, in the example of FIG. 10, the record 1010 of the post-name identification data configuration pattern 1000 corresponds to this. In the record 1010, the value of the generation / storage table type presence / absence field 1003 is “before name identification”, the value of the generation link type field 1004 is “independent”, and the value of the generation link start point table field 1005 is “before name identification”. , The value of the generated link end point field 1006 is “before name identification”. That is, the record 1010 expresses that the table definition related to the post-name comparison data is defined in the pre-name comparison table, and that a link in a non-dependent format is generated from the pre-name comparison table to the pre-name comparison table. The same applies to the following patterns, and a description thereof will be omitted. However, the name-related data management requirement 910 is such that the value of the form in which the record before the name comparison is merged into a plurality of records after the name identification is “b”, and the data management requirement 510 after the name comparison uses one of the records before the name identification as the parent and Assuming that the case of managing data is “2”, in the example of FIG. 10, two records 1050 and 1060 of the post-name identification data configuration pattern 1000 correspond. This means that the contents of two records are generated.
[0056]
The post-name identification data configuration pattern 1000 is a pattern for a total of six, which is a combination of three post-name identification data management requirements and two name identification-related data management requirements. In any of the patterns, since the generation / storage table type exists, the definition screen 1100 of the name identification related table configuration is output to the output device 204, and the name identification relevant table configuration input from the input device 202 is acquired on the screen 1100. Define.
[0057]
FIG. 11 shows an example of a definition screen of the configuration of the name identification related table. The name identification related table configuration definition screen 1100 includes a table name input area 1101 for storing name identification related data, and a name input area 1102 for defining the items of the name identification related data. Input areas 1103 to 1105, an input completion button 1106, and an input cancel button 1107. Each input area is the same as that of the pre-name comparison table configuration definition screen 300, and thus the description is omitted.
[0058]
However, the difference from the pre-comparison table configuration definition screen 300 is that if the pre-comparison record management requirement 910 is such that the pre-comparison record is merged into a single post-comparison record, as described above, Is stored in the pre-comparison table, the table name is set to the name of the pre-comparison table set in step 101, and cannot be changed from the screen 1100.
[0059]
In addition, when the name identification related data management requirement 910 is such that the record before the name identification is merged into a plurality of records after the name identification, the dependency on the name identification related table from the table before the name identification or the table after the name identification is determined according to the pattern 1000 of the name identification related data. Since the format link is generated, the definition of the primary key item is that the primary key items of the before-name comparison table and the after-name comparison table of the name identification DB definition 800 are defined as they are. It is impossible to change the presence / absence, type, and number of digits of the primary key item, and only the item name of the primary key item can be changed from the item name input area 1102 of the screen 1100.
[0060]
The items other than the primary key and the definition of the table name are input to the input areas 1101 to 1105 of the name identification related table configuration definition screen 1100 using the input device 202, and the input completion button 1106 is pressed. Enter the configuration.
[0061]
The input name identification related table configuration and the link configuration referred to from the name identification related data configuration pattern 900 are additionally stored in the name identification DB definition 800 which is the name identification database design information, and stored in the storage device 203 as the name identification DB definition 1200.
[0062]
The name identification DB definition 1200 has a structure corresponding to six, which is a combination of three data management requirements after name identification and two data management requirements related to name identification. The database structure when the record before the name identification is merged into the only record after the name identification and the data after the name identification is not managed is set to 1201. The database structure for managing data is referred to as 1202, the pre-name record is merged into a single post-name record, and the database structure for managing the post-name data in a new name record is referred to as 1203. In the case where the database structure in which the name of the record before the name identification is not managed and the data after the name identification is not managed is 1204, the record before the name identification is merged with a plurality of records after the name identification, and the data after the name identification is managed using one of the records before the name identification as a parent Database structure of 120 , The name identification prior record is the name identification to a plurality of name identification after record shows the database structure of managing name identification data after a new name identification after record in 1206.
[0063]
Reference numeral 1201 includes a pre-name comparison table “customer” and an independent link from the pre-name comparison table to the pre-name comparison table. Reference numeral 1202 denotes a pre-name comparison table “customer” and a post-name comparison table “name comparison parent customer”. A sub-type link from the pre-name comparison table to the post-name comparison table, and an independent link from the post-name comparison table to the pre-name comparison table. There is. Reference numeral 1203 denotes a pre-name comparison table “customer” and a post-name comparison table “household”, and a link from the post-name comparison table to the pre-name comparison table. Reference numeral 1204 denotes a name comparison table “customer” and a name identification related table “name identification related”, and two links from the name comparison table to the name identification related table. Reference numeral 1205 denotes a pre-comparison table “customer”, a post-comparison table “comparison parent customer”, and a comparison table “comparison”, and a link from the pre-comparison table to the comparison table and a post-comparison table to the comparison table. There is a link. Reference numeral 1206 denotes a pre-comparison table “customer”, a post-comparison table “household”, and a comparison table “comparison”, and a link from the pre-comparison table to the comparison table and a link from the post-comparison table to the comparison table. There is.
[0064]
The name identification DB definition 1200 created by the above processing is design result information of the name identification database.
[0065]
As described above, according to the present embodiment, in the design of the name identification database, the structure of the data before the name identification, the data after the name identification, and the data associated with the name identification are acquired, and by using the name identification management requirement pattern, the data of the name identification easily can be obtained. It is possible to design a name identification database corresponding to management requirements and management requirements for name identification related data.
[0066]
In addition, since the name identification pattern has a normalized data structure, there is no waste such as duplication of data as shown in FIG. 12, and a scalable database can be designed.
[0067]
In the processing flow of the above-described embodiment, the processing is performed in the order of steps 101 to 105. However, as is clear from the relationship between input and output data of each processing, the step 104 of setting the name-related related data management requirements includes a table relating to the data after name matching. Alternatively, the processing before the link configuration definition step 103 may be performed. Further, the processing order of the definition step 101 of the pre-name identification table configuration, the setting step 102 of the post-name identification data management requirement, and the processing step 104 of setting the name identification related data management requirement may be any order.
[0068]
In the above-described embodiment, an example of designing a database for individual customers in a company is described. However, in the case of a corporate customer, the name of a related company or a corporate group can be obtained by using the pre-name data as the corporate customer. Is applicable.
[0069]
【The invention's effect】
As described above, according to the present invention, in the design of the name identification database, the management requirements of post-name identification data and the management requirements of the name identification related data can be easily met, and the design of the scalable name identification database becomes easy.
[Brief description of the drawings]
FIG. 1 is an overall processing flow of a name identification database design support system according to the present invention.
FIG. 2 is a configuration diagram of a name identification database design support system according to an embodiment of the present invention.
FIG. 3 is an example of a definition screen of a table configuration before merging in the embodiment of the present invention.
FIG. 4 is an example of a file configuration of a name identification DB definition relating to a pre-name identification table in the embodiment of the present invention.
FIG. 5 is an example of a management requirement setting screen for post-name identification data in the embodiment of the present invention.
FIG. 6 is a file configuration example of a data structure pattern after name identification according to the embodiment of the present invention.
FIG. 7 is an example of a definition screen of a table configuration after name identification in the embodiment of the present invention.
FIG. 8 is a file configuration example of a name identification DB definition relating to a pre-name identification table and a name identification table in the embodiment of the present invention.
FIG. 9 is an example of a management requirement setting screen for name identification related data in the embodiment of the present invention.
FIG. 10 is a file configuration example of a name identification related data configuration pattern in the embodiment of the present invention.
FIG. 11 is an example of a definition screen of a name identification related table configuration in the embodiment of the present invention.
FIG. 12 is a file configuration example of a name identification DB definition relating to a pre-name identification table, a name identification table, and a name identification related table in the embodiment of the present invention.
[Explanation of symbols]
101: Means for defining a pre-comparison table configuration, 102: Management requirement setting means for post-comparison data, 103: Table relating to post-comparison data, link configuration definition means, 104: Management requirement setting means for comparison-related data, 105: Merging related data Table and link configuration definition means.

Claims (9)

A table for storing records related to the name identification processing, in order to store data related to the name identification processing, which associates a plurality of different records managing information on customers and contracts under predetermined conditions related to the same customer or related customers. And a system for supporting the design of a merging database consisting of links indicating the relation of items between the tables,
A means for defining a pre-comparison table configuration that stores a pre-comparison record that is a source of the merging to be designed,
Means for setting management requirements of post-name identification data, which is data after name identification of the pre-name identification record,
Using the set management requirements for post-name identification data as a search key, referencing a post-name identification data configuration pattern corresponding to the post-name identification data management requirements stored in the storage device in advance, and storing a record relating to post-name identification data in a post-name comparison table configuration And means for defining a link configuration for the post-name identification table;
Means for setting management requirements for the name identification-related data, which is data representing the name identification-related contents of the data before the name identification and the data after the name identification,
With the set management requirements for the name identification related data and the management requirements for the name identification data as search keys, refer to the name identification related data management requirements stored in the storage device in advance and the name identification related data configuration pattern according to the name identification data management requirements. And a means for defining a link configuration relating to a name-related table storing a record relating to the name-related data, and a link configuration relating to the name-related table.
A name identification database design support system comprising: The definition of each table configuration related to before, after, and after name identification according to claim 1,
In the database design, it is a definition about the table name, the name of the item belonging to the table, the type, the number of digits, and whether the primary key is applicable,
A name identification database design support system characterized by the following. The definition of the link configuration according to claim 1 is:
In the database design, to define a table as a starting point of a link, a table as an ending point of the link, and a type of the link, which are the configuration targets,
The link types include three types of primary key items of a table serving as a starting point depending on a format used as an item of a table serving as an ending point.
The primary key item of the table that is the starting point is the subtype format used as the same primary key item in the table that is the ending point,
A dependency format in which the primary key item of the starting table is used as one of the primary key items of the ending table;
There is a non-dependent format in which the primary key item of the starting table is used as a non-primary key item of the ending table.
A name identification database design support system characterized by the following. The post-name identification data according to claim 1,
Such as the total number of records before the name identification,
A name identification database design support system characterized by the following. The name identification-related data according to claim 1,
A name identification database design support system, characterized by a name identification date, a name identification method, and the like, in which each pre-name identification record is identified with respect to a post-name identification record. The management requirements for post-name identification data according to claim 1 are:
Whether to manage the data after the name identification, or to manage the data after the name identification as a parent of one of the records before the name identification, or to manage the data after the name identification as a new record after the name identification, one of the requirements,
The post-name identification data configuration pattern is:
When the set management requirements of the post-name identification data do not manage the post-name comparison data, the post-name comparison table configuration and the link configuration are not defined,
In the case where the set management requirements for post-name identification data are to manage post-name comparison data using one of the pre-name comparison records as a parent, a post-name comparison table configuration is defined, and a subtype link from the pre-name comparison table to the post-name comparison table is provided. Defining the configuration,
In the case where the set management requirements of the post-commercial data manage post-comparison data as a new post-comparison record, a post-comparison table configuration is defined, and a link configuration is not defined.
The management requirements for the name identification-related data are as follows:
Either the pre-name record is merged into a single post-name record, or the pre-name record is merged into one or more post-name records.
The name identification related data configuration pattern,
In the case where the set management requirement of the name identification related data is that the record before the name identification is merged into only one record after the name identification, the name identification related table configuration is defined and included in the table configuration before the name identification,
In addition, when the post-name identification data management requirement is that there is no post-name identification data management, defining a link configuration in an independent form from the name identification table to the name identification table,
Alternatively, when the management requirement of the post-name identification data is to manage the post-name identification data by using one of the records before the name identification as a parent or to manage the post-name identification data as a new post-name identification record, Defining an independent link structure from the table to the pre-name table,
When the management requirements for the name identification related data are such that the record before the name identification is merged into one or more records after the name identification, a configuration of the name identification related table is defined, and the dependency format from the table before the name identification to the name identification associated table is defined. Defining the link configuration,
In addition, when the management requirement of the post-comparison data is no management of post-comparison data, defining a link configuration in a dependent format from the pre-comparison table to the comparison table,
When the set management requirements of the post-comparison data are to manage the post-comparison data using one of the pre-comparison records as a parent or to manage the post-comparison data as a new post-comparison record, Is a pattern showing that a link configuration in a dependent form to a related table is defined,
A name identification database design support system characterized by the following. The name identification database design support system according to claim 1,
Means for outputting the table configuration and the link configuration of the set name identification database in a database definition statement in an SQL language format or an ER diagram format;
A name identification database design support system characterized by the following. Stores the records related to the name identification process, in order to store data related to the name identification process, which associates a plurality of different records managing information on customers and contracts under predetermined conditions such as the same customer and related customers. A method for supporting the design of a merging database comprising a table to be linked and a link indicating an association between items between the tables,
A pre-comparison table configuration that stores a pre-comparison record that is a source of the merging to be designed is defined,
The data relating to after the name identification of the record before the name identification, set the management requirements of the data after the name identification,
Using the set management requirements for post-name identification data as a search key, referencing a post-name identification data configuration pattern corresponding to the post-name identification data management requirements stored in the storage device in advance, and storing a record relating to post-name identification data in a post-name comparison table configuration And define a link configuration for the post-name identification table,
The management requirements of the name identification related data, which is data representing the name identification related content between the data before the name identification and the data after the name identification,
With the set management requirements for the name identification related data and the management requirements for the name identification data as search keys, refer to the name identification related data management requirements stored in the storage device in advance and the name identification related data configuration pattern according to the name identification data management requirements. Then, a name identification related table configuration that stores records related to the name identification related data and a link configuration related to the name identification related table are defined.
A method for supporting the design of a name identification database. In order to store data relating to the name identification process, which associates a plurality of different records managing information relating to customers and contracts under predetermined conditions such as the same customer or related customers, the record relating to the name identification is stored. A program for causing a computer to implement a function of supporting design of a table and a name identification database including links indicating the relations of items between the tables,
A function for defining a pre-comparison table configuration that stores a pre-comparison record that is a source of the merging to be designed,
A function for setting management requirements for post-name identification data, which is data after name identification of the pre-name identification record,
Using the set management requirements for post-name identification data as a search key, referencing a post-name identification data configuration pattern corresponding to the post-name identification data management requirements stored in the storage device in advance, and storing a record relating to post-name identification data in a post-name comparison table configuration And a function for defining a link configuration for the post-name identification table,
A function for setting management requirements for the name identification related data, which is data representing the name identification related content between the data before the name identification and the data after the name identification,
With the set management requirements for the name identification related data and the management requirements for the name identification data as search keys, refer to the name identification related data management requirements stored in the storage device in advance and the name identification related data configuration pattern according to the name identification data management requirements. And a function to define a link structure related to a name-related table that stores records related to the name-related data, and a link structure related to the name-related table.
For causing the computer to realize the above.

Images