4 Steps to (Architectural) Epiphany

Slides for talk given at UIKonf in Berlin 2016.

Transcript

1. 4 Steps to (Architectural) Epiphany Isabel Barrera @ifbarrera
2. Intro
3. Rent the Runway
4. Goals • to understand common architecture patterns • to identify the underlying principles of common architecture patterns • to apply architectural principles strategically based on your unique needs
5. What even is architecture?
6. Architecture is the intentional design of the interaction between the components of your application. • defines the information flow between components • gives structure and purpose to your classes • intended to simplify your software
7. Patterns: A Brief History
8. VIP MVVM MVC VIPER
9. MVC VIEW CONTROLLER MODEL massive view controller :(
10. MVVM VIEW MODEL VIEW MODEL Presentation Logic
11. Clean Architecture • “Uncle Bob’s Clean Architecture” - 2014 • Use case based design Source: “The Clean Architecture” http://blog.8thlight.com/uncle-bob/2012/08/13/the-clean-architecture.html
13. Single Responsibility Principle “A software module should have only one reason to change.”
15. Dependency Rule “Source code dependencies can only point inwards.”
16. VIP VIEW PRESENTER INTERACTOR Business Logic Presentation Logic MODEL dependencies
17. VIPER An extension of Clean Architecture VIEW PRESENTER INTERACTOR Business Logic Presentation Logic ENTITY Business Objects ROUTER Navigation Controller
18. View/Controller Presenter Interactor Entity dependencies abstraction Router
19. VIP MVVM MVC VIPER ???
20. Underlying Principles • Separation Of Concerns • Single Responsibility Principle • Dependency Rule • Abstraction & Composition
21. Application
22. 1. Understand Your Needs
23. Understand Your Needs • What are you building? • How does it fit with the rest of the application? • Are you building on an existing app? • Who will be working on this project?
24. 2. Predict the future
25. Predict the Future • How might it need to change in the future? • How extendible does your module need to be? • How will your project scale complexity increases? • How might your architecture break down in the future?
26. Build your architecture with the future in mind
27. 3. Identify the MVF (minimum viable function)
28. Identify the MVF • define clear roles for all of your layers • how will your layers communicate data? • apply the principles
29. complexity degree of decoupling VIPER MVC
30. 4. Establish Your Standards
31. Establish Your Standards • communicate with your team • define a suggested development pattern • practice architectural code reviews • establish a strict organizational structure • be consistent and diligent • document your work
32. Conclusions
33. Conclusions • architecture is a process • good architecture is a team effort • make good design principles a part of your life
34. Think outside the box & look at the bigger picture
35. Thank You! @ifbarrera