WO2016147354A1

WO2016147354A1 - Database design assistance device and database design assistance program

Info

Publication number: WO2016147354A1
Application number: PCT/JP2015/058113
Authority: WO
Inventors: 貴洋嶋
Original assignee: 三菱電機株式会社
Priority date: 2015-03-18
Filing date: 2015-03-18
Publication date: 2016-09-22
Also published as: JPWO2016147354A1; JP6289735B2

Abstract

For each data item which chart data (11) comprises, an interface unit (110) accepts input of a classification type (13) which signifies whether the data item is discrete data, or aggregate data in which the discrete data have been aggregated. A processing unit (120) generates database definition information (21), which includes table definition information (22) in which the data items for which the classification type is the discrete data are treated as attributes, and hierarchy definition information (23) in which the data items for which the classification type (13) is the aggregate data are treated as parents, and the data items for which the classification type (13) is the discrete data are treated as children.

Description

Database design support apparatus and database design support program

This invention relates to a technology for supporting database design using tabular data.

場合 When an existing database system is improved and a new database system is constructed, the system builder designs the database and generates database definition information. At this time, the system builder generates the database definition information by using the design information of the existing system and the drawing in which the facility configuration information is described.

Patent Document 1 describes that database definition information is generated by inputting tabular data including data items and data belonging to the data items. In Patent Document 1, a data storage table of a database is constructed using one sheet of tabular data as one data unit. As a result, the load of database system construction work including acquisition of specialized knowledge such as a database language is reduced.

JP 2004-341770 A

In the technique described in Patent Document 1, data retrieval speed and application development efficiency are not considered at all, and a table having data items of tabular data as attributes is simply defined. Therefore, the system builder takes a long time to correct the generated database definition information.
An object of the present invention is to reduce the load on a system builder when designing a database.

The database design support apparatus according to the present invention is:
A group information receiving unit that receives input of group information indicating each group obtained by grouping a plurality of data items included in tabular data;
For each data item that the tabular data has, a type reception unit that receives input of a classification type indicating whether it is individual data or total data obtained by totaling the individual data;
A table definition unit for generating table definition information having an attribute indicating a data item whose classification type received by the type reception unit is individual data;
For each group indicated by the group information received by the group information reception unit, hierarchy definition information is generated with a data item whose classification type is aggregated data as a parent and a data item whose classification type is individual data as a child. And a hierarchy definition unit.

In this invention, a table having an attribute indicating a data item whose classification type is individual data is defined, and for a data item whose classification type is aggregated data, a hierarchy definition between the data item whose classification type is individual data Generate information. As a result, the number of table attributes can be reduced, and an efficient table is defined. Therefore, the load of correction work of the system builder is reduced, and the load of the system builder when designing the database can be reduced.

1 is a configuration diagram of a database design support apparatus 100 according to Embodiment 1. FIG. Explanatory drawing of the tabular data 11. FIG. Explanatory drawing of the item classification information 16. FIG. 5 is a flowchart showing the operation of the interface unit 110. Explanatory drawing of the input screen 31. FIG. The flowchart which shows the table definition process which is operation | movement of the table definition part 121. FIG. Explanatory drawing of a table definition process. 7 is a flowchart showing a hierarchy definition process that is an operation of the hierarchy definition unit 122; Explanatory drawing of a hierarchy definition process. The block diagram of the database design assistance apparatus 100 which concerns on Embodiment 2. FIG. Explanatory drawing of the unit conversion information 18. FIG. The flowchart which shows the calculation definition process which is operation | movement of the calculating part 123 and the calculation definition part 124. FIG. The flowchart which shows the calculation definition process which is operation | movement of the calculating part 123 and the calculation definition part 124. FIG. The figure which shows the operation example of the process shown in FIG. Explanatory drawing of the process shown in FIG. The figure which shows the operation example of the process shown in FIG. Explanatory drawing of the process shown in FIG. The figure which shows the hardware structural example of the database design assistance apparatus 100 which concerns on

Embodiment

1,2.

Embodiment 1 FIG.
*** Explanation of configuration ***
Based on FIG. 1, the structure of the database design support apparatus 100 which concerns on Embodiment 1 is demonstrated.
The database design support apparatus 100 includes an interface unit 110 and a processing unit 120.

The interface unit 110 is an interface with a user of the database design support apparatus 100 such as a system builder.
The interface unit 110 includes a data display unit 111, a group information reception unit 112, a type reception unit 113, a table information reception unit 114, and a generation instruction reception unit 115.

The data display unit 111 displays an input screen showing the tabular data 11 designated by the user on the display device. The tabular data 11 has a plurality of data items, and a value is set for each data item.
The data display unit 111 may display the tabular data 11 in a table state, or may display the tabular data 11 as a graph when the tabular data 11 can be displayed as a graph.

The group information receiving unit 112 receives input of group information 12 indicating each group obtained by grouping a plurality of data items included in the tabular data 11. Here, the group information receiving unit 112 receives the group information 12 input by the user operating the input screen displayed by the data display unit 111.

The type reception unit 113 receives an input of the classification type 13 as to whether each data item included in the tabular data 11 is individual data or total data obtained by tabulating the individual data. That is, for each data item, the type accepting unit 113 is individual data in which a measurement value or the like for a facility with the data item is set, or total data in which a value obtained by totaling values of a plurality of individual data is set The input of the classification type 13 is received. Here, the type receiving unit 113 receives an input of the classification type 13 input by the user operating the input screen displayed by the data display unit 111.

The table information receiving unit 114 receives an input of a table name 14 of a table for storing data of each data item included in the tabular data 11.
The table information receiving unit 114 may automatically set the file name of the tabular data 11 as the table name 14 when the table name 14 is not input.

The generation instruction reception unit 115 receives input of instruction information 15 that instructs the processing unit 120 to generate the database definition information 21.
When receiving the input of the instruction information 15, the generation instruction receiving unit 115 outputs the tabular data 11 displayed by the data display unit 111 to the processing unit 120. Further, the generation instruction receiving unit 115 includes an item classification including the group information 12 received by the group information receiving unit 112, the classification type 13 received by the type receiving unit 113, and the table name 14 received by the table information receiving unit 114. Information 16 is output to the processing unit 120.

Here, the group information receiving unit 112 includes a data item in which the classification type 13 is individual data and a data item in which the classification type 13 is total data. Group information 12 grouped so as to be the same group is received.

The processing unit 120 generates the database definition information 21 based on the item classification information 16 and the tabular data 11 output from the generation instruction receiving unit 115.
The processing unit 120 includes a table definition unit 121 and a hierarchy definition unit 122.

The table definition unit 121 generates table definition information 22 that is one of the database definition information 21. The table definition unit 121 has an attribute indicating a data item in which the classification type 13 received by the type reception unit 113 is individual data, and table definition information 22 having the table name 14 received by the table information reception unit 114 as the table name. Is generated.
Here, the table definition unit 121 does not have a data item whose classification type 13 is aggregated data in at least one of the groups as an attribute, and has only a data item whose classification type 13 is individual data as an attribute. Definition information 22 is generated.

The hierarchy definition unit 122 generates hierarchy definition information 23 that is one of the database definition information 21. The hierarchy definition unit 122 generates, for each group indicated by the group information 12, hierarchy definition information 23 having a data item whose classification type 13 is aggregated data as a parent and a data item whose classification type 13 is individual data as a child. .

The tabular data 11 will be described with reference to FIG.
The tabular data 11 has a plurality of data items, and a value is set for each data item. In the tabular data 11, a unit indicating a reference value of each data item is set.
In FIG. 2, tabular data 11 named file A is shown. The tabular data 11 has data for the entire building, 1F, 2F, and 3F, and the amount of power from January to December is set for each data item. In FIG. 2, KW (kilowatt) is set as the unit of the value of each data item.

The item classification information 16 will be described with reference to FIG.
The item classification information 16 has items of data item name, type, group name, unit, table name, and tabular data name for each of a plurality of data items.
The data item name indicates the name of the data item defined in the tabular data 11. The type indicates the classification type 13 of the data item received by the type receiving unit 113. The group name indicates a name for identifying a group of data items indicated by the group information 12 received by the group information receiving unit 112. The unit indicates the unit of the data item defined by the tabular data 11. The table name indicates the table name 14 for storing the data item received by the table information receiving unit 114. The tabular data name indicates the file name and file path of the tabular data 11.

*** Explanation of operation ***
The operation of the database design support apparatus 100 according to the first embodiment will be described with reference to FIGS.
The operation of the database design support apparatus 100 according to the first embodiment corresponds to the database design support method according to the first embodiment. The operation of the database design support apparatus 100 according to the first embodiment corresponds to the processing of the database design support program according to the first embodiment.

The operation of the interface unit 110 will be described with reference to FIGS.
In the data display process of S101, the data display unit 111 displays an input screen 31 as shown in FIG. 5 showing the tabular data 11 designated by the user.
The input screen 31 includes a display field 32 for tabular data 11 and a display field 33 for item classification information 16. The display column 32 for the tabular data 11 includes a selection column 34 for the tabular data 11. When the selection button is pressed while the table format data 11 designated in the selection field 34 is shown, the table format data 11 is designated, and the designated table format data 11 is displayed. Here, tabular data 11 named file A shown in FIG. 2 is designated, and tabular data 11 is displayed as a graph.

In the group information reception process in S102, the type reception process in S103, and the table information reception process in S104, the group information reception unit 112, the type reception unit 113, and the table information reception unit 114 are operated by the user on the input screen 31. Then, various information constituting the item classification information 16 is received.
Here, in the group information receiving process, the group information receiving unit 112 receives the group information 12 having the entire building, 1F, 2F, and 3F data items as one group and the name as BUILD. In the type reception process, the type reception unit 113 indicates that the data is total data for the entire building, and receives a classification type 13 that indicates individual data for 1F, 2F, and 3F. In the table information receiving process, the table information receiving unit 114 receives a table name 14 called TableA.

In the generation instruction reception process of S105, the generation instruction reception unit 115 receives the input of the instruction information 15, and outputs the item classification information 16 and the tabular data 11 to the processing unit 120.
Here, when receiving the input of the instruction information 15, the generation instruction receiving unit 115 outputs the item classification information 16 shown in FIG. 3 and the tabular data 11 shown in FIG. 2 to the processing unit 120.

The operation of the processing unit 120 will be described with reference to FIGS.
First, based on FIG.6 and FIG.7, the table definition process which is operation | movement of the table definition part 121 is demonstrated.
In the information acquisition process of S201, the table definition unit 121 acquires the item classification information 16 output in S105.

In the item acquisition process of S202, the table definition unit 121 acquires one data item from the item classification information 16 acquired in S201.

In the type determination process of S203, the table definition unit 121 determines whether or not the classification type 13 of the data item acquired in S202 is individual data. If the table definition unit 121 is individual data (YES in S203), the process proceeds to S204. If the table definition unit 121 is total data (NO in S203), the process proceeds to S205.

In the attribute addition process of S204, the table definition unit 121 adds an attribute indicating the data item acquired in S202 to the table definition information 22.
Specifically, if there is no table whose name is the table name 14 of the data item acquired in S202, the table definition unit 121 adds the name table to the table definition information 22 and then adds the data item. Add an attribute whose name is the name. On the other hand, when there is a table whose name is the table name 14 of the data item acquired in S202, the table definition unit 121 adds an attribute whose name is the data item name to the table.

In the attribute determination process of S205, the table definition unit 121 determines whether an attribute indicating the data item acquired in S202 exists in the table definition information 22.
Specifically, the table definition unit 121 determines whether or not the table definition information 22 includes an attribute having the name of the data item name in the table having the name of the table name 14 acquired in S202.
If the table definition unit 121 exists (YES in S205), the process proceeds to S206. If the table definition unit 121 does not exist (NO in S205), the process proceeds to S207.

In the attribute deletion process of S206, the table definition unit 121 deletes the attribute indicating the data item acquired in S202 from the table definition information 22.
Specifically, the table definition unit 121 deletes from the table definition information 22 the attribute whose name is the data item name of the table whose name is the table name 14 acquired in S202.

In the item determination process of S207, the table definition unit 121 determines whether or not the data item acquired in S202 is the last data item of the item classification information 16 acquired in S201.
If it is the last data item (YES in S207), the table defining unit 121 advances the process to S208. If it is not the last data item (NO in S207), the table defining unit 121 returns the process to S202.

In the conversion process of S208, the table definition unit 121 converts the table definition information 22 into a database operation language. Here, the table definition unit 121 converts the table definition information 22 into SQL (Structured Query Language).

Here, as shown in FIG. 7, the table definition process generates table definition information 22 in which a table called TableA having attributes of 1F, 2F, and 3F whose classification type 13 is individual data is defined. Then, the table definition information 22 is subjected to SQL conversion.

Next, the hierarchy definition process that is the operation of the hierarchy definition unit 122 will be described with reference to FIGS.
In the information acquisition process of S301, the hierarchy definition unit 122 acquires the item classification information 16 output in S105.

In the item acquisition process of S302, the hierarchy definition unit 122 acquires one data item from the item classification information 16 acquired in S301.

In the type determination process of S303, the hierarchy definition unit 122 determines whether or not the classification type 13 of the data item acquired in S302 is total data. The hierarchy definition unit 122 advances the process to S304 if the data is aggregate data (YES in S303), and advances the process to S308 if the data is individual data (NO in S303).

In the first hierarchy determination process of S304, the hierarchy definition unit 122 determines whether or not individual data of the same group exists in the hierarchy definition information 23.
Specifically, the hierarchy definition unit 122 includes a data item having the same group name as the data item group name acquired in S <b> 302 and having the classification type 13 as individual data in the hierarchy definition information 23. It is determined whether or not.
If the hierarchy definition unit 122 does not exist (NO in S304), the process proceeds to S305, and if it exists (YES in S304), the process proceeds to S306.

In the first initial hierarchy setting process of S305, the hierarchy definition unit 122 adds the data item acquired in S302 to the hierarchy definition information 23 as an element of the i hierarchy that is the initial hierarchy for the aggregated data.

In the first hierarchy acquisition process of S306, the hierarchy definition unit 122 acquires the hierarchy j of the individual data of the same group. In the parent hierarchy setting process of S307, the hierarchy definition unit 122 adds the data item acquired in S302 to the hierarchy definition information 23 as an element of the hierarchy j-1 that is the parent hierarchy of the hierarchy j acquired in S306. To do.

In the second hierarchy determination process of S308, the hierarchy definition unit 122 determines whether or not the aggregate data of the same group exists in the hierarchy definition information 23.
More specifically, the hierarchy definition unit 122 includes a data item having the same group name as the data item group name acquired in S <b> 302, and a data item whose classification type 13 is aggregated data exists in the hierarchy definition information 23. It is determined whether or not.
If the hierarchy definition unit 122 does not exist (NO in S308), the process proceeds to S309, and if it exists (YES in S308), the process proceeds to S310.

In the second initial hierarchy setting process of S309, the hierarchy definition unit 122 adds the data item acquired in S302 to the hierarchy definition information 23 as an element of the k hierarchy that is the initial hierarchy for the individual data.

In the second hierarchy acquisition process of S310, the hierarchy definition unit 122 acquires the hierarchy m of the aggregate data of the same group. Then, in the child hierarchy setting process of S311, the hierarchy definition unit 122 adds the data item acquired in S302 to the hierarchy definition information 23 as an element of the hierarchy m + 1 that is a child hierarchy of the hierarchy m acquired in S310.

In the item determination process of S312, the hierarchy definition unit 122 determines whether the data item acquired in S302 is the last data item of the item classification information 16 acquired in S301.
If it is the last data item (YES in S312), the hierarchy defining unit 122 advances the process to S313, and if it is not the last data item (NO in S312), returns the process to S302.

In the conversion process of S313, the hierarchy definition unit 122 converts the hierarchy definition information 23 into a database operation language. Here, the hierarchy definition unit 122 performs SQL conversion on the hierarchy definition information 23.

Here, as shown in FIG. 9, the hierarchy definition information 23 is defined as 1F, 2F, and 3F in which the classification type 13 is the individual data, and the classification type 13 is the individual data. Is generated. Then, the hierarchy definition information 23 is subjected to SQL conversion.

*** Explanation of effects ***
As described above, in the database design support apparatus 100 according to the first embodiment, the database definition information including the table definition information 22 and the hierarchy definition information 23 is obtained by operating the table format data 11 output from the existing system or the like. 21 can be generated. In particular, in the database definition information 21, the table definition information 22 has only data items whose classification type 13 is individual data as attributes.
Therefore, the number of table attributes can be reduced, and an efficient table is defined. Therefore, the load of correction work of the system builder is reduced, and the load of the system builder when designing the database can be reduced.

In the database design support apparatus 100 according to the first embodiment, the operation of the tabular data 11 does not require understanding of design information and acquisition of specialized knowledge such as a database language. As a result, the load on the system builder's prior work is reduced, and the load on the system builder when designing the database can be reduced.

Further, when the tabular data 11 is output from an existing system, users of the existing system often have experience using the tabular data 11. Therefore, in this case, the operation of the tabular data 11 can be performed even by a user who uses an existing system or the like. In particular, a simple system database design such as a demo system can be performed even by a user.

In the above description, the case where only one tabular data 11 is targeted has been described. However, a plurality of tabular data 11 can be targeted.
When a plurality of tabular data 11 are targeted, the interface unit 110 may perform the processing from S101 to S105 of FIG. At this time, if the same table name 14 is designated in S104, data items in the plurality of tabular data 11 can be set as attributes of one table.

When a plurality of tabular data 11 are targeted, in the processing shown in FIG. 6, depending on the execution order, a data item whose classification type 13 is aggregated data in a certain tabular data 11 is included in the table definition information 22 as an attribute. May be defined.
For example, it is assumed that the data item X is individual data in the tabular data 11Y and is total data in the tabular data 11Z. In this case, if the tabular data 11Y is processed before the tabular data 11Z, the data item X is defined as an attribute in the processing of the tabular data 11Y, but the data item X is defined in the processing of the tabular data 11Z. The attribute that defined is deleted. Therefore, the data item X is not defined in the table definition information 22 as an attribute. However, when the tabular data 11Z is processed before the tabular data 11Y, the data item X is not defined as an attribute in the processing of the tabular data 11Z, and the data item X is defined as an attribute in the processing of the tabular data 11Y. Defined. Therefore, the data item X is defined in the table definition information 22 as an attribute.
Therefore, after the process for all the tabular data 11 is completed, the attribute deletion process of S206 may be executed for the data item whose classification type 13 is the total data in all the tabular data 11. Thereby, it is possible to prevent a data item in which the classification type 13 is aggregated data in a certain table format data 11 from being defined in the table definition information 22 as an attribute.

Further, in the above description, the table format data 11 is assumed to have a unit set for the value of each data item. However, there may be a case where no unit is set. In this case, the table information reception part 114 should just receive the unit input about the value of each data item with the table name 14. FIG.

Embodiment 2. FIG.
The second embodiment is different from the first embodiment in that calculation definition information 24 that defines a method for calculating aggregate data by using individual data as input is generated. In the second embodiment, this different point will be described.

*** Explanation of configuration ***
Based on FIG. 10, the structure of the database design assistance apparatus 100 which concerns on Embodiment 2 is demonstrated.
1 differs from the database design support apparatus 100 shown in FIG. 1 in that the interface unit 110 includes a calculation information acquisition unit 116 and a unit conversion information acquisition unit 117, and the processing unit 120 includes a calculation unit 123 and a calculation definition unit 124.

The calculation information acquisition unit 116 acquires a plurality of calculation information 17 indicating a calculation method.
Here, the tabular data 11 is data in a format corresponding to the spreadsheet software. The calculation information acquisition unit 116 acquires calculation information 17 indicating calculation methods such as summation and averaging, which are defined by the spreadsheet software corresponding to the tabular data 11, from the spreadsheet software.

The unit conversion information acquisition unit 117 acquires a plurality of unit conversion information 18 indicating a conversion method for converting a unit indicating a value reference to another unit.
Here, the unit conversion information 18 is registered in advance by a user or the like, and the unit conversion information acquisition unit 117 acquires the registered unit conversion information 18. The unit conversion information 18 may be input when the tabular data 11 is specified, or may be acquired from an external server or the like.

The calculation unit 123 uses the data item whose classification type 13 is aggregated data as a target item, and receives the value of the data item whose classification type 13 in the same group as the target item is individual data, and the calculation information acquisition unit 116 acquires it. Calculation is performed by a calculation method indicated by each calculation information 17.
When the unit of the value of the target item is different from the unit of the value of the data item that is individual data, the calculation unit 123 uses the unit conversion information 18 acquired by the unit conversion information acquisition unit 117 to The unit of the value of the data item whose classification type 13 in the same group is individual data is converted into the unit of the value of the target item. Then, the calculation unit 123 performs the calculation by the calculation method indicated by each calculation information 17 after the conversion.

The calculation definition unit 124 generates calculation definition information 24 that is one of the database definition information 21. The calculation definition unit 124 generates the calculation information 17 indicating the calculation method when the result calculated by the calculation unit 123 matches the value of the target item as the calculation definition information 24 for the target item. When the calculation unit 123 uses the unit conversion information 18 to convert units, the calculation definition unit 124 generates the calculation definition information 24 by combining the calculation information 17 and the used unit conversion information 18.

The unit conversion information 18 will be described based on FIG.
The unit conversion information 18 indicates a conversion method for converting a unit to another unit. Here, each unit conversion information 18 has a unit after conversion and a conversion formula to the unit after conversion.
FIG. 11 shows a conversion formula “unit A (ampere) × unit V (volt)” for the unit W (watt) that is the unit after conversion and a conversion formula “( 2.8 × 10 ⁻⁶ ) units KW (kilowatts) ”.

*** Explanation of operation ***
The operation of the database design support apparatus 100 according to the second embodiment will be described with reference to FIGS. Here, the calculation definition process which is the operation of the calculation unit 123 and the calculation definition unit 124 will be described.
The operation of the database design support apparatus 100 according to the second embodiment corresponds to the database design support method according to the second embodiment. The operation of the database design support apparatus 100 according to the second embodiment corresponds to the processing of the database design support program according to the second embodiment.

In the information acquisition process of S401, the calculation unit 123 acquires the item classification information 16 and the plurality of calculation information 17 output in S105.

In the tabular data acquisition process of S402, the calculation unit 123 acquires all data items for the target data from the item classification information 16 acquired in S401, with one tabular data 11 as target data.
In the group acquisition process in S403, the calculation unit 123 acquires all the data items for the target group from the data items acquired in S402, with one group as the target group.

In the first calculation information acquisition process of S404, the calculation unit 123 acquires one calculation information 17 from the calculation information 17 acquired in S401.
In the first calculation execution process of S405, the calculation unit 123 receives the value of the data item whose classification type 13 in the target group is individual data, and executes the calculation by the calculation method indicated by the calculation information 17 acquired in S404. .
In the first result determination process of S406, the calculation unit 123 determines whether the result calculated in S405 matches the value of the data item (target item) whose classification type 13 in the target group is aggregated data. . If they match (YES in S406), operation unit 123 advances the process to S407, and if they do not match (NO in S406), advances the process to S408.

In the first calculation definition process of S407, the calculation definition unit 124 generates the calculation information 17 acquired in S404 as the calculation definition information 24 for the target item.

In the first difference calculation process of S408, the calculation unit 123 calculates the difference between the result calculated in S405 and the value of the target item and registers it in the difference list.
In the first calculation determination process of S409, the calculation unit 123 determines whether or not the calculation information 17 acquired in S404 is the last calculation information 17 acquired in S401. If the calculation unit 123 is the last calculation information 17 (YES in S409), the process proceeds to S501 in FIG. 13, and if it is not the last calculation information 17 (NO in S409), the process returns to S404.

In the group determination processing in S410, the calculation unit 123 determines whether the data item for the target group acquired in S403 is the data item for the last group in the tabular data 11 acquired in S402. . If it is a data item for the last group (YES in S410), the arithmetic unit 123 advances the process to S411, and if it is not a data item for the last group (NO in S410), returns the process to S403.

In the tabular data determination process in S411, the calculation unit 123 determines whether the data item for the target data acquired in S402 is the data item for the last tabular data 11 in the item classification information 16 acquired in S401. Determine whether or not. If it is a data item for the last tabular data 11 (YES in S411), the calculation unit 123 ends the process, and if it is not a data item for the last tabular data 11 (NO in S411), the processing is performed in S402. Return to.

In the unit acquisition process of S501, the calculation unit 123 acquires one data item whose classification type 13 of the target group is individual data together with the value unit of the data item.

In the unit determination process in S502, the calculation unit 123 determines whether the value unit of the target item is the same as the value unit of the data item acquired in S501. If they are the same (YES in S502), operation unit 123 advances the process to S503, and if not (NO in S502), advances the process to S504.

In the item addition process of S503, the calculation unit 123 adds the data item acquired in S501 to the target list.

In the unit conversion information acquisition process of S504, the calculation unit 123 acquires the unit conversion information 18 including the unit of the target item as the unit after conversion and including the unit of the value of the data item acquired in S501 in the conversion formula.
That is, the calculation unit 123 acquires the unit conversion information 18 for converting from the data item value unit acquired in S501 to the target item value unit.

In the conversion formula generation process of S505, the calculation unit 123 replaces the unit of the value of the data item acquired in S501 of the conversion formula in the unit conversion information 18 acquired in S504 with the data item acquired in S501.
In addition, the calculation unit 123 acquires a data item having the remaining unit in the conversion formula from the data item of the target group. Then, the remaining units in the conversion formula are replaced with corresponding data items.
Thereby, the calculating part 123 produces | generates a unit conversion type | formula.

In the formula addition process of S506, the calculation unit 123 adds the unit conversion formula generated in S505 to the target list.

In the item determination process of S507, the calculation unit 123 determines whether or not the data item acquired in S501 is the last data item whose classification type 13 in the target group is individual data. At this time, the data item acquired in S505 is treated as acquired.
If it is the last data item (YES in S507), the arithmetic unit 123 advances the process to S508, and if it is not the last data item (NO in S507), returns the process to S501.

In the second calculation information acquisition process of S508, the calculation unit 123 acquires one calculation information 17 from the calculation information 17 acquired in S401.
In the aggregation formula generation process of S509, the calculation unit 123 is acquired in S508 using the data items added to the target list in S503 and the data items constituting the unit conversion formula added to the target list in S506. An aggregation formula that constitutes the calculation method indicated by the calculation information 17 is generated.
In the second calculation execution process of S510, the calculation unit 123 inputs the value of the data item to the aggregation formula generated in S509, and executes the calculation by the calculation method indicated by the calculation information 17 acquired in S508.
In the second result determination process of S511, the calculation unit 123 determines whether the result calculated in S510 matches the value of the target item. If they match (YES in S511), operation unit 123 advances the process to S512, and if they do not match (NO in S511), advances the process to S513.

In the second calculation definition process of S512, the calculation definition unit 124 generates the aggregation formula generated in S509 as the calculation definition information 24 for the target item.

In the second difference calculation process of S513, the calculation unit 123 calculates the difference between the result calculated in S510 and the value of the target item, and registers it in the difference list.
In the second calculation determination process in S514, the calculation unit 123 determines whether or not the calculation information 17 acquired in S508 is the last calculation information 17 acquired in S401. If the calculation unit 123 is the last calculation information 17 (YES in S514), the process proceeds to S515. If the calculation unit 123 is not the last calculation information 17 (NO in S514), the process returns to S508.

In the third calculation definition process of S515, the calculation definition unit 124 generates, as the calculation definition information 24 for the target item, the calculation information 17 or the aggregation formula having the smallest difference among the differences registered in the difference list.

Based on FIGS. 14 and 15, an example of the operation of the process shown in FIG. 12 will be described.
First, in step S401, item classification information 16 and a plurality of calculation information 17 are acquired ((1) to (2) in FIG. 14). Further, in S402 to S403, all data items of the file “Group” “BUILD” are acquired ((3) in FIG. 14).
In S404, “total” for calculating the total value of the input values is obtained as one piece of calculation information 17 ((4) in FIG. 14). Then, in S405, the calculation method indicated by the calculation information 17 using the values “1000”, “500”, and “250” set in the data items “1F”, “2F”, and “3F” of the individual data as inputs. The calculation is executed by “total” ((5) in FIG. 14). In S406, it is determined whether or not the calculation result “1750 (= 1000 + 500 + 250)” matches the value “1750” set in the “entire building” data item of the total data ((6 in FIG. 14). )).
Since they match here, in S407, “total” is generated as the calculation definition information 24 of “entire building” which is the data item of the total data ((7) in FIG. 14). That is, the value of “entire building” is defined as the sum of the values set in “1F”, “2F”, and “3F”.

Here, as shown in FIG. 15, the values set for the entire building whose classification type 13 is aggregated data are the values set for 1F, 2F and 3F whose classification type 13 is individual data, as shown in FIG. The operation definition information 24 that is defined to be the sum of is generated. Here, the calculation definition information 24 is generated as the data search viewpoint definition information 25 together with the hierarchy definition information 23. Then, the data retrieval viewpoint definition information 25 is subjected to SQL conversion.

Based on FIGS. 16 and 17, an example of the operation of the process shown in FIG. 13 will be described.
First, in step S401, item classification information 16 and a plurality of calculation information 17 are acquired ((1) to (2) in FIG. 16). Further, in S402 to S403, all data items of the file “B” group “BUILD” are acquired ((3) in FIG. 16).
Here, no matter what the calculation information 17 is calculated, the calculation result and the value set to “1F” which is the data item of the total data do not match in S406. Therefore, the process proceeds from S409 to S501 in FIG.
In S501, the data item “1F_voltage” of the individual data is acquired together with the unit “KV (kilovolt)” ((4) in FIG. 16). In S502, it is determined that the unit “KV” is different from the unit “KW” of the value of the data item “1F” of the total data, and in S504, the unit conversion information 18 including the unit “KV” is acquired (FIG. 16). (5)). In S505, the unit “KV” in the conversion formula of the unit conversion information 18 is replaced with the data item “1F_voltage”, and the remaining unit “KA” is replaced with the corresponding data item “1F_current” to generate the unit conversion formula. ((6) in FIG. 16). In S506, the unit conversion formula is added to the target list ((7) in FIG. 16).
The data item “1F_other” of the remaining individual data is added to the target list in S503 because the unit “KW” is the same as the unit “KW” of the value of the data item “1F” of the total data (FIG. 16). (8)).

In S508, “total” is acquired as one piece of operation information 17 ((9) in FIG. 16). Using the unit conversion formula and the data items added to the target list in S509, a totaling formula constituting the calculation method “total” is generated ((10) in FIG. 16).
In S510, the values “50”, “20”, “500” set in the data items “1F_voltage”, “1F_current”, and “1F_other”, which are individual data items, are input and the calculation is performed using the aggregation formula. ((11) in FIG. 16). In S511, the calculation result “1500 (= (20 × 50) +500)” and the value “1500” set to “1F” which is the data item of the total data match, so in S512, the total formula is The calculation definition information 24 of “1F” which is a data item of the total data is used ((12) in FIG. 16). That is, the value of “1F” is defined as a value obtained by tabulating the values set in “1F_Voltage”, “1F_Current”, and “1F_Other” by the tabulation formula.

Here, as shown in FIG. 17, the value in which the classification type 13 is set to 1F, which is total data, is set to 1F_voltage, 1F_current, 1F_, etc., in which the classification type 13 is individual data, as shown in FIG. Operation definition information 24 is generated that is defined to be a value obtained by tabulating the obtained values with a summation formula. Here, the calculation definition information 24 is generated as the data search viewpoint definition information 25 together with the hierarchy definition information 23. Then, the data retrieval viewpoint definition information 25 is subjected to SQL conversion.

In the description of FIG. 14 and FIG. 15, the calculation is performed on the data for January, and it is determined whether the calculation result matches the value of the total data. However, an operation may be performed on the data for each month, and it may be determined whether or not the operation result and the value of the aggregate data match for all the month data.

As described above, the database design support apparatus 100 according to Embodiment 2 defines a calculation method for data items whose classification type 13 is aggregated data, based on the calculation information 17 used in the tabular data 11. Thereby, it is possible to generate the database definition information 21 that can calculate the value of the data item that is not generated as an attribute of the table from the value of the data item generated as the attribute. As a result, it is possible to reduce the load on the system builder when designing the database.

Further, in the database design support apparatus 100 according to the second embodiment, when the calculation is not possible only by the calculation information 17 used in the tabular data 11 due to different units, the calculation method is performed by converting the units. Define As a result, it is possible to reduce the load on the system builder when designing the database.

FIG. 18 is a diagram illustrating a hardware configuration example of the database design support apparatus 100 according to the first and second embodiments.
The database design support apparatus 100 is a computer.
The database design support apparatus 100 includes hardware such as a processor 901, an auxiliary storage device 902, a memory 903, a communication device 904, an input interface 905, and a display interface 906.
The processor 901 is connected to other hardware via the signal line 910, and controls these other hardware.
The input interface 905 is connected to the input device 907 by a cable 911.
The display interface 906 is connected to the display 908 by a cable 912.

The processor 901 is an IC (Integrated Circuit) that performs processing. The processor 901 is, for example, a CPU (Central Processing Unit), a DSP (Digital Signal Processor), or a GPU (Graphics Processing Unit).
The auxiliary storage device 902 is, for example, a ROM (Read Only Memory), a flash memory, or an HDD (Hard Disk Drive).
The memory 903 is, for example, a RAM (Random Access Memory).
The communication device 904 includes a receiver 9041 that receives data and a transmitter 9042 that transmits data. The communication device 904 is, for example, a communication chip or a NIC (Network Interface Card).
The input interface 905 is a port to which the cable 911 of the input device 907 is connected. The input interface 905 is, for example, a USB (Universal Serial Bus) terminal.
The display interface 906 is a port to which the cable 912 of the display 908 is connected. The display interface 906 is, for example, a USB terminal or an HDMI (registered trademark) (High Definition Multimedia Interface) terminal.
The input device 907 is, for example, a mouse, a keyboard, or a touch panel.
The display 908 is, for example, an LCD (Liquid Crystal Display).

The auxiliary storage device 902 includes the interface unit 110, the data display unit 111, the group information reception unit 112, the type reception unit 113, the table information reception unit 114, the generation instruction reception unit 115, the calculation information acquisition unit 116, and unit conversion information. Acquisition unit 117, processing unit 120, table definition unit 121, hierarchy definition unit 122, calculation unit 123, calculation definition unit 124 (hereinafter, interface unit 110, data display unit 111, group information reception unit 112, type reception unit 113, table The information reception unit 114, the generation instruction reception unit 115, the calculation information acquisition unit 116, the unit conversion information acquisition unit 117, the processing unit 120, the table definition unit 121, the hierarchy definition unit 122, the calculation unit 123, and the calculation definition unit 124 are collectively referred to as “ A program that realizes the function of “part” is stored.
This program is loaded into the memory 903, read into the processor 901, and executed by the processor 901.
Further, the auxiliary storage device 902 also stores an OS (Operating System).
Then, at least a part of the OS is loaded into the memory 903, and the processor 901 executes a program that realizes the function of “unit” while executing the OS.
In FIG. 18, one processor 901 is illustrated, but the database design support apparatus 100 may include a plurality of processors 901. A plurality of processors 901 may execute a program for realizing the function of “unit” in cooperation with each other.
In addition, information, data, signal values, and variable values indicating the results of the processing of “unit” are stored as files in the memory 903, the auxiliary storage device 902, or a register or cache memory in the processor 901.

“Parts” may be provided by “Circuitry”. Further, “part” may be read as “circuit”, “process”, “procedure”, or “processing”. “Circuit” and “Circuitry” include not only the processor 901 but also other types of processing circuits such as logic IC, GA (Gate Array), ASIC (Application Specific Integrated Circuit), or FPGA (Field-Programmable Gate Array). It is a concept to include.

100 database design support device, 110 interface unit, 111 data display unit, 112 group information reception unit, 113 type reception unit, 114 table information reception unit, 115 generation instruction reception unit, 116 calculation information acquisition unit, 117 unit conversion information acquisition unit , 120 processing section, 121 table definition section, 122 hierarchy definition section, 123 calculation section, 124 calculation definition section, 11 tabular data, 12 group information, 13 classification type, 14 table name, 15 instruction information, 16 item classification information, 17 calculation information, 18 unit conversion information, 21 database definition information, 22 table definition information, 23 hierarchy definition information, 24 calculation definition information, 25 data search viewpoint definition information.

Claims

A group information receiving unit that receives input of group information indicating each group obtained by grouping a plurality of data items included in tabular data;
For each data item that the tabular data has, a type reception unit that receives input of a classification type indicating whether it is individual data or total data obtained by totaling the individual data;
A table definition unit for generating table definition information having an attribute indicating a data item whose classification type received by the type reception unit is individual data;
For each group indicated by the group information received by the group information reception unit, hierarchy definition information is generated with a data item whose classification type is aggregated data as a parent and a data item whose classification type is individual data as a child. A database design support apparatus comprising a hierarchy definition unit.
The group information is a group in which a data item whose classification type is individual data and a data item whose classification type is individual data are aggregated into the same group. Show each group divided,
The database design support device further includes:
A calculation information acquisition unit for acquiring a plurality of calculation information indicating a calculation method;
Each calculation information acquired by the calculation information acquisition unit using a data item whose classification type is aggregated data as a target item and a value of a data item whose classification type is individual data in the same group as the target item is input. A calculation unit that calculates using the calculation method shown;
2. The database according to claim 1, further comprising: an operation definition unit that generates operation information indicating an operation method in a case where a result calculated by the operation unit coincides with a value of the target item, as operation definition information about the target item. Design support device.
The database design support device further includes:
A unit conversion information acquisition unit for acquiring a plurality of unit conversion information indicating a conversion method for converting a unit indicating a value reference into another unit;
The arithmetic unit uses any of the unit conversion information acquired by the unit conversion information acquisition unit, and sets the unit of the value of the data item whose classification type is individual data in the same group as the target item. After converting to the unit of the value of the item, it is calculated by the calculation method indicated by each calculation information,
The calculation definition unit generates calculation definition information by combining calculation information indicating a calculation method when the calculation result of the calculation unit matches the value of the target item and the unit conversion information used. The database design support apparatus according to claim 2.
The database design support device further includes:
A data display unit for displaying an input screen including the tabular data;
The group information receiving unit receives the group information input by a user operating an input screen displayed by the data display unit,
The database design support apparatus according to any one of claims 1 to 3, wherein the type receiving unit receives the classification type input by a user operating an input screen displayed by the data display unit.
The tabular data is data in a format corresponding to spreadsheet software,
The database design support apparatus according to claim 2, wherein the calculation information acquisition unit acquires calculation information defined by the spreadsheet software from the spreadsheet software.
A group information receiving process for receiving input of group information indicating each group obtained by grouping a plurality of data items included in the tabular data;
For each data item included in the tabular data, a type reception process for receiving an input of a classification type, which is individual data or total data obtained by totaling the individual data;
A table definition process for generating table definition information having an attribute indicating a data item whose classification type received in the type reception process is individual data;
For each group indicated by the group information received in the group information receiving process, hierarchy definition information is generated with a data item whose classification type is aggregated data as a parent and a data item whose classification type is individual data as a child. A database design support program that causes a computer to execute hierarchy definition processing.