JP2020197839A - Data management program, data management method and data management system - Google Patents

Abstract

To support changes to entity data created based on an object-oriented data model flexibly.SOLUTION: A data management program causes a computer to generate meta data from a product information data schema 110 of an object-oriented data model description (S101), generate a schema ID for each product information data schema 110 (S102), register the meta data in a data dictionary 111 using the schema ID as a key (S103) ("data dictionary registration"), and create a product information database 112 to store product information entity data by referring to the meta data registered in the data dictionary 111 (S104) ("product information database creation"), so as to store and extract the product information entity data in/from the product information database 112.SELECTED DRAWING: Figure 1

Description

The present invention relates to a data management program, a data management method and a data management system.

Conventionally, for large-scale and long-term products such as civil engineering / buildings and aircraft / ships, the life cycle includes the planning / design stage, construction / manufacturing stage, and post-shipment operation / maintenance stage of the product. It is required to accumulate and manage product information as a whole. In order to make it possible to handle information on the entire life cycle related to such products, a product information model that employs an object-oriented data modeling method has been proposed and specified.

On the other hand, in order to accumulate and manage the actual data which are these product information data for a long period of time, for example, a relational database having excellent ACID characteristics is suitable. Therefore, in order to store and manage the actual data created based on the object-oriented data model on a computer, a mechanism has been proposed in which the data is converted into a relational model and the data is efficiently manipulated.

As a related prior art, there is a technology for accumulating and managing actual data created based on an object-oriented data model on a computer.

Japanese Unexamined Patent Publication No. 2001-195297 JP-A-2004-46650 Japanese Unexamined Patent Publication No. 2005-202850

However, during a long operation period, changes such as addition / update of the product information model itself, that is, the object-oriented data model itself may be made, and in the prior art, the substance based on these changes is made. There is a problem that data cannot be unified and managed.

In one aspect, it is an object of the present invention to flexibly respond to changes in an object-oriented data model and to manage real data based on the changes in a unified manner.

In one embodiment, the metadata of the information is generated from the data schema of the information created based on the object-oriented data model, the metadata is registered in the data dictionary, and the meta registered in the data dictionary. A data management program is provided, which comprises causing a computer to perform processing by referring to data and creating a database related to the information from the data schema.

According to one aspect of the present invention, it is possible to uniformly manage the actual data created based on the object-oriented data model.

FIG. 1 is an explanatory diagram showing an example of an outline of a data management program according to an embodiment. FIG. 2 is an explanatory diagram showing an example of the configuration of the data management system according to the embodiment. FIG. 3 is a block diagram showing an example of a hardware configuration of an information processing device (server, information terminal device) constituting the data management system according to the embodiment. FIG. 4 is a block diagram showing an example of the functional configuration of the data management system according to the embodiment. FIG. 5 is an explanatory diagram showing an example of the configuration of the data dictionary. FIG. 6 is an explanatory diagram showing an example of the configuration of the product information database. FIG. 7 is a flowchart showing an example of the procedure for registering metadata in the data dictionary. FIG. 8 is a flowchart showing an example of a procedure for registering data in the product information database definition table. FIG. 9 is a flowchart showing an example of the procedure for registering data in the class definition table. FIG. 10 is a flowchart showing an example of a procedure for registering data in the attribute definition table. FIG. 11 is a flowchart showing an example of a product information database creation procedure (instance table generation). FIG. 12 is a flowchart showing an example of a product information database creation procedure (class table generation). FIG. 13 is a flowchart showing an example of a data access control procedure (data registration) to the product information database. FIG. 14 is a flowchart showing an example of a data access control procedure (data acquisition) for the product information database.

The data management program, the data management method, and the embodiment of the data management system according to the present invention will be described in detail with reference to the drawings below.

(Embodiment)
(Overview of data management program)
FIG. 1 is an explanatory diagram showing an example of an outline of a data management program according to an embodiment. In FIG. 1, the data management program according to the present embodiment registers the metadata generated from the product information data schema 110 in the data dictionary 111 (“data dictionary registration”), and is registered in the data dictionary 111. By creating the product information database 112 that stores the actual product information data (“creating the product information database”) by referring to the metadata, the actual data of the product information is saved and extracted from the product information database 112. can do.

Specifically, first, the metadata of the product information database 112 created in step S104 is generated from the product information data schema 110 of the object-oriented data model description (step S101). Next, one schema ID is generated for one product information data schema 110 (step S102). Thereby, the metadata can be managed by the schema ID. Then, the metadata generated in step S101 is registered in the data dictionary 111 with the schema ID generated in step S102 as the primary key (step S103).

In this way, the data management program performs "data dictionary registration" in steps S101 to S103. The detailed procedure for registering the data dictionary will be described with reference to FIGS. 7 to 10 described later. This is the first feature of the data management program according to the embodiment.

Next, the product information database 112 is created from the product information data schema 110 of the object-oriented data model description with reference to the metadata registered in the data dictionary 111 in step S103 (step S104). In this way, the data management program "creates the product information database" in step S104. The detailed procedure for creating the product information database will be described with reference to FIGS. 11 and 12 described later. This is the second feature of the data management program according to the embodiment.

Further, the schema ID generated in step S102 and the instance ID of the entity data are used as primary keys to access the entity data on the relational database (step S105). Then, the actual data of the product information is stored or extracted from the product information database 112 (step S106). The detailed procedure of data access to the product information database 112 will be described later in FIGS. 13 and 14.

In this way, the data management program, data management method, and data management system according to the embodiment unify the actual data having different product information data schemas by performing "data dictionary registration" and "product information database creation". Can be managed. As a result, it is possible to flexibly respond to additions and changes of the product information model itself.

(Data management system configuration)
FIG. 2 is an explanatory diagram showing an example of the overall configuration of the data management system according to the embodiment. In FIG. 2, the data management system 200 includes a server 201, which is an example of an information processing device, and an information terminal device 202, which is another example of an information processing device. The information terminal device 202 is connected to the server 201 via the network 203, respectively.

The server 201 manages the entire data management system 200 and transmits / receives information to / from each information terminal device 202. Further, the data dictionary 111 and the product information database 112 may be provided in the server 201, or may be communicably connected to the server 201. Then, the server 201 manages data input / output, update, and the like of the data dictionary 111 and the product information database 112. In this way, the server 201 can realize the function of the data management system according to the embodiment.

Further, the server 201 may be accessiblely connected to another one or a plurality of servers (not shown) via the network 203. Then, at least one of the data dictionary 111 and the product information database 112 may be distributed and managed by another one or a plurality of servers including the server 201.

The information terminal device 202 is a device capable of accessing the data dictionary 111 and the product information database 112. Specifically, for example, an electronic device having a communication function such as a personal computer, a tablet terminal, or a smartphone. The function can be realized by.

(Example of hardware configuration of information processing device)
FIG. 3 is a block diagram showing an example of a hardware configuration of an information processing device (server, information terminal device) constituting the data management system according to the embodiment. In FIG. 3, the information processing apparatus (server 201, information terminal apparatus 202) includes a CPU (Central Processing Unit) 301, a memory 302, an I / F (Interface) 303, a recording medium I / F 304, and a recording medium 305. And have. Further, each of the constituent units 301 to 304 is connected by a bus 300.

Here, the CPU 301 controls the entire information processing device (server 201, information terminal device 202). The memory 302 includes, for example, a ROM (Read Only Memory), a RAM (Random Access Memory), a flash ROM, and the like. Specifically, for example, a flash ROM or ROM stores various programs, and RAM is used as a work area of CPU 301. The program stored in the memory 302 is loaded into the CPU 301 to cause the CPU 301 to execute the coded process.

The I / F 303 is connected to the network 203 through a communication line, and is connected to another information processing device via the network 203. Then, the I / F 303 controls the interface between the network and the inside of the own device, and controls the input / output of data from another information processing device. For the I / F 303, for example, a modem, a LAN adapter, or the like can be adopted.

The disk drive, which is an example of the recording medium I / F 304, controls the read / write of data to the disk, which is an example of the recording medium 305, according to the control of the CPU 301. A disk, which is an example of the recording medium 305, stores data written under the control of the recording medium I / F 304. Examples of the recording medium 305 include magnetic disks and optical disks.

The information processing device (server 201, information terminal device 202) includes, for example, an SSD (Solid State Drive), an HDD (Hard Disk Drive), a display, and an input device, although not shown, in addition to the above-described components. And so on.

The display displays data such as documents, images, and functional information, as well as cursors, icons, and toolboxes. As the display, for example, a liquid crystal display, an organic EL (Electroluminescence) display, or the like can be adopted.

The input device has keys for inputting characters, numbers, various instructions, etc., and inputs data. The input device may be a keyboard, a mouse, or the like, or may be a touch panel type input pad, a numeric keypad, or the like.

(Functional configuration of data management system)
FIG. 4 is a block diagram showing an example of the functional configuration of the data management system according to the embodiment. In FIG. 4, the data management system 200 includes a data dictionary 111, a product information database 112, a metadata registration unit 401, a product information database creation unit 402, and a data access control unit 403. ..

Here, the data dictionary 111 converts the product information data schema 110 into a table of a relational database and stores it, as shown in FIG. 5 described later. Further, the product information database 112 stores the product information substance data 410 as shown in FIG. 6 described later. The data dictionary 111 and the product information database 112 are realized by, for example, storage areas such as the memory 302 and the recording medium 305 shown in FIG.

Further, the metadata registration unit 401, the product information database creation unit 402, and the data access control unit 403 are functions that serve as control units in the data management system 200. Specifically, the metadata registration unit 401, the product information database creation unit 402, and the data access control unit 403 store programs stored in storage areas such as the memory 302 and the recording medium 305 shown in FIG. The function is realized by causing the CPU 301 to execute the data or by using the I / F 303. The processing result of each functional unit is stored in a storage area such as the memory 302 or the recording medium 305 shown in FIG. 3, for example.

The metadata registration unit 401 extracts metadata from the product information data schema 110 and registers it in the data dictionary 111. That is, the metadata registration unit 401 generates metadata of the information from the data schema 110 of the information created based on the object-oriented data model, and registers the metadata in the data dictionary 111.

More specifically, the metadata registration unit 401 generates a schema ID for each product information data schema 110, and registers the metadata extracted from the product information data schema 100 in the data dictionary 111 using the schema ID as a key. ..

The product information database creation unit 402 creates a product information database from the metadata registered in the data dictionary 111. That is, the product information database creation unit 402 creates the product information database 112 from the product information data schema 110 of the object-oriented data model description with reference to the metadata registered in the data dictionary 111.

The data access control unit 403 stores or extracts the product information substance data 410 from the product information database 112. At that time, the data access control unit 403 accesses the actual data on the product information database 112 using the schema ID and the instance ID of the actual data as keys.

(Structure of data dictionary 111)
Next, the configuration of the data dictionary 111 will be described. FIG. 5 is an explanatory diagram showing an example of the configuration of the data dictionary. In FIG. 5, the data dictionary 111 is configured as a relational database including three tables, a product information database definition table 501, a class definition table 502, and an attribute definition table 503.

The product information database definition table 501 is a table that manages the "data schema name" and the "product information database name" with the "schema ID" as the primary key (Primary Key (PK)). Thereby, the product information database definition table 501 can manage the correspondence between the "schema ID" and the product information database 112. The product information database definition table 501 is used to identify the product information database 112 on the relevant database system corresponding to the product information data schema.

The class definition table 502 uses the "schema ID" and "product information class name" as the primary key (PK), the "inheritance source class name", the class table name of the instance storage destination ("instance storage destination table name"), and It is a table that manages "dependent table name". Thereby, the class definition table 502 can manage the correspondence between the "schema ID" and the information regarding the class of the product information. The class definition table 502 is referred to when the product information database 112 is created and when the product information entity data 410 is accessed.

The attribute definition table 503 uses the "schema ID" and "product information class name" as the primary key (PK), and stores the "attribute name", the "data type" and "data dimension number" of the attribute, and the storage. It is a table that manages the corresponding "column name" of the primary class table. As a result, the attribute definition table 503 can manage the correspondence between the "schema ID" and the information related to the attributes of the product information class. The attribute definition table 503 is referred to and used for creating the product information database 112 and accessing the product entity data 410, similarly to the class definition table 502.

With such a configuration, the data dictionary 111 can store and manage the product information data schema 110 described in the object-oriented data model as a relational database.

(Configuration of product information database 112)
Next, the configuration of the product information database 112 will be described. FIG. 6 is an explanatory diagram showing an example of the configuration of the product information database. In FIG. 6, the product information database 112 includes an instance table 601, a class table (inheritance source class table 602, inheritance destination class table 603), and a dependent table (inheritance source class table 602 dependent table 604, inheritance destination class table 603). It is configured as a relational database consisting of three types of tables in the dependent table 605).

The instance table 601 uses the "instance ID" of the object as the primary key from the product information class, and sets the "storage table name" of the storage table in which the actual data of the product information corresponding to the "instance ID" is stored. It is a table to manage. Specifically, for example, the inheritance source class table 602 and the inheritance destination class table 603, which are class tables, are managed. As a result, the instance table 601 manages the correspondence between the instance ID and the storage table in which the product information entity data 410 corresponding to the "instance ID" is stored.

Further, the inheritance source class table 602 and the inheritance destination class table 603, which are class tables, have the "instance ID" as the primary key, the "storage table name", and the attribute name of the product information entity data 410 corresponding to the instance ID. It is a table that manages the "attribute column name" corresponding to. Here, if there is an inheritance source class, it is managed including the "attribute column name" of the inheritance source class. As a result, the class table manages the correspondence between the "instance ID" and the attribute column of the product information entity data 410 corresponding to the "instance ID".

The dependent tables 604 and 605 store the attribute information when the attribute data type of the product information class is not a primitive type. The dependent tables 604 and 605 are tables that manage the "instance ID" and the "table name" with each of the "parent instance ID", "attribute name", and "index" as the primary key. That is, the dependent tables 604 and 605 are dependent tables for the storage table (inheritance source class table 602, inheritance destination class table 603).

(Processing in the metadata registration unit 401)
Next, the contents of the processing in the metadata registration unit 401 will be described with reference to FIGS. 7 to 10. FIG. 7 is a flowchart showing an example of the procedure for registering metadata in the data dictionary.

In the flowchart of FIG. 7, the metadata registration unit 401 shown in FIG. 4 first automatically assigns a unique schema ID based on the designated product information data schema 110 and the product information database name 710 (step S701). ). Then, each DML (Data Manipulation Language) for registering the metadata in the data dictionary 111 is generated using this schema ID as the main key, and the metadata is registered in the data dictionary 111 by the DML.

More specifically, a data registration DML in the product information database definition table (TBL) 501 is generated (step S702), and the generated data registration DML is used to register the data in the product information database definition table 501. (See FIG. 8 described later).

Further, a data registration DML in the class definition table (TBL) 502 is generated (step S703), and the generated data registration DML is used to register the data in the class definition table 502 (see FIG. 9 described later). ..

Similarly, a data registration DML in the attribute definition table (TBL) 503 is generated (step S704), and the generated data registration DML is used to register data in the attribute definition table 503 (see FIG. 10 described later). ).

FIG. 8 is a flowchart showing an example of a procedure for registering data in the product information database definition table. The flowchart of FIG. 8 corresponds to steps S701 and S702 of the flowchart shown in FIG. 7. In the flowchart of FIG. 8, the schema ID is automatically numbered, and the data schema name (file name, file path) of the input product information data schema 110 and the product information using the automatically numbered schema ID as a key. A DML having the database name 710 as a column is generated (step S801). The following is an example of DML generated in step S801.

INSERT INTO dictionary (schema_id, db_name, schema_name)
VALUES ('1','BMateness_ifc4','IFC4_BM');

Then, according to this DML output, data is registered in the product information database definition table 501 of the data dictionary 111.

FIG. 9 is a flowchart showing an example of the procedure for registering data in the class definition table. The flowchart of FIG. 9 corresponds to step S703 of the flowchart shown in FIG. In the flowchart of FIG. 9, first, the product information class name and the inheritance source class name thereof are extracted from the product information data schema 110 (step S901).

Next, based on the product information class name extracted in step S901, the storage destination table name is generated according to a given rule (step S902). Further, a DML having a schema ID (PK), a product information class name, an inheritance source class name, a corresponding storage destination table name, and a dependent table name as columns is generated (step S903). The following is an example of DML generated in step S903.

INSERT INTO entity_definitions (schema_id, entity_name, table_name, ind_table_name)
VALUES ((SELECT schema_id FROM dictionary WHERE db_name ='BMAincentence_ifc4'),'ifcvirtual dictionary','en_ifcvirdiction_entirquitirdict'

Then, according to this DML output, data is registered in the class definition table 502 of the data dictionary 111.

FIG. 10 is a flowchart showing an example of a procedure for registering data in the attribute definition table. The flowchart of FIG. 10 corresponds to step S704 of the flowchart shown in FIG. In the flowchart of FIG. 10, first, from the product information data schema 110, the product information class name of the product information class, the attribute name in the product information class, the data type in the product information class, and the aggregate data type in the product information class. The number of dimensions of is extracted (step S1001).

Next, the attribute column name is generated according to a given rule based on the attribute name in the product information class extracted in step S1001 (step S1002). Further, a DML having a schema ID (PK), a product information class name (PK), an attribute name, a data type, a set data type flag, and a corresponding attribute column name as columns is generated (step S1003). The following is an example of DML generated in step S1003.

INSERT INTO entity_attributes (schema_id, entity_name, attribute_name, data_type, collection_dimension_number, volume_name)
VALUES ((SELECT schema_id FROM dictionary WHERE db_name ='BMAincentence_ifc4'),'ifcvirtual dictionary','offsetdistance','offsetdistations','idents','ifc

Then, according to this DML output, data is registered in the attribute definition table 503 of the data dictionary 111. In this way, the metadata registration unit 401 can register the metadata in the data dictionary 111.

(Processing in product information database creation unit 402)
Next, the contents of the processing in the product information database creation unit 402 will be described with reference to FIGS. 11 and 12.

FIG. 11 is a flowchart showing an example of a product information database creation procedure (instance table generation). In the flowchart of FIG. 11, the product information database creation unit 402 generates an instance table 601 having a class table name (storage table name) as a column, with the instance ID as the primary key (step S1101). As a result, the instance table 601 in the product information database 112 can be generated.

Further, FIG. 12 is a flowchart showing an example of a procedure for creating a product information database (generation of a class table). In the flowchart of FIG. 12, "1" is set to "N" (N = 1) (step S1201).

Next, it is determined whether or not there is the Nth class definition information (step S1202). Here, when there is the Nth class definition information (step S1202: Yes), the Nth class definition information is acquired from the data dictionary 111 (step S1203). Then, it is determined whether or not the acquired Nth class definition information is in the processed list (step S1204). Here, if it is in the processed list (step S1204: Yes), it is not necessary to process the Nth class definition information, so the process proceeds to step S1207 without doing anything.

On the other hand, if the acquired class definition information is not in the processed list in step S1204 (step S1204: No), then the inheritance source class does not exist or the class table generation process of the inheritance source class has been completed. Whether or not it is determined (step S1205). Here, if there is no inheritance source class, or if there is an inheritance source class but the generation process of the class table of the inheritance source class has been completed (step S1205: Yes), the Nth class definition information is obtained. Generate a class table and put it in the processed list (step S1206). After that, the process proceeds to step S1207.

On the other hand, in step S1205, when there is an inheritance source class and the generation process of the class table of the inheritance source class is not processed (step S1205: No), the process proceeds to step S1207 without doing anything. .. In this way, if there is an inheritance source class, priority is given to the generation process of the class table of the inheritance source class.

In step S1207, "N + 1" is set to "N" (N = N + 1) (step S1207), and the process returns to step S1202. In this way, each process of steps S1202 to S1207 is repeatedly executed. Then, in step S1202, when there is no Nth class definition information, that is, when the class table generation process for all the class definition information is completed (step S1202: No), a series of processes is terminated.

In this way, the product information database creation unit 402 can create the product information database 112 from the product information data schema 110 of the object-oriented data model description by referring to the metadata registered in the data dictionary 111. ..

(Processing in data access control unit 403)
Next, the processing in the data access control unit 403 will be described. The process in the data access control unit 403 includes two processes, a data registration process and a data acquisition process. FIG. 13 is a flowchart showing an example of a data access control procedure (data registration) to the product information database.

In the flowchart of FIG. 13, the data access control unit 403 refers to the data dictionary 111 and uses the “schema ID” and the “product information class name” given by the user as keys to obtain the “product information database name” and the “product information database name”. Acquire the "dependent table name", "attribute name", "data type", "number of data dimensions" and "column name" (step S1301).

Next, a record having the "instance ID" of the physical data object and the acquired "class table name (storage table name)" as elements is inserted into the instance table 601 (step S1302). Further, a record having each attribute value of the object of the actual data as an element is inserted into the class table of the acquired class table name (inheritance source class table 602 or inheritance destination class table 603) (step S1303).

Here, it is determined whether or not the data type of the attribute is a primitive type (step S1304). Here, when the data type of the attribute is not a primitive type (step S1304: No), the "parent instance ID", "attribute name", "instance ID", and "instance ID" are displayed in the dependent table (dependent table 604 or dependent table 605). , Inserts a record whose element is the "table name" (step S1305), and ends a series of processes. On the other hand, when the data type of the attribute is a primitive type (step S1304: Yes), a series of processes is terminated without doing anything.

In this way, the data access control unit 403 can perform data registration processing on the product information database 112.

FIG. 14 is a flowchart showing an example of a data access control procedure (data acquisition) for the product information database. In the flowchart of FIG. 14, the data access control unit 403 refers to the data dictionary 111 and acquires the “product information database name” using the “schema ID” and the “product information class name” as keys (step S1401).

In addition, referring to the instance table 601 of the product information database 112, the "class table name (storage table name)" is acquired by using the "instance ID" of the object as a key (step S1402).

Next, referring to the class table (inheritance source class table 602 or inheritance destination class table 603) of the "class table name (storage table name)" acquired in step S1402, each using the "instance ID" of the object as a key. The attribute value is acquired and assigned to the attribute of the object (step S1403).

Further, with reference to the dependent table (dependent table 604 or dependent table 605) of the "class table name" acquired in step S1402, the "instance ID" of each attribute is acquired using the "parent instance ID" as a key. Assign to the attribute of the object (step S1404).

After that, the object is returned (step S1405), and a series of processes is completed. In this way, the data access control unit 403 can perform data acquisition processing on the product information database 112.

As described above, according to the present embodiment, the metadata of the product information is generated from the product information data schema 110 created based on the object-oriented data model, and the metadata is registered in the data dictionary 111. , A database related to product information (product information database 112) is created from the product information data schema 110 with reference to the metadata registered in the data dictionary 111, so that the actual data having different product information data schema 110 is unified. Can be managed.

Further, according to the present embodiment, a schema ID is generated for each product information data schema 110, and metadata is registered in the data dictionary 111 using the schema ID as a key. Thereby, the product information database 112 can be efficiently and surely created from the product information data schema 110 by using the schema ID of the data dictionary 111.

Further, according to the present embodiment, when the product information substance data 410 is stored or extracted from the product information database 112, the product information is used by using the schema ID and the instance ID of the product information substance data as keys. Access the physical data on the database 112. Thereby, the schema ID of the data dictionary 111 can be used to efficiently and surely access the actual data.

Further, according to the present embodiment, the data dictionary 111 has a product information database definition table 501 that manages the correspondence between the schema ID and the product information database 112. Further, the data dictionary 111 has a class definition table 502 that manages the correspondence between the schema ID and the information regarding the class of product information. Further, the data dictionary 111 has an attribute definition table 503 that manages the correspondence between the schema ID and the information related to the attributes of the product information class. As a result, the metadata of the product information can be easily registered in the data dictionary 111 for reference.

Further, according to the present embodiment, the product information database 112 manages the correspondence between the instance ID and the storage table in which the product information entity data 410 corresponding to the instance ID is stored. Have. Further, the product information database 112 has an inheritance source class table 602 and an inheritance destination class table 603 that manage the correspondence between the instance ID and the attribute column of the product information entity data 410 corresponding to the instance ID. As a result, it is possible to easily access the actual data on the product information database 112.

Further, according to the present embodiment, the product information database 112 has dependent tables 604 and 605 for the storage table (inheritance source class table 602, inheritance destination class table 603). This makes it possible to handle cases where the data type of the attribute is not a primitive type.

In this way, even the product information data schema 110 of the information created based on the object-oriented data model can flexibly respond to additions and changes of the product information model itself, and is created based on the object-oriented data model. It is possible to unify and manage the actual data.

In the present embodiment, the information created based on the object-oriented data model has been described as product information, but the information is not limited thereto. That is, the information may be created based on an object-oriented data model other than the product information.

Further, the data management method described in the present embodiment can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. The data management program can be read by a computer such as a hard disk, a flexible disk, a CD (Compact Disk) -ROM, an MO (Magnet-Optical Disk), a DVD (Digital Versaille Disk), a flash memory, and a USB (Universal Social Bus) memory. It is executed by being recorded on a recording medium and read from the recording medium by a computer. Further, the data management program may be distributed via a network such as the Internet.

The following additional notes are further disclosed with respect to the above-described embodiment.

(Appendix 1) Generate metadata for the information from the data schema of the information created based on the object-oriented data model.
Register the metadata in the data dictionary and
A database relating to the information is created from the data schema with reference to the metadata registered in the data dictionary.
A data management program characterized by having a computer perform processing.

(Appendix 2) Generate a schema ID for each data schema.
The metadata is registered in the data dictionary using the schema ID as a key.
The data management program according to Appendix 1, wherein the processing is executed by a computer.

(Appendix 3) When saving or extracting the actual data of the information from the database.
Using the schema ID and the instance ID of the entity data as keys, the entity data on the database is accessed.
The data management program according to Appendix 2, wherein the processing is executed by a computer.

(Supplementary Note 4) The data management program according to Supplementary note 2 or 3, wherein the data dictionary has a database definition table that manages a correspondence relationship between the schema ID and the database.

(Supplementary Note 5) The data management program according to Supplementary note 4, wherein the data dictionary has a class definition table that manages a correspondence relationship between the schema ID and information related to the class of the information.

(Supplementary Note 6) The data management program according to Supplementary Note 5, wherein the data dictionary has an attribute definition table that manages a correspondence relationship between the schema ID and information related to attributes of the information class.

(Supplementary Note 7) Addendum 3 is characterized in that the database has an instance table that manages a correspondence relationship between the instance ID and a storage table in which the entity data corresponding to the instance ID is stored. Described data management program.

(Appendix 8) The data management program according to Appendix 7, wherein the database has a class table that manages a correspondence relationship between the instance ID and the attribute column of the entity data corresponding to the instance ID. ..

(Supplementary note 9) The data management program according to Supplementary note 8, wherein the database has a dependent table to the storage table.

(Supplementary Note 10) The data management program according to any one of Supplementary notes 1 to 9, wherein the information is product information related to a product.

(Appendix 11) Generate metadata of the information from the data schema of the information created based on the object-oriented data model.
Register the metadata in the data dictionary and
A database relating to the information is created from the data schema with reference to the metadata registered in the data dictionary.
A data management method characterized by a computer performing processing.

(Appendix 12) Generate metadata of the information from the data schema of the information created based on the object-oriented data model.
Register the metadata in the data dictionary and
A database relating to the information is created from the data schema with reference to the metadata registered in the data dictionary.
A data management system characterized by having a control unit.

110 Product information data schema 111 Data dictionary 112 Product information database 200 Data management system 201 Server 202 Information terminal device 203 Network 401 Metadata registration unit 402 Product information database creation unit 403 Data access control unit 410 Product information real data 501 Product information database definition Table 502 Class definition table 503 Attribute definition table 601 Instance table 602 Inheritance source class table 603 Inheritance destination class table 604, 605 Dependent table 710 Product information database name

Claims (11)

Generate metadata for the information from the data schema of the information created based on the object-oriented data model.
Register the metadata in the data dictionary and
A database relating to the information is created from the data schema with reference to the metadata registered in the data dictionary.
A data management program characterized by having a computer perform processing. Generate a schema ID for each data schema
The metadata is registered in the data dictionary using the schema ID as a key.
The data management program according to claim 1, wherein the processing is executed by a computer. When storing or extracting the actual data of the information from the database
Using the schema ID and the instance ID of the entity data as keys, the entity data on the database is accessed.
The data management program according to claim 2, wherein the processing is executed by a computer. The data management program according to claim 2 or 3, wherein the data dictionary has a database definition table that manages a correspondence relationship between the schema ID and the database. The data management program according to claim 4, wherein the data dictionary has a class definition table that manages a correspondence relationship between the schema ID and information about a class of the information. The data management program according to claim 5, wherein the data dictionary has an attribute definition table that manages a correspondence relationship between the schema ID and information related to the attributes of the information class. The data according to claim 3, wherein the database has an instance table that manages a correspondence relationship between the instance ID and a storage table in which the entity data corresponding to the instance ID is stored. Management program. The data management program according to claim 7, wherein the database has a class table that manages a correspondence relationship between the instance ID and the attribute column of the entity data corresponding to the instance ID. The data management program according to claim 8, wherein the database has a dependent table on the storage table. Generate metadata for the information from the data schema of the information created based on the object-oriented data model.
Register the metadata in the data dictionary and
A database relating to the information is created from the data schema with reference to the metadata registered in the data dictionary.
A data management method characterized by a computer performing processing. Generate metadata for the information from the data schema of the information created based on the object-oriented data model.
Register the metadata in the data dictionary and
A database relating to the information is created from the data schema with reference to the metadata registered in the data dictionary.
A data management system characterized by having a control unit.

Images