The document outlines various software development processes including Test Driven Development (TDD), Behavior Driven Development (BDD), Feature Driven Development (FDD), and Acceptance Test Driven Development (ATDD). It discusses the benefits and drawbacks of each methodology, emphasizing the importance of clear requirements and user collaboration. The document aims to provide a comprehensive understanding of these development approaches without covering model or domain-driven development.

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

6. Traditional Development Process
Copyrighted to: Manning Publications Co.

7. Common misconception:
•TDD/ATDD is NOT about testing!!

8. Test Driven Development
•Short development iterations
•Based on requirements and unit test cases
•Necessary code to pass the test cases
•Refactor

9. Test Driven Development
Source: http://joshldavis.com/

10. Benefits-Test Driven Development
•Stability
•Necessary code to pass the test cases
•Refactor
•Cut rework
•Reduce bugs

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

14. Examples-Behavior Driven Development

15. Benefits-Behavior Driven Development
•Deliver more valuable software
•Faster & Reliable releases
•Reduced maintenance costs

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

19. Feature Driven Development
Source: Palmer, SR, Felsing, JM.2002.p.57

20. Feature Driven Development
Source: Palmer, SR, Felsing, JM.2002.p.77, 80

21. Feature Driven Development
Source: Palmer, SR, Felsing, JM.2002.p.85

22. Benefits-Feature Driven Development
•Bigger Projects
•More novice developers
•Critical projects

23. Drawbacks-Feature Driven Development
•Not as powerful on smaller projects
•High reliance on chief programmer

24. Acceptance Test Driven Development
•Crystallize acceptance criteria
•Develop right product

25. Acceptance Test Driven Development
Begin with the
end in mind
-Stephen R. Covey

26. Acceptance Test Driven Development
“It's not enough to know how to do things
You must know why you do them.”
– Harvey Mackay

27. Acceptance Test Driven Development
Source: David Starr

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.

29. Acceptance Test Driven Development
Copyrighted to: Quality Tree Software Inc.

30. Acceptance Test Driven Development
Copyrighted to: Quality Tree Software Inc.

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

33. Q & A

34. To dive deeper:
ttp://dannorth.net/introducing-bdd/
ttp://lizkeogh.com/
ttp://testobsessed.com/wp-content/uploads/2011/04/atddexample.pdf