The document discusses the differences between enterprise architecture (EA) and a collection of architectures in an enterprise. It argues that EA requires a top-down guidance framework to ensure the various architectures developed across an organization are coordinated and aligned. The key elements of an effective EA framework include a target vision, principles, governance, reference architectures, development approaches, and an evolution roadmap. The document also outlines the focus areas in each phase of the TOGAF architecture development method to help ensure successful adoption of EA in initiatives, programs and projects. Effective EA requires balancing top-down guidance with bottom-up flexibility for organic growth.
What is the Value of Mature Enterprise Architecture TOGAFxavblai
Judith Jones received the Open Group award for Outstanding Contributions to the development of TOGAF 9 at 19th Open Group Enterprise Architecture Practitioners Conference Chicago - July 21-23, 2008. Former CEO of Architecting the Enterprise which has been a member of The Open Group for 6 years, she is personnally involved since 1997. As an active member of The Open Group and she is a major contributor and an editor of TOGAF 7, 8 and 9 as well as leading TOGAF projects for localisation, case studies, ADML, synergy and collaboration projects.
http://www.opengroup.org/member/member-spotlight-jones.htm
During last few years, role of Enterprise Architecture has expanded from technical to strategic in an Organization. This slide deck presents: Using Enterprise Architecture in your Organization.
A Brief Introduction to Enterprise Architecture Daljit Banger
Presentation to Metropolitan University (London) on the 16th Feb 2017.
The purpose of the session was to introduce core basic concepts around Enterprise Architecture and discuss the role of the Enterprise Architect .
Practical Enterprise Architecture in Medium-size Corporation using TOGAFMichael Sukachev
Overview on the Practical Enterprise Architecture approach using TOGAF ADM for architectures development, Zachman Framework as artifacts repository and Sparx EA as a modelling tool.
How to Articulate the Value of Enterprise Architecturecccamericas
Ever struggled with the question, What is the Value of Enterprise Architecture? In this facilitated conversation, Michael Fulton will share his perspective on Enterprise Architecture and the value it provides to the CIO, to IT, and to the business.
Come ready to engage, because in the conversation we will discuss:
•The EA 7-year itch
•Several External Perspectives on EA Value
•The CC&C perspective on a simplified approach to EA Value
•Ensuring your perspective on EA Value is relevant for your stakeholders
At the end of this conversation, you should walk away with:
•A new perspective on the value of EA
•Tips and tricks on how to articulate and quantify EA Value for your key stakeholders.
What is the Value of Mature Enterprise Architecture TOGAFxavblai
Judith Jones received the Open Group award for Outstanding Contributions to the development of TOGAF 9 at 19th Open Group Enterprise Architecture Practitioners Conference Chicago - July 21-23, 2008. Former CEO of Architecting the Enterprise which has been a member of The Open Group for 6 years, she is personnally involved since 1997. As an active member of The Open Group and she is a major contributor and an editor of TOGAF 7, 8 and 9 as well as leading TOGAF projects for localisation, case studies, ADML, synergy and collaboration projects.
http://www.opengroup.org/member/member-spotlight-jones.htm
During last few years, role of Enterprise Architecture has expanded from technical to strategic in an Organization. This slide deck presents: Using Enterprise Architecture in your Organization.
A Brief Introduction to Enterprise Architecture Daljit Banger
Presentation to Metropolitan University (London) on the 16th Feb 2017.
The purpose of the session was to introduce core basic concepts around Enterprise Architecture and discuss the role of the Enterprise Architect .
Practical Enterprise Architecture in Medium-size Corporation using TOGAFMichael Sukachev
Overview on the Practical Enterprise Architecture approach using TOGAF ADM for architectures development, Zachman Framework as artifacts repository and Sparx EA as a modelling tool.
How to Articulate the Value of Enterprise Architecturecccamericas
Ever struggled with the question, What is the Value of Enterprise Architecture? In this facilitated conversation, Michael Fulton will share his perspective on Enterprise Architecture and the value it provides to the CIO, to IT, and to the business.
Come ready to engage, because in the conversation we will discuss:
•The EA 7-year itch
•Several External Perspectives on EA Value
•The CC&C perspective on a simplified approach to EA Value
•Ensuring your perspective on EA Value is relevant for your stakeholders
At the end of this conversation, you should walk away with:
•A new perspective on the value of EA
•Tips and tricks on how to articulate and quantify EA Value for your key stakeholders.
It is well known that an effective PMO is key to successful and efficient program and project execution. In other words, doing things “right”. Enterprise Architecture is the discipline that plans and monitors enterprise transformation and aligns the business strategy with information technology capabilities. In other words, doing the “right things” to support the business.
Why is it organizations despite having both of these disciplines still struggle with effective enterprise transformation? What can we done to use these disciplines more effectively to effect better business outcomes? What are the roles of each discipline and how do they work together to create business value?
In this presentation, Riaz will address these questions and will provide real life examples that can help build a strong relationship between the PMO and Enterprise Architecture.
Learning Objectives:
• How to build a strong relationship between the PMO and Enterprise Architecture (EA) to deliver positive outcomes for your organization
• Identify the different roles and functions of the PMO and EA as well as their similarities
Introduction to Enterprise architecture and the steps to perform an Enterpris...Prashanth Panduranga
This presentation was used to introduce Enterprise Architecture, Introduction to how to perform an Enterprise Architecture Assessment followed by TechSharp introduction.
Deliverables in the presentation is not clear, the slides represent what was shown as part of the demo.
List of deliverables:
Application Rationalization framework
Portfolio Analysis framework
Road Map
Current state analysis
Target State establishing process
System Context
System Landscape
This presentation is on leveraging Enterprise Architecture Governance and Project Portfolio Management Best Practices to:
Accelerate project execution
Manage project and architecture inter-dependencies
Deliver realised value
Improve Enterprise and PMO collaboration
How to develop and govern a Technology Strategy in 10 weeksLeo Barella
This presentation covers the organizational layout, EA Services and EA Governance processes necessary to develop and govern a technology strategy effectively.
Application rationalization- Invest today to save tomorrow!Vivek Mishra
As organizations grow, their IT environment gets complex with all the digital applications acquired over time. Due to this, the platform is plagued by data silos and unstructured applications that do not work together anymore. This is where application portfolio rationalization or APR kicks in.
Learn how APR can help you in streamlining the existing application portfolio with an explicit goal of improving efficiency, reducing complexity, and lowering Total Cost of Ownership.
Design Architecture Review Board (ARB) to Enable Digital Strategy Mohan K.
Architecture Review Board (ARB) to Enable Digital Strategy Execution - *Based on case study of establishing Architecture Review Board (ARB) at a multinational manufacturing
Digital Transformation And Solution ArchitectureAlan McSweeney
Digital strategy is a statement about the organisation’s digital positioning, competitors and customer and collaborator needs and behaviour to achieve a direction for innovation, communication, transaction and promotion. Digital strategy needs to be defined in the same framework structure as the proposed digital architecture platform.
Achieving the target digital organisation means deploying solutions that enable the digital architecture. Solution architecture needs to design solutions that fit into the target digital architecture framework. This requires:
• Solution architecture team operating in an integrated manner designing solutions to a set of common standards and that run on the platform
• Solution architecture team leadership ensuring solutions conform to the common standards
• Solution architecture technical leadership to develop and maintain common solution design standards
• Solution architecture updates the digital reference architecture based on solution design experience
Digital solution design requires greater discipline to create an integrated set solutions that operate within the rigour of the digital architecture framework. The solution architecture function must interact with other IT architecture disciplines to ensure the set of solutions that implement the digital framework operate together. This requires greater solution architecture team leadership. This needs to be supplemented and supported by a well-defined set of digital solution design standards.
This follows-on from the previous presentation: Digital Transformation And Enterprise Architecture
https://www.slideshare.net/alanmcsweeney/digital-transformation-and-enterprise-architecture.
According to Gartner, "The stongest performing IT organizations are distinguished by strong strategy practices. The weak performing IT organizations are distinguished by weak delivery practices."
Having an IT strategy and executing it are important.
This brief presentation covers:
1. Why IT Strategy?
2. What does a great IT Strategy look like?
3. How to create a great IT Strategy
4. How to make the IT Strategy real
A simple guide to learn what EA is, why it’s important and how you can be using it to help your enterprise.
For more information: info@boc-group.com
Try ADOIT for EA:
https://www.boc-group.com/adoit/#test-it
This examines the potential for the application of Design Science principles to the solution design process within solution architecture to improve the rigour and accuracy of solution designs.
Design Science is the structured and systematic process for creating designs that resolve problems. It is concerned with the structured process for the acquisition and application of knowledge in relation to the problems to the resolved and the solution knowledge to be applied.
The application of Design Science must be a means to an end – better solution quality – and not an end in itself – an incentive for the design function is to become large.
Solution architecture requires a (changing) combination of technical, leadership, interpersonal skills, experience, analysis, appropriate creativity, reflection and intuition applied in a structured manner.
Knowledge management – problem knowledge and solution knowledge – is at the core of the application of design science principles.
Knowledge management requires good management of the solution architecture function.
Introduction to Enterprise Architecture and TOGAF 9.1iasaglobal
Santos Pardos nos dará una visión general a TOGAF. Durante 2 horas, Santos nos introducirá al mundo de The Open Group Architecture Framework (TOGAF), ese marco de trabajo de Arquitectura Empresarial que muchos escuchamos hablar. Nos contará el enfoque propuesto para el diseño, planificación, implementación y gobierno de una arquitectura empresarial de información. También repasará, a alto nivel, cuatro niveles o dimensiones: Arquitectura de Negocios Arquitectura de Aplicaciones Arquitectura Tecnológica Arquitectura de Dat
It is well known that an effective PMO is key to successful and efficient program and project execution. In other words, doing things “right”. Enterprise Architecture is the discipline that plans and monitors enterprise transformation and aligns the business strategy with information technology capabilities. In other words, doing the “right things” to support the business.
Why is it organizations despite having both of these disciplines still struggle with effective enterprise transformation? What can we done to use these disciplines more effectively to effect better business outcomes? What are the roles of each discipline and how do they work together to create business value?
In this presentation, Riaz will address these questions and will provide real life examples that can help build a strong relationship between the PMO and Enterprise Architecture.
Learning Objectives:
• How to build a strong relationship between the PMO and Enterprise Architecture (EA) to deliver positive outcomes for your organization
• Identify the different roles and functions of the PMO and EA as well as their similarities
Introduction to Enterprise architecture and the steps to perform an Enterpris...Prashanth Panduranga
This presentation was used to introduce Enterprise Architecture, Introduction to how to perform an Enterprise Architecture Assessment followed by TechSharp introduction.
Deliverables in the presentation is not clear, the slides represent what was shown as part of the demo.
List of deliverables:
Application Rationalization framework
Portfolio Analysis framework
Road Map
Current state analysis
Target State establishing process
System Context
System Landscape
This presentation is on leveraging Enterprise Architecture Governance and Project Portfolio Management Best Practices to:
Accelerate project execution
Manage project and architecture inter-dependencies
Deliver realised value
Improve Enterprise and PMO collaboration
How to develop and govern a Technology Strategy in 10 weeksLeo Barella
This presentation covers the organizational layout, EA Services and EA Governance processes necessary to develop and govern a technology strategy effectively.
Application rationalization- Invest today to save tomorrow!Vivek Mishra
As organizations grow, their IT environment gets complex with all the digital applications acquired over time. Due to this, the platform is plagued by data silos and unstructured applications that do not work together anymore. This is where application portfolio rationalization or APR kicks in.
Learn how APR can help you in streamlining the existing application portfolio with an explicit goal of improving efficiency, reducing complexity, and lowering Total Cost of Ownership.
Design Architecture Review Board (ARB) to Enable Digital Strategy Mohan K.
Architecture Review Board (ARB) to Enable Digital Strategy Execution - *Based on case study of establishing Architecture Review Board (ARB) at a multinational manufacturing
Digital Transformation And Solution ArchitectureAlan McSweeney
Digital strategy is a statement about the organisation’s digital positioning, competitors and customer and collaborator needs and behaviour to achieve a direction for innovation, communication, transaction and promotion. Digital strategy needs to be defined in the same framework structure as the proposed digital architecture platform.
Achieving the target digital organisation means deploying solutions that enable the digital architecture. Solution architecture needs to design solutions that fit into the target digital architecture framework. This requires:
• Solution architecture team operating in an integrated manner designing solutions to a set of common standards and that run on the platform
• Solution architecture team leadership ensuring solutions conform to the common standards
• Solution architecture technical leadership to develop and maintain common solution design standards
• Solution architecture updates the digital reference architecture based on solution design experience
Digital solution design requires greater discipline to create an integrated set solutions that operate within the rigour of the digital architecture framework. The solution architecture function must interact with other IT architecture disciplines to ensure the set of solutions that implement the digital framework operate together. This requires greater solution architecture team leadership. This needs to be supplemented and supported by a well-defined set of digital solution design standards.
This follows-on from the previous presentation: Digital Transformation And Enterprise Architecture
https://www.slideshare.net/alanmcsweeney/digital-transformation-and-enterprise-architecture.
According to Gartner, "The stongest performing IT organizations are distinguished by strong strategy practices. The weak performing IT organizations are distinguished by weak delivery practices."
Having an IT strategy and executing it are important.
This brief presentation covers:
1. Why IT Strategy?
2. What does a great IT Strategy look like?
3. How to create a great IT Strategy
4. How to make the IT Strategy real
A simple guide to learn what EA is, why it’s important and how you can be using it to help your enterprise.
For more information: info@boc-group.com
Try ADOIT for EA:
https://www.boc-group.com/adoit/#test-it
This examines the potential for the application of Design Science principles to the solution design process within solution architecture to improve the rigour and accuracy of solution designs.
Design Science is the structured and systematic process for creating designs that resolve problems. It is concerned with the structured process for the acquisition and application of knowledge in relation to the problems to the resolved and the solution knowledge to be applied.
The application of Design Science must be a means to an end – better solution quality – and not an end in itself – an incentive for the design function is to become large.
Solution architecture requires a (changing) combination of technical, leadership, interpersonal skills, experience, analysis, appropriate creativity, reflection and intuition applied in a structured manner.
Knowledge management – problem knowledge and solution knowledge – is at the core of the application of design science principles.
Knowledge management requires good management of the solution architecture function.
Introduction to Enterprise Architecture and TOGAF 9.1iasaglobal
Santos Pardos nos dará una visión general a TOGAF. Durante 2 horas, Santos nos introducirá al mundo de The Open Group Architecture Framework (TOGAF), ese marco de trabajo de Arquitectura Empresarial que muchos escuchamos hablar. Nos contará el enfoque propuesto para el diseño, planificación, implementación y gobierno de una arquitectura empresarial de información. También repasará, a alto nivel, cuatro niveles o dimensiones: Arquitectura de Negocios Arquitectura de Aplicaciones Arquitectura Tecnológica Arquitectura de Dat
In this presentation, Gerhard Botha, Head of Group MES architecture at Sasol, discusses the major technological trends that are set to challenge businesses. He will take a look at opportunities as well as ways to respond to the challenges.
Enterprise Architecture - The Linchpin between Corporate Governance & IT Gove...The Open Group SA
Enterprise Architecture - The Linchpin between Corporate Governance & IT Governance V2
Stuart Macgregor
The presentation (updated to version 2 with new slides and information) focuses on how a synergistic approach between Corporate Governance, IT Governance, and Enterprise Architecture can increase an organisation’s value while reducing cost.
Read more about The Open Group SA at http://www.opengroup.co.za/
The Future for Smart Technology ArchitectsPaul Preiss
The future of software and even hardware is based in ever more complex abilities to adapt to highly dynamic change and input. The Internet of Things brings with it input from billions of sources locally and around the globe and for intelligent architects this represents an opportunity to create deep competitive advantage and customer loyalty.
The Japanese have used intelligent systems for years from cars to trains to vacuum cleaners and there will continue to be smarter and smarter systems. Architects around the world must include this thinking into their designs and strategies. Adaptive social networks, individually designed health care, just in time 3d printing are only some of the components of this coming era.
How to include smart system thinking into designs
How to get started with smart tools like inferencing, fuzzy, neural and other technologies
When to think smart and when to avoid
Possible outcomes to strive for today in preparing your architecture for the age of smart systems
There are many companies and professionals that seem to make Enterprise Architecture some sort unnecessarily complicated black art, but in reality it's actually quite simple at its core. Here's a methodology I developed that approaches EA with a simpler approach.
Integrated Requirements Management with Serena Dimensions RM 02-2016Serena Software
You work in an environment where requirements must be known, validated and tracked through the Application Development and Delivery lifecycle. The webinar presentation talks about
how you can streamline your requirements management process
overcome the challenges of achieving centralized management and visibility of requirements
ensure efficient collaboration and communication among stakeholders,
and achieve comprehensive end-to-end traceability with reporting and metrics.
Join Kay Fuhrmann and Ashley Owen as they talk about integrated Requirements Management and how to overcome the challenges of achieving end-to-end traceability within your complex application development lifecycle.
Building Business & IT Architecture Roadmaps with ArchiMate & TOGAFCorso
Building effective Business and IT Architecture Roadmaps and aligning your business strategy and IT capability with current and future-state architectures with ArchiMate and TOGAF.
Learn about:
• Transition planning
• Milestones with visual status
• Heatmaps and gap analysis
• Lifecycle states
• And more...
Corso webinar slides. Presented on Thursday 25th September 2014 by Larry Wallendorf, Global Pre-Sales Manager Enterprise Architecture at Corso.
This presentation leverages some content from others to give an overview of System and Software Architecture in general and an introduction into the fundamentals of the Iasa architecture model.
Enterprise Architecture, SOA, and their relationships
Apply SOA to Enterprise Architecture – Service Oriented Enterprise Architecture
Service Oriented Enterprise
Service Oriented Applications and Systems
Service Oriented Infrastructure
The Government of New Brunswick Enterprise Architecture RoadmapTamim Rahman
This document can be downloaded as a PDF for a better viewing experience; click on "Save". This roadmap was shared in a Symposium held on September 25th. A summary of this event can be found on http://www.qrs3e.com/gnb_ocio_togaf/
Enterprise Architecture Tools By Eacomposereacomposer
We are an independent software company specializing in Enterprise Architecture Tools and TOGAF since 2006. We are a pure-player for EA tools and EAComposer is our only software product. Our motto is to focus on one thing and do that really well so you can focus on architecture.
IT Strategy and
Enterprise Architecture
Ensuring that the IT
organization is aligned with the business throughout the cycle of innovation, planning and delivery
Aligning the IT
organization’s structure, skills and sourcing strategy with the needs of the business, while promoting employee learning and satisfaction
Defining the technology
architectures and the processes for developing, deploying, enhancing and supporting business capabilities using technology solutions Managing IT resources
and operations to ensure effective and efficient support of business and financial goals
Master Plan and Notional Target ArchitectureJohn Wu
Master plan and notional Target Architecture inherit the top down and vertical architecture theory from traditional architecture development method. It is the first architecture theory among the Light Enterprise Architecture concept of vertical, horizontal and circular architecture theory.
LEA takes the light approach to conduct master plan and the notional target architecture because it is futile to design a frozen blueprint in an organic enterprise.
LEA adopt the ideal of master planning comes from city planning. Master plan and notional target architecture represent the construct and the notion of enterprise target architect. However, it serve as the mean of Enterprise Architecture rather than the end. EA is not only about drawing some high level architecture drawings. It is long term guideline not only for the enterprise mechanical architecture but also used to facilitate collaboration and knowledge sharing.
It is intended for both business and engineering community. It shows how business take advantage of different resources which include not only IT but also human and financial resources. It is not intended as the guideline on how to design or create these resources. EA should not be confused as the enterprise wide solution architecture.
Master plan and notional architecture is delivered in architecture drawing sets and spread sheet for the purpose of intuitive and comprehension by the business community. The notional architecture drawing is not as rigid a the engineering blueprint, It is flexible and creative.
The LEAF is a 3x3 matrix to illustrate EA comprehensively with three main goals suggest to practice EA in three tiers instead of a big bang approach.
The main goals of EA are Align IT to Business; Enable enterprise agility via interoperability, reuse and sharing; Adapt to change in the organic enterprise. To achieve these goals, it takes three architecture disciplines in vertical, horizontal and circular direction..
LEAF suggest to practice EA in three tier approach of Notional EA, Practical EA and Daily EA. A big bang EA approach requires significant investment of time and resources, In the three tier approach, The Notional Architecture is relatively light, The practical EA in segment scope is also light.
153
مبادرة
#تواصل_تطوير
المحاضرة ال 153 من المبادرة
المهندس / محمد زكريا
أخصائي البنية المؤسسية والاستراتيجية الرقمي
بعنوان
"مقدمة عن البنية المؤسسية"
وذلك يوم الإثنين 21مارس 2022
الثامنة مساء توقيت القاهرة
التاسعة مساء توقيت مكة المكرمة
و الحضور عبر تطبيق زووم من خلال الرابط
https://us02web.zoom.us/meeting/register/tZIqcu-spjoiH902NOccdtAoNJnGQ35joBnv
علما ان هناك بث مباشر للمحاضرة على القنوات الخاصة بجمعية المهندسين المصريين
ونأمل أن نوفق في تقديم ما ينفع المهندس ومهمة الهندسة في عالمنا العربي
والله الموفق
للتواصل مع إدارة المبادرة عبر قناة التليجرام
https://t.me/EEAKSA
ومتابعة المبادرة والبث المباشر عبر نوافذنا المختلفة
رابط اللينكدان والمكتبة الالكترونية
https://www.linkedin.com/company/eeaksa-egyptian-engineers-association/
رابط قناة التويتر
https://twitter.com/eeaksa
رابط قناة الفيسبوك
https://www.facebook.com/EEAKSA
رابط قناة اليوتيوب
https://www.youtube.com/user/EEAchannal
رابط التسجيل العام للمحاضرات
https://forms.gle/vVmw7L187tiATRPw9
ملحوظة : توجد شهادات حضور مجانية لمن يسجل فى رابط التقيم اخر المحاضرة.
Selecting Approaches to Enterprise Architecturesallybean
This presentation was given at EAC Europe (the premier European Enterprise Architecture conference) in 2010. It shows how some of the ideas of Systems and Complexity Science can be applied to produce a new way of thinking about EA that is accessible to all stakeholders and supports improved communication between people as well as machines
Cloud Computing Model with Service Oriented ArchitectureYan Zhao
This presentation will discuss cloud computing from the evolution of service orientation point of view. It will discuss cloud computing models, the prior-arts, and the evolution path in federal government from Federal Enterprise Architecture, Service Oriented Architecture (SOA), and Service Oriented Infrastructure (SOI) or Federal Infrastructure Optimization Initiative, to Cloud Computing. It will also discuss the current trend of the new generation IT operating model, as well as the related business impact. While cloud computing is contributing to the enterprise evolution towards service orientation and shared services, appropriate business management and operation mechanisms must be in place in order to practice successfully, e.g. suitable business models, service models, service structure, funding models, operation models, operation structure, as well as lifecycle and governance. This presentation intends to provide a holistic view for the cloud computing evolution and shared service adoption in Federal Government.
This paper introduces the notion of Inter-Enterprise Architecture (IEA) in response to the current evolution of business environment and landscape associated with the adoptions of common service, cloud computing, and social networking. The IEA describes the context, business environment, collaboration channels, partnership opportunities, influential components and relationships across enterprises and business organizations in selected business domain or service domain for a targeted enterprise or business organization(s). The IEA enables enterprises and business organizations to understand its position in currently connected and networked business world. Due to the open and dynamic nature of service adoption and collaboration, and the autonomy of current enterprise structure, culture, and operation environment, it is necessary to explore how business should be architected across boundaries to effectively response to the common service and collaboration environment.
Integrate IT Strategic Planning with Performance MeasurementYan Zhao
This presentation discusses performance modeling, measurement, and management in the context of integrating IT strategic planning with performance measurement in federal government departments and agencies. It presents a cohesive performance measurement and management mechanism across strategic planning, enterprise architecture, capital planning and investment control (CPIC), and enterprise initiatives, which can be driven down to program and project level details as well.
Service Oriented Enterprise Architecture and Service Oriented Enterprise
Enterprise Architecture .vs. Collection of Architectures in Enterprise
1. The Open Group Conference, Washington D.C., July 16 – 18, 2012
Enterprise Architecture vs. Collection of
Architectures in Enterprise
Yan Zhao, PhD
Chief Architect, ArchiTech Consulting LLC
yan.zhao@architechllc.com
www.architechllc.com
July 17, 2012
2. Content Summary
Rationale
EA concept and position
EA vs. a collection of architectures in enterprise
The essential elements for EA development
The focus in each phase and stage of EA
development (e.g. based on TOGAF) to ensure
successful EA adoptions in solutions, initiatives,
programs, and projects
Yan Zhao, Ph.D, ArchiTech Consulting LLC 2
3. Rationale
EA practice needs improvement: EA has been practiced visibly for
over 10 years, necessity is well recognized, but success is limited;
more collection of architectures in enterprise vs. real EA
The major challenges: stakeholder participation, architecture
modeling, architecture usage, architecture maintenance and
program management
Lessons learned:
EA development needs target vision as its soul, and needs core
concepts as its art of creation. The common knowledge of architecture
is applicable to EA
The federated EA development needs to be more effective -> EA vs.
Collection of Architectures in Enterprise
Too much control will be counter-productive
Too much freedom can be chaotic, self adjustment can be very costly
Intention: clarify the concept, find the soul, refresh the core, simplify
the efforts, promote a balanced approach for success
7/17/2012 Yan Zhao, Ph.D, ArchiTech Consulting LLC 3
4. Architecture Concept
Original definition of Architecture by Sir Henry Watton: “In
architecture as in all other operative arts, the end must direct the
operation. The end is to build well. Well building has three
conditions: Commodity, Firmness and Delight”
This definition is applicable to EA as well: EA is an operative
art, the EA products must direct the effective enterprise operation
Commodity: EA should serve all its relevant audience and
stakeholders, should be consistent and understandable by them
(e.g. via multiple views)
Firmness: EA products should be solid and practicable enough for
implementation
Delight: EA has to be well appreciated and accepted to be adopted
and be effective in implementation
Yan Zhao, Ph.D, ArchiTech Consulting LLC 4
5. What is Enterprise Architecture?
Enterprise Architecture (EA) is an enterprise blueprint with descriptions of
enterprise structure and operating models. It consists of business, application,
info/data, and technical architectures as sub-domains (each sub-domain can
drive down further beyond EA).
Program & Project Management
Enterprise Architecture
Business & IT Strategies
Business Application
Architecture Architecture
Security
Architecture
Info/Data Technical
Architecture Architecture
Performance Management Model
Solutions & Execution
Yan Zhao, Ph.D, ArchiTech Consulting LLC 5
6. The Purpose of EA
Establish common vision and views across organizations to
support achievement of common goals (via target vision)
Have a blueprint to support business decision making and
decision impact analysis (via both as-is and target EA)
Provide guidance for enterprise evolution in response to the
continuous change requests imposed from business and
technologies, to avoid less informed decisions (roadmap)
Have better understanding of the current business and system
implementations, identify improvement and optimization
opportunities across board (via as-is EA)
Enable cost reduction and overall performance improvement from
enterprise global optimization. Enable the use of IT effectively
and efficiently across enterprise, so to improve automation
opportunities (via target EA)
Yan Zhao, Ph.D, ArchiTech Consulting LLC 6
7. EA vs. Collection of Architectures
in Enterprise
Enterprise Architecture
Plan: EA consists of architecture artifacts in concert by planning ahead with a
designated purpose and scope for its views
Content: EA is an art of creation, with core concepts serving its soul of vision,
and has the sense of entirety. The level of details should be just good enough
to convey the intent and to serve the purpose. It can be refined in federated
manner by sub-organizations and tasks to go further
Cultural Fitness: EA has to be fit in its cultural environment, with global
optimization in nature, so to be appreciated and accepted for implementation
Collection of Architecture in Enterprise
Architecture artifacts may be developed separately, in different timeframes,
cover different level of content details, and are created from different
perspectives for different purpose
Lack of an overall guidance for the core, the soul, and the disciplinary elements
Make above two work together in concert -> a balanced approach
Provide the essential top-down guidance and governance framework to
facilitate federated EA development effectively
The bottom-up EA development should follow the guidance and governance
framework, so to keep in concert during organic growth
Yan Zhao, Ph.D, ArchiTech Consulting LLC 7
8. EA Best Practice Observation
EA Stakeholder Participation
It needs clear target vision or work direction for stakeholders to understand what
they need to do and why doing it
It needs clearly identify the roles and responsibilities in order to proceed for EA
development and in collaboration with others
EA Modeling
Just by using an EA tool and framework, and follow some widely published EA
process will not get the EA as the end products
EA is a creative art, it needs soul and core concepts
EA Lifecycle and Management
EA is a living art with lifecycle, the evolution of architectural vision, drivers,
insight, intent, and requirements guide EA through its evergreen process
EA is in a complex domain of people, systems, and culture, and in a constantly
changing environment. It is important to balance top-down guidance/governance
with bottom-up flexibility/freedom for organic growth -> collection of federated
architectures developed with discipline.
EA Skills
Bridge technical and business, with breadth and depth in knowledge
Creative and artistic on vision, insight, models and views with abstraction
7/17/2012 Yan Zhao, Ph.D, ArchiTech Consulting LLC 8
9. The Essential Disciplinary Elements for
EA Top-Down Guidance and Governance
EA target vision: a commonly accepted direction, as the soul of
intent and purpose, which is important in identify the scope of EA
efforts, e.g. for both current state assessment and target architecture
creation
EA principles: EA Principles are general rules and guidelines last a
long time, which support enterprise vision, mission, goals and
objectives
EA governance: policies, rules, guidelines, processes,
measurements, and enforcement mechanisms
EA reference architectures: provide guidance for effective,
disciplined, consistent, and cohesive architecture description
mechanism across organizations
EA development approach, methodologies, and tools: these
are selectable for the best fit
EA evolution roadmap: EA products should be alive with evergreen
process in place, which will keep it current and effective all the time
Yan Zhao, Ph.D, ArchiTech Consulting LLC 9
10. The Role and Context of EA Principles
EA principles reflect an enterprise's purpose, vision, and values. It
provides a foundation for EA development and implementation.
•Business mission, vision, value
•Business & IT strategic plan •Industry best practice
•Target vision and requirements •Knowledge & experience
Drivers Guidance
EA Principles
Governance Guidance
Policies & procedures •Reference Architectures
for governance framework Support •EA development
•Solution implementation
Business & IT decision making
(via best practice guidance,
criteria, and constrains)
7/17/2012 Yan Zhao, Ph.D, ArchiTech Consulting LLC 10
11. From EA Principles to Executions
EA Principles
Implications
Governance
Action Items Guidance
Policies & procedures •Reference Architectures
Support •EA development
for governance framework
•Solution implementation
Business & IT decision making
(via best practice guidance,
criteria, and constrains)
7/17/2012 Yan Zhao, Ph.D, ArchiTech Consulting LLC 11
12. EA Governance Structure
Constitution: EA principles
Legislation: guidelines, Judiciary
process, standards, rules,
policies, measurement, etc.
Judiciary: governance
board for enforcement of
execution -> results, and
consequences
Continuous Operation: for
process execution and
sustainable performance
Change of Operation: for Legislation Constitution
determination and
management of changes
7/17/2012 Yan Zhao, Ph.D, ArchiTech Consulting LLC 12
13. EA Framework with Reference Models
Views What How Where Who When Why
Entity/Data Function Network People Time Motivation
B1. List of Entities B2. Operational B4. List of Business B7. List of Stakeholders: B9. List of Events B10. Architecture Vision;
Business Important to the Business Concept Diagram: Locations Role Catalog; Actor/Role Driver/Goal/Objective Catalog
Environment (security entity included) Enterprise View Matrix and Cycles B11. Architecture Principles
B5. Context Diagram Important to the
B8.Organization Model for
(Planner) B3. Business Footprint B6. Business Enterprise Architecture Business
B12. List of Critical Business
Diagram
Business and Enterprise Reference Models
Interaction Matrix
Concerns and Risks
Info/Data Reference Models
F1. Data Entity/Data F3. Business Functional Services and F6. Environments and Location F9 Organization Charts:
Capabilities, F12. Master F13. Performance
Component Catalog for Business and Enterprise Level Architecture
Decomposition: Architecture Building Diagram; Location Catalog Organization
for Info/Data Architecture
Blocks; Business Service Function
Functions, F2. Business
Catalog; Function Decomposition
Diagram
Schedule Model
F7. Locations Mapped to
Services
Decomposition Diagram
Service/Information Diagram F10. Organization/Actor
Services F4. Activity Model
F8. Communication Interfaces: Catalog
F3. Data Entity/Business F5. Business Process Model: Process Interface Catalog
(Owner) Function Matrix Flow Diagram F11. Stakeholder Map
F6. Security Capability Specification Matrix
L3. Application and Service Logical System L9. Distributed Service Architecture:
L1. Logical Data Model: L11. Role/System Matrix L14. Event Diagram L17. Business Rule
Logical Entity Relationship
Models: Architecture Building Blocks
Application Communication Diagram;
L4. Business Services to Application Services
Application Interaction Matrix; L12. System/Organization L15. Model
Systems Diagram
Mapping
L5. Process Flow Diagram
Communications Engineering
Diagram; Processing Diagram
Matrix Process/Event/Control/Prod
(Designer) L2. Data Security L6. System/Function Matrix
L10. Distributed Security Service
L13. Use Case Diagram uct Catalog L18. Business Rule
L16. Process/System Design
Application/Service Reference Models
L7. System/Data Matrix
Diagram Model
L8. Application Security Service Model Realization Diagram
Physical P2. Physical System Architecture: P5. Application and User
P1. Physical P8. Stakeholder
Systems Data Model,
Platform Decomposition Diagram
P3. Logical System Components to
Physical System Components Mapping
for Application Architecture
Location Diagram
List (include
P6. Network Architecture :
(Builder) P4. Physical Security Service Spec. Networked Computing
/Hardware Diagram security)
P7. Network Security Spec.
Technology T1. Information T2. Fannie Mae Technical
Reference Model (TRM): T4. Technology
References Dictionary Technology Principles;
Technology Standards Catalog Portfolio
T3.System/Technology Matrix Catalog
Technology Reference Models
Technology DS1. Data DS2. Building for Technology Architecture
DS3. Network DS4. PoCs DS5. Detailed DS6. Rule
Details Definitions Components (e.g. implementation Schedule Specification
COTS and
Specification (Dictionary) Program) components
7/17/2012 Yan Zhao, Ph.D, ArchiTech Consulting LLC 13
14. Reference Architectures
across EA Sub-Domains
Business Reference Architecture: consists of Business Reference
Models (BRM) describing business environment, capabilities, functions,
and services (in yellow area)
Application/Service Reference Architecture: consists of
Application/Service Reference Models (ARM) describing logical and
physical systems for implementing business functions (in blue area)
Info/Data Reference Architecture: consists of Info/Data Reference
Models (DRM) describing presentation for information and data
structures (in green area)
Technology Reference Architecture: consists of Technology
Reference Models (TRM) covers technology architecture relevant
matters and technology standard specifications (in pink area)
Security Reference Architecture: consists of Security Reference
Models (SRM) addressing security solution options across layers
Performance Reference Model (PRM): serves as motivation and
measurement mechanism for capabilities, functions, and services
improvement
*Note: Many reference models that compose the reference architectures
can be found in EA modeling tools
Yan Zhao, Ph.D, ArchiTech Consulting LLC 14
15. EA Development Approaches,
Methodologies, and Tools
Examples of EA Development Approaches
Service-orientation
Component-based
Model-driven
Examples of EA Development Methodologies
TOGAF ADM
DoDAF
Examples of EA Development Tools
Modeling tools (System Architect, Metis, MEGA, SPARX, ArchiMate, etc.)
Repositories (Troux EA Repository, Rational System Architect Repository, etc.)
Requirements management tools (DOORS, Requisite Pro, etc.)
Presentation tools (EA Modeling Tools, Visio, PowerPoint, etc.)
Examples of Frameworks and Best Practice References
Zachman Framework (a framework)
TOGAF (a framework and best practice reference)
Gartner Framework (a framework with best practice reference)
A Practical Guide to Federal EA (best practice reference)
7/17/2012 Yan Zhao, Ph.D, ArchiTech Consulting LLC 15
16. The Focus in TOGAF ADM Phases to
Ensure EA Adoption
Preliminary Phase
Stakeholder identification
EA program and governance structure establishment (e.g. federated)
EA development approach, methodologies, and tools decision
Phase A: Architecture Vision
EA target vision (driven by enterprise strategic plan)
EA principles and guidance
EA reference architectures
EA evolution roadmap
Phase B, C, D: Architecture Development
Can be accomplished in federated manner across organizations
Phase E: Solution Development
Identify sub-domains, and develop solution architectures
Identify initiatives, programs and projects for implementation
Phase F, G, H: Architecture Implementation
Define and implementation roadmap and transition plan in a federated manner
across organizations, initiatives, programs and projects
Manage EA with lifecycle process and governance
7/17/2012 Yan Zhao, Ph.D, ArchiTech Consulting LLC 16
17. EA Framework with Scope of Focuses
Views What How Where Who When Why
Entity/Data Function Network People Time Motivation
B1. List of Entities B2. Operational B4. List of Business B7. List of Stakeholders: B9. List of Events B10. Architecture Vision;
Business Important to the Business Concept Diagram: Locations Role Catalog; Actor/Role Driver/Goal/Objective Catalog
Environment (security entity included) Enterprise View Matrix and Cycles B11. Architecture Principles
B5. Context Diagram Important to the
B8.Organization Model for
(Planner) B3. Business Footprint
Diagram Enterprise Architecture
B6. Business
Interaction Matrix
Enterprise Architecture Business
B12. List of Critical Business
Concerns and Risks
Capabilities, F1. Data Entity/Data
Component Catalog
F3. Business Functional Services and
Decomposition: Architecture Building
Blocks; Business Service Function
(scope of focus)F12. Master
F6. Environments and Location
Diagram; Location Catalog
F9 Organization Charts:
Organization F13. Performance
Functions, Catalog; Function Decomposition F7. Locations Mapped to Decomposition Diagram Schedule Model
Info/Data Architecture
F2. Business Diagram Services
Service/Information Diagram F10. Organization/Actor
Services F4. Activity Model
F8. Communication Interfaces: Catalog
F3. Data Entity/Business F5. Business Process Model: Process Interface Catalog
(Owner) Function Matrix Flow Diagram F11. Stakeholder Map
(scope of focus)
F6. Security Capability Specification Matrix
L3. Application and Service Logical System L9. Distributed Service Architecture:
L1. Logical Data Model: L11. Role/System Matrix L14. Event Diagram L17. Business Rule
Logical Entity Relationship
Models: Architecture Building Blocks
Application Communication Diagram;
L4. Business Services to Application Services
Application Interaction Matrix; L12. System/Organization L15. Model
Systems Diagram
Mapping
L5. Process Flow Diagram
Communications Engineering
Diagram; Processing Diagram
Matrix Process/Event/Control/Prod
(Designer) uct Catalog L18. Business Rule
L2. Data Security
Diagram
L6. System/Function Matrix
L7. System/Data Matrix
L8. Application Security Service Model
Model Solution Architectures
L10. Distributed Security Service
L13. Use Case Diagram
L16. Process/System
Realization Diagram
Design
Physical P1. Physical P2. Physical System Architecture:
Platform Decomposition Diagram
Location Diagram
(scope of focus)
P5. Application and User
P8. Stakeholder
Systems Data Model, P3. Logical System Components to
Physical System Components Mapping P6. Network Architecture : List (include
(Builder) P4. Physical Security Service Spec. Networked Computing
/Hardware Diagram security)
P7. Network Security Spec.
Technology T1. Information T2. Fannie Mae Technical
Reference Model (TRM): T4. Technology
References Dictionary Technology Principles;
Technology Standards Catalog Portfolio
T3.System/Technology Matrix Technology Architectures
Catalog
Technology DS1. Data DS2. Building (scopeDS4. PoCs
DS3. Network
of focus) DS5. Detailed DS6. Rule
Details Definitions Components (e.g. implementation Schedule Specification
COTS and
Specification (Dictionary) Program) components
7/17/2012 Yan Zhao, Ph.D, ArchiTech Consulting LLC 17
18. Recommended Action Items
Have a target vision as the soul (e.g. in response to next
generation Internet, shared services, cloud computing,
Internet of things, etc.) and have the core concepts in place
before EA development; EA development is not an
engineering process, it is an art of creation for enterprise
operation, like the building architecture for building
construction
Enhance guidance, discipline, coordination, and
governance for EA development. EA is not merely a
collection of architectures in an enterprise
Balance the centralized efforts and control from top-down
with the flexible federated development efforts from bottom-
up to be productive in organic growth, where insightful and
wise decisions have to be made in the Chief Enterprise
Architect level
Yan Zhao, Ph.D, ArchiTech Consulting LLC 18