JPH04242427A - Program designing system - Google Patents

Abstract

PURPOSE:To efficiently design a program by automatizing conversion between a source program and design information and the diagnosis of a design pattern. CONSTITUTION:This system is equipped with a term dictionary 1 wherein the correspondence between terms used in the design information and variable names in the program is rearranged as term information and stored in dictionary form, a program design information control part 5 which controls the source program 8 and the contents of the design information 7 which has design contents as the design pattern 13, a rule control part 6 which stores a converting method for representing the contents of the design information in detail or roughly in a rule base as a conversion rule, and an algorithm extracting process part 2 which converts the contents of the design information according to the conversion rule and generates the design information showing the process concept. Further, the system is equipped with the term dictionary 1, program design information control part 5, rule control part 6, algorithm detailing process part 3 which converts the contents of the design information showing the process concept according to the conversion rule and generates the design information representing the detailed process contents, and a diagnostic process part 4 which detects the design pattern specified by the design rule in the rule base 9 according to the contents of the design information and diagnoses the design contents.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a software development support system processing method, and more particularly to a program design method for automating design and managing design information in a program design support tool.

0002

[Background Art] Conventionally, design information management methods in design support tools do not have rules for detailing or summarizing design information, and the work of detailing design information into source programs and source programs The work of extracting design information from was done manually.

0003

[Problems to be solved by the invention] In the conventional design method, when manually detailing design information into a source program, defects are likely to occur during the detailing work, and it is difficult to automatically create a source program from design information. When generating, automatic generation is not possible unless the design information is manually detailed.
The drawback was that it was not very effective. Furthermore, with conventional design methods, the design information that can be automatically generated from source programs is detailed design information, and the work of creating design outlines and algorithms from source programs must be done manually. was there.

The present invention has been made to solve these problems, and its purpose is to provide a program design method that allows design work to be carried out efficiently.

[0005]

[Means for Solving the Problems] The present invention relates to a program design method capable of solving the above problems, in which the correspondence between terms used in design information and variable names on the program is used as terminology information. A program design information management department that manages terminology dictionaries that are organized and stored in a dictionary format, and the content of design information that includes source programs and design content as design patterns; It has a rule management unit that stores and manages conversion methods in a rule base as conversion rules, and an algorithm extraction processing unit that converts the contents of design information based on the conversion rules and creates design information representing a processing outline. There is.

Furthermore, the present invention organizes the correspondence between terms used in design information and variable names on a program as terminology information, and uses a terminology dictionary stored in a dictionary format to design source programs and design contents. a program design information management section that manages the contents of design information held as patterns; a rule management section that stores and manages conversion methods for detailing or summarizing the contents of design information in a rule base as conversion rules; The algorithm includes an algorithm detailing processing unit that converts the contents of design information representing a processing outline based on conversion rules and creates design information representing detailed processing contents.

Furthermore, the present invention organizes the correspondence between terms used in design information and variable names on a program as terminology information, and uses a terminology dictionary stored in a dictionary format, a source program, and design contents as a design pattern. a program design information management unit that manages the content of design information held as a program design information management unit; a rule management unit that stores and manages inspection content for inspecting the content of design information in a rule base as design rules; The system includes a diagnosis processing unit that detects a design pattern specified by a design rule in a rule base and diagnoses the design content.

[0008]

Embodiments Next, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing an embodiment of the present invention, which includes a term dictionary 1, an algorithm extraction processing section 2, an algorithm detailing processing section 3, a diagnosis processing section 4, a program design information management section 5, a rule management section 6, It consists of design information 7, source program 8, and rule base 9. The term dictionary 1 contains term information 1 that includes term names and attribute information.
It is composed of 2. The terminology information 12 consists of a Japanese name 201, a program name 202, and attribute information 203, as shown in FIG. The design information 7 is composed of examples of design patterns 13 representing design contents. The rule base 9 includes conversion rules 10 for detailing or summarizing the contents of design information, and design rules 11 for inspecting the contents of the design information.

FIG. 3 is a diagram showing an example for explaining the configuration of the conversion rule 10. The conversion rule 10 has a rule name 3.
01, a detailed pattern 302, and a summary pattern 305. Further, the detailed pattern 302 and the summary pattern 305 each have a keyword 3 indicating the type of pattern.
03 and an entity 304 indicating specific information regarding the keyword 303.

FIG. 4 is a diagram showing an example for explaining the structure of the design rule 11. The design rule 11 includes a design rule name 401 and a keyword 402 indicating the type of design content.
, a sequence of entities 403 indicating the contents of the process to be inspected, and a diagnostic message 404 that is output when the design rule 11 is not met.

FIG. 5 is a diagram showing an example for explaining the structure of the design pattern 13 constituting the design information 7. The design pattern 13 has a keyword 501 indicating the type of pattern.
and entity 5 indicating specific information regarding the keyword 501.
It consists of 02.

Next, the operation will be explained. FIG. 6 is a flowchart showing the process flow of the program design information management unit 5;
7 is a flowchart showing the processing flow of the algorithm extraction processing section 2, FIG. 8 is a flowchart showing the processing flow of the algorithm detailing processing section 3, FIG. 9 is a flowchart showing the processing flow of the diagnosis processing section 4, and FIG. is a flowchart showing the flow of processing by the rule management section 6. Also,
FIG. 11 is a diagram showing examples of terminology dictionaries, source programs, conversion rules, design information, and diagnostic information used to show the processing flow of the algorithm extraction processing section 2 and the diagnosis processing section 4. The operation of this embodiment will be explained below based on the above drawings.

In this embodiment, first, the design information 7 representing the processing outline is extracted from the source program 8 or the design information 7.
When creating the algorithm, the algorithm extraction processing section 2 is activated. As shown in FIG. 7, the algorithm extraction processing unit 2 inputs the distinction between the source program 8 and the design information 7 to be processed (701), and determines whether the distinction is the design information 7 (702). If the distinction is design information 7, design information 7 is input using the program design information management section 5 (703). The program design information management unit 5 determines whether it is in the input mode as shown in FIG. 6 (601).
, if the input mode is selected, the design pattern 13 is input from the design information 7 (602). Then, using the terminology dictionary 1, the program name 202 in the design pattern 13 is converted into a Japanese name 201 (603).

On the other hand, if the distinction is not in the design information 7, input the source program 8 as shown in FIG. Convert to name. After inputting the source program 8 or design information 7 to be processed, the algorithm extraction processing unit 2 extracts the conversion rule 10 using the rule management unit 6 (706).

In the rule management unit 6, as shown in FIG. 10, the rule base 9 is positioned at the top (1001),
Extract conversion rule 10 from rule base 9 (100
2), determine whether the conversion rule 10 to be retrieved has been completed (
1003). As a result of this determination, if the conversion rule 10 to be extracted is not completed, it is assumed that the conversion rule 10 has been successfully extracted and the rule management section 6 is terminated. If the conversion rule 10 to be taken out is finished, it is positioned in the next rule base 9 (1004), and it is determined whether the rule base to be positioned is finished (1005). If the rule base 9 to be positioned is not finished, the conversion rule is extracted (1002), and if the rule base 9 to be positioned is finished, the rule management unit 6 is terminated as the rule base 9 is finished.

After execution of the rule management unit 6, the algorithm extraction unit 2 determines whether the rule base 9 is completed (707), as shown in FIG. 7, and if it is not completed, the conversion rule 10 is
It is checked whether the rows of the detailed pattern 302 and the design pattern 13 match (708). Next, the matching test result between the detailed pattern 302 and the column of the design pattern 13 is determined (709), and if they match, the column of the matched design pattern 13 is converted using the conversion rule 10 (710). Furthermore, if the columns of the detailed pattern 302 and the design pattern 13 do not match, the next conversion rule 10 is extracted (
706). When the rule base 9 is completed in this way, the program design information management unit 5 is used to output the sequence of design patterns 13 to be processed to the design information 7 (711
).

The program design information management unit 5 determines whether the design information 7 is input as shown in FIG. 6 (601).
, if design information 7 is not input, convert the program name 202 of design pattern 13 to Japanese name 201 (6
04), Output the design pattern 13 to the design information 7 (6
05). After outputting the design information 7, the processing of the algorithm extraction processing section 2 is ended.

Furthermore, in this embodiment, when creating the design information 7 or source program 8 representing processing details from the design information 7, the algorithm detailing processing section 3 is activated.

As shown in FIG. 8, the algorithm detailing processing section 3 first inputs the generation distinction of whether the generation target is the source program 8 or the design information 7 (801). Next, input the design information 7 using the program design information management section 5 (
802), the conversion rule 10 is extracted using the rule management unit 6 (803). Thereafter, it is determined whether the rule base 9 has been completed (804), and if not, it is checked whether the summary pattern 305 of the conversion rule 10 and the column of the design pattern 13 match (805). and,
The match check result between the outline pattern 305 and design pattern 13 columns is determined (806), and if they match, conversion rule 1 is applied.
Convert the sequence of matched design pattern 13 using 0 (
807). If they do not match, the next conversion rule 10 is extracted (803) and the same process is performed. When the rule base 9 is completed in this way, it is determined whether the generation type is source program 8 (808), and if the generation type is source program 8, the sequence of design patterns 13 is changed to the form of source program 8. It is converted and output (810), and the processing of the algorithm detailing processing unit 3 is ended. Furthermore, if the generation distinction is not source program 8, the program design information management unit 5 is used to output the sequence of design patterns 13 to the design information 7 (809), and the algorithm detailing processing unit 3
Terminates the process.

Furthermore, in this embodiment, when performing a conformance check on the design information 7 using the design rules 11 of the rule base 9, the diagnostic processing section 4 is activated.

In the diagnosis processing section 4, as shown in FIG. Rule 11 is taken out (902). After that, it is determined whether the rule base 9 is finished (903), and if it is not finished, the appearance order of the keyword 501 and the entity 502 in the column of design pattern 13 of the design information 7 is the keyword of the design rule 11 of the rule base 9. 402 and entity 403
(904). Next, the conformity check result is determined (905), and if the conformance is not conformed, information regarding the violation of the design rule is output using the diagnostic message 404 (906), and the next design rule 11 is extracted (902). Further, if the conformity test result is conformity, the next design rule 11 is extracted (902). When the rule base 9 is completed, the processing of the diagnostic processing unit 4 is ended.

Next, the processing related to the conversion rule 10 and the design rule 11 by the algorithm extraction processing section 2 and the diagnosis processing section 4 will be explained using FIG. 11.

The algorithm extraction processing unit 2 is shown in FIG. 11(b).
) is input, and the design information 7 shown in FIG. 3(c) is created using the terminology dictionary 1 shown in FIG. 2(a). In addition, the algorithm extraction processing unit 2 uses the conversion rule 10 shown in FIG. 11(d) and the conversion rule 10 shown in FIG.
generate. The diagnostic processing unit 4 uses the design rule 11 shown in FIG. 5 to output design rule violation information shown in FIG. 11(f) for the design information 7 shown in FIG. 11(e).

[0024]

[Effects of the Invention] As explained above, the present invention provides a terminology dictionary for managing names in programs and Japanese names for design, and a term dictionary for managing names in programs and Japanese names for design, and for managing design information in patterns and for detailing and summarizing design patterns. By creating rules and managing relationships between patterns, it is possible to automate the conversion between source programs and design information, and also to automate the diagnosis of design patterns. Furthermore, by managing the rules by dividing them into a plurality of rule bases, there is an effect that the rules can be classified and managed for each design purpose.

[Brief explanation of the drawing]

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

FIG. 2 is an explanatory diagram showing the structure of term information.

FIG. 3 is an explanatory diagram showing the structure of a conversion rule.

FIG. 4 is an explanatory diagram showing the structure of a design rule.

FIG. 5 is an explanatory diagram showing the structure of a design pattern.

FIG. 6 is a flowchart showing the flow of processing by a program design information management unit.

FIG. 7 is a flowchart showing the flow of processing by an algorithm extraction processing section.

FIG. 8 is a flowchart showing the flow of processing by an algorithm detailing processing unit.

FIG. 9 is a flowchart showing the flow of processing by the diagnostic processing unit.

FIG. 10 is a flowchart showing the flow of processing by the rule management unit.

FIG. 11 is an explanatory diagram showing examples of a terminology dictionary, source program, conversion rules, design information, and diagnostic information used to show the flow of processing by the algorithm extraction processing section and the diagnosis processing section.

[Explanation of symbols]

1. Terminology dictionary 2 Algorithm extraction processing section 3 Algorithm detailing processing unit 4 Diagnosis processing section 5 Program design information management department 6. Rules Management Department 7 Design information 8 Source program 9 Rule base 10 Conversion rules 11 Design rules 12 Terminology information 13 Design pattern

Claims (4)

[Claims] Claim 1: In a program design support system, the correspondence between terms used in design information and variable names on a program is organized as terminology information, and a terminology dictionary stored in a dictionary format, a source program, and design contents are provided. A program design information management section that manages the contents of design information having design patterns as design patterns, and a rule management section that stores and manages conversion methods for detailing or summarizing the contents of design information in a rule base as conversion rules. and an algorithm extraction processing unit that converts the content of design information based on conversion rules and creates design information representing a processing outline. Claim 2: In a program design support system, the correspondence between terms used in design information and variable names on a program is organized as terminology information, and a terminology dictionary stored in a dictionary format, a source program, and design contents are provided. A program design information management section that manages the contents of design information having design patterns as design patterns, and a rule management section that stores and manages conversion methods for detailing or summarizing the contents of design information in a rule base as conversion rules. and an algorithm detailing processing unit that converts the content of design information representing a processing outline based on a conversion rule and creates design information representing detailed processing content. 3. In a program design support system, a terminology dictionary that organizes correspondence between terms used in design information and variable names on a program as terminology information and is stored in a dictionary format, a source program, and design contents. a program design information management section that manages the contents of design information having design information as a design pattern; a rule management section that stores and manages inspection contents for inspecting the contents of design information in a rule base as design rules; 1. A program design method comprising: a diagnosis processing unit that detects a design pattern specified by a design rule in a rule base from the contents of the rule base and diagnoses the design contents. 4. The program design method according to claim 1, further comprising a rule management section that manages a plurality of rule bases storing conversion rules and design rules.