Behavior-driven development: Difference between revisions

Revision as of 03:43, 29 June 2006

Revision as of 19:12, 13 July 2006

Line 1:

{{context}}

In computer science '''Behavior Driven Development''' is a programming technique that questions the behavior of an application before and during the development process. By asking questions as ''what should this application do?'' or ''what should this part do?'' developers can identify gaps in their understanding of the problem ___domain and talk to their peers or ___domain experts to find the answers. By focussingfocusing on the behavior of applications developers try to create a common language that's shared by all stakeholders: management, users, developers, project management and ___domain experts.

The purpose is to question each part of the application and the application entirely. These questions deal not mere with technical or requirements issues but also with cost and time related issues. ''Is it feasible for our organization to build an application of this scope?'' is a question that can be answered by writing behavior tests. By exposing the complexities early on developers and management can make better assumptions on how fit the organization is to handle the creation of an application.