Software Architecture Fundamentals

Example code: https://github.com/HenriqueSilverio/bmi-calculator

Transcript

1. Software Architecture Fundamentals
2. Henrique Silvério github.com/HenriqueSilverio twitter.com/RikeSilverio Software Engineer @ IM+
3. The signature of a mess
4. Behavior Vs. Architecture Developer: "Do you want to be able to make changes?" Manager: "Of course! But… functionality is more important than later flexibility…"
5. Behavior Vs. Architecture Manager: "Hey! We need to add this 'little button' to the screen!" Developer: "Ok! We gonna need {insert unaffordable high cost here} to make it." Manager:
6. Fight for the architecture!
7. What is architecture? "The architecture of a software system is the shape given to that system by those who build it." "Low-level details and high-level decisions are part of the whole design." — Robert C. Martin
8. Source: https://br.pinterest.com/pin/817966351053743259/
9. Source: https://coolhouseconcepts.com/house-plans/three-bedroom-cool-house-concept/
10. Source: https://libraries.usc.edu/library-floor-plans
11. Architecture is about intent. So why we came at this:
12. Hm! It's a Laravel app! It's a Web app!
13. Uh! It's a Ruby on Rails app! It's a Web app!
14. Architecture goals "The purpose [...] is facilitate the development, deployment, operation, and maintenance of the software system" "The ultimate goal is to minimize the lifetime cost of the system and to maximize programmer productivity." "The strategy behind that facilitation is to leave as many options open as possible, for as long as possible." — Robert C. Martin
15. Keep options open!
16. A Use Case Driven Approach
17. Use Cases Application specific business rules.
18. Design Principles SRP: Single Responsibility Principle OCP: Open-Closed Principle LSP: Liskov Substitution Principle ISP: Interface Segregation Principle DIP: Dependency Inversion Principle
19. Dependency Inversion Principle High-level modules should not depend on low-level modules. Both should depend on abstractions. Abstractions should not depend on details. Details should depend on abstractions. — "Agile Software Development, Principles, Patterns, and Practices", Robert C. Martin
21. Domain Application agnostic business rules.
22. Boundaries
23. The Web is a detail.
25. The Database is a detail.
27. Show me the code. The BMI Calculator example.
28. Standing on the shoulders of Giants
29. Thank you! Henrique Silvério github.com/HenriqueSilverio twitter.com/RikeSilverio