0% found this document useful (0 votes)
113 views63 pages

Introduction To EA - Session1

The document introduces enterprise architecture and discusses when architecture is needed. It states that greater complexity requires more formal architecture. For large, complex enterprises, architecture is essential to guide development and change. Enterprise architecture describes an enterprise's current and future services, processes, information systems and how they are aligned with its goals. The value of architectural thinking is a well-planned, sustainable and efficient enterprise versus an unplanned one that is inefficient and limited. Enterprise architecture provides governance, strategy and standards for an enterprise in the same way a city plan provides structure for a city.

Uploaded by

Somnath Mitra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
113 views63 pages

Introduction To EA - Session1

The document introduces enterprise architecture and discusses when architecture is needed. It states that greater complexity requires more formal architecture. For large, complex enterprises, architecture is essential to guide development and change. Enterprise architecture describes an enterprise's current and future services, processes, information systems and how they are aligned with its goals. The value of architectural thinking is a well-planned, sustainable and efficient enterprise versus an unplanned one that is inefficient and limited. Enterprise architecture provides governance, strategy and standards for an enterprise in the same way a city plan provides structure for a city.

Uploaded by

Somnath Mitra
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 63

Introduction to

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?

In simple endeavors, for example


construction of a mud hut, a
formal architecture blueprint may
not be needed to ensure
successful construction and
subsequent maintenance
Context and Need for Architecture
Do we need an
Architecture?

In simple endeavors, for example


a wood cabin, a formal
architecture blueprint may not be
needed to ensure successful
construction and subsequent
maintenance
Context and Need for Architecture

Greater the complexity of the


endeavor, greater is the necessity
of a guiding blueprint.

Blueprint is also essential to


undertake further development or
make modifications.

For significantly large endeavors,


not only is a blueprint essential, a
phased plan/roadmap is a must.
Context and Need for Architecture

Building large, complex,


enterprise-wide information
systems without an
enterprise architecture is like
trying to build a city without
a city plan.
Can you build a city without a
city plan? Probably Yes.
Would you want to live in
such a city? Probably not.
Context and Need for Architecture
Township State Enterprise and Partner Systems

Gated Community Sector ERP, CRM, SCM, …

ERP (FMIS, HRMS,


Residential Tower Department
….)

Package
Urban House Agency
(HRMS)

Wood Cabin Service Module


Architecture for Architecture for
Hut Architecture Request Service Delivery Program Information Systems
for Construction in State of Enterprise
Context and Need for Architecture
Township State Enterprise and Partner Systems

Gated Community Sector ERP, CRM, SCM, …

ERP (FMIS, HRMS,


Residential Tower Department

Complexity due to Size & Scale


….)

Package
Urban House Agency
(HRMS)

Wood Cabin Service Module


Architecture for Architecture for
Hut Architecture Request Service Delivery Program Information Systems
for Construction in State of Enterprise
Enterprise Architecture – A Recap
Context and Need for Enterprise Architecture
Township State Enterprise and Partner Systems

Gated Community Sector ERP, CRM, SCM, …

ERP (FMIS, HRMS,


Residential Tower Department

Dynamics of Change
….)

Package
Urban House Agency
(HRMS)

Wood Cabin Service Module


Architecture for Architecture for
Hut Architecture Request Service Delivery Program Information Systems
for Construction in State of Enterprise
Defining Enterprise Architecture

19/07/2022 National Informatics Centre 10


Defining Enterprise Architecture
• Enterprise: Any collection of organizations that have common goals
• Union Government or State Government at broader level
• Individual Ministry or Department at narrower level

• Enterprise Architecture: Description of


the current and future services, processes
and information systems of the enterprise
aligned with its vision.

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

19/07/2022 National Informatics Centre 12


How to define Enterprise Architecture
• Study the enterprise in its current state and how it should be in the
future.
• Work out the alternatives for moving from the current state to the
future target state.
• Create frameworks to manage the architecture, spell out descriptions
of the architecture and its components and road maps to show the
best way to change or improve the architecture.
• Assess the constraints and opportunities, costs, benefits, risks and
value in each option to help decision makers to select the best
alternative.
19/07/2022 National Informatics Centre 13
Do we need enterprise architects?
• No there are many enterprises that exist without the intervention of a
enterprise architect. However, there are many situations when it is
better to architect an enterprise than to leave the creation and
evolution of its architecture to chance.
• Every enterprise will always have an architecture, its not optional. But
we do have a choice ..whether we manage its evolution or not and
how well we manage it.

19/07/2022 National Informatics Centre 14


Value of Architectural Thinking

• 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

Aligning Change to Business Need


Enterprise Architecture
Governance IS/IT
Architecture Architecture
• Service • Information
• Process • Application Enterprise Architecture: “the city plan”
• People • Technology

Transition Planning
Project focus

Government Processes & IT Systems


IT Solutions
IT Solutions Solution: “the building design”
16
EA – The Building Blocks

Strategy & Performance Architecture


Business

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

The United States Singapore South Korea Australia


of America

Estonia United Kingdom New Zealand Germany Finland

EA mandated by
act of Parliament
Bangladesh Bhutan Malaysia

19/07/2022 National Informatics Centre 18


EA Leveraged to Plan and Manage
Transformations
Goal
Target State

Step2

Transition State 2

Step1
Transition State 1

19/07/2022 National Informatics Centre 19


Benefits of Enterprise Architecture

Higher RoI from


investments in
Increased efficiency of Improved effectiveness of
technology, through
service delivery scheme implementation
common, re-usable
components

Increased innovation Increased agility through


enabled by a defined quicker technology Seamless interoperability
architecture and its changes in response between systems
governance dynamic business changes
20
Decisions in Enterprise Architecture
• Should we use a common set of applications across different
programs / services OR develop independent applications?
• Which systems must we develop / enhance / retire?
• Which data area / elements must we standardize across the
enterprise?
• What enterprise-wide interfaces should our systems provide?
• Should we standardize the technology we use?
• What kind and which current or upcoming technologies should we
invest in?

19/07/2022 National Informatics Centre 21


Key Takeaways
• Enterprise architecture:
• is to understand the enterprise on a holistic basis (business, technology and
operating environment)
• helps effectively direct the enterprise to deliver strategic goals by aligning
business and technology operations to strategic intent
• We need enterprise architecture to:
• improve service delivery efficiency and scheme implementation effectiveness
by improving alignment of business & technology to strategic intent
• increase agility by making faster changes in response to dynamic business
• increase RoI from technology investments through optimized landscape
enabled by common & re-usable components

22
Thank you
Enterprise Architecture
Frameworks

19/07/2022 National Informatics Centre 24


EA Frameworks Overview
EA Frameworks typically include:
TOGAF
• Processes & methods
• Catalog of architecture deliverables
Enterprise Architecture and artifacts
Gartner FEA
Frameworks • Content model and repository
structure
• Reference models
Zachman
• Best practices, guidelines &
techniques
• Architecture capability development
• Architecture governance &
compliance

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

19/07/2022 National Informatics Centre 25


EA Frameworks Evolution
Year 1987 1994 1996 2002 2003 2006 2009 2017 2018
Zachman’s TAFIM Clinger – FEA replaces TOGAF 8.0 FEA TOGAF 9 IndEA TOGAF 9.2
Enterprise released Cohen Bill FEAF Enterprise completed released created released
Activity Architecture passed Edition (~)
released

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.

The Open Group The Federal Enterprise


The Zachman Framework The Gartner Methodology
Architectural Framework Architecture
The Zachman Framework is The Open Group A federal enterprise Gartner Methodology is
an Enterprise Ontology Architecture Framework architecture (FEA) provides based on the amalgamation
which provides a formal and (TOGAF) is a framework for a common approach for the of Gartner framework and
structured way of viewing enterprise architecture integration of strategic, Meta architecture
and defining an enterprise. which provides an approach business and technology development process.
for designing, planning, management as part of
implementing, and organization design and
governing an enterprise’s performance improvement
architecture
19/07/2022 National Informatics Centre 26
Zachman Framework (1/2)
• Schema - the intersection between two classifications:
• First: Primitive interrogatives – What, How, When, Who,
Where, and Why.
• Second: Derived from the transformation of an abstract
idea into an instantiation – Identification, Definition,
Representation, Specification, Configuration and
Instantiation

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

• These activities are meant to convey a logical


sequence of development-based on
relationships and dependencies, rather than a
rigidly linear sequence of events.
34
IndEA as National Standard
Candida Shadap
National Informatics Centre
Meghalaya State Unit

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 Adoption Guide Data Reference Model Life-cycle Mgt of


IndEA Interoperability Integration Reference
Model (IRM)
(DRM) Enterprise Data of & Integration of

• 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)

19/07/2022 National Informatics Centre 36


Indian eGovernance Context

19/07/2022 National Informatics Centre 37


Indian eGovernance Evolution
From Digitization to Digitalization

Pre 1995 1995 - 2005 2006 - 2013 2014 onwards


• Networks - State HQs • Localized champion driven • NeGP – institutional • Digital India & eKranti –
department / state initiatives & MMPs Transformational initiatives
• Computerization (Banks, initiatives
Railway Reservations) • SWAN - Blocks • BharatNet - Villages
• Networks - District HQ
• eServices with basic • Platform based, integrated,
• Emails, Basic Websites workflows transformative services
• Emphasis on local • Focus on standardisation – • Citizen engagement and
automation & efficiency Infra, Policies, Tools, experience centric

19/07/2022 National Informatics Centre 38


Initiatives & Enablers Partial List
Central Initiatives (17) State Initiatives (16) Integrated Initiatives (11)
• Central Excise and Customs • Employment Exchange (National • e-Courts
• e-Office Career Service Project) • e-Biz
• Income Tax • Crime and Criminal Tracking Networks • e-Procurement
• IVFRT: Immigration, Visa Foreigner’s and Systems (CCTNS) • e-Trade (EDI)
Registration & Tracking • e-District • India Portal
• MCA21 • Commercial Taxes • e-Sangam (formerly National Services
• Passport Seva Project • e-Municipality Delivery Gateway)
• Banking MMP • e-Panchayat • Common Services Centers (CSC)
• Insurance MMP • National Land Records Modernization • Financial Inclusion
• Pensions Programme (NLRMP) • Roads and Highways Information
• e-Sansad • Public Distribution System (PDS) System (RAHI)
• e-Vidhaan • Education • National Geospatial Information System
• NMEICT (National Mission in Education • e-Health (NGIS)
through ICT) • Agriculture 2.0 • Social Benefits
• Urban Governance • Rural Development
• Women and Child Development

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

19/07/2022 National Informatics Centre 40


Current Landscape
While we have developed several systems to automate key government
processes, resulting landscape is far from optimal

One Citizen –
Little system
Low Multiple
Siloed Systems flexibility for
interoperability
quick change
Government
Experience

Senior Leadership has to often put significant efforts


to further gather and organize information for making decisions!
Holistic Enterprise Architecture Led Transformation is an Approach for Future
19/07/2022 National Informatics Centre 41
Current Landscape
While we have developed several systems to automate key government
processes, resulting landscape is far from optimal

One Citizen –
Little system
Low Multiple
Siloed Systems flexibility for
interoperability
quick change
Government
Experience

Senior Leadership has to often put significant efforts


to further gather and organize information for making decisions!
Holistic Enterprise Architecture Led Transformation is an Approach for Future
19/07/2022 National Informatics Centre 42
IndEA Framework

19/07/2022 National Informatics Centre 43


A 2-Speed Model for
Digital Governance

Architecture at Macro-level IndEA


+
for ONE Government

Service Standards at Micro-level DSS


for a rich UX
44
Why IndEA ?
• India is below global average on UN e-Government Index
• We need to take large strides to make up !!
• Enterprise Architecture approach is a good way.

• India has to leverage its current strengths – widely, rapidly!


• Aadhaar, Mobile, Digital India…

• Adoption of IndEA enables a planned development


• Through ‘Architectural Thinking’
45
The IndEA Vision (WoG)

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

TECHNOLOGY STAKEHOLDER BENEFITS PROCESS / PEOPLE 46


The 8 Reference Models of IndEA
Business Reference Model
(BRM)
Provides Portfolio
of Services to
Provides Application Defines methods for
Application Reference Portfolio & S/w Outcome Performance Reference
Model (ARM)
Development methods to Assessment to Model (PRM)

Data Reference Model Integration Reference


(DRM)
Life-cycle Mgt of
Enterprise Data of IndEA Interoperability
& Integration of Model (IRM)

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 36 Principles


Reference Model (GRM)
of IndEA47
The IndEA Business Landscape

Public Distribution System


Energy

Transportation

Public Safety
Disaster Management
Skill Development

Rural Development
Social Justice

Industry, Labour & Employment


Natural Resources & Environment

Tourism
Health
Education

Urban Development & Housing

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

• Adoption of Reference Model


• Enables fast-tracking Architecture Development (cuts 70% of effort)
• Ensures compliance with relevant Standards
• Enables compliance with Architectural Principles

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

Are Specified by Are Enhanced by Are Realized thru Are Assessed by

Service Definition Service Transformation Service Delivery Measurement


Is Achieved by

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

SYSTEMS EXTERNAL TO IndEA


Social Justice Industry Transportation Labour Tourism Natural Resource

GROUP APPLICATIONS 9
Meta-model of ARM

Primary Sector Education Health Works Land Mgt


Concentric 4-Layered

Benefits/ DBT Skill Development Infrastructure Disaster Mgt

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

IndEA CORE PLATFORM 6


Enterprise Portal Enterprise App Store SMS Gateway
API Gateway / ESB India Stack IAM

57
TECHNOLOGY REFERENCE MODEL
Performance Reference Model (PRM) Business Reference Model (BRM)
PRM and BRM Provi des I nput To Provides Input To

Data Reference Model (DRM) Applications Reference Model (ARM)

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

S e c u r ity R e f e r e n c (Se RMM)o d e l


Access Devices,
Th ird Party Ecosystem Open API Gatew ay
Network Components,

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

Apps, App Stores, Architected as


Application Platform, Microservices
ROA/SOA on Cloud
Mobil e Device M gmt, and S OA bas ed
Big Data/IoT Web Services

Connects To Dept. Permises /


Hos ted State Da ta Center
Network Infras tructure At
Connects To
NIC Cloud Data Center
(MeghR aj)
Subject To

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

TRM Service Standards


Provides Input To
Provides Input To
Specifications for eGovernance in India

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

Architecture Level Security Architecture


Supports

Solution Level Protection Detection Response Recovery


Through
Implementation Level Tools Procedures Capabilities Governance
60
IndEA Governance Reference Model

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

Builds Reviews Is Responsible for Manages Implements

Architecture Architecture Architecture Migration of Legacy Green Field Projects


GRC
Capabilities Development Compliance Applications to to fulfil Architecture
Target Architecture Vision
Architecture
Manages

Contract Through Through


Architecture
Incumbent New
Developer
System Integrators System Integrators
Architecture
61
Repository
Prime Principles of IndEA (9 of 36)
SDG Linkage

Reusable Integrated Services


Applications
Primacy
Data Sharing of Cloud First

Principles
Technology
Mobile First
Independence

Federated Orchestration
62
PRINCIPLES OF
IndEA (36 OF 36)

63

You might also like