CSC/ECE 517 FALL 2009/wiki2 1 HJ: Difference between revisions

From Expertiza_Wiki
Jump to navigation Jump to search
No edit summary
Line 59: Line 59:


[3] http://c2.com/cgi/wiki?TestDrivenDevelopment
[3] http://c2.com/cgi/wiki?TestDrivenDevelopment
=== BDD ===
[4] http://behaviour-driven.org/Introduction
[5] http://en.wikipedia.org/wiki/Behavior_Driven_Development
[6] http://www.code-magazine.com/article.aspx?quickid=0805061

Revision as of 09:40, 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

[2] http://www.agiledata.org/essays/tdd.html

[3] http://c2.com/cgi/wiki?TestDrivenDevelopment

BDD

[4] http://behaviour-driven.org/Introduction

[5] http://en.wikipedia.org/wiki/Behavior_Driven_Development

[6] http://www.code-magazine.com/article.aspx?quickid=0805061