Enterprise Architecture
Frameworks and
Methodologies
According to CompTIA, these are the four leading Enterprise
Architect Planning (EAP) methodologies:
1. The Open Group Architectural
Framework (TOGAF)
• TOGAF is a method of designing, implementing,
guiding, and maintaining the construction of
enterprises using controlled phases—or, as it is
known, the “Architectural Development Method
(ADM)”.
• Its strategies have been iteratively improved
upon for 25 years.
•
2. Zachman Framework for
Enterprise Architecture
• The Zachman Framework for Enterprise
Architecture -- which covers six architectural
points as well as six primary stakeholders that
aid in defining and standardizing IT architecture
components.
• The Zachman Framework uses a 36-column
matrix to help organize your company’s
enterprise architecture and lend insight into
your organization’s IT assets.
3. Federal Enterprise Architecture
Framework (FEAF)
• FEAF, an architectural framework designed
initially for use by the U.S. Government to
integrate its federal agencies, is a
collaborative planning methodology that has
become a popular EA model used in private
enterprises.
4. Gartner's Enterprise
Architecture Framework
• Gartner, a global leader in IT research and
insights, has put forward enough best
practices for Enterprise Architecture solutions
throughout the years during its consulting
practices that it has built up its own
methodology — one focusing more so on
business outcomes than abstract phasing.
TOGAF vs Zachman:
What’s The Difference?
TOGAF: The Open Group
Architecture Framework
• TOGAF is the de facto industry standard
framework, offering a methodological
approach to Enterprise Architecture design,
planning, implementation, and governance.
• It provides a consistent view of architectural
artifacts that can be well understood by all
stakeholders within the organization.
Architecture Development Method
(Steps)
• Architecture vision.
• Business architecture.
• Information systems architecture.
• Technology architecture.
• Opportunities & solutions.
• Migration planning.
• Implementation governance.
• Architectural change management.
TOGAF has three pillars through which is
explores your company’s architecture:
• Enterprise Architecture Domains
• ARM
• Enterprise Continuum
Zachman Enterprise Architecture
• The Zachman Framework offers a model-
based approach that:
• Specifies the deliverables
• Categorizes various aspects of enterprise
system subsets into a matrix form
• Associates them with the decision choices of
the business-I environment
Zachman Framework rules
1. Columns have no order, but should be
arranged in top-down order starting with the
most significant category.
2. Each column has a simple generic model
and can have its own meta-model within
that column.
3. The basic model of each column must be
unique and avoid overlapping or replicating
data in any other column.
Zachman Framework rules
4. Each row describes a distinct, unique
perspective.
5. If you are successful with rules 2, 3 and 4, you .
should have a matrix where each cell is unique.
6. Avoid altering the names of your rows or
columns.
7. The logic is recursive and generic, which
means that it can be used to classify or analyze
anything related to the enterprise architecture
in question.
Choosing TOGAF or Zachman
• Which enterprise architecture you choose depends on your
approach.
• The TOGAF framework provides a systematic approach for
defining the process of creating or improving an Enterprise
Architecture. With its ADM, the framework offers a process for
implementing the decision choices in order to produce your
desired model.
• The Zachman Framework is more of an ontology—a structured
set of expressions that describe how artifacts can be
categorized, and thus created, operated, and changed. Unlike
TOGAF, Zachman uses various enterprise perspectives in order
to scope, define, and plan details regarding individual subsets
of your enterprise system.
Enterprise architect role
• Prepares EA business case, exposes benefits and drivers, financial merits
• Presents, justifies communicates to all stakeholders in business and IT
• Specifies EA framework, best practices and tools
• Establishes architecture, design and technology principles and guidelines
• Participates in EA design and development
• Coordinates works done by domain architects
• Controls the consistency and compliancy of artefacts
• Owns the EA repository and decides access rights
• Recommends transformation roadmap and works with Program
Management
• Controls EA iterations deliveries
• Establishes compliance checkpoints in major capability development
processes
• Assesses EA maturity
• Measures returned value at each iteration
Enterprise Architecture Domains
What are the goals of enterprise
architecture?
General goals of any EA are:
• Effectiveness
• Efficiency
• Agility
• Continuity
What are the benefits of
enterprise architecture?
There’s a myriad of benefits of EA,
including:
• Design
• Standards
• Project management
• Discovery
• System development and management
• IT complexity and value
• IT openness
• IT risk management
What are the six basic elements of
enterprise architecture?
• 1. Architecture management
• 2. Architecture framework
• 3. Implementation methodology
• 4. Documentation artifacts
• 5. Architecture repository
• 6. Associated best practices
Desired certifications
• AWS Certified Solution Architect
• Axelos ITIL Master certification
• Dell EMC Proven Professional Cloud Architect Training
and Certification
• Google Professional Cloud Architect
• Professional Cloud Solutions Architect Certification
• Red Hat Certified Architect
• Salesforce Certified Technical Architect (CTA)
• The Open Group TOGAF 9 Certification
• The Open Group Certified Architect (Open CA)
References:
• [Link]
oks/ea_what_is_enterprise_architecture.html
• [Link]
• [Link]
• [Link]
[Link]
• [Link]
• [Link]
• [Link]
responsibilities
• [Link]
oks/ea_lists_diagrams_and_matrices.html
• [Link]
• [Link]
enterprise-architecture/[Link]
• [Link]