CSC/ECE 517 Fall 2012/ch1b 1w69 mv

From Expertiza_Wiki
Revision as of 00:11, 27 September 2012 by Mstonse (talk | contribs) (→‎Need for BDD)
Jump to navigation Jump to search

Introduction to Behavior-Driven Design and User Stories

Behaviour Driven Design is a software development methodology which involves incorporating stakeholder’s point of view in the development of the software. The software is implemented by taking into consideration its behaviour as described by its stakeholders.

Need for BDD

BDD comes under agile development. Agile development came into picture to overcome the reasons for software project failure.Some of the reasons for software project failure are:

* Lack of understanding of user requirements.
* Changing requirements
* Pressure to meet the project deadline.
* Budget and time constraints
* Difficulty in software development and management
* Miscommunication or lack of communication between stakeholders.

Agile development involves stakeholder participation throughout the lifetown of the product. BDD helps achieve this objective of agile development.User stories are written in BDD to describe the feature that is to be implemented.User stories can then be used to write tests to check the behaviour desired by the stakeholder.TDD approach can then be used to implement the system.