Expand & Refine Knowledgebase

This post is the second one in our two-part series exploring how business architecture and IT architecture really are BFF (Best Friends Forever).

We’ve been very business-focused in our StraightTalk so far—and intentionally so. But a business architect always has a foot in two different worlds: one as part of the business and the other as part of the enterprise architecture team. So, for the next two posts, we are going to focus on how business architecture relates to IT architecture, and we’ll see how these two really are BFF (Best Friends Forever). Business architecture provides the business context and direction, and IT architecture makes it real through automated solutions.

Back to business architecture school one more time. In our last installment, we talked about how to map out (a.k.a write down) the “core” business architecture that included capabilities, value streams, organization and information. Here in this installment, we’re going to talk about mapping the “extended” business architecture domains.

Okay, time to go back to business architecture school. Having our business architecture written down is at the heart of us being able to do cool stuff with it, so we better talk a little more about mapping it out.

In this StraighTalk installment, we’re going to talk about the “core” business architecture domains. That means those four boxes in the middle of our favorite diagram below.