CSC/ECE 517 Fall 2009/wiki2 6 TDD: Difference between revisions
| Line 3: | Line 3: | ||
== Software Development Methodology == | == Software Development Methodology == | ||
According to [http://en.wikipedia.org/wiki/Software_development_methodologies 1 ]: | According to [http://en.wikipedia.org/wiki/Software_development_methodologies 1 ]: | ||
''<pre>"A software development methodology is a framework used to structure, plan, and control the process of developing a software system."</pre>'' | ''<pre>"A software development methodology is a framework used to structure, plan, and control the process of developing a software system.[1]"</pre>'' | ||
A software might range from a simple small application to a large and complex system in which the applications typically manage immense data sets and support complicated and extensive algorithms. Ad hoc approaches might sometimes work in developing small applications, because of the brilliance of the individuals developing it, but fails in most cases. A software development process has requirements. The things that an organization must understand are what software system will be developed, how much time would the development take, and what would be the quality of the final product. The amount and the way the software system meets the requirements determines the quality of a software system, Hence, a software development methodology is a critical tool for reaching these, complex and difficult to manage, requirements. | [[Image:softwaredevpic.jpg|thumb|Table 1 <sup>[8]</sup>]] | ||
<p> A software might range from a simple small application to a large and complex system in which the applications typically manage immense data sets and support complicated and extensive algorithms. Ad hoc approaches might sometimes work in developing small applications, because of the brilliance of the individuals developing it, but fails in most cases. A software development process has requirements. The things that an organization must understand are what software system will be developed, how much time would the development take, and what would be the quality of the final product. The amount and the way the software system meets the requirements determines the quality of a software system, Hence, a software development methodology is a critical tool for reaching these, complex and difficult to manage, requirements [2].</p> | |||
== Responsibility Driven Development(RDD)== | == Responsibility Driven Development(RDD)== | ||
Revision as of 23:18, 9 October 2009
Survey of "Driven Development" Methodologies
Software Development Methodology
According to 1 :
"A software development methodology is a framework used to structure, plan, and control the process of developing a software system.[1]"
A software might range from a simple small application to a large and complex system in which the applications typically manage immense data sets and support complicated and extensive algorithms. Ad hoc approaches might sometimes work in developing small applications, because of the brilliance of the individuals developing it, but fails in most cases. A software development process has requirements. The things that an organization must understand are what software system will be developed, how much time would the development take, and what would be the quality of the final product. The amount and the way the software system meets the requirements determines the quality of a software system, Hence, a software development methodology is a critical tool for reaching these, complex and difficult to manage, requirements [2].