applying the iso rm-odp standard in e-government b. meneklis 1, a. kaliontzoglou 2,3, d. polemi 1,...
Post on 21-Dec-2015
219 views
TRANSCRIPT
Applying the ISO RM-ODP Standard in e-Government
B. Meneklis1, A. Kaliontzoglou2,3, D. Polemi1, C. Douligeris1
1 University of Piraeus, Department of Informatics {bmenekl, dpolemi, cdoulig}@unipi.gr
2National Technical University of Athens, School of Electrical & Computer Engineering [email protected]
3Expertnet 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 servicesWeb site hosting, limited online
transactionsSecure 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 standardsOMG/CORBAOSF/DCEISO/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
Interoperability
Scalability
Security/Trust
User Friendliness/Accessibility
Cost Considerations
Transparent Automated Processing
Cross-border Characteristics
Limited Training
Compatibility with Existing Infrastructures
Mobility Aspects
Suitability of RM-ODP for E-Government Openness
Scalability InteroperabilityCross-border characteristics
IntegrationCost considerationsCompatibility with existing
infrastructures
Suitability of RM-ODP for E-Government Flexibility
Compatibility with existing infrastructuresMobility aspects
ModularityCost considerations
Federation InteroperabilityCross-border characteristics
Suitability of RM-ODP for E-Government Manageability
ScalabilityLimited training
Quality of ServiceUser friendliness/Accessibility
Suitability of RM-ODP for E-Government Security
Security/Trust Transparency
User friendliness/AccessibilityTransparent 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
e-document
Notification Document
Certification Document
Request Document
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!