AccessMyLibrary provides FREE access to millions of articles from top publications available through your library.

The case for collaborative programming.

Communications of the ACM

| March 01, 1998 | Nosek, John T. | COPYRIGHT 1987 Association for Computing Machinery, Inc. (Hide copyright information)Copyright

Team programming usually means coordinating efforts of individual programmers who divide up the programming tasks for a large, complex system. Collaborative programming is used here to mean two programmers working jointly on the same algorithm and code. Previous research indicates that student programmers working collaboratively outperformed individual programmers. A follow-up field experiment was conducted using experienced programmers who worked on a challenging problem important to their organization, in their own environments, and with their own equipment. To the surprise of the managers and participants, all the teams outperformed the individual programmers, enjoyed the problem-solving process more, and had greater confidence in their solutions.

Description of the Experiment

"Effective problem-solving performance" is defined in terms of (a) the readability of the proposed solution, that is, the degree to which the problemsolving strategy could be determined from the subject's work; and (b) the functionality of the proposed solution, that is, the degree to which the strategy accomplishes the objectives stated in the problem description. The variables READABILITY and FUNCTIONALITY were defined accordingly. Readability is a component of overall score since it is possible for a subject to use a reasonable strategy and to use programming language structures appropriately and yet fail to solve the problem (in the sense of generating the correct output). In such cases, the programmer may have misinterpreted the problem description or overlooked a critical component. Overall success on the problem-solving effort is measured by a variable SCORE, which is a simple sum of component variables READABILITY and FUNCTIONALITY. based on previous results, four predictions were made:

1. Programmers working in pairs will produce more readable and functional solutions to a programming problem than will programmers working alone.

2. Groups will take less time on average to solve the problem than individuals working alone.

3. Programmers working in pairs will express higher levels of confidence about their work (CONFID) and …

Related articles from newspapers, magazines, journals, and more
ALL I REALLY NEED TO KNOW ABOUT PAIR PROGRAMMING I LEARNED IN...
Magazine article from: Communications of the ACM WILLIAMS, LAURIE A. KESSLER, ROBERT R. May 1, 2000 700+ words
Rivals join forces to solve 'Year 2000' computer woes.
Magazine article from: Business First-Columbus Hoke, Kathy March 21, 1997 700+ words
New ICT Curriculum Proposed by Royal Academy of Engineering and BCS
News wire article from: Europe Intelligence Wire November 13, 2012 700+ words
The Century Date Change, Again
Magazine article from: Management Review Ettore, Barbara December 1, 1998 700+ words
Consultants don't hit the jackpot. (independent contractors not earning as...
Magazine article from: InfoWorld Alexander, Steve December 22, 1997 700+ words
©2013 Gale, a part of Cengage Learning. All rights reserved. Contact us | Privacy policy | Terms and conditions

The AccessMyLibrary advertising network includes: womensforum.com GlamFamily