Tools for stacking uncoordinated software projects

• US 7,661,089 B2
• Filed: 04/28/2005
• Issued: 02/09/2010
• Est. Priority Date: 04/28/2004
• Status: Expired due to Fees

• Current Assignee: Rogue Wave Software Incorporated (Perforce Software Incorporated)
• Original Assignee: OpenLogic, Inc. (Perforce Software Incorporated)
• Inventors: Cope, Rod, Weidner, Eric
• Primary Examiner(s): Zhen; Wei Y
• Assistant Examiner(s): CHOW, CHIH CHING
• Application Number:
  US11/118,084
• Publication Number:
  US 20060036651A1
• Time in Patent Office: 1,748 Days
• Field of Search: 717/101, 717/106, 705/52
• US Class Current: 717/106
• 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 into a package multiple discrete software applications that are separately available from independent sources and that include at least one open source software application, comprising the steps of:

first operating a computer based tool to receive user input information regarding a first software application for inclusion in a package of interest, wherein said input information includes one of a description, function, and name associated with said first software application, and wherein said package of interest comprises two or more software applications that share one or more logical resources or are configured for cooperative and dependent operation;

second operating said computer based tool, responsive to said input information, to determine at least a first characteristic of said first software application of said package of interest, wherein said first characteristic identifies a related second software application for inclusion in said package of interest, and wherein said second software application has a vertical dependency relationship with said first software application, wherein at least one of said first and second software applications is an open source software application; and

third operating said computer based tool, based on said first characteristic, to output information regarding said second software application of said packages wherein said third operating comprises providing said output information regarding an assembly of said first and second software applications, and said computer based tool is further operative to repeat said steps of second and third operating until all software applications required of said package of interest are identified.

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

3. A method as set forth in claim 1, wherein said step of third operating comprises identifying said first software application as satisfying a vertical dependency of said all software applications.

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

5. A method as set forth in claim 1, wherein said first and second software applications are uncoordinated in that said first and second software applications are free from any specific preconfiguration to cooperate in a package of software applications.

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

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

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

9. A method as set forth in claim 1, wherein said receiving comprises receiving a request via a wide area network.

10. A computer based tool for use in assembling packages of software applications, comprising:

a knowledge base with storage configured for storing dependency relationship information concerning interoperation of members of a set of software applications, wherein said software applications include at least one open source software application, and wherein each of said software applications is produced by an independent source;

a user interface with interface logic for receiving an input and providing an output related to assembly of a package of software applications, wherein said package comprises two or more of said software applications that share one or more logical resources or are configured for cooperative and dependent operation; and

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

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

12. A tool as set forth in claim 10, wherein said input identifies a first software application of said package and said processing logic is operative to access said storage based on said first software application.

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

14. A tool as set forth in claim 13, wherein at least one of said first and second software applications is an open source software application.

15. A tool as set forth in claim 13, wherein at least one of said first and second software applications operates at a tools or applications layer of said package above an operating system level of said package.

16. A tool as set forth in claim 10, wherein said processing logic is operative to employ an application filter to identify one or more software applications of said package, wherein said filter is operative to implement a policy concerning one of access to and use of a set of software applications.