JPH05197533A - Control method for data item - Google Patents

Abstract

(57) [Abstract] [Purpose] "Data item", which is metadata shared in the course of application program development.
On the other hand, it can be integrated based on logical commonality without being affected by physical conditions such as attributes, and realizes unified management with a consistent name from beginning to end. Moreover, the burden on the user is reduced by the function of automatically completing the change of all the affected areas when the metadata specifications are changed. [Structure] A display device 11 for displaying input information, an input device 12 for inputting setting information or search information of a data item on the format of the display device 11, and a processing of the input information in a data item management system. However, the processing device 13 having the data item registration function and the search function, and the one-to-one correspondence between the purpose of use and the attribute information based on the name of the data item.
And a data item dictionary 15 for managing a plurality of data items 14 configured by a combination of.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a management method for registering and retrieving data items to be handled in a series of processes for developing a large-scale application program.
In particular, the present invention relates to a data item management method that enables consistent management as data items that are centrally managed by a logical meaning for logically identical data.

[0002]

2. Description of the Related Art Conventionally, in the process of developing an application program, the type of each data used,
By registering the metadata called "data item" that describes the attribute information such as data length in the metadata database called "data item dictionary", and sharing the "data item" thereafter, the development and subsequent maintenance can be performed. Methods to increase efficiency are generally known. In this data item, since the unified management of uniquely identifying the attribute by the search means using the name as a key is realized, it is necessary to set a unique name for each attribute. In the development of a large-scale application program, in a series of processes from the upstream to the downstream, the attribute is differentiated for each purpose of use, so that a different name must be set each time. In this case, since the data items are registered in the data item dictionary with different names for each attribute, it is difficult to perform unified management based on the relation of logical contents. As a function to set data items by this method, EAGLE2 /
There was a data item specification creation function of the XDM data dictionary in DCT. Regarding this function, for example, "Program Product VOS3 System Development Support EAGLE2 System Development Edition, No. 6180-3.
-810-10, page 257, Hitachi, Ltd.
Published by Software Development Headquarters ".

[0003]

In the above-mentioned data item dictionary according to the prior art, when searching for a corresponding data item,
The method uses the name of the data item as a key, and in order to realize unified management of the data item with this method, it is necessary to set a unique data item name for each different combination of data and attribute. there were. Therefore, even if the contents are logically the same, it is necessary to set the name of another data item only because the attribute of the input or output format, for example, the data type is different. Therefore, there were the following four problems. 1. Increasing the number of data items Although the data is logically the same, the name of another data item must be set each time the attribute of that data is different. Therefore, the number of names of data items to be managed in the data item dictionary becomes huge. Due to this phenomenon, the number of names of data items to be searched increases, so it is necessary to properly specify the necessary data items while recognizing many data items. In the above, it becomes a cause of increasing annoyance. 2. Inconsistency of data item names in the upstream and downstream of the application program development process
In the downstream, which is the basic design, it is general to differentiate into concrete individual attributes. Therefore, in the conventional technique in which the name of the data item and the attribute of the data have to be registered in a one-to-one correspondence, a new individual data item name has to be set again for each of the differentiated attributes. For example, in the upstream process of application program development, there is a possibility that the design is performed at a level of handling some date without recognizing the attribute of concrete data. At such a time, only the name of the data item can be set. In the downstream process of application program development, the purpose of use of this data item is clearly determined, so that multiple items such as full-width numeric characters for Japanese calendar display and half-width numeric characters for Western calendar display can be used. Is subdivided into attributes. In this case, in the conventional technology, since the data are logically the same, but the attributes are different, it is necessary to set unique data item names, and the data item names set in the upstream process are However, it cannot be used as it is in the downstream process. That is,
In the upstream process and the downstream process of development, there is no choice but to give different names to data items that logically represent the same concept. Therefore, the description about the names of data items does not match between the document created in the upstream process of the design and the document created in the downstream process, resulting in lower productivity, maintainability, and lower system reliability. It was the cause. 3. Difficulty in grasping open positions when changing the specifications of data items Since a unique data item name is required for each attribute, the conventional method of data item management that only has a search function using the data item name as a key It was not possible to grasp the related range based on the logical identity. In order to deal with such a problem, in the past, the name of a data item was sometimes divided into a prefix and a suffix. For example, suppose that a data item handling date is named "S-DATE", and the date written in full-width characters and the date written in half-width characters are to be shown in association with each other. In this case, "S
-DATE "is used as a prefix, and" -FULL "and
"S-DATE-" with the suffix "-HALF"
The names "FULL" and "S-DATE-HALF" are added to the data items. With this method, since names that are similar in appearance are used as a guide to know whether or not they are related, when changing the specifications of data items, each data item is searched independently and I still have to make changes, and
It was unreliable because there was no certainty that all relevant data items could be changed without exception. 4. The attribute expansion information from upstream to downstream of the design cannot be reused. In the above conventional technology, the name expanded from the abstract data item in the upstream process of the development to the concrete data item in the downstream process has changed. In that case, since the data item does not have the function of storing the origin of the name, if the data item registered in the data item dictionary is to be reused for system development with a similar configuration, it is specified in the downstream process. Only the specified data items can be reused, and it was not possible to reuse the process whose name was embodied in the process from the upstream process to the downstream process. The object of the present invention is to improve such problems and, in a series of processes for developing an application program, affect logically identical data from the upstream process to the downstream process to the difference in attributes. It is to provide a management method of data items that can be consistently managed from the beginning to the end as a data item that is centrally managed by a logical meaning.

[0004]

In order to achieve the above object, the data item management method of the present invention provides correspondence between data item names and data attributes handled in a series of steps in software design and development. In the system of registering and using as a shared resource, it is equipped with a data item dictionary that manages data items that combine the purpose of use and attributes under a single name, and logically the same data is stored in a single name. Originally registered as the same data item, logically related data items are integrated and managed as the same data item, and at the time of retrieval, the target attribute is made unique by using the name and purpose of use as keys. Decide or specify only its name as a key and display a list of purposes and attributes managed as the same data item under that name By fixing the attribute information corresponding to the selected purpose of use, it is possible to correspond to the conventional data item that has only one attribute, and it is possible to reduce the number of names to be managed and the man-hours for name setting. There is. In addition, in the application program development support system using the above-mentioned data item dictionary, when registering a data item, only the name of the data item is registered unless the information including the purpose of use and attributes of the data is confirmed. The characteristic is that data attributes and purpose of use that have been determined as development progresses are added as a set, and the names of data items are centrally managed throughout the entire development process. If only the name is designated as a key, the purpose and attribute managed as the same data item under the name are displayed in a list, and the attribute information corresponding to the selected purpose is determined. Furthermore, when reusing the data item dictionary obtained from the upstream process to the downstream process of application program development, if only a single name indicating a data item was changed, it was integratedly managed under that name. It is characterized by inheriting and managing the combination of purpose of use and attribute under the changed name, including the development process. By adopting this management method, consistent design and upstream processes are possible. Since the name of the data item can be used, when the specification of the data item is changed, it is possible to detect the range of influence on all related detailed designs and automatically correct it by simply changing the data item. is there.

[0005]

In the present invention, since consistent data item names are inherited throughout the process of application program development, unified management of data items in the data item dictionary is realized, and chaotic data item names are realized. It is possible to prevent the diffusion of numbers. Further, even though a plurality of attributes are managed by the same data item name, it is possible to maintain consistency of each attribute according to its use. Furthermore, since it is possible to specify a logical data item name that is not affected by the difference in attributes, for example, in each process of application program development, the data item name set in the upstream process can be specified in the downstream process. , Even if subdivision of attributes occurs, they can be continuously shared. Therefore, in each design process, unified management with consistent data item names can be realized from beginning to end, and when the specifications of a data item change, simply change the contents of the data item and It is possible to deal with the entire range of influence beyond differences.

[0006]

DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram of a data item management system in one embodiment of the present invention, FIG. 2 is a diagram showing a data item setting method in one embodiment of the present invention, and FIG. 3 is a data item setting in one embodiment of the present invention. FIG. 4 is a diagram showing the process of FIG. 4, and FIG. 4 is a diagram showing a data item search method in an embodiment of the present invention. In FIG. 1, 11 is a display device for displaying input / output information, 12 is an input device for inputting setting information or search information of data items on the format of the display device 11,
Reference numeral 13 denotes a processing device that processes the input information and has a data item registration function and a data item search function, and a data item dictionary 15 that manages a plurality of data items. Reference numeral 14 indicates a data item accessed from the processing device 13 based on the input information, which is centrally managed by combining a plurality of purposes and attribute information based on a single name. It

Next, the setting function of the processing device 13 will be described. In FIG. 2, reference numeral 22 is an input screen for inputting each data, 21 is a format for setting data items displayed in the drawing 22, 23 is a name input field, 24 is a purpose input field, and 25 is an attribute input field. Shown respectively. The name input field 23 is an area for inputting a single name used for unifying management of data items. The purpose-of-use input field 24 has a one-to-one relationship with the attribute input field 25, and is an area for inputting the purpose of use of data to be handled and attributes such as data length and data type. In this embodiment, when a plurality of attributes are managed under the name of a single data item and the data item is set, according to the process of program development,
Input required data from the input screen 22 (display device 11 in FIG. 1). For example, in the upstream process when developing a large-scale application program for data items, if the detailed attributes are not yet determined, only the name input field 32 is determined as shown in FIG. The contents are stored in the item dictionary 15. After that, when the specifications are finalized in the downstream process, the data item dictionary 15 is searched using the name of the data item as a key, and as shown in (b), the intended purpose and attribute are respectively entered into the intended purpose input field 35 and the attribute input. Box 3
After inputting in 6, register again. Furthermore, when the data item is divided into a plurality of attributes according to the purpose, the target data item is searched from the data item dictionary 15 using the name of the data item as a key,
As shown in (c), the setting contents are added to the new intended use input field 38 and the attribute input field 39 in a one-to-one correspondence and stored again in the data item dictionary 15. In FIG. 3, 31,
Reference numerals 34 and 37 denote formats for setting data items.
By repeating these operations, a plurality of different attributes are collectively registered under the name of a single data item. As a result, logically related data items having a plurality of attributes can be centrally managed under the name set in the upstream process, and consistent data item setting can be realized.

Next, the search function of the processing device 13 shown in FIG. 1 will be described. In FIG. 4, 41 is a search key input screen (display device 11 in FIG. 1), 42 is a name input field in the data item search format, 43 is a purpose input field, and 45 and 46 are output screens. This name input field 4
Reference numeral 2 is an area for inputting the name of a data item in which a plurality of attributes are centrally managed due to the logically identical relationship. Further, the purpose-of-use input field 43 is an area for inputting the purpose of use set to one-to-one with the attribute by the registration function of the processing device 13. In the present embodiment, in addition to the search function using only the name of the data item as a key, it has a search function using the purpose of use as a key. For example, if only the name field 42 is input on the screen 41 and a plurality of attributes are registered in the data item of this name, the requested attribute cannot be determined, so registration is performed based on this data item. The output screen 46 displays a list of the purpose of use and the attributes that have been set. If both the name column 42 and the intended use column 43 are entered, the data item dictionary 1
Search for 5. In this case, since all the keys necessary for searching the data item are prepared, the content of the target data item can be confirmed as shown in the output screen 45.

Here, the case where the shared data item is used in the downstream process of the application program design will be described. FIG. 5 is a diagram showing application program development using the data item management method of the present invention, and FIG. 6 is a diagram showing data items for which only attributes are fixed in one embodiment of the present invention. In FIG. 5, 51 is CO
BOL source program edit window, 52 data item content list screen, 56 copy command, 58
Is cursor, 59 is edit screen, 60 is paste command, 5
Reference numeral 7 is a temporary memory. In this embodiment, when the registered data item is used for the definition of the data used in the COBOL source program, the display device 11 shown in FIG. 1 is used.
In addition, the editing window 51 and the list screen 52 of the purpose and attribute of the data item to be used are displayed in a multi-window. At this time, the screen 52 is the screen 41 shown in FIG.
The name of the data item to be used is entered in the name field 42 of, and the data item dictionary 15 is searched and displayed. Then, from the list display of the purpose of use and attributes belonging to the data item, the portion 55 that matches the purpose of use to be used is selected with the keyboard, mouse, etc., and the copy command 5
By selecting 6, the name and attribute of the data item is stored in the temporary memory 57. On the other hand, on the screen 59, the cursor 58 is moved to the data item input area, and the paste command 60 is selected from the pull-down menu or the like on this screen. This command 60 copies the name and attribute information of the data item previously stored in the temporary memory 57 to the editing area. Further, when registering a data item in this embodiment, if there is only one attribute related to the data item, even if the search key is only the name of the data item, the corresponding attribute is uniquely determined. .. For example, as shown in FIG. 6, when the contents of the data item name column 62 and the attribute column 63 are confirmed and the intended use column 61 is blank, the attribute is only “N (9)”, The attribute can be uniquely determined only by specifying the name “S-DATE”. Therefore, if the name field 42 of the screen 41 shown in FIG. 4 is filled, the purpose field 43 need not be entered.
Further, since the data items shown in FIG. 6 are the same as the data items of the conventional method (method of setting a unique name for each attribute in the data item), the data items are accumulated by the conventional method. The method of the present invention can be applied while directly inheriting the existing data item dictionary. That is, the data items according to the conventional method may be treated in the same manner as when the above-mentioned purpose field is not required to be input.

Here, a registration method will be specifically described in the case where the correspondence between the purpose of use of the data item and the attribute is determined in a very limited manner depending on the user environment. For example, when the date is a data item, the data entity is a Japanese calendar represented by full-width characters such as "August 20, 1991" or half-width characters such as "1991.08.20". Generally, the character type and the number of digits are limited to some extent depending on the purpose of use, such as the Western calendar represented by the number. In such a case, the correspondence between the purpose of use and the attribute thereof is, for example, the combination of purpose of use: Japanese calendar date, attribute: N (10) and purpose of use: Western calendar date, attribute: X (10). By registering as a reserved word in advance such as a combination, the registered attribute can be automatically set only by selecting the purpose of use from the reserved words. As a result, it is possible to register and manage the data item only by the name and the purpose of use, which does not require the input of the data attribute. Further, in this example, when the data item is changed or the existing data item is used, the name of the data item to be searched and the purpose of use are input. That is, two types of search functions as shown in FIG. 4 are prepared. These two types of functions are as follows. First search function: When both the name of the data item and the purpose of use are input, the corresponding data item is searched from the data item dictionary using the input name and purpose of use as keys. Then, when the corresponding data item is registered, the data item can be directly used. Second search function: When only the name of a data item is entered, the name is used as a key to search the data item dictionary for a data item, and a list of registered purposes and attributes is displayed. Let the user choose which one to use. This makes it possible to use data having an attribute that suits the purpose. If the correspondence between the purpose of use and the attribute can be determined extremely limited by the user environment, the attribute is not displayed and only the list of the purpose of use is displayed so that the user can recognize the attribute of the data. You can eliminate the need.

[0011]

According to the present invention, by registering / managing a plurality of logically related attributes in one data item, it is possible to prevent the number of data items to be managed from spreading, and to make an application program. Consistent data items are shared from the upstream process to the downstream process of development, and unnecessary processes such as resetting data items for each different attribute are unnecessary.
Therefore, it is possible to reduce the man-hours required for developing the application program, and also to operate and centrally manage it as a general-purpose asset that can be used as it is in the development of other application programs. further,
By centrally managing multiple logically related attributes with a single data item, if a specification change occurs in a data item, you can simply change the data item and change all related impact areas. Can be completed.

[0012]

[Brief description of drawings]

FIG. 1 is a configuration diagram of a data item management system according to an embodiment of the present invention.

FIG. 2 is a diagram showing a method of setting data items in an example of the present invention.

FIG. 3 is a diagram showing a process of setting data items according to an embodiment of the present invention.

FIG. 4 is a diagram showing a data item search method according to an embodiment of the present invention.

FIG. 5 is a diagram showing application program development using the data item management method of the present invention.

FIG. 6 is a diagram showing a data item in which only an attribute is fixed according to an embodiment of the present invention.

[Explanation of symbols]

 11 display device 12 input device 13 processing device 15 data item dictionary 57 temporary memory

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Keiko Taniguchi, 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa, Ltd. Software Development Division, Hitachi, Ltd. (72) Incubator, Kiyoko Sobue, Totsuka-cho, Totsuka-ku, Yokohama, Kanagawa Address Company Hitachi, Ltd. Software Development Headquarters (72) Inventor Toshiharu Tsukagoshi 5030 Totsuka-cho, Totsuka-ku, Yokohama-shi, Kanagawa Prefecture In-house Company Hitachi Ltd. Software Development Headquarters (72) Toshiaki Isa Totsuka, Totsuka-ku, Yokohama-shi, Kanagawa 5030, Machi Incorporated company Hitachi Ltd. Software Development Division

Claims (6)

[Claims] 1. For a data item handled in a series of steps in designing and developing software, the correspondence between the name of the data item and the attribute of the data is registered, and the registration and retrieval of the data item of the system used as a shared resource. The method includes a data item dictionary that manages data items that combine a purpose of use and attributes under a single name, and logically identical data is registered as the same data item under the name. In addition, when searching for a data item, a management method for the data item is characterized in that the target attribute is uniquely determined by using the name and the purpose of use as keys. 2. An application program development support method using the data item dictionary according to claim 1,
When registering a data item, if the information including the purpose of use and attributes of the data is not confirmed, register only the name of the data item and set the attribute and purpose of use of the data determined as the development progresses. A method for registering data items, which is characterized by sequentially adding. 3. An application program development support method using the data item dictionary according to claim 1,
If only the above single name is specified as a key when searching for data items, a list of purposes and attributes managed as the same data item under that name is displayed.
A method for searching a data item, which comprises determining attribute information corresponding to a selected purpose of use. 4. A method of managing a data item of a system, wherein a correspondence between a data item name and a data attribute is registered for a data item handled in a series of steps in software design and development, and is used as a shared resource. , A data item dictionary that manages data items that combine the purpose of use and attributes under a single name is provided, and logically the same data is registered as the same data item under the name. When searching for a data item, if the name and purpose of use are specified as a key, the attribute of interest is uniquely determined and displayed. If only the name is specified as a key, the name A data item management method characterized by displaying a list of intended use and attributes managed as the same data item in and in and defining attribute information corresponding to the selected intended use. Law. 5. An application program development support method using the data item dictionary according to claim 1,
When reusing the data item dictionary, if only a single name that indicates a data item is changed, the combination of the purpose of use and the attributes that were integrated and managed under the name is changed to the changed name. A data item management method characterized by being inherited by and. 6. When reusing the data item dictionary, if the specification of the data item is changed, only the data item is changed, and the range of influence on all related detailed designs is detected, The data item management method according to claim 5, wherein the data item is corrected.