Scribd
Upload
159 views

Enterprise Architecture Components: System Integration and Architecture

The document discusses enterprise architecture frameworks and their benefits. It describes common EA frameworks like TOGAF, Zachman, and FEAF. These frameworks provide structured guidance for documenting an organization, visualizing relationships through standard notations, following design processes, and structuring EA teams. The best framework depends on an organization's needs, but all aim to increase transparency, standardization, and alignment of business and IT.

Uploaded by

wilmark maguigad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
159 views

Enterprise Architecture Components: System Integration and Architecture

The document discusses enterprise architecture frameworks and their benefits. It describes common EA frameworks like TOGAF, Zachman, and FEAF. These frameworks provide structured guidance for documenting an organization, visualizing relationships through standard notations, following design processes, and structuring EA teams. The best framework depends on an organization's needs, but all aim to increase transparency, standardization, and alignment of business and IT.

Uploaded by

wilmark maguigad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 17

Enterprise Architecture

Components
System Integration and Architecture
Objectives

 Differentiate the Implementation Technology of Enterprise Architecture


 Understand and use the frameworks underlying Enterprise Architecture
 Know the Architecture components and artifacts
Benefits of Enterprise Architecture

 EA can offer support for re-designs and re-organization, especially during major
organizational changes, mergers or acquisitions. It’s also useful for bringing more
discipline into the organization by standardizing and consolidating processes for
more consistency.
 EA is also used in system development, IT management and decision-making,
and IT risk management to eliminate errors, system failures and security
breaches. It can also help businesses navigate complex IT structures or to make IT
more accessible to other business units.
Benefits of Enterprise Architecture (cont.)

According to CompTIA, the biggest benefits of EAP include:


 Allowing more open collaboration between IT and business units
 Giving business the ability to prioritize investments
 Making it easier to evaluate existing architecture against long-term goals
 Establishing processes to evaluate and procure technology
 Giving comprehensive view of IT architecture to all business units outside
of IT
 Providing a benchmarking framework to compare results against other
organizations or standards
Enterprise Architecture Framework(Methodologies)

 Enterprise architecture as a framework can be vague since it’s meant to address


the entire organization, instead of individual needs, problems or business units.
Therefore, several frameworks exist to help companies effectively implement and
track EAP.
 According to CompTIA, these are the four leading Enterprise Architect Planning
(EAP) methodologies:
Enterprise Architecture Framework(Methodologies)

 The Open Group Architectural Framework (TOGAF): TOGAF provides


principles for designing, planning, implementing and governing enterprise IT
architecture. The TOGAF framework helps businesses create a standardized
approach to EA with a common vocabulary, recommended standards, compliance
methods, suggested tools and software and a method to define best practices. The
TOGAF framework is widely popular as an enterprise architect framework, and
according to The Open Group it’s been adopted by more than 80 percent of the
world’s leading enterprises.
Enterprise Architecture Framework(Methodologies) (cont.)

 The Zachman Framework for Enterprise Architecture: The Zachman


framework is named after one of the original founders of enterprise architecture
and it’s another popular EA methodology. It’s better understood as a “taxonomy,”
according to CompTIA, and it spans six architectural focal points and six primary
stakeholders to help standardize and define the IT architecture components and
outputs.
Enterprise Architecture
Framework(Methodologies) (cont.)
 Federal Enterprise Architecture Framework (FEAF): FEAF was introduced in
1996 as a response to the Clinger-Cohen act, which introduced mandates for IT
effectiveness in federal agencies. It’s designed for the U.S. government, but it can
also be applied to private companies that want to use the framework.
Enterprise Architecture
Framework(Methodologies) (cont.)
 Gartner: After acquiring The Meta Group in 2005, Gartner
established best practices for EAP and adapted them into the
company’s general consulting practices. While it’s not an individual
framework, CompTIA recognizes it as a “practical” methodology
that focuses on business outcomes with “few explicit steps or
components.”
What’s the Best Enterprise Architecture Framework?

 Although this might be somewhat of a non-answer, it’s the only one that rings
true: the best enterprise architecture framework is the one that’s most relevant to
your organization, and what you’re trying to achieve.
 Each different type of enterprise architecture framework has its particular benefits
and focus. For example, there are types of enterprise architecture frameworks best
suited for organizations concerned with defense.
What’s the Best Enterprise Architecture Framework? (cont.)

 Having a good understanding of what the different types of EA framework are,


can help an organization better understand better understand which EA
framework to apply.
 Ultimately, organizations will benefit most, from an enterprise architecture
management system (EAMS) that supports multiple EA frameworks. This way,
the most relevant enterprise architecture framework is always available.
What Makes Up an Enterprise Architecture Framework?

 The EA discipline views an organization as having complex and intertwined


systems. Effective management of such complexity and scale requires tools and
approaches that architects can use.
 An enterprise architecture framework provides the tools and approaches to
abstract this information to a level of detail that is manageable. It helps bring
enterprise design tasks into focus and produces valuable architecture
documentation.
What Makes Up an Enterprise Architecture Framework?
(cont.)

The components of an enterprise architecture framework provide structured


guidance for four main areas:
1. Architecture description – How to document the enterprise as a system from
different viewpoints.
 Each view describes one domain of the architecture; it includes those meta-
types and associations that address particular concerns of interest to particular
stakeholders; it may take the form of a list, a table, a chart, a diagram or a higher
level composite of such.
What Makes Up an Enterprise Architecture Framework?
(cont.)

2. Architecture notation – How to visualize the enterprise in a standard manner.


 Each view can be represented by a standard depiction that is understandable
and communicable to all stakeholders. One such notation is ArchiMate from
The Open Group.
3. Design method – The processes that architects follow. Usually, an
overarching enterprise architecture process, composed of phases, breaks into
lower-level processes composed of finer grained activities.
 A process is defined by its objectives, inputs, phases (steps or activities) and
outputs. Approaches, techniques, tools, principles, rules and practices may
support it. Agile architecture is one set of supporting techniques.
What Makes Up an Enterprise Architecture
Framework? (cont.)
4. Team organization – The guidance on the team structure,
governance, skills, experience and training needed
 Kanban boards and agile architecture can help provide team
structure, governance and best practices.
Summary

 As you can see enterprise architecture can be hard to define. But when
implemented you will see an increase in productivity while breaking down silos
around the company. It will have a roadmap that everyone can follow. It is
transparent and accessible to everyone regardless of being in the marketing
department, sales, or IT.
 When everyone has the same blueprint that maps out the tools and processes to
complete their projects there will be transformation through standardization,
decreased duplication, and tech alignment.
Summary (cont.)

 The EA has a pulse on the company’s target market and their desires so that your
business is creating products that will sell. It can be difficult to manage all three
sectors of the product development process so having a solid framework is key.
 Enterprise Architects creates the blueprint that everyone else will follow. This
blueprint must align with the key initiatives of their organization while also
giving structure for their operations team. It gives everyone a path to follow.
 Unfortunately, there isn’t one single agreed-upon definition or standard in EA.
However, as businesses build their program they will use the elements that fit
with their company.

You might also like