JPH0877051A - Common data management system - Google Patents

Abstract

PURPOSE: To access common data from plural scopes by controlling the order of referring to a scope table through a current scope table, and assigning the same scope when a data type is the same and registering the common data. CONSTITUTION: When common data is newly generated, a right processing program 6 refers to the scope table 2 in the order of scopes defined in the current scope table 3; when there is data of the same data type, its scope and discrimination information are added to and defined in a right table 14 and the newly generated data is added to and defined in a data table 5. When data is updated, the right table 4 and data table 5 are referred to on the basis of the discrimination information of the data to be updated to obtain the scope and data type of the data to be updated, and then the scope table 2 is referred to in the scope order defined in the current scope data table 3, so that when the same scope and the same type are defined, the update object data in the data table 5 is updated.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION The present invention is applicable to, for example, CASE (Co
mputer Aided Software Engen
The present invention relates to a shared data management system that is suitable for use in EEering.

[0002]

2. Description of the Related Art Conventionally, in CASE, there is a software life cycle model called a waterfall model. In this model, there is a tool for each process, and the shared data is used such that the data required for the current process is extracted and used from the shared data obtained in the previous process.

In many cases, in consideration of the shift from the outline development to the detailed development as the process is performed later,
We either did not allow the information obtained in the previous process to be changed in the subsequent process, or we made some efforts to allow it. Therefore, in order to extract the data necessary for the work of the current process from the shared data obtained in the previous process, duplicate the data of the predetermined part of the shared data obtained in the previous process and I used to work in the current process.

As a method of managing such shared data, as disclosed in Japanese Patent Laid-Open No. 4-359331, a relationship is established between a DD / D user and a DD / D view, and an access right ( (Reference, add, update, delete).

[0005]

However, if the data required for the current work is duplicated and used, the same data will be duplicated in the system, and it will be difficult to maintain the consistency. There's a problem.

Further, in the data management method disclosed in Japanese Patent Laid-Open No. 4-359331, when accessing shared data from a plurality of scopes (fields of view), it is not possible to control access for each scope. is there.

An object of the present invention is to provide a shared data management system which can be accessed from a plurality of scopes without duplicating shared data in the system.

[0008]

In order to achieve the above object, the present invention basically provides a relationship between a plurality of scopes showing a field of view for shared data composed of a plurality of data and a data type of each data. The defined scope table,
The current scope table that defines the usage order of the plurality of scopes, the privilege table that defines the scope that has the usage right for each data that makes up the shared data, and the relationship between each data that makes up the shared data and the data type When a new data table is created, the scope table is referred to in the order of the scopes defined in the current scope table, and if there is data of the same data type, the scope of the data type and the data identification information are granted the authority. A data addition processing means for additionally defining the table, and additionally defining the identification information, data type and data of the newly created data in the data table,
Upon updating the data, the authority table and the data table are referred to based on the identification information of the update target data, the scope and data type of the update target data are acquired, and then the scope tables are ordered in the scope defined in the current scope table. If the same data type is defined in the same scope as the scope of the update target data, the data update processing means for updating the update target data in the data table, and the identification information of the reference target data when referring to the data After referring to the authority table and the data table based on the above, and obtaining the scope and data type of the reference target data, the scope tables are referenced in the order of the scopes defined in the current scope table, and the same scope as the scope of the reference target data. Same data in Is defined, the data reference processing means for obtaining the reference target data in the data table, and at the time of deleting the data, the authority table and the data table are referred to based on the identification information of the deletion target data, After acquiring the scope and data type of, the scope table is referred to in the order of the scope defined in the current scope table, and if the same data type is defined in the same scope as the scope of the data to be deleted, in the data table And data deletion processing means for deleting the deletion target data.

[0009]

According to the present invention, when new data is created, the scope tables are referenced in the order of the scopes defined in the current scope table, and if there is data of the same data type, the scope of that data type and the data identification information are Is additionally defined in the authority table, and the identification information, data type and data of the newly created data are additionally defined in the data table.

At the time of updating the data, the authority table and the data table are referred to based on the identification information of the data to be updated, the scope and data type of the data to be updated are acquired, and then the scope tables are defined in the scope order defined in the current scope table. If the same data type is defined in the same scope as the update target data scope, the update target data in the data table is updated.

This is similarly performed for referring to and deleting data.

Therefore, when a program is created by using CASE or the like, by making the scope different for each process, even if the data type is the same, the shared data is updated, referenced, and deleted in the subsequent processes having different scopes. Will not be possible.

On the contrary, the order in which the scope tables are referred to is controlled by the current scope table, and if the data types are the same, the same scope is assigned and new shared data can be registered. It is possible to update, refer to, and delete without duplicating shared data having the same data identification information in the data type. That is, shared data can be accessed from multiple scopes.

[0014]

Embodiments of the present invention will now be described in detail with reference to the drawings.

FIG. 1 is a functional block diagram showing an embodiment of the present invention.

In FIG. 1, 1 is a dialogue terminal for inputting / outputting various data, and 2 is a scope table defining a relationship between a plurality of scopes showing a field of view of shared data composed of a plurality of data and a data type of each data. 3 is
A current scope table that defines the usage order of the plurality of scopes, 4 is a privilege table that defines a scope that has usage authority for each data that forms shared data, and 5 is a relationship between each data that forms shared data and a data type Is a data table that defines, and 6 is an authority processing program that controls access to shared data reference, addition, deletion, and update requests.

As will be described later, this authority processing program refers to the scope table 2 in the order of the scopes defined in the current scope table 3 when newly creating shared data, and if there is data of the same data type, that data type And the data identification information are additionally defined in the authority table 4, and the identification information (data ID) of the newly created data, the data type and the data are additionally defined in the data table 5, and at the time of updating the data. , The authority table 4 and the data table 5 are referenced based on the identification information of the update target data, the scope and data type of the update target data are acquired, and then the scope table 2 is referenced in the order of the scopes defined in the current scope table 2, In the same scope as the scope of data to be updated If one data type is defined, the data update processing step of updating the update target data in the data table 5, and at the time of referring to the data, the authority table 4 and the data table 5 are referred to based on the identification information of the reference target data. , After obtaining the scope and data type of the reference target data, refer to the scope table 2 in the order of the scopes defined in the current scope table 3, and if the same data type is defined in the same scope as the reference target data, A data reference processing step of acquiring reference target data in the data table 5,
When deleting data, the authority table 4 and the data table 5 are referred to based on the identification information of the deletion target data, the scope and data type of the deletion target data are acquired, and then the scope table 2 is ordered in the scope defined in the current scope table 3. And a data deletion processing step of deleting the deletion target data in the data table 5 when the same data type is defined in the same scope as the deletion target data.

FIG. 2 is a hardware configuration diagram showing the specific configuration of FIG. 1, in which the privilege acquisition processing program 6 is stored in the memory 8 and sequentially read and executed by the CPU 7 through the bus 9. In addition, each table 2, 3, 4,
5 is connected to the CPU 7 through the bus 9.

FIG. 3 is a block diagram of the scope table 2, which is composed of fields that define a scope ID 201, a data type ID 202, and data type information 203, and is an accessible data type ID when a certain scope is applied. And the relationship (data type information) between each data type ID and other data types. Note that here, the combinations of the scope ID 201 and the data type ID 202 are different.

FIG. 4 is a block diagram of a current scope table defining current scope information, which is information defining the order in which scopes are referred to.
It is defined that the ID scopes of S001 and S005 should be referenced in order.

FIG. 5 is a block diagram of the authority table 4.
It is composed of fields that define a data ID 501 and an authority scope ID 502, and describes the ID of a scope that has access authority to the shared data of the data ID 501.

FIG. 6 is a block diagram of the data table 5, which is composed of fields defining a data ID 601, a data type ID 602, and data 603.

FIG. 7 is an explanatory diagram showing the relationship between the scopes defined in the scope table 2 of FIG. 3 and the data types. The data type is indicated by the ID in the solid line frame, and the scope is in the broken line frame. The ID is shown. Also, the relationship with each data type indicated by the data type information 203 is related by a straight line.

FIG. 8 is an explanatory view showing the relationship between the scope and the data type from another point of view, for example ID = S0.
The scope of 01 has data of the data type of ID = DT0074 and DT0073 in the field of view, and similarly ID = S.
The scope of 004 is ID = DT0421, DT0073
It is shown to have data of the data type of within the field of view.

In this case, it is shown that the data of the data type of ID = DT0421 falls within the visual field of the scope of ID = S006.

9A and 9B are flowcharts showing the procedure of the data addition process and the data update process executed by the authority processing program 6.

The data addition process and the data update process will be described in detail below with reference to FIG.

First, in the data addition process of FIG. 9A,
Data created using the interactive terminal 1 and data type I
Input D (step 701). Now the data is "A
A "and the data type ID are" DT0073 ".

Next, the current scope information is read from the current scope table 3 (step 702).

Next, one line of the scope table 2 is read according to the current scope information (step 703). The current scope information is S004, as shown in FIG.
Since the order is S001 and S005, the scope table 2 whose scope ID 201 is S004 is searched in order, and when this is completed, the scope I in the scope table 2 is searched.
When D201 is S001, when it is finished, the scope table 2 is searched sequentially for scope ID201 of S005.

It is determined whether or not the scope table 2 can be read, and if it is possible, step 704 is executed, and if not so, the processing ends (step 707).

Data type ID read in step 703
202 is compared with the data type ID input in step 701. If they match, step 705 is executed, and if they do not match, step 703 is executed (step 70).
4).

Here, when the scope ID specified by the current scope information is S004, according to the scope table 2 of FIG. 3, the data type IDs of DT0421 and DT0073 described in the line numbers 205 and 206 are read out. However, of these, DT0073 is step 701.
Since it matches the data type entered in step 70
The process moves to 5.

In step 705, a data ID is assigned to the data input in step 701. For example, “D0041” is assigned. Then, the data ID and the data input in step 701 are additionally registered in the data table 5 (step 705). As a result, as shown in FIG.
6, "D0041" is additionally registered as the data ID 601, "DT0073" is additionally registered as the data type ID 602, and "AA" is additionally registered as the data 603.

Finally, the authority scope ID 502 is "S004" and the data ID 501 is "D0041".
Is additionally registered in the authority table 4 (step 706).
As a result, the line number 505 of the authority table 4 becomes as shown in FIG.

With the above, the data addition processing is completed.

Next, the data updating process of FIG. 9B will be described.

In the data updating process, the data ID and data of the data to be updated are input using the interactive terminal 1 (step 751). Now, the data ID is "D0041",
The data is “BB”.

Next, using the authority table 4, the data ID
Acquires the authority scope ID 502 from (step 75)
2).

For example, in the authority table 4 of FIG. 5, the authority scope ID 502 of data ID = D0041
Is described as "S004", the authority scope I
“S004” is acquired as D502.

Next, using the data table 5, the data ID 760 to the data type ID 602 of the data to be updated.
Is acquired (step 753).

For example, in the data table 5 of FIG. 6, the data type ID of data ID = D0041 is “D
Since it is described as "T0073", the data type ID
As a result, “DT0073” is acquired.

Next, the current scope information is read (step 754).

Next, the scope table 2 is sequentially read line by line in the order of the scope indicated by the current scope information (step 755). Now, the current scope information is S
Since the order is 004, S001, and S005, the scope table 201 is searched for the scope ID 201 of S004 in order, and when it ends, the scope table 2 of which the scope ID 201 is S001 and the end of scope table 2 Scope ID 201 is S005
Search for items in order.

Whether or not the scope table 2 can be read is determined. If it is readable, step 756 is executed, otherwise step 758 is executed (step 771).

At step 758, the data type ID obtained at step 753 is displayed on the interactive terminal 1 with a warning indicating that the data type ID cannot be found even if the scope table 2 is read in the order of the current scope information, and the data updating process is terminated. .

On the other hand, if the scope table 2 can be read, then the data type ID 202 read from the scope table 2 in step 755 and step 7
53 Compared with the acquired data type ID, if they match, execute step 757, and if they do not match, step 7
55 is executed (step 756).

Line number 2 in scope table 2
Since the data type IDs match when the contents of 06 are read, step 757 is executed next.

In step 757, the scope I in the authority scope IDs 502 and 206 acquired in step 752.
D201 is compared (step 757). If they match, step 760 is executed, and if they do not match, step 759.
To execute.

At step 760, the data 603 corresponding to the data ID 760 in the data table 5 is updated.

In the case of this example, the data 60 of the line number 606
“AA”, which is 3, is updated to “BB”.

On the other hand, if the authority scope IDs 502 and 206 do not match the scope ID 201, a pseudo update process and a warning, which will be described later, are displayed in step 759. After the execution of step 758 or step 759 or step 760, the data update process ends.

By the way, in the data reference process, the data input in step 751 in the data update process is eliminated, and the data 6 is obtained using the data table 5 from the data ID.
In step 760, the data to be referred to is displayed in a shaded manner in order to notify that there is no authority for updating or the like. Note that step 75
In the case of 8,759, a warning is displayed that there is no reference authority.

The same applies to the data deletion processing.
This is achieved by eliminating the input of data in step 751 in the data updating process, deleting the data to be deleted as it is in step 760, and displaying a warning that there is no deletion authority in steps 758 and 759.

By the way, when the data created in the previous process causes inconvenience in the subsequent process, it is necessary to artificially update the data by some method, and review and adjust at an appropriate time.

FIG. 10 is a functional block diagram showing a second embodiment enabling pseudo update. A pseudo update processing program 10 is provided in place of the authority processing program 6 of FIG. 1, and a pseudo data table 11 is provided. Has been added.

As shown in FIG. 11, the pseudo data table 11 is composed of fields of data ID 901, data 902, pseudo data ID 903, and next pseudo data ID 904. The data ID 904 forms a chain structure. That is, the next pseudo data ID 90
When 4 is not blank, there is the same pseudo data ID 903 as the next pseudo data ID 904, and the data IDs corresponding to both are the same.

The pseudo data ID 903 and the next pseudo data ID 904 are used for the purpose of arranging the contents of data changes other than the update from the authorized scope in time series.

FIG. 12 is a flowchart showing the processing procedure of the pseudo update processing program 10. Hereinafter, the processing procedure will be described in detail with reference to FIG. In the pseudo update processing program 10, it is assumed that the data ID and the data are already stored.

Now, the data ID is "D0041",
It is assumed that “AA.04” is stored in the data.

Pseudo data ID of the pseudo data table 11
Unused pseudo data ID 910 in 903 is allocated (step 7581). For example, “RD080” is assigned.

Next, one line of the pseudo data table 11 is read (step 7582).

If it is readable, step 7584 is executed, otherwise step 7587 is executed (step 7583).

The known data ID is compared with the data ID 901 read in step 7582. If they are the same, step 7585 is executed, and if not, step 7
582 is executed (step 7584).

Next, it is checked whether or not the next pseudo data ID 904 read in step 7582 is blank. If it is blank, step 7586 is executed, and if it is not blank, step 7582 is executed (step 7585).

In Step 7586, Step 7581
The pseudo data ID 910 allocated in step 7582
It is substituted in the place of the next pseudo data ID 904 read in. Next, the known data ID and data, the pseudo data ID 910, and the blank set are added to the end of the pseudo data table 11 (step 7587).

At the end of this process, the contents of the row numbers 910 and 911 of the pseudo data table 11 are changed to the state shown in FIG.

With the above, the pseudo update process is completed.

A method of referring to the data thus pseudo-updated will be briefly described.

First, the data ID to be referred to and the data ID 901 in the pseudo data table 11 are matched. If there is, the chain of the pseudo data ID 903 and the next pseudo data ID 904 is traced from there to the blank portion of the next pseudo data ID 904, and the data 902 of that line is displayed. At this time, information such as pseudo updated data is also displayed.

However, if there is no match between the referenced data ID and the data ID 901 in the pseudo data table 11, the referenced data ID has not been subjected to the pseudo update process. Therefore, the pseudo update process described above is performed. Perform reference processing when not performing.

Further, when the user sees the data before the pseudo update processing or the data after the pseudo update processing which is not the latest, the user can freely trace the chain of the pseudo data ID 903 and the next pseudo data ID 904. Can be referred to.

Next, the authority transfer process will be described.

FIG. 13 is a functional block diagram showing an embodiment in which the authority transfer processing is enabled, and an authority transfer processing program 12 is provided in place of the pseudo update program 10 of FIG.

FIG. 14 is a flowchart showing the procedure of the authority transfer process, which will be described in detail below with reference to FIG.

First, the data I of the data for transferring the authority
D and the transferee's scope ID are input using the interactive terminal 1 (step 1001). Now, "D0041" is used as the data ID, and "S000" is used as the scope ID.
It is assumed that "1" is input.

Next, using the data table 5, the data I
The data type ID 602 is acquired from D "D0041" (step 1002). In this example, since the data ID is “D0041”, the row number 606 of the data table 5 indicates that the data type ID 602 is “DT.
“0073” is acquired.

Next, the current scope information is read (step 1003). Further, the scope table 2 is read in the order of the scope of the current scope information (step 1004). If it is readable in step 1004, step 1006 is executed, otherwise step 10
09 is executed (step 1005).

Next, the scope ID 201 read in step 1004 and the scope ID 1052 input in step 1001 are compared, and if they are the same, step 100
7 is executed, otherwise step 1004 is executed (step 1006).

Next, the data type ID 202 read in step 1004 and the data type ID acquired in step 1002 are compared, and if they are the same, step 10
08, otherwise execute step 1004 (step 1007).

Now from step 1004 to step 100
The loop up to 7 moves to step 1008 when the line number 206 of the scope table 2 is read.

Next, the data ID "D" in the authority table 4
The authority scope ID 502 corresponding to "0041" is rewritten to the scope ID "S0001", and the processing ends (step 1008).

As a result, line number 5 in authority table 4
05 authority scope ID 502 is from "S004" to "S
Is rewritten as "001".

In step 1009, processing such as displaying an error message on the interactive terminal 1 is performed, and the authority transfer processing ends.

As described above, according to the above embodiment, when new shared data is created, the scope table 2 is referred to in the order of scopes defined in the current scope table 3,
If there is data of the same data type, the scope of the data type and the data identification information are additionally defined in the authority table 4, and the identification information of the newly created data, the data type and the data are additionally defined in the data table 5.

When updating the data, the authority table 4 and the data table 5 are referred to based on the identification information of the data to be updated, the scope and data type of the data to be updated are acquired, and then defined in the current scope table 3. The scope table 2 is referred to in the order of the scopes, and if the same data type is defined in the same scope as the scope of the update target data, the update target data in the data table 5 is updated.

Since access to shared data is controlled for data reference and deletion as in the update process, the scope is made different for each process when a program is created using CASE or the like. As a result, even if the same data type is used, shared data cannot be updated, referenced, or deleted in a subsequent process with a different scope, and confusion due to arbitrary change of shared data can be prevented.

On the contrary, the order in which the scope table 2 is referred to is dynamically controlled by the current scope table 3,
For the same data type, by assigning the same scope and registering new shared data, it is possible to update, refer to, without duplicating the shared data of the same data identification information with the same data type created in the previous process. Can be deleted. That is, shared data can be accessed from multiple scopes.

Further, since the pseudo update can be referred to and the reference can be made to the update, the data can be updated while keeping the original data and its authority. This can be used, for example, when the data decided at the design stage is not convenient in the field, and when the pseudo update is performed for adjustment at a later date. In addition, since it is possible to transfer the authority, it can be used when it is impossible to go back to the initial stage and remake it because of the progress of the process. Further, by using the authority process and the authority transfer process, an appropriate scope can be selected at the time of data creation and the authority can be given to the scope.

[0090]

As described above, according to the present invention, CASE
When a program is created using, etc., by making the scope different for each process, it is not possible to update, reference, or delete shared data even in the same process with the same data type in subsequent processes with different scopes. It is possible to prevent confusion due to arbitrary changes in.

On the contrary, by dynamically controlling the order in which the scope tables are referred to by the current scope table, and if the same data type is used, the same scope is assigned and new shared data can be registered. It is possible to update, refer to, and delete the shared data having the same data type and having the same data identification information without duplication. That is, shared data can be accessed from multiple scopes.

Specifically, if the contents expressed by the scope are tools used at a certain stage, for example, it is possible to control access to data shared by the tools. As a result, one shared data can be referred to by multiple tools at the same time, and when a change is made from a certain tool, the change is made only when the request is made by a legitimate tool, and the changed contents. Can be directly reflected in other tools.

[Brief description of drawings]

FIG. 1 is a functional block diagram showing an embodiment of the present invention.

FIG. 2 is a hardware configuration diagram of FIG.

FIG. 3 is a configuration diagram of a scope table.

FIG. 4 is a configuration diagram of a current scope table.

FIG. 5 is a configuration diagram of an authority table.

FIG. 6 is a configuration diagram of a data table.

FIG. 7 is an explanatory diagram showing a relationship between a scope and a data type.

FIG. 8 is an explanatory diagram showing a relationship between a scope and a data type from another viewpoint.

FIG. 9 is a flowchart for a data addition process and a data update process.

FIG. 10 is a functional block diagram showing a second embodiment provided with a pseudo update processing function.

FIG. 11 is a configuration diagram of a pseudo data table that stores the relationship between original data and pseudo update data.

FIG. 12 is a flowchart for performing a pseudo update process.

FIG. 13 is a functional block diagram showing a third embodiment provided with a right transfer processing function.

FIG. 14 is a flowchart for performing authority transfer processing.

[Explanation of symbols]

1 ... Interactive terminal, 2 ... Scope table, 3 ... Current scope table, 4 ... Authority table, 5 ... Data table, 6 ... Authority processing program, 7 ... CPU, 8 ... Memory, 10 ... Pseudo update processing program, 11 ... Pseudo data table, 12 ... Authority transfer processing program.

Claims (1)

[Claims] 1. A scope table defining a relationship between a plurality of scopes showing a field of view for shared data composed of a plurality of data and a data type of each data, a current scope table defining a use order of the plurality of scopes, A privilege table that defines the scope that has usage rights for each data that makes up shared data, a data table that defines the relationship between each data that makes up shared data and the data type, and the current scope table when creating new data The scope table is referred to in the order of the scopes defined in 1., and if there is data of the same data type, the scope of the data type and data identification information are additionally defined in the authority table, and the newly created data in the data table is also defined. Additional definition of identification information, data type and data When the data addition processing means and the data are updated, the authority table and the data table are referred to based on the identification information of the update target data, the scope and data type of the update target data are acquired, and then the data is defined in the current scope table. Referring to the scope table in order of scope, if the same data type is defined in the same scope as the scope of the update target data, the data update processing means for updating the update target data in the data table, at the time of referring to the data, After referring to the authority table and the data table based on the identification information of the reference target data and acquiring the scope and data type of the reference target data, the scope tables are referenced in the order of the scopes defined in the current scope table, and the reference target Same as data scope If the same data type is defined in the co-op, the data reference processing means for acquiring the reference target data in the data table, and when deleting the data, refer to the authority table and the data table based on the identification information of the deletion target data. Then, after acquiring the scope and data type of the data to be deleted, refer to the scope table in the order of the scope defined in the current scope table, and if the same data type is defined in the same scope as the scope of the data to be deleted And a data deletion processing unit that deletes the deletion target data in the data table, the shared data management system.