Behavior Driven Development
In software engineering, behavior-driven development (abbreviated BDD) is a software development process based on test-driven development (TDD). Behavior-driven development combines the general techniques and principles of TDD with ideas from domain-driven design and object-oriented analysis and design to provide software developers and business analysts with shared tools and a shared process to collaborate on software development.
Although BDD is principally an idea about how software development should be managed by both business interests and technical insight, the practice of BDD does assume the use of specialized software tools to support the development process. Although these tools are often developed specifically for use in BDD projects, they can be seen as specialized forms of the tooling that supports test-driven development. The tools serve to add automation to the ubiquitous language that is a central theme of BDD.
Read more about Behavior Driven Development: History, Principles of BDD, Specialized Tooling Support, Story Versus Specification
Famous quotes containing the words behavior, driven and/or development:
“If parents award freedom regardless of whether their children have demonstrated an ability to handle it, children never learn to see a clear link between responsible behavior and adult privileges.”
—Melinda M. Marshall (20th century)
“A broad-backed ox can be driven straight on his road even by a small goad.”
—Sophocles (497–406/5 B.C.)
“The man, or the boy, in his development is psychologically deterred from incorporating serving characteristics by an easily observable fact: there are already people around who are clearly meant to serve and they are girls and women. To perform the activities these people are doing is to risk being, and being thought of, and thinking of oneself, as a woman. This has been made a terrifying prospect and has been made to constitute a major threat to masculine identity.”
—Jean Baker Miller (20th century)