IEEE Software Presents On Architecture Podcasts with Grady Booch

Grady Booch

Grady Booch has recorded all of his On Architecture columns from IEEE Software magazine for this podcast on Computing Now.

We're sure you'll enjoy listening to Grady's podcasts as much as we enjoy being able to provide them.

If you enjoy On Architecture, be sure to check out Grady's new podcast, On Computing. Listen to Grady introduce his new podcast.

Subscribe  Google | RSS

ABOUT GRADY

Grady is recognized internationally for his innovative work on software architecture, software engineering, and modeling. He was chief scientist of Rational Software Corp. from its founding in 1981 until it became part of IBM, where he's an IBM Fellow. Grady was one of the original authors of the Unified Modeling Language and one of the original developers of several Rational products. Grady has served as architect and architectural mentor for complex, software-intensive projects around the world in just about every domain imaginable.

CURRENT PODCAST

38. Transition
Gracy Booch introduces listeners of On Architecture to his new podcast, On Computing.

Also available:

All Things Unseen

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.

Facing Future

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.

The Professional Architect

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."

The Architecture of Small Things

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.

Unintentional and Unbalanced Transparency

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.

The Soul of a New Watson

Watson, IBM's reasoning system, is both new and exploratory, and managing its architecture has considerable payoff.

The Architect's Journey

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.

Dominant Design

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.

Draw Me A Picture

Grady explores how we can reconcile the need for drawing diagrams and visualizing ultra-large complex systems.

The Elephant and The Blind Programmers

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.

An Architectural Oxymoron

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.

Systems Architecture

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.

Architecture Reviews

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.

Enterprise Architecture and Technical Architecture

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.

Architecture as a Shared Hallucination

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.

Software Abundance in the Face of Economic Scarcity, Part 2

Software-intensive systems are an inescapable and necessary element in helping us operate, innovate, and even thrive in the face of lean economic times.

Software Abundance in the Face of Economic Scarcity, Part 1

Software-intensive systems are an inescapable and necessary element in helping us operate, innovate, and even thrive in the face of lean economic times.

The Defenestration of Superfluous Architectural Accoutrements

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.

Like a River

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.

The Resting Place of Innovation

Successful software-intensive systems are generally quite innovative, as evidenced by their success. Although their architectures will, over time, converge to a stable point, this does not mean that innovation stops. Rather, for any such system to remain vibrant and relevant, innovation much proceed simultaneously at many levels.

Not With a Bang

Grady talks about two patterns and one antipattern that can help architects address the systemic issues that, left unattended, can lead software-intensive systems to collapse.

Back to the Future

Over the past 25 years, we've made great advances in tooling, technologies, and techniques that make software design more concrete. But design still requires careful thought.

Nine Things You Can Do with Old Software

Grady discusses what we can do intentionally with legacy code, from abandonment to evolution and many things in between.

Measuring Architectural Complexity

Grady talks about complex software-intensive systems and how they become increasingly irregular and thus chaotic over time.

Architectural Organizational Patterns

Grady proposes five overarching organizational patterns.

Tribal Memory

Grady discusses how a software development organization can preserve its stories in a system's written architecture and make evolving that system materially easier.

Morality and the Software Architect

There is a moral dimension to developing software, another force to consider when engineering a reasonably optimal software-intensive solution.

Artifacts and Process

Grady's comparison of building architecture and software architecture reveals the differences, congruences, and commonalities between the two.

The Economics of Architecture-First

Grady discusses how an architecture-first approach appears to be a reflection of sound development practices.

The Well-Tempered Architecture

By comparing musical and software patterns, Grady helps clarify the purposes and forms of patterns.

The Irrelevance of Architecture

Grady discusses the architecture of a software-intensive system and why it's largely irrelevant to its end users.

Speaking Truth to Power

Grady talks about the pitfalls, promises, complexities, and contradictions of speaking truth to power.

It Is What It Is Because It Was What It Was

Grady discusses software systems and their same basic architectural patterns.

Goodness of Fit

After a wide-ranging conversation with John Backus, Grady concludes that, for a given domain, there are forces at play that are best resolved by a common architectural pattern that allows variants.

From Small to Gargantuan

Grady discusses the different forces at work that act to make systems so complex.

The Accidental Architecture

Grady talks about the differences between intentional and accidental architecture.

On Architecture

Grady's inaugural column discussing the growth of software architecture and his Handbook of Software Architecture.

Subscribe to IEEE Software

IEEE Software magazine offers pioneering ideas, expert analyses, and thoughtful overviews for professional developers and managers who need to keep up with rapid technology change.

Current issue:
SE for Compliance