JP3335851B2 - Software coding system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention uses a part file which is a set of source codes (hereinafter referred to as part source code) as parts of an existing program, and converts a source code of a new program from a design document file of the new program. The present invention relates to a software coding system that automatically generates codes.

[0002]

2. Description of the Related Art A conventional software coding system will be described with reference to FIG. In this figure, 80
Is a design information database, and the program designer 81
Thus, the design information of the new program is input. 82
Is an expert shell, and the design information database 8
0 and the knowledge database 8 for judgment in accordance with the design document file of the new program 0.
4 is used to infer whether the existing source code file 85 can be used for the new program. The knowledge database 83 stores design knowledge of the program designer. The judgment knowledge database 84 stores judgment criteria for determining whether an existing component source code can be used. The source code file 85 is a collection of source codes of an existing program. 86 is a monitor display.

In the above-described software coding system, the source code file 85 and the new program design information in the design information database 80 are determined by the inference operation of the expert shell 82 based on the knowledge database 84 for determination, and the necessary component source is determined. This is an expert system for reusing a program that extracts code from a source code file 85. If there is a mismatch in the source code search, an "unusable" message is output as an error output. Error occurrence position information indicating which part cannot use the existing source code is not output (Japanese Unexamined Patent Application Publication No. 2-25721).
6), it is not possible to cope with the part where the error has occurred, and there is a disadvantage that the productivity of program creation deteriorates.

A program design specification library, a program library in which existing software assets are stored in a database, a keyword dictionary for storing related information such as system names, and a knowledge database 83 which is the knowledge and know-how of a skilled developer are provided. A consultation system (refer to Japanese Patent Laid-Open No. 5-134855) that manages the generation and update of a program by the expert shell 82 according to the production rules of THEN- Requires a knowledge database for judgment 84 for selecting a source code of an existing source code file 85 that can be used by the user, and a problem that requires maintenance for maintaining and updating this database. There was a title.

[0005]

SUMMARY OF THE INVENTION The present invention has been made in view of such a background, and an object of the present invention is to provide a software coding system in which productivity of program development is improved and maintenance is not required.

[0006]

According to the first aspect of the present invention,
A software coding system in which a computer creates source files for a new program using source codes of an existing program stored in a storage device, based on the configuration requirements of the new program and the design document file specified or specified. And extracting means for extracting search information of a source code used for the new program from the new program design file, and using the search information extracted by the extracting means for a new program from a source code file of the existing program. Searching means for searching for the source code, output means for outputting mismatch information for the source code when the source code corresponding to the search information is not searched by the searching means, and searching for the source code Place
In this case, using this source code,
Program generating means for creating a file .

According to a second aspect of the present invention, in the software coding system according to the first aspect, the search information is a character string. According to a third aspect of the present invention, in the software coding system according to the first aspect, the source code mismatch information can specify the source code, and indicates a character string line having the search information. According to a fourth aspect of the present invention, in the software coding system according to the first aspect, the existing program program is supplied to the software coding system simultaneously with the design document file.

[0008]

DETAILED 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 showing a configuration of a software coding system according to an embodiment of the present invention. In this figure, reference numeral 1 denotes input information, which has new program design information, and is composed of a key information file 2, a header file 3, an existing source 4, and design document files 5a to 5c.

The key information file 2 defines key information as a character string definition for identifying each function in the design document files 5a to 5c and identification character information in the component source code. The header file 3 is an aggregate of the definition definition having a character string to be converted as a comment. The existing source file 4 is a past software property and supplies component source code to a new program. The design document files 5a to 5c have design information of a new program.

Reference numeral 7 denotes a source code generation unit, which comprises an input control unit 8, an output control unit 9, and a component control unit 10. The key code is a character string defined in the key information file 2. Design document file 5a ~
5c are sequentially identified, the corresponding part file 12 in the temporary file 11 in the storage device is extracted, and the design document file 5a is extracted.
5c, the generated source code 14 is output as the output information 13 in the order recognized, and a new program is created based on the input information 1.

The input control unit 8 includes a design file input unit 15
And a key information control unit 16, and the input information 1
Input control. The design file input unit 15 reads a design file from the design document files 5a, 5b and 5c. The key information control unit 16 controls key information for each function of the design file read by the design file input unit 15.

The output control unit 9 includes a source code output unit 17
And an error information output unit 18 for controlling output information of the created program. The source code output unit 17 outputs the component source code acquired corresponding to the new program. The error information output unit 18 outputs error information 19 when the search of the component source code based on the key information is not applicable and does not match.

The component control unit 10 has a component acquisition unit 20 and writes the component file 12 to the temporary file 11. The component acquisition unit 20 identifies a component source code from the existing source file 4 and creates the component file 12.

Next, the operation of the above embodiment will be described with reference to FIG. 1 and the flowchart of FIG. FIG.
5 is a flowchart illustrating an operation outline of the source code file automatic generation system. For example, it is assumed that in step S1, the input control unit 8 acquires the file names of the key information file 2, the header file 3, the existing source file 4, and the design document 5a, and makes them accessible. As a result, in step S2, the key information control unit 16 extracts key information from the design document file 5a.

Next, in step S3, based on the key information sequentially extracted from the design document file 5a,
The component obtaining unit 10 searches the component file 12 for a component source code corresponding to the described function, and outputs the source code to the temporary storage device. Then, the design document 5a which is a functional unit of the program
The source code output unit 17 generates the generated source code 1 based on
4 is output. Then, in step S4, the input control unit 8 acquires the next design document file name.

Next, in step S5, for example, assuming that the corresponding design document file is the design document file 5b, the process returns to step S1, and the operations in steps S1 to S5 are repeated. Also,
In step S5, for example, if there is no corresponding design document file, the design operation of the program ends.

Next, referring to FIG. 1, the operation of step S2 of the design document conversion process will be described in detail with reference to FIG. First, in step S11, for example, when the design file input unit 15 reads the head line of the design document file 5a, in step S12, the key information control unit 16 converts the read line information into the component of the key information file 2. The type of key information is identified based on the key and control key information.

For example, assuming that the key information is a component key, a component key process is executed by the key information control unit 16 in step S13. This processing will be described later in detail. For example, assuming that the key is a control key, a control key process is executed by the key information control unit 16 in step S14. This processing will be described later in detail. Further, in the case of the header at the top of the page, the page information processing is executed by the key information control unit 16 in step S15. In other cases, a comment process is executed by the key information control unit 16 in step S16.

After the processing of the corresponding line is completed,
In step S17, the input control unit 8 reads the next line of the design document file 5a. For example, this line indicates "EOF" indicating the end of the file.
If not, steps S11 to S17 are repeated. For example, if the read line is "E
If "OFF", the design document file conversion process in step S2 (see FIG. 2) ends.

Next, step S13 in FIG. 3 for performing the component key process will be described in detail with reference to FIG. 1 and the flowchart of FIG. First, in step S21, a line having component key information of the design document file 5a is recognized, and position information of the line is stored in the temporary storage device. Next, in step S22, the character string of the line whose component key information is recognized is
6, each component is decomposed into an element indicating a component key, and a component key for searching for a component source code from the component file 12 is extracted.

Next, in step S23, a component source code is searched from the component file 12 by the extracted component key, and the obtained component source code is stored in the temporary storage device by the component control unit 10. At this time, in step S24, the component acquisition unit 20 checks whether the component source code corresponding to the component key exists in the component file 12. For example, assuming that a component source code corresponding to the component key is detected, in step S25, after reading the next line of the design document file 5a by the input control unit 8, the component key processing in step S14 ends.

If the component source code corresponding to the component key is not detected by the component acquisition unit 20 from the component file 12, for example, in step S26, the design is performed based on the line position information stored in step S21. The error occurrence function of the document file 5a is output as error information by the error information output unit 18, and the component key processing in step S14 ends.

Next, the key information file 2 in FIG. 1 used in one embodiment will be described with reference to FIG. FIG.
Is an example of the key information file 2 in the configuration diagram of the source code file automatic generation system in FIG. In this figure, numeral 40 indicates the format of the key information file. Reference numeral 41 denotes a text data area, and a part key indicating replacement with a part source code in this area is defined by “•”.

Next, the component file 12 in FIG. 1 used in one embodiment will be described with reference to FIG. FIG.
FIG. 2 is an example of a component file 12 composed of component source codes recognized from an existing source file 4 in the configuration diagram of the source code file automatic generation system in FIG. 1.
Reference numeral 50 denotes an example of the component file 12, which is composed of areas 51 and 52. In the areas 51 and 52, component source codes recognized in the existing source file 4 (see FIG. 1) are shown.

FIG. 7 shows the structure of the design document files 5a, 5b and 5c in FIG. 1 used in one embodiment. These files are design materials for creating a new program in the automatic source code file generation system, and component keys corresponding to necessary component source codes are extracted.

FIG. 9 shows the output information 13 of FIG. 1, which is an example of a source code file 14 of a new program generated according to one embodiment. In this figure, 40 indicates the format of this file. Reference numerals 71 and 72 denote text areas in which comments on the functions of the used component source code are shown.

Next, the operation of the embodiment will be described with reference to FIGS. 5, 6, 7, 8 and 9, and according to FIG. In step S1, the input control unit 8 acquires the file names of the key information file, the component file of FIG. 6, and the design document file of FIG. 7, and converts the acquired document file into a text file that allows character search. Then, in step S2, the key information control unit 16
A character search for the part key is performed in the design document file of FIG. 7, and “VP path connection setting” shown in the area 57 and “VP” shown in the area 58 in the design document file of FIG. The path connection status lead is extracted.

Next, component source codes corresponding to these functions are retrieved from the component file shown in FIG.
Are stored in the temporary storage device. Then, in step S3, when the processing for the design document file per unit is completed by the output control unit 9, the generation source file shown in FIG. 9 is output. Then, in step S4, the input control unit 8
Reads the design document file name to be processed next. Then, in step S5, the design file input unit 15 checks whether or not the file exists. For example, if the corresponding file is confirmed in step S5, the processing of steps S1 to S5 is repeated.

Next, the operation of step S2 in FIG. 2 will be described with reference to FIGS. First,
In step S11, the input control unit 8 reads the text sentence in the area 57 which is the first line of the design document file in FIG. Next, in step S12, the key information control unit 16 uses the part key “•” shown in the area 41 of the key information file in FIG.
The part key “•” shown in the area 57 of the design document file in FIG. 8 is recognized.

Next, in step S12, the key information control unit 16 recognizes that the key information is a component key, and executes step S13. Then, in step S17, the input control unit 8 reads the next line of the design document file in FIG. 8, and if, for example, the read line is not “EOF”, step S1
Steps S1 to S17 are repeated, and the conversion process of the design document file is performed. If the read line is “EOF”, the processing of the design document file is terminated.

Next, the operation of step 13 in FIG. 3 will be described with reference to FIGS. 6, 7 and 8, and according to FIG.
First, in step 21, the key information control unit 16 stores the position information of the area 57 where the part key is recognized from the design document file in FIG. 8 in a line counter (not shown) but in a temporary storage device. Is done. Next, in step S22, the key information control unit 16 decomposes the character string of the design document file of FIG.
Decompose into the design document file format shown in

Then, the key information control unit 16 extracts the character string in the area 57 which is the component key information for searching the component source code. Next, in step S23, the component acquisition unit 20 is operated based on the component key extracted in step S22.
Acquires the component source code of the area 51 corresponding to the character string of the area 57 from the component file of FIG. 6, and stores it in the temporary storage device. At this time, in step S24, since the component source code corresponding to the component key information is confirmed by the component acquisition unit 20, the next line of the design document file in FIG. After that, the process ends. Also, for example, if the component source code is not confirmed in step S24, the error information output unit determines in step S26 the error occurrence function of the design document file based on the line position information stored in the line counter. Output as information.

[0033]

According to the first aspect of the present invention, a computer uses a source code of an existing program stored in a storage device based on a design document file in which the configuration requirements and specifications of the new program are indicated, and the computer is newly implemented. In a software coding system for creating a source file of a program, extracting means for extracting search information of a source code used for a new program from the new program design file, and extracting the existing program by using the search information extracted by the extracting means Searching means for searching the source code file used for a new program from the source code file, and outputting the mismatch information for the source code when the source code corresponding to the search information is not searched by the searching means. and means, said Sosuko If the soil is found, this source
Create source files for new programs using code
Since it is provided with a program generating means, it is clear whether any part of the source code of the existing program can be adapted to the new program, and the program development efficiency is improved.

According to a second aspect of the present invention, in the software coding system according to the first aspect, since the search information is a character string, the design document file and the source code of the existing program are all represented by character codes. Therefore, the design document file can be easily described, errors can be easily confirmed, and operability is improved. According to a third aspect of the present invention, in the software coding system according to the first aspect, the design document file is opened because the source code mismatch information can identify the source code and indicate a character string line having the search information. The line in which the error occurred can be clearly identified, and the operability of program development is improved. According to a fourth aspect of the present invention, in the software coding system according to the first aspect,
Since the existing program program is supplied to the software coding system at the same time as the design document file, there is no need for a database for the source code of the existing program, so that there is no need to maintain the software coding system.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a configuration of a software coding system according to an embodiment of the present invention.

FIG. 2 is a flowchart showing an outline of operation of a software coding system according to an embodiment of the present invention.

FIG. 3 is a flowchart showing a design document file conversion processing operation in the operation of the embodiment of the present invention.

FIG. 4 is a flowchart showing an operation of executing a component key process in the operation of the embodiment of the present invention.

FIG. 5 is a specific example of a key information file according to an embodiment of the present invention.

FIG. 6 is a specific example of a component file according to an embodiment of the present invention.

FIG. 7 is a specific example of a design document file according to an embodiment of the present invention.

FIG. 8 is a specific example of a design document file according to an embodiment of the present invention.

FIG. 9 is a specific example of a generated source code file according to an embodiment of the present invention.

FIG. 10 is a block diagram showing a configuration of a conventional software coding system.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Input information 2 Key information file 3 Header file 4 Existing source file 5a, 5b, 5c Design document file 7 Source code generation part 8 Input control part 9 Output control part 10 Parts control part 11 Temporary file 12 Parts file 13 Output information 14 Generation Source code 15 Design file input unit 16 Key information control unit 17 Source code output unit 18 Error information output unit 19 Error information 20 Parts acquisition unit 40 Key information file 41 Area 50 Parts file 51, 52 Area 57, 58 Area 70 Generation source file 71, 72 area 80 design information database 81 program designer 82 expert shell 83 knowledge database 84 judgment knowledge database 85 source code file 86 monitor display

Continuation of the front page (58) Field surveyed (Int.Cl. ⁷ , DB name) G06F 9/06 G06F 9/44

Claims (1)

(57) [Claims] 1. A software program for a computer to use a source code of an existing program stored in a storage device to create a source file of the new program based on a design document file in which the configuration requirements and specifications of the new program are specified. In the coding system, while extracting the search information of the source code used for the new program from the design document file ,
Position indicating the position in the design document file
Extracting means for storing information in a temporary storage device ; searching means for searching the source code file of the existing program for the source code to be used for a new program based on the search information extracted by the extracting means; If the source code corresponding to the search information is not found, the source code is written to the temporary storage device.
The design document file is stored based on the stored location information.
Output means for outputting an error occurrence function of a file as error information; and program generation means for creating a source file of a new program using the source code when the source code is searched. A software coding system characterized by the following.