Behaviour-driven development is an “outside-in” methodology. It starts at the outside by identifying business outcomes, and then drills down into the feature set that will achieve those outcomes. Each feature is captured as a “story”, which defines the scope of the feature along with its acceptance criteria. This article introduces the BDD approach to defining and identifying stories and their acceptance criteria.
We know it: most people prefer to use pen and paper or a whiteboard to make software mockups because “it’s the fastest way”.
Well, if you count the time it takes to transfer the mockup from paper to a digital image, we think Balsamiq Mockups is faster, not to mention much easier and, dare we say it, more fun!
We optimized the user interface for speed: fewer buttons, more keyboard commands, full undo/redo, object snapping...you name it.
A. Hoffmann, E. Bittner, and J. Leimeister. Requirements Engineering: Foundation for Software Quality, Lecture Notes in Computer Science, 7830, Springer Verlag, Essen, Germany, JML_395.(2013)
L. R.. (2011)cited By (since 1996) 0; Conference of IEEE 2nd International Conference on Computing, Control and Industrial Engineering, CCIE 2011; Conference Date: 20 August 2011 through 21 August 2011; Conference Code: 86652.
C. Wild, K. Maly, C. Zhang, C. Roberts, D. Rosca, and T. Taylor. TENCON '94. IEEE Region 10's Ninth Annual International Conference. Theme: Frontiers of Computer Technology. Proceedings of 1994, (August 1994)
J. Carroll, G. Chin, M. Rosson, and D. Neale. Proceedings of the 3rd conference on Designing interactive systems: processes, practices, methods, and techniques, (2000)