Systems and methods for incremental software development

• US 10,019,256 B2
• Filed: 10/28/2015
• Issued: 07/10/2018
• Est. Priority Date: 06/20/2011
• Status: Active Grant

• Current Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Original Assignee: PayPal, Inc. (PayPal Holdings, Inc.)
• Inventors: Somani, Mahesh K., Rethinakaleeswaran, Kumar, Saha, Debashis, Dodd, David William, Mathew, Suresh
• Primary Examiner(s): Rampuria, Satish
• Application Number:
  US14/925,446
• Publication Number:
  US 20160048391A1
• Time in Patent Office: 986 Days
• Field of Search: 717101-126
• 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:

storing, in a repository, a plurality of binary libraries, a set of binary libraries of the plurality of binary libraries being associated, via dependency metadata, with a checkpoint of a first project;

generating a second project from the checkpoint of the first project;

responsive to the generating of the second project, providing to a development environment, by a processor of a machine, the set of binary libraries associated with the checkpoint of the first project without providing source code;

receiving a request to modify source code associated with a first binary library of the plurality of binary libraries;

responsive to the request, providing the source code associated with the first binary library to the development environment;

receiving, from the development environment, modified source code associated the first binary library;

identifying a second binary library of the plurality of binary libraries based on dependency metadata of the second binary library that indicates a dependency of the second binary library on the modified source code;

determining, based on the identification of the second binary library, that the modified source code necessitates a modification to the second binary library; and

in response to the determination, providing the source code associated with the second binary library to the development environment.

2. The method of claim 1, wherein the checkpoint of the first project is associated with a particular feature, functionality, or performance level.

3. The method of claim 1, further comprising:

in response to the determination, providing, by the development environment, a notification that the modified source code necessitates the modification to the second binary library.

4. The method of claim 3, wherein the notification is provided while a user is modifying the source code.

5. The method of claim 1, further comprising:

compiling the modified source code to produce compiled source code;

building a revised version of the second project using the compiled modified code and the plurality of binary libraries;

testing the revised version of the second project; and

based on results of the testing, updating dependency data for the second project.

6. A system comprising:

a memory having instructions embodied thereon;

one or more processors communicatively coupled to the memory and configured to, in response to executing the instructions, perform or control performance of operations, the operations comprising;

storing, in a repository, a set of binary libraries being associated, via dependency metadata, with a checkpoint of a first project;

generating a second project from the checkpoint of the first project;

responsive to the generating of the second project, providing to a development environment the set of binary libraries associated with the checkpoint of the first project;

receiving a request to modify source code associated with a first binary library of the set of binary libraries;

providing the source code associated with the first binary library of the set of binary libraries to the development environment;

receiving, from the development environment, modified source code for the first binary library;

identifying a second binary library of the set of binary libraries based on dependency metadata of the second binary library that indicates a dependency of the second binary library on the modified source code; and

providing source code associated with the second binary library of the set of binary libraries to the development environment in response to determining that the modified source code necessitates a modification to the second binary library.

7. The system of claim 6, wherein the checkpoint of the first project is associated with a particular feature, functionality, or performance level.

8. The system of claim 6, further comprising:

compiling the modified source code to produce compiled source code;

building a revised version of the second project using the compiled modified code and the set of binary libraries;

testing the revised version of the second project; and

based on results of the testing, updating dependency data for the second project.

9. The system of claim 6, further comprising:

in response to the determination, providing, by the development environment, a notification that the modified source code necessitates the modification to the second binary library.

10. The system of claim 9, wherein the notification is provided while a user is modifying the source code.

11. A non-transitory machine-readable medium having instructions embodied thereon, which, when executed by one or more processors of a system, cause the system to perform or control performance of operations comprising:

providing to a development environment a set of binary libraries;

receiving a request to modify source code associated with a first binary library of the set of binary libraries;

providing the source code associated with the first binary library of the set of binary libraries to the development environment;

receiving, from the development environment, modified source code for the first binary library;

identifying a second binary library of the set of binary libraries based on dependency metadata of the second binary library that indicates a dependency of the second binary library on the modified source code; and

determining, based on the identification of the second binary library, that the modified source code necessitates a modification to the second binary library;

in response to the determination, providing, by the development environment, a notification that the modified source code necessitates the modification to the second binary library; and

providing source code associated with the second binary library of the set of binary libraries to the development environment upon determining the source code associated with a first binary library has been modified, the second binary library being dependent on the first binary library.

12. The non-transitory machine-readable medium of claim 11, wherein the set of binary libraries is associated with a checkpoint of a project and the checkpoint of the project is associated with a particular feature, functionality, or performance level.

13. The non-transitory machine-readable medium of claim 11, further comprising:

compiling the modified source code to produce compiled source code;

building a revised version of a project using the compiled modified code and the set of binary libraries;

testing the revised version of the project; and

based on results of the testing, updating dependency data for the project.