BDD for Business Analysts

May 27, 2014
One of the best tools you could ask for when your goal is understanding, "What is this supposed to do?"
Image source:
Jeffrey Davidson

A practical blog on how to write Scenarios using BDD

from Ryan McKergow: BDD aims to explain the behavior of a system in easy to understand language. Using BDD and Scenarios allows requirements and tests to utilize the same approach in documenting system behavior. The format is fairly simple, but sometimes hard to get your head around how to write in this format. This is why I’m aiming to explain in practical terms how it works, so that you can either begin using it or get a refresher on BDD.

Key Process Patterns

From Gojko Adzic via Manning Publications: Summarizing chapter 2 of Specification by Example

Using “Given-When-Then” to Discover and Validate Requirements

from Mary Gorman and Ellen Gottesdiener: Here we summarize the technique of Given-When-Then (GWT). It is a structured format for expressing scenarios with example data, including pre- and post-conditions, helping project stakeholders (business, customer and technology partners) communicate using business domain language. You can use GWT to explore product options and confirm selected options in a concrete, tangible way. Often called “specification by example,” GWT provides living documentation for your delivered product. It simultaneously specifies requirements while identifying acceptance tests, thereby streamlining discovery and delivery.

What is Specification by Example?

Who writes the specification, now again?

3 misconceptions about BDD

Scenario-Oriented vs. Rules-Oriented Acceptance Criteria
John Doe |
Page loading slowly...
click here to view screenshot
You have reached the end of:
BDD for Business Analysts
Was it helpful? Share it!
Recommended next Roojooms: