Method and apparatus for providing a user configurable system which integrates and manages a plurality of different task and software tools

• US 5,423,023 A
• Filed: 06/25/1990
• Issued: 06/06/1995
• Est. Priority Date: 06/25/1990
• Status: Expired due to Term

• Current Assignee: PTC Inc.
• Original Assignee: Prime Computer, Inc. (DR Holdings, Inc. of Delaware)
• Inventors: Russell, Robert A., Ivanov, Pavel, Michel, Timothy I., Batch, James C., Burns-Brookens, Eileen M.
• Primary Examiner(s): Lall, Parshotam S.
• Assistant Examiner(s): Lim, Krisna
• Application Number:
  US07/543,048
• Time in Patent Office: 1,807 Days
• Field of Search: 395/500, 395/700
• US Class Current: 717/117
• CPC Class Codes: G06F 2111/20 Configuration CAD, e.g. designing by assembling or positioning modules selected from libraries of predesigned modules
• CPC Class Codes: G06F 30/00 Computer-aided design [CAD]
• CPC Class Codes: G06F 8/70 Software maintenance or management

Abstract

A user configurable system which integrates and manages a plurality of different tasks and software tools. It is adapted primarily for use in design and production automation systems. The system has a main control routine which utilizes macros to control each process to be performed, including the sequencing of tasks and the encapsulation of any incompatible software tools which interface with the control program. The encapsulation controls the interpretations for transfers between the incompatible tool and the control program. Additional routines are provided for providing interfacing between various tools, including tools having various types of incompatibilities, and between an operator and the system or the various tools used therein. All such routines are rules based and such rules, including the macros used with the control routine, are written in an interpretive extension language which is both human and machine readable. This renders the system easily configurable and reconfigurable by the user.

Claims

1. A system for integrating and managing the operations of a plurality of different software tools, the system comprising:

means for storing a plurality of rule macros, each corresponding to a particular process;

means for inputting a process to the system;

means responsive to the inputted process for retrieving the corresponding macro;

execution means, responsive to the retrieved corresponding macro, for causing one or more selected tools to be executed in a predetermined sequence as determined by the corresponding rule macro, the macros each including rules for executing one receiving inputs and for providing outputs in response to the inputs, wherein each tool is individually operable to perform a desired function and is operable as part of a process with other software tools, wherein at least some of the tools receive inputs and/or provide outputs which are incompatible with the system;

means for determining whether one of the selected tools being executed is incompatible with the system based on a list of software tools; and

encapsulation means, responsive to the execution of an incompatible tool and to interpretation rules, for causing all transfers from and to the incompatible tool to be automatically checked and interpreted as necessary.

2. A system as claimed in claim 1 wherein the list of software tools to be utilized in the system is stored in said means for storing, an indication being provided in the list for each tool as to whether the tool is an incompatible tool.

3. A system as claimed in claim 1 wherein a plurality of interpretation rules are at a predetermined location in a macro corresponding to an incompatible tool, the encapsulation means including:

means for checking each transfer from and to the incompatible tool for an input/output to which one of the interpretation rules applies, and

means responsive to the transfer of an input/output to which an interpretation rule applies for performing the interpretation set forth in the interpretation rule.

4. A system as claimed in claim 3 wherein said interpretation rules include separate rules for items transferred from the incompatible tool and for items transferred to the incompatible tool, and wherein said means for checking and said means for performing check and perform, respectively, with respect to the appropriate rules for the directions in which an item is being transferred.

5. A system as claimed in claim 4 including

means, operative when an incompatible tool is being executed, for determining if the interpretation rules for transfer from the incompatible tool should be stored,

means for storing the interpretation rules which the determining means determines should be stored, and

means, responsive to an output from said tool, for returning said interpretation rules and for utilizing said interpretation rules to interpret outputs from the incompatible tool.

6. A system as claimed in claim 2 wherein said rule macros, including said interpretation rules, are written in an interpretive extension language which is both human and machine readable.

7. A system as claimed in claim 6 wherein at least some of said macros contain rules for a plurality of software tools to perform a given function, the rules specifying the order in which the tools are executed.

8. A system as claimed in claim 7 wherein at least one of said macros contains a rule which causes the retrieval of a new macro from said means for storing.

9. A system for integrating and managing the operations of a plurality of different software tools, at least some of which are incompatible with the system, a format for at least one of said tools being different from a format for another tool, and wherein transfer can occur in at least one direction between said one and said another tool, the system comprising:

means for storing a plurality of rule macros, each relating to a particular function;

means for inputting a process to the system;

means responsive to an inputted process for retrieving a corresponding macro;

means responsive to the retrieved macro for causing selected tools to be executed in a predetermined sequence, wherein a macro includes rules for controlling the sequencing of tools and the interfacing of tools with the system, with a user, and with each other, wherein a software tool is a program for receiving inputs and for providing outputs in response to the inputs, wherein each tool is individually operable to perform a desired function and is operable as part of a process with other software tools, wherein at least some of the tools receive inputs and/or provide outputs which are incompatible with the system as determined by a list of software tool;

a rules file containing format conversion rules for tools having incompatible formats;

means, operative when there is to be a transfer between format incompatible tools, for retrieving the appropriate format conversion rules from the rules file; and

means for utilizing the retrieved rules to control format conversion of material to be transferred between the format incompatible tools.

10. A system as claimed in claim 9 wherein one or more of the tools includes a nested hierarchy of material on a component with different names being utilized for the same item at different levels in the hierarchy;

and

including a rules file for translations of said names for the various hierarchy levels, and means for utilizing said rules file to obtain the appropriate name for an item at a given hierarchy level.

11. A system as claimed in claim 9 wherein at least two format incompatible tools are also name incompatible;

the system further including means for performing required name translations on transfers between said name incompatible tools.

12. A system for integrating a number of software tools, wherein a software tool is a program for receiving inputs and for providing outputs in response to the inputs, wherein each tool is individually operable to perform a desired function and is operable as part of a process with other software tools, wherein at least some of said tools provide outputs which are name incompatible with other tools so that means of outputs for one tool are not compatible as inputs to another tool, said system comprising:

means for storing a plurality of rule macros, each relating to a particular process;

means for inputting a process to the system;

means responsive to an inputted process for retrieving a corresponding macro;

means responsive to the retrieved macro for causing selected tools to be executed in a predetermined sequence, wherein a macro includes rules for controlling the sequencing of tools and the interfacing of tools with the system, with a user, and with each other, wherein a software tool is a program for receiving inputs and for providing outputs in response to the inputs, wherein each tool is individually operable to perform a desired function and is operable as part of a process with other software tools, wherein at least some of the tools receive inputs and/or provide outputs which are incompatible with the system as determined by a list of software tools;

a rules file including translation rules for tools which are name incompatible; and

means operative when there is a transfer of names between name incompatible tools for utilizing appropriate rules in the rules file to effect translations necessary to render said tools compatible.

13. A system as claimed in claim 12 including means for storing with each rules file a list of name translations for the name incompatible tools.

14. A system as claimed in claim 13 wherein said rules and corresponding name list are stored in a scope, a name translation entry being added to the list each time a translation is made for a name not already on the list.

15. A system as claimed in claim 14 further including:

means, responsive to the transfer of a name requiring translation between said name incompatible tools, for determining if there is an entry for the name requiring translation in the names list,

means, responsive to a determination that there is an entry for the name requiring translation, for utilizing the entry to translate the name, and

means, responsive to a determination that there is no entry for the name requiring translation, for utilizing the appropriate rules to translate the name requiring translation.

16. A system as claimed in claim 15 wherein said means for utilizing the appropriate rules includes means for looking at each appropriate rule to determine if it is applicable to the name, and means for applying appropriate rules to perform the translation of the name.

17. A system as claimed in claim 16 including means for removing any invalid characters after a name translation by said means for applying appropriate rules.

18. A system as claimed in claim 16 including means for truncating a translated name to an appropriate maximum length.

19. A system as claimed in claim 16 including means for adding any required prefixes or suffixes to a translated name.

20. A system as claimed in claim 16 including means for determining if a unique translated name is required for each name to be translated, means operative if a unique translated name is required for determining if the translated name is unique, means operative if the translated name is not unique for determining if the translated name can be modified to be unique, and means for modifying the translated name to be unique if such modification is possible.

21. A system as claimed in claim 20 including means for indicating for each entry in said name list whether such entry is for 1 translated name which is required to be unique.

22. A system as claimed in claim 14 including means for storing the name list of a scope as an alias file.

23. A system as claimed in claim 14 including means for utilizing the names list in a scope to provide original names from generated names, wherein if there is not a unique original name, said means to provide provides a list of original names for each generated name applied thereto.

24. A method as claimed in claim 14 including the steps of storing the name list of a scope as an alias file.

25. A system for integrating a number of software tools, wherein a software tool is a program for receiving inputs and for providing outputs in response to the inputs, wherein each tool is individually operable to perform a desired function and is operable as part of a process with other software tools, said system comprising:

means for storing a plurality of rule macros, each relating to a particular process;

means for inputting a process to the system;

means responsive to an inputted process for retrieving a corresponding macro;

means responsive to the retrieved macro for causing selected tools to be executed in a predetermined sequence, wherein a macro includes rules for controlling the sequencing of tools and the interfacing of tools with the system, with a user, and with each other, wherein input information is required from a user for at least some tools, wherein a software tool is a program for receiving inputs and for providing outputs in response to the inputs, wherein each tool is individually operable to perform a desired function and is operable as part of a process with other software tools, wherein at least some of the tools receive inputs and/or provide outputs which are incompatible with the system as determined by a list of software tools;

rules files; and

means for utilizing the rules files to actively enter required input information.

26. A system as claimed in claim 25 wherein said rules files provide default inputs for each stage at which inputs are required of each tool, and including means operative when a tool is at a stage where inputs are required for displaying the default inputs for such stage to the user, means for permitting the user to make changes to the default inputs, and means for communicating the default inputs as modified by the user to the tool.

27. A system as claimed in claim 26 including means for permitting the user to indicate that the user wishes to make inputs to a tool or to the system.

28. A system as claimed in claim 26 including means for prompting the user in the default input display as to items which the user must add as inputs at the given stage in the tool.

29. A system as claimed in claim 28 including means for inhibiting further operation of the tool until the user makes the required inputs.

30. A system as claimed in claim 28 including means for prompting the user in the default input display as to optional items which the user may add as inputs at the given stage in the tool.

31. A system as claimed in claim 25 including means for storing information concerning a design and for storing translation information concerning a selected one or more tools;

means for prompting a user to select an element of the stored design on which a selected translations is to be performed; and

means responsive to a user input for effecting the selected translation on the element selected by the user.

32. A system as claimed in claim 25 wherein said required input information is digital graphic information;

and

including means for storing state definitions for valid digital states for the graphic information;

means for receiving graphic information to be inputted; and

means for utilizing the stored state definitions to display said received graphic information.

33. A system as claimed in claim 32 wherein the received graphic informations may be either default graphic information from the system or graphic information provided by a user.

34. A system as claimed in claim 32 wherein said means for storing rules files includes means for storing logic rules for operating on said graphic information;

means for receiving and recognizing commands for operating on said graphic information; and

means for utilizing appropriate stored logic rules to execute a received and recognized command.

35. A system as claimed in claim 32 wherein said digital graphic information includes waveforms;

and wherein said means to display utilizes the stored state definitions to control the display for each successive state of a waveform to be displayed.

36. A method for integrating and managing the operations of a plurality of different software tools, said method comprising the computer implemented steps of:

storing a plurality of rule macros, each corresponding to a particular process;

inputting a process to the system;

retrieving a corresponding macro in response to the inputted process;

executing one or more selected tools in a predetermined sequence in response to the retrieved corresponding macro, the macros each including rules for executing one or more tools, wherein a software tool is a program for receiving inputs and for providing outputs in response to the inputs, wherein each tool is individually operable to perform a desired function and is operable as part of a process with other software tools, wherein at least some of the tools receive inputs and/or provide outputs which are incompatible with the system;

determining if one of said selected tools being executed is incompatible with the system based on a list of software tools; and

encapsulating the tool, causing all transfers from and to the tool to be checked and to be interpreted as necessary in accordance with interpretation rules in response to a determination that the selected tool being executed is incompatible.

37. A method as claimed in claim 36 wherein the list of software tools to be utilized in the system is stored with said macros, an indication being provided for each tool in the list whether the tool is an incompatible tool.

38. A method as claimed in claim 36 wherein said encapsulation step includes the steps of:

checking the interpretation rules at a predetermined location in a macro for a software tool requiring encapsulation during each transfer from and to the tool for an item to which one of the interpretation rules applies, and

performing the interpretation set forth in the interpretation rule in response to the transfer of the item to which the interpretation rule applies.

39. A method as claimed in claim 38 including the steps, operative when an incompatible tool is being executed, of

determining if the interpretation rules for transfer from the tool should be stored,

storing the interpretation rules in response to a determination that the interpretation rules should be stored,

returning said stored interpretation rules in response to an output from said incompatible tool, and

utilizing said returned interpretation rules to interpret outputs from said incompatible tool.

40. A method as claimed in claim 37 wherein said rule macros, including said interpretation rules, are written in an language which is both human and machine readable.

41. A method as claimed in claim 40 wherein a macro may contain rules for a plurality of software tools to perform a given function, the rules specifying the order in which the tools are performed.

42. A method as claimed in claim 41 wherein at least one of said macros contains a rule which causes the retrieval of a new macro from said means for storing.

43. A method for integrating and managing the operations of a plurality of different software tools, at least some of which are incompatible with the system, said method comprising the computer implemented steps of:

storing a plurality of rule macros, each relating to a particular function;

inputting a process to the system;

retrieving a corresponding macro in response to an inputted process; and

executing selected tools to be executed in a predetermined sequence in response to the retrieved macro, wherein a software tool is a program for receiving inputs and for providing outputs in response to the inputs, wherein each tool is individually operable to perform a desired function and is operable as part of a process with other software tools, wherein at least some of the tools receive inputs and/or provide outputs which are incompatible with the system;

wherein a macro can include rules for controlling the sequencing of tools and the interfacing of tools with the system, with a user, and with each other through interpretation rules for translating outputs of one tool to another form for use as inputs to another tool which is incompatible as determined by a list of software tools.

44. A method as claimed in claim 43 wherein the format for at least one of said tools is different from the format for another tool, and wherein transfer may occur in at least one direction between said one and said other tool, said method further including:

providing a rules file having format conversion rules for tools having incompatible formats;

returning the appropriate format conversion rules from the rules file when there is to be a transfer between format incompatible tools; and

utilizing the retrieved format conversion rules to control format conversion of material to be transferred between the format incompatible tools.

45. A method as claimed in claim 44 wherein at least two format incompatible tools are also name incompatible;

and including the steps of performing required name translations on material transferred between said name incompatible tools.

46. A method as claimed in claim 43 wherein at least some of said tools are name incompatible said method further including:

providing a rules file containing translation rules for tools which are name incompatible; and

utilizing appropriate rules in the rules file to effect translations necessary to render said tools compatible when there is a transfer between name incompatible tools.

47. A method as claimed in claim 46 including the step of storing, with each rules file, a list of name translations for the name incompatible tools.

48. A method as claimed in claim 47 further comprising:

storing said rules and corresponding name list in a scope, and

adding a name translation entry to the list each time a translation is made for a name not already on the list.

49. A method as claimed in claim 48 including the steps of:

determining, when there is a transfer of a name requiring translation between said name incompatible tools, whether there is an entry for a name requiring translation in the names list,

utilizing the entry to translate the name in response to a determination that there is an entry for the name requiring translation in the names list, and

utilizing the appropriate rules to translate the name in response to a determination that there is no entry for the name requiring translation in the names list.

50. A method as claimed in claim 49 wherein said utilizing step includes the steps of

checking each appropriate rule to determine if it is applicable to the name, and applying appropriate rules to perform the translation of the name.

51. A method as claimed in claim 50 including the steps of removing any invalid characters after a name translation during said applying appropriate rules step.

52. A method as claimed in claim 50 including the steps of truncating a translated name to an appropriate maximum length.

53. A method as claimed in claim 50 including the step of adding any required prefixes or suffixes to a translated name.

54. A method as claimed in claim 50 including the steps of determining if a unique translated name is required for each name to be translated,

if a unique translated name is required,

determining if the translated name is unique,

if the translated name is not unique,

determining if the translated name can be modified to be unique, and

modifying the translated name to be unique if such modification is possible.

55. A method as claimed in claim 54 including the step of indicating, for each entry in said name list whether each entry is for a translated name which is required to be unique.

56. A system as claimed in claim 48 including the step of:

utilizing the names list in a scope to provide original names from generated names, so that if there is not a unique original name, said providing step includes providing a list of original names for each generated name applied thereto.

57. A method as claimed in claim 43 wherein one or more of the tools includes a nested hierarchy of material on a component with different names being utilized for the same item at different levels in the hierarchy.

58. A method as claimed in claim 43 wherein input information is required from a user for at least some tools, said method further including:

providing a rules files written in an interpretive extension language; and

utilizing the rules files to interactively enter required input information.

60. A method as claimed in claim 58 wherein said rules files provide default inputs for each stage at which inputs are required of each tool;

and including the steps of;

displaying the default inputs for each stage to the user when a tool is at a stage where inputs are required,

permitting the user to make changes to the default inputs, and

communicating the default inputs as modified by the user to the tool.

61. A method as claimed in claim 60 including the step of permitting the user to indicate that the user wishes to make inputs to a tool or to the system.

62. A method as claimed in claim 60 including the step of prompting the user in the default input display as to items which the user must add as inputs at the given stage in the tool.

63. A method as claimed in claim 62 including the step of inhibiting further operation of the tool until the user makes the required inputs.

64. A method as claimed in claim 62 including the step of prompting the user in the default input display as to optional items which the user may add as inputs at the given stage in the tool.

65. A method as claimed in claim 58 wherein said required input information is digital graphic information;

and

including the steps of storing state definitions for valid digital states for the graphic information;

receiving graphic informations to be inputted; and

utilizing the stored state definitions to display said received graphic information.

66. A method as claimed in claim 65 wherein the received graphic informations may be either default graphic information from the system or graphic information provided by a user.

67. A method as claimed in claim 65 including the steps of storing logic rules for operating on said graphic information;

receiving and recognizing commands for operating on said graphic information; and

utilizing appropriate stored logic rules to execute a received and recognized command.

68. A method as claimed in claim 65 wherein said digital graphic information includes waveforms;

and wherein the stored state definitions are utilized to control the display for each successive state of a waveform to be displayed.

59. A method as claimed in 58 including the steps of:

storing information concerning a design;

storing translation information concerning a selected one or more tools;

prompting a user to select an element of the stored design on which a selected translation is to be performed; and

effecting, in response to a user input, the selected translation on the element selected by the user.