Method for competitive peer programming

• US 20050120334A1
• Filed: 03/11/2004
• Published: 06/02/2005
• Est. Priority Date: 11/27/2003
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Deboer, Timothy G.
• Application Number:
  US10/798,915
• Publication Number:
  US 20050120334A1
• Time in Patent Office: Days
• US Class Current: 717/120
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A method for competitive peer programming provides for multiple software developers to make changes to a common body of source code concurrently. A first developer makes changes to a section of source code resulting in modified code. The modified code is made accessible to other developers. The modified code is tested and a test result is compared with a reference test result. Based on the comparison a second developer can choose to change a section of source code thereby replacing the modified code. The steps of making the modified code accessible, testing the modified code, comparing the test results and determining if further changes are desired can be repeated any number of times with the first and second developers exchanging roles. The method according to the present invention enables improved interactions between multiple software developers and enables multiple developers to work on a section of source code concurrently.

Claims

1. A method for competitive peer programming in an environment where each of a first and a second developer can make changes to any of a plurality of sections of source code comprising the steps of:

a) enabling said first developer to make changes to a first section of source code thereby producing a modified section of code;

b) providing access to said modified section of code;

c) enabling testing of said modified section of code to produce a test result;

d) enabling comparison of said test result with a reference test result; and

e) based on the comparison of step d), enabling said second developer to make changes to a second section of source code thereby replacing said modified section of code and repeating steps b) through e) with said first and said second developers exchanging roles, until said comparison indicates no further changes are required.

2. The method of claim 1, wherein said first section of source code and said second section of source code are different sections.

3. The method of claim 1, wherein said first section of source code and said second section of source code are the same section.

4. The method of claim 1, wherein said reference test result is produced from a version of said first section of source code before said changes were made.

5. The method of claim 1, wherein said reference test result is produced from a version of said second section of source code before said changes are made.

6. The method of claim 1, wherein a third developer can make changes to any of a plurality of sections of source code and steps b) through e) are executed separately with said second developer being replaced by said third developer.

7. A computer program product for competitive peer programming in an environment where each of a first and a second developer can make changes to any of a plurality of sections of source code, the computer program product comprising:

computer readable program code devices for;

a) enabling said first developer to make changes to a first section of source code thereby producing a modified section of code;

b) providing access to said modified section of code;

c) enabling testing of said modified section of code to produce a test result;

d) enabling comparison of said test result with a reference test result; and

e) based on the comparison of step d), enabling said second developer to make changes to a second section of source code thereby replacing said modified section of code and repeating steps b) through e) with said first and said second developers exchanging roles, until said comparison indicates no further changes are required.

8. The computer program product of claim 7, wherein said first section of source code and said second section of source code are different sections.

9. The computer program product of claim 7, wherein said first section of source code and said second section of source code are the same section.

10. The computer program product of claim 7, wherein said reference test result is produced from a version of said first section of source code before said changes are made.

11. The computer program product of claim 7, wherein said reference test result is produced from a version of said second section of source code before said changes are made.

12. The computer program product of claim 7, wherein a third developer can make changes to any of a plurality of sections of source code and steps b) through e) are executed separately with said second developer being replaced by said third developer.

13. A method for competitive peer programming in an environment where each of a first and a second developer can make changes to any of a plurality of sections of source code comprising the steps of:

a) making changes to a first section of source code thereby producing a modified section of code, wherein said changes are made by said first developer;

b) accessing said modified section of code;

c) testing said modified section of code to produce a test result;

d) comparing said test result with a reference test result; and

e) based on the comparison of step d), making changes to a second section of source code thereby replacing said modified section of code, wherein said changes are made by said second developer, and repeating steps b) through e) with said first and said second developers exchanging roles, until said comparison indicates no further changes are required.

14. The method of claim 13, wherein said first section of source code and said second section of source code are different sections.

15. The method of claim 13, wherein said first section of source code and said second section of source code are the same section.

16. The method of claim 13, wherein said reference test result is produced from a version of said first section of source code before said changes were made.

17. The method of claim 13, wherein said reference test result is produced from a version of said second section of source code before said changes are made.

18. The method of claim 13, wherein a third developer can make changes to any of a plurality of sections of source code and steps b) through e) are executed separately with said second developer being replaced by said third developer.