eGovernment interoperability

1,441 views
1,314 views

Published on

Workshop organised by DG INFSO - eGovernment Unit in Brussels on 18 March 2003

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,441
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

eGovernment interoperability

  1. 1. eGovernment Interoperability World-wide initiatives and future research directions Dr. Luis Guijarro Associate Professor Lecturer on Information Society E-Forum member
  2. 2. Agenda Current initiatives in e-Government interoperability Analysis Future reseach on e-Government interoperability Issues to address
  3. 3. E-Gov interoperability initiatives Timeline 1996 1997 1998 1999 2000 2001 2002 2003 2004 Clinger-Chen Act OMB “e- TODAY “Information Government Cabinet Office “e- Management Strategy Government. A Technology Act” strategic framework for public services in the Information Age” 1720/1999/EC, “Interoperability and T. Carcenac, “Pour access to TEN for IDA” une administration électronique citoyenne” CIO Council, E-Gov EA FEAF 1.1 Guidance 2.0d E-Envoy, e-GIF 4.0 e-GIF 5.0d e-GIF ATICA, CCR 2d CCR 1 EC Enterpise DG, Architecture Guidelines 6.1 Architecture Guidelines 4.1
  4. 4. E-Gov interoperability initiatives E-Government Interoperability Framework Office of the e-Envoy (UK) Mandatory specifications and policies for joined-up and web enabled government Key policies Internet and web standards Browser interface for access XML for data integration Metadata for content management
  5. 5. E-Gov interoperability initiatives Le Cadre Commun d’Intéroperabilité (CCR) Agence pour les TIC dans l'Administration (France) Recommendations for strengthening Public electronic systems coherence and for enabling multi-agency electronic service delivery
  6. 6. E-Gov interoperability initiatives IDA Architecture Guidelines (AG) IDA (Interchange of Data between Administrations) programme (EU) Concepts and reference for optimum inter- operablity between European Institutions, European Agencies, and Administrations in Member States
  7. 7. E-Gov interoperability initiatives E-Gov Enterprise Architecture Guidance (EAG) Federal Chief Information Officers Council (USA) Mandatory target conceptual architecture for Federal E-Gov programs Selected standards for consideration in E- Gov initiatives
  8. 8. Analysis and future directions Framework Two-phase interoperability roadmap Enabling the interoperability Leveraging the interoperability
  9. 9. First phase: definition Enabling the interoperability Interoperability is the ability to exchange functionality and interpretable data between two software entities. It can be defined in terms of 4 enabling requirementes: communications, request generation, data format, and semantics. Source: Mowbray (1995), The essential CORBA
  10. 10. E-GIF E-GIF 5 draft Specifications Interconnection: IPv4, HTTP, S/MIME ... Data integration: XML, XSL, UML, RDF Content Management Metadata XML and e-GMS Access DTV Internet, workstation, mobile phone, game console, PDA, smart card
  11. 11. CCR CCR 2 Standards Interconnectivité: IPv4, FTP, S/MIME... Données: XML, XSLT, UML Format et supports: TIFF,MP3,XML,CGM... Les architectures applicatives: J2EE, RMI/IIOP...
  12. 12. IDA AG IDA AG 6.1 Service Profiles Document archiving Workflow management Document exchange Directory Content interoperability Network management WWW Group working Middleware Carrier Telecommunications Message transfer WAN File transfer Security
  13. 13. E-Gov EAG E-Gov EAG 2.0 draft Standards Human computer interface services HTML, Symbian Epoc ... Data interchange services WAP, J2EE, .NET, WS ... Network services MIME, T.120, H.323... Data management services JDBC, WebDAV ... Security services S/MIME, SAML ...
  14. 14. First phase: analysis Internet and WWW technologies build the interoperability framework core Two approaches: OSI legacy: e-GIF, CCR POSIX legacy: IDA AG, e-Gov EAG Hereby, information CAN seamlessly flow between Institutions CANNOT seamlessly flow for service delivery to citizens
  15. 15. First phase: future directions Goal: Interoperability efficiency Service interoperability Web Services • Service “description, discovery and integration” • Actors: W3C, OASIS Semantics Semantic Web • Higher abstraction level for interoperability • Actors: W3C
  16. 16. Second phase: definition Leveraging the interoperability Build the enterprise architecture Enterprise architecture refers to a comprehensive description of all the key elements and relationships that make up an organization Alignment between • Business processes and goals • IS applications and middleware systems
  17. 17. Zachman Framework TIME MOTIVATION PEOPLE DATA FUNCTION NETWORK What How Where Who When Why List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE SCOPE to the Business Business Performs the Business Operates to the Business Important to the Business (CONTEXTUAL) (CONTEXTUAL) Function = Class of Planner Ends/Means=Major Bus. Goal/ ENTITY = Class of Node = Major Business Planner People = Major Organizations Time = Major Business Event Business Process Critical Success Factor Business Thing Location e.g. Master Schedule e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Owner Owner Ent = Business Entity Proc. = Business Process Node = Business Location End = Business Objective People = Organization Unit Time = Business Event Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) Node = I/S Function Ent = Data Entity Proc .= Application Function Time = System Event People = Role End = Structural Assertion (Processor, Storage, etc) Designer Designer Cycle = Processing Cycle Reln = Data Relationship I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Control Structure e.g. Rule Design e.g. Presentation Architecture TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Node = Hardware/System Builder Ent = Segment/Table/etc. Proc.= Computer Function End = Condition Builder People = User Time = Execute Software Reln = Pointer/Key/etc. I/O = Data Elements/Sets Cycle = Component Cycle Means = Action Link = Line Specifications Work = Screen Format DETAILED e.g. Security Architecture e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF (OUT-OF- CONTEXT) CONTEXT) Sub- Sub- End = Sub-condition Proc.= Language Stmt Contractor Ent = Field Node = Addresses Time = Interrupt People = Identity Contractor Cycle = Machine Cycle Reln = Address I/O = Control Block Link = Protocols Work = Job Means = Step FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE Source: Zachman Institute for Framework Advancement, <www.zifa.com>, as of July 2000
  18. 18. E-GIF E-Services Development Framework
  19. 19. IDA AG Interoperability model dimensions
  20. 20. E-Gov EAG Architectures Models
  21. 21. Second phase: analysis E-Gov initiatives are using tools provided by Enterprise engineering CIMOSA, PSL, EDOC Software engineering UML, Object-oriented Analysis and Design Now, information CAN seamlessly flow for service delivery to citizens
  22. 22. Second phase: future directions Goal: interoperability effectiveness Public service modelling FEAF Business Reference Model Change management Transition • from baseline architecture • to target architecture
  23. 23. Issues to address Is technology a bottleneck for deploying e-gov at my Administration? Which technology will speed my transition to e-gov? Can I know the processes at my Administration? Am I ready for e-gov transition? May I manage the change?

×