CSC/ECE 517 FALL 2009/wiki2 1 HJ: Difference between revisions
No edit summary |
No edit summary |
||
| Line 8: | Line 8: | ||
== Test Driven Development (TDD) == | == Test Driven Development (TDD) == | ||
=== Overview === | |||
=== Strength === | === Strength === | ||
| Line 16: | Line 18: | ||
== Behavior Driven Development (BDD) == | == Behavior Driven Development (BDD) == | ||
Behavior Driven Development (or BDD) focused on the language and interactions used in the process of software development. BDD encourages collaboration between developers and non-technical or business participants in a software project. This allows the developers to focus on why the code should be created, rather than the technical details, and minimizes translation between the technical language in which the code is written and the domain language spoken by the business, users, stakeholders, project management etc. | |||
BDD is an Agile software development technique. | |||
=== Strength === | === Strength === | ||
BDD increases feedback and communication in a software development. | |||
Behavior-driven developers use both their native language and the language of Domain Driven Design to describe the purpose and benefit of their code. | |||
=== Weakness === | === Weakness === | ||
| Line 39: | Line 47: | ||
== Conclusion == | == Conclusion == | ||
== References == | |||
=== TDD === | |||
[1] http://en.wikipedia.org/wiki/Test-driven_development | |||
[2] http://www.agiledata.org/essays/tdd.html | |||
[3] http://c2.com/cgi/wiki?TestDrivenDevelopment | |||
Revision as of 06:31, 12 October 2009
Responsibility Driven Development (RDD)
Strength
Weakness
Test Driven Development (TDD)
Overview
Strength
Weakness
Behavior Driven Development (BDD)
Behavior Driven Development (or BDD) focused on the language and interactions used in the process of software development. BDD encourages collaboration between developers and non-technical or business participants in a software project. This allows the developers to focus on why the code should be created, rather than the technical details, and minimizes translation between the technical language in which the code is written and the domain language spoken by the business, users, stakeholders, project management etc. BDD is an Agile software development technique.
Strength
BDD increases feedback and communication in a software development. Behavior-driven developers use both their native language and the language of Domain Driven Design to describe the purpose and benefit of their code.
Weakness
Domain Driven Development (DDD)
Strength
Weakness
Model Driven Development (MDD)
Strength
Weakness
Conclusion
References
TDD
[1] http://en.wikipedia.org/wiki/Test-driven_development