SYSTEMS AND METHODS FOR INCREMENTAL SOFTWARE DEVELOPMENT

• US 20120324417A1
• Filed: 06/20/2011
• Published: 12/20/2012
• Est. Priority Date: 06/20/2011
• Status: Active Grant

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: eBay Inc.
• Inventors: Somani, Mahesh K., Rethinakaleeswaran, Kumar, Saha, Debashis, Dodd, David William, Mathew, Suresh
• Granted Patent: US 8,856,724 B2
• Time in Patent Office: Days
• US Class Current: 717/101
• CPC Class Codes: G06F 11/368 for test version control, e.g. updating test cases to a new software version
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/41 Compilation
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44 Arrangements for executing specific programs

Abstract

Methods and systems for facilitating incremental software development are disclosed. For example, a method can include receiving a plurality of binary software libraries sufficient for building a software project. A request from a user to modify source code for at least one of the plurality of binary libraries is received, in response to receiving the request, the source code for the at least one of the plurality of binary libraries is retrieved. The source code for the at least one of the plurality of binary libraries is presented to the user. Modified source code for the at least one of the plurality of binary libraries is received. The modified source code is compiled to produce compiled modified code. A revised version of the software project is built using the compiled modified code and the plurality of binary libraries.

Claims

1. A method, comprising:

receiving a plurality of binary libraries sufficient for building a software project;

receiving a request from a user to modify source code for at least one of the plurality of binary libraries;

in response to receiving the request, retrieving the source code for the at least one of the plurality of binary libraries;

presenting the source code for the at least one of the plurality of binary libraries to the user;

receiving modified source code for the at least one of the plurality of binary libraries;

compiling the modified source code to produce compiled modified code; and

building a revised version of the software project using the compiled modified code and the plurality of binary libraries.

2. The method of claim 1, further comprising:

notifying the user if the modified source code necessitates a modification to any of those of the plurality of binary libraries not including the least one of the plurality of binary libraries.

3. The method of claim 2, the notifying of the user occurring while the user is modifying the source code.

4. The method of claim 2, the notifying of the user occurring after the user saves the modified source code.

5. The method of claim 1, further comprising:

retrieving dependency information identifying the plurality of binary libraries from among a second plurality of binary libraries comprising the plurality of binary libraries;

the receiving of the plurality of libraries comprising identifying the plurality of libraries based on the dependency information.

6. The method of claim 1, further comprising:

receiving a request to retrieve binary libraries associated with a code version identifier;

the receiving of the plurality of binary libraries comprising identifying the plurality of binary libraries based on the code version identifier.

7. The method of claim I, further comprising:

testing the revised version of the software project;

if the testing identifies a. failure, informing the user of the failure; and

if the testing does not identify a failure, identifying the binary libraries and the compiled modified code with a code version identifier associated with the revised version of the software project.

8. The method of claim 7, further comprising:

if the testing does not identify a failure, producing at least one revised binary library for the revised version of the software project;

storing the at least one revised binary library in a repository; and

associating the at least one revised binary library with the code version identifier.

9. A system comprising at least one processor and a plurality of modules providing instructions to be executed by the at least one processor, the modules comprising:

a repository to provide access to a plurality of binary libraries sufficient for building a software project;

a source control system to provide access to source code for the plurality of binary libraries; and

a development environment to retrieve the plurality of binary libraries from the repository, to receive a request from a user to modify source code for at least one of the plurality of binary libraries, to retrieve the source code for the at least one of the plurality of binary libraries from the source control system in response to the request, to present the source code for the at least one of the plurality of binary libraries to the user, to modify the source code for the at least one of the plurality of binary libraries in response to instructions from the user, to compile the modified source code to produce compiled modified code; and

to build a revised version of the software project using the compiled modified code and the plurality of binary libraries.

10. The system of claim 9, the development environment to notify the user if the modified source code necessitates a modification to any of those of the plurality of binary libraries not including the at least one of the plurality of binary libraries.

11. The system of claim 9:

the repository to provide access to other binary libraries in addition to the plurality of binary libraries; and

the development environment to generate dependency information identifying the plurality of binary libraries, and to retrieve the plurality of binary libraries based on the dependency information.

12. The system of claim 9, the development environment to receive a request to retrieve binary libraries associated with a code version identifier, and to retrieve the plurality of binary libraries by identifying the plurality of binary libraries via the repository based on the code version identifier.

13. The system of claim 9, the modules further comprising:

a validation environment to test the revised version of the software project, to inform the user if the testing identifies a failure, and to identify the binary libraries and the compiled modified code with a code version identifier associated with the revised version of the software project if the testing does not identify a failure.

14. The system of claim 13, the development environment to produce at least one revised binary library for the revised version of the software project if the testing does not identify a failure, to store the at least one revised binary library via the repository, and to associate the at least one revised binary library with the code version identifier.

15. The system of claim 14, the development environment to store the at least one revised binary library via the repository by associating each of the at least one revised binary libraries with each software project in which the associated at least one revised binary library is employed.

16. A non-transitory machine-readable storage medium having instructions encoded thereon which, when executed by at least one processor, cause the at least one processor to:

receive a plurality of binary libraries sufficient for building a software project;

receive a request from a user to modify source code for at least one of the plurality of binary libraries;

in response to receiving the request, retrieve the source code for the at east one of the plurality of binary libraries;

present the source code for the at least one of the plurality of binary libraries to the user;

receive modified source code for the at least one of the plurality of binary libraries;

compile the modified source code to produce compiled modified code; and

build a revised version of the software project using the compiled modified code and the plurality of binary libraries.

17. The non-transitory machine-readable storage medium of claim 16, wherein the instructions cause the at least one processor to notify the user if the modified source code necessitates a modification to any of those of the plurality of binary libraries not including the at least one of the plurality of binary libraries.

18. The non-transitory machine-readable storage medium of claim 16, wherein the instructions cause the at least one processor to receive a request to retrieve binary libraries associated with a code version identifier, and to retrieve the plurality of binary libraries by identifying the plurality of binary libraries from a repository based on the code version identifier.

19. The non-transitory machine-readable storage medium of claim 16, wherein the instructions cause the at least one processor to:

test the revised version of the software project;

if the testing identifies a failure, inform the user of the failure; and

if the testing does not identify a failure, identify the binary libraries and the compiled modified code with a code version identifier associated with the revised version of the software project.

20. The non-transitory machine-readable storage medium of claim 19, wherein the instructions cause the at least one processor to:

if the testing does not identify a failure, produce at least one revised binary library for the revised version of the software project;

store the at least one revised binary library in a repository; and

associate the at least one revised binary library with the code version identifier.