Applying the ISO RM-ODP Standard in e-Government B. Meneklis 1, A. Kaliontzoglou 2,3, D. Polemi 1, C. Douligeris 1 1 University of Piraeus, Department.

Slides:



Advertisements
Similar presentations
Logical and Physical Design of an Information System
Advertisements

SOA for EGovernment 1 Emergency Services Enterprise Framework: A Service-Oriented Approach Sukumar Dwarkanath COMCARE Michael Daconta Oberon Associates.
Applying the SOA RA Utah Public Safety ESB Project Utah Department of Technology Services April 10, 2008 Prepared by Robert Woolley.
Open Distributed Processing in SC7 - Status and Future Bryan Wood (Convenor WG19) SC7 AG 12 May 2002.
SOA and Web Services. SOA Architecture Explaination Transport protocols - communicate between a service and a requester. Messaging layer - enables the.
IST Priority - No Venue:Bolzano eMayor Clustering Event Author(s):A. Kaliontzoglou, I. Stamatiou, P. Hengeveld Organisations: Expertnet S.A., Deloitte.
Chapter 6 Methodology Conceptual Databases Design Transparencies © Pearson Education Limited 1995, 2005.
Lecture 13 Revision IMS Systems Analysis and Design.
1 MPEG-21 : Goals and Achievements Ian Burnett, Rik Van de Walle, Keith Hill, Jan Bormans and Fernando Pereira IEEE Multimedia, October-November 2003.
1 Objectives To introduces the concept of software Design. To introduce the concept of Object- Oriented Design (OOD). To Define various aspects about object.
Using Architecture Frameworks
Tools and Services for the Long Term Preservation and Access of Digital Archives Joseph JaJa, Mike Smorul, and Sangchul Song Institute for Advanced Computer.
Lecture Fourteen Methodology - Conceptual Database Design
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
Terregov: eGovernment interoperability on a semantically driven world Interop-ESA/eGov Interop conference Geneva, February 2005 Santos Vicente, María Pérez,
Ministry of Transport, Information Technology and Communications Technological base: Interoperability Tsvetanka Kirilova Ministry of TITC Bulgaria.
Roles and Responsibilities Jahangheer Shaik. Service Specification Specification requires development of three inter-related documents CIM, PIM and PSM.
Web application architecture
International Telecommunication Union ITU-T Study Group 17, Moscow, 30 March – 8 April 2005 New Recommendations on ODP Arve Meisingset Rapporteur Q15.
Training of master Trainers Workshop 10 – 15 November 2012 e-Services Design and Delivery Module VI Emilio Bugli Innocenti.
Key Elements for electronic Local Authorities’ Networks Cagliari, 27 th May 2002 Walter Wenzel CEO of KEeLAN project.
Desired Quality Characteristics in Cloud Application Development Leah Riungu-Kalliosaari.
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Cardea Requirements, Authorization Model, Standards and Approach Globus World Security Workshop January 23, 2004 Rebekah Lepro Metz
ITEC224 Database Programming
An Introduction to Software Architecture
Methodology - Conceptual Database Design Transparencies
Software School of Hunan University Database Systems Design Part III Section 5 Design Methodology.
Methodology Conceptual Databases Design
9/14/2012ISC329 Isabelle Bichindaritz1 Database System Life Cycle.
1 Chapter 15 Methodology Conceptual Databases Design Transparencies Last Updated: April 2011 By M. Arief
Assessing the Suitability of UML for Modeling Software Architectures Nenad Medvidovic Computer Science Department University of Southern California Los.
EMI INFSO-RI SA2 - Quality Assurance Alberto Aimar (CERN) SA2 Leader EMI First EC Review 22 June 2011, Brussels.
Information System Development Courses Figure: ISD Course Structure.
OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative OOI Cyberinfrastructure Architecture Overview Michael Meisinger Life Cycle Architecture Review.
Methodology - Conceptual Database Design. 2 Design Methodology u Structured approach that uses procedures, techniques, tools, and documentation aids to.
1/26/2004TCSS545A Isabelle Bichindaritz1 Database Management Systems Design Methodology.
Ocean Observatories Initiative Data Management (DM) Subsystem Overview Michael Meisinger September 29, 2009.
Openscotland Information Age Framework Craig Russell 21st Century Government Unit, Scottish Executive 29th October 2004.
Identity Management: A Technical Perspective Richard Cissée DAI-Labor; Technische Universität Berlin
Methodology - Conceptual Database Design
Engineering Essential Characteristics Security Engineering Process Overview.
Transboundary Trust Space February 16, 2012 Ensuring trust in information exchange – proposal and approaches from Russia and CIS-states (RCC states) National.
ERP Implementation Fundamentals Richard Byrom Oracle Consultant, Speaker and Author
Semantic based P2P System for local e-Government Fernando Ortiz-Rodriguez 1, Raúl Palma de León 2 and Boris Villazón-Terrazas 2 1 1Universidad Tamaulipeca.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
1 ECCF Training 2.0 Introduction ECCF Training Working Group January 2011.
1 reTHINK Deliverables, How To Read reThink deliverables quick starter.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Geospatial Systems Architecture
Providing web services to mobile users: The architecture design of an m-service portal Minder Chen - Dongsong Zhang - Lina Zhou Presented by: Juan M. Cubillos.
GRID ANATOMY Advanced Computing Concepts – Dr. Emmanuel Pilli.
June California Investor Owned Utilities (IOU) HAN vision statement development 15 June 2007.
Developing an IDM Information Delivery Manual Part 1. Industry Workgroup Training, Creating IDMs Alliance NA 2010 Dianne Davis, NA-IDM Coordinator Jan.
1 Dr. Spyros Papastergiou, University of Piraeus (Greece)–Dept. of Informatics M. Zaharias Singular Logic (Greece) CYSM Risk Assessment Methodology.
Stork is an EU co-funded project INFSO-ICT-PSP STORK PRESENTATION Frank LEYMAN Manager International Relations 04/06/2009.
University of Piraeus Research Centre (UPRC) Assistant Professor Nineta Polemi “PREVENTION, PREPAREDENESS AND CONSEQUENCE MANAGEMENT OF.
INTRODUCTION: This report contains the results of the International Council of System Engineer (INCOSE) UML/SySML Team efforts to produce UML/SySML Architecture.
© The InfoCitizen Consortium Project Presentation Agent based negotiation for inter- and intra-enterprise coordination employing a European Information.
Grid Services for Digital Archive Tao-Sheng Chen Academia Sinica Computing Centre
GEOSS Model Based System Engineering Session Plan By Lawrence E. McGovern, DSC International Council on System Engineering/Blue Heron Services.
Methodology Conceptual Databases Design
CIIT-Human Computer Interaction-CSC456-Fall-2015-Mr
Methodology Conceptual Database Design
Workplan for Updating the As-built Architecture of the 2007 GEOSS Architecture Implementation Pilot Session 7B, 6 June 2007 GEOSS Architecture Implementation.
eMayor at a Glance – Standards
An Introduction to Software Architecture
Dashboard eHealth services: actual mockup
Methodology Conceptual Databases Design
Presentation transcript:

Applying the ISO RM-ODP Standard in e-Government B. Meneklis 1, A. Kaliontzoglou 2,3, D. Polemi 1, C. Douligeris 1 1 University of Piraeus, Department of Informatics {bmenekl, dpolemi, 2 National Technical University of Athens, School of Electrical & Computer Engineering 3 Expertnet S.A.

Topics The e-Government Context ODP Systems Design Methodologies Overview of the RM-ODP Standard Architectural Requirements of e-Government Systems Suitability of RM-ODP for e-Government Example: The eMayor Case Study Conclusions

The e-Government Context Development of e-government services  Web site hosting, limited online transactions  Secure transactions, interactive service delivery, cross-border interactions Efficient and secure electronic exchange and processing of data Geographical dispersion leads to distributed system architectures

ODP Systems Design Methodologies Design standards  OMG/CORBA  OSF/DCE  ISO/RM-ODP

Overview of the RM-ODP Standard Supports distribution, interworking and portability Defines basic concepts of distributed processing Identifies the characteristics that qualify a system as an ODP system Introduces five viewpoints in order to specify an ODP system Provides a viewpoint language to describe each viewpoint Provides distribution transparencies between system applications

RM-ODP Viewpoint Specifications Enterprise viewpoint – Policies, purpose of operation and scope of the system Information viewpoint – Information entities communicated, stored and processed in the system Computational viewpoint – How distribution of processing is achieved Engineering viewpoint – Ways of communication between objects and resources needed for this communication Technology viewpoint – Selected technology of a system

Architectural Requirements of E-Government Systems Interoperability Scalability Security and trust User-Friendliness and accessibility Cost considerations Transparent automated processing Cross-border characteristics Limited training Compatibility with existing infrastructures Mobility aspects

RM-ODP Features Against E-Government Requirements

Suitability of RM-ODP for E-Government Openness  Scalability  Interoperability  Cross-border characteristics Integration  Cost considerations  Compatibility with existing infrastructures

Suitability of RM-ODP for E-Government Flexibility  Compatibility with existing infrastructures  Mobility aspects Modularity  Cost considerations Federation  Interoperability  Cross-border characteristics

Suitability of RM-ODP for E-Government Manageability  Scalability  Limited training Quality of Service  User friendliness/Accessibility

Suitability of RM-ODP for E-Government Security  Security/Trust Transparency  User friendliness/Accessibility  Transparent automated processing

The eMayor Case Study Actual application of the standard E-government platform attuned to the environment of European SMGOs (European municipalities)

eMayor Design RM-ODP principles and concepts applied in combination with UML notation Address the various organisational and architectural needs of the municipalities Examples from three RM-ODP viewpoints (Enterprise, Information and Computational)

eMayor Enterprise Viewpoint Identified communities Main stakeholders Roles assumed defined (e.g. Citizen, Civil Servant, Public Agency) Business processes in the communities identified Policies and constraints to processes described Definition of Enterprise Objects

TTP Sub-Community Enterprise Object Roles  Regional CAs  Pan-European CA  Pan-European Validation Authority  Registered Users Relationships between them defined Processes they follow

eMayor Information Viewpoint Identification of Information Objects used internally and communicated by the eMayor platforms (Class Diagrams) Description of state transitions of the various Information Objects (UML StateChart Diagrams)

eMayor Information Objects E-Document  Request Document  Certification Document  Notification Log File Configuration File Policy

eMayor Computational Viewpoint Overall architecture of the eMayor system Functional decomposition of the system into packages which interact at interfaces Definition of Computational Objects Depicts mechanisms enabling distribution of processing

eMayor Computational Objects User Interface Policy Enforcement Format Transformation Content Routing Service Handling Legacy Systems Adaptation Printing Notification Persistent Storage

Conclusions Suitability of RM-ODP standard in the design of ODP systems for e-government Clear separation of concerns through the viewpoint specifications RM-ODP applied to the design of an actual system

Thank you!