Tools for stacking uncoordinated software projects

• US 20060036651A1
• Filed: 04/28/2005
• Published: 02/16/2006
• Est. Priority Date: 04/28/2004
• Status: Active Grant

• Current Assignee: Rogue Wave Software Incorporated (Perforce Software Incorporated)
• Original Assignee: OpenLogic, Inc. (Perforce Software Incorporated)
• Inventors: Cope, Rod, Weidner, Eric
• Granted Patent: US 7,661,089 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Abstract

A tool is provided for addressing a number of issues related to assembling software stacks including multiple uncoordinated components such as open source projects. The tool identifies individual projects for stacking, manages dependency relationships and provides an intuitive graphical interface to assist a user. A project filter is also provided for controlling access to or installation of projects in accordance with filter criteria. In this manner, compliance with internal policies regarding the use of open source or other software is facilitated.

Claims

1. A method for use in assembling stacks of software projects, comprising the steps of:

first operating a computer based tool to receive input information regarding a stack of interest;

second operating said computer based tool, responsive to said input information, to determine at least a first characteristic of a first project of said stack; and

third operating said computer based tool, based on said characteristic, to provide information regarding a second project of said stack.

2. A method as set forth in claim 1, wherein said step of first operating comprises receiving information identifying a function of said stack.

3. A method as set forth in claim 1, wherein said step of first operating comprises receiving information identifying said first project.

4. A method as set forth in claim 1, wherein said step of second operating comprises identifying one or more projects having a dependency relationship with said first project.

5. A method as set forth in claim 1, wherein said first project has a first vertical dependency such that another project is required for functionality of the first project as designed, and said step of third operating comprises identifying said second project as satisfying said first dependency.

6. A method as set forth in claim 5, wherein said computer based tool is further operative for identifying a third project as satisfying said first dependency.

7. A method as set forth in claim 6, wherein said computer based tool is further operative for identifying a fourth project as satisfying a second vertical dependency of said first project.

8. A method as set forth in claim 1, wherein said step of third operating comprises identifying said first project as satisfying a vertical dependency of said second project.

9. A method as set forth in claim 1, wherein said step of second operating comprises determining a resource requirement of said first project.

10. A method as set forth in claim 1, wherein said first and second projects are uncoordinated in that said first and second projects are free from any specific preconfiguration to cooperate in a stack.

11. A method as set forth in claim 1, wherein at least one of said first and second projects is an open source project.

12. A method as set forth in claim 1, wherein said step of third operating comprises providing status information regarding an installation of said second project.

13. A method as set forth in claim 1, wherein said step of third operating comprises employing a project filter to identify said second project, wherein said filter is operative to implement a policy concerning one of access to and use of a set of projects.

14. A method as set forth in claim 1, wherein at least one of said first and second projects operates at a tools or applications layer of said stack above an operating system level of said stack.

15. A method for use in assembling stacks of software projects, comprising the steps of:

identifying a first set of software projects;

determining, for said first set of software projects, a second set of dependency relationships relating to interoperation of said software projects;

providing a controller including logic for accessing information reflecting said second set of dependency relationships and relating particular ones of said software projects based on said dependency relationships;

receiving, at said controller, a user input indicating an interest in assembling a stack of projects and identifying, at least by type, at least a first project for inclusion in said stack; and

identifying, at said controller, at least a second project for inclusion in said stack based on said user input and said second set of dependency relationships.

16. A method as set forth in claim 15, wherein said first project has a first vertical dependency such that another project is required for functionality of the first project as designed, and said step of identifying comprises identifying said second project as satisfying said first dependency.

17. A method as set forth in claim 16, wherein said computer based tool is further operative for identifying a third project as satisfying said first dependency.

18. A method as set forth in claim 15, wherein said computer based tool is further operative for identifying a fourth project as satisfying a second vertical dependency of said first project.

19. A method as set forth in claim 15, wherein said first and second projects are uncoordinated in that said first and second projects are free from any specific preconfiguration to cooperate in a stack.

20. A method as set forth in claim 15, wherein at least one of said first and second projects is an open source project.

21. A method as set forth in claim 15, wherein said step of identifying comprises employing a project filter to identify said second project, wherein said filter is operative to implement a policy concerning one of access to and use of a set of projects.

22. A method as set forth in claim 15, wherein at least one of said first and second projects operates at a tools or applications layer of said stack above an operating system level of said stack.

23. A computer based tool for use in assembling stacks of software projects, comprising:

storage configured for storing dependency relationship information concerning interoperation of members of a set of software projects;

interface logic for receiving an input and providing an output related to assembly of a stack; and

processing logic for using said input to selectively access said storage to obtain a portion of said dependency relationship information and for outputting stack information based on said portion of said dependency relationship information.

24. A tool as set forth in claim 23, wherein said input identifies a function of said stack and said processing logic is operative to access said storage based on said identified function.

25. A tool as set forth in claim 23, wherein said input identifies a first project of said stack and said processing logic is operative to access said storage based on said first project.

26. A tool as set forth in claim 23, wherein said processing logic provides information identifying at least first and second projects of said stack, wherein said first and second projects are uncoordinated in that said first and second projects are free from any specific preconfiguration to cooperate in a stack.

27. A tool as set forth in claim 26, wherein at least one of said first and second projects is an open source project.

28. A tool as set forth in claim 26, wherein at least one of said first and second projects operates at a tools or applications layer of said stack above an operating system level of said stack.

29. A tool as set forth in claim 23, wherein said processing logic is operative to employ a project filter to identify one or more projects of said stack, wherein said filter is operative to implement a policy concerning one of access to and use of a set of projects.

30. A computer based tool for use in assembling stacks of uncoordinated open source software projects, comprising:

a knowledge base for storing current information regarding a first set of uncoordinated open source software projects, a second set of dependency relationships concerning interoperation of said open source software projects and a machine state relating to an installation status of said open source software projects for at least a first machine; and

a processing engine for receiving user inputs regarding assembly of a first stack, selectively accessing said knowledge base to obtain portions of said current information, and identifying at least one of said open source software projects for potential inclusion in said stack;

wherein said knowledge base and processing engine define an architecture for enabling updating of said current information regarding one or more of said open source software projects, dependency relationships and said machine state independent of modification of said processing engine.

31. A tool as set forth in claim 30, wherein said processing engine is operative to implement a project filter to identify said at least one of said open source software projects, wherein said filter is operative to implement a policy regarding one of access to and use of a set of projects.

32. A method for use in selecting software stacks of projects, comprising:

first operating a computer based tool to receive an input regarding a software stack of interest;

second operating said computer based tool to sue said input at least in part to select a first software stack from at least two software stacks;

wherein one of said at least two software stacks includes a first software project uncoordinated with at least one other software project contained in one of said at least two software stacks; and

third operating said computer based tool to transmit information regarding said first software stack.

33. A method as set forth in claim 32, wherein said input identifies one of a project and a function of said stack of interest.

34. A method as set forth in claim 32, wherein said step of operating comprises accessing storage including information regarding a number of stacks.

35. A method as set forth in claim 34, further comprising the step of storing said information regarding said number of stacks prior to receiving said input.

36. A method as set forth in claim 34, wherein said storage includes predetermined information regarding stacks, at least some of which include uncoordinated projects, wherein at least dependency relationships have been addressed in connection with determining said stacks, and said step of third operating comprises providing information for one of identifying and installing said first software stack.

37. A method for use in assembling a stack of uncoordinated software projects, comprising the steps of:

accessing a system for providing stack information regarding stacks of software projects including stacks of uncoordinated software projects;

submitting an input regarding a stack of interest; and

receiving stack information responsive to the input.

38. A method as set forth in claim 37, wherein said step of accessing comprises directing a request via a wide area network.

39. A method as set forth in claim 37, wherein said stack information includes one of:

an identification of the project content of one or more possible stacks;

projects for installation as one or more stacks; and

installation information for one or more stacks.