architecture models to support accessible egovernment services for all

23
Architecture Models to Support Accessible eGovernment Services for All rl Wessbrandt, the Swedish Administrative Development Agency April 2007

Upload: inari

Post on 14-Jan-2016

36 views

Category:

Documents


1 download

DESCRIPTION

Architecture Models to Support Accessible eGovernment Services for All. Karl Wessbrandt, the Swedish Administrative Development Agency 19 April 2007. Local level Elections to the Municipal Council The Municipal Council elects the Municipal Executive Board. Regional level - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Architecture Models to Support  Accessible eGovernment Services for All

Architecture Models to Support Accessible eGovernment Services for All

Karl Wessbrandt, the Swedish Administrative Development Agency 19 April 2007

Page 2: Architecture Models to Support  Accessible eGovernment Services for All

The democratic system in SwedenNational level• Elections to the Riksdag (Swedish parliament)

• The Riksdag elects the Prime Minister, who forms a government

Regional level• Elections to the County Council Assembly

• The County Council Assembly elects the County Council Executive Board

21 Countys

Local level• Elections to the Municipal Council

• The Municipal Council elects the Municipal Executive Board

290 Municipalities

Page 3: Architecture Models to Support  Accessible eGovernment Services for All

Appropriation directions,

allocation of appropriations

and assignments

Appointments to

senior posts and

organisational form

Performance Management

Laws and ordinances

Directing the Operations of Government Agencies

§

Page 4: Architecture Models to Support  Accessible eGovernment Services for All

eGovernment targeted areas

• Service Quality

• Efficiency

• Working Conditions

• Impact on Society

• Transparency

Page 5: Architecture Models to Support  Accessible eGovernment Services for All

Government AgenciesMunicipalities

& Counties

Regulations Guidelines

Verva - The AdministrativeDevelopment Agency

Cabinet

Representatives Representatives

Industry

Representatives

Page 6: Architecture Models to Support  Accessible eGovernment Services for All

Verva – instruments

• Prepare and issue guidelines and ordinances to national

agencies

• ICT-procurement for public sector

• To promote common development and activities

• To promote joint action within the public sector and with the

private sector

Page 7: Architecture Models to Support  Accessible eGovernment Services for All

A Public Administration that is Connected and Coherent

Personal eID Service eIDFront Office Back Office

Organi-sation eID

&Dynamic

Chan-nels

Inter

Office

Page 8: Architecture Models to Support  Accessible eGovernment Services for All

Coherent Case Processing

Styra processer

Verksamhets- och stödsystem

Skapa/fångainformation Hantera information

Söka information

Arkivera [elektroniskt och/eller fysiskt]

Presentera/sändainformation

Stove-pipe systems

XML-converter

Secure eLinkTransport

Information Content

XMLSchema,Metadata,Controlled terminology

Internet

Agency A

Styra processer

Verksamhets- och stödsystem

Skapa/fångainformation Hantera information

Söka information

Arkivera [elektroniskt och/eller fysiskt]

Presentera/sändainformation

Agency B

standardizedmessages

Service Oriented Support

Web catalog

Infra Services

Information Management Platform

Joined-up eGov Services:

Page 9: Architecture Models to Support  Accessible eGovernment Services for All

e-Identification modelTop Down?

Page 10: Architecture Models to Support  Accessible eGovernment Services for All

e-Identification modelBottom Up?

Internet Banking:Some 3 millionaccountholders(out of a populationof close to 9 million)

”Soft eID’s”Download over the netNo Cards – now…

Page 11: Architecture Models to Support  Accessible eGovernment Services for All

• Contract.• ”Token” or other method to handle keys.• Safe identification method.• Client hardware and software.• Help Desk and Revocation.

• Secure Channel• Revocation information• Helpdesk and Service.:

e-Id Service Model

Page 12: Architecture Models to Support  Accessible eGovernment Services for All

Relying Party pays:• For Active User.• For Usage• etc

The User pays• For Certificate.• For Usage.• etc

e-Id Cost ModelPeriod Payment

Transaction Payment

Page 13: Architecture Models to Support  Accessible eGovernment Services for All

What´s in the message envelope?Good practice schema structure, designed for re-use

Page 14: Architecture Models to Support  Accessible eGovernment Services for All

Semantic interoperability: Example from a modeling workshop about the concept ”person”

Stödbegrepp, används för att definiera ett begrepp

Begrepp med definition

säljs till 1:M(köper 1:M)

Sambandstyp, läs i pilens riktning, parentesen visar motsatt riktning

0:11:10:M1:M

Avbildning, 0:M ger svar på hur många? där 0 är minimalt och M är maximalt

Specialisering, används för att ordna hierarkier. Vit ring visar att det kan finnas flera typer av tex slutkunder dvs icke-uttömmande

Fylld ring illustrerar att det finns inga fler varianter dvs uttömmande

Notation

Gemensamma begrepp för myndigheterna: Bolagsverket, Försäkringskassan, Lantmäteriet, Rikspolisstyrelsen och Skattverket

fysisk person

person

juridisk person namnfysisk person

förnamn

tilltalsnamn

mellannamn

efternamn

består av 0:M(ingår i)

består av 1:M(ingår i)

har 0:1(avser ?:?)

personidentitet

tilldelas 0:M(gäller 1:1)

personnummerSamordningsnummer

(GD-nr)tilldelat personnr

folkbokföring

är folkbokförd i 0:1(? 1:M)

fastighet

kommun

sker på

sker på

antingen eller

roll fysisk person

är i ett visst sammanhang 0:M(gäller 0:M)

adress

har 0:Mtillhör 0:M

persons status

befinner sig i 1:1(gäller för 1:M)

personsekretess(folkbokföringssekretess)

omfattas av 0:1(gäller 0:M)

kön

är av 1:1(gäller 1:M)

särskilda behov

har 0:M

födelsedatum

tilldelas 0:1(gäller 0:M)

tilldelas 1:1 unik identitet (uu-id)

levande

död

blivande

ekonomisk status

har 1:Mtilldelas 0:1

är född i 0:1har 1:1

företrädareyrkesbehörighet

näringsförbud

biträdesförbud

konkurs

födelsehemort

födelseortfödelseland medborgarskap

civilstånd

antingen eller

alias

har 0:M(avser 1:1)

har relation till 0:M

Begreppsmodell 051121Person, utökad version

kanaladress (kommunikationsadress)

gäller 0:M(har 0:M)

Page 15: Architecture Models to Support  Accessible eGovernment Services for All

Example: Termbank of the National Health & Welfare Board

http://app.socialstyrelsen.se/termbank/

Page 16: Architecture Models to Support  Accessible eGovernment Services for All

Critical issues & success factors for eGovernment development

Interoperability layers and supporting services

Models and Guidelines

IT Framework Agreements

Page 17: Architecture Models to Support  Accessible eGovernment Services for All

Interoperability Layers

Organisational interoperability

Legal interoperability

Semantic interoperability

Technical interoperability

Based on IDABC EIF

Page 18: Architecture Models to Support  Accessible eGovernment Services for All

Framework of Architectures

Enterprise architecture

Interoperability Architecture

Statskontoret

Page 19: Architecture Models to Support  Accessible eGovernment Services for All

Architecture Framework for eGovernment

User demands and neeeds

Common Front End Functions

Enterprise systems

Enterprise systems

Enterprise systems

Common Resources and Structures

Standards InterfacesProcesses

Regulations Procurements

Verva as a platform for collaboration

eGovernment Specifications

Specifications Methods

GuidelinesStatskontoret 2004

Page 20: Architecture Models to Support  Accessible eGovernment Services for All

Approach according to the OASIS SOA Reference Model

1. Framework – stating basic principles, independent of specific

standards or technologies

2. Reference Architectures – with more detailed guidelines, from different

viewpoints and for different sectors, including references to standards or

common specifications

3. Concrete Architectures, describing the details needed to implement specific

solutions

1 and 2 are central issues, 2 and 3 are handled by the sectors,

by the user organisations and by the vendors and consultants concerned

Page 21: Architecture Models to Support  Accessible eGovernment Services for All

Map and Publish Electronic Information Exchange per Public Authority

Provide info about•Data Base Name•Purpose•Legal basis•Secrecy level (if any)•Access fees (if any)•Information security•Information Interface•Communication Interface•etc.

Open Catalog Service

Authority AAgency B

Board C Agency E

Authority F

Municipality X

Municipality Y

Region Z

Authority D

Public Internet Access

Page 22: Architecture Models to Support  Accessible eGovernment Services for All

A coherent process from idea to working solution to build a collaborative eGovernment system

Standards InterfacesProcesses

Ordinances Procurements

eGovernment Reference Architectures

Specifications Methods

Guidelines

eGovernment Architecture Framework

eGovernment Function Specifications

Working, collaborative implementations

idea

development

implementation

practice

Formal standards InterfacesProcessesSpecifications Methods

General Market Function Specifications

De facto Standards

Page 23: Architecture Models to Support  Accessible eGovernment Services for All

Karl Wessbrandt, the Swedish Administrative Development Agency [email protected]