Software architecture in practice /
"The definitive, practical, proven guide to architecting modern software, fully updated with new content on mobility, the cloud, energy management, DevOps, quantum computing, and more. Updated with eleven new chapters, Software Architecture in Practice, Fourth Edition, thoroughly explains what...
Guardado en:
Autor principal: | |
---|---|
Otros Autores: | , |
Formato: | Libro |
Lenguaje: | Inglés |
Publicado: |
Boston :
Addison-Wesley,
c2022.
|
Edición: | 4th ed. |
Colección: | SEI series in software engineering
|
Materias: | |
Aporte de: | Registro referencial: Solicitar el recurso aquí |
LEADER | 04071cam a2200373 a 4500 | ||
---|---|---|---|
001 | 99972233304151 | ||
005 | 20240404101827.0 | ||
008 | 210707s2022 maua b 001 0 eng d | ||
020 | |a 9780136886099 |q (hardcover) | ||
020 | |a 0136886094 |q (hardcover) | ||
035 | |a (OCoLC)1263793436 | ||
035 | |a (OCoLC)on1263793436 | ||
040 | |a UKMGB |c UKMGB |d OCLCO |d OCLCF |d NJI |d OCLCL |d U@S | ||
049 | |a U@SA | ||
050 | 4 | |a QA76.754 |b .B37 2022 | |
082 | 0 | 4 | |a 658.0551 |2 23 |
100 | 1 | |a Bass, Len. | |
245 | 1 | 0 | |a Software architecture in practice / |c Len Bass, Paul Clements, Rick Kazman. |
250 | |a 4th ed. | ||
260 | |a Boston : |b Addison-Wesley, |c c2022. | ||
300 | |a xvii, 438 p. : |b il. ; |c 24 cm. | ||
490 | 1 | |a SEI series in software engineering | |
504 | |a Incluye referencias bibliográficas (p. 399-413) e índice. | ||
505 | 0 | |a Part I. Introduction: 1. What is software architecture? -- 2. Why is software architecture important? -- Part II. Quality attributes: 3. Understanding quality attributes -- 4. Availability -- 5. Deployability -- 6. Energy efficiency -- 7. Integrability -- 8. Modifiability -- 9. Performance -- 10. Safety -- 11. Security -- 12. Testability -- 13. Usability -- 14. Working with other quality attributes -- Part III. Architectural solutions: 15. Software interfaces -- 16. Virtualization -- 17. The Cloud and distributed computing -- 18. Mobile systems -- Part IV. Scalable architecture practices: 19. Architecturally significant requirements -- 20. Designing an architecture -- 21. Evaluating an architecture -- 22. Documenting an architecture -- 23. Managing architecture debt -- Part V. Architecture and the organization: 24. The role of architects in projects -- 25. Architecture competence -- Part VI. Conclusions: 26. A glimpse of the future: Quantum computing. | |
520 | |a "The definitive, practical, proven guide to architecting modern software, fully updated with new content on mobility, the cloud, energy management, DevOps, quantum computing, and more. Updated with eleven new chapters, Software Architecture in Practice, Fourth Edition, thoroughly explains what software architecture is, why it's important, and how to design, instantiate, analyze, evolve, and manage it in disciplined and effective ways. Three renowned software architects cover the entire lifecycle, presenting practical guidance, expert methods, and tested models for use in any project, no matter how complex. You'll learn how to use architecture to address accelerating growth in requirements, system size, and abstraction, and to manage emergent quality attributes as systems are dynamically combined in new ways. With insights for utilizing architecture to optimize key quality attributes--including performance, modifiability, security, availability, interoperability, testability, usability, deployability, and more--this guide explains how to manage and refine existing architectures, transform them to solve new problems, and build reusable architectures that become strategic business assets. Discover how architecture influences (and is influenced by) technical environments, project lifecycles, business profiles, and your own practices; Leverage proven patterns, interfaces, and practices for optimizing quality through architecture; Architect for mobility, the cloud, machine learning, and quantum computing; Design for increasingly crucial attributes such as energy efficiency and safety; Scale systems by discovering architecturally significant influences, using DevOps and deployment pipelines, and managing architecture debt; Understand architecture's role in the organization, so you can deliver more value." --Descripción del editor. | ||
650 | 0 | |a Software architecture. | |
650 | 0 | |a Computer architecture. | |
650 | 0 | |a Software engineering. | |
650 | 7 | |a Software para computadora |x Arquitectura. |2 UDESA | |
650 | 7 | |a Computadoras |x Arquitectura. |2 UDESA | |
650 | 7 | |a Ingeniería de software (Computadoras). |2 UDESA | |
700 | 1 | |a Clements, Paul, |d 1955- | |
700 | 1 | |a Kazman, Rick. | |
830 | 0 | |a SEI series in software engineering |