2. Framework Definition
Frameworks Definition :
• A basic structure underlying a system, concept, or textual structure intended to serve as a
support or guide for the building of something that expands the structure into
something useful.
• A framework may be for a set of functions within a system and how they interrelate
Information Technology Framework :
• A logical structure intended to provide a comprehensive representation of an
• information technology enterprise that is independent of the tools and methods used in
any particular IT business.
• There are many different frameworks that can be used for managing the delivery of cost-
effective IT services. Many frameworks only cover a specific aspect of IT (such as information
security, service management, quality etc.)
3. Why do we need enterprise architecture ?
• Today’s computer and technology systems are complex – especially when they are
responsible for so much of the productive activities within most organizations.
Physical and cloud servers, applications, and enterprise software all must
communicate and share data seamlessly in order to provide the customer a
successful and satisfactory user experience.
• The holistic view of all these pieces is referred to as enterprise architecture.
Guidance surrounding this implementation are often known as enterprise
architecture frameworks (EAFs), which we are exploring from a high level in this
subject.
• Because the enterprise must collaborate across disciplines, it relies heavily on
technology – storing and collecting data, selling and implementing the good,
providing customer service. These various business needs require their own
technology to function properly and satisfactorily, which can lead to dozens or
hundreds of pieces of individual technology. If they can’t function together, the
customer experience probably won’t work smoothly.
4. History of enterprise architecture
Pre-EA: Originating with IBM, the BSP formalized a methodology that indicates a theory for information
systems architecture. It included both a top-down planning approach and an architecture planning process
that was divided into a series of steps for a company to follow.
Early EA: This begins in the 1980s and runs into the 1990s, and this era codifies the term “enterprise
architecture”. The initial wave of EAF theories include the PRISM, sponsored by IBM among others, released
in 1986, the Zachman Framework in 1987, and the NIST EA in 1989.
Modern EA: Starting in the late 1990s, this era continues to present day. Newer frameworks include the FEAF,
which is based on Spewak’s EAP
, as well as the TOGAF, a well-known version today, with roots in the TAFIM.
Today’s frameworks aim to provide tangible solutions beyond only IT, integrating all layers of an enterprise,
including overall strategy, business needs, IT infrastructure, and applications.
Despite the differences in approaches that these eras indicate, all frameworks are generally based on the
original BSP
methodology, often advocating similar steps or phases for planning and implementing enterprise IT.
5. Many EA frameworks combine data and application domains into a single (digitized)
information system layer, sitting below the business (usually a human activity system) and
above the technology (the platform IT infrastructure).
Architecture
domain
6. Architecture
View
A view model is a framework that defines the set of views or approaches used in systems analysis,
systems
design, or the construction of an enterprise architecture.
Since the early 1990s, there have been a number of efforts to define standard approaches for
describing and analyzing system architectures. Many of the recent Enterprise Architecture
frameworks have some kind of set of views defined, but these sets are not always called view
models.
7. Enterprise Architecture as a Meta-
Discipline
An enterprise-wide architecture should serve
as an authoritative reference, source of
standards for processes / resources, and
provider of designs for future operating states.
An EA is therefore THE architecture of the
enterprise and should cover all elements and
aspects. Having a single source of reference
is essential to avoiding waste and duplication
in large, complex organizations. It also
resolves the “battle of best practices” and
competition between sub architectural domains
which can be problematic for organizations that
are trying to become for efficient. Developing
an enterprise-wide architecture using the EA
methods is a unique and valuable undertaking
for organizations, in that the EA is holistic and
serves as an umbrella or “meta-context” for all
other management and technology best
practices.
Balance Score
Card SWOT,
Six Sigma
Strategic
Level
Busine
ss
Level
T
echnolog
y
Level
CPIC, Alternatives Analysis
SOA, Business Cases,
PMBOK, BPI / BPR
ITIL, COBIT, CORBA, SDLC,
OO Design & Analysis,
Cloud Computing,
Mobile
Enterprise Architecture as a Meta
Discipline
EA is the organizing meta-context and
standards authority for implementing all
management and
technology best practices
8. The Enterprise Architecture
Approach
FRAMEWO
RK
METHODOLO
GY
ARTIFAC
TS
STANDAR
DS
BEST
PRACTICES
Core Elements of an
Enterprise
Architecture Approach
Governance
The first core element is “Governance” which identifies the
planning, decision-making, and oversight processes and
groups that will determine how the EA is developed and
maintained, accomplished as part of an organization’s
overall governance.
Methodology
The second core element is “Methodology” which are
specific
steps to establish and maintain an
EA program, via the selected approach.
Framework
The third core element is “Framework” which identifies the scope of the overall architecture and the
type and relationship of the various sub-architecture levels and threads. Not all frameworks allow for
sub- domains or are able to integrate strategy, business, and technology planning.
Artifacts
The fourth core element is “Artifacts” which identifies the types and methods of documentation to be
used in each sub-architecture area, including strategic analyses, business plans, internal controls,
security controls, and models of workflow, databases, systems, and networks. This core element
also includes the online repository where artifacts are stored.
The
Governance
9. Standards
The fifth core element is “Standards” which identify business and
technology standards for the enterprise in each domain,
segment, and component of the EA. This includes recognized
international, national, local, and industry standards as well as
enterprise-specific standards.
Best Practices
The sixth core element is “Associated Best Practices” which are
proven ways to implement parts of the overall architecture or
sub- architectures, in context of the over-arching EA.
Enterprise Architecture Activities
Enterprise architecture is
accomplished
managementprogram and an
analysis
through a
and
design
method that is repeatable at various levels of scope.
Together the EA program and method provide an
ongoing capability and actionable, coordinated
views of an enterprise’s strategic direction,
business services, information flows, and resource
utilization.
10. As a management program, EA provides:
Strategic Alignment: Connects goals, activities, and
resources
Standardized Policy: Resource governance and
implementation
Decision Support: Financial control and
configuration management
Resource Oversight: Lifecycle approach to
development/management
As an analysis and design method, EA provides:
EA Approach: The framework, analysis/design
method, and artifact set
Current Views: Views of as-is strategies, processes,
and resources
Future Views: Views of to-be strategies, processes,
and resources
EA Management Plan: A plan to move from the
current to the future EA
EA can help to identify gaps in the
performance of line of business
activities/programs and the
capabilities of supporting IT
services, systems, and
11. Individual Class
Assignment
• Answers can be written using Bahasa or Language
• Mention the types of IT Framework and their definitions
• Describe some criteria that can be defining a framework as an enterprise architecture
• Please, provide detail explanation by compiling information from the internet using your own
words about some of the terms below :
a. Business Architecture
b. Information Architecture
c. Application Architecture
d. Technology Architecture
• Do not forget to include various literature that you use by referring to the book title / web title /
article title,
• author, publisher (if in the form of a book) / web address (if the article is online), year of publication.
• Do not take articles from blogs (wordpress, blogspot) and wikipedia.
Completion time: 50 minutes
Upload to Elitag
