In my Enterprise Architecture practice work, I leverage the dictionary, original EA publications and strong contemporary trends to help define EA and its related terms.
Architecture: is the fundamental organization of an object (e.g., house, airplane, building, etc…) or system embodied in its components, their relationships to each other and to the environment and the principles guiding its design and evolution. The architecture of an object is often described via a set of blueprints.
Enterprise Architecture: is the fundamental organization of an enterprise embodied in its components (e.g., people, processes, technology, assets, etc…), their relationships to each other and to the environment and the principles guiding its design and evolution. The architecture of an enterprise is best described via a set of blueprints and is often summarized in one “core diagram.”
Enterprise Architecture Framework: is a comprehensive collection of models/views (e.g., blueprints, lists, financial statements, etc…) that are used to describe an enterprise’s architecture. The framework is often arranged in a matrix format. The industry standard, created circa 1984, is the Zachman Framework. Note that in 2001, Zachman relabeled his framework as ontology due to issues with the word “framework.”
Enterprise Architecture Planning (aka Process or Methodology): is a process, approach or methodology to populate the framework with current and future state information; describe gaps and associated risks; and then craft a roadmap to address the gaps. The first published process was Spewak’s EAP in 1993 which focused on the top 2 rows of Zachman’s 1993 framework. More recently, TOGAF’s ADM seeks to address all Zachman rows.
Enterprise Architecture Reference Models: are blueprints that define best practice design patterns to help facilitate better decision-making. For example, the TOGAF TTM seeks to define a technology reference model.
Business Transformation: implies how businesses remake themselves into significantly better competitors. This field is often referred to as change management or strategic change. The McKinsey 7S model is a model of an organization using 7 components that help to highlight areas of strength, weakness, opportunity, threats as well as misalignment between the 7 components. Enterprise Architecture details the business via 36 models. Note that John P. Kotter’s publications address the social, political and other soft design issues.
Digital (Business) Transformation: is the design and change process associated with infuses information technologies into business processes in order to yield superior business capabilities.
@RayBordogna opines on Enterprise Architecture concepts.