EA foundations (views + repository)

Enterprise Architecture Foundations
The best way for
Digital Transformation
‫المؤسسية‬ ‫البنية‬ ‫أساسيات‬
‫الطريق‬
‫األمثل‬
‫نحو‬
‫الرقمي‬ ‫التحول‬

Course Structure
0
The Big Picture

ENTERPRISE ARCHITECTURE BIG PICTURE (aligned with Togaf 9.2)
Consume building blocks (BB)
Enterprise
Continuum
Building
Blocks
Generate Building blocks (BB)
Guidelines and Techniques
(Principles, Gap Analysis, CBP, Stakeholder Mgmt. ,…)
Building
Blocks
Catalogs
Matrices
Diagrams
Artifacts
Architecture Development Method (ADM)
Operating Model ( Governance Framework, Architecture Capability , Interaction Model, Architecture Compliance , Architecture Contracts, …)
Architecture Metamodel
Arch. Repository Management
Deliverables
Stakeholders,
Views
&
Viewpoints
Reference Models
Ecosystem Tool Management

1 Architecture Foundations - ‫البنية‬ ‫أساسيات‬
▷Stakeholders, Views and Viewpoints Basics
▷Enterprise Continuum & Architecture Repository
▷Building Blocks
▷Architecture Metamodel
▷Artifacts and Deliverables Basics

SECTION I
1
Stakeholders, Views & Viewpoints Basics
‫النظر‬ ‫ووجهات‬ ‫المنظور‬ ‫أساسيات‬ , ‫العالقة‬ ‫أصحاب‬

Stakeholders, Views & Viewpoints
Stakeholders ‫العالقة‬ ‫أصحاب‬
Concerns ‫اإلهتمامات‬
Views & Viewpoints ‫المنظور‬
–
‫النظر‬ ‫وجهات‬
Ecosystem / System ‫منظومة‬
-
‫نظام‬

EVERYTHING ABOUT ARCHITECTURE RELATES TO DEEPLY UNDERSTANDING OF TWO MAIN
CONCEPTS (WHAT & HOW)
What & How Concepts
Differentiators (HOW) ‫كيف‬
- How do you visualize something ? / How can I do something ?
- Differentiators point of views
- i.e How I Make Coffee ?
Building Blocks (WHAT) ‫ماذا‬
- Identify what you have ?
- Basic unit (Building blocks ) from which something is built up.
- i.e What I Have to Make Coffee ?

AS ENTERPRISE ARCHITECT, ECOSYSTEM/SYSTEM REPRESENT WHAT YOU SHOULD CONSIDER
DURING YOUR ARCHITECTURE-RELATED ACTIVITIES AS “ A SCOPE OF ENTERPRISE IMPACTED”
Ecosystem / System overview Ecosystem
System is a combination of interacting elements organized to achieve one or more stated purposes
Encompasses individual applications, systems in the traditional sense, subsystems, systems of systems,
product lines, product families, whole enterprises, and other aggregations of interest
System N
Ecosystem go beyond
organization boundary to include
its environment industry
(i.e. suppliers, distributors,
customers, competitors,
government agencies, and so on)
Ecosystem network involved
in the delivery of a specific
product or service through
both competition and
cooperation

ECOSYSTEM / SYSTEM REAL EXAMPLE (1/2)
Photosynthesis Ecosystem
Ecosystem
Plant Development System
Photosynthesis Ecosystem
1 2

ECOSYSTEM / SYSTEM REAL EXAMPLE (2/2)
Ant Colony Ecosystem
Ecosystem
Ant Colony System
Ant Colony Ecosystem
1 2

EXTENDED
ENTERPRISE
SCOPE OF EXTENDED ENTERPRISE ENCOMPASSES BOTH ENTERPRISE SYSTEM AND ITS
ECOSYSTEM …
Enterprise / Extended Enterprise overview
Any collection of organizations that has a
common set of goals
Large corporations may comprise multiple enterprises
Enterprise Bigger umbrella care
about its internal system as well
as its ecosystem
Comprises the partners,
suppliers, and customers, as
well as internal business units.
❖ Whole corporation, or division of a corporation
❖ Government agency or a single department;
❖ Chain of geographically distant organizations linked
together by common ownership
❖ Groups of countries or governments working
together to create common or shareable deliverables
❖ Partnerships and alliances of businesses working
together, such as a consortium or supply chain
ENTERPRISE

… TO PRESERVE ITS POSITION, ENTERPRISE SHOULD GUARANTEE ITS COMPETITIVE
ADVANTAGES THROUGH EMPOWERING BOTH INTERNAL AND EXTERNAL PILLARS
Connecting Dots
Goals and values
Resources and capabilities
Structure & Systems
Environment/Strategy Interface
Firm/Strategy interface
Strategy
The Firm
Enterprise
(System)
Environment
Industry
(Ecosystem)
Customers
Competitors
Suppliers
Partners
Complementors

STAKEHOLDERS ARE INDIVIDUALS, TEAMS, ORGANIZATIONS, OR CLASSES THEREOF, HAVING
AN INTEREST IN A SYSTEM
Stakeholders
System

A SYSTEM HAS ONE OR MORE STAKEHOLDERS, EACH STAKEHOLDER TYPICALLY HAS ROLE,
INTERESTS IN, OR CONCERNS RELATIVE TO, THAT SYSTEM
Image Source: Togaf 9.2 Foundation Guide book – Typical set of stakeholders for EA
Stakeholders for Enterprise Architecture

INTERESTS IN A SYSTEM CAN BE RELEVANT TO ONE OR MORE OF ITS STAKEHOLDERS WHICH
CAN BE FUTHER DECOMPOSED INTRO REQUIREMENTS
Architecture Concern = Area of Interest
Functionality
Development
Operations
Acceptance
Concerns
related to
any system
aspects
Performance Reliability Distribution
Authorization Risk Audit Assurance …
Agility Mobility …
Coverage Usability Consistency
…
…
…

ARCHITECTURE VIEWPOINTS ESTABLISHES THE CONVENTIONS FOR CONSTRUCTING, INTERPRETING
AND USING AN ARCHITECTURE VIEW TO ADDRESS CONCERN(S) ABOUT A SYSTEM-OF-INTEREST
Viewpoints / Views
What you see ?
Where are you looking from ?
Viewpoint ‫المنظور‬ View ‫النظر‬ ‫وجهات‬
- Representation of a system from the perspective of
a related set of concerns
- Visualized asset to inform stakeholders that their
concerns are being met.
- An architecture view is always specific to the
architecture for which it is created.
Instance of the completed template
- Vantage point or perspective that determines what you see
- Viewpoint defines the perspective from which an
architecture view is taken.
- The specification of the conventions for a particular kind of
architecture view
- Architecture viewpoints are generic, and can be stored in
libraries for re-use, known as a viewpoint library.
Template

VIEWPOINTS / VIEWS REAL EXAMPLES (1/4)
Building Architecture
VIEWPOINT
VIEW

Scene Viewpoint & Camera View

Human Eye Retina Viewpoint Layers
VIEWPOINT LAYERS (LIBRARY)
LANSCAPE
COMPLEX
VIEW

Protractor Viewpoint (Contradicting Views) – No Cooperation

EA FRAMEWORKS VIEWS / VIEWPOINTS (1/2)
Togaf Standard Viewpoints
Source: https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap31.html

EA FRAMEWORKS VIEWS / VIEWPOINTS (2/2)
Zachman Framework Viewpoints
Source: https://www.zachman.com/about-the-zachman-framework

SECTION I
2
Enterprise Continuum & Architecture Repository
‫المؤسسية‬ ‫البنية‬ ‫مستودع‬ ‫و‬ ‫التصنيف‬ ‫نظام‬

Enterprise Continuum
Architecture/Solution Continuum ‫والحلول‬ ‫البنية‬ ‫تصنيف‬
Arch. Repository Structure ‫البنية‬ ‫مستودع‬ ‫مكونات‬
Tool Standardization ‫المؤسسية‬ ‫البنية‬ ‫أدوات‬
Enterprise Continuum ‫التصنيف‬ ‫نظام‬

WITHOUT DEFINING “A CLEAR CONTEXT”, PEOPLE DISCUSSING ARCHITECTURE CAN OFTEN
TALK AT CROSS-PURPOSES (REFERENCING DIFFERENT POINTS AT THE SAME TIME)
Classification System
Unclassified Docs - Ad Hoc Store
Games Classification of PS Store
1 2

THE ENTERPRISE CONTINUUM PROVIDES METHODS FOR CLASSIFYING ARCHITECTURE AND
SOLUTION ARTIFACTS, BOTH INTERNAL AND EXTERNAL TO THE ARCHITECTURE REPOSITORY
Views & Classification System
Stakeholder
Views
of
a
System
Architecture
Domains
Data
Application
Technology
Business
Security
Strategy Business
Finance
BigData
Data
Mgmt.
AI
CyberSec.
InfoSec.
Foundation Extended
Solution
Architecture
Generic Specific
B
D
A
T
S
B
D
A
T
S
Foundation
Common
Sys.
Industry
Org.
specific
Classification System

THE ENTERPRISE CONTINUUM CONSISTS OF THREE PARTS, EACH PART IS CONSIDERED TO BE A
DISTINCT CONTINUUM
Constituent Parts of the Enterprise Continuum (1/2)
Enterprise
Continuum
Solution
Continuum
Architecture
Continuum
Outermost continuum and classifies assets
related to the context of the overall
Enterprise Architecture
Classifies contextual assets used to develop
architectures, such as policies, standards,
strategic initiatives, organizational structures,
and enterprise-level capabilities
Consistent way to describe/ understand
the implementation of the assets
defined in the Architecture Continuum
Defines what is available in the
organizational environment as re-
usable Solution Building Blocks (SBBs)
Addresses the commonalities and
differences among products, systems,
and services of implemented systems
Represents a structuring of
Architecture Building Blocks (ABBs)
which are re-usable architecture assets
ABBs evolve through their
development lifecycle from abstract/
generic entities to fully expressed Org-
Specific Architecture assets
Useful tool to discover commonality
and eliminate unnecessary redundancy
Guide
specialized form

THE ENTERPRISE CONTINUUM CONSISTS OF THREE PARTS, EACH PART IS CONSIDERED TO BE A
DISTINCT CONTINUUM
Constituent Parts of the Enterprise Continuum (2/2)

THE ARCHITECTURE CONTINUUM SHOWS THE RELATIONSHIPS AMONG FOUNDATIONAL
FRAMEWORKS, COMMON SYSTEMS, INDUSTRY, AND ENTERPRISE ARCHITECTURES …
Architecture Continuum
Specific
Generic
Solution Building Blocks SBBs
B
D
A
T
S
B
D
A
T
S
Foundation
Architecture
Common
Sys.
Architecture
Industry
Architecture
Org.
specific
Architecture
Arch.
Cont.
Solu.
Cont.
Foundation
Architecture
Generic components, inter-relationships, principles, and guidelines that
provide a foundation on which more specific architectures can be built
Common Systems
Architecture
Use services in Foundation Architecture to create an architecture useful for
building common Solutions (high reusable) across a wide number of
relevant domains.
Org-Specific
Architecture
Industry
Architecture
Describe and guide the final deployment of solution components for a
particular enterprise
Integration of common systems components with industry-specific
components (certain vertical industries)

… THAT AIMS TO DISCOVER COMMONALITY AND ELIMINATE UNNECESSARY REDUNDANCY
Architecture Continuum – Examples (1/2)
- TRM (Technical Reference
Model)
- Specific Industry Architecture
- e.g. Retail industry's "Active
Store" architecture (SCOR-
RM)
- Energetics Oil and Gas data
exchange standards
- Bank X Architecture
- Gov. Entity Y Architecture
- Your Org. Architecture
- SOA Architecture
- ERP Architecture
- Security Architecture
- Network Architecture
- Management Architecture
- Operations Architecture
- III-RM
FA CSA IA OSA

SAMPLE COMMON SYSTEMS ARCHITECTURE – SOA REFERENCE MODEL
Architecture Continuum – Examples (2/2)
Related to BDAT Architecture Domains
- Business Service
- Data Service
- Application Service
- Infrastructure Service
SOA is an architecture style for Enterprise Architecture

ALONGSIDE REQUIREMENTS AND PRINCIPLES, ARCHITECTURE CONTINUUM GUIDES, DIRECTS,
AND SUPPORT SELECTION, REALIZATION AND DEVELOPMENT OF APPROPRIATE SOLUTIONS
Architecture / Solution Continuum

THE SOLUTIONS CONTINUUM PROVIDES A CONSISTENT WAY TO DESCRIBE AND UNDERSTAND
THE IMPLEMENTATION OF THE ASSETS DEFINED IN THE ARCHITECTURE CONTINUUM …
Solution Continuum
Foundation
Solutions
Highly generic concepts, tools, products, services, and solution
components that are the fundamental providers of capabilities such as:
- Professional services: training and consulting services
- Support Services: Help Desk
Common Systems
Solutions
- Implementation of a Common Systems Architecture and is comprised
of a set of products and services.
- Represent collections of common requirements and capabilities, rather
than those specific to a particular customer or industry.
Org-Specific
Solutions
Industry
Solutions
- Implementation of the Organization-Specific Architecture that provides
the required business functions
- Structured to support specific Service-Level Agreements (SLAs) to
ensure support of the operational systems at desired service levels
- Implementation of an Industry Architecture, which provides re-usable
packages of common components and services specific to an industry.
- Industry-specific, aggregate procurements that are ready to be tailored
to an individual organization’s requirements
Specific
Generic
Architecture Building Blocks ABBs
Foundation
Solutions
Common
Sys.
Solutions
Industry
Solutions
Org.
specific
Solutions
Arch.
Cont.
Solu.
Cont.
B
D
A
T
S
B
D
A
T
S

- Third-party solution with Specific
Service-Level Agreements (SLAs)
- key operating parameters and
quality metrics to monitor and
manage the organization
environment
- Specific products, services, and
systems solutions that are
appropriate to that industry
- Physical database schema
- An industry-specific point-of-
service device
… THROUGH DISCOVERTY OF WHAT IS AVAILABLE IN THE ORGANIZATIONAL ENVIRONMENT AS
RE-USABLE SOLUTION BUILDING BLOCKS (SBBS)
Solution Continuum – Examples
- Programming languages
- Foundational structures (EDI)
- Generic Approaches to
Organization structuring
- Foundational structures for
organizing IT operations
(such as ITIL or the IT4IT RA)
- Enterprise mgmt. sys. products
- Security system products
- Scalable data warehousing
systems
- “Software as a service”
common apps solutions
FS CSS IS OSS

OPERATING A MATURE ARCHITECTURE CAPABILITY CREATES A HUGE VOLUME OF
ARCHITECTURAL OUTPUT THAT EMPHASIZE THE ROLE OF EFFECTIVE MANAGEMENT …
Architecture Repository Structure (1/2)

… TO OPERATE AND LEVERAGE THESE WORK PRODUCTS, A FORMAL TAXONOMY IS REQUIRED
ALONGSIDE DEDICATED PROCESSES/TOOLS FOR ARCHITECTURAL CONTENT STORAGE
Architecture Repository Structure (2/2)
Architecture
Metamodel
Describes the organizationally tailored application of an architecture framework, including a method for architecture development
and a metamodel for architecture content
Architecture
Capability Defines the parameters, structures, and processes that support governance of the Architecture Repository
Architecture
Landscape * presents an architectural representation of assets in use, or planned, by the enterprise at particular points in time
Reference
Library
Governance
Log
Arch. Requirements
Repository
Solutions
Landscape
Standard Info.
Base (SIB) *
Provides guidelines, templates, patterns, and other forms of reference material that can be leveraged in order to accelerate the
creation of new architectures for the enterprise
Provide a record of governance activity across the enterprise
Provides a view of all authorized architecture requirements which have been agreed with the Architecture Board
Presents an architectural representation of the SBBs supporting the Architecture Landscape which have been planned or deployed
by the enterprise
Captures the standards with which new architectures must comply, which may include industry standards, selected products and
services from suppliers, or shared services already deployed within the organization
* Will be further detailed out in the next slides

DUE TO THE SHEER VOLUME AND THE DIVERSE STAKEHOLDER NEEDS THROUGHOUT AN ENTIRE
ENTERPRISE, THE ARCHITECTURE LANDSCAPE IS DIVIDED INTO THREE LEVELS OF GRANULARITY
Architecture Repository Structure - Architecture Landscape detailed view
Strategic Architectures
- Long-term summary view of the entire enterprise
- Allow for direction setting at an executive level
- Provide an organizing framework for operational and change activity
Segment Architectures
- More detailed operating models for areas within an enterprise
- Can be used at the program or portfolio level
- Organize and operationally align more detailed change activity
Capability Architectures
- Show in a more detailed fashion how the enterprise can support a particular
unit of capability (overview about current/ target capability and capability increments)
- Allow for individual work packages and projects to be grouped within managed
portfolios and programs

DUE TO THE SHEER VOLUME AND THE DIVERSE STAKEHOLDER NEEDS THROUGHOUT AN ENTIRE
ENTERPRISE, THE ARCHITECTURE LANDSCAPE IS DIVIDED INTO THREE LEVELS OF GRANULARITY
Architecture Repository Structure - Architecture Landscape Example
In Y 2000
Revenue
40M$
In Y 2001
Revenue
50M$
In Y 2002
Revenue
20M$
Why enterprise lose revenue ?
Architecture models
over time ( years)
EA as strategic enabler ,
help business decisions
Enterprise planning space where
EA can add true value
Business intelligence
(Business Analytics)
Stakeholder Leave
Architecture Landscape
Architecture
Model 1
Architecture
Model 2
Architecture
Model 3 Capability
Strategic
Segmented

THE STANDARDS INFORMATION BASE IS A REPOSITORY AREA THAT HOLDS A RECORD OF THE
SET OF SPECIFICATIONS, TO WHICH ARCHITECTURES MUST CONFORM
Architecture Repository Structure - Standards Information Base detailed view
Stated in a clear
and unambiguous
manner, so that
compliance can be
objectively assessed
Easily accessible to
projects and therefore
the obligations of the
project can be
understood and
planned for
Basis for
Architecture
Governance
Standards Information Base (SIB)
Business Standards
Application Standards
Data Standards
Technology Standards

IMPLEMENTING THE ARCHITECTURE REPOSITORY IN A TOOL WILL CATER FOR STAKEHOLDER
ENQUIRIES FOR MODELS, VIEWS, AND REQUIRED ANALYTICS FOR DECISION MAKING
EA Tool - key benefits
Promote
RE-USE
Facilitate easier
maintenance of the
architecture
Provide
stakeholders with
relevant models
Enable sharing
of architecture
information
Ensure common
terminology
is used

EA Tool - key Features
IMPLEMENTING THE ARCHITECTURE REPOSITORY IN A TOOL WILL CATER FOR STAKEHOLDER
ENQUIRIES FOR MODELS, VIEWS, AND REQUIRED ANALYTICS FOR DECISION MAKING
Impact
Analysis
Strategic
dashboards
Workflows
Modeling &
Heatmapping
Dynamic
Deliverables
EA TOOL KEY FEATURES

ENTERPRISE ARCHITECTURE AND INNOVATION LEADERS SHOULD SELECT EA TOOLS THAT
SUPPORT LONG-TERM BUSINESS TRANSFORMATION, MODERNIZATION AND INNOVATION GOALS
Tool benchmarking

Thanks!
For Further Engagement
You can find me at:
eng.mohamedzakarya@gmail.com
Mohamed Zakarya Abdelgawad

EA foundations (views + repository)

Recommended

More Related Content

What's hot (20)

Similar to EA foundations (views + repository) (20)

More from Mohamed Zakarya Abdelgawad (20)

Recently uploaded (20)

EA foundations (views + repository)