Here is the synopsis of our sample research paper on Agile & Plan-Driven Software Development/Finding A Balance. Have the paper e-mailed to you 24/7/365.
Essay / Research Paper Abstract
A 15 page research paper that examines a new paradigm in the field of software programming development, which is known as agile programming. This new method is compared with traditional plan-driven methods in regards to whether or not it is possible to find a middle ground or balance between these concepts. Bibliography lists 15 sources.
Page Count:
15 pages (~225 words per page)
File: D0_khagpdsd.rtf
Buy This Term Paper »
Unformatted sample text from the term paper:
into turmoil (Boehm, 2002). Traditionalists support the continued use of "extensive planning, codified process and rigorous reuse" in order to keep the developmental process both efficient and predictable (Boehm, 2002,
p. 64). This view of software development sees it as a process that "gradually matures toward perfection" (Boehm, 2002, p. 64). However, countering this paradigm, a new generation of software
developers are rebelling against what they see as the demoralizing weight of corporate bureaucracy. They argue that the effects of detailed plan-drive development is dehumanizing and propose revolution (Boehm, 2002).
As specified in the Manifesto for Agile Software Development (http://www.agileAlliance.org), these developers call for change and a revitalized approach to development that dispenses with the old paradigm (Boehm, 2002). Not
surprisingly, there continue to be software developers who favor the plan-drive methods and they have reacted to the Agile Manifesto with determined criticism (Boehm, 2002). There are real-world examples
that can be presented both pro and con in regards to agile methods. Boehm (2002) argues that both agile and plan-driven approaches have their positive points and that each of
these methodologies lay claim to a "home ground," in which project features associated with each approach perform extremely well. Furthermore, Boehm (2002) argues that outside their areas of expertise,
a combined approach between these two approach to software development is possible and preferable over either approach used in isolation. This following examination of literature pertaining to this topic follows
Boehms approach and offers recommendations pertinent to finding a balance between these developmental paradigms. As Boehm states, while many advocates of both stances consider agile and plan-driven software
development methods to be "polar opposites," it is possible that a synthesis of the two approaches can provide developers with an improved and comprehensive "spectrum of tools and options" (Boehm,
...