JBehave leaves the clever bits to people.
Writing the acceptance criteria, scenarios, for a story is done by the business coach.
JBehave then translates these scenarios into empty JBehave classes.
The developer then writes the code within the JBehave classes.
Writing the scenarios for a story may require the Business Coach to work out the conversation that the system will have with the user and then break that down into the scenarios.
JBehave does not attempt to do anything clever and its for that reason that it is so useful. It does not attempt to generate the code for the application like model driven development tools. It leaves the clever bits to the business coach and developer.
Posted by chrismatts at December 15, 2004 3:58 PM