A Comparative Review of Business Architecture

Business Architecture provides foundational and actionable concepts for enterprises and their transformation. In practical terms, Business Architecture is an approach to represent the way an organization operates, capture the resources it takes (including IT applications) and instrument alignment between business performance and strategic priorities. These Business Architecture goals have received a great deal of attention from different disciplines in the last two decades. Recently, companies and industries in regimes of fast technological change and innovation have made Business Architecture gain new emphasis. As it is also seen from the literature, Business Architecture is being revisited intensively by companies, government, analysts, standards organizations, and researchers.

As Business Architecture involves different concepts and it has a strong multidisciplinary nature, it is common to find a number of approaches to Business Architectures in the literature. Furthermore, the variety of Business Architecture perspectives is wide and their applications depend on purpose of adoption, scope of usage, and overall maturity of specific concepts. Thus, in order to unravel commonalities and differences among these approaches, it is important to establish a unified perspective for presenting and comparing them.

Business Architecture comprises three core components or dimensions, namely, conceptual model, methodology and tooling. This report reviews ten approaches to Business Architecture from the literature and evaluates them according to proposed measures. Strengths and shortfalls may be identified across the above dimensions. A particular focus of the evaluation is laid on the service concept, which is often presented as the connection point between business and IT.

By: Susanne Glissmann; Jorge Sanz

Published in: RJ10451 in 2009


This Research Report is available. This report has been submitted for publication outside of IBM and will probably be copyrighted if accepted for publication. It has been issued as a Research Report for early dissemination of its contents. In view of the transfer of copyright to the outside publisher, its distribution outside of IBM prior to publication should be limited to peer communications and specific requests. After outside publication, requests should be filled only by reprints or legally obtained copies of the article (e.g., payment of royalties). I have read and understand this notice and am a member of the scientific community outside or inside of IBM seeking a single copy only.


Questions about this service can be mailed to reports@us.ibm.com .