Business Architecture and Integration

Posted by Ralph Whittle on Friday, February 24, 2012 - 10:55

Rate this:
Total votes: 0

One easy to understand definition of architecture was provided by Ivar Jocabson in his book 'The Object Advantage: Business Process Reengineering with Object Technology.' In its most simple terms, an architecture represents one element linked to other elements to form, collectively, a structure. Given this simple, but elegant definition, how would one link an element of the Business Architecture with the strategy? And by the way, how would one link an element of the Business Architecture with the Data/Information architecture?


Login or register below to comment on this discussion.
Pierre Gagne
posted 3 years 51 weeks ago
Ralph, Over the years, we have developed a Capability map and an enterprise business architecture framework for the insurance and wealth management industry. As a consulting company, we used to use it on almost all projects with our clients. In the case you mention, we would follow the following steps: - define and document the business strategies
- out of the strategies, we would help define the objectives that the client would want to achieve
- each business objective would then be matched with capabilities required to support it
- then processes for those capabilities would be turned into processes As to the data/information architecture, as part of our business framework, we had also developed an information architecture. For each capability, we have developed data topics that we be owned by each of them. In identifying the data topics with each capability, you are defining the information required for the strategies and objectives. I addition to this, we had also developed a CRUD matrix which shows the business integration and the business interfaces. This would allow to define the capabilities that are related to the capabilities that support the strategies and objectives. It is all linked together. If you want to see samples of the insurance and wealth management framework that we have developed, go to These frameworks are available to the financial industry. If you want to discuss this, you can email me at Pierre
Pearl Zhu
posted 5 years 9 weeks ago
Interesting discussion, well, we do have many great brainstorms regarding BA & EA, BA is more about asking big Why & What about organization: the value chain, the organizational structure, the business capability, the enterprise culture, the strategy planning., etc. and the purpose of BA/EA need become an effective communication tool, the governance framework or integration roadmap., etc, still, architecture is about bridging the strategy and execution, so if BA is about why and what, then EITA (DA+ PA+AA...) is about how, where, when....thanks.
David Champeau
posted 5 years 22 weeks ago
Ralph, in the work that I am currently doing, I am trying to build a set of relationships into a "line of sight" along the path of business strategy<->IT strategy<->business architecture<->information architecture<->application architecture<->technical architecture. In order to do this, I define "business architecture" as simply business processes, roles and rules. The info architecture starts with the "entities" such as "customer", "location", "product". The business process is broken down into three levels, business process, sub-process and activity. Each "activity" does something to one or more entities. The entities can be broken down into multiple levels and I am still working on that one. Then each activity is managed by an application and each entitiy is created and consumed by other applications. So far I am still prototyping all this and working with my client. But the benefits are already evident to the stakeholders. David

Join the Discussion

Already a Member? Login Here:

Shopping cart

View your shopping cart.

Editorial DIrectors

Gregg Rock
Gregg Rock
Editor & Founder

Jeff Scott
Editorial Director

Andrew Spanyi
Editorial Director