Distributed software development tool

• US 7,331,034 B2
• Filed: 01/09/2001
• Issued: 02/12/2008
• Est. Priority Date: 01/09/2001
• Status: Active Grant

• Current Assignee: Leverage Rock, LLC
• Original Assignee: Thomas G. Anderson
• Inventors: Anderson, Thomas G.
• Primary Examiner(s): Chaki; Kakali
• Assistant Examiner(s): ROCHE, TRENTON J
• Application Number:
  US09/756,819
• Publication Number:
  US 20020144255A1
• Time in Patent Office: 2,590 Days
• Field of Search: 705/51, 705/52, 705/37, 705/39, 705/59, 709/203, 709/205, 707/203, 707/9, 707/10, 717/100, 717/103, 717/120, 717/108, 717/106
• US Class Current: 717/103
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A tool for distributed software development maintains a pool of software modules. A module manager manages submissions to and downloads from the pool. The module manager can be a computer system with programming and resources suited for managing the pool. Developers and users can access the module manager via a computer network such as the internet, or via other transmission mechanisms. A developer intending to submit a module to the pool can specify access conditions associated with the module, and transmit information needed to access the module. The module manager can add the access information and access conditions to the pool. A developer or user intending to access a module from the pool can identify a desired module. The module manager can then determine if the intended access complies with the access conditions associated with the desired module. If it does, then the module manager can transmit the access information.

Claims

1. A method of using a computer network to facilitate distributed software development, using a pool of software modules maintained with a module manager, comprising the steps of:

a) establishing a connection via said network between a user computer and a module manager (“

connect”

step);

b) accepting at the module manager an indication from the user computer specifying a submission or a download (“

mode”

step);

c) if the indication specifies a submission, then (collectively “

submission”

step);

i) accepting at the module manager from the user computer access conditions (“

SAC”

) related to a submit software module (“

SSM”

) for submission to said pool (“

submit conditions”

step);

ii) accepting at the module manager from the user computer access information (“

SAI”

) related to the SSM (“

submit access”

step);

iii) storing at the module manager the SAC and SAI as part of said pool (“

pool addition”

step);

d) If the indication indicates a download, then (collectively “

download”

step);

i) accepting at the module manager information from the user computer identifying a download software module (“

DSM”

) to be downloaded from said pool (“

identify download”

step);

ii) accessing from the pool the access conditions (“

DAC”

) associated with the DSM, and accepting at the module manager information from the user computer indicating that the DSM are accepted (“

download conditions”

step);

iii) accessing from the pool the access information (“

DAI”

) corresponding to the DSM, and communicating the DAI from the module manager to the user computer (“

transmit download”

step);

e) wherein said SAC include at least one of;

i) subsequent distribution limited to object code;

ii) subsequent distribution only allowed on payment of a fee;

iii) subsequent distribution to downloaders for research use is allowed on payment of a fee lower than distribution to downloaders for commercial use;

iv) distribution from the module pool is allowed, but further distribution by downloaders from the module pool is prohibited;

v) distribution from the module pool is allowed, but further distribution by downloaders is allowed only after payment of a fee.

2. The method of claim 1, wherein said computer network comprises the internet.

3. The method of claim 1, further comprising maintaining a user database of users and associated access privileges, and wherein the connect step comprises:

a) accepting information at the module manager identifying a user of the user computer;

b) storing the SAC and SAI only if the access privileges corresponding to said user indicate that said user is allowed to submit the SSM;

c) communicating the DAI only if the access privileges corresponding to said user indicate that said user is allowed to download the DSM.

4. The method of claim 1, wherein the submit conditions step comprises communicating from the module manager to the user computer a set of allowable access conditions, and accepting information at the module manager from the user computer specifying selections from said set.

5. The method of claim 1, wherein the download conditions step further comprises accessing pool access conditions (“

PAC”

) from the module manager, and accepting at the module manager from the user computer an indication that the PAC are accepted.

6. The method of claim 5, wherein the PAC comprises permission to modify the DSM and prohibition against distributing modifications anywhere except the module pool.

7. The method of claim 1, wherein said SAC include an indication of whether or not a software module is available for commercialization.

8. The method of claim 1, wherein the submit access step comprises accepting at the module manager the SSM from the user computer.

9. The method of claim 1, wherein the submit access step comprises accepting at the module manager a computer network identifier identifying a computer from which the SSM can be accessed.

10. The method of claim 1, wherein the submission step further comprises using electronic commerce contracting to transfer intellectual property rights corresponding to the SAC and the SSM.

11. The method of claim 1, wherein said pool comprises a database of software module access information and corresponding access conditions, and wherein the pool addition step comprises adding corresponding entries to the database.

12. The method of claim 1, wherein the identify download step comprises:

a) communicating from the module manager to the user computer descriptions related to software modules in said pool;

b) accepting at the module manager information from the user computer specifying selection of a download software module.

13. The method of claim 1, wherein the identify download step comprises:

a) accepting at the module manager information from the user computer specifying characteristics of a desired software module;

b) determining a set of software modules in said pool having said characteristics;

c) communicating from the module manager to the user computer descriptions related to software modules in said set;

d) accepting at the module manager information from the user computer specifying selection of a download software module from said set.

14. The method of claim 1, wherein the download conditions step comprises:

a) communicating the DAC from the module manager to the user computer;

b) accepting at the module manager a confirmation that the DAC are accepted.

15. The method of claim 1, wherein the download conditions step comprises storing at the module manager a record of said acceptance and said communication of the DAI.

16. The method of claim 1, wherein the transmit download step comprises communicating the DSM directly from the module manager to the user computer.

17. The method of claim 1, wherein the transmit download step comprises communicating a computer identifier identifying a computer where the DSM can be accessed.

18. The method of claim 1, wherein the download step further comprises using electronic commerce contracting to transfer intellectual property rights corresponding to the DAC and the DSM.

19. The method of claim 1, wherein the SAC comprise fee information associated with access to the SSM.

20. The method of claim 19, wherein the download step further comprises communicating the fee information associated with the DSM to the user computer, and accepting payment complying with the fee information at the module manager before communicating the DAI.

21. The method of claim 19, further comprising, when a module is downloaded, storing in a fee-database information related to the download if indicated by the DAC, and wherein the download step further comprises determining a fee from the fee-database and the DAC.

22. The method of claim 21, wherein the download step further comprises communicating said fee to the user computer, and accepting payment complying with the fee at the module manager before communicating the DAI.

25. The method of claim 1, wherein the download step allows download of a plurality of modules, and further comprising determining a fee associated with the download of the plurality of modules, where the fee is allocated among modules according to

$F_j=F_T$

W T ⁢

w j ⁢

v j ∑

i ⁢

w i ⁢

v i ,

where F_T is the total fee, W_T is a proportion of the total fee to be allocated among modules, F_j is the fee allocated to module j, v_i is an indication of the value of module i, and w_i is a weighting applied to the value of module i, and wherein modules submitted early in the module pool have a larger w_i than they would have received had they been submitted later.

23. A method of using a computer network to facilitate distributed software development, using a pool of software modules maintained with a module manager, comprising the steps of:

a) establishing a connection via said network between a user computer and a module manager (“

connect”

step);

b) accepting at the module manager an indication from the user computer specifying a submission or a download (“

mode”

step);

c) if the indication specifies a submission, then (collectively “

submission”

step);

i) accepting at the module manager from the user computer access conditions (“

SAC”

) related to a submit software module (“

SSM”

) for submission to said pool (“

submit conditions”

step);

ii) accepting at the module manager from the user computer access information (“

SAI”

) related to the SSM (“

submit access”

step);

iii) storing at the module manager the SAC and SAI as part of said pool (“

pool addition”

step);

d) If the indication indicates a download, then (collectively “

download”

step);

i) accepting at the module manager information from the user computer identifying a download software module (“

DSM”

) to be downloaded from said pool (“

identify download”

step);

ii) accessing from the pool the access conditions (“

DAC”

) associated with the DSM, and accepting at the module manager information from the user computer indicating that the DSM are accepted (“

download conditions”

step);

iii) accessing from the pool the access information (“

DAI”

) corresponding to the DSM, and communicating the DAI from the module manager to the user computer (“

transmit download”

step);

e) further comprising, when a module is downloaded, storing in a fee-database information related to the download if indicated by the DAC, and wherein the download step further comprises determining a fee from the fee-database and the DAC;

f) wherein the download step further comprises communicating said fee to the user computer, and accepting payment complying with the fee at the module manager before communicating the DAI;

g) wherein the fee is determined from an indication of the demand for the DSM, wherein the indication of demand increases with increasing number of downloads of the module, and decreases with increasing numbers of downloads of other modules from the pool.

24. The method of claim 23, wherein the effect of an individual download of the module on the indication of demand decreases with increasing time elapsed since said download, and wherein the effect of an individual download of another module decreases with increasing time elapsed since said download.

26. A method of using a computer to accept software modules into a module pool, comprising the steps of:

a) accepting access conditions (“

SAC”

) related to a submit software module (“

SSM”

) for submission to said pool (“

submit conditions”

step);

b) accepting access information (“

SAI”

) related to the SSM (“

submit access”

step);

c) storing at the computer the SAC and SAI as part of said pool (“

pool addition”

step);

d) wherein said SAC include at least one of;

i) subsequent distribution limited to object code;

ii) subsequent distribution only allowed on payment of a fee;

iii) subsequent distribution to downloaders for research use is allowed on payment of a fee lower than distribution to downloaders for commercial use;

iv) distribution from the module pool is allowed, but further distribution by downloaders from the module pool is prohibited;

v) distribution from the module pool is allowed, but further distribution by downloaders is allowed only after payment of a fee.

27. The method of claim 26, further comprising maintaining a user database of users and associated access privileges, and wherein the pool addition step comprises storing the SAC and SAI only if the access privileges corresponding to said user indicate that said user is allowed to submit the SSM.

28. The method of claim 26, wherein the submit conditions step comprises communicating a set of allowable access conditions, and accepting information specifying selections from said set.

29. The method of claim 26, wherein said SAC include an indication of whether or not a software module is available for commercialization.

30. The method of claim 26, wherein the submit access step comprises accepting the SSM from the user computer.

31. The method of claim 26, wherein the submit access step comprises accepting an identifier indicating how the SSM can be accessed.

32. The method of claim 26, wherein said pool comprises a database of software module access information and corresponding access conditions, and wherein the pool addition step comprises adding corresponding entries to the database.

37. The method of claim 30, wherein the PAC comprises permission to modify the DSM and prohibition against distributing modifications anywhere except the module pool.

33. A method of using a computer network to manage access to a pool of software modules, wherein the pool comprises entries having module access conditions and module access information, comprising the steps of:

a) accepting information identifying a download software module (“

DSM”

) to be downloaded from said pool (“

identify download”

step);

b) accessing from the pool access conditions (“

DAC”

) associated with the DSM, and accepting information indicating that the DSM are accepted (“

download conditions”

step);

c) accessing from the pool the access information (“

DAI”

) corresponding to the DSM, and communicating the DAI (“

transmit download”

step);

d) wherein the download step further comprises communicating fee information associated with the DSM, and accepting payment complying with the fee information before communicating the DAI; and

e) wherein the fee is determined from an indication of the demand for the DSM, wherein the indication of demand increases with increasing number of downloads of the module, and decreases with increasing numbers of downloads of other modules from the pool.

34. The method of claim 33, further comprising maintaining a user database of users and associated access privileges, and wherein the transmit download step comprises communicating the DAI only if the access privileges corresponding to said user indicate that said user is allowed to download the DSM.

35. The method of claim 33, wherein the submit conditions step comprises communicating a set of allowable access conditions, and accepting information specifying selections from said set.

36. The method of claim 33, wherein the download conditions step further comprises accessing pool access conditions (“

PAC”

), and accepting an indication that the PAC are accepted.

38. The method of claim 33, wherein the identify download step comprises:

a) communicating descriptions related to software modules in said pool;

b) accepting information specifying selection of a download software module.

39. The method of claim 33, wherein the identify download step comprises:

a) accepting information specifying characteristics of a desired software module;

b) determining a set of software modules in said pool having said characteristics;

c) communicating descriptions related to software modules in said set;

d) accepting information specifying selection of a download software module from said set.

40. The method of claim 33, wherein the download conditions step comprises:

a) communicating the DAC;

b) accepting a confirmation that the DAC are accepted.

41. The method of claim 33, wherein the download conditions step comprises storing a record of said acceptance and said communication of the DAI.

42. The method of claim 33, wherein the transmit download step comprises communicating the DSM directly.

43. The method of claim 33, wherein the transmit download step comprises communicating a computer identifier identifying a computer where the DSM can be accessed.

44. The method of claim 33, wherein the download step further comprises using electronic commerce contracting to transfer intellectual property rights corresponding to the DAC and the DSM.

45. The method of claim 33, wherein the download step further comprises communicating fee information associated with the DSM, and accepting payment complying with the fee information before communicating the DAI.

46. The method of claim 33, further comprising, when a module is downloaded, storing in a fee-database information related to the download if indicated by the DAC, and wherein the download step further comprises determining a fee from the fee-database and the DAC.

47. The method of claim 45, wherein the download step further comprises communicating said fee, and accepting payment complying with the fee before communicating the DAI.

48. The method of claim 33, wherein the effect of an individual download of the module on the indication of demand decreases with increasing time elapsed since said download, and wherein the effect of an individual download of another module decreases with increasing time elapsed since said download.

49. A method of using a computer network to manage access to a pool of software modules, wherein the pool comprises entries having module access conditions and module access information, comprising the steps of:

a) accepting information identifying a download software module (“

DSM”

) to be downloaded from said pool (“

identify download”

step);

b) accessing from the pool access conditions (“

DAC”

) associated with the DSM, and accepting information indicating that the DSM are accepted (“

download conditions”

step);

c) accessing from the pool the access information (“

DAI”

) corresponding to the DSM, and communicating the DAI (“

transmit download”

step);

d) wherein the download step allows download of a plurality of modules, and further comprising determining a fee associated with the download of the plurality of modules, where the fee is allocated among modules according to

$F_j=F_T<br><br>W_T<br><br>\frac{w_j<br><br>v_j}{{\sum <br><br>}_i<br><br>w_i<br><br>v_i},$

where F_T is the total fee, W_T is a proportion of the total fee to be allocated among modules, F_j is the fee allocated to module j, v_i is an indication of the value of module i, and w_i is a weighting applied to the value of module i, and wherein modules submitted early in the module pool have a larger W_i than they would have received had they been submitted later.

50. A method of using a computer to facilitate distributed software development, comprising:

a) Accepting submitted software modules at a module manager, wherein accepting a submitted software module comprises;

i) Accepting access conditions specifying conditions for use of the submitted module;

ii) Accepting access information specifying how to access the submitted module;

iii) Storing the access conditions and access information as related entries in a database;

b) Allowing access by users to modules from the module manager, wherein allowing a user access to modules comprises;

i) Determining a desired software module from the database to be accessed;

ii) Determining if the user'"'"'s desired access complies with the access conditions associated with the desired software module, and, if so, then communicating the access information associated with the desired module to the user;

c) wherein accepting access conditions for a submitted module comprises accepting an indication of whether or not the module is available for commercialization; and

wherein allowing access to modules comprises determining if the user desires access to a set of modules for commercialization, and, if so, then determining an apportionment of fees from commercialization according to

$F_j=F_T<br><br>W_T<br><br>\frac{w_j<br><br>v_j}{{\sum <br><br>}_i<br><br>w_i<br><br>v_i},$

where F_T is the total fee, W_T is a proportion of the total fee to be allocated among modules, F_j is the fee allocated to module j, v_i is an indication of the value of module i, and w_i is a weighting applied to the value of module i, and wherein modules submitted early in the module pool have a larger w, than they would have received had they been submitted later.

51. A method of using a computer to facilitate distributed software development, comprising:

a) Accepting submitted software modules at a module manager, wherein accepting a submitted software module comprises;

i) Accepting access conditions specifying conditions for use of the submitted module;

ii) Accepting access information specifying how to access the submitted module;

iii) Storing the access conditions and access information as related entries in a database;

b) Allowing access by users to modules from the module manager, wherein allowing a user access to modules comprises;

i) Determining a desired software module from the database to be accessed;

ii) Determining if the user'"'"'s desired access complies with the access conditions associated with the desired software module, and, if so, then communicating the access information associated with the desired module to the user;

c) wherein modules in the pool are characterized by membership in one of three classes, wherein the first class denotes modules not available for commercialization, the second class denotes modules available for commercialization, and the third class denotes modules available for commercialization and having a higher quality than modules in the second class.