JP3886726B2 - PROGRAM SPECIFICATION CREATION DEVICE, PROGRAM SPECIFICATION CREATION METHOD, AND RECORDING MEDIUM CONTAINING PROGRAM SPECIFICATION CREATION PROGRAM - Google Patents

Description

  The present invention relates to a technique for creating a program specification from comments inserted in a source program in the field of reengineering and reverse engineering, and more particularly to a technique for improving the efficiency of creating a program specification.

  Conventionally, a comment describing the processing contents of a program is generally inserted into a source program. There are comments about files and comments about symbols. Here, “symbol” means, for example, an element that has one characteristic in common, such as a class, a member function, an external variable, etc., when the source program is written in C ++ language. An aggregate of In general, a comment regarding a file is inserted at the beginning of the file, and a comment regarding a symbol is inserted immediately before the symbol.

  Therefore, at the beginning of the file, the comment about the file and the comment about the symbol are adjacent to each other, and there are the following problems. That is, each comment includes a comment item (hereinafter referred to as “item”) corresponding to the program specification. For this reason, when the same item is included in each comment, it is difficult to determine which comment the item belongs to, and the item cannot be extracted or is extracted redundantly. Due to such problems, even if an attempt was made to create a program specification based on the extracted items, the items could not be used as they were, and manual correction work was indispensable.

  Therefore, in view of the conventional problems, the present invention aims to clarify the comment to which each item belongs, thereby improving the item extraction accuracy and improving the efficiency of creating the program specification.

To achieve the above object, as a first means, for each source program, a separator for identifying various comments inserted in the source program is set through a graphical user interface , and the separator setting means is used to set the separator. For each separator, the keyword setting means for setting the extracted keyword of the comment item corresponding to the program specification via the graphical user interface, and each comment of the source program based on the separator set by the separator setting means Comment range extracting means for extracting a range of comments, and for each comment range extracted by the comment range extracting means, a comment item is extracted from the source program based on the extracted keyword set by the keyword setting means. And a comment specification extraction unit configured to generate a program specification based on the comment item extracted by the comment item extraction unit. To do.

According to such a configuration, a program specification can be efficiently created from comments inserted in the source program as follows. That is, as an operation for describing the source program, a separator for identifying the comment type is inserted into the source program. When the separator specification unit sets the separator via the graphical user interface when creating the program specification, the range of each comment is extracted based on the set separator. On the other hand, for each extracted comment range, a comment item is extracted from the source program based on the extracted keyword set by the keyword setting means through the graphical user interface . Then, a program specification is generated based on the extracted comment item.

  At this time, even if comments of different types are adjacent to each other at the beginning of the file, each comment range is accurately and reliably identified by the separator for identifying both. Accordingly, it is possible to prevent the comment item from being extracted or the comment item from being extracted twice as in the conventional case, and the program specification can be created by using the extracted comment item as it is. . Accordingly, the accuracy of extracting comment items can be improved, and the efficiency of creating a program specification can be improved.

The separator may be configured to identify the start line and end line of various comments.
According to this configuration, the start line and the end line of various comments are reliably identified by the separator. For this reason, the extraction accuracy of the comment range is improved, and the creation efficiency of the program specification can be further improved.

Further, the separator setting means may be configured to set at least a separator for identifying a comment relating to a file and a comment relating to a symbol.
With this configuration, it is possible to reliably identify adjacent comments at the beginning of the file. That is, generally, a comment related to a file and a comment related to a symbol are inserted adjacent to each other at the beginning of the file. For this reason, if at least a separator for identifying both is set, the extraction of the comment range at the beginning of the file can be reliably performed.

In addition to this, the comment range extraction unit may extract a comment range based on a separator or an executable statement of another comment for a comment for which no separator is set by the separator setting unit. Good. Further, the comment range extracting unit inserts between two comments when two comments are inserted adjacent to each other at the beginning of the file and no separator is set by the separator setting unit. A range of comments may be extracted based on the sentence.
According to such a configuration, various comment description methods can be supported.

In addition, the comment item extraction unit may extract a comment item from which a comment identifier corresponding to a program language describing a source program is removed.
According to such a configuration, an unnecessary comment identifier is removed when generating a program specification, so that an easy-to-read program specification can be created.

As a second means, for each source program, a separator setting step for setting various types of comments inserted in the source program via a graphical user interface, and for each separator set by the separator setting step, A keyword setting step for setting a comment item extraction keyword corresponding to the program specification via a graphical user interface, and a comment for extracting a range of each comment of the source program based on the separator set by the separator setting step A comment item extraction for extracting a comment item from the source program based on the extracted keyword set by the keyword setting step for each range of the comment extracted by the range extracting step and the comment range extracting step. A step, on the basis of the comment items extracted by the comment item extraction process, a program specification generation step of generating a program specifications, characterized in that the configured program specification creation process to be executed by a computer.

According to such a configuration, a program specification can be efficiently created from comments inserted in the source program as follows. That is, as an operation for describing the source program, a separator for identifying the comment type is inserted into the source program. Then, when creating a program specification, if a separator is set via a graphical user interface in the separator setting step, the range of each comment is extracted based on the set separator. On the other hand, for each extracted comment range, a comment item is extracted from the source program based on the extracted keyword set through the graphical user interface by the keyword setting step. Then, a program specification is generated based on the extracted comment item.

  At this time, even if comments of different types are adjacent to each other at the beginning of the file, each comment range is accurately and reliably identified by the separator for identifying both. Accordingly, it is possible to prevent the comment item from being extracted or the comment item from being extracted twice as in the conventional case, and the program specification can be created by using the extracted comment item as it is. . Accordingly, the accuracy of extracting comment items can be improved, and the efficiency of creating a program specification can be improved.

As a third means, for each source program, a separator setting function for setting various types of comments inserted in the source program via a graphical user interface, and for each separator set by the separator setting function, A keyword setting function for setting a keyword for extracting a comment item corresponding to the program specification via a graphical user interface, and a comment for extracting a range of each comment of the source program based on the separator set by the separator setting function A comment item extraction that extracts a comment item from the source program based on the extracted keyword set by the keyword setting function for each comment range extracted by the range extracting function and the comment range extracting function. Features and, on the basis of the comment items extracted by the comment entry extractor, program specifications computer-readable recording medium a program specification generation program for implementing a program specification generation function of generating, to computer Recorded.

  Here, the “recording medium” refers to a medium that can reliably record various kinds of information and can be reliably removed as necessary, such as a magnetic tape, a magnetic disk, a magnetic drum, an IC card, and a CD-ROM. This applies to portable recording media.

  According to this configuration, the program specification creation program for realizing the separator setting function, the keyword setting function, the comment range extraction function, the comment item extraction function, and the program specification generation function is recorded on the recording medium. Therefore, if there is such a recording medium, the program specification creation device according to the present invention can be easily constructed using a general electronic computer.

  In order to describe the present invention in more detail, it will be described with reference to the accompanying drawings.

  2 to 5 show an example of a source program to be processed by a program specification creation device (hereinafter referred to as “specification creation device”) according to the present invention. These source programs are described in the C ++ language as a programming language, and the comments are a part starting with “/ *” and ending with “* /”, and a part after “//” in each line. The numbers attached to the beginning of each line in the source program represent the program line number.

  The configuration of the source program shown in FIG. 2 will be described as follows. That is, the first to sixth lines are comments regarding the file, the seventh to sixteenth lines are comments regarding the class (symbol), and the 17th and subsequent lines are class definition statements. In addition, a separator indicating the start and end of a comment is provided for each comment relating to a file and each comment relating to a class. In the comments regarding the file, “*******” included in the first and sixth comment lines functions as a separator, and in the comments regarding the class, the seventh and sixteenth lines "------------" included in the comment line of "" functions as a separator.

  In addition, the source program shown in FIG. 3 is an example in which no separator is provided for comments related to classes. The source program shown in FIG. 4 is an example in which no comment is provided for comments relating to files and classes, and an executable statement “#include <stdio.h>” that functions as a separator is inserted between the comments. The source program shown in FIG. 5 is an example in which there is no comment regarding the class.

FIG. 1 shows the overall configuration of the specification creation apparatus.
The specification creation device includes a display device 10, an input device 20, an external storage device 30, a calculation device 40, and a printing device 60. The display device 10 is configured by a display such as a CRT or LCD, and provides a GUI (Graphical User Interface) function for a user. The input device 20 includes a keyboard and a pointing device such as a mouse, and provides a data input function for the GUI. The external storage device 30 is configured by a hard disk or the like, and provides a source program storage function. The arithmetic device 40 is configured to include at least a central processing unit (CPU) and a memory, and controls the entire specification creation device by a program loaded in the memory. The printing device 60 is configured by a printer or the like, and provides a printing function for the created program specifications.

  In addition, an extraction keyword setting unit 42, a comment range extraction unit 44, a comment item extraction unit 46, a specification generation unit 48, and a specification printing unit 50 are mounted on the arithmetic device 40 by a program.

  In the extraction keyword setting unit 42, a GUI is provided in cooperation with the display device 10 and the input device 20, and an extraction keyword corresponding to the type of comment is set. Here, the “comment type” refers to an identifier such as a comment about a file or a comment about a class when the source program is described in C ++ language. The extracted keyword setting unit 42 functions as a separator setting means, a separator setting process, a separator setting function, a keyword setting means, a keyword setting process, and a keyword setting function.

  The comment range extraction unit 44 reads the source program file 32 from the external storage device 30 and extracts the extraction range of comments over the entire file based on the set extraction keyword. If the source program shown in FIG. 2 is described as an example, the first to sixth lines are extracted as the comment range regarding the file, and the seventh to sixteenth lines are extracted as the comment range regarding the class. Needless to say, the range of comments to be extracted includes not only the head portion of the file but also subsequent comments. The comment range extraction unit 44 functions as a comment range extraction means, a comment range extraction step, and a comment range extraction function.

  In the comment item extraction unit 46, comment items included in each comment are extracted based on the set extraction keyword. For example, the comment on the source program file shown in FIG. 2 is described as follows: “1. Summary” based on the extracted keyword “Car class declaration”, “2. Creator” based on the extracted keyword “Koji Sasaki” Is extracted. The comment item extracting unit 46 functions as a comment item extracting means, a comment item extracting step, and a comment item extracting function.

The specification generation unit 48 generates a program specification as shown in FIG. 6 based on the extracted comment item. The specification generation unit 48 functions as a program specification generation unit, a program specification generation process, and a program specification generation function.
In the specification printing unit 50, the generated program specification data is transmitted to the printing device 60, and the printing device 60 prints the program specification.

Next, the operation of the specification creation apparatus having such a configuration will be described.
FIG. 7 shows a flowchart of a procedure for creating a program specification.
In step 1 (abbreviated as “S1” in the figure, the same applies hereinafter), an extraction keyword for extracting a comment from the source program is set. That is, when the “extract keyword setting” command is executed, the extraction keyword setting unit 42 is selectively activated, and an extraction keyword setting screen (hereinafter referred to as “setting screen”) 100 as shown in FIGS. 8 and 9 is displayed. Is done. On the setting screen 100, an extraction keyword is set for each comment type. The extracted keyword includes separator information indicating the start and end of a comment and specification information associated with the program specification.

  As a procedure for setting an extraction keyword, first, a comment type is selected from the type selection unit 102. Then, by appropriately operating the add button 104, the delete button 106, and the change button 108, an extraction keyword related to the separator and the comment item is input. In addition, when continuously setting extracted keywords related to other comment types, it is only necessary to select another comment type from the type selection unit 102 and repeat the same operation. When the input of the extraction keyword is completed, the extraction keyword is determined by operating the OK button 110. On the other hand, if it is desired to cancel the setting of the extracted keyword, the extracted keyword returns to the previous state by pressing the cancel button 112 at an arbitrary time.

In FIG. 8, separator information “*******” and specification information “1. overview” and “2. creator” are set as extraction keywords related to file information. Is shown (the same applies to FIG. 9). As a result, extraction keywords as shown in FIG. 10 are set.
In step 2, a comment is extracted from the source program for each comment type. That is, when the “extract comment” command is executed, the comment range extraction unit 44 and the comment item extraction unit 46 are selectively activated, and comments are extracted according to the flowcharts of FIGS.

  In step 3, a program specification as shown in FIG. 6 is generated based on the extracted comment. That is, when the “create program specification” command is executed, the specification generation unit 48 is selectively activated, and a program specification is generated by the function.

In step 4, the generated program specification is output from the printing device 60. That is, when the “print program specification” command is executed, the specification printing unit 50 is selectively activated and the printing device 60 prints the program specification.
In the above procedure, the creation and printing of the program specification can be arbitrarily selected. However, for example, when a comment is extracted, the program specification may be automatically printed.

FIG. 11 shows a main routine of processing for extracting a comment from the source program.
In step 10, the source program file 32 is read from the external storage device 30, and symbol information in the source program is extracted. Here, “symbol information” refers to line information and symbol type information of a symbol definition sentence. Taking the source program shown in FIG. 2 as an example, since there is a class definition statement on the 17th line, the line information is “17th line” and the type information is “class”. Note that the extracted symbol information is held in ascending order using, for example, line information as a key.

In step 11, a subroutine for extracting comments regarding the file is called. The extracted comments are held in a table format using, for example, comment types and comment items for specifications as keys (the same applies hereinafter).
In step 12, the next symbol information is read. That is, the first symbol information is read in the first process, and the second, third,... Symbol information is read in the subsequent processes.

In step 13, a subroutine for extracting a comment regarding the symbol is called using the symbol information as a parameter.
In step 14, it is determined whether or not the extraction of the comment regarding the symbol has been performed up to the end of the source program file 32, that is, whether or not the extraction of the comment has been completed. If the comment extraction is completed, the process is terminated (Yes). If the comment extraction is not completed, the process returns to Step 12 (No).

FIG. 12 shows a subroutine called in step 11, that is, a subroutine for extracting a comment relating to a file.
In step 20, a subroutine for obtaining the extraction range of the comment regarding the file is called.
In step 21, a subroutine for extracting a comment item corresponding to the program specification from the comment extraction range obtained in step 20 is called.

FIG. 13 shows a subroutine called in step 13, that is, a subroutine for extracting a comment related to the symbol.
In step 30, a subroutine for obtaining a comment extraction range for the symbol is called.
In step 31, a subroutine for extracting a comment item corresponding to the program specification from the comment extraction range obtained in step 30 is called. The subroutine called here is the same as the subroutine called in the previous step 21.

FIG. 14 shows a subroutine called in step 20, that is, a subroutine for obtaining a comment extraction range for a file.
In step 40, the contents of the first line of the source program are fetched.
In step 41, it is determined whether or not the content of the first line taken out is an executable statement. Here, the “executed statement” means a statement other than a comment line. For example, when the source program is written in the C ++ language, a preprocessor processing target statement such as a “#define” statement, a variable definition statement, This applies to class definition statements. If the content of the first line is an executable statement, it is determined that there is no comment about the file in the source program, and the process proceeds to step 47 (Yes). On the other hand, if the content of the first line is not an executable statement (ie, a comment line), the process proceeds to step 42 (No).

  In step 42, it is determined whether or not the content of the first line is a symbol separator. Here, the symbol separator is based on the one set on the extraction keyword setting screen 100 shown in FIG. 9 (the same applies hereinafter). If it is a symbol separator, it can be determined that the first line of the source program is a comment related to the symbol, so that it is determined that there is no comment related to the file, and the process proceeds to step 47 (Yes). On the other hand, if it is not a symbol separator, it is determined that the comment is a start line for the file, and the process proceeds to step 43 (No).

In step 43, the contents of the next line (hereinafter referred to as “line contents”) are retrieved.
In step 44, it is determined whether or not the line content is an executable statement. If the line content is an executable statement, it is in a format without a separator indicating the end of the comment on the file (see the source program in FIG. 4), and it is determined that the comment on the file has ended on the previous line. Proceed (Yes). On the other hand, if the line content is not an executable statement, it is determined that comments regarding the file continue, and the process proceeds to step 45 (No).

  In step 45, it is determined whether or not the line content is a file separator. If it is a file separator, it is determined that it is the end line of a comment relating to the file, and the process proceeds to step 47 (Yes). On the other hand, if it is not a file separator, it is determined that comments relating to the file continue, and the process proceeds to step 46 (No).

  In step 46, it is determined whether the line content is a symbol separator. If it is a symbol separator, it is determined that the comment on the file has been completed in the previous line, and the process proceeds to step 47 (Yes). On the other hand, if it is not a symbol separator, it is determined that comments relating to the file continue, and the process returns to step 43 (No). Here, such a determination is made in consideration of, for example, a case where there is no separator indicating the end of a comment related to a file.

  In step 47, the extraction range of the comment regarding the file is calculated. When it is determined in step 41 or step 42 that there is no comment related to the file, information indicating that there is no comment line related to the file, for example, “0” is set in the start line and the end line.

FIG. 15 shows a subroutine called in step 30, that is, a subroutine for obtaining a comment extraction range regarding symbols.
In step 50, the contents one line before the symbol definition line are fetched. Here, the symbol definition line is specified based on the content of the parameter (symbol information) when the subroutine related to the symbol (see FIG. 13) is called in step 13. For example, in the case of the source program of FIG. 2, since the definition statement of the symbol (class) is on the 17th line, the contents on the 16th line are extracted.

  In step 51, it is determined whether or not the content one line before the symbol definition line is an executable statement. If the content one line before the symbol definition statement is an executable statement, it is determined that there is no comment related to the symbol, and the process proceeds to step 56 (Yes). On the other hand, if the content one line before the symbol definition statement is not an execution statement, the process proceeds to step 52 (No). As shown in FIG. 5, when the comment immediately before the symbol definition sentence is a comment of a file, it is desirable to refer to the extraction range of the comment related to the file so as not to extract the overlapping range.

  In step 52, it is determined whether or not the content of the symbol definition sentence one line before is another separator, that is, a separator of a file and another symbol. If it is another separator, it is determined that there is no comment regarding the symbol, and the process proceeds to step 56 (Yes). On the other hand, if it is not another separator, it is determined that it is the end line of the comment related to the symbol, and the process proceeds to step 53 (No).

In step 53, the contents of the previous line are retrieved. That is, the file analysis is performed toward the beginning of the file, and the start line of the comment related to the symbol is searched.
In step 54, it is determined whether or not the line content is an executable statement. If the line content is an executable statement, it is determined that there is no separator indicating the start of a comment regarding the symbol (see the source program in FIG. 3), and the comment regarding the symbol starts from the next line. Proceed (Yes). On the other hand, if the line content is not an executable statement, it is determined that a comment regarding the symbol is continued, and the process proceeds to step 55 (No).

  In step 55, it is determined whether or not the line content is another separator. If the line content is another separator, it is determined that there is no separator indicating the start of a comment regarding the symbol (see the source program in FIG. 3), and the comment regarding the symbol starts from the next line. Proceed to (Yes). On the other hand, if the line content is not another separator, it is determined that the comment regarding the symbol is continued, and the process returns to step 53 (No).

  In step 56, a comment extraction range for the file is calculated. If it is determined in step 51 or step 52 that there is no comment regarding the file, the same information as in step 47 is set.

FIG. 16 shows a subroutine called in step 21 and step 31, that is, a subroutine for extracting comment items necessary for the program specification.
In step 60, the contents of the first line of the comment line relating to the file or symbol are retrieved. Here, the content to be extracted is a comment identifier representing a comment line, for example, “***” except “/ *” and “* /” in the comment relating to the source program file shown in FIG. “***” is taken out.

In step 61, it is determined whether or not the content of the comment line is specification information. If it is the specification information, the process proceeds to step 62 (Yes), and if it is not the specification information, the process proceeds to step 64 (No).
In step 62, the element number, pointer, etc. of the array for storing the comment items according to the specification information are changed.

  In step 63, it is determined whether or not the next line is the comment item extraction range. If it is the comment item extraction range, the process returns to step 60 (Yes), and if it is not the comment item extraction range, the process is terminated (No).

  In step 64, it is determined whether or not the comment item storage destination has been set. That is, it is determined whether or not the storage destination has been changed (set) in the process of step 62. In order to make such a determination, if the storage destination is not set, “NULL” may be set as the storage destination. If the storage destination has been set, the process proceeds to step 65 (Yes), and if the storage destination has not been set, the process proceeds to step 63 (No). Here, an example of the case where the storage destination is not set is when the first comment line is being processed and the line is a separator.

In step 65, the comment item is stored in a predetermined storage location.
According to the processing described above, in order to efficiently create a program specification from comments inserted in a source program, a separator for identifying a comment type is inserted when the source program is described. When the inserted separator information is set when creating the program specification, the range of each comment is extracted based on the separator information. At this time, even if a comment related to the file and a comment related to the symbol are adjacent to each other at the beginning of the file, the range is accurately and reliably identified by the separator for identifying both. Thereafter, in the extracted range, each comment item corresponding to each comment is extracted, and a program specification is generated.

  Therefore, it is possible to prevent the comment types from being confused at the head of the file, and to create a program specification using the extracted comment items as they are. For this reason, the efficiency of creating the program specification is greatly improved, and for example, the program development period can be shortened and the development cost can be reduced.

  In the specification creating apparatus described above, the source program written in the C ++ language is the processing target, but other program languages, for example, RASIC, COBOL, FORTRAN, Java, etc. may be the processing target. .

  If a program for realizing such a function is recorded on a recording medium such as a magnetic tape, a magnetic disk, a magnetic drum, an IC card, or a CD-ROM, the program for creating a program specification according to the present invention is put on the market. It can be distributed. And the person who acquired such a recording medium can construct | assemble the program specification preparation apparatus based on this invention easily using a general electronic computer, for example.

  As described above, the program specification creation device and the program specification creation method according to the present invention are extremely useful because the accuracy of extracting comment items is improved. Further, the recording medium on which the program specification creation program according to the present invention is recorded is extremely useful because a program specification creation device can be easily constructed using a general electronic computer.

It is a whole block diagram of the specification preparation apparatus which concerns on this invention. It is a figure which shows the 1st example of the source program used as a process target. It is a figure which shows the 2nd example of the source program used as a process target. It is a figure which shows the 3rd example of the source program used as a process target. It is a figure which shows the 4th example of the source program used as a process target. It is a figure which shows an example of the program specification produced | generated. It is a flowchart which shows the flow of a specification preparation procedure. It is a figure which shows an example of the setting screen of an extraction keyword. It is a figure which shows an example of the setting screen of an extraction keyword. A set extraction keyword is shown, (A) shows comment information about a file, and (B) shows comment information about a class. It is a flowchart of the main routine which extracts a comment. It is a flowchart of the subroutine which extracts the comment regarding a file. It is a flowchart of the subroutine which extracts the comment regarding a symbol. It is a flowchart of the subroutine which calculates | requires the extraction range of the comment regarding a file. It is a flowchart of the subroutine which calculates | requires the extraction range of the comment regarding a symbol. It is a flowchart of the subroutine which extracts the comment item required for a specification.

Claims (8)

Separator setting means for setting, via a graphical user interface, a separator for identifying various comments inserted in the source program for each source program ;
For each separator set by the separator setting means, keyword setting means for setting an extraction keyword for a comment item corresponding to the program specification via a graphical user interface ;
Comment range extracting means for extracting the range of each comment of the source program based on the separator set by the separator setting means;
Comment item extracting means for extracting a comment item from a source program based on the extracted keyword set by the keyword setting means for each comment range extracted by the comment range extracting means;
Program specification generating means for generating a program specification based on the comment item extracted by the comment item extracting means;
An apparatus for creating a program specification characterized by comprising   2. The program specification creation device according to claim 1, wherein the separator is configured to identify a start line and an end line of various comments. The separator setting means, at least, program specification creation device ranging first claim of claim is configured to set the separator identifies the comments on comments and symbols for files.   The comment range extraction unit is configured to extract a comment range based on a separator or an executable statement of another comment for a comment for which a separator is not set by the separator setting unit. Program specification creation device described in the section.   The comment range extracting means inserts an executable statement inserted between the two comments when two comments are inserted adjacent to each other at the beginning of the file and no separator is set by the separator setting means. The program specification creation device according to claim 1, which is configured to extract a comment range based on the program.   2. The program specification creation device according to claim 1, wherein the comment item extraction unit is configured to extract a comment item from which a comment identifier corresponding to a program language describing a source program is removed. For each source program, a separator setting step for setting a separator for identifying various comments inserted in the source program via a graphical user interface ;
A keyword setting step for setting an extraction keyword of a comment item corresponding to the program specification via a graphical user interface for each separator set by the separator setting step;
Based on the separator set by the separator setting step, a comment range extraction step for extracting the range of each comment of the source program,
For each comment range extracted by the comment range extraction step, a comment item extraction step for extracting a comment item from the source program based on the extracted keyword set by the keyword setting step;
A program specification generation step for generating a program specification based on the comment item extracted by the comment item extraction step;
A program specification creating method characterized in that a computer is executed . For each source program, a separator setting function for setting a separator for identifying various comments inserted in the source program via a graphical user interface ;
A keyword setting function for setting an extraction keyword of a comment item corresponding to a program specification via a graphical user interface for each separator set by the separator setting step;
A comment range extracting function for extracting the range of each comment of the source program based on the separator set by the separator setting function;
For each comment range extracted by the comment range extraction function, a comment item extraction function for extracting a comment item from the source program based on the extracted keyword set by the keyword setting function;
A program specification generation function for generating a program specification based on the comment item extracted by the comment item extraction function;
The computer-readable recording medium which recorded the program specification preparation program for making a computer implement | achieve .

Images