Automatic programming system with design review capabilities

• US 5,269,014 A
• Filed: 11/15/1991
• Issued: 12/07/1993
• Est. Priority Date: 05/27/1988
• Status: Expired due to Term

• Current Assignee: Mitsubishi Denki Kabushiki Kaisha (Mitsubishi Electric Corporation)
• Original Assignee: Mitsubishi Denki Kabushiki Kaisha (Mitsubishi Electric Corporation)
• Inventors: Ogino, Toru
• Primary Examiner(s): Kriess, Kevin A.
• Application Number:
  US07/792,803
• Time in Patent Office: 753 Days
• Field of Search: 395/500, 395/700, 395/140, 395/12, 364/578, 364/191, 364/579
• US Class Current: 703/22
• CPC Class Codes: G06F 8/00 Arrangements for software engineering testing or debugging G06F11/36; administrative, planning or organisation aspects of software project management G06Q10/06
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines

Abstract

An automatic programming system seeks to maximize the automation of software development. This automatic programming system includes a capability to trade-off program structure so as to optimize the structure to fulfill requested software specification requirements. The system also includes an ability to perform failure mode and effect analysis and design review. The design operation and testing operations are directly coupled to each other so that the design data may be utilized effectively during testing.

Claims

1. An automatic programming system comprising:

(a) a program constitution trading-off means for determining an optimum combination of components for a piece of software corresponding to a given software specification, which identifies functions, performance and scale of the piece of software, by analyzing possible combinations of components in view of operation parameters, wherein said components include sub-routines and/or modules;

(b) block diagram production means for producing block diagrams such as sub-routine, module and signal system diagrams from a result of the optimum combination of components;

(c) program failure mode and effect analysis means for performing failure mode and effect analysis of the program from the block diagrams to produce an analysis sheet;

(d) simulation means for performing simulation for confirming the operation of the program constituted by the block diagrams to ensure that it satisfies the software specification;

(e) software design reviewing means including;

(i) a learning section for learning of design knowledge about the piece of software from the analysis sheet;

(ii) a knowledge base section for storing the learned design knowledge; and

(iii) an inference section for effecting inference by using the acquired design knowledge;

(f) automatic program production means for producing program source codes from block diagrams wherein said codes are produced by relating portions of the block diagrams to source codes based on a member data base;

(q) automatic program test data production means for producing program test rules from the analysis sheet; and

(h) program test means for performing program tests on the program source codes on the basis of the test rules.

2. An automatic programming system according to claim 1, wherein said program constitution trading off means has;

(a) evaluation reference parameters for optimizing trading-off; and

(b) is provided with a function of effecting an optimization process and also effecting trading-off in colloquy with a designer to determine a basic structure of program functions necessary for realizing rough requested functions in the specification for the piece of software and then determine detailed structures for realizing each such requested function.

3. An automatic programming system according to claim 1, wherein said learning section includes

design knowledge acquisition and learning means for (i) accepting result data, said result data including data from said program constitution trading-off means defining a combination of components, and analysis data from said program failure mode and effect analysis means, (ii) extracting design knowledge and rules from the result data, (iii) transforming the design knowledge and rules into knowledge for design reviewing, and (iv) storing the knowledge for design reviewing.

5. An automatic programming system according to claim 3, wherein said inference section includes design evaluation means for reviewing a design of the piece of software including (i) means for using said knowledge for design reviewing to identify deficiencies in the design, and (ii) means for passing evaluation data to said program constitution trading-off means and to said program failure mode and effect analysis means.

6. An automatic programming system according to claim 5, wherein said program constitution trading-off means includes design consultation means for accepting any inquiry including system specifications and retrieving data from the knowledge base section in accordance with the inquiry.

7. An automatic programming system according to claim 1, wherein said program failure mode and effect analysis means includes:

(1) formatting means for creating a format including items for (i) names of said basis components, (ii) functions of said basic components, (iii) possible failures of said basic components, (iv) causes of said failures, and (v) effects of said failures, and

(2) question production processing means for producing and displaying questions for each item of said format so as to allow a designer to enter answers including the names, functions and possible failures of basic components in question, and causes and effects of said failures based on technical knowledge of the designer, for inputting these answers into the respective item, for classifying said possible failures by each of said basic components, for inputting names, functions and possible failures of basic components into an assumption section of diagnosis rules, and for inputting causes and effects of said failures into a conclusion section of diagnosis rules.

8. An automatic programing system according to claim 1, wherein said inference section includes design evaluation means for reviewing a design of the piece of software including (i) means for using said knowledge for design reviewing to identify deficiencies in the design, and (ii) means for passing evaluation data to said program constitution trading-off means and to said program failure mode and effect analysis means.

9. An automatic programming system according to claim 1, wherein said program constitution trading-off means includes design consultation means for accepting an inquiry including system specifications and retrieving data from the knowledge base section in accordance with the inquiry.

4. An automatic programming system for developing a computer program, comprising:

(a) program constitution trading-off means for (i) allocating requirements for functions and scale to basic components of said program, said basic components including sub-routines and modules, (ii) encoding such requirements, (iii) storing such requirements in a member database, and (iv) obtaining an optimum combination of said basic components according to parameters including processing speed, scale, portability, cost and use records of each of said basic components;

(b) block diagram production means for producing a block diagram including a sub-routine diagram, a module diagram and a signal system diagram corresponding to the optimum combination of said basic components;

(c) program failure mode and effect analysis means for producing an analysis sheet using an analysis of failure mode and effects of said program based on said block diagram;

(d) simulation means for performing simulation and checking whether the program defined by said block diagram satisfies said requirements;

(e) software design reviewing means including (1) a learning section for extracting rules from the optimum combination of said basic components and said analysis sheet, and for accepting and learning design knowledge for the production of programs, (2) a knowledge base section for storing the acquired design knowledge, and (3) an inference section for effecting inference by classifying and systematizing the acquired design knowledge;

(f) automatic program production means for producing program source code by using source code fragments stored in a member database to implement said basic components;

(g) automatic program test data production means for producing program test rules to which corresponding possible failures may be allocated so as to permit checking of failures in each of said basic components using said analysis sheet; and

(h) program test means for performing program test on said program source codes according to said test rules;

wherein said program failure mode and effect analysis means includes;

(1) formatting means for creating a format including items for (i) names of said basic components, (ii) functions of said basic components, (iii) possible failures of said basic components, (iv) causes of said failures, and (v) effects of said failures, and

(2) question production processing means for producing and displaying questions for each item of said format so as to allow a designer to enter answers including the names, functions and possible failures of basic components in question, and causes and effects of said failures based on technical knowledge of the designer, for inputting these answers into the respective item, for classifying said possible failures by each of said basic components, for inputting names, functions and possible failures of basic components into an assumption section of diagnosis rules, and for inputting causes and effects of said failures into a conclusion section of diagnosis rules.

10. An automatic programming system for developing a computer program, comprising:

(a) program constitution trading-off means for (i) allocating requirements for functions and scale to basic components of said program, said basic components including sub-routines and modules, (ii) encoding such requirements (iii) storing such requirements in a member database, and (iv) obtaining an optimum combination of said basic components according to parameters including processing speed, scale, portability, cost and use records of each of said basic components;

(b) block diagram production means for producing a block diagram including a sub-routine diagram, a module diagram and a signal system diagram corresponding to the optimum combination of said basic components;

(c) program failure mode and effect analysis means for producing an analysis sheet using an analysis of failure mode and effects of said program based on said block diagram;

(d) simulation means for performing simulation and for checking whether the program defined by said block diagram satisfies said requirements;

(e) software design reviewing means including a learning section, wherein said learning section includes design knowledge acquisition and learning means for (i) accepting result data, said result data including data defining a combination of basic components from said program constitution trading-off means, and analysis data from said program failure mode and effect analysis means, (iii) extracting design knowledge and rules from the result data, (iv) transforming the design knowledge and rules into knowledge for design reviewing, and (v) storing the knowledge for design reviewing in said knowledge base section;

(f) automatic program production means for producing program source code by using source code fragments stored in a member database to implement said basic components;

(g) automatic program test data production means for producing program test rules to which corresponding possible failures may be allocated so as to permit checking of failures in each of said basic components using said analysis sheet; and

(h) program test means for performing program tests on said program source codes according to said test rules.

11. An automatic programming system according to claim 10, wherein said inference section includes design evaluation means for reviewing a design of the piece of software including (i) means for using said knowledge for design reviewing to identify deficiencies in the design, and (ii) means for passing evaluation data to said program constitution trading-off means and to said program failure mode and effect analysis means.

12. An automatic programming system according to claim 10, wherein said program constitution trading-off means includes design consultation means for accepting an inquiry including system specifications and retrieving data from the knowledge base section in accordance with the inquiry.

13. An automatic programming system comprising:

(a) a program constitution trading-off module having (i) first input means for accepting a software specification, (ii) a second input, (iii) a learning section, (iv) means for determining a possible optimum combination of components for a piece of software corresponding to a given software specification, and (v) output means for outputting a possible optimum combination of components;

(b) a block diagram production module having (i) input means for accepting a possible optimum combination of components from said program constitution trading-off module, (ii) means for producing a block diagram, and (iii) output means for outputting a block diagram;

(c) a program failure mode and effect analysis module having (i) input means for accepting a block diagram from said block diagram production module, (ii) means for performing failure mode and effect analysis using the block diagram, and (iii) output means for outputting an analysis sheet; and

(d) a software design reviewing module having (i) input means for accepting an analysis sheet from said program failure mode and effect analysis module, (ii) means for producing design deficiency data, and (iii) output means for outputting said design deficiency data to said second input of said program constitution trading-off means.

14. An automatic programming system according to claim 13, wherein said means for determining a possible optimum combination of components for a piece of software corresponding to a given software specification includes a knowledge base section and an inference section.