On Architecture Podcast
Grady Booch, one of UML's original authors, offers his perspective on various aspects of software architecture.

NOTE: This podcast is no longer being updated, but please explore this archive of the valuable content that was published while it was active.

Recent Episodes

Loading Tech News Entries
By Grady Booch
Gracy Booch introduces listeners of On Architecture to his new podcast, On Computing.
By Grady Booch
Considerable literature exists on the public face of civil architecture. But now we are coming to live in structures made not of atoms, but of bits. Here we ponder how these things unseen may become part of the fabric of our lives.
By Grady Booch
Every successful software-intensive system comes to a point where placing a pile of your best developers at one end of a lever can no longer move the world. Crossing that point while preserving the values and tribal memory of your organization's development culture requires serious adult supervision.
By Grady Booch
All complex systems grow from smaller systems that work in the first place; all complex systems will fail, in one way or another. Between the small and the large, between the perfect and the flawed, there is some person or persons who had a vision for the shape of things to come. We call such people "architects.”
By Grady Booch
There is complexity, and then there is organized complexity. Pure complexity is chaotic; organized complexity is full of patterns. Naming these patterns and respecting their intention is the essence of architecture.
By Grady Booch
Security and privacy impact each other; saying they are alternatives is a false dichotomy. Architecting a system that attends to both security and privacy is possible and desirable, yet there are often unintended, unexpected consequences in doing so.
By Grady Booch
Watson, IBM's reasoning system, is both new and exploratory, and managing its architecture has considerable payoff.
By Grady Booch
Architecting a software-intensive system encompasses technical elements and social considerations. Most interesting systems start small and focus on technical concerns, but once they become economically significant, social issues begin looming large.
By Grady Booch
The architecture of innovative software-intensive systems experience many periods of growth and collapse. Fighting this reality wastes energy; ignoring it is even more disastrous.
By Grady Booch
Grady explores how we can reconcile the need for drawing diagrams and visualizing ultra-large complex systems.
By Grady Booch
The architecture of a software-intensive system is best reasoned about through multiple, nearly independent views. Here Grady examines Kruchten's 4+1 model view in a new light.
By Grady Booch
To some, the phrase "agile architecture" is an oxymoron. Grady explores why we view the meaning behind the phrase to be a very good idea, helping a team attend to building the right software at the right time with the right amount of resources.
By Grady Booch
All complex systems fail, by some measure of the word "fail," with consequences ranging from benign to catastrophic. Grady examines the process of to triage in the face of a failing system.
By Grady Booch
An architectural review serves several purposes: to gain confidence in the design, to reason about alternatives, to attend to architectural rot. The process of such a review involves the interplay of design decisions, scenarios, and forces on the system.
By Grady Booch
Enterprise architecture and technical architecture are related yet different: whereas EA focuses on the architecture of a business that uses software-intensive systems, TA focuses on the architecture of the software-intensive systems that are used by a business to makes its mission manifest.
By Grady Booch
Architecture is just a collective hunch, a shared hallucination, an assertion by a set of stakeholders on the nature of their observable world, be it a world that is or a world as they wish it to be. Grady examines the technical and social factors that give rise to the value of architecture-as-artifact.
By Grady Booch
Software-intensive systems are an inescapable and necessary element in helping us operate, innovate, and even thrive in the face of lean economic times.
By Grady Booch
Software-intensive systems are an inescapable and necessary element in helping us operate, innovate, and even thrive in the face of lean economic times.
By Grady Booch
Simple architectures have conceptual integrity and are better than more complex ones. Continuous architectural refactoring helps to converge a system to its practical and optimal simplicity.
By Grady Booch
The metaphor of software development as building construction is an old one. Here is a fresh perspective, considering the life cycle of a software-intensive system as a river.
There are no results for this search.
   About the Author
Grady Booch is a Chief Scientist of Software Engineering at IBM. He is recognized internationally for improving the art and the science of software development and has served as architect and architectural mentor for numerous complex software-intensive systems around the world. The author of six best-selling books and several hundred articles on computing, he has lectured on topics as diverse as software methodology and the morality of computing. He is an IBM Fellow, an IEEE Fellow, an ACM Fellow, a World Technology Network Fellow, and a Software Development Forum Visionary.