JPH0296231A - Edition support method - Google Patents

Abstract

PURPOSE:To reduce the labor and the time required for the users to retrieve the internal information on a data dictionary by storing a pair of each data name and additional information, updating the corresponding additional information for each editing job to decide the display sequence, and displaying the data name of the highest priority. CONSTITUTION:A CPU stores a data name and its additional information, e.g., an access time point into a data dictionary 106 in a pair for each editing job. When a user performs the editing operations like the insertion, deletion, etc., of the software specifications in an editing mode by means of an input device 111, the CPU analyzes the input information to acquire the corresponding data name and time information out of the specification or the dictionary 106 and updates the time information. Then the CPU executes an editing operation instruction produced from the user. This action is repeated for each editing operation and at the same time the display sequence of data names is decided based on the updated time information and stored in a display table. Then the data name of the highest priority within the table is displayed on a display device. As a result, the possibility is increased for display of the corresponding data name at transcription. Then it is possible to reduce the the labor and the time for the user to retrieve the internal information on the dictionary.

Description

[Detailed description of the invention]

[Industrial Application Field] The present invention relates to a support method and apparatus for editing software specifications or programs, and in particular displays data names 'JIB'd in a data dictionary on a screen, and displays the following information on the screen:
By posting the data name selected by the user,
The present invention relates to an editing support method and apparatus suitable for reducing key human labor required for data naming. [Prior art] As a conventional editing support method, in general document creation,
In addition to means for searching for information in a dictionary, such as the kana-kanji conversion function of word processors, there are also means for changing the display order of information in the dictionary by means of search operations. Also,
Regarding software specifications, Information Processing Society of Japan, 34th
As described in ``Personal Software Design Support System Based on R Design Dictionary,'' Collected Papers of the Japan National Conference P977, when transcribing information in the data dictionary, the user searches for the information to be transcribed from the data dictionary and displays it on the screen. There is something to display.

[Problem to be solved by the invention]

In the above-mentioned conventional technology, the display order of information in the data dictionary is changed when accessing the data dictionary in some way, such as with a kana-kanji conversion function when editing a document.
When editing operations that frequently appear in software specifications or programs, such as inserts, copies, etc., do not access the data dictionary, the display order of information in the data dictionary is not changed. Therefore, when the user attempts to access the data dictionary thereafter, the data name operated on first is not displayed preferentially, and a search operation must be performed. The purpose of the present invention is to provide information on the information in the data dictionary even when the user performs editing operations that frequently appear on data names in software specifications or programs, such as inserting and copying operations that do not access the data dictionary. To provide an editing support method that changes the display order and reduces the effort of a user to search for information in a data dictionary. The data name in the software specification or program and the additional information corresponding to this data name are stored as a pair in the data dictionary, and when the user performs editing operations, the data name in the data dictionary is paired with the target data name. The present invention is characterized in that the additional information of the data dictionary is updated, the display order of the data names in the data dictionary is determined based on this additional information, and the data names in the data dictionary are displayed in accordance with the display order. As this additional information, for example, information such as the time of use, the number of times of use, and the second hierarchical level of the data type is used for each data name.

[Effect]

In the present invention, data names in a software specification or program and additional information corresponding to the data names are stored in pairs to determine the order of data names in a data dictionary to be displayed. In addition to obtaining information for determining the order, when the user performs editing operations on software specifications or programs during editing, the additional information of the data name to be edited is updated, and the user performs editing operations. Each time you do this, the display order of the data names in the data dictionary to be displayed is changed, and the display order of the data names in the data dictionary is determined based on the additional information in the data dictionary. When a person transfers a data name from the data dictionary into a software specification or program during editing, the target data name is more likely to be displayed on the screen and search for information in the data dictionary. It can save you time and effort. [Example 1] Hereinafter, an example of the present invention will be described in detail with reference to the drawings. In the following embodiment, an example of editing a software specification will be described. FIG. 1 is a diagram showing an example of the functional configuration of a computer system that implements the editing support method of the present invention. The input information analysis unit 101 in FIG.
11, when editing software specifications, such as inserting, deleting, copying, etc., the entered information (character string, mouse cursor coordinates) is checked whether it was entered from the keyboard or the screen of the display device. Analyze from which position above the input was made. As a result of the analysis, when the human input is performed using a mouse on the software specification displayed on the screen, the editing area data name acquisition unit 102:
The data name corresponding to the input coordinates is obtained from within the software specification. Input information analysis section 10
As a result of the analysis in step 1, if the input was made from within the data dictionary displayed on the screen, the dictionary data name acquisition unit 1
In step 03, the data name corresponding to the input coordinates is acquired from the data dictionary. The additional information acquisition unit 104 searches the data dictionary 106 for the same data name as the data name acquired by the dictionary data name acquisition unit 103 or the editing area data name acquisition unit 102, and performs known text matching. The data name is detected and the additional information paired with the data name is acquired. The additional information update unit 105 updates the additional information acquired by the additional information acquisition unit 104. The data name transfer unit 107 transfers the data name acquired by the dictionary data name acquisition unit 103 to the editing unit 10 for editing.
Transfer to 8. The editing unit 108 executes the editing operation command issued by the user. The display order determining unit 109 determines the display order of the data names to be displayed based on the additional information paired with each data name listed in the data dictionary 106, and stores the result in a display table. The data name display unit 110 displays data names at the bottom of the screen according to a display table that stores the display order of data names determined by the display order determining unit 109. FIG. 2 is a diagram showing the hardware configuration of a computer system that implements the editing support method according to the present invention.
．． Keyboard 202. Maum 203° Memory 2049 Display device 205. It consists of an external storage device 206. The functions of each section 101 to 105 and 107 to 110 in FIG. 1 are realized by a program of the CPU 201. Furthermore, the input device 111 in FIG. 1 is the keyboard 202 in FIG. Corresponding to the mouse 203, the output device 112 of FIG. 1 is the display device 205 of FIG. Corresponding to the external storage device 206, the first
The data dictionary 106 in the figure is the memory 204 in FIG. It is stored in the storage device 206 or the like. Next, based on the functional configuration diagram of FIG. 1, the processing procedure flowchart of FIG. 3, the screen example of FIG. 4, and FIG. 5 are shown. This will be explained in more detail using the example data dictionary shown in FIG. FIG. 4 is an example of a screen during editing of a specification whose specification name is "Order Processing", and shows that an editing operation is performed to transfer the data name indicated by a red stamp 401 to an area indicated by an arrow 402. Further, on the right side of the fourth drawing example, eight data names registered in the data dictionary are displayed in descending order of priority in the display order. Even if they are registered in the data dictionary, those with a lower priority j potential in the first display order are not displayed on the screen. When displaying a data name other than the data name initially displayed on the screen, it may be displayed while scrolling one screen, or may be displayed by searching a data dictionary using a search command. The first process for the editing operations manually performed by the user above.
An example of this will be explained using the flowchart shown in FIG. In the editing target object input processing 301. Select the data name to be edited by pressing the mouse button on the screen. In the coordinate analysis process 302,
For the coordinates input in the edit target object input process 301,
It is determined whether these coordinates correspond to the software specifications displayed on the screen or the data dictionary. In this embodiment, it is a data dictionary. In data dictionary-like data name acquisition processing 304, a data name corresponding to the input coordinates is acquired by searching a data dictionary for the input coordinates. In the screen example shown in FIG. 4, the data name "Order Form" has been acquired. Additional information update processing 306
Now, a data name identical to the acquired data name "C order form" is searched in the data dictionary shown in FIG. 5, and additional information paired with this data name is acquired and updated. The left side of the data dictionary shown in FIG. 5 represents registered data names, and the right side represents additional information. As an example of the additional information, a case will be described in which data, such as time, is used that allows the order in which data names in the data dictionary are accessed to be determined. As a result of a search in the data dictionary with the same data name as the data name "Order Form", the additional information paired with this data name is
It turns out that it is 8:50. This indicates that the data name "Order Form" was accessed once at 8:50.If the time when the above editing operation was performed was 9:21, the data name in the data dictionary The additional information paired with "order form" is updated from 8:50 to 9:21 as shown in FIG. In order to post the command "Post" shown by arrow 403 in FIG.
The data name “order form” indicated by 402 and the posting destination indicated by arrow 402 are passed to the command execution process 308. Command execution processing 3
In step 08, based on the information sent in step 307, transcription processing is executed by operating the internal table of the software specification. In the display order determination process 309, the priority order of the display order is determined based on the additional information in the data dictionary M shown in FIG. In this embodiment, as an example of a rule for determining the display order, a rule is used in which data names with newer access times are displayed preferentially. Figure 6 shows that additional information 601 of the data name to be edited has been updated in accordance with one editing operation, and when determining the data name display j1a order, the additional information shown on the left side of Figure 6 is updated. With reference to the access time, the display priority is determined in order of data name with the newest access time. In FIG. 6, the data name with the highest display priority is "Order Form" and the data name with the lowest display priority is "Paper Accounting Department". According to the display order determined in the data name display order determination process 309, the data names in the data dictionary of FIG. 6 are stored in the display table. In display processing 310, data names are displayed on the screen based on the information stored in the display table. The results are shown in FIG. The data name ``Order Form'' is transferred to the specified position, and the data name ``Order Form'', which was displayed at the bottom in Figure 4 due to its low display priority, is now displayed at the top.Additional information As another example, we will explain the case where the access frequency for the data name is used. An example of the data dictionary is shown in FIG. 8. When the operation shown in FIG. ” additional information is changed from 7 to 8.Display order determination process 309
Then, the display priority is determined in descending order of the data names that are accessed most frequently. The results after the operation are shown in FIG. Among the data names with the same access frequency, "Order form" is displayed with higher priority.As another example of additional information, we will explain the case where the type of data name is used.Generally, in the software specifications Existing data names have types. For example,
S D F (S structuredData F
The data names existing in the low diagram can be classified into function names, data storage names, external entity names, etc. An example of the data dictionary is shown in FIG. Assume that an editing operation is performed to insert a new processing symbol into the screen shown in FIG. In the display order determination process 309, only the priorities of data names of the data type "process" are compared to determine the display priority. Store only the data name of the data type "Paper processing" in the display table.The results after the operation are stored in the 11th
As shown in the figure. Only the data name of the process is displayed. As another example of the additional information, a case will be explained in which the hierarchical level of the software specification where the data name exists is used. In general, some of the data names that exist in software specifications are "parent" in the hierarchical structure of software specifications.
It also exists in the corresponding software specifications. The software specification has one hierarchical level, as shown in FIG. 12, for example. An example of the data dictionary is shown in FIG. In the display order determination process 309, first, the hierarchical level of the software specification to be edited is input. Next, the hierarchical level of the parent software specification is determined from this hierarchical level. If the input hierarchy level is one digit, the parent hierarchy level is set to O. If it is not in 1 digit, drop the lower skill of the hierarchy level. For example, if the input hierarchy level is 2.1.2, the parent hierarchy level will be 2.1. Next, only the priorities of the data names corresponding to the software specifications to be edited or the parent software specifications are compared to determine the priorities for one display. FIG. 14 shows an example of the screen after the operation. Only data names corresponding to hierarchy levels 2.1.2 and 2.1 are displayed. Although the embodiment has been described above regarding four types of additional information, it is also possible to use a combination of these four types of additional information. A second example will be explained. In addition to the first embodiment, when a user inputs a data name that is not registered in the data dictionary while editing a software specification, the data name is automatically saved in the data dictionary.
The flowchart of an example in which a process for recording lI is provided is shown in No. 15.
As shown in the figure. FIG. 16 shows that the specification name order processing is being edited, and the editing operation of inserting the data name "customer ledger" into the area indicated by the arrow 901 is shown. As can be seen, the data name "Customer Ledger" has not been registered in the data dictionary. In editing target data name input processing 801, a character string or coordinates input from a mouse is received. When coordinates are input, the data name corresponding to these coordinates is a data name already registered in the dictionary, so the subsequent processing is the same as in the first embodiment. If input as a character string, the same data name search process 807 searches whether the same data name "customer ledger" as the input data name is registered in the data dictionary shown in FIG. If the same data name as this data name is not registered in the data dictionary, the data name "Customer Ledger" is registered in the data dictionary as a new data name in data name registration processing 809. When a new data name is input, additional information registration processing 810 registers additional information paired with the data name. The input time of the data name "Customer Ledger" is used as additional information.
B. Edit information transfer processing 812 includes the command “insert”
(indicated by arrow 902 in FIG. 16), data name "customer ledger", and insertion position (indicated by arrow 901 in FIG. 16) are passed to command execution processing 812. Command execution processing 812
Now, execute the insert process. In the data name display order determination process 813, the display priority order is determined, including the newly registered data name and the additional information associated with this data name. In display processing 814,
Data names in the data dictionary are expressed on one screen according to display priority. The results are shown in FIG. The data name "Customer Ledger" is inserted into the area indicated by the arrow 901 in FIG. 16, and the inserted data name "Customer Ledger" is registered in the data dictionary and displayed at the top. ,
Information 1101 with the data name “Customer Ledger” represents the data dictionary after registration. The input (access) time of 9:25 is registered in the additional information of the registered data name ``Customer Ledger''. Next, a third example will be shown. In addition to the embodiment, this is a flowchart that includes a process for prohibiting the input of data names that are not registered in the data dictionary during software specification editing.The screen example shown in FIG. represents the g collection operation of inserting the data name ``accounts receivable information'' into the area indicated by the arrow 1301. In the flowchart of FIG. In the editing target object input processing 1201, if the data name input by the user is input from the keyboard, a character string is received, and the data name input by the user is input by selecting the data name in the specification order processing or data dictionary with the mouse. If so, take the coordinates. When input using a mouse, the data name corresponding to the input coordinates is acquired in data dictionary data name acquisition processing 1206 or editing area data name acquisition processing 1204. When a data name is input from the keyboard, it is searched and determined whether a data name identical to this data name exists in the data dictionary (process 12).
05). In the data dictionary shown in FIG. 5, data names used in specification order processing are registered in advance. In order to inform the user that the data name "receivables balance information" input in the editing operation shown in FIG. 20 cannot be used in the specification order processing, the error message output process 1212 outputs the error message 1303 shown in FIG. Output the message as shown in . Command cancellation processing 1213
Since the editing command input by the user is invalidated, the editing command is cleared and returned to the initial state. As shown in this example, when editing a software specification, the data names used in the software specification to be edited are registered in the data dictionary in advance, and the data names to be used are limited, thereby reducing the redundancy of data names. It also makes it easier to manage data names. Next, a fourth example will be shown. FIG. 21 shows a flowchart when the access time of the data name and the type of the data name are used as additional information. In the screen example of FIG. 22, the data name "Order form" indicated by arrow 1501 is
Represents an editing operation of copying to the area indicated by . FIG. 10 shows an embodiment of the data dictionary. The processes up to process 1405 are the same as those in the first embodiment. In data name type acquisition processing 1406, the type of data name is acquired. this is,
This is done by searching within the data dictionary. In the screen example shown in FIG. 22, there are types in the area where data names exist, such as processing and data. There are data accumulation angles, etc. In the VI area indicated by arrow 1501 in FIG. 22, data names are displayed, and arrow 1
In the area indicated by 502, the data accumulation angle is to be displayed. In the editing target area type acquisition process 1407, the type of area indicated by the arrow 15o2 is obtained by referring to the internal table of the specification order receiving process. In FIG. 22, it can be seen that the type indicated by the area of arrow 1502 is the data storage name. Processing! In step 11408, it is determined whether the respective types acquired in the data name type acquisition processing 1406 and the re-gathering target area f type acquisition processing 1407 match. If they do not match, the error message output section 1'l 14-14 outputs a message as the error message output 1503 in FIG. 22 to inform the user that the editing operation is invalid. In command cancel processing 1415, in order to invalidate the editing command, the command is cleared and returned to the initial state. If the types match, normal processing is performed as shown in the first embodiment. It is done. The type is used as additional information, one type is associated with each data name, and the type is
7. By determining whether they match, and executing an editing command only if they match, it is possible to uniformly manage the data names in the software specification. Next, a fifth example will be shown. In addition to the first embodiment, for the data names in the data dictionary, specify a data name for which you want to keep the display order of data names constant, have the specified display position as additional information, and FIG. 23 shows a flowchart of an example in which processing for displaying is provided. The processing up to processing 1706 is the same as the processing of the first embodiment. In process 1707, it is determined whether a display position is specified as additional information of the data name. In display position specification data name display processing 1708, as a result of processing 1707,
Displays the data name for which the display position is specified. FIG. 24 shows an embodiment of the data dictionary. The numbers shown in the display position of the additional information column represent the display order. The shaded area indicates that the display position has not been specified. In the display order determination process 1710, when determining the display order,
Among the data names in the data dictionary shown in FIG. 24, the display order is determined for those whose display position is not specified in the additional information. FIG. 25 shows a screen example of this embodiment. 25th
The shaded area on the right side of the figure is the data name whose display position is specified, and the display order does not change depending on the editing operation, and the data is always displayed at the fixed position. The effects of the following embodiments will be explained. This is related to the software specification order processing used in this embodiment. When creating another software specification, it can be edited by transcribing the data name from the data dictionary. Therefore, it is desirable that the data name to be transcribed be displayed on the screen at all times during editing. In some editing operations, the data name used may be affected by previous editing operations, so by changing the priority of data names displayed each time an editing operation is performed, it is possible to change the data name that is likely to be used during editing. It is possible to display the data name. Next, a sixth example will be shown. The above has described the case where a data name is stored in a data dictionary, but in general, a data name is often a compound word made up of a limited number of words. Therefore, it is also possible to divide the data name into words and store them in the data dictionary. One method for registering words in a data dictionary is to compare a character string input by a user from a keyboard with a Japanese dictionary and divide it into words during creation of a software specification. An example of the data dictionary is shown in FIG. It is possible to reduce the amount of content in the data dictionary by breaking it down into words and registering them. In the above example, the editing of software specifications was explained as an example, but the present invention is not limited thereto, and it goes without saying that the present invention can also be applied to editing of programs. Next, a seventh embodiment will be described. FIG. 27 is a diagram showing an example of the functional configuration of a system according to the seventh embodiment, and FIG. 28 is a flowchart showing a processing procedure according to the seventh embodiment. FIG. 29 is a diagram showing part of the contents of a data dictionary to be described later. In FIG. 27, 1801 is a mouse for inputting coordinates on the screen, and 1802 is a display device that displays data names retrieved from the data dictionary on one screen. 180
3 is a data dictionary that stores the data name and the hierarchical level of the software specification in which the data name exists; 1804 is a keyboard for inputting the mN level of the software specification to be edited; 1805 is the parent software specification of the software specification; This is the 1st hierarchy level calculation unit that calculates the hierarchy level of . The parent hierarchy level calculation unit 1805 performs calculations such as setting the hierarchy level of the rough 1-ware specification of 5 parents to 1 when the hierarchy level of the software specification to be edited is 1.3. A data name search unit 1806 searches the data dictionary 1803 for a data name corresponding to the hierarchical level of the parent software specification and registers the searched data name in a display table. 1807 converts the contents of the display table into display data;
A display section for sending data to the display device 1802 is shown. Third
FIG. 0 shows an example in which a data name is searched from the data dictionary 1803 and displayed when editing the software specification whose hierarchy level is 1.3. Furthermore, the display section 1807
A data name corresponding to the coordinates input using the mouse 1 described above is detected from the display table. 1808 is the display section 18o7
This is a data name transfer unit having a function of transferring the data name detected by the editor 1809 to the editor 1809. editor 1809
transcribes the data name transferred by the data name transfer unit 1808. In addition, in FIG. 27, normally each part 1805 to 1809
This function is realized by the program in the CP tJ 201 shown in FIG. The operation of each part in FIG. 27 will be described below based on the flowchart in FIG. 28. First, in process 1900, the hierarchical level of the software specification to be edited is inputted from the keyboard 1804. Next, in process 1901, the hierarchical level of the input software specification is determined, and based on this, the hierarchical level of the "parent" software specification is calculated. In this case, if the hierarchy level of the input software specification is 1 digit, the hierarchy level of "parent" is set to "0" (process 1903)
. If it is not a single digit, drop the lower digit of the hierarchy level (processing 1
902). For example, if the hierarchy level of the input software specification is 2.1.2, the hierarchy level of the "parent" is 2.
．． This means that it becomes 1. Next, in process 1904, data names corresponding to the hierarchical levels of the parent specification and the specification to be edited are searched from the data dictionary 1803, and the searched data names are registered in the display table (process 1905). In processing 1906,
The contents of the display table are displayed on the screen of the display device 1802. The user clicks the mouse 1 on the data name displayed on the screen.
801, the coordinates are manually processed (1907) and the selected data name is acquired from the input coordinates (processing 1908). Transfer the acquired data name to the editor 1809 (process 1909), editor 180
In step 9, this data name is transferred. The above embodiment differs from the conventional one in that data names and hierarchical levels are stored in correspondence with each other in the data dictionary 1803, as shown in FIG. Similarly, the data name and the name of the specification in which this data name exists are stored in the data dictionary 1803, and separately, the name of the specification in which the above-mentioned data name exists and its hierarchy level are stored in the hierarchy information. It may also be stored in the form of a table. FIG. 31 shows an example of the layer information table. Next, an eighth example will be shown. FIG. 32 is a flowchart showing the processing procedure of the embodiment in the case of using the data dictionary that stores the data name and the name of the specification in which the data name exists, and the hierarchy information table. The operation in this case will be explained below. First, process 2000
Then, from the keyboard 1804, the name of the software specification to be edited is entered manually. Next, in process 2001,
The above hierarchy information table is read, and in step 2002, the hierarchy level of the input specification is determined. Based on this, the hierarchy level of the "parent" software specification is calculated, and the name of the parent specification is determined in step 20o3 using the above hierarchy information table. Next, in process 2004, data names existing in the specification to be edited or the parent specification are searched from the data dictionary. An example of the structure of the data dictionary in this case is shown in FIG. 33. Next, a ninth embodiment will be described. FIG. 34 shows an embodiment in which data types are added to the data dictionary shown in FIG. 29. Further, FIG. 35 is a flowchart showing an embodiment in which data types are added to the seventh embodiment shown earlier. The operation in this case will be explained below. The process until the data name is searched is the same as the case in FIG. 28. Thereafter, the retrieved data name and its type are registered in the internal table (process 2005). Next, in process 2006, the type of display target to be posted is input, a data name having a type that matches this type is searched from the internal table, and registered in the display table (process 2007). The subsequent processing is similar to the flowchart in FIG. 28. It goes without saying that it is also possible to perform processing without using the internal table. FIG. 36 shows an example of transcribing the name of a data flow. When the user picks a data flow display target with the mouse 1801, the type of data flow is input,
Display only the data name that corresponds to the data flow. After transcription, the process of inputting the type of display object is repeated. Next, a tenth example will be shown. FIG. 37 shows an example in which the number of transcriptions is added to the data dictionary shown in FIG. 34. Further, FIG. 38 is a flowchart showing an embodiment in which the number of transcriptions is added to the above embodiment. The operation in this case will be explained below. The process up to inputting the type of display target to be posted (process 2006) is the same as in the case of FIG. 35. Thereafter, data names corresponding to the type of display target are searched from the internal table and registered in the display table in descending order of the number of transcriptions (process 2008). The process is the same as that shown in FIG. 35 until the selected data name is transferred. Here, the difference is that in process 2009 1
The purpose is to increase the number of transcriptions in the data dictionary χ corresponding to the selected data name. FIG. 39 shows an example in which the information is displayed in order of the number of transcriptions. The effects of the eighth embodiment will be described below, taking as an example the case where a child software specification shown in FIG. 41 is newly created for the parent software specification shown in FIG. 40. Child software specifications 7! There are 25 data names, 11 of which exist in the parent software specifications, so they can be transcribed. In terms of the number of characters, 52 out of 99 characters can be transcribed, achieving a reduction in key manpower of approximately 50%. In the above explanation, the case where the data name is stored in the data dictionary has been explained, but in the following explanation, a method of dividing the data name into its constituent words and storing them in the data dictionary will be explained. One method for registering words in a data dictionary is to divide the character strings entered by the user from the keyboard into words by comparing them with a Japanese dictionary while creating software specifications.
This is a method of 1B. Another method is to check data names existing in existing software specifications against a Japanese dictionary, divide them into words, and register them. If the software specification is a COBOL source program, lexical analysis is performed, and the data name is divided by minus signs and registered in the data dictionary. An example of this data dictionary is shown in FIG. When creating a new software specification as shown in Fig. 41, if the above method of dividing the data name into its constituent words and storing them in the data dictionary is applied,
69 out of 99 characters can be transcribed, and approximately 70% key manpower reduction is achieved. The above embodiments are merely examples, and the present invention can be applied in various ways. [Effects of the Invention] According to the present invention, when editing a software specification, program, etc., when transferring a data name in a data dictionary to the software specification, the target data name is accessed in a past editing operation. By preferentially displaying data names in the data dictionary that are likely to be used, the user line has the effect of reducing the effort required to search for necessary information from the data dictionary rII.

[Brief explanation of the drawing]

FIG. 1 is a diagram showing an example of the functional configuration of the editing support method of the present invention, FIG. 2 is a block diagram showing an example of the hardware configuration of a system that implements the editing support method of the present invention, and FIG. Flowcharts showing the processing procedure of the first embodiment of the invention, FIG. 4, FIG. 7, FIG. 9, FIG. 11, and FIG. 14 are diagrams showing screen examples related to the first embodiment, and FIG. , Fig. 6, Fig. 8
10 and 13 are diagrams showing an example of a data dictionary related to the first embodiment, FIG. 12 is a diagram showing an example of hierarchical levels of software specifications, and FIG. 15 is a diagram showing an example of the hierarchical level of software specifications. FIGS. 16 and 17 are flowcharts showing the processing procedure of the second embodiment, and FIGS.
FIG. 8 is a diagram showing an example of a data dictionary regarding the second embodiment,
FIG. 19 is a flowchart showing the processing procedure of the third embodiment of the present invention, FIG. 20 is a diagram showing an example of a screen related to the third embodiment, and FIG. 21 is a flowchart showing the processing procedure of the third embodiment of the present invention. 22 is a diagram showing an example of a screen related to the fourth embodiment, FIG. 23 is a flowchart showing the processing procedure of the fifth embodiment of the present invention, and FIG. 24 is a flowchart showing the processing procedure of the fifth embodiment of the present invention.
FIG. 25 is a diagram showing an example of a screen related to the fifth embodiment. FIG. 26 is a diagram showing an example of a data dictionary related to the sixth embodiment of the present invention. , FIG. 27 is a block diagram showing an example of the functional configuration of a system according to the seventh embodiment of the present invention, FIG. 28 is a flowchart showing the processing procedure of the seventh embodiment of the present invention, and FIG.
30 is a diagram showing an example of the contents of a data dictionary related to the seventh embodiment, FIG. 30 is a diagram showing an example of a display output by the seventh embodiment, and FIG. 31 is a diagram showing an example of the display outputted from the seventh embodiment. FIG. 3 shows a hierarchical information table regarding the seventh embodiment.
FIG. 2 is a flowchart showing the processing procedure of the eighth embodiment of the present invention, FIG. 33 is a diagram showing an example of a data dictionary regarding the eighth embodiment, and FIG. 34 is a flowchart showing the processing procedure of the eighth embodiment of the present invention. FIG. 35 is a flowchart showing a processing procedure regarding the ninth embodiment, and FIG. 36 is a diagram showing an example of a data dictionary related to
FIG. 37 is a diagram showing an example of a screen related to the embodiment of FIG.
A diagram showing an example of a data dictionary related to the tenth embodiment of the present invention, FIG. 38 is a flowchart showing a processing procedure related to the tenth embodiment, FIG. 39 is a diagram showing an example of a screen related to the tenth embodiment, FIG. 40 and FIG. 4V are diagrams showing examples of software specifications, and FIG. 42 is a diagram showing an example of a data dictionary. 101... Input information analysis unit, 102... Edit area data name acquisition unit, 103... Dictionary data name acquisition unit, 104... Additional information acquisition unit, 105... Additional information update unit, 106... Data dictionary, 107... Data name transfer section, 108... Editing section, 109... Display order determining section, 110... Data name display section. Fig. 1 Fig. 2 Fig. J Fig. 5 Fig. fig. Figure 13 Figure Figure Figure Figure 7'7 Hizuzan 1) Ku: 2, Rinobu'! Kuya 1 Figure 18 Takumekoma 1 Kuchikoma 2θ Ward Order Processing / 303 ¥122 Kuchiko; Residence Residence To) Be 1 for 1 Gne Fee, Store Sa'' Bi/) Circulation Zuko 1 Figure 24-Figure 26 Rattan Figure 29 Figure Figure 33 Figure 34 Figure 37 Figure 3/. Easy 3g diagram 3rd? Figure 42

Claims (1)

[Claims] 1. In an information processing device having a processing device, an input device, a display device, and a memory device, when editing a software product, information registered in a data dictionary in the memory device An editing support method that displays a plurality of data names on the display device and writes the data name selected on the screen of the display device in the editing area of the display device, the method comprising: A first step that determines data names to be displayed on the display device during editing and the display order of the data names, based on additional information of a data dictionary that stores pairs of additional information corresponding to the data names in the memory device. a second step of displaying the data names on the display device in the determined order; and selecting a desired data name from the displayed data names and writing it in the editing area. An editing support method comprising a third step. 2. The editing support method according to claim 1, further comprising a fourth step of updating additional information in the data dictionary for the data name when the editing operation is performed on the data name in the software product. 3. Claim comprising: a fifth step of registering a data name input from the input device in a data dictionary of the memory device; and a sixth step of storing additional information for the data name in pairs in the memory device. Editing support method described. 4. The editing support method according to claim 1, further comprising a seventh step of prohibiting input of data names not registered in the data dictionary from the input device when editing the software product. 5. The second step is a step of specifying the display position of the data name when displaying the data name in the data dictionary registered in the data dictionary, and displaying the data name in the data dictionary based on the specification. 2. The editing support method according to claim 1, comprising the step of: 6. The editing support method according to claim 1, further comprising an eighth step of lexically analyzing the data name from the input device, dividing it into constituent words, and registering the words in a data dictionary. 7. The editing support method according to claim 1, wherein the software product comprises a software specification or a program. 8. The above additional information includes the access time of the above data name,
7. The editing support method according to claim 1, wherein the information includes access frequency, type, hierarchical level of the software product in which the data name exists, or a combination thereof. 9. In an information processing device having a processing device and a dialogue terminal, when editing a software specification, multiple data names registered in the data dictionary are displayed, and the data name selected on the display screen is displayed in the editing area. The computer inputs the hierarchical structure of the software specification to be edited from a data dictionary in which the data name and the hierarchical level of the software specification in which the data name exists are stored in correspondence with each other. and a second step of displaying on the screen of the terminal the data name in the software specification that is the "parent" in the hierarchical structure of the software specification. 10. A memory device that stores a data name in a software product and additional information corresponding to the data name in pairs as a data dictionary; and a display device that displays the software product and the data name in the data dictionary. , an input device for selecting and inputting a desired data name from among the data names displayed on the display device; and an input device for selecting and inputting a desired data name from among the data names displayed on the display device, and displaying the data name on the display device based on additional information of the data dictionary when editing the software product. An editing support device comprising a data name and a processing device that determines and displays the data name in a display order and writes the data name selected by the input device in an editing area of the display device. 11. Claim 10, wherein the processing device includes means for updating the additional information for the data name when an editing operation is performed on the data name in the software product.
Editing support device described.