Skip to content

Enterprise Architecture

Introduction

MIT CISR defines enterprise architecture as “the organizing logic for business process and IT capabilities reflecting the integration and standardization requirements of the firm’s operating model.” We view architecture as a strategic, rather than technical, exercise. A firm’s architecture describes a shared vision of how a firm will operate—thus providing a shared understanding of the role of IT. We have found enterprise architecture to be a critical tool for aligning IT and business strategy and for driving business value from IT. We emphasize three key concepts in our research:

  1. Operating model: a simple statement of the integration and standardization requirements for the firm’s core processes (“Forget Strategy: Focus IT on Your Operating Model”).
  2. Core diagram: a visual representation of the firm’s key business processes, shared data, and integrating technology (“Enterprise Architecture: Depicting a Vision of the Firm”).
  3. Architecture maturity: a description of the journey an established firm embarks upon as it transitions into more strategic use of IT ( “Maturity Matters: How Firms Generate Value from Enterprise Architecture”).

Slideshow

Enterprise Architecture: Four operating modelsEnterprise Architecture builds agility over timeEnterprise Architecture: Unification model core diagram

Publications

View all

Title Author Type Date
Schneider Electric: Connectivity Inspires a Digital Transformation Ross, Jeanne W.
Beath, Cynthia M.
Moloney, Kate
Working Paper2017-05-24
Designing Digital Organizations—Summary of Survey FindingsRoss, Jeanne W.
Sebastian, Ina
Beath, Cynthia M.
Jha, Lipsa
The Boston Consulting Group, Technology Advantage Practice of
Working Paper2017-02-28
Your Newest Governance Challenge: Protecting and Exploiting Your Digital ServicesUmbach, Christian
Ross, Jeanne W.
Research Briefing2017-02-16
Winning With IoT: It’s Time to ExperimentWixom, Barbara H.Research Briefing2016-11-17
Expanding Digital Innovation at AudiFonstad, Nils O.
Mocker, Martin
Working Paper2016-10-06