Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I personally prefer to follow the BDD, or Behavior Driven Design, methodology. BDD is another form of Agile and Test-Driven development, a little stricter in intent and process, that aims, like most other agile methodologies, to reduce waste and improve product quality. The beautiful thing about BDD is that it beautifully melds the tenets of Agile with the process of TDD via the concept of Specification.</p> <p>The general approach is to start with a user story (aka placeholders for conversations). When you sit down with the appropriate parties to have those conversations, you develop one or more specifications. A specification defines the concern, the context within which the concern will be met, and the expected results, or observations, that a solution for that concern, within that contest, will generate. Specifications become tasks for the user story under discussion. </p> <p>When the time comes to implement those tasks, you turn those written specifications into executable specifications via TDD, and create your code through a continuous, iterative verify-and-refactor process.</p> <p>I could explain the process in detail, but the following article will cover it much better than I can:</p> <p><a href="http://www.code-magazine.com/article.aspx?quickid=0805061" rel="nofollow noreferrer">http://www.code-magazine.com/article.aspx?quickid=0805061</a></p> <p>BDD is a very modern, lean approach to software development. Decision is put off to the latest moment, and design takes place as the continual process of collaboration and iterative coding.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload