Enterprise architectures for e government development

H T T P : / / W W W . I G I -
G L O B A L . C O M / C H A P T E R / E N T E R P R I S E -
A R C H I T E C T U R E S - G O V E R N M E N T - D E V E L O P M E N T / 7 7 0 9 1
1

H T T P : / / W W W . I G I -
2

ABSTRACT
Two common Strategies for e-Government Development
• Demand based
• Architecture based
A National Enterprise Architectural (NEA) approach provides guidelines form
project planning to technical development and operations. It aligns all the e-
government projects with some standard principles.
In this Chapter following architectures and frameworks have discussed
Zachman Framework
RM-ODP (Reference Model- Open Distributed Processing)
ARCON (A Reference Model for Collaboration Network)
TOGAF (The Open Group Architectural Framework)
FEAF (Federal Enterprise Architecture Framework )
H T T P : / / W W W . I G I -
3

Similarity Between Town Planning & Enterprise Architecture
Long-term plans such as roads,
transportation and communication
networks, provision of utilities,
health and housing facilities, etc
Long-term plans such as
integrated databases, enterprise
applications, e-services at mass
level, legal frameworks etc
H T T P : / / W W W . I G I -
4

provides guidelines at
• the strategic level to design &
implement ICT infrastructure
• starting from the top-level applications to
lowest level of physical IT facilities
• while keeping manpower,
security and governance in view.
Similar to a town plannerH T T P : / / W W W . I G I -
5

• I n s t i t u t i o n a l i z a t i o n
• S t a n d a r d i z e d
D e v e l o p m e n t
• S u s t a i n a b i l i t y
• C o s t R e d u c t i o n T h r o u g h
S h a r e d R e s o u r c e s
• R e t u r n O n I n v e s t m e n t
( R O I )
H T T P : / / W W W . I G I -
6

Pioneer in EA
development & implementation
Government Open Systems
Interconnection Profile (GOSIP) in 1980
The law on public IT acquisitions
supported the EA
Federal Chief Information Officer Council
(CIOC) published the "Federal Enterprise
Architecture Framework (FEAF) in 1999
Based on Zachman & TOGAF
H T T P : / / W W W . I G I -
7

Standards and Architectures for
e-Government Applications
(SAGA) initiated by Federal
Administration (KBSt) as a NEA
It is based on Reference Model-
Open Distributed Processing (RM-
ODP)
It evolved and extended to
e-Government 2.0 &
Deutschland-Online programs
H T T P : / / W W W . I G I -
8

e-Government
Interoperability
Framework (e-GIF)
in 2001
e-GIF is a popular
framework and has been
adopted by some Commonwealth
countries
Scotland is using the Open Scotland
Information Age Framework (OSIAF)which
is extension of e-GIF
New Zealand also owns e-GIF
UK Government has introduced a new cross-
Government Enterprise Architecture (xGEA). It
supports the better inter-working between agencies
through the agreement of shared standards
The Reference Model of xGEA is xGEARM having
repository of Architectures for administrative branches
and their agencies to develop departmental EAsH T T P : / / W W W . I G I -
9

e G o v C H w a s
i n i t i a t e d i n 2 0 0 6
a s N E A b a s e d o n
T h e O p e n G r o u p
A r c h i t e c t u r a l F r a m e w o r k
( T O G A F ) a l s o a i m s t o p r o m o t e
o p e n s o u r c e , v e n d o r - n e u t r a l
a n d f r e e l y a v a i l a b l e t o o l s
T h e S w i s s I T C o u n c i l A p p r o v e d
t h e O p e n S o u r c e S o f t w a r e ( O S S )
a n d O p e n S t a n d a r d S t r a t e g y I n 2 0 0 4
e G o v C H i s S e r v i c e - o r i e n t e d P a r a d i g m .
I t a l s o t a k e s c a r e o f P o l i t i c a l a n d L e g a l
C o n s t r a i n t s
H T T P : / / W W W . I G I -
10

A n E A t o o l k i t
“ B u s i n e s s T r a n s f o r m a t i o n
E n a b l e m e n t P r o g r a m ( B T E P )
w a s i n t r o d u c e d f o r
1 . T h e s t r a t e g i c r e f e r e n c e m o d e l s
o f C a n a d i a n g o v e r n m e n t :
i t s u g g e s t s a c o m m o n m o d e l i n g
l a n g u a g e f o r f e d e r a l , p r o v i n c i a l
a n d m u n i c i p a l t o m a p t h e i r p r o c e s s e s
2 . T r a n s f o r m a t i o n m e t h o d o l o g y : i t i n v o l v e s
s t e p - b y - s t e p p r o c e s s e s a n d i m p l e m e n t a t i o n
p l a n s
I n 2 0 0 4 , C h i e f I n f o r m a t i o n O f f i c e r b r a n c h o f
t h e t r e a s u r y b o a r d o f C a n a d a s e c r e t a r i a t
d e v e l o p e d G o v e r n m e n t s o f C a n a d a S t r a t e g i c
R e f e r e n c e M o d e l ( G S R M ) u n d e r t h e s h a d o w o f
B T E P
H T T P : / / W W W . I G I -
11

N e t h e r l a n d s
o r D u t c h G o v e r n m e n t
R e f e r e n c e A r c h i t e c t u r e ( N O R A )
i s n o t a m a n d a t o r y m o d e l f o r a d o p t i o n
a c r o s s t h e g o v e r n m e n t a g e n c i e s .
O r g a n i z a t i o n s w o r k w i t h N O R A o n a v o l u n t a r y
b a s i s . N O R A e n a b l e s b e t t e r c o h e s i o n a n d
c o l l a b o r a t i o n a m o n g g o v e r n m e n t b o d i e s
H T T P : / / W W W . I G I -
12

G o v e r n m e n t i n i t i a t e d
A u s t r a l i a n G o v e r n m e n t A r c h i t e c t u r e
R e f e r e n c e M o d e l s ( A G A - R M ) w h i c h
i s b a s e d t h e F E A F
H T T P : / / W W W . I G I -
13

Government
started EA program
in 2002
In 2007, a set of reference
models were introduced
Singapore Government Enterprise
Architecture (SGEA) including
• Business Reference Model (SG-BRM);
• Data Reference Model (SG-DRM);
• Application Reference Model (SG-ARM);
• Technology Reference Model (SG-TRM)
A methodology was developed named as
Methodology for AGency ENTerprise Architecture
(MAGENTA)
to enable agencies to align to and fully support the
government‟s transformation objectives and outcomes.
The program is now called Whole-of-Government Enterprise
Architecture (WOG EA) and aims for end to end service
delivery with integration and shared approach
H T T P : / / W W W . I G I -
14

Denmark
is Europe‟s leader
in the use of NEA.
NEA was initiated in a
white Paper in 2003
NEA implementation approach
is based on incentives and
voluntarism, i.e. there are no rules,
regulations, governing standards and
principles for NEA development in government.
This highly decentralized governance model
provides liberty to municipalities to adopt it
independently and get benefited from experience of
mature and large size municipalities.
NEA was initiated by the Ministry of Science, Technology
and Innovation (MVTU) and is based on the Zachman
framework.
H T T P : / / W W W . I G I -
15

Norwegian
Government developed
a centralized architecture and
translated into domain and
organizational architectures at
the local level.
It is mandatory for national agencies
There is a strong emphasis on open
standards and open software.
The Norwegian NEA comprises technical,
conceptual, organizational and procedural
standards.
It also includes a shared component library
H T T P : / / W W W . I G I -
16

Ministry
of Finance
initiated NEA program
in 1990s.
Finnish Government has been
a leader in introducing ICT
based reforms in public
administration and services.
Many countries learn from Finnish experiences.
The framework consists of four common viewpoints:
business, information, application and technology.
The framework is based on several famous frameworks
such as FEA and TOGAF
H T T P : / / W W W . I G I -
17

NEA IMPLEMENTATIONS
• Strongly Federated: Countries having strong federated structure have
implemented this type of centralized NEA. Usually, these are small
countries needing no decentralization.
• Weakly Federated: Countries who have decentralized their structure at
different sub-national levels implement a devolved NEA structure.
Usually these countries are big in size and have large population. They
may partially decentralize their NEA using devolved models.
• Independent: Countries having nearly independent states/sub-
nationals do not have a mandatory or controlled NEA structure. They
have very broad level guidelines and leave the actual implementation of
EA to the respective states/sub-nationals.
H T T P : / / W W W . I G I -
18

DEVOLUTION / DECENTRALIZATION
In the second half of the century, many countries embraced decentralization in terms of
• political,
• fiscal and
• administrative powers
“Devolution to lower levels has to involve a meaningful transfer of authority
to be acceptable and to work effectively. It also has to maintain horizontal
equity by ensuring a fair distribution of fiscal and other resources across the
units”
The “Soufflé” theory of decentralization described role of political, fiscal, and
administrative decentralization. It proposed that only appropriate mixture of these types
of decentralizations can produce results
H T T P : / / W W W . I G I -
19

DEVOLUTION IN E-GOVERNMENT
Heeks categorized eight main areas of decentralization i-e planning,
organizational structures and staffing, data management, computing and data
management architecture, information systems development, information
technology acquisition, training, and technical support
A centralized approach requires very strong controls, whereas a partial
decentralized approach in which few modules are centralized while few are
decentralized can be cost effective and a better solution for both mature and
undeveloped organizations.
Richard Heeks recommended a „core-periphery approach to public information, a
system that combines both central and local action, and is therefore most
effective. In the Core-Periphery solution is defined as:
“… core-periphery approach that attempts to reconcile the push of the
centralized approach with the pull of the decentralized approach”
(Heeks, 1999).
H T T P : / / W W W . I G I -
20

DEVOLUTION IN E-GOVERNMENT……
Federal level may devolve many powers and service delivery operations to sub-
nationals (local government and municipalities) while policy, enterprise
applications and related databases may be kept centralized.
In this way, integration, standardization, security, technical experience and
investment can be utilized in optimum manner.
As a result, multiple levels of government need to rearrange their roles and
intergovernmental relationships. Devolution in e-governance facilitates the
transfer of few powers related to e-government activity from central
government to sub-national level with respect to other devolutions such as
political, fiscal and administrative power.
e-Devolution highly depends on the devolution of political representation, fiscal
management and administrative control of the e-government functions.
H T T P : / / W W W . I G I -
21

POLITICAL REPRESENTATION
• In a democratic regime, public representation is essential at local level for electronic
service delivery to public and business sector.
• Political ownership and “will” is also very important for the implementation set by
central government.
• Federal and state/provincial governments may select technocrats and political
leaders for effective launching of e-services.
• Local governments and municipalities may set targets for elected councilors for the
mobilization and education of the people for usage of online services.
• Individual participation like polls for need of e-services, quality and reliability of e-
services, and Owning of ruling party, audit by opposition, and mobilization through
none governmental organizations (NGO) or civil society organizations (CSO).
• Trust in e-government services can be improved through these political participations
• Political value chain is as significant in e-government as value chain in industrial
business
H T T P : / / W W W . I G I -
22

FISCAL MANAGEMENT
Fiscal devolution supports the political as well as administrative devolution and
has major role in inter-governmental relations horizontally as well as
vertically.
Economists have believed that in fiscal autonomy can increase the efficiency and
responsibility of sub-national governments.
Many countries have granted greater fiscal autonomy to their sub-nationals for
better planning, budgeting and revenue collection as per their socio-economic
conditions.
Fiscal devolution can provide liberty for the development projects as compared to
the centralized fiscal regimes, however it poses considerable challenges for
macroeconomic management.
H T T P : / / W W W . I G I -
23

ADMINISTRATIVE CONTROL
Reference to the scale of country and traditional administrative devolution, e-
government devolution also needs a complete administrative role in delivering
public services.
Operations of e-services also need some degree of involvement of field staff,
kiosks and back-offices.
This requires administrative work-force at the local government level, hence
requiring devolution in the administrative access of e-government portals or
applications.
High degree of collaboration is required between agencies at different levels, both
horizontal as well as vertical to deliver e-services by using integrated
information
H T T P : / / W W W . I G I -
24

ADOPTION OF DEVOLUTION APPROACH
International experience may be summarized into three
categories:
• Decentralized such as Taiwan
• devolved
• centralized
Singapore, the Netherlands, Korea,
Switzerland and Japan have all
both centralized and decentralized
or devolved governance.
H T T P : / / W W W . I G I -
25

Decentralized Approach Devolved Approach Centralized Approach
Sub-nationals or local
governments may develop their
own software applications,
databases, security models and
provide online services to their
respective stakeholders.
databases, security models by
considering the Federal
Instructions and provide online
services to their respective
stakeholders.
databases, security models by
using shared resources and
provide online services to their
respective stakeholders.
One stop e-government having
all centralized G2C, G2B, G2G
and G2E services
Implementation of few vital
shared resources such as
databases and applications
Shared applications, databases
and services
Instructions for interoperability
and integration of different
independent software
applications and databases of
local governments
Instructions for interoperability
and integration of different
independent software
applications and databases of
local governments
Instructions for the usage of
centralized services
SOPs for operations
Legislation related to complete
decentralization
Local government may establish
e-governments of their own
choice
Legislation related to partial
decentralization
e-governments by adopting
mandatory conditions
Legislation related to partial
decentralization
e-governments by adopting
mandatory conditions
Legislation related to centralized
e-government
Local governments bound to
follow the SOPs defined by
Federal government
Local governments may design
and develop their own EAs
and develop their own EAs
under the Federal government
instructions or broader NEA
and develop shadow EAs under
a comprehensive NEA
Strong and comprehensive NEAH T T P : / / W W W . I G I -
26

E-GOVERNMENT ARCHITECTURAL FRAMEWORK
• e-Government is a complex and multidimensional enterprise system, and needs
comprehensive plan for development, implementation and operations.
• A National Enterprise Architecture integrates all the related initiatives.
• NEA can connect horizontal as well as vertical relationship among national and sub-
national levels.
• Enterprise Architecture is the basic instrument for transformation and reconstruction of
government
• There are many generic EAs available. Five different Enterprise Architectures are
selected for discussion in the light of devolution in e-government
Zachman Framework
RM-ODP (Reference Model- Open Distributed Processing)
ARCON (A Reference Model for Collaboration Network)
TOGAF (The Open Group Architectural Framework)
FEAF (Federal Enterprise Architecture Framework )
H T T P : / / W W W . I G I -
27

• John Zachman introduced Zachman Enterprise Architecture
Framework (ZF) in 1987
• It is the most famous framework among public and
private sectors.
• Majority of the enterprise architectures have been derived from
John Zachman‟s original framework
• Zachman organized different information in an enterprise matrix.
• Each cell of this matrix represents the relation to certain viewpoint
(data, function, network, people, time, and motivation) and of the perception
(contextual, conceptual, logical, physical, and out of context).
• Each column estimates one of the Aristotelian questions: what, how, where,
who, when and why. Each row corresponds to one of the roles: the planner,
the owner, the designer, the builder, and the subcontractor
• This framework is initiated at the planning level and then it bridges with lower
sections containing the technical architecture.
• Overall this framework delivers comprehensive knowledge about the business
process and its technical development.
ZACHMAN FRAMEWORK
H T T P : / / W W W . I G I -
28

H T T P : / / W W W . I G I -
29

E-Devolution and Zachman
Framework
• Zachman Framework (ZF) has
capability to facilitate the
devolution approach for a
centralized e-government.
• Devolution in e-governance may
be accommodated at fourth
column “who” which can address
organization, people and
stakeholders.
H T T P : / / W W W . I G I -
30

REFERENCE MODEL OF
OPEN DISTRIBUTED PROCESSING (RM-ODP)
• RM-ODP was introduced by International Organization for Standardization
(ISO) and International Telecommunication Union (ITU)
• German government implemented it as NEA with name known as SAGA
(Standards and Architectures for e-Government Applications)
• This EA has five viewpoints to explain a complex enterprise system.
• Enterprise Viewpoint
• Information Viewpoint
• Computational Viewpoint
• Engineering Viewpoint
• Technology Viewpoint
H T T P : / / W W W . I G I -
31

REFERENCE MODEL OF
OPEN DISTRIBUTED PROCESSING (RM-ODP)
H T T P : / / W W W . I G I -
32

A REFERENCE MODEL FOR COLLABORATION
NETWORKS (ARCON)
This consists of three perspectives
(1) Life cycle perspective
(2) Environment characteristics perspective
(3) Model intents perspective
These dimensions may be incorporated to establish a virtual government by
collaborative prospective:
“Virtual government – an alliance of governmental organizations (e.g. city hall, tax
office, cadaster office, and civil infrastructures office) that combine their
services through the use of computer networks to provide integrated services
to the citizen through a common front-end”
H T T P : / / W W W . I G I -
33

A R C O N
H T T P : / / W W W . I G I -
34

DEVOLUTION ASPECT IN ARCON
H T T P : / / W W W . I G I -
35

THE OPEN GROUP ARCHITECTURE FRAMEWORK
(TOGAF)
• TOGAF initiated by the Architecture Forum of The Open Group and
progressing since the mid-1990s. TOGAF‟s objective is to facilitate a broad
range framework to develop architectures for enterprises and specifically for
e-governments
• A main area of TOGAF is Architecture Development Method (ADM) that
describes the comprehensive processes from scratch to certain mature level.
• Enterprise Continuum (EC) is very useful feature of TOGAF. ADM and EC
facilitate the requirements of a large organization such as e-government
where number of agencies and sub-national organizations are engaged.
• ADM is based on feedback of experienced architectural practitioners. It
suggests an approach for developing the enterprise architecture, and
integrates the components of TOGAF.
• The Enterprise Continuum is an important component for the communication
and understanding. This is a "framework-within-a-framework".
• e-Government requires enterprise continuum for its NEA implementation and
also needs to develop common understanding among all the stakeholders.
H T T P : / / W W W . I G I -
36

TOGAF
TOGAF is based on the following four architecture domains with respect to e-
devolution.
• Business Architecture aims to address the strategy, policy, governance,
organization, and business processes of the different government services.
Reference to TOGAF as NEA, devolution architecture can also be easily explained
here
• Applications Architecture is the showcase for the technical specifications of
application systems to be deployed. Most important sub domain of this architecture
is the integration specifications.
• Data Architecture includes the data sources of organization. In case of NEA,
centralized and local databases should be documented with the comprehensive
policies regarding data usage, ownership, updating and integration.
• Technical Architecture focuses the ICT infrastructure including hardware,
software and bandwidth necessary for electronic services to all stakeholders of e-
government.
H T T P : / / W W W . I G I -
37

TOGAF: DEVOLUTION
H T T P : / / W W W . I G I -
38

FEDERAL ENTERPRISE ARCHITECTURE
FRAMEWORK (FEAF)
• United States is the pioneer in EA technologies that was triggered by the
Clinger-Cohen Act.
• Federal CIO (Chief Information Officers) Council of USA introduced "Federal
Enterprise Architecture Framework" (FEAF) Version 1.1 for developing EA for
federal agencies.
• The FEAF aims to provide a standard for developing and documenting
architecture explanations.
• A few countries are in the process to following this framework as NEA such as
Australia.
• It evolved from Zachman framework
H T T P : / / W W W . I G I -
39

Common between Zachman & FEAF
Zachman Columns What How Where
FEAF Columns Data Architecture Application Architecture
Technology
Architecture
Planner Perspective List of Business Objects
List of Business
Processes
List of Business
Locations
Owner Perspective Semantic Model Business Process Model
Business Logistics
System
Designer
Perspective
Logical Data Model Application Architecture
System Geographic
Deployment
Architecture
Builder Perspective Physical Data Model Systems Design
Technology
Architecture
Subcontractor
Perspective
Data Dictionary Programs Network Architecture
H T T P : / / W W W . I G I -
40

REFERENCE MODELS OF FEAF
FEAF architecture domains are business, data, applications, and
technology. The Federal Enterprise Architecture Framework is built
using following reference models
• Performance Reference Model (PRM)
• Business Reference Model (BRM)
• Service Component Reference Model (SCRM)
• Data Reference Model (DRM)
• Technical Reference Model (TRM)
H T T P : / / W W W . I G I -
41

DEVOLUTION ASPECT IN FEAF
H T T P : / / W W W . I G I -
42

EVALUATION OF NEA
Governments have to evaluate their investment and efforts spent for the
implementation of NEA . Evaluation model may aim to assess the following
objectives
1. reduced costs (no duplication of efforts, sharing of common resources)
2. providing a complete status of the enterprise,
3. assessment of business-IT alignment,
4. improved change management,
5. improved risk management,
6. improved interoperability and integration, and
7. shortened cycle times
Above mentioned evaluation objectives are not limited. Reference to the
“International Enterprise Architecture survey, 2006”, approximately 45% of the
countries are measuring EA performance including USA, Switzerland, Japan,
Taiwan and Denmark.
H T T P : / / W W W . I G I -
43

SUMMARY
• This chapter introduces the concept of National Enterprise Architecture (NEA) and
emphasizes its importance. Adoption of NEA by different countries is also briefly
discussed.
• A review of e-government implementations of different countries indicates that
governments adopt either a centralized, decentralized or a devolved governing
structure based on their strongly federated, weakly federated or independent
governance models
• This chapter also discusses five different enterprise architecture frameworks in light
of devolved e-government.
• Zachman architecture is the pioneer and is reflected in the implementation of majority
of the NEAs.
• All of these frameworks can be implemented for three different governance
structures.
• RM-ODP and TOGAF are also generic architectures and frameworks that may be
implemented on any governing structure.
• However the Collaborative Network approach is more appropriate for countries
having decentralized or independent governing model.
• The NEAs are approaching a maturity stage. It is now needed to evaluate these NEA
investments and efforts and assess their maturity level.
H T T P : / / W W W . I G I -
44

Enterprise architectures for e government development

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Andere mochten auch

Andere mochten auch (14)

Mehr von Muhammad Farooq

Mehr von Muhammad Farooq (16)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Enterprise architectures for e government development