Test drive on driven development process.
What we covered:
* Test Driven Development
* Behavior Driven Development
* Feature Driven Development
* Acceptance Test Driven Development
What are we not covered:
* Model Driven Development
* Domain Driven Development
Automating Business Process via MuleSoft Composer | Bangalore MuleSoft Meetup...
Test drive on driven development process
1. TEST DRIVE ON
DRIVEN DEVELOPMENT
PROCESS
By - Swathi Lakshmi Rajan
2. Agenda
• What is Software Development Process?
• Traditional development process
• TDD
• BDD
• FDD
• ATDD
• Q & A session
3. What are we covering?
• Test Driven Development
• Behavior Driven Development
• Feature Driven Development
• Acceptance Test Driven Development
4. What are we not covering?
• Model Driven Development
• Domain Driven Development
5. Software Development process
software development process or life cycle is a structure imposed on the
development of a software product.
ix phases involved
11. Drawbacks-Test Driven Development
•Programmers like to code, not to test
•Big time investment
•Additional Complexity
•Effectiveness depends on developers
12. Behavior Driven Development
•User stories
•Ubiquitous language
•Format:
- Given[context]
- When[event]
- Then[outcome]
•Power of:
- Business Analyst, Developer, Tester
13. Examples-Behavior Driven Development
A new frequent flyer
starts off with Bronze
status
If she earns 300
points, she
becomes a Silver
Frequent Flyer
Silver 300 points
Gold 700 points
Platinum 1500 points
16. Challenges- Behavior Driven Development
•Writing good scenarios takes practice
•Requires high business engagement and collaboration
17. Feature Driven Development
•Short iterations
•Developing by Feature
•Color coded UML
•Delivers frequent, tangible working results at all steps
18. Feature Driven Development
Yellow – Person / Organization
Blue – Description
Green – Place/ Thing
Pink - Time
Source: Palmer, SR, Felsing, JM.2002.p.124
28. Acceptance Test Driven Development
As an administrator, I want users creating
accounts to be required to choose secure
passwords so that their accounts cannot be
hacked by someone using a password
guessing program.
31. Benefits- Acceptance Test Driven
Development
•Avoid misunderstood requirements
•Thorough product testing
•Earlier defect detection
32. Drawbacks-Acceptance Test Driven
Development
•Time constraint
•Getting entire team to follow the process
•Project progress may be slow due to additional work