JPH07281882A - Data base normalization support device - Google Patents

Abstract

PURPOSE:To obtain a support device which can design a data base that is easily normalized on an interactive basis by extracting an unregistered key candidate from key items of key candidates as candidates for normalization and displaying it as the identifier pattern together with a selected item. CONSTITUTION:This device is equipped with a repetitive part-divided information storage part 106 for the normalization in the data base, and a table is taken out of a table group in the repetitive part-divided information storage part 106. Registered keys are extracted from name items of the extracted table and the key candidate which is not registered is extracted from the key obtained by combining the extracted registered key items. The extracted key candidate is displayed as the identifier pattern on an input/output device 101 and the data item belonging to the registered keys as a new selection items of the identifier pattern. The new key specified among the displayed identifier patterns and data belonging to the new key are normalized and integrated in an integration result storage part 116.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an apparatus for efficiently supporting normalization work when designing a database of an information system.

[0002]

2. Description of the Related Art FIG. 21 shows, for example, Japanese Patent Application Laid-Open No. 2-27833.
This is the conventional database generation support method disclosed in Japanese Patent Laid-Open No. In the figure, 101 is an input / output device for inputting or outputting information necessary for this database generation support method from the outside, 2101 is an existing program storage unit containing an existing COBOL source code, 2102
Is an existing program analysis part that extracts the data part of the source code in the existing program storage part and estimates data items that are considered to have the same content from the comparison sentence and transfer sentence of the procedure part. Reference numeral 2103 denotes an existing file record information storage unit that stores the data portion extracted by the existing program analysis unit illustrated in FIG. 22. Reference numeral 2104 indicates the same content in the existing program analysis unit illustrated in FIG. A data item related information storage unit that stores data items. 21
Reference numeral 05 denotes a data item standardization unit that newly names data items to be unified as the same content, and 2106 is a standardized file record information storage unit that stores the unified and newly named data items, an example of which is shown in FIG. is there. Two
Reference numeral 107 is a relation extraction unit for extracting relation information from the contents of the standardized file record information storage unit, 21
Reference numeral 08 denotes a relation storage unit that stores the extracted relation information, an example of which is shown in FIG. 25, and 2109 is a relation normalization unit that performs the first to third normalization operations. Reference numeral 2110 is a relation integration unit that integrates relation information having the same key and gives a new name. 211
26 shows an example thereof in FIG. 26. An integrated relation storage unit 2112 for storing the integrated and newly named relation information is a logical schema information creating unit 2112 for creating the logical schema information of the database. It is a database logical schema information storage part which stores the created logical schema information which shows an example.

Next, the operation will be described. In such a conventional database generation support method, the data portion of the program source code of the existing program storage unit 2101 is extracted by the existing program analysis unit 2102 to collect data items, and the existing file record information storage unit 21 is collected.
Accumulate in 03. In addition, the existing program analysis unit 2 sets the data items that are considered to have the same contents as the comparison sentence and the transfer sentence of the Procedure Division.
It is estimated at 102 and stored in the data item related information storage unit 2104. Next, in the data item standardization unit 2105, the input / output device 1 is based on the contents of the existing file record information storage unit 2103 and the data item related information storage unit 2104.
The data item standardization instruction is input from 01, and the data item standardized by the designation is stored in the standardized file record information storage unit 2106.

Next, the relation extraction unit 2107 extracts relation information, which is table information of data items, from the standardized file record information storage unit 2106,
The relation normalization unit 2109 inputs the result of normalization to the relation information from the input / output device 101, and stores it in the relation storage unit 2108. Next, the relation integration unit 2110 integrates those having the same key in the relation storage unit 2108, gives a new name to the relation information integrated by the input / output device 101, and stores it in the integrated relation storage unit 2111. Finally, the logical schema creation unit 2112 creates database logical schema information and stores it in the database logical schema information storage unit 2113.

Here, the normalization is to classify and classify the data items into entities to which the data should be originally belonged (persons, places, events, concepts, etc., which collectively represent what one wants to manage in business), and as a result. Suppose it is a process that leads to a sophisticated and simple data structure. Alternatively, it is assumed that a separate file is created with a repeating portion configured by repeating items for each entity. When normalization is performed, it is created by dividing into three levels of first normalization, second normalization, and third normalization. It can be said that the first normalization is an entity configured so as not to include other entities. Second
Normalization can be said to be an entity that satisfies the first normalization and that all data items in the entity are subordinate to all key items that identify the entity. It can be said that the third normalization is an entity that satisfies the second normalization and that data items in the entity do not depend on data items other than key items.

[0006]

The conventional method as described above has a problem that a designer having a normalization technique must manually perform the normalization work. In addition, there is a problem that the existing program source code must exist in order to collect the data items necessary for designing the database.

The present invention has been made to solve the above problems, and it is an object of the present invention to obtain a support device capable of designing a database which has been easily normalized in an interactive manner in the database normalization work. And

[0008]

A database normalization support apparatus according to the present invention creates a table from a repeating partial division information storage means for normalization in a database and a table group in the repeated partial division information storage means. A means for extracting and extracting a registered key from each item of the extracted table, a means for extracting an unregistered key candidate from the combined key of the extracted registered key items, and this extraction Means for displaying the selected key candidate as an identifier pattern, and a data item subordinate to the registered key as a new selection item of the identifier pattern, and a specified new key in the displayed identifier pattern, A result integrated storage means for normalizing the data dependent on the new key is provided.

Furthermore, the already registered single key item of the table in the repeated partial division information storage means is deleted from the key candidates extracted for displaying as the identifier pattern and displayed.

The database normalization support apparatus according to the present invention is an identifier term storage means for selecting an identifier that is a candidate that can be a key for normalizing a table in a database, and registration of a repeated portion of this normalization. Repeated subdivision information storage means that contains a table of stored keys and data items dependent on that key, and a table is extracted from the table group in this repeated subdivision information storage means, and each data item of the extracted table is extracted. Then
Means for checking whether the extracted data item includes an identifier in the identifier term storage means, and a new identifier guide when the extracted data item includes an identifier in the identifier term storage means, and A means for displaying the key and the data item subordinate to the key, and a result integrated storage means for normalizing the designated new key in the displayed identifier pattern and the data subordinate to the new key are provided.

Furthermore, a suffix is registered to select an identifier that is a candidate that can be a key for normalizing a table in the database, and the identifier term storage means is the identifier suffix storage means, and the repeated partial division information is used. The comparison with the data item extracted from the storage means is made as to whether or not the data item includes the suffix.

[0012]

In the database normalization support device according to the present invention, unregistered key candidates are extracted from the key items in the keys considered to be normalization candidates, and are displayed as an identifier pattern together with the selected items. This makes it easy to give an instruction and normalizes the instruction.

Furthermore, when extracting a key candidate, a single key item that has already been registered is removed and output to facilitate selection.

In the database normalization support device according to the present invention, a registered identifier that can be a key for normalization is compared with a data item subordinate to the already registered key, and a new key candidate is selected. The identifier guide is output and displayed together with the selected items. This makes it easy to give an instruction and normalizes the instruction.

Furthermore, when extracting a key candidate, extraction is performed by comparing the registered suffix with a data item containing the same suffix.

[0016]

【Example】

Example 1. In the present embodiment, a layout form in which it is easy to see which part is the normalized part is displayed on the screen, and the screen is used as it is to specify the key for the normalization and the data items subordinate to it as the input screen. Now, create a split file that is normalized based on that specification. FIG. 1 is a diagram for explaining the overall configuration and operation of a database normalization support device according to an embodiment of the present invention. 2 is shown in FIG.
Showing a layout image input by the layout image input unit of FIG. 3, FIG. 3 shows a portion highlighted by being selected by the repeated portion selecting unit of FIG. 1, and FIG. 4 is normalized from the layout image information of FIG. It is a figure which shows the example of the normalization table created by dividing a repeating part as a result of designating a part. FIG. 5 is a diagram for explaining an operation of creating a divided file by designating a normalized portion from the layout images shown in FIGS. 2 and 3 and repeatedly accumulating it in the partial division information accumulating unit together with data items.

In FIG. 1, 101 is an input / output device for externally inputting or outputting information necessary for the normalization support system, 102 is a layout image input section, 103 is a layout information storage section, and 104 is a repeat. Candidate storage unit, 105 is a repeated portion selection unit, 106 is a repeated partial division information storage unit, 107 is an identifier determination unit,
Reference numeral 108 is an identifier determination result storage unit. 109 is an identifier suffix input unit, 110 is an identifier suffix storage unit, 111 is a non-key identifier candidate extraction unit, 112 is a non-key identifier candidate storage unit, 113 is a non-key identifier determination unit, and 114 is a non-key identifier determination result storage unit. Reference numeral 115 is an identical key table integration unit, 116 is an integration result storage unit, 117 is a table related information extraction unit, and 118 is a table related information storage unit.

Next, the operation of the first normalization in this embodiment will be described. First, the layout image input unit 102 creates a layout of screens, forms, etc. used in the information system to be constructed by arranging prompts, fields, and literals interactively on the screen of the input / output device 101. . A prompt is the name of a data item,
The field is an area for displaying the contents of the data item, the literal is another character string, and the prompt and the field are usually associated in a one-to-one relationship.

From the created layout, the display position and length and attribute information of fields, the display position and display contents of prompts and literals are read, and the layout information storage unit 103 together with the screen / form name input from the input / output device 101 is read. Accumulate in. The operation so far has nothing directly to do with normalization. However, the layout is designed so that the key and data item for normalization can be easily specified, that is, which item is repeated. The display position is represented by the position of the first line where the field, prompt, and literal are placed, and the column position.

Next, the keys constituting the file are specified on the screen. A data item that can uniquely identify all data items in the layout among the data items in the table is given as a key item from the input / output device 101 in an interactive manner. The layout information is accumulated by this designation, and at the same time, the data items on the layout are extracted and the set of the data items is used as a table. Information that the data item is a key item is also repeatedly stored in the candidate storage unit 104 as key item information together with the screen / form name. Further, when it is desired to repeat the same content in the row or column on the layout a plurality of times, the repetition is repeated.
The operator instructs more interactively. For example, when a row or a column is created, information for instructing the row or column to be repeated n times or information for copying the row or column n times on the screen is given. On the computer side, based on this instruction, information that the repeated data item is a candidate for the repeated portion is stored in the repeated candidate storage unit 104 as the repeated candidate information together with the screen / form name. Only when this repetition exists is the relationship between the prompt and the field 1 to n.

FIG. 2 shows an example of a layout arranged on the screen of the input / output device 101, and all the following description will be made using this example. The key item that can uniquely identify the data item on the screen in this example is the order number 201.
And the repetition candidate accumulating unit 104 as a repetition candidate.
The data items accumulated in are product code 202, product name 2
03, unit price 204, quantity 205, order amount 206, department code 207, department name 208.

Next, the normalized part is confirmed. In the repeated portion selection unit 105, the input / output device 101 interactively determines whether or not the repeated candidate information stored in the repeated candidate storage unit 104 is a data item to be repeated, and if the operator confirms it by looking at the layout screen. , Based on the confirmation, the repeated partial division information storage unit 1
In 06, the name of the data item and information as to whether it is a repeated portion are stored as repeated partial division information. FIG. 5 is an operation flow diagram of dividing the repetition candidate, which is a detailed operation of the repetition part selection unit 105 and the repetition part division information storage unit 106 of FIG. First, step 5
In 02, the layout is input / output device 101 based on all information of the accumulated information for one screen in the layout information accumulating unit 103.
To display. Next, in step 504, the prompt portion is marked so that the repetition candidate information accumulated in the repetition candidate accumulating unit 104 can be identified on the input / output device 101, for example, in a shaded manner in FIG.

In step 505, if the repetition candidate information is correct, the operator interactively inputs, from the input / output device 101, a data item having a repeating portion among the data items of the repetition candidate information. Further, since the key item is designated first, the given data item is recognized as a data item subordinate to the key item, and the information is stored in the repeated partial division information storage unit 106 as the repeated partial division information. Repeated subdivision information storage unit 1
The information of the data item stored in 06 is the name of the data item. If the candidate is incorrect, leave it as is.

Usually, the above operation is sufficient, but if there is a repeated portion other than the repeated candidate information,
It is also possible for the operator to look at the layout information displayed on the input / output device 101 again and input the repeated data item from the data items on the screen and the data item that is the key item in the data item. In that case, as in the above case, the key item and the data item are stored in the repeated partial division information storage unit 106 as the repeated partial division information.

With the above work, the division of the repeated portion is completed, and the data items on the screen which are not the repeated portion are
Information that the data item is subordinate to the data item that is the key item in the layout image input unit 102 is similarly stored in the repeated partial division information storage unit 106 as the repeated partial division information. This repeated portion selection unit 105
In this example, the display contents of the input / output device 101 in FIG. 3 are as shown in FIG. 3, and the shaded portion 301 shows the data items accumulated in the repeated candidate accumulating unit 104.

As described above, when the operator recognizes that the shaded portion 301 of FIG. 3 is a repeating portion and gives an instruction to make the key item of the repeating portion the product code 302 in an interactive form, that portion Is determined and stored in the repeated partial division information storage unit 104 as repeated partial division information. The content of the repeated partial division information is shown in, for example, FIG. 4, in which the data item on the left side of the double line indicates a key item and the right side indicates a data item subordinate to the key item. The first table is a table with the order number 401, which is a key item in the layout image input section 102, as a key, and the second table is the order number 40.
1 and the product code 402 which is the key item of the repeated part
It is a table of the repeated part with the key. By the work up to this point, the one equivalent to the one subjected to the first normalization can be obtained. That is, even a person who is not an expert in normalization knowledge with a special program source can easily specify a normalization range and key items by using a layout form that is easy for a normal operator to understand. Up to this point, the so-called first normalization is completed.

Next, an example of easy second normalization, which is an embodiment of the present invention, will be described. That is, in the following description, the configuration and operation of the support device when the second normalization is repeated after the above normalization is performed will be described. FIG. 6 is a flow chart showing an operation of creating an identifier pattern which is a key candidate for the second normalization in the identifier determining unit of FIG. 1, and FIG. 7 is a key which is considered to overlap from the key candidates extracted in FIG. It is a flowchart which shows the operation | movement except an item. FIG. 8 is a diagram showing an example of an initial display screen displayed on the basis of the operations of FIGS. 6 and 7 in the identifier determining unit of FIG. 1, and FIG. 9 shows keys and corresponding data items on the screen of FIG. FIG. 10 is a diagram showing an example of a determined determination work end display screen, and FIG. 10 is a diagram showing an example of a table generated by the input obtained by the confirmation of FIG. 9 from the table of FIG.

Next, the support operation for the second normalization in this embodiment and the table generating operation by the support operation will be described. This is a detailed operation of the parts of the identifier determination unit 107 and the identifier determination result storage unit 108 in FIG. 1, which will be described according to the flows of FIGS. 6 and 7. The identifier determination unit 107 creates an identifier pattern and displays the identifier pattern on the input / output device 101 as, for example, the identifier pattern 801 in FIG. In the flow chart of the identifier pattern generation operation of FIG. 6, step 601 repeats the partial division information storage unit 10
The table is extracted from the repeated partial division information accumulated in No. 6.

As a concrete example, if the second normalization is to be supported from the table of FIG. 4, first, a table having the order number 401 as a key is taken out. Step 603
Since the order number is a key in, it is extracted, and step 610
Selects an identifier pattern with and ends. Next, a table in which the order number of 401 and the product code 402 are key items is taken out in step 601. Since the order number has already become an identifier pattern in the first round, the second round is entered in step 611. In the second round, the product code 402 is extracted in step 603, and the order number / product code combined in step 608 becomes the identifier pattern. Further, in step 610, the product code also becomes an identifier pattern and ends.

According to the above operation of the support device, "order number" and "order number / product code" are used as the identifier pattern.
Three types of "product code" will be selected. However, since the "order number" has already been designated as a key, it is not necessary to display it again as an identifier pattern. Therefore, the operation of FIG. 7 reduces unnecessary unnecessary key display to make it easier to see the new identifier pattern of the key candidate. In step 701 of FIG. 7, the order number of the identifier pattern is first extracted, and step 703 returns Yes, and step 7
It is removed from the identifier pattern at 04. Step 705 means that the table in which the order number is a key item is separated into another file.

Input / output device 1 in the identifier determination unit 107
The initial display contents of 01 are as shown in FIG. 8 in this example by the operations of FIGS. 6 and 7. Reference numeral 801 is an area of an identifier pattern to be displayed, 802 and 803 are generated identifier patterns, and 804 is a data item other than the key items listed as selection items. The operator gives from the input / output device 101 interactively which identifier pattern the data items other than the key items depend on. The information that the identifier pattern is a key and the information that a data item other than the key item is subordinate to the identifier pattern are used as the identifier determination result information as the identifier determination result storage unit 1.
It is accumulated in 08.

FIG. 9 shows the display contents of the input / output device 101 when the identifier judging work instructed by the operator is completed, and FIG. 10 shows an example of the information of the identifier judging result created as a result. The group with the order number in FIG. 4 as the key item is the first table 1001 in FIG. 10, and the group 902 with the product code in FIG. 9 as the key item is 3 in FIG.
The second table 1002 in FIG. 10 is a lump 901 in which the order table / product code in FIG. 9 is used as a key item. This is stored as the identifier determination result in the identifier determination result storage unit 108 in FIG. 1 as the identifier determination result in FIG. By the work up to this point, the one equivalent to the one subjected to the second normalization can be obtained. That is, even a person who is not a database expert can easily perform normalization design by using the support device.

Example 2. Next, an example of easy third normalization, which is an embodiment of the present invention, will be described. FIG. 11 is a flow chart for explaining a detailed processing operation for extracting an identifier guide which is a key candidate for the third normalization in the identifier candidate extracting unit other than the key of FIG. 12 is a diagram showing an example of an initial display screen in the identifier determination unit other than the key in FIG. 1, FIGS. 13 and 14 are diagrams showing examples of display screens during determination in the identifier determination unit other than the key in FIG. 1, FIG. FIG. 15 is a diagram showing an example of a display screen at the time when the determination work by the identifier other than key is completed, and FIG. 16 is a diagram showing an example of a table created as a result of performing the identifier determination other than the key from the table of FIG.

Next, the support operation for the third normalization of this embodiment and the table generating operation by it will be described. First, the operator inputs an identifier, which is a candidate data item that is likely to become a key item for the third normalization, from the input / output device 101 in advance. These input elements are stored in the identifier term storage section. In the present embodiment, an example will be described in which only suffixes are input and stored as identifiers, and comparison is made with data items described later to determine whether there is a data item including this registered suffix. Next, the non-key identifier candidate extraction unit 111 selects a code, a classification, a NO from the data items other than the key items stored in the identifier determination result storage unit 108.
An item having the end of the number is extracted, and the information that the data item is a candidate for the identifier is stored in the other-key-identifier candidate storage unit 112 as the other-key identifier candidate information.

Next, the non-key identifier determination unit 113 displays the data item name of the non-key identifier candidate information in the non-key identifier candidate storage unit 112 on the input / output device 101 as an identifier guide according to the flow of FIG. In the description of the present embodiment, the suffix "code" is registered. Therefore, in step 1101 of FIG. 11, the table of the lump 1001 with the order number of FIG. 10 as a key is taken out,
In step 1105, the “code” is extracted. There is no data item with the suffix "code" in this table, so it ends. The table of the lump 1002 using the next order number / product code as a key is taken out, and the "department code" is stored in the candidate identifier storage unit 112 other than the key as an identifier guide in Step 1108 in Step 1107.

In this way, when all the tables are extracted and the comparison in step 1107 as to whether the registered suffixes are included is completed,
It is displayed on the screen of the input / output device 101. From the input / output device 101, the operator interactively indicates which identifier guide 1201 all the data items except the key item 1208 correspond to among the identifier determination result information stored in the identifier determination result storage unit 108. Its identifier guide,
In other words, the information that the candidate information other than the key is the key and the information that the data items excluding the key item in the identifier determination result information depend on the candidate identifier information other than the key The determination result is stored in the storage 114.

At this time, when a data item uniquely identified by a plurality of identifier candidates or a data item uniquely identified by another data item is found, an identifier for identifying the data item is added from the input / output device 101. As an interactive form. Then, the information that the identifier is an identifier candidate is stored in the other-key-identifier candidate storage unit 112 as the other-key identifier candidate information. In addition, the information that the data item associated with the non-key identifier candidate information is subordinate to the non-key identifier candidate information is stored in the non-key identifier determination result storage unit 114.

The initial display contents of the input / output device 101 in the identifier determining section 113 other than the keys are as shown in FIG. 12 in this example. Reference numeral 1201 denotes a candidate identifier storage unit 11 other than the key
2 is an identifier guide column for presenting the data item name in 2 as a guide, and 1202-1205 are data items other than the key items listed as the selection item 1206.
Reference numeral 7 is a non-key identifier candidate extracted by the non-key identifier candidate extraction unit in this example. Reference numeral 1208 shows the current key item of the selection item 1206. Further, in this example, the section code 1204 in the selection item column has already been listed in the identifier guide column 801 as an identifier candidate other than the key, so that it is determined, for example, shaded.

FIG. 13 shows the screen of the input / output device 101 after the judgment about the order date 1202 is given. Order date 12
02 is determined to be subordinate to the current key order number 1301 regardless of the department code 1207, and the input / output device 10
The determination from 1 as is is given interactively. The order date 1202 to which the determination is given is in the determined state. Figure 1
Reference numeral 4 is a screen of the input / output device 101 after the determination of the supplier name 1203 is given. The operator thinks that the supplier name 1203 is determined by the supplier code that is not in the identifier guide column 1201, and sets the supplier code 1401 in the identifier guide column 1201 newly from the input / output device 101 in an interactive manner. Then, the supplier name 1203 is interactively set as the supplier code attribute item 1402. As a result, the supplier name 1203 in the selection item column is converted into the supplier code 1403.

FIG. 15 shows the screen of the input / output device 101 at the time when the judgment work by the operator is completed. It is determined that the department / section name 1205 in FIG. 12 is subordinate to the department / section code 1207, and the input / output device 101 indicates that the department / section code attribute column 150
Instruct to move to 1 interactively. FIG. 16 is an example showing the non-key identifier determination information generated as a result of the non-key identifier determining unit 113. By the work up to this point, the one equivalent to the one subjected to the third normalization can be obtained.

When the instruction up to the third normalization is completed, the support apparatus of the present embodiment causes the same key table integration unit 115 of FIG. 1 to perform the integration result accumulation unit 116 according to the operation flow shown in FIG.
Integrate the table into. At this time, the unified information of each table is interactively given a table name from the input / output device 101 and stored in the integrated result storage unit 116 as integrated result information. FIG. 18 is a diagram showing an example in which other tables are integrated as a result of the above operation with respect to the table of FIG.

Next, in the table related information extracting section 117,
The relationship between the individual tables stored in the integration result storage unit 116 is determined whether a data item that is a key item in each table exists as a data item in another table. If present, information indicating that there is a relationship between the tables is stored in the table-related information extraction unit 117 as table-related information. FIG. 19 is a flow chart of the logic when extracting. First, in 1901,
One table stored in the integration result storage unit 116 is extracted, and all data item names that are key items are extracted from the table. Next, at 1902, another table containing a data item having the same data item name as the data item name extracted at 1901 is searched from the integrated result accumulating unit 116. Next, in 1903, it is determined whether or not the searched table exists, and if there is, in 1904, a data item having the same data item name is found in each searched table as a key item of the searched table. It is determined whether the data item exists as a data item of or a data item subordinate to the key item.

If it exists as a data item of the key item, in 1905, the retrieved table name and the information that it is included in the key part are stored in the table-related information storage unit 118 as table-related information. If it exists as a data item subordinate to the key item, in 1906, the table name searched and the information that it is included in the part other than the key is stored in the table related information storage unit 118 as table related information. Then at 1907,
It is determined whether or not the above extraction and search operations have been completed for all the tables existing in the integration result accumulating unit 116. If the extraction and search operations have been completed, the operations are completed.

FIG. 20 shows an example of the table related information stored in the table related information storage unit 118 as a result of performing the operation shown in FIG. 19 on the table example of FIG. The character on the left side of the box is the table name, and the table names and symbols in the box are related to each other. If there is a relationship with a plurality of tables, this is repeated. Is a symbol
K'represents the information contained in the key part, and'N
K'represents information that it is included in a part other than the key.
For example, in this example, the order table indicates that the key item of the order is included in the key part of the order details.

Example 3. As another embodiment, in the first embodiment, the layout image input unit 102 uses a method of interactively creating a layout of screens, forms, etc. used in the information system constructed from the input / output device 101. However, if the screen / form design information of the existing information system exists, the information can be imported from the input / output device 101. At this time, the extraction of the repetition candidate is performed from the repetition information (for example, matrix information) held in the screen / form design information.

[0046]

Since the database normalization support device of the present invention is configured as described above, a new key candidate is displayed together with the selection item, and it is easy to give an instruction and the support is simple. There is.

Furthermore, there is an effect that the registered single key item is removed, selection becomes easy, and support is even easier.

Since the database normalization support device of the present invention is configured as described above, new key candidates are displayed together with selection items in the lower normalization,
The effect is that instructions can be given easily and support is easy.

Furthermore, there is an effect that the data item including the registered suffix is selected and displayed, the selection becomes easy, and the support is easy.

[Brief description of drawings]

FIG. 1 is a flowchart showing the relationship between the configuration and the operation of a database normalization support device according to an embodiment of the present invention.

FIG. 2 is a diagram showing a screen display example of layout image information input by a layout image input unit of FIG.

FIG. 3 is a diagram showing an example of a display screen in a repeated portion selection unit in FIG.

FIG. 4 is a diagram showing an example of a table as a result of dividing a repeated portion from the layout image information of FIG.

5 is a flowchart showing the operation of the repeated portion selection unit in FIG.

FIG. 6 is a flow chart showing an operation of generating an identifier pattern of the identifier determination unit of FIG.

FIG. 7 is a flowchart showing an operation of removing an already-keyed item when the identifier pattern shown in FIG. 5 is generated.

FIG. 8 is a diagram showing an example of an initial display screen in the identifier determining unit of FIG.

9 is a diagram showing an example of a display screen at the end of the determination work in the identifier determination unit of FIG.

10 is a diagram showing an example of a table created as a result of determining the identifier of FIG. 9 as a key from the table of FIG.

11 is a flowchart showing an operation of generating an identifier guide of the identifier candidate extraction unit other than the key of FIG. 1 of the present invention.

12 is a diagram showing an example of an initial display screen in an identifier determination unit other than the keys of FIG.

13 is a diagram showing an example of a display screen during the determination work in the identifier determination unit other than the keys of FIG.

14 is a diagram showing an example of a display screen during the determination work in the identifier determination unit other than the keys of FIG.

15 is a diagram showing an example of a display screen at the end of the determination work in the identifier determination unit other than the keys of FIG.

16 is a diagram showing an example of a table created as a result of performing an identifier determination other than a key from the table of FIG.

FIG. 17 is a flowchart illustrating a detailed processing procedure of the same key table integration unit of FIG. 1 in Embodiment 1 of the present invention.

FIG. 18 is a diagram showing an example of a table in which tables created from a plurality of layout images are integrated by the same table integration unit in FIG. 1.

FIG. 19 is a flowchart showing the operation of the table related information extracting section in FIG. 1.

20 is a diagram showing an example of table-related information generated from the table of FIG. 18 by the operation flow of FIG.

FIG. 21 is an explanatory diagram showing functions and processing procedures of a conventional database generation support system.

FIG. 22 is a diagram showing an example of a data section extracted by an existing program analysis section of a conventional example.

FIG. 23 is a diagram showing an example of data items estimated to have the same content by the existing program analysis unit of the conventional example.

FIG. 24 is a diagram showing an example of data items unified and given a new name as the same contents as in the conventional example.

FIG. 25 is a diagram showing an example of relation information extracted from the contents of a standardized file record information storage unit of a conventional example.

FIG. 26: After normalization by the relation normalization unit of the conventional example,
It is a figure which shows the example of the relation information which integrated the relation information further and was given the new name.

FIG. 27 is a diagram showing an example of logical schema information created by a conventional logical schema information creation unit.

[Explanation of symbols]

101 Input / output device 102 Layout image input unit 103 Layout information storage unit 104 Repeated candidate storage unit 105 Repeated portion selection unit 106 Repeated partial division information storage unit (means) 107 Identifier determination unit 108 Identifier determination result storage unit 109 Identifier suffix input unit 110 identifier suffix accumulation unit 111 other than key identifier candidate extraction unit 112 other than key identifier candidate accumulation unit 113 other than key identifier determination unit 114 other than key identifier determination result accumulation unit 115 same key table integration unit 116 integration result accumulation unit 117 table related information extraction Part 118 Table-related information storage part 201-208 Data item 301 Repeated candidate display 302 Data item 401-402 Key item 601 Table extraction step 603 Key item extraction step 608 Combination key Extraction step 610 Extraction data item candidate step 701 Candidate extraction step 704 Unnecessary candidate removal step 707 Extraction candidate display step 708 Data item display step 801 Identifier pattern field 802, 803 Selected generated identifier Pattern 804 Selection item 901 to 902 Data item group having identifier pattern as key item 1001, 1002, 1003 Table generated by instruction after judgment work 1101 Table extraction step 1103 Data item extraction step 1105 Registration suffix extraction step 1107 Suffix And data item comparison step 1201 identifier guide column 1202-1205 selection item 1206 selection item column 1207 identifier guide 1208 key column 1301 key 1401 setting identifier De 1402 identifier guide of attributes (subordinate items) 1403 selection 1501 identifier guide of attributes (subordinate items)

─────────────────────────────────────────────────── ───

[Procedure amendment]

[Submission date] January 26, 1995

[Procedure Amendment 1]

[Document name to be amended] Statement

[Name of item to be corrected] 0022

[Correction method] Change

[Correction content]

Next, the normalized part is confirmed. In the repeated portion selection unit 105, the input / output device 101 interactively determines whether or not the repeated candidate information stored in the repeated candidate storage unit 104 is a data item to be repeated, and if the operator confirms it by looking at the layout screen. , Based on the confirmation, the repeated partial division information storage unit 1
In 06, the name of the data item and information as to whether it is a repeated portion are stored as repeated partial division information. FIG. 5 is an operation flow diagram of dividing the repetition candidate, which is a detailed operation of the repetition part selection unit 105 and the repetition part division information storage unit 106 of FIG. First, step 5
In 01 , the layout is input / output device 101 based on all information of the accumulated information for one screen in the layout information accumulating unit 103.
To display. Next, in step 504, the prompt portion is marked so that the repetition candidate information accumulated in the repetition candidate accumulating unit 104 can be identified on the input / output device 101, for example, in a shaded manner in FIG.

[Procedure Amendment 2]

[Document name to be amended] Statement

[Correction target item name] 0042

[Correction method] Change

[Correction content]

Next, in the table related information extracting section 117,
The relationship between the individual tables stored in the integration result storage unit 116 is determined whether a data item that is a key item in each table exists as a data item in another table. If present, information indicating that there is a relationship between the tables is stored in the table related information storage unit 118 as table related information. FIG. 19 is a flow chart of the logic when extracting. First, in 1901,
One table stored in the integration result storage unit 116 is extracted, and all data item names that are key items are extracted from the table. Next, at 1902, another table containing a data item having the same data item name as the data item name extracted at 1901 is searched from the integrated result accumulating unit 116. Next, in 1903, it is determined whether or not the searched table exists, and if there is, in 1904, a data item having the same data item name is found in each searched table as a key item of the searched table. It is determined whether the data item exists as a data item of or a data item subordinate to the key item.

[Procedure 3]

[Document name to be corrected] Drawing

[Name of item to be corrected] Figure 1

[Correction method] Change

[Correction content]

[Figure 1]

Claims (4)

[Claims] 1. A repetitive partial division information accumulating means for normalization in a database, and a table is taken out from a table group in the repetitive partial division information accumulating means, and is registered from each item of the taken out table. A means for extracting a key, a means for extracting an unregistered key candidate from a key that is a combination of the extracted registered key items, the extracted key candidate as an identifier pattern, and the registered Means for displaying a data item subordinate to the key as a new selection item of the identifier pattern; result integrated storage means for normalizing the specified new key in the displayed identifier pattern and the data subordinate to the new key Database normalization support device equipped with. 2. A single key item that has already been registered in the table in the repeated partial division information storage means is deleted from the key candidates extracted for display as an identifier pattern and displayed. The database normalization support device according to item 1. 3. An identifier term accumulating means for selecting an identifier that is a candidate that can be a key for normalizing a table in a database, a registered key of the repeating portion of the normalization and a subordinate to the key. Table of data items to be stored, and a table is extracted from the table group in the repeated partial partition information storage unit, each data item of the extracted table is extracted, and among the extracted data items As a new identifier guide when the extracted data item includes an identifier in the identifier term storage means, and as a new identifier guide for the key and the key Means for displaying the data item to be displayed, the specified new key in the displayed identifier pattern and the new key Database normalization supporting apparatus having a result integration storing means for normalizing the subordinate data. 4. A suffix is registered in order to select an identifier that is a candidate that can be a key for normalizing a table in a database, and the identifier term accumulating means is an identifier suffix accumulating means to accumulate repeated partial division information. 4. The database normalization support device according to claim 3, wherein the comparison with the data item extracted from the means compares the data item including the suffix.