Ad
More Related Content
What's hot (20)
Viewers also liked (9)
Ad
Similar to Agile Software Design (20)
Ad
Recently uploaded (20)
Agile Software Design
- 1. Software Design on Agile Methods Eduardo Guerra
- 2. GUERRA [email protected] ITA @emguerra MundoJ Architect + Researcher Frameworks SwingBean, Esfinge Experience Research JavaSE, JavaEE, JavaME Patterns + Frameworks + Agile + Tests + Design
- 3. some months latter borrow some money pay what you borrowed plus interest
- 4. some years latter borrow some money pay with your life!
- 6. bad code was duplicated maintenance in this code is time- consuming people avoid reusing this code other classes became coupled with the bad design
- 8. sometimes there is no turn back
- 9. “Shipping first time code is like going into debt. A little debt speeds development so long as it is paid back promptly with a rewrite... The danger occurs when the debt is not repaid. Every minute spent on not-quite-right code counts as interest on that debt. Entire engineering organizations can be brought to a stand-still under the debt load of an unconsolidated implementation, object- oriented or otherwise.” Ward Cunningham
- 10. Technical Debt As soon as you pay it, less work you need to fix it!
- 11. Sometimes clients doesn't FACTS know exactly what requirements they need in their software Design solutions based on one requirement can be different if others are considered These facts create a risk to deliver wrong software to the client!
- 12. Traditional software engineer uses he same approach of other types of engineering projects!
- 13. Identify all Create a Construct based requirements complete project on the project Deliver the Test to verify the software requirements
- 14. Cost of Change Curve Using traditional style, it is cheaper to change in the COST beginning TIME
- 15. Traditional software engineer put a lot of effort on requirements and project to avoid changes!
- 16. But, didn't they see the signs?
- 18. Expected! Unexpected... Due to bad communication Because market needs.
- 19. Agile software development has a distinct approach...
- 20. Instead of fight against changes ...
- 22. Agile software engineer focus on implementation and tests to enable software to be changed easily!
- 23. Automated Testing Makes safe to change Decoupling Changes are isolated Clean Code Changes are more easy to make
- 24. Test-Driven Refactoring Development
- 26. Imagine if you could test- driven your life...
- 27. Why some people don't do that with their code?
- 28. Test Driven Development is a development and design technique in which the tests are created before the production code.
- 29. TDD is a crazy idea that works! Kent Beck Software Engineering Radio Podcast
- 31. Add a Test design class interface + define expected behavior Make Test Pass create actual behavior + most simple solution Refactor clean implemented code + adjust class design
- 32. Baby Steps
- 33. All code is Guilty untl proven Innocent
- 34. Refactoring
- 35. How often people wash the dishes in a restaurant kitchen?
- 36. The next meal will take longer and be more expensive because we are cleaning the kitchen. What???
- 37. This feature that you are asking is expensive because the code is not clean and we will need to change it. Humm... OK...
- 38. Are your source code like this?
- 39. Is it better to Or to let dirt clean little by and mess little? accumulate?
- 40. Some dirt are hard to clean in the course of time! Remember Technical Debt?
- 41. How to clean the source code? Refactoring
- 42. “Refactoring is a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior.” Martin Fowler
- 43. Code Bad Smells Have you ever look to a piece of code which doesn't smell very nice? Code smell is any symptom in the source code that can indicate a problem!
- 44. In every step, the tests should be executed to verify if everything still working! Refactoring is performed in small steps to remove bad smells and reach the desired design
- 45. Using refactoring, the application design emerge according to its needs!
- 46. Is it not dangerous to change a wining team? No when you have automated unit tests!
- 47. Conclusions
- 48. Cost of Change Curve Agile practices keep l na the cost of change io constant in later dit tra phases of the project COST agile TIME
- 49. short iterations
- 50. Short iterations only works if your code is ready to change!
- 51. Don't try to predict future design requirements Work hard in your current needs and let design emerge
- 53. See you on