Materi 13
Materi 13
Materi 13
Architecture
Course Overview
This chapter provides the author’s thoughts on future trends and
issues in the practice of enterprise architecture, based on readings
and observations during work on EA projects.
This is done to give the reader a sense of the issues that are
currently of interest to enterprise architects and organizations
considering EA programs.
These comments are also intended to help promote discussion in
each topic area as well as to encourage the adoption of a common
language for EA greater collaboration among those in this emerging
profession.
Course Objective
• Familiarize the reader with current issues in the practice of
EA.
• Stimulate discussion of EA issues.
• Provide a high-level view of where the practice of EA may be
going.
Course Contents
• Introduction
• Private Industry Models of EA – Competitive Advantage
• EA is Essential to Mergers and Acquisitions
• IT Services/Resources Become Commodities - New EA
Models
• Government Integration and EA
• Emerging EA Standards
Introduction … (1)
• EA is increasingly being used by corporations,
governments, non-profit groups, and academic
institutions in many nations.
• In the private sector, profit drives most planning and
decision-making, and EA is an optional activity.
• In the public sector, service delivery is the primary driver,
money is a use-or-lose resource, and EA may be an
activity mandated by law
• The following are some of the future trends :
• Corporations use EA for competitive advantage
• EA becomes an essential element in mergers and acquisitions
Introduction …(2)
• While this helps to mature the practice of EA, the lack of a standard
base of terminology allows for the continuing proliferation of
approaches and prevents meta-concepts from emerging, which
serves mainly to confuse enterprises that are implementing and/or
maintaining EA programs.
• Within the European Union, the UEML (Unified Enterprise Modeling
Language) has been developed by the CIMOSA Association along
with the CIMOSA Reference Architecture. In the past few years, the
terms and modeling concepts of the UEML have been accepted by
the European Commission
• However, this standard language for modeling has not been adopted
in the U.S., nor has it transcended to the level of EA
The Military’s Use of EA
• One of the most pressing considerations that the military has in using
EA is the vulnerabilities that a consolidation of capability and detailed
documentation present
• If the duplication in IT resource capabilities is completely eliminated,
then there will most likely be a reliance on fewer sources of IT
products and solutions.
• The potential to create “single points of failure” in systems and
applications is increased when duplication is totally eliminated. For
ex : if DOD were to totally rely on a single commercial operating
system, then security vulnerabilities become critical in terms of
potentially enabling hackers to take down large parts of the DOD
warfighting capability.
• For this reason, EA needs to promote a risk adjusted level of
interoperability and functional duplication, and the subsequent cost
inefficiency be viewed as acceptable in order to reduce IT
vulnerabilities
Academia’s Contribution to EA
• The trend with regard to EA in the academic sector continues to be
slow growth
• Universities are participating in standards bodies (e.g., IEEE, ISO, and
CEN), and development groups (e.g. the Object Modeling Group - OMG)
• However, the real contribution that academia should make to EA is
theory, and that is largely being ignored.
• The EA frameworks and modeling approaches that are in use in the
public and private sector were largely developed by government
groups and commercial practitioners
• In that EA is about the documentation of complex social enterprises
and how they use technology to improve performance, there are many
areas that academia can and should comment on
• This includes the ability of particular EA frameworks to capture
enterprise resources, requirements, performance gaps, and cultures
EA as a Profession / Certification
• EA is a profession that has levels of capability that will increasingly
be supported by training/education programs.
• It takes 15-20 years of experience to qualify a senior enterprise
architect, and up to 10 years to become proficient as a domain
architect for business process improvement, systems designs,
service-oriented architecture, data architecture, network
engineering, and security architecture
• The trend in EA certification is one of continuing growth as the
number of EA programs in business and government grows
• While academia needs to focus on developing EA-related theories,
courses, and case studies, professional training groups need to
provide EA Certification programs
EA as a Profession / Certification