Just Enough Software Architecture: A Risk-Driven Approach
ago 2010 · Marshall & Brainerd
4.1star
41 opiniones
Libro electrónico
376
Páginas
family_home
Apto
info
Acerca de este libro electrónico
This is a practical guide for software developers, and different than other software architecture books. Here's why:
It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book describes a way to do just enough architecture. It avoids the one-size-fits-all process tar pit with advice on how to tune your design effort based on the risks you face.
It democratizes architecture. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes, and how seemingly small changes can affect a system's properties.
It cultivates declarative knowledge. There is a difference between being able to hit a ball and knowing why you are able to hit it, what psychologists refer to as procedural knowledge versus declarative knowledge. This book will make you more aware of what you have been doing and provide names for the concepts.
It emphasizes the engineering. This book focuses on the technical parts of software development and what developers do to ensure the system works not job titles or processes. It shows you how to build models and analyze architectures so that you can make principled design tradeoffs. It describes the techniques software designers use to reason about medium to large sized problems and points out where you can learn specialized techniques in more detail.
It provides practical advice. Software design decisions influence the architecture and vice versa. The approach in this book embraces drill-down/pop-up behavior by describing models that have various levels of abstraction, from architecture to data structure design.
It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book describes a way to do just enough architecture. It avoids the one-size-fits-all process tar pit with advice on how to tune your design effort based on the risks you face.
It democratizes architecture. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes, and how seemingly small changes can affect a system's properties.
It cultivates declarative knowledge. There is a difference between being able to hit a ball and knowing why you are able to hit it, what psychologists refer to as procedural knowledge versus declarative knowledge. This book will make you more aware of what you have been doing and provide names for the concepts.
It emphasizes the engineering. This book focuses on the technical parts of software development and what developers do to ensure the system works not job titles or processes. It shows you how to build models and analyze architectures so that you can make principled design tradeoffs. It describes the techniques software designers use to reason about medium to large sized problems and points out where you can learn specialized techniques in more detail.
It provides practical advice. Software design decisions influence the architecture and vice versa. The approach in this book embraces drill-down/pop-up behavior by describing models that have various levels of abstraction, from architecture to data structure design.
Calificaciones y opiniones
4.1
41 opiniones
Fernando Paita
- Marcar como inapropiada
13 de enero de 2020
Ola buenas tardes todo bien 5 estrellas es muy bueno
Esta opinión les resultó útil a 4 personas
Acerca del autor
Dr. George Fairbanks has been teaching software architecture and object-oriented design for over a decade. He holds a Ph.D. in Software Engineering from Carnegie Mellon University. He has publications on frameworks and software architecture in selective academic conferences, including OOPSLA and ICSE.
He has written production code for telephone switches, plugins for the Eclipse IDE, and everything for his own web dot-com startup. He maintains a network of Linux servers in his spare time.
George has been a program committee member for the Working International Conference on Software Architecture (WICSA), the International Conference on Software Maintenance (ICSM), and the European Conference on Software Architecture (ECSA). He has been a referee for IEEE Transactions on Software Engineering (TSE) and IEEE Software.
He has written production code for telephone switches, plugins for the Eclipse IDE, and everything for his own web dot-com startup. He maintains a network of Linux servers in his spare time.
George has been a program committee member for the Working International Conference on Software Architecture (WICSA), the International Conference on Software Maintenance (ICSM), and the European Conference on Software Architecture (ECSA). He has been a referee for IEEE Transactions on Software Engineering (TSE) and IEEE Software.
Califica este libro electrónico
Cuéntanos lo que piensas.
Información de lectura
Smartphones y tablets
Instala la app de Google Play Libros para Android y iPad/iPhone. Como se sincroniza de manera automática con tu cuenta, te permite leer en línea o sin conexión en cualquier lugar.
Laptops y computadoras
Para escuchar audiolibros adquiridos en Google Play, usa el navegador web de tu computadora.
Lectores electrónicos y otros dispositivos
Para leer en dispositivos de tinta electrónica, como los lectores de libros electrónicos Kobo, deberás descargar un archivo y transferirlo a tu dispositivo. Sigue las instrucciones detalladas que aparecen en el Centro de ayuda para transferir los archivos a lectores de libros electrónicos compatibles.
