02 - Enterprise Architecture Framework Flashcards
He introduced this framework in 1987.
John Zachman
This framework was introduced in 1987 by John Zachman.
The Zachman Framework
It was previously called “Framework for Information Systems Architecture.”
The Zachman Framework
It was recognized as the first comprehensive framework for enterprise architecture.
The Zachman Framework
It is a logical structure for classifying and organizing the descriptive representations of an enterprise system development.
The Zachman Framework
Enumerate the six (6) basic interrogatives in The Zachman Framework.
- What
- How
- Where
- Who
- When
- Why
This framework addresses an enterprise as a whole wherein issues can be easily mapped to understand its nature, implications, and possible solutions.
The Zachman Framework
The framework is an ontology and not a methodology.
The Zachman Framework
It originated as a generic framework and a methodology for developing technical architectures, which evolved into an enterprise architecture framework and method.
The Open Group Architecture Framework (TOGAF)
It is the latest version which provides guidance, error correction, improved document structure, updated business architecture and content meta-model.
TOGAF Standard Version 9.2
This addresses the organization, processes, skills, roles, and responsibilities required to establish and operate an architecture within an enterprise.
Architecture Capability Framework
This provides the “way of working” for architects.
Architecture Development Method
It is considered as the core of TOGAF, which consists of the stepwise cycle approach for the overall enterprise development and centers requirements management.
Architecture Development Method
Enumerate the eight (8) processes involved in the stepwise cycle appraoch.
- Architecture Vision
- Business Architecture
- Information Systems Architectures
- Technology Architecture
- Migration Planning
- Opportunities and Solutions
- Implementation Governance
- Architecture Change Management
This considers four closely related architectural structures in an enterprise.
Architecture Content Framework
Enumerate the four (4) architectural structures in an enterprise.
- Business Architecture
- Data Architecture
- Application Architecture
- Information Technology (IT) Architecture
This comprises various reference models that illustrate how architectures are developed across a wide variety of foundational architectures such as common system architecture, industry-specific architecture, and individually-owned enterprise.
Enterprise Continuum
Enumerate the three (3) reference models in an enterprise continuum.
- Technical Reference Model
- Building Blocks Information Base
- Open Group’s Standard Information Base (SIB)
Enumerate the four (4) main components of TOGAF.
- Architecture Capability Framework
- Architecture Development Method
- Architecture Content Framework
- Enterprise Continuum
Aims to provide an open and vendor-neutral approach to interoperability and raises the level of abstraction in enterprise architecture.
Model-Driven Architecture (MDA)
It provides guidelines for structuring software specifications that are expressed as models.
Model-Driven Architecture (MDA)
It separates the business and application logic from the underlying platform technology.
Model-Driven Architecture (MDA)
It provides a standard repository of MDA model and defines structures that help multiple groups work with a model while having a standard view.
Meta-Object Facility (MOF)
It is an established industry standard for for data repository integration, standardized database model representation, schema transformation models, and data mining models.
Common Warehouse Metamodel (CWM)
This mapping expresses Unified Modeling Language (UML) models in Extensible Markup Language (XML) and allows it to be moved around an enterprise as it progresses from analysis to modelling and to application.
XML Metadata Interchange (XMI)
Enumerate the three (3) key modeling technologies that MDA was based upon.
- Meta-Object Facility (MOF)
- Common Warehouse Metamodel (CWM)
- XML Metadata Interchange (XMI)
It is a key feature of MDA.
Mapping
It is a set of rules and techniques used to modify one (1) model to come up with a new model.
Mapping
This includes the business requirements and business model or domain model that describes the state of the enterprise where the system will be integrated.
Computation Independent Model (CIM)
This abstracts the automated data processing system.
Computation Independent Model (CIM)
This describes the internal structure of an operating system while abstracting specific details for a particular platform.
Platform-Independent Model (PIM)
This shows that a certain part of a complete set of specifications does not change from one platform to another.
Platform-Independent Model (PIM)
This combines the specifications in the PIM and the details on how a system uses a particular type of platform.
Platform-Specific Model (PSM)
