Part I. Introduction. Chapter 1. What is esign and architecture? Chapter 2. A tale of two values. Part II. Starting with the bricks: programming paradigms. Chapter 3. Paradigm overview. Chapter 4. Structured programming. Chapter 5. Object-oriented programming. Chapter 6. Functional programming. Part III. Design principles. Chapter 7. SRP: the single responsibility principle. Chapter 8. OCP: the open-closed principle. Chapter 9. LSP: the liskov substitution principle. Chapter 10. ISP: the interface segregation principle. Chapter 11. DIP: the dependency inversion principle. Part IV. Components principles. Chapter 12. Components. Chapter 13. Component cohesion. Chapter 14. Component coupling. Part V. Architecture. Chapter 15. What is architecture? Chapter 16. Independence. Chapter 17. Boundaries: drawing lines. Chapter 18. Boundary anatomy. Chapter 19. Policy and level. Chapter 20. Business rules. Chapter 21. Screaming architecture. Chapter 22. The clean architecture. Chapter 23. Presenters and humble objects. Chapter 24. Partial boundaries. Chapter 25. Layers and boundaries. Chapter 26. The main component. Chapter 27. Services: great and small. Chapter 28. The test boundary. Chapter 29. Clean embedded architecture. Part VI. Details. Chapter 30. The database is a detail. Chapter 31. The web is a detail. Chapter 32. Frameworks are details. Chapter 33. Case study: video sales. Chapter 34. The missing chapter. Part VII. Appendix. Appendix A. Architecture archaelogy.

Sistemas

By applying universal rules of software architecture, you can dramatically improve developer productivity throughout the life of any software system. Now, building upon the success of his best-selling books clean code and the clean coder, legendary software craftsman Robert C. Martin ("Uncle Bob") reveals, no-nonsense solutions for the real challengers you'll face the ones that will make or break your projects. Learn what software architects need to achieve and core disciplines and practices for achieving it. Master essential software desing principles for addressing function, component separation, and data management. See how programming paradigms impose discipline by restricting what developers can do. Understand what's critically important and what's merely a detail". Implement optimal, high-level structures for web, database, thick-client, console, and embedded applications. Define appropriate boundaries and leyers, and organize components and services. See why designs and architectures go wrong, and how to prevent (or fix) these failures.