Managing hierarchies of components

• US 8,521,736 B2
• Filed: 10/26/2005
• Issued: 08/27/2013
• Est. Priority Date: 10/26/2005
• Status: Active Grant

• Current Assignee: Dassault Systemes Enovia Corporation (Dassault Systemes SA)
• Original Assignee: Dassault Systemes Enovia Corporation (Dassault Systemes SA)
• Inventors: Rigg, Dana, Reyfman, Semyon, Raghavan, Mahesh, Cox, Kenneth, Mastellone, Mitch
• Primary Examiner(s): SOMERS, MARC S
• Application Number:
  US11/259,739
• Publication Number:
  US 20070106708A1
• Time in Patent Office: 2,862 Days
• Field of Search: 715/514, 715/713, 707/203, 707/8, 707/201, 707/736, 707/829
• US Class Current: 707/736
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Described are methods, systems, and apparatus, including computer program products for managing a hierarchy of modules. A user can select a first hierarchy or a second hierarchy, where the first hierarchy includes a module and a first sub-module. The module is associated with a component and the first sub-module is associated with a first sub-component of the component. The module is associated with the first sub-module using a first hierarchical reference of a first type. The second hierarchy includes the module and a second sub-module, where the second sub-module is associated with the first sub-component. The module is associated with the second sub-module using a second hierarchical reference of a second type that is different from the first type.

Claims

1. A computerized method for managing a hierarchy of modules, the method comprising:

displaying a user interface that enables a user to select from a first hierarchy tangibly embodied in a machine-readable storage device and a second hierarchy tangibly embodied in a machine-readable storage device, the first hierarchy including a module and a first sub-module, the module including a first hierarchical reference of a first type and a second hierarchical reference of a second type different from the first type, the module being associated with a component, the first sub-module being associated with a first sub-component of the component, the module being associated with the first sub-module using the first hierarchical reference, the second hierarchy including the module and a second sub-module, the second sub-module being associated with the first sub-component, the module being associated with the second sub-module using the second hierarchical reference;

receiving, from a computer input device, a request from the user indicative of the first hierarchy or the second hierarchy; and

providing the first hierarchy or the second hierarchy to the user based on the request.

2. The method of claim 1, wherein the first and the second sub-modules are the same.

3. The method of claim 1, wherein the first and the second sub-modules are different.

4. The method of claim 1, wherein the first type of the first hierarchical reference comprises a static type and the second type of the second hierarchical reference comprises a dynamic type.

5. The method of claim 4, wherein the first hierarchical reference has a fixed association with the first sub-module.

6. The method of claim 5, wherein the fixed association is with a particular version number of the component.

7. The method of claim 4, wherein the second hierarchical reference has a changeable association with the second sub-module.

8. The method of claim 7, wherein the changeable association is with a changeable tag.

9. The method of claim 8, wherein the changeable tag is associated with the second sub-module.

10. The method of claim 8, wherein the changeable tag is associated with a branch, the branch comprising the first and the second sub-module.

11. The method of claim 10, wherein the first and the second sub-modules are different, the first sub-module created at a time earlier than the second sub-module.

12. The method of claim 7, wherein the changeable association is with a branch, the branch comprising the second sub-module.

13. The method of claim 12, wherein the first and the second sub-modules are different, the first sub-module created at a time earlier than the second sub-module.

14. The method of claim 4, further comprising providing the first hierarchy when the request is indicative of a static version of the module.

15. The method of claim 14, wherein the first hierarchy further includes a static version of the first sub-module.

16. The method of claim 14, the first hierarchy further including a static version of the first sub-module and a static version of a third sub-module, the third sub-module associated with a second sub-component different from the first sub-component, the module being associated with the third sub-module using a third hierarchical reference of a static or a dynamic type.

17. The method of claim 4, further comprising providing the second hierarchy when the request is indicative of a dynamic version of the module.

18. The method of claim 17, the second hierarchy further including a dynamic version of the second sub-module.

19. The method of claim 17, the second hierarchy further including a dynamic version of the second sub-module and a dynamic version of a third sub-module, the third sub-module associated with a second sub-component different from the first sub-component, the module being associated with the third sub-module using a third hierarchical reference of a static or a dynamic type.

20. The method of claim 4, wherein the second hierarchy further includes a third sub-module, the third sub-module associated with a second subcomponent different from the first sub-component, the module being associated with the third sub-module using a third hierarchical reference of a third type, the method further comprising providing the second hierarchy when the request is indicative of a hybrid version of the module, the second hierarchy further including a dynamic version of the second sub-module and a version of the third type of the third sub-module.

21. The method of claim 20, wherein the third type is a static type or a dynamic type.

22. The method of claim 1, wherein the module comprises files, data, or source code.

23. A system for managing a hierarchy of modules, the system comprising:

a computer database tangibly embodied in a machine-readable storage device including a first hierarchy of modules and a second hierarchy of modules, the first hierarchy including a module and a first sub-module, the module including a first hierarchical reference of a first type and a second hierarchical reference of a second type different from the first type, the module being associated with a component, the first submodule being associated with a first sub-component of the component, the module being associated with the first sub-module using the first hierarchical reference, the second hierarchy including the module and a second sub-module, the second sub-module being associated with the first sub-component, the module being associated with the second sub-module using the second hierarchical reference,

the computer database adapted to provide a user with a selection of the first hierarchy and the second hierarchy;

the computer database adapted to receive a request from a client over a network for selecting the first or the second hierarchy of modules,

the computer database adapted to transfer the first or the second hierarchy of modules to the client over the network based on the request.

24. A computer program product, tangibly embodied in a machine-readable storage device, the computer program product including instructions being operable to cause a data processing apparatus to:

provide a user with a selection of a first hierarchy of modules and a second hierarchy of modules, the first hierarchy including a module and a first sub-module, the module including a first hierarchical reference of a first type and a second hierarchical reference of a second type different from the first type, the module being associated with a component, the first sub-module being associated with a first sub-component of the component, the module being associated with the first sub-module using the first hierarchical reference, the second hierarchy including the module and a second sub-module, the second sub-module being associated with the first sub-component, the module being associated with the second sub-module using the second hierarchical reference;

receive a request from the user indicative of the first hierarchy or the second hierarchy; and

provide the first hierarchy or the second hierarchy to the user based on the request.