The document discusses test driven development (TDD) and its history and benefits. TDD involves writing automated tests before writing code to make sure it passes the tests, eliminating bugs. It originated from Toyota's "just in time" manufacturing model and helps reduce waste and defects compared to traditional waterfall development approaches. The document demonstrates TDD with a live coding example and provides resources for learning more.

1. CodeAndroid meetup Test Driven Development

2. Objectives Brief history of TDD Do a very basic test

4. “ The fundamental problem with program maintenance is that fixing a defect has a substantial (20-50 %) chance of introducing another defect.” Mythical Man Month

5. Today: Test Driven Development

9. Unable to be “explained” to the layman

11. Money

12. Energy

13. Traditional model: Implementation Requirements Design Verification Maintenance

15. Your manager/your client will have provided the specs, and you now need to “follow the process”

16. You are a cog in the machine.

17. Manufacturing & construction industries Software has requirements that are never in spec. Requirements evolve over time Software developers are rarely domain experts BDUF meant changes later on were costly Waterfall model is based on “Physical Design”

18. Manufacturing & construction industries BDUF meant changes later on were costly Software is difficult to change in maintenance Two teams same project.

21. 2. Eliminate duplication.

24. Your manager/your client will have provided the specs, and you now need to “follow the process”

25. You are a cog in the machine.

28. Live programming demo

29. Useful URLs: android-sdk/platforms/android-1.5/samples/ApiDemos My life with android (mylifewithandroid.blogspot.com) Diego Torres Milano's blog (dtmilano.blogspot.com)

30. “ The fundamental problem with program maintenance is that fixing a defect has a substantial (20-50 %) chance of introducing another defect.” Mythical Man Month