JPH08110855A - Database design support system - Google Patents

Abstract

(57) [Summary] [Purpose] To provide a database design support system capable of independently and flexibly designing and supporting a database in a downstream process regardless of the progress status in the upstream process and data specifications. [Structure] An extraction database editing means 12 for displaying / editing the data of the extraction database 8 is provided, and the downstream database editing means 13 sets the certainty factor indicating the necessity of merging to the data of the downstream database 14 before merging. The extraction data merging means 15 selectively performs the merge according to the certainty factor value set in the data of the downstream database 14 when the merge is performed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a database design support system, for example, a downstream database design support system in a downstream process in a supervisory control computer system of a plant.

[0002]

2. Description of the Related Art A conventional database design support system will be described with reference to the block diagram of FIG. In FIG.
The data flow is shown by a broken line, and the control flow is shown by a solid line.

Conventional database design support system 10
0 is an upstream database input means 4 for inputting data corresponding to the input request 50 from the input / output device 1 from the upstream database 2 located upstream in the design process and storing the data in the internal upstream database 3; The extraction / automatic conversion request 51 from the output device 1 is input via the upstream database extraction request means 6, and the data of the internal upstream database 3 is used by using the extraction / automatic conversion rule 53 input from the extraction / automatic conversion rule unit 7. Is extracted and converted, and the upstream database extraction / automatic conversion means 5 for generating the extraction database 8 from the extracted / converted data and the extraction data merge means 11 to be described later are activated in accordance with the merge request 52 from the input / output device 1, and A downstream database that edits a downstream database 10 to be described later according to an editing request 52 from the input / output device 1. And editing means 9, it merges the data of the data and the downstream data base 10 of the extraction database 8, and an extracted data merge unit 11 for storing the result in downstream database 10.

Next, the operation of the conventional database design support system 100 will be described. In accordance with the input request 50 from the input / output device 1, the upstream database input means 4 inputs the data of the upstream database 2 and outputs it to the internal upstream database 3.

As shown in FIG. 12, an example of the field structure of the data of the upstream database 2 is shown in FIG. Here, the field of the data of the upstream database 2 is composed of a term Du1, a term Du2, a term Du3, ..., A term Dun. For example, the term Du1 is Tag. In the term indicating no, the value (“TAG X
YZ ") is stored in a character type (char).

[0006] The upstream database extraction / automatic conversion means 5 which receives the extraction / automatic conversion request 51 from the input / output device 1 via the upstream database extraction request means 6 has the extraction / automatic conversion rule of the extraction / automatic conversion rule section 7. Based on 53, the value of each field of the data taken out from the internal upstream database 3 is extracted / converted and stored in the extraction database 8.

FIG. 13 shows an example of the extraction / automatic conversion rule 53 stored in the extraction / automatic conversion rule unit 7. FIG. 13A shows fields of data related to extraction / automatic conversion and corresponding extraction / automatic conversion rule numbers, and FIG. 13B shows each extraction / automatic conversion rule number. Shows the part where the content of the rule is described.

[0008] FIG. 14 shows an example of fields of data stored in the extraction database 8 after being extracted and automatically converted.

The upstream database extraction request means 6 is shown in FIG.
Process No. 3 shown in (a) of FIG. Extraction / automatic conversion rule No. 1 corresponding to From 1, the extraction / automatic conversion rule number (No), the data item Dc1 of the extraction database 8 to be output, and the data item Du1 of the internal upstream database 3 to be input are input. Then, according to the content of the extraction / automatic conversion rule shown in FIG. 13B, the value (“TAG” of the item Du1 of the internal upstream database 3 shown in FIG. XYZ ”)
As it is, as shown in FIG. 14, the term D of the extraction database 8
Save to c1. Similarly, the process No. According to the contents of the extraction / automatic conversion rule of No. 2, the value of the term Du2 of the data in the internal upstream database 3 (“X system pump flow rate Y measurement”) is stored as it is in the term Dc2 of the data of the extraction database 8.
Next, processing No. Extraction / Automatic conversion rule No. 3 shown in FIG.
According to the extraction / automatic conversion rule of No. 2, the value (the range is shown and the value is "0 to 3600T / H") of the data item of the internal upstream database 3 is read, and the first numerical data ("0") is read. It is decomposed into the second numerical data (“3600”) and the subsequent character data (“T / H”), the type of the numerical data is converted from the character type to the numerical type, and the first numerical data and the second numerical data are converted. The smaller one (0) of the numerical data is stored as the lower limit in the term Dc3 of the extraction database 8, and the larger data (3600) is stored as the upper limit in the term Dc4,
The character data (“T / H”) that follows it is used as it is in item D.
Save to c5. In this way, the data as shown in FIG. 14 is stored in the extraction database 8.

The downstream database editing means 9 receives the extraction request 51 from the input / output device 1 and receives the extraction data merging means 11
To start.

The extracted data merging means 11 takes out data from the extracted database 8 and merges the data with the data in the downstream database 10. At this time, if the downstream database 10 has not been generated, the downstream database 10 is initially generated. If there is a term in the extraction database 8 that has no data to be merged, that data is absent.

FIG. 15 shows an example of data fields of the downstream database 10. As a field of data,
There are terms Dd1 to Ddn. For example, in the term Dd2, a value indicating the PID (“ABC01”) is stored in a character type (char).

The extracted data merging means 11 determines the term D of the key data of the extracted database 8 which matches the term Dd1 which is the key data of the field of the data of the downstream database 10.
The value of c1 is extracted, the value of the term Dc2 of the field of the data of the extracted database 8 is stored in the term Dd2 of the corresponding field of the data of the downstream database 10, and the terms Dd3 and Dd are stored.
4, ..., the value of the term Ddn is also the term Dc3, the term Dc4 ,.
Save each to.

Further, the downstream database editing means 9 edits the data of the downstream database 10 in response to the editing request 52 from the input / output device 1.

As described above, the conventional database design support system extracts and automatically converts data from the upstream database created based on the upstream specifications,
We have supported the design of the database by adding it to the data of the downstream database and further editing the downstream database.

[0016]

As described above, in the conventional database design support system, data is extracted and automatically generated from the upstream database, and the data is merged with the downstream database, that is, the data in the downstream database is extracted database. After being added by the data of, the downstream database was edited. However, in the actual database design, not only the items to which the data of the upstream database is added as they are, but also the items to be edited independently in the downstream process, and the design knowledge in the downstream process are added and modified based on the data of the upstream database. There are also items to be created. Also, in the actual design process, various change requests and changes in the specifications of the upstream database are delayed, so the work of the downstream process may be performed before that of the upstream process.

In this case, in the conventional database design support system, the data in the downstream database, which is known not to be added in advance to the data in the upstream database, that is, the data in the downstream database, which is known not to be merged, is unilaterally added to the data in the upstream database. Since it will be added, it was necessary to correct the data in the downstream database after it was merged.

Therefore, an object of the present invention is to provide a database design support system capable of independently and flexibly designing and supporting a database in a downstream process regardless of the progress status in the upstream process and data specifications.

[0019]

A database design support system according to claim 1 of the present invention inputs data from an upstream database according to an input request from an input / output device,
An upstream database input means for storing the data in the internal upstream database, an upstream database extraction request means for inputting a data extraction request from the input / output device, and a data extraction request for input from the upstream database extraction request means,
Extraction / Automatic conversion rule part extraction / automatic conversion rules
The upstream database extraction / automatic conversion means for generating an extraction database from the converted data, the downstream database editing means for editing the downstream database according to the editing request from the input / output device, and the downstream database editing means for the merge request from the input / output device In the database design support system having the extraction data merging means for merging the data of the extraction database with the data of the downstream database according to the merge request and storing the result in the downstream database, the data of the extraction database is input. Equipped with extraction database editing means for displaying / editing in response to a display / editing request from the output device, the downstream database editing means is required to be merged with the data in the downstream database according to a setting request from the input / output device before being merged. Is set to indicate Configured as a downstream database editing means with a confidence measure means, the extraction data merging means, when the data of the extraction database and the data of the downstream database are merged, depending on the value of the confidence factor set in the data of the downstream database. It is characterized in that it is configured as an extraction data merging unit with a certainty factor unit for selectively merging.

In the database design support system according to claim 2 of the present invention, the extraction data merging means stores the data of the extraction database which has not been merged and the data of the downstream database corresponding to the data in the merge unexecuted database. It is configured as an extracted data merging unit with a certainty factor unit / merge unexecuted data storage unit, and has a merge unexecuted database display unit for displaying the data of the merge unexecuted database on the input / output device. It is what

In the database design support system according to claim 3 of the present invention, in the downstream database editing means, the presence / absence of confirmation of the data which is not merged in the data of the downstream database and the step when the confirmation is performed. Is configured as a downstream database editing means with a certainty factor / confirmation means for setting.

In the database design support system according to claim 4 of the present invention, the upstream database input means inputs, from a plurality of upstream databases, the type of the upstream database in which the data was stored, and the data and the type. Is stored in the internal upstream database, and the extraction / automatic conversion rule section stores multiple extraction / automatic conversion rules for extracting / converting data from multiple upstream databases. It is characterized in that it is configured as a part.

In the database design support system according to claim 5 of the present invention, in the upstream database extraction / automatic conversion means, the data of the internal upstream database and the type of the upstream database in which the data is stored are paired with the extracted database. It is characterized in that it is configured as an extraction / automatic conversion means with extraction information addition means for generating.

[0024]

In the database design support system according to the first aspect of the present invention, the certainty factor indicating the degree of undesired merging to the data of the downstream database is set in advance, and the certainty factor is referred to to selectively select the certainty factor. The data in the upstream database and the data in the downstream database are merged.

The database design support system according to claim 2 of the present invention stores the data of the extraction database that has not been merged according to the certainty value and the data of the downstream database data corresponding to the data in the unexecuted database. The data in the merge-unexecuted database can be referred to via the input / output device.

In the database design support system according to claim 3 of the present invention, after the data of the upstream database and the data of the downstream database are merged, the designer can confirm the data of the downstream database which has not been merged. The data is displayed on the input / output device, and the presence or absence of confirmation and the work process at the time of the confirmation are recorded on the data.

The database design support system according to claim 4 of the present invention is provided with an extraction / automatic conversion rule unit for extracting / automatically converting data input from a plurality of upstream databases into one extraction database. .

A database design support system according to a fifth aspect of the present invention generates an extraction database including data of a plurality of upstream databases and the type of upstream database in which the data was stored.

[0029]

DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of a database design support system according to claim 1 of the present invention will be described with reference to the block diagram of FIG. It should be noted that the processes from the upstream database 2 to the extraction database 8 are the same as those described in the conventional technique, and thus the description thereof is omitted.

The database design support system 200 of the present embodiment edits the extracted database 8 by the edit request 54 from the input / output device 1 with respect to the conventional database design support system 100 described in FIG. Means 12 are newly provided. The extraction database editing means 12 extracts data from the extraction database 8, displays the data on the input / output device 1, edits the data in accordance with the edit request 54 from the input / output device 1, and extracts the result. Save to 8.

As described above, conventionally, the data in the extraction database 8 could not be edited before the data in the extraction database 8 extracted from the upstream database 2 were merged. By newly providing the extraction database editing means 12 for editing the data of the extraction database 8, the data of the upstream database can be selectively added to the downstream database in the downstream process.

Further, according to the present embodiment, according to a request from the input / output device 1, a downstream database with certainty means for activating the extracted data merging means 15 with certainty means to be described later or for editing the downstream database 14 with certainty data. It has edit means 13 and extracted data merge means 15 with confidence measure that selectively merges the data of the extraction database 8 and the data of the downstream database 14 with confidence data with the confidence measure.

First, the extracted data merging means 15 with confidence measure means will be described. The extracted data merging means 15 with confidence measure inputs data from the extraction database 8 and considers the degree of confirmation of the confidence measure field newly provided on the data in the downstream database 14 with confidence measure data. The data in the downstream database 14 with certainty data is merged.

FIG. 2 shows an example of data fields of the downstream database 14 with confidence data. Figure 2
As shown in, the downstream database 14 with confidence data
In this data, a certainty factor data field P is newly provided for the field of the data of the conventional downstream database 10 (see FIG. 15). The certainty factor values P1 to Pn of the certainty factor data field correspond to the terms Dd1 to Ddn, and the certainty factor means-equipped extracted data merging means 1 to be described later.
5. Confidence refers to the data of the extraction database 8 and the corresponding data of the downstream database with confidence data 14 when the values of the terms Dd1 to Ddn of the downstream database with confidence data 14 corresponding thereto differ from each other. Is a numerical value indicating whether or not the data can be directly written in the field of. The degree of confirmation is set by the designer in advance from the input / output device 1 together with the terms Dd1 to Ddn via the downstream database editing means 13 with confidence means. Hereinafter, a specific description will be given.

Here, the value of the term Dd2 of the downstream database 14 with confidence set by the downstream database editing means 13 with confidence means is temporarily ("Z plant X
System pump flow Y measurement "), and the value of the term Dc2 of the extraction database 8 corresponding to this is" X system pump flow Y measurement "(see FIG. 14). In this case, the designer extracts the database. When it is determined that the data No. 8 (here, “X system pump flow rate Y measurement”) is not desired to be added, the designer uses the downstream database with confidence measure editing means 13 in advance through the downstream database 1 with confidence measure data.
The confidence factor P2 of the data of No. 4 is set to the value "100". On the other hand, if the data of the downstream database 14 with confidence measure means may be added by the data of the extraction database 8, it is set to "0".

When prioritizing the current downstream data, depending on the degree of conviction of the designer, "1" to "10" is given.
It is also possible for the designer to set the value of "0" via the input / output device 1. Of course, setting in only two stages of 0 and 100 is also possible.

Extraction data merging means 15 with confidence measure means
Refers to the certainty factor of the data in the downstream database 14 with certainty factor data when merging, the certainty factor “0”
The data of the extraction database 8 is added only to the data of (3) and stored in the downstream database 14 with certainty data.

As described above, when it is not desired to add the data of the upstream database to the data of the downstream database in advance, it is necessary to edit the data of the upstream database on the downstream process side or to previously add the information of whether or not to add the data to the data of the downstream database. Can be set, so that the database can be designed independently in the downstream process.

An embodiment of the database design support system according to claim 2 of the present invention will be described with reference to the block diagram of FIG.

As shown in the figure, the process until the extraction database 8 is created from the upstream database 201 is the same as that described in the conventional technique, and therefore the description thereof is omitted.

Compared to the database design support system 100 described with reference to FIG. 1, the database design support system 201 of the present embodiment not only merges data according to the certainty value but also merges data that has not been merged. Extraction data merging means 18 with certainty measure / merging non-execution data saving means to be stored in the non-execution database 17
(Hereinafter, abbreviated as unmerged data storage means)
And a merge non-execution data display means 19 for displaying the data in the merge non-execution database 17 to the designer via the input / output device 1.

The merge unexecuted data storage means 18 is started by the downstream database editing means 13 with confidence factor means via the input / output device 1, inputs data from the extraction database 8, and the downstream database 14 with confidence factor data.
Data is merged in consideration of the certainty factor set for the data, and if the certainty factor is not merged, the data of the extraction database 8 and the downstream database with certainty data corresponding thereto are extracted. The data of 14 are paired and stored in the merge incomplete database 17.

The merge incomplete database display means 19 displays the data in the merge incomplete database 17 on the input / output device 1.

As described above, the data of the upstream database that has not been merged and the corresponding data of the downstream database are stored as a pair, and the data is displayed on the input / output device. Therefore, the designer extracts from the upstream database. -Data that has not been added to the downstream database among the automatically converted data can be confirmed via the input / output device.

An embodiment of the database design support system according to claim 3 of the present invention will be described with reference to the block diagram of FIG.

From the upstream database 2 as shown,
Until the extraction database 8 is created, it is the same as the one described in the conventional technique, and therefore the description thereof is omitted.

In the database design support system 202 of this embodiment, as compared with the database design support system 201 described with reference to FIG. 3, the confidence factor / confirmation that data having a field newly added with a confirmation item is stored. Downstream database 22 with data and downstream database 2 with confidence / confirmation data in response to a request from input / output device 1
A downstream database editing means 21 with a certainty / confirmation data for editing 2 is newly provided.

First, the fields of the data stored in the downstream database 22 with confidence / confirmation data are shown in FIG.
Shown in The data field is, for example, a confirmation data area C for confirmation such as confirmation data C1 corresponding to the term Dd1 of the data field and confirmation data C2 corresponding to the term Dd2.
Have. The designer activates the downstream database editing means 21 with confidence factor / confirmation means through the input / output device 1 while referring to the unmerged data displayed by the merge unexecuted database display means 19 to determine the confidence factor.
The data confirmation result is input to the data of the downstream database 22 with the confirmation data. For example, the term Dd2 of a field
If the name data is not merged, the data in the extraction database 8 that is not merged and the corresponding data in the downstream database 22 with confidence / confirmation data will not match. If the designer confirms the disagreement and determines that there is no problem, the designer confirms the confirmation data C
Input the data of "OK: Confirmation work Rev. No." into 1. When it is determined that there is a problem, "NG: Confirmation work Rev. No." is input. Confirmation work Rev. No
Shows the work process at the time when this confirmation work is performed. Note that when the downstream database 22 with confidence / confirmation data is initially generated, "unconfirmed" data is set as the initial value.

As described above, the data extracted from the upstream database
When the data of the automatically generated extraction database and the data of the corresponding downstream database are not merged, the designer confirms whether the inconsistency is OK (OK) or whether there is a problem (NG). As a result, it is possible to set which work process has been confirmed, and therefore, it is possible to prevent the confirmation failure of the mismatch between the upstream process data and the downstream process data.

An embodiment of the database design support system according to claim 4 of the present invention will be described with reference to FIG.

As shown in the figure, in the present embodiment, the conventional database design support system 203 inputs from one database, whereas a plurality of upstream databases U
The data can be input from 1 to Un. Here, there are two upstream databases, a first upstream database U1 (see FIG. 7A) that stores instrument specifications and suppliers, and a U2 (see FIG. 7B) that stores measurement instrument installation related data. Think As shown in the figure, a plurality of extraction / automatic conversion rule parts in which an extraction / automatic conversion rule 60 for generating one extraction database 8 is stored from an internal upstream database 3 which stores data of a plurality of upstream databases U1 and U2. 27 is newly provided.

FIG. 7 shows a part of the data fields of the upstream databases U1 and U2, and FIG. 8 shows an example of the extraction / automatic conversion rule 60 of the multiple extraction / automatic conversion rule unit 27. The operation of refining one extraction database 8 from the databases U1 and U2 will be described. FIG. 8A shows fields of data related to extraction / automatic conversion and corresponding extraction / automatic conversion rule numbers, and FIG. 8B shows each extraction / automatic conversion rule number. Shows the part where the content of the rule is described.

First, the upstream database input means 4 inputs data from each of the upstream databases U1 and U2 in accordance with the input request 50 from the input / output device 1, and determines the type of the upstream database in which the data is stored together with the data. Stored in the internal upstream database 3.

Next, the upstream database extraction / automatic conversion means 5 causes the multiple extraction / automatic conversion rule unit 27 to process No. 1
Extraction / Automatic conversion rule No. Extraction / automatic conversion rule number (No) from 1 ', the term Dc1 of the extraction database 8 to be output, the value of the first reference ("U1 Du1") which is the term of the related upstream database 3 to be input, and the relationship to be input The second reference value (not here) of the upstream database 3 is input (see (a) of FIG. 8). Here, the value (“U1”) described in the relevant upstream database 3 section to be input,
("U2") indicates the type of upstream database as it is. Then, the extraction / automatic conversion rule No. According to the content of the extraction / automatic conversion rule 1 '(see FIG. 8B), the value of the term Du1 of the data of the upstream database U1 stored in the internal upstream database 25 is directly stored in the term Dc1 of the extraction database 8. . Next, processing No.
No. 2 extraction / automatic conversion rule No. According to the contents of the rule of No. 3, the systematic name is extracted from the data item Du2 of the upstream database U2 stored in the internal upstream database 25, and the systematic system is extracted from the data item Du2 of the upstream database U2 stored in the internal upstream database 25. The remaining names except the name are extracted, combined, and stored in the term Dc2 of the extraction database 8. In addition, the processing No. Extraction / Automatic conversion rule No. 3 shown in FIG. Internal upstream database 3 according to 2 '
Value of the data item Du3 of the upstream database U1 (which indicates the range, and the value is "0 to 3600 T / H") is read, and the first numerical data ("0") and the second numerical data ("3600") are read. ) Followed by character data (“T /
H ”). Next, the data type is converted from the character type to the numerical type, and the smaller one (0) of the first and second data is set as the lower limit value in the term Dc3 of the extraction database 8,
With the larger data (3600) as the upper limit, the term Dc4
Then, the character data ("T / H") that follows is stored in the item Dc5 as it is. Also. Process No. No. 4 extraction / automatic conversion rule No. According to the content of the rule 4
Extract the installation location from the item U2 Du3 in the upstream database,
It is stored in the item Dc2 of the extraction database 8. At this time, if the value of the term Du3 of the upstream database U2 is not described in the field (including cases such as "metaphysical" and "undecided"), the installation location is determined from the item Du5 of the data of the upstream database U1. It is extracted and stored in the term Dc2 of the extraction database 8.

As described above, it is possible to extract / automatically convert data from a plurality of upstream databases to create an extraction database, and one term of the extraction database involves similar terms by a plurality of upstream databases. Even in this case, the extraction / automatic conversion can be performed by referring to the rule of multiple extraction / automatic conversion rules. Further, it is possible to combine a plurality of terms in a plurality of upstream databases and perform extraction / automatic conversion.

An embodiment of the database design support system 204 according to claim 5 of the present invention will be described with reference to the block diagram of FIG. In this embodiment, two upstream databases U
1 and U2 are the same as those in the embodiment described with reference to FIG. 6 in that data are input, and the description of the overlapping portions will be omitted.

In this embodiment, the data in the internal upstream database 25 is extracted and converted according to the extraction / automatic conversion rule 60 of the multiple extraction / automatic conversion rule unit 27, and the data is saved. The extraction / automatic conversion means 31 with extraction information addition means for generating the extraction database 30 with extraction information by adding the extraction information indicating the type of the upstream database that has been created is provided.

FIG. 10 shows a part of the data of the extraction database 30 with the extraction information thus generated.
Here, the upstream database referred to when each data is extracted / automatically generated as the extraction information and the value of the term of the data are stored in the corresponding field of the extraction database with extraction information 30. For example, the value of the term Dc1 (“U2 Du1”) in the extraction information field of FIG. 10 indicates that it was generated from the value of the term Du1 of the upstream database U2.

An extraction information added extraction database editing means 32 for displaying / editing the data of the extraction information added extraction database 30 via the input / output device 1 is provided. This allows multiple upstream databases U
The corresponding data can be displayed by searching for 1, U2 based on the extracted information data.

As described above, in this embodiment, when a downstream database is constructed from a plurality of upstream databases, it is possible to refer to and edit from which upstream database the data of the downstream database is extracted. It is possible to know from which upstream database the data of is extracted.

[0061]

According to the present invention, it is possible to provide a database design support system capable of independently and flexibly designing and supporting a database in a downstream process regardless of the progress status in the upstream process and data specifications.

[Brief description of drawings]

FIG. 1 is a block diagram showing an embodiment of a database support system according to claim 1 of the present invention.

FIG. 2 is a chart for explaining fields of data in a downstream database with certainty factor data.

FIG. 3 is a block diagram showing another embodiment according to claim 2 of the present invention.

FIG. 4 is a block diagram showing another embodiment according to claim 3 of the present invention.

FIG. 5 is a chart for explaining fields of data of a downstream database with certainty confirmation.

FIG. 6 is a block diagram showing another embodiment according to claim 4 of the present invention.

FIG. 7 is a chart for explaining fields of data in a plurality of upstream databases.

FIG. 8 is a diagram for explaining multiple extraction / automatic conversion rules.

FIG. 9 is a block diagram showing an embodiment according to claim 5 of the present invention.

FIG. 10 is a diagram for explaining fields of data of an extraction database with extraction information.

FIG. 11 is a block diagram showing a conventional database support system.

FIG. 12 is a chart for explaining fields of data in an upstream database.

FIG. 13 is a diagram for explaining an extraction / automatic conversion rule according to a conventional technique.

FIG. 14 is a chart for explaining fields of data of the extraction database according to the related art.

FIG. 15 is a diagram for explaining fields of data in a downstream database according to the related art.

[Explanation of symbols]

1 Input / Output Device 2 Upstream Database 3 Internal Upstream Database 4 Upstream Database Input Means 5 Extraction / Automatic Conversion Means 6 Upstream Database Extraction Request Means 7 Extraction / Automatic Conversion Rule Part 8 Extraction Database 9 Downstream Database Editing Means 10 Downstream Database 11 Extracted Data Merge Means 12 Extraction Database Editing Means 13 Confidence Means Downstream Database Editing Means 14 Confidence Data Downstream Databases 15 Confidence Means Extracted Data Merge Means 17 Merge Unexecuted Databases 18 Confidence Means / Merge Unexecuted Data Saved Extracted Data Merges Means 19 Merge unexecuted database display means 21 Confidence / confirmation means-equipped downstream database editing means 22 Confidence / confirmation data-equipped downstream database U1, U2 Multiple upstream databases 27 Duplication Number extraction / automatic conversion rule section 30 Extraction database with extraction information 31 Extraction / automatic conversion means with extraction information addition means 32 Extraction database with extraction information editing means 200 Database design support system 201 according to the embodiment according to claim 1 Claim 2 Database design support system 202 according to the embodiment according to claim 3 Database design support system according to the embodiment according to claim 3 203 Database design support system according to the embodiment according to claim 4 Database design support system according to the embodiment according to claim 5

Claims (5)

[Claims] 1. An upstream database input means for inputting data from an upstream database according to an input request from an input / output device and storing the data in an internal upstream database; and an upstream database extraction for inputting a data extraction request from the input / output device. The data extraction request is input from the requesting means and the upstream database extraction requesting means, the data in the internal upstream database is extracted / converted according to the extraction / automatic conversion rule of the extraction / automatic conversion rule section, and the extracted / converted data is extracted. An upstream database extraction / automatic conversion means for generating an extraction database, a downstream database editing means for editing a downstream database according to an editing request from the input / output device, and a merge request from the input / output device via the downstream database editing means. And enter the extracted data according to the merge request. A database design support system having merged database data and data in the downstream database and storing the result in the downstream database in the database design support system, wherein the data in the extracted database is displayed from the input / output device. Extraction database editing means for displaying / editing in response to an editing request is provided, and the downstream database editing means is confident that the data in the downstream database is required to be merged in advance according to a setting request from the input / output device before being merged. Configured as a downstream database editing means with a confidence measure means for setting a degree, the extraction data merging means, when the data of the extraction database and the data of the downstream database are merged, the data set in the downstream database According to the confidence value of Database design support system for characterized by being configured to over-di as the reliability means with extracting data merge unit selectively perform. 2. The extracted data merging means stores the unmerged data of the extracted database and the data of the downstream database corresponding to the data in a merged unexecuted database. The database design support system according to claim 1, further comprising a merge-unexecuted database display unit configured as an extracted-data merge unit with a storage unit and displaying the data of the merge-unexecuted database on the input / output device. . 3. Downstream with confidence / confirmation means, wherein said downstream database editing means sets presence / absence of confirmation and a process at the time of confirming the unmerged data in the data of said downstream database. The database design support system according to claim 2, which is configured as a database editing means. 4. The upstream database input means inputs from the plurality of upstream databases the type of the upstream database in which the data was stored together with the data, and stores the data and the type in the internal upstream database. The extraction / automatic conversion rule unit is configured as a multiple extraction / automatic conversion rule unit in which extraction / automatic conversion rules for extracting / converting data from a plurality of upstream databases are stored. Claim 1 to 3 characterized by the above-mentioned.
The database design support system described in any of 1. 5. The extraction with an extraction information addition means for generating the extraction database by pairing the data of the internal upstream database with the type of the upstream database in which the data is stored. The database design support system according to claim 4, wherein the database design support system is configured as automatic conversion means.