Apparatus for generating software logic rules by flowchart design

• US 8,131,663 B1
• Filed: 10/13/2008
• Issued: 03/06/2012
• Est. Priority Date: 10/12/2007
• Status: Active Grant

• Current Assignee: Blaise Dieudonne Taylor
• Original Assignee: Bonamy Taylor
• Inventors: Taylor, Bonamy
• Primary Examiner(s): Gaffin, Jeffrey A
• Assistant Examiner(s): Hill, Stanley K
• Application Number:
  US12/249,995
• Time in Patent Office: 1,240 Days
• Field of Search: None
• US Class Current: 706/59
• CPC Class Codes: G06F 8/34 Graphical or visual programming

Abstract

A apparatus implemented using a programmable computer that automatically generates the rules required by a software rules engine as a process flow diagram is designed. The apparatus includes a developer interface; an editing interface, and a rules generator. A developer interface enables the user to define functions and variables together with their properties from the business application. An editing interface allows the user to define the logical rules the business would follow in performing the business application by constructing a process flow diagram and associated tables using the functions and variables defined in the developer interface. The rules generator then automatically parses the flow diagrams and tables defined by the business user and, using the functions and variables defined in the developer interface, generates rules for a rules engine. The rules can then be deployed to a controller that implements the process automatically based on the input rules.

Claims

1. An apparatus implemented on a programmed computer for generating rules in a format acceptable to a rules engine for automating a business process, said business process having functions, variables and project properties, said apparatus comprising:

a developer interface having plural dialog boxes for defining functions, variables and project properties of a business process to be automated, wherein said project properties have an activity class defined in the project properties which project properties include an executable, a path to said executable, a startup argument, a resource file, a resource file deployment path, a rules file, a rules file deployment path, and a list of excludable modules;

an editing interface for designing a flow diagram using shapes and connectors selected from a pre-selected list of shapes and connectors, said flow diagram being based on said business process, said shapes and connectors being software objects carrying said functions and variables; and

a rules generator that parses said flow diagram and, using said functions and variables carried by said shapes and connectors, generates rules in a form adapted for use by a rules engine for automatically implementing said business process.

2. The apparatus as recited in claim 1, wherein said functions include dialog functions, multiple choice functions, and set variable functions.

3. The apparatus as recited in claim 2, wherein said functions further include binary operators.

4. The apparatus as recited in claim 2, wherein said functions further include remove variable functions.

5. The apparatus as recited in claim 1, wherein said variables are field variables or property variables.

6. The apparatus as recited in claim 1, wherein said variables have a reference name and a reference category.

7. The apparatus as recited in claim 1, wherein said variables are implemented or automatic, said implemented variables requiring implementation by a developer.

8. The apparatus as recited in claim 1, wherein said variables are of a type selected from the group consisting of Boolean, DateTime, String, Char, Decimal, Single, Double, Byte, Int16, Int32, Int64, SByte, UInt16, UInt32 or UInt64.

9. The apparatus as recited in claim 1, wherein said variables include an evaluation type, a domain and a variable type.

10. The apparatus as recited in claim 9, wherein said evaluation type may be a RETE function, a variable fact or a non-variable fact.

11. The apparatus as recited in claim 9, wherein said domain defines a list of choices for said variable.

12. The apparatus as recited in claim 9, wherein said variable type is a number, string or symbol.

13. The apparatus as recited in claim 1, wherein said shapes are selected from the group consisting of Action, Dialog, Module, Decision, Connector, Module Begin, Module End, Begin Flow, End Flow, Jump, Condition, Terminate, Wait Decision, Wait Condition, Question List and Update Variables shapes and combinations thereof.

14. The apparatus as recited in claim 13, wherein said Connector shape has an index property, a category property, and a text property, said index property being used to distinguish said Connector shape from a different Connector shape, and wherein said category property indicating whether said Connector shape is leaving a Dialog shape, a Condition shape, or a Decision shape, and wherein said text property holds said text value.

15. The apparatus as recited in claim 14, wherein said text value is yes or no for said connector shape when said connector shape is leaving said condition shape and said decision shape.

16. The apparatus as recited in claim 13, wherein said shapes contain data stored as meta data, and wherein said rules generator parses said flow chart by basing said rules on shapes and data stored within said shapes.

17. The apparatus as recited in claim 1, where each rule is based on a first number of said shapes and a second number of said connectors, said second number being one less than said first number.

18. The apparatus as recited in claim 1, wherein said rules include start rule shapes, intermediate rule shapes and end rule shapes.

19. The apparatus as recited in claim 18, wherein said intermediate shapes are always action shapes.

20. The apparatus as recited in claim 18, wherein said end rule shapes of one rule may be start rule shapes of a different rule.

21. The apparatus as recited in claim 13, wherein said shapes are characterized by conditions defined by properties, said properties including a driver property, a selection property, a module begin property, and a module end property.

22. The apparatus as recited in claim 21, wherein said selection property is set by the user at run time when a multiple choice function is invoked.

23. A method of generating rules for a rules engine to implement a business process, said method comprising the steps of:

(1) defining, using a programmed computer, a business process in terms of functions and variables;

(2) storing on said computer metadata for functions and variables used in shapes and connectors;

(3) constructing, using said computer, a process flow diagram according to said business process with objects selected using an object-based software programming language, said objects being the shapes and connectors, said objects having project properties wherein each project property has an activity class defined in the project properties including an executable, a path to said executable, a startup argument, a resource file, a resource file deployment path, a rules file, a rules file deployment path, and a list of excludable modules;

(4) parsing, using said computer, said process flow diagram and said properties of said shapes and connectors of said process flow diagram for rules regarding said process;

(5) generating using said computer said rules in a software language readable by a rules engine;

(6) defining, using said computer, the sequence of execution of said rules by using index values associated with the shapes and page numbers of the Start Rule Shapes and End Rule Shapes;

(7) generating, using said computer, menus for display at run time based on multiple choice dialog functions and the associated connectors; and

(8) defining, using said computer, the sequence of execution of said rules by generating choices for the runtime user based on the connectors leaving the dialog shape.