JP2000010839A - Method and device for data registering process and storage medium having stored data registering process program thereon - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make it possible to extract a necessary data group by tracing data and reference information by registering data themselves and a group wherein the data are registered together in one group, defining the dependency relation between data as a dependence source and a dependence destination, and recording two pieces of reference information using a data name and a version. SOLUTION: A relative name saving part 12 retrieves a passed pair of a version ID and an ID and a relative name wherein a version ID (reference source) and an ID (reference source) or a version ID (reference destination) and an ID (reference destination) match with each other. The retrieval result is saved in an extracted relative name saving part 16. The relative name saving part 12 compares pairs of version IDs and IDs of a software component name and a property name and adds nonexistent ones to an extracted software component name saving part 14 and an extracted property name saving part 15. An extraction management part 13 takes out relative names saved in the extracted relative name saving part 16, one by one, from the head and two pairs of version IDs and IDs (reference source and reference destination) and registers them in an extracted discrimination saving part 17.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a data registration processing method and apparatus, and a storage medium storing a data registration processing program.
The present invention relates to a data registration processing method and apparatus for reducing operation of data registration and eliminating inconsistency between data, and a storage medium storing a data registration processing program.

[0002]

2. Description of the Related Art In a conventional data storage system (hereinafter, referred to as a data storage system), there is a technology for extracting and managing a difference by comparing the previously registered data at the time of data registration (eg, UNIX). SCCS). In this technique, when managing the relation between data, the operator performs the operation by following the relation between the data and integrating them without contradiction. For example, UN
In the case of IX, the relationship between individual files is managed by an operator who adds information (version) added when registering to the SCCS so that the relationship can be understood, and acquires necessary information based on the version. .

When data is related to other data, the related data is copied and managed when the data is registered. On the other hand, when registering data,
When only individual data is registered and all the data are registered, the relation of the data can be registered separately.

[0004]

However, in the above-mentioned conventional technique, when data is related to other data, the method of copying and managing the related data at the time of registering the data involves the related technique. It is efficient to verify inconsistencies between data because data is copied, but when related data itself changes, all copy destination data must be updated at the same time and reconfirmed for inconsistency. No. In addition, when registering data, only the individual data is registered, and at the stage where all the data has been registered, the method of registering the data relation separately requires checking whether the registered data is inconsistent or not. There is a problem that it cannot be determined until after registration.

[0005] The present invention has been made in view of the above points, and when registering data, instead of copying the related data at the time of registering the data, it is necessary to have only reference information of the related data. In addition, at the time of data update, it is possible to register as another data referring to the original data, and at the time of extracting data, it is possible to extract a necessary data group by following the data and reference information It is an object to provide a storage medium storing a registration processing method and apparatus and a data registration processing program.

[0006]

FIG. 1 is a diagram for explaining the principle of the present invention. According to the present invention (claim 1), in a data registration processing method for registering data, data itself and a group (version) in which the data are registered are recorded as a set (step 1), and a dependency (reference relationship) between the data is recorded. Two sets of reference information using a data name and a version are recorded as a dependence source (reference source) and a dependence destination (reference destination) (step 2).

According to a second aspect of the present invention, in a data registration processing method for registering data, data itself and a group (version) in which the data is registered are recorded as a set, and a dependency (reference relationship) between the data is dependent. Source (reference source) and dependent (reference destination)
, Two sets of reference information using a data name and a version are recorded, and data is extracted while following the reference information.

FIG. 2 is a diagram showing the principle of the present invention. The present invention (Claim 3) is a data registration processing device for registering data, comprising: a recording unit 100 for recording data itself and a group (version) in which the data is registered as a group; ) As a dependency source (reference source) and a dependency destination (reference destination), a reference information recording unit 200 that records two sets of reference information using a data name and a version.

According to a fourth aspect of the present invention, there is provided a data registration processing apparatus for registering data, comprising: a recording unit for recording data itself and a group (version) in which the data is registered in a set; Reference information recording means for recording two sets of reference information using a data name and a version with the reference relationship as a dependent source (reference source) and a dependent destination (reference destination), and data for extracting data while following the reference information Extraction means.

[0010] The present invention (claim 5) is a data registration device for registering data, wherein reference identification information recorded in ascending order of a version ID for identifying the same data having a plurality of contents at the time of data registration. And data having a version ID for identifying version information at the time of registration and an ID for distinguishing from other data, and related data having a version ID and ID for identifying a relationship between data as a set And registration means for simultaneously registering, when registering the data, if the data is related to the related data, a version ID of the related data and related data having the ID.

According to the present invention (claim 6), when the data is changed, the registration means has a version ID included in the updated reference identification information and registers the data as another data having the ID of the data. It includes a change registering means and a related data registering means for simultaneously registering related data having data before the change.

The present invention (claim 7) further comprises a data extracting means for designating a version ID or a version name when extracting data and extracting data having the same version ID based on the reference identification information. Have. The present invention (claim 8) includes, in the data extracting means, means for also extracting data having a version ID designated by data capable of tracing the reference identification information.

According to a ninth aspect of the present invention, there is provided a storage medium storing a data registration processing program for registering data, comprising: a recording process for recording data itself and a group (version) in which the data is registered; Dependencies (reference relationships) between the source (reference source) and the destination (reference destination),
A reference information recording process for recording two sets of reference information using a data name and a version.

According to a tenth aspect of the present invention, there is provided a storage medium storing a data registration processing program for registering data, comprising: a recording process for recording a set of data itself and a group (version) in which the data is registered; Dependencies (reference relationships) between the source (reference source) and the destination (reference destination),
It has a reference information recording process of recording two sets of reference information using a data name and a version, and a data extraction process of extracting data while following the reference information.

As described above, in the data registration system, the present invention has a table T for identifying so that the same data can have a plurality of contents at the time of data registration. Version ID, which is an identifier for distinguishing from
In the ascending order, and each data D-Ai has a version ID for identifying the version information Ti at the time of registration. It also has an ID for identifying it from others. Next, it has data DR indicating the relation between the data D. The data DR have a pair of version IDs and IDs for identifying the reference source and the reference destination. When the data DA1 is related to the data DA2, when the data DA1 is registered, the version ID and the data DR1 having the ID of the associated data DA2 are registered at the same time. When the data D-A1 has been changed, the new table T2 has the version ID,
Is registered as the data D-A3 having the data ID D. The data D-R2 having the data D-A1 is simultaneously registered as the related data.

When extracting data, if a version ID or a version name is designated, data having the same version ID is extracted based on the table Ti. At that time, necessary latest data can be extracted without contradiction by extracting data having a version ID designated by data traceable by the reference information. In the present invention, the same data is first selected from the data DA based on the version information of the table T to be extracted. Next, to extract the data referred to by the selected data, the data D-
Select the data in which the selected data is the reference source (reference side) in R. The data DA is searched from the reference destination (referenced side) information of the selected data D-Ri, and is added after the data DA extracted so far. By repeating this process, there is no more information to add,
In addition, the data extracted once traces only reference information and is not added to the extracted data itself, thereby realizing a function of extracting data without contradiction. When registering data, reference information D-Ri representing that the data D-Ai to be registered has the data D-Aj referred to is registered. When the referred data D-Ai is changed, the data D-Ak is newly registered, and the data D-Rk, which is a reference from the original data D-Ai, is created.

This makes it possible to extract the entire part including the relevant data in the version specified by the operator.

[0018]

DESCRIPTION OF THE PREFERRED EMBODIMENTS First, the outline of the operation of the present invention will be described. FIG. 3 is a diagram for explaining the outline of the operation of the present invention. The data shown in FIG. 3 includes data 101 to be registered / changed, data 102 having a relationship between the data, and information 103.

In the data registration processing device of the present invention,
The information 103 is a table for identifying the same data so as to have a plurality of contents when registering the data. Table 1
03-i contains version I, which is an identifier for distinguishing it from others.
D in ascending order, and each data 101-i has a version ID for identifying the version information 103-i at the time of registration. It also has an ID for identifying it from others. Next, data 1
The data 102 indicating the relationship between 01 and 01 has a pair of version IDs and IDs for identifying the reference source and the reference destination. When the data 101-1 is related to the data 101-2, when registering the data 101-1, the data 102-1 having the version ID and ID of the related data 101-2 is registered.
1 are registered at the same time. When the data 101-1 is changed, it is registered as the data 101-3 having the version ID held by the new table 103-2 and having the ID of the data 101-1. 1
Is registered at the same time.

When extracting data, when a version ID or a version name is specified, data having the same version ID is extracted based on Table 103-i. At that time, the reference information 103
By extracting the data having the version ID specified by the data traceable by the above, necessary latest data can be extracted without contradiction. Next, a series of operations will be described.

Based on the version information 103 to be extracted, the same version is first selected from the data 101. Next, in order to extract the data referred to by the selected data, the data 102 in which the selected data is the reference source (the side performing the reference) is selected.

The data 101 is searched from the reference destination (referenced side) information of the selected data 102-i and added after the data 101 extracted so far. By repeating this process, there is no information to be added, and once extracted data traces only reference information and is not added to the extracted data itself, thereby realizing a function of extracting data without contradiction. When registering data, reference information 102-i expressing that the data 101-i to be registered has the data 101-j to which it refers is registered.
When the data 101-i referred to is changed, the data 101-k is newly registered, and data 102-k which is a reference from the original data 101-i is created.

[0023]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 4 shows the data registration process of the present invention. Less than,
With reference to the figure, description will be made using an example in which data (software component names and attribute names constituting the software components) are registered in the data storage system.

By following the steps shown in the figure, the data registration device realizes an extraction function for extracting the entire part including the relevant data in the version specified by the operator. In the figure, solid arrows indicate the order of steps, and dotted arrows indicate return of steps. The following processing is performed in each step shown in FIG. “Step 1” version registration: A new ID is paid out and version information is registered.

[Step 2] Software part name registration: A new software part name is added. Alternatively, the name of the existing software component is changed. “Step 3” Attribute name registration: A new attribute name is added.
Alternatively, the existing attribute name is changed. “Step 4” Related name registration: A new related name is added.
Alternatively, the existing related name is changed.

[Step 5] Data extraction: Registered data is extracted. This step can be performed independently of steps 1 to 4. FIG. 5 shows the configuration of the data registration device according to one embodiment of the present invention. The data registration device shown in FIG. 1 includes a terminal device 1 operated by an operator who registers a version relationship of data registration, a terminal device 2 operated by an operator performing data registration, and a terminal operated by an operator performing related name registration. Device 3, terminal device 4 operated by an operator who performs data extraction, version management unit 5 for managing versions of data registration, version storage unit 6 for storing version relationships, software component name registration unit for registering software component names 7, a software component name storage unit 8 for storing software component names, an attribute name registration unit 9 for registering attribute names, an attribute name storage unit 10 for storing attribute names, and a relation for registering a reference relationship between names. A name registration unit 11, a related name storage unit 12 for storing reference relationships, an extraction management unit 13 for managing versions of data extraction, an extracted software component name storage unit 14 for storing extracted software component names, an extracted attribute An extraction attribute name storage unit 15 for storing names, an extraction related name storage unit 16 for storing extracted names and reference relationships between names, and an extraction identifier storage unit 17 for storing identifiers necessary for identifying extracted data. Consists of

The version management unit 5 stores information (version ID) on the version input from the terminal device 1 in the version storage unit 6. Further, a version ID specified by the operator of the terminal device 1 is added to the software component name and the attribute name input from the terminal device 2. The software component name registration unit 7 includes a software component name to which a version ID is assigned, an identifier (ID) for uniquely identifying the software component name and the attribute name, and a component type, which is a specification of the software component name. Is stored in the software component name registration unit 8 as a set of data.

The attribute name registration unit 9 stores an attribute name and an identifier (ID) to which a version ID has been given, and an attribute name storage unit 10 as a set of attribute data types and the number of digits, which are attribute specifications. To save. Related name registration part 1
In order to register the association between the software component name and the attribute name, 1 is a set of the ID and the version ID assigned to the software component name, and the ID and the version ID assigned to the attribute name as one set of data.
It is stored in the related name storage unit 12.

The extraction management unit 13 extracts software component names and attribute names that match the version ID input from the terminal device 4 from the component name storage unit 7 and the attribute name storage unit 9, respectively.
The extracted software component name storage unit 14 and the extracted attribute name storage unit 15 sequentially store the extracted software component name storage unit 14 and the extracted attribute name storage unit 15. Extraction software name storage unit 1
4 and the attribute name storage unit 10, the identifier (ID) and the version I
D is collected, and a search is made for a name that matches the name stored in the related name storage unit 12, and all dependent items are extracted from the extracted software component name storage unit 14 and the extracted attribute name storage unit. 15 and the search result itself is added to the extraction-related name storage unit 16. This process is repeated until the stored data is exhausted.

Next, the software component name and the attribute name are searched in order from the top from the extracted software component name storage unit 14 and the extracted attribute name storage unit 15, and the extracted version ID and ID are added to the extraction identifier storage unit 17. I will do it. At this time, duplicated IDs are not added, so that the same data is not duplicated. Finally, the version ID stored in the extraction identifier storage unit 17 and the data corresponding to the ID are extracted from the extraction software component name storage unit 14 and the extraction attribute name storage unit 15 and the extraction related name storage unit 16
The necessary data can be extracted without inconsistency by outputting the data registered in.

FIG. 6 is a diagram for explaining each component of an embodiment of the present invention. In FIG. 5, the version storage unit 6, the software component name storage unit 8, the attribute name storage unit 10, the related name storage unit 12, the extracted software component name storage unit 14, the extracted attribute name storage unit 15, and the extraction related name shown in FIG. It shows the data stored in the storage unit 16 and the extracted identifier storage unit 17 and the relationship between them. In this figure, the same parts as those in FIG.

Referring to FIG.
Is a software component name correspondence unit 2 that stores software component names
One. As shown in FIG. 7, the software component name correspondence unit 21 has one ID for each software component name, and indicates a description for one software component name with a version ID and an ID or any of the software component names. One software component name has a component type as its content.

The attribute name storage unit 10 has an attribute name target corresponding unit 22 for storing attribute names. As shown in FIG. 8, there is one ID for each attribute name, and the version ID and either the ID or the attribute name represent a description for one attribute name. One attribute name has an attribute data type and the number of digits as its contents. The related name storage unit 12
As shown in FIG. 9, there is a related name correspondence unit 23 for storing related names, and as shown in FIG. 9, two sets of version IDs and IDs (reference source and ID) are sufficient to identify one software component name and one attribute name. Are referred to data, and a reference destination is referred to data).

The version storage section 6 has a version correspondence section 24 for storing the correspondence between the version ID and the version name (nickname).
As shown in FIG. 10, the version correspondence unit 24 includes a version ID and a version name. The extracted software component name storage unit 14 has an extracted software component name correspondence unit 25 that stores the result extracted from the software component name storage unit 8 based on the version ID specified at the time of data extraction. Extracted software component name correspondence unit 25
Is composed of a version ID, an ID, a software component name, and a component type, as shown in FIGS. FIG. 11 shows an example of extraction when the version name is designated as “application”, and FIG. 12 shows an example of extraction when the version name is designated as “basic data definition 2”.

The extracted attribute name storage section 15 has an extracted attribute name corresponding section 26 for storing the result of extraction from the attribute name storage section 10 based on the version ID specified at the time of data extraction.
The extracted attribute name corresponding unit 26 is composed of a version ID, an ID, an attribute name, an attribute data type, and the number of digits, as shown in FIGS. FIG. 13 shows an example of extraction from the attribute name storage unit 10 when the version name is specified as “application”, and FIG. 14 shows an example of extraction when the version name is specified as “basic data definition 2”. is there.

The extraction-related name storage section 16 has an extraction-related name correspondence section 27 for storing a result extracted from the relation name storage section 12 at the time of data extraction. Extraction related name correspondence unit 27
Is, as shown in FIGS. 15 and 16, the version ID (reference source),
ID (reference source), version ID (reference destination), and ID (reference destination). FIG. 15 shows an example of extraction when the version name is designated as “application” in the extraction related name correspondence unit 27, and FIG. 16 shows the related name when the version name is designated as “basic data definition 2”. 6 is an example of extraction from the storage unit 12.

The extracted identifier storage unit 17 has an extracted identifier corresponding unit 28 that extracts a set of a version ID and an ID existing in the extracted software component name storage unit 14 and the extracted attribute name storage unit 15. As shown in FIGS. 17 and 18, the extraction identifier corresponding unit 28 includes a version ID, an ID, and whether or not display is possible.
FIG. 17 shows an example of extraction in the case where the version name is designated as “application” in the extraction identifier correspondence unit 28. Only one of the extraction identifiers having the same ID is output to the terminal device 4. You. Also, if the reference destination of the extracted identifier that has not been displayed has not appeared so far, the identifier and the identifier to which the identifier refers are not displayed, so that the version ID = 1 and the ID = 1 , Edition I
With D = 2, ID = 103 is not output. FIG. 18 is an example of extraction when the version name is specified as “basic data definition part 2”, and shows that all of the version ID = 1, ID = 1 and version ID = 3 are not output.

Hereinafter, the entire flow of the operation of the present embodiment will be described. (1) Step 1 (version registration) First, step 1 for paying out a new version ID and registering version information will be described. Step 1 is processed by the terminal device 1, the version management unit 5, and the version storage unit 6. FIG. 19 is a flowchart of the plate registration process according to one embodiment of the present invention.

Step 31) The version management section 5 receives the version name from the terminal device 1. Step 32) The version management section 5 attaches a version ID to the version name and passes it to the version storage section 6. Step 33) The version storage unit 6 stores the received version ID and version name in the version correspondence unit 25. Step 34) The version management unit 5 displays the pair of the version ID and the version name on the terminal device 1.

(2) Step 2 (Software Part Name Registration) Next, Step 2 for adding a new software part name or changing an existing software part name will be described. Step 2 is processed by the terminal device 2, the plate crab 5, the plate storage 6, the software component name registration unit 7, and the software component name storage 8. FIG. 20 is a flowchart of the software component name registration processing according to one embodiment of the present invention.

Step 41) The version management section 5 receives the version name from the terminal device 2. Step 42) The version management unit 5 passes the version name to the version storage unit 6. Step 43) The version storage unit 6 stores the version I corresponding to the version name.
D is searched, and the found version ID is passed to the version management unit 5. Step 44) The version management unit 5 receives the software component name and the component type from the terminal device 2 and passes them to the software component name registration unit 7 together with the version ID.

Step 45) Software part name registration unit 7
Searches the software component name storage unit 8 to see if it is already registered with the same name as the passed software component name. As a result of the search, if the ID has already been registered, the ID is registered in the software component name storage unit 8 as a set of the version ID, the ID, the software component name, and the component type using the new ID otherwise.

(3) Step 3 (Attribute Name Registration) Next, Step 3 for adding a new attribute name or changing an existing attribute name will be described. The process 3 includes a terminal device 2, a version management unit 5, a version storage unit 6, an attribute name registration unit 9
And the attribute name storage unit 10. FIG.
It is a flow chart of attribute name registration processing of one example of the present invention.

Step 51) The version management section 5 receives the version name from the terminal device 2. Step 52) The version management unit 5 passes the version name to the version storage unit 6. Step 53) The version storage unit 6 stores the version I corresponding to the version name.
D is searched, and the found version ID is passed to the version management unit 5. Step 54) The version management unit 5 receives the attribute name, the attribute data type, and the number of digits from the terminal device 2, and passes the attribute name, the version ID, and the attribute ID to the attribute name registration unit 9.

Step 55) The attribute name registering section 9 searches whether the attribute name has already been registered under the same name as the attribute name passed to the attribute name storing section 10. As a result of the search, if the ID is already registered, the ID is used. If not, the ID is stored in the attribute name storage unit 10 using the version ID, the ID, the attribute name, the attribute data type, and the number of digits. register. (4) Step 4 (Registering Related Name) Next, Step 4 for adding a new related name or changing an existing related name will be described. The step 4 includes the terminal device 3, the related name registration unit 11 and the related name storage unit 12
Is processed by

FIG. 22 is a flowchart of a related name registration process according to one embodiment of the present invention. Step 61) The related name registration unit 11 receives from the terminal device 3 two pairs of the version ID and the ID representing the reference source and the reference destination, and registers the pair in the related name storage unit 12. (5) Step 5 (Data Extraction Processing) Finally, Step 5 of extracting registered data will be described. This step 4 can be executed independently of the previous steps 1 and 4. The step 4 includes the terminal device 4, the version storage unit 6, the software component name storage unit 8, the attribute name storage unit 10, the related name storage unit 12, the extraction management unit 13, the extracted software component name storage unit 14, and the extraction attribute name storage. The processing is performed by the unit 15, the extraction-related name storage unit 16, and the extraction identifier storage unit 17.

FIG. 23 is a flowchart of the data extracting process according to one embodiment of the present invention. Step 71) The extraction management unit 13 receives the version name from the terminal device 4. Step 72) The extraction management unit 13 passes the version name to the version storage unit 6. Step 73) The version storage unit 6 stores the version I corresponding to the version name.
D is retrieved, and the found version ID is passed to the extraction management unit 13.

Step 74) The extraction management section 13 checks the version I
D is passed to the software component name storage unit 8. Step 75) The software component name storage unit 8 searches for a software component name that matches the passed version ID, and passes it to the extraction management unit 13. Step 76) The extraction management unit 13 passes the received software component name to the extracted software component name storage unit 14 and adds it.

Step 77) The extraction management unit 13 checks the version I
D is passed to the attribute name storage unit 10. Step 78) The attribute name storage unit 10 transmits the passed version I
An attribute name matching D is retrieved and passed to the extraction management unit 13. Step 79) The extraction management unit 13 passes the received attribute name to the extracted attribute name storage unit 15 and adds it.

Step 80) The extraction management unit 13 receives all the extracted software component names and the extracted attribute names registered from the extracted software component name storage unit 14 and the extracted attribute name storage unit 15, and sets a set of version ID and ID. Is passed to the related name storage unit 12. Step 81) The related name storage unit 12 stores the received version I
A related name in which the pair of D and ID, the version ID (reference source) and ID (reference source), or the version ID (reference destination) and ID (reference destination) match is searched. The search result is stored in the extraction-related name storage unit 16, and when the version ID (reference source) and the ID (reference source) match, the version ID (reference destination) and the ID (reference destination) are replaced with the version ID. (Reference) and ID (reference)
If the IDs match, the version ID (reference source) and the ID (reference source)
Is extracted and passed to the software component name storage unit 8 and the attribute name storage unit 10.

Step 82) Software part name storage section 8
The attribute name storage unit 10 searches for a software component name and an attribute name that match the passed version ID and ID pair, and passes them to the related name storage unit 12. Step 83) The related name storage unit 12 executes step 80
Is compared with the pair of the version ID and the ID passed in step 82 and the pair of the version ID and ID of the software component name and the attribute name passed in step 82, and those not present in step 80 are extracted. , To the extracted attribute name storage unit 15.

Step 84) While there is something to be added in step 83, the processing from step 80 is repeated. Step 85) The extraction management unit 13 extracts two pairs of version ID and ID (reference source / reference destination) from the top of the related names stored in the extracted related name storage unit 16 one by one, and Register to 17 Display permission / inhibition is determined by comparing the contents of the extracted identifier storage unit that has already been registered. If the same ID has already been registered regardless of the reference source / reference destination, the display is disabled. Next, in the case of the reference source, if there is an identifier that can be displayed by the ID of the reference destination, it is determined to be possible, and otherwise, it is determined to be impossible. In the case of the reference destination, the reference source and the display permission are matched (if the display is not possible, the display is disabled, and if possible, the display is possible). Since the same name of the version ID and the ID is registered a plurality of times, the related name is not added unless it is already registered in the extraction identifier storage unit 17. This process is performed for all of the items registered as the extraction identifier.

Step 86) The extraction management unit 13 extracts the software component name stored in the extracted software component name storage unit 14 from the top. Version ID and I of the retrieved item
The extracted identifier storage unit 17 is searched on the basis of the pair of D, and if it can be displayed according to whether or not it is possible to display a match, the terminal device 4
Of the software component name, the software component name and the component type are displayed. In the case where they do not match, the terminal device 4 displays the ID in the software component name, the software component name, and the component type. The above is performed for all the names registered in the extracted software component name storage unit 14.

Step 87) The extraction management unit 13 extracts the attribute name stored in the extracted attribute name storage unit 15 from the top. The extracted identifier storage unit 17 is searched based on the pair of the version ID and the ID of the extracted one, and according to whether or not the matched one can be displayed, if it can be displayed, the ID in the attribute name, the attribute name, and the attribute data Display type and number of digits. Also, even when they do not match, the terminal device 4 displays the ID in the attribute name, the attribute name, the attribute data type, and the number of digits. The above is performed for all the names registered in the extracted attribute name storage unit 15.

Step 88) The extraction management unit 13 extracts the related name stored in the extracted related name storage unit 16 from the top. The extracted identifier storing unit 17 is searched based on two pairs (reference source and reference destination) of the version ID and ID of the extracted one, and if both sets can be displayed depending on whether or not the matched one can be displayed, the ID (reference source) And the ID (reference destination) to the terminal device 4
To be displayed. After the display, the extracted software component name storage unit 1
4, extraction attribute name storage unit 15, and extraction related name storage unit 16
And all the contents stored in the extraction identifier storage unit 17 are deleted.

Although the above embodiment has been described based on the configuration of FIG. 5, the version management unit 5, software component name registration unit 7, attribute name registration unit 9, related name registration unit 11,
The operation of the extraction management unit 13 is constructed as a program, and a disk device connected to a computer used as the data registration device, a floppy disk or a CD-RO
The present invention can be easily realized by storing it in a portable storage medium such as M and installing it when implementing the present invention.

The present invention is not limited to the above embodiment, but can be variously modified and applied within the scope of the claims.

[0058]

As described above, according to the present invention, when registering data, the related data is not copied at the time of registering the data, but has only the reference information of the related data. . When updating the data, the original data is registered as another data that refers to the original data. When extracting data, by extracting the necessary data group by tracing the data and reference information, by specifying the version in the data registration, no inconsistency occurs between the data at the time of data extraction, and Related data can also be obtained.

[Brief description of the drawings]

FIG. 1 is a diagram for explaining the principle of the present invention.

FIG. 2 is a principle configuration diagram of the present invention.

FIG. 3 is a diagram for explaining an outline of an operation of the present invention.

FIG. 4 is a diagram showing a data registration process according to one embodiment of the present invention.

FIG. 5 is a configuration diagram of a data registration device according to an embodiment of the present invention.

FIG. 6 is a diagram for explaining each component of an embodiment of the present invention.

FIG. 7 is an example of data of a software component name corresponding unit according to an embodiment of the present invention.

FIG. 8 is an example of data of an attribute name corresponding unit according to an embodiment of the present invention.

FIG. 9 is an example of data of a related name corresponding unit according to one embodiment of the present invention.

FIG. 10 is an example of data of a plate correspondence unit according to an embodiment of the present invention.

FIG. 11 is an example (No. 1) of data of an extracted software component name corresponding portion according to an embodiment of the present invention.

FIG. 12 is a data example (part 2) of an extracted software component name corresponding unit according to an embodiment of the present invention.

FIG. 13 is an example (No. 1) of data of an extracted attribute name corresponding section according to an embodiment of the present invention.

FIG. 14 is an example (No. 2) of data of an extracted attribute name corresponding portion according to an embodiment of the present invention.

FIG. 15 is an example (No. 1) of data of an extraction-related name corresponding section according to an embodiment of the present invention.

FIG. 16 is an example (No. 2) of data of an extraction-related name corresponding portion according to an embodiment of the present invention.

FIG. 17 is an example (No. 1) of data of an extracted identifier corresponding unit according to an embodiment of the present invention.

FIG. 18 is an example (No. 2) of data of an extracted identifier corresponding unit according to an embodiment of the present invention.

FIG. 19 is a flowchart of a plate registration process according to an embodiment of the present invention.

FIG. 20 is a flowchart of a software component name registration process according to one embodiment of the present invention.

FIG. 21 is a flowchart of an attribute name registration process according to an embodiment of the present invention.

FIG. 22 is a flowchart of a related name registration process according to an embodiment of the present invention.

FIG. 23 is a flowchart (part 1) of a data extraction process according to an embodiment of the present invention.

FIG. 24 is a flowchart (No. 2) of a data extraction process according to an embodiment of the present invention.

FIG. 25 is a flowchart (part 3) of a data extraction process according to an embodiment of the present invention.

[Explanation of symbols]

 1, 2, 3, 4 Terminal device 5 Version management unit 6 Version storage unit 7 Software component name registration unit 8 Software component name storage unit 9 Attribute name registration unit 10 Attribute name storage unit 11 Related name registration unit 12 Related name storage unit 13 Extraction management unit 14 Extraction software component name storage unit 15 Extraction attribute name storage unit 16 Extraction related name storage unit 17 Extraction identifier storage unit 21 Software component name correspondence unit 22 Attribute name correspondence unit 23 Related name correspondence unit 24 Version correspondence unit 25 Extraction software Part name corresponding part 26 Extracted attribute name corresponding part 27 Extraction related name corresponding part 28 Extracted identifier corresponding part 100 Recording means 200 Reference information recording means

Claims (10)

[Claims] In a data registration processing method for registering data, data itself and a group (version) in which the data are registered are recorded as a set, and a dependency relationship (reference relationship) between data is dependent on a dependency source (reference source). A data registration processing method characterized by recording two sets of reference information using a data name and a version as a destination (reference destination). 2. A data registration processing method for registering data, wherein the data itself and a group (version) in which the data is registered are recorded as a set, and a dependency (reference relationship) between the data is dependent on a dependency source (reference source). A data registration processing method characterized by recording two sets of reference information using a data name and a version as a reference (reference destination), and extracting data while following the reference information. 3. A data registration processing device for registering data, comprising: recording means for recording a set of data itself and a group (version) in which the data is registered; and a dependency source (reference relationship) between the data. A data registration processing device comprising: reference information recording means for recording two sets of reference information using a data name and a version as a reference source) and a dependence destination (reference destination). 4. A data registration processing device for registering data, comprising: recording means for recording a set of data itself and a group (version) in which the data is registered; and a dependency source (reference relationship) between the data. A reference information recording unit that records two sets of reference information using a data name and a version as a reference source) and a dependence destination (reference destination); and a data extraction unit that extracts data while following the reference information. A data registration processing device characterized by the above-mentioned. 5. A data registration apparatus for registering data, comprising: reference identification information in which version IDs for identifying the same data having a plurality of contents at the time of data registration are recorded in ascending order; Data having a version ID for identifying the ID and an ID for identifying the other data, related data having a version ID and an ID for identifying a relationship between the data as a set, and registering the data. If the data is related to the related data, the version ID and the ID of the related data
A registration unit for simultaneously registering related data having the following. 6. The change registering means, when the data is changed, has the version ID of the updated reference identification information, and registers the version ID as another data having the ID of the data. The data registration processing device according to claim 5, further comprising: related data registration means for simultaneously registering related data having data before the change. 7. A data extracting means for extracting data having the same version ID based on the reference identification information by designating the version ID or the version name when extracting data. Data registration processor. 8. The data registration processing device according to claim 7, wherein said data extracting means includes means for also extracting data having a version ID designated by data capable of tracing said reference identification information. 9. A storage medium storing a data registration processing program for registering data, comprising: a recording process for recording the data itself and a group (version) in which the data is registered as a set; ) As a dependency source (reference source) and a dependency destination (reference destination), and stores a reference information recording process for recording two sets of reference information using a data name and a version. Storage media. 10. A storage medium storing a data registration processing program for registering data, comprising: a recording process for recording data itself and a group (version) in which the data is registered as a group; ) As a dependency source (reference source) and a dependency destination (reference destination), a reference information recording process for recording two sets of reference information using a data name and a version, and a data extraction for extracting data while following the reference information And a storage medium storing a data registration processing program having a process.