Run time dependency management facility for controlling change propagation utilizing relationship graph

• US 5,634,056 A
• Filed: 10/06/1995
• Issued: 05/27/1997
• Est. Priority Date: 10/06/1995
• Status: Expired due to Term

• Current Assignee: Altair Engineering Incorporated
• Original Assignee: Runtime Design Automation (Altair Engineering Incorporated)
• Inventors: Casotto, Andrea
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): Coby, Frantz
• Application Number:
  US08/540,392
• Time in Patent Office: 599 Days
• Field of Search: 395/600, 395/200.05, 395/700, 395/200.08, 395/650, 395/550, 395/617, 395/619, 364/300
• US Class Current: 1/1
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A method and apparatus for controlling the propagation of changes made to a data file in a system of interrelated data files is described. In one embodiment of the method of the invention, a run-time dependency management facility is provided on the computer system which is effective to generate under computer control a graph indicating relationships among the data files and software tools present on the system. A change is made to at least one of the data files and a determination is made as to whether that change is significant. If a significant change is made, then at least one propagation barrier is provided which is effective to prevent computer-implemented propagation of the change in said data file through at least one data file which is interdependent with the changed data file. In another embodiment, a computer readable medium containing program instructions for providing a run-time dependency management facility on a computer in which the run-time dependency facility is effective to generate under computer control a graph indicating relationships among the data files and the software tools residing on the system. The computer readable medium further includes program instructions for determining under computer control that the change to data in at least one of the data files is not a significant change. Finally the computer readable medium includes program instructions for generating at least one propagation barrier in response to the determination which is effective to prevent propagation of the changes in the data file through at least one data file which is interrelated with the changed data file. The above-described computer readable medium may also include program instructions for a clever tool which can determine whether changes made to the changed data file are significant.

Claims

1. A method for controlling the computer-implemented propagation of changes made to at least one data file throughout a system of interrelated data files resident on a computer system, said data files being interrelated by one or more software tools resident on said computer system, the method comprising the steps of:

a) providing a run-time dependency management facility on said computer system, said run-time dependency management facility being effective to generate under computer control a graph indicating relationships among said data files and said software tools;

b) changing data in at least one of said data files under computer control;

c) determining under computer control that said change to said data in said data file is not a significant change in response to said changing; and

d) activating under computer control at least one propagation barrier in response to said determination, said propagation barrier being effective to prevent computer-implemented propagation of said change in said data file through at least one data file which is interrelated with said data file.

2. The method of claim 1, wherein said propagation barrier is an input barrier which is activated in response to a determination that no significant change occurred since the last invocation of said tool.

3. The method of claim 2, wherein said step of activating said input barrier is performed by said run-time dependency management facility.

4. The method of claim 3, wherein said step of activating comprises sending a message from said run-time dependency management facility to said tools indicating that said input barrier is active.

5. The method of claim 4, wherein at least one of said tools activates an output barrier in response to said message from said run-time dependency management system.

6. The method of claim 2, wherein said propagation barrier is an output barrier which is activated in response to a determination that changes made to at least one of the output files of said tool is not a significant change.

7. The method of claim 6, wherein said step of determining that said change is not a significant change is performed by said tool.

8. The method of claim 7, wherein said tool notifies said run-time dependency facility that said change is not a significant change.

9. The method of claim 1, wherein said software tools are clever tools.

10. A computer system for controlling the computer-implemented propagation of changes made to at least one data file throughout a system of interrelated data files resident on a computer system, said data files being interrelated by one or more software tools resident on said computer system, said system comprising:

a) a run-time dependency management facility, said run-time dependency management facility being effective to generate under computer control a graph indicating relationships among said data files and said software tools;

b) an evaluator for determining under computer control that said change to said data in said data file is not a significant change, said evaluator being configured to be activated by a change in one of said data files; and

c) a propagation barrier activator for activating under computer control at least one propagation barrier in response to a determination by said evaluator that said change is not significant, wherein said propagation barrier is effective to prevent computer-implemented propagation of said change in said data file through at least one data file which is interdependent with said changed data file.

11. The computer system of claim 10, wherein said propagation barrier activator activates an input barrier in response to a determination by said evaluator that no significant change has occurred to said changed file since the last invocation of said tool.

12. The computer system of claim 11, wherein said propagation barrier activator activates an output barrier in response to a determination by said evaluator that said change is not a significant change.

13. The computer system of claim 10, wherein said tool is a clever tool.

14. A computer readable medium containing program instructions for:

a) providing a run-time dependency management facility on a computer system, said run-time dependency management facility being effective to generate under computer control a graph indicating relationships among interrelated data files and software tools resident on the computer system;

b) determining under computer control that said change to data in at least one of said data files is not a significant change, in response to said changing; and

c) activating under computer control at least one propagation barrier in response to said determination, said propagation barrier being effective to prevent computer-implemented propagation of said change in said data file through at least one data file which is interrelated with said changed data file.

15. The computer readable medium of claim 14, further including program instructions for activating an input barrier in response to a determination that said changed file is an input file for at least one of said tools and that no significant change occurred since the last invocation of said tool.

16. The computer readable medium of claim 15, further including program instructions for activating an output barrier in response to a determination that said changed file is an output file of at least one of said tools and that said change is not a significant change.

17. The computer readable medium of claim 14, further including program instructions for a clever tool.

18. The computer readable medium of claim 17, wherein said program instructions for said clever tool include instructions for determining whether changes to said changed data file are significant.

19. The computer readable medium of claim 18, wherein said program instructions for said clever tool include program instructions for indicating to said run-time dependency facility that said changes to said changed file are not significant.