1. 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, cdoulig}@unipi.gr 2 National Technical University of Athens, School of Electrical & Computer Engineering akalion@softlab.ntua.gr 3 Expertnet S.A.

2. 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

3. 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

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

5. 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

6. 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

7. 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

8. RM-ODP Features Against E-Government Requirements

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

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

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

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

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

14. 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)

15. 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

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

17. 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)

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

19. 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

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

21. 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

22. Thank you!