Resumen y explicación de Behavior Driven Development
4 likes389 views
Behavior Driven Development (BDD) combines principles of Test Driven Development (TDD) with Domain Driven Design to enable collaboration between developers and business analysts, focusing on user behavior rather than developer opinions. User stories are essential in capturing requirements and expressing customer expectations, helping define what users want to achieve in business processes. They describe the user's role, goal, and motivation, and serve as a foundational element for planning and tracking project progress.
Resumen y explicación de Behavior Driven Development
- 1. Behavior Driven Development Tomado de Code Magazine y Wikipedia Behaviordriven development combines the general techniques and principles of TDD with ideas from domaindriven design and objectoriented analysis and design to provide software developers and business analysts with shared tools and a shared process to collaborate on software development, with the aim of delivering "software that matters" Testdriven development focuses on the developer’s opinion on how parts of the software should work. Behaviordriven development focuses on the users’ opinion on how they want your application to behave. Codeship User Stories User stories are the central axis around which a software project rotates. Developers use user stories to capture requirements and to express customer expectations. User stories provide the unit of effort that project management uses to plan and to track progress. Estimations are made against user stories, and user stories are where software design begins. User stories help to shape a system’s usability and user experience. User stories express requirements in terms of The Role, The Goal, and The Motivation. A user story isn’t concerned with a named user, like “Bob Smith” or “Anne Wilson.” User stories are concerned with a user role, for example: a customer, or a salesman, or a call center operator. User stories describe what that user wants to do from the perspective of an interaction with a business process, like purchasing, or ordering, or paying a bill. A user story describes the user’s goal in terms of needing to get something done with the business, rather than in terms of using the system itself. A user story also captures the user’s motivation for wanting to accomplish the goal. The motivation captures some of the backstory and the context for the user’s interaction with the business. Example User Story As a <role> I want to <goal> so that <motivation> As an account holder, I want to transfer funds between two of my accounts Documento creado por Francisco Quintero