More Related Content
![UiPath Automation Suite Installation (Hands-On) [2/3]](https://cdn.slidesharecdn.com/ss_thumbnails/automationsuitecommunitysession2-251015095633-a6d862f1-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Agile Software Design
- 1. Software Design on Agile Methods Eduardo Guerra
- 2. GUERRA guerraem@gmail.com ITA @emguerra MundoJ Architect + Researcher Frameworks SwingBean, Esfinge Experience Research JavaSE, JavaEE, JavaME Patterns + Frameworks + Agile + Tests + Design
- 3. some months latter borrowsome money pay what you borrowed plus interest
- 4. some years latter borrowsome money pay with your life!
- 5.
- 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
- 7.
- 8.
- 9. “Shipping first timecode 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 useshe 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 ChangeCurve Using traditional style, it is cheaper to change in the COST beginning TIME
- 15. Traditional software engineerput a lot of effort on requirements and project to avoid changes!
- 16. But, didn't they seethe signs?
- 18. Expected! Unexpected... Due to bad communication Because market needs.
- 19. Agile software development has adistinct approach...
- 20. Instead of fight againstchanges ...
- 21.
- 22. Agile software engineerfocus on implementation and tests to enable software to be changed easily!
- 23. Automated Testing Makes safeto change Decoupling Changes are isolated Clean Code Changes are more easy to make
- 24. Test-Driven Refactoring Development
- 25.
- 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 adevelopment and design technique in which the tests are created before the production code.
- 29. TDD is acrazy idea that works! Kent Beck Software Engineering Radio Podcast
- 30.
- 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.
- 33. All code isGuilty untl proven Innocent
- 34.
- 35. How often peoplewash the dishes in a restaurant kitchen?
- 36. The next mealwill take longer and be more expensive because we are cleaning the kitchen. What???
- 37. This feature thatyou are asking is expensive because the code is not clean and we will need to change it. Humm... OK...
- 38. Are your sourcecode like this?
- 39. Is it betterto Or to let dirt clean little by and mess little? accumulate?
- 40. Some dirt arehard to clean in the course of time! Remember Technical Debt?
- 41. How to clean the source code? Refactoring
- 42. “Refactoring is adisciplined 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 applicationdesign emerge according to its needs!
- 46. Is it notdangerous to change a wining team? No when you have automated unit tests!
- 47.
- 48. Cost of ChangeCurve Agile practices keep l na the cost of change io constant in later dit tra phases of the project COST agile TIME
- 49.
- 50. Short iterations only worksif your code is ready to change!
- 51. Don't try topredict future design requirements Work hard in your current needs and let design emerge
- 53.