System and method for active configuration management

• US 20030200098A1
• Filed: 04/12/2002
• Published: 10/23/2003
• Est. Priority Date: 04/12/2002
• Status: Active Grant

• Current Assignee: Telelogic Technologies North America, Inc.
• Original Assignee: Telelogic Technologies North America, Inc.
• Inventors: Weber, Darcy L. Wiborg, Crane, Patrick C., Gillibrand, Jay C., Smith, Philip Steven Alexander, Geipel, Barry L.
• Granted Patent: US 7,644,392 B2
• Time in Patent Office: Days
• US Class Current: 705/1
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A system and method for active configuration management of the components of a data repository maintained in memory of a computer system is disclosed herein. The method includes creating a plurality of file system event objects in response to the occurrence of a corresponding plurality of events associated with ones of the components. A plurality of file system event objects are then entered into an event queue. Next, a sequence of configuration management (CM) operations involving identified ones of the components are executed on the basis of corresponding ones of the file system event objects

Claims

1. A method for active configuration management of components of a data repository maintained in memory of a computer system, said method comprising:

creating a plurality of file system event objects in response to the occurrence of a corresponding plurality of events associated with ones of said components;

entering said plurality of file system event objects into an event queue; and

executing a sequence of configuration management (CM) operations involving identified ones of said components on the basis of corresponding ones of said file system event objects.

2. The method of claim 1 further including setting a result time upon entry of a first of said file system event objects into said event queue, said first of said file system event objects being transferred from said event queue to a command queue upon expiration of said result time.

3. The method of claim 1 further including creating a new file system event object based upon first and second related ones of said file system event objects, said new file system event object replacing said first and second related ones of said file system event objects and being inserted into a predefined position within said event queue.

4. The method of claim 1 further including filtering said plurality of file system event objects in order to identify selected ones of said file system event objects to be monitored, said selected ones of said file system event objects being transferred from said event queue said command queue.

5. The method of claim 4 wherein said selected ones of said file system event objects includes said first of said file system event objects, said first of said file system event objects being transferred to said event queue to said command queue upon expiration of a result time associated with said first of said file system event objects.

6. The method of claim 4 wherein said sequence of configuration management operations are executed in response to a corresponding sequence of said selected ones of said file system event objects within said command queue.

7. The method of claim 1 further including comparing an additional file system event object associated with a first of said components to each of said plurality of file system objects within said event queue and identifying one of said plurality of file system objects also associated with said first of said components, said one of said plurality of file system objects being replaced with a new file system object based upon said additional file system event object and said one of said plurality of file system objects.

8. The method of claim 1 wherein a first of said file system event objects is a ModifyEvent object indicative of modification of a first of said components into a modified component, said ModifyEvent object resulting in execution of a first of said CM operations disposed to synchronize said modified component with a preexisting version of said first of said components.

9. The method of claim 8 further including checking a directory structure in order to identify said preexisting version of said first of said components and determine whether said preexisting version of said first of said components is a controlled component.

10. The method of claim 8 further including augmenting a directory structure to include said modified component when said preexisting version of said first of said components is determined not to be a controlled component.

11. The method of claim 1 wherein a first of said file system event objects is a RemoveEvent object, said RemoveEvent object resulting in execution of a first of said CM operations disposed to remove a corresponding first of said components from a current project.

12. The method of claim 11 further including identifying said first of said components corresponds as a directory structure and deleting all subdirectories and files assoicated with said directory structure.

13. The method of claim 1 wherein a first of said file system event objects is a RenameEvent object, said RenameEvent object resulting in execution of one of said CM operations disposed to remove one of said components corresponding to said RenameEvent object from a current project when said one of said components is determined to be a controlled component.

14. The method of claim 13 wherein said one of said CM operations invokes another of said CM operations disposed to effect component synchronization when said one of said components is determined not to be a controlled component.

15. The method of claim 13 wherein said one of said CM operations invokes another of said CM operations disposed to effect component synchronization when a preexisting version of said one of said components is determined to exist in a work area.

16. A system for active configuration management of components of a data repository maintained in memory of a computer system, said system comprising:

a file system monitor module capable of being instantiated into a plurality of file system event objects in response to the occurrence of a corresponding plurality of events associated with ones of said components;

an event queue into which are entered said plurality of file system event objects;

a listener module, in communication with said file system monitor module and said event queue, for generating a plurality of active configuration management (CM) commands on the basis of said plurality of file system event objects; and

a command queue for storing said plurality of active CM commands, thereby facilitating execution of a corresponding plurality of configuration management (CM) operations involving said components.

17. The system of claim 16 further including means for setting a result time upon entry of a first of said file system event objects into said event queue, said first of said file system event objects being transferred from said event queue to a command queue upon expiration of said result time.

18. The system of claim 16 wherein said file system monitor module is operative to create a new file system event object based upon first and second related ones of said file system event objects, said new file system event object replacing said first and second related ones of said file system event objects and being inserted into a predefined position within said event queue.

19. The system of claim 16 further including filtering said plurality of file system event objects in order to identify selected ones of said file system event objects to be monitored, said selected ones of said file system event objects being transferred from said event queue said command queue.

20. A method for facilitating active configuration management of components of a data repository maintained in memory of a computer system, said method comprising:

creating a plurality of file system event objects in response to the occurrence of a corresponding plurality of events associated with ones of said components;

entering said plurality of file system event objects into an event queue; and

generating a plurality of active configuration management (CM) commands on the basis of said plurality of file system event objects, said plurality of active CM commands capable of being executed to perform a corresponding plurality of configuration management (CM) operations involving said components.

21. The method of claim 20 further including storing said plurality of active CM commands within a command queue.

22. The method of claim 21 further including setting a result time upon entry of a first of said file system event objects into said event queue, said first of said file system event objects being transferred from said event queue to said command queue upon expiration of said result time.

23. The method of claim 20 further including creating a new file system event object based upon first and second related ones of said file system event objects, said new file system event object replacing said first and second related ones of said file system event objects and being inserted into a predefined position within said event queue.