Revision as of 04:35, 13 October 2007 edit Tristessa de St Ange (talk \| contribs) 4,690 edits further improvements ← Previous edit		Revision as of 04:36, 13 October 2007 edit undo Tristessa de St Ange (talk \| contribs) 4,690 edits m →Modern trends: multiple programmers to one sub-task: bracket Next edit →
Line 9: == Modern trends: multiple programmers to one sub-task == Difficulties experienced with these older methods, such as costs spiralling out of control as systems grew, and schedules failing to meet time-to-market targets, gave rise to techniques such as [[pair programming]]. Conceived in the early [[1990s]], these strategies involve multiple programmers working collaboratively on the ''same'' piece of [[source code]] as opposed to being ''individually'' responsible for individual tasks. This technique is frequently used in newer programming methodologies that are focused around [[object-oriented]] programming techniques, such as the [[Rational Unified Process]] and [[Extreme Programming]] (acronym "XP"), often in combination with design documentation methods such as the [[Unified Modelling Language]] (UML). In "pair programming", responsibility for the resulting product is equally shared between two programmers who work on their assigned sub-task together. Benefits of this approach include the ability for deficiencies in knowledge and ability in specific areas to be compensated for by the other programmer; in addition, the shared responsibility is thought to increase incentives for meeting project deadlines and quality targets.

Team programming: Difference between revisions