Introduction To EA - Session1
Introduction To EA - Session1
Enterprise Architecture
Seemantinee Sengupta
Enetrprise Architecture Resource Division
National Informatics Centre
20 February 2019
Context and Need for Architecture
When do we need an
architecture?
Context and Need for Architecture
Do we need an
Architecture?
Package
Urban House Agency
(HRMS)
Package
Urban House Agency
(HRMS)
Dynamics of Change
….)
Package
Urban House Agency
(HRMS)
11
How to define Enterprise Architecture
• There is a process of architecting which is prescribed by the discipline
of EA.
• It produces outputs that describe the architecture of an enterprise.
• The process of architecting involves, taking stock of the relevant
components or building blocks that make up an enterprise.
• An architect then needs to examine how these components enable or
constrain the enterprise in fulfilling the goals of the enterprise.
• This is done by looking at how the components are organized or
configured, how they are used or how they behave or perform together
• Public transit, schools and parks are afterthoughts • Future-oriented, planned and sustainable
• No common services • Common services
• Inefficient and fragmented processes • Principles and standards (fire, safety, master plan)
• Aesthetically unpleasing • Higher productivity and effectiveness
• Limited scope for growth • Aesthetically pleasing
15
Enterprise Architecture is Analogous to City
Planning for an Enterprise
Governance
IT Strategy
Strategy
Enterprise-wide focus
Transition Planning
Project focus
Business Understanding
IT Change Driven by
Service & Process Architecture
IT
17
Leveraging Enterprise Architecture
Throughout the globe many countries have utilized Enterprise Architecture approach
to successfully undertake transformation journeys
EA mandated by
act of Parliament
Bangladesh Bhutan Malaysia
Step2
Transition State 2
Step1
Transition State 1
22
Thank you
Enterprise Architecture
Frameworks
Each of the frameworks follows different philosophies, and any implementing enterprise may choose bits and
pieces from each of the methodologies, modify and merge them as per their unique set of requirements
The development of the above frameworks has paved the way for multiple Nations (Korea, Singapore, UAE, UK and USA) and Industry
(Microsoft and Oracle) to develop their own tailored enterprise architecture frameworks which are being consumed by enterprises.
27
Zachman Framework (2/2)
28
The Open Group Architecture Framework (TOGAF)
(1/2)
• Detailed method and a set of supporting tools for
developing an enterprise architecture.
• Based on an iterative process model called
Architecture Development Method (ADM)
• TOGAF is developed and maintained by members of
The Open Group
29
The Open Group Architecture Framework (TOGAF)
(2/2)
30
Federal Enterprise Architecture (FEA) (1/2)
• Supports planning and decision-making in US Federal Govt. through
documentation and information providing an abstracted view of
enterprise at various levels of scope and detail.
• Core is Consolidated Reference Model (CRM) – set of 5 interrelated
reference models
• Also provides Collaborative Planning Methodology – a simple,
repeatable process to aid planning
31
Federal Enterprise Architecture (FEA) (2/2)
Consolidated Reference Model Collaborative Planning Methodology
32
Gartner Methodology (1/2)
• Gartner methodology believes that EA is about bringing together
three constituents:
• Business owners
• Information specialists
• Technology implementers
• According to Gartner, EA project must be started with understanding
enterprise direction on business, not with finding its current position.
33
Gartner Methodology (2/2)
• The sequence of future-state EA development
activities include
• Develop requirements - identification of the
business-driven requirements
• Develop principles - qualities that must be exhibited
by an enterprise to realize its goals
• Develop models - detailed drilling down of
architecture content
20 February 2019
India Enterprise Architecture (IndEA)
Framework
Notified as national standard on October 9, 2018
Business Reference Model
Published Documents:
(BRM)
Provides Portfolio
of Services to
• IndEA Framework
Provides Application Defines methods for
Application Reference Portfolio & S/w Outcome
Performance Reference
Model (ARM) Development methods to Assessment to Model (PRM)
• IndEA Primer
Technology Specifies Technology
Landscape &
Specifies Standards &
Best Practices for
Security Reference
Reference Model (TRM) Standards of
Guides Design &
Security of assets of Model (SRM)
Implementation of
Architecture Governance
Reference Model (GRM)
Aadhaar eSign Digital eTaal ServicePlus Unified PFMS MyGov.in BharatNet IndEA Vibrant
(Digital ID) Locker Payments & UMANG & DSS Private
Interface Sector
19/07/2022 Digital
National India
Informatics Centre 39
UN eService Maturity Model: Connected Services
is the Next Stage of Progression for India
Present
Future
One Citizen –
Little system
Low Multiple
Siloed Systems flexibility for
interoperability
quick change
Government
Experience
…
One Citizen –
Little system
Low Multiple
Siloed Systems flexibility for
interoperability
quick change
Government
Experience
…
IndEA Vision
ONE Government
IndEA Principles
IndEA Reference Models
GoI Ministries States & UTs PSUs
• Unified & Uniform Interfaces
Interoperability
SDG Approach
•
Prioritization
Citizen/ Business-centric Services
Shared Infra
Applications
engineering
Change Mgt
Standards
Common
Process
• Guaranteed Service Levels
Open
Re-
• Effective Program Management
• Less Government, More Governance
• Security & Privacy
Transportation
Public Safety
Disaster Management
Skill Development
Rural Development
Social Justice
Tourism
Health
Education
Infrastructure
Primary Sector
16 Verticals
12 Horizontals
IndEA Core
Financial Management
HR Management
Performance Management
Procurement
Litigation Management
Land &Resources Management
Grievance Management
Unified Contact Center
Standardize
Data Analytics Integrate
Service Delivery Management Virtualize
Right To Information
48
Thank you
XXX
National Informatics Centre
Ministry of Electronics and Information Technology
Government of India
50
Value of an Architectural Reference Model
• An Architectural Reference Model
• Depicts the Components of each Domain (Business, Application, Data etc)
• Identifies the relationships between the Components
• Defines the Standards applicable to the Domain
51
IndEA RM to Implementation
• Problem Space
• Constraints
• Stakeholder Needs
• Opportunities
• Business Reqts
IndEA Reference
Solution
Reference Arch Dev Architectures for Solution Design Implementations
Model(s) the Domain Architecture
52
53
GOAL
Goal Defines
Objectives v
Govern
Programs, Projects, Schemes
REFERENCE MODEL
Sectors
Relate to
ORGANIZATION
BUSINESS
Consist of
Departments
Provide
SERVICES
BENEFITS & RESULTS
Comprises of
Objective
Channels
Analyses
Output
Specifies
Type
Category Service Provider Outcome
BPR Change Management
Priority Beneficiary Economy
Service Level 54
PERFORMANCE
REFERENCE MODEL
55
DATA
REFERENCE MODEL
56
Dept-SPECIFIC APPLICATIONS 11
Public Safety Urban Devpt Rural Devpt Public Distribution System Energy
GROUP APPLICATIONS 9
Meta-model of ARM
COMMON APPLICATIONS 14
Finance Mgt HR Mgt e-Procurement E-Office e-Cabinet
Grievance Mgt
Scheme Mgt Performance Mgt Content Mgt
Unified Call Centre
License Mgt Litigation Mgt Data Analytics RTI GIS
57
TECHNOLOGY REFERENCE MODEL
Performance Reference Model (PRM) Business Reference Model (BRM)
PRM and BRM Provi des I nput To Provides Input To
Provides Input To
P r o v id e s In p u t T o
Technology Reference Model (TRM)
TR M Components
Grouped By
C o n s is ts O f
C o n s is ts O f
Open S tandards
G o v e r n a n c e R e f e re n(Gc eR M) o d e l
) od el
Compri ses of
Open S ource Products
c e MM
Delivery Platforms and
Proprietary Products
In te g r a ti o n R e f e r e n (IR
Open F ormats Cloud
P r o v id e s In p u t T o
Compri ses Of
P r o v id e s In p u t T o
IT Infrastructure Input
PRM
Subject To SLAs / OLAs To
Subject To
Connects To Connects To
Communi cation Interface for Intra/ Service Outlets,
Infras tructure Interface Internet Objects Devices & Applications
Provides Input To
58
INTEGRATION REFERENCE MODEL
59
IndEA Security Reference Model
BRM Risks
Provide inputs for of to Information
Provides Assessment Assets
Supports DESIGN of Threats
Business Vision
Strategies Security Policy Risk Management
Indicates
Requirements
Business Priorities of
Services Data Layer
Guides choice of Guides choice of
Application Layer
Are
Are
Red dotted line delineates
Perimeter Layer Additional
the scope of SRM Controls Controls
applied at
applied at
Network Layer
Endpoint Layer
Reference Model Level
Enables Design of
Performance to
Government
Reports Progress of
Development to
Reports
Architecture
Provides Architecture Vision to Provides Approvals & Resources to
Participates in
A Structure A Structure
Has Architecture IT Has
Roles & Governance Board Governance Board Roles &
Reports
Responsibilities Responsibilities
Architecture
Compliance to
Principles
Technology
Mobile First
Independence
Federated Orchestration
62
PRINCIPLES OF
IndEA (36 OF 36)
63