1 / 65

e -Governance for Enhance Service Delivery

e -Governance for Enhance Service Delivery Transfer Knowledge, Develop and Implement Quick Win Pilot E-Services (Service Oriented Architecture (SOA) -Based Business Process Management (BPM)) June 2 nd to 21 st 2012 Amman- Jordan Day 1 Present by:. Agenda.

cricket
Télécharger la présentation

e -Governance for Enhance Service Delivery

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. e-Governance for Enhance Service Delivery Transfer Knowledge, Develop and Implement Quick Win Pilot E-Services (Service Oriented Architecture (SOA) -Based Business Process Management (BPM)) June 2nd to 21st 2012 Amman- Jordan Day 1 Present by:

  2. Agenda

  3. E-Government Enterprise Architecture Reference Model معمارية المؤسسات للحكومة الإلكترونية النموذج المرجعي

  4. Introduction The purpose of the reference architecture model is to provide the government agencies with adequate reference material in order to: • Support government agencies that want to develop their enterprise architecture  • Provide the entities with guidelines that allow them to  hook up with the central architecture • دعم الجهات الحكومية التي ترغب في تطوير البنية المعمارية لأعمالها • تزويد الجهات الحكومية بمبادئ توجيهية لربطها مع معمارية الحكومة الإلكترونية المركزية

  5. Advantages المزايا • Align IT infrastructure and process with enterprise strategy and goals • Supplement the existing e-government strategy and project management methodology with EA Standards & Guidelines • EA sets the standards for informed technical management decisions • EA Promotes "interoperability" among entities • مواءمة البنية التحتية التقنية وعمليات الأعمال مع إستراتيجية المؤسسة وأهدافها • تكملة إستراتيجية الحكومة الإلكترونية القائمة ومنهجية إدارة المشاريع مع معايير ومبادئ هيكلية المؤسسة • هيكلية المؤسسة تضع معايير تساعد الإدارة الفنية على اتخاذ قرارات مستنيرة • هيكلية المؤسسة تشجع على ”التخاطب البيني“ بين الكيانات الحكومية

  6. Componentsالمكونات • Business Architecture: Identify business processes and supporting organizational structure. Help in achieving the business model • Application Architecture : the architecture of applications that support the business processes • Technology Architecture : addressing the infrastructure that supports the applications • DataArchitecture : addressing the information that supports the applications

  7. Enterprise Architecture (EA) Framework • EA Framework is a tool for systematically documenting the enterprise architecture. • EA framework provide the tools and artifacts needed for documenting the architecture. • It also has a Technical Reference Model or TRM, that can be referred to for creating the architecture. • Based on TOGAF or ZACHMAN. TOGAF is more popular • TOGAF: The Open Group Architecture Framework

  8. E-Gov Challenges • Need to transform e-government strategy and vision into concrete business and IT solutions. • Interoperability Issues among entities. • Lack of reuse of functionality (Re-inventing the wheel). • Lack of e-service maturity at some entities. • Limited funding for e-government related activities at entities. • Limited technical skill sets at entities. • Duplicate data ownership.

  9. E-Services E-Services Applications Applications Governance Governance Software Software Infrastructure Infrastructure E-Services Applications Governance Software Infrastructure Technical Architecture Entity Reference Model Entity Reference Model Central Architecture Entity Architecture Entity Architecture Delivery Delivery Interoperability Framework Interoperability Framework Integration Integration Middle ware Middle ware Access Access Governmental Entities E-Government Governmental Entities

  10. Componentsالمكونات • Central Architecture & Building Blocks – Architecture for “common services” such as “Payment Gateway” provided by e-government program that all entities can use. • Entity Reference Architecture – Provide a process that entities can adopt to integrate with central building blocks. Additionally It provides direction for entities to create there own information technology architecture using the “FEAF” Framework. • Interoperability Framework – This framework provide technical standards to streamline interoperability. It provides data standards to create unique standardized XML data dictionaries for common data elements across all entities. This will help in removing any confusion regarding the data ownership, type, relationship or structure. • Governance – The frameworks and architectures described above are subject to the EGAF Governance process, that will ensure that the EGAF remain relevant over time.

  11. e-Government Architecture Framework إطار الهيكلة الحكومة الالكترونية

  12. Business Perspective Information Perspective Application Perspective Technology Perspective Business model Information model Service catalogue Technology platform Process model Logical data model Application architecture model Technical architecture model Workflow model Physical data model Application design model Infrastructure model Framework Overview Conceptual Level Logical Level Operational Level

  13. Business Model Example model Description The business model describes the core and support activities an organization performs. Purpose The business model supports process and service orientation of eGovernment activities

  14. Process Model Example model Description The process model describes processes within and between organisations. Purpose The process model supports process- and service orientation, as well as business process improvement and re-engineering

  15. Workflow Model Example model Description The workflow model describes process and workflow on a detailed level. Purpose The workflow model supports implementation of defined processes using selected technology.

  16. Service Catalogue Example model Description The service catalogue provides a high-level overview of business services and e-services. Purpose The service catalogue makes services visible and/or available to internal and external users.

  17. Application Architecture Example model Description The application architecture describes application components that supports business services and e-services. Validate against Purpose The application architecture provides a vehicle to connect and integrate services and technology

  18. Application Design Example model Description The application design describes implementation of applications. Validate against Purpose The application design supports implementation of specific applications and/or application integration.

  19. Information Model Example model Description The information model describes the core concepts related to a specific area or organisational unit. Purpose The information model provides a shared vocabulary for a specific area or organisational unit.

  20. Logical Model Example model Description The logical data model provides a description of information elements and their relations Purpose The logical data model provides a vehicle for creating a shared definition of a specified area or organisational unit.

  21. Physical Data Model Example model Description The physical data model provides a detailed and technology-specific definition of data elements and their relations. Purpose The physical data model supports implementation of the data model, using a specific technology

  22. Technology Platform Model Description Example model The technology platform model gives a high-level view of the technology platform, including all platform components. Purpose The technology platform model provide the organisation with a high- level understanding of the technology platform.

  23. Technology Architecture Model Example model Description The technical architecture model describes the components and interactions between the components in the technology platform. Purpose The technical architecture models provide a detailed view of a certain area or organisational unit.

  24. Infrastructure Model Example model Description The infrastructure model details the technical components of the solution. Purpose The infrastucture model provides documentation as well as blueprints for ICT systems.

  25. Master Data Essentials أساسيات البيانات الموحدة الأشخاص البطاقة الشخصية شهادة الجنسية المؤسسات العناوين GIS بطاقة السكن البطاقة التموينية الحكومة الإلكترونية الرقم الوطني الموحد العقارات المركبات

  26. E-Government Technical Architecture المعمارية التقنية للحكومة الإلكترونية

  27. Overviewنظرة عامة • Customer/citizen Centric تتمحور حول المواطن • All services centered around customer needs. جميع الخدمات تتمحور حول تلبية احتياجات العملاء • Stakeholders الأطراف: • E-Government الحكومة الإلكترونية • Governmental Entities الجهات الحكومية • Businesses قطاع الأعمال • Customers / Citizens المواطنون • Multiple Access & Delivery Channels: قنوات إيصال و تواصل متعددة: • Traditional التقليدية • Web الويب • Call Center مركز خدمات على الهاتف • Mobile الجوال • SMS رسائل الجوال

  28. Architectureالمعمارية • Central Enterprise Service Bus – ESB • Provides: • Transformation • Mapping • Rounting • Provides Central Services such as Identity Management, Payment Gateway • Orchestrates Business Processes • Acts a central mediator for: • Customer / Government Interactions • Business / Government Interactions • Government / Government Interactions

  29. High Level Integration Architectureمعمارية الترابط

  30. Integration & Canonical Data Modelالترابط و نموذج البيانات القياسي Gov Entity 1 Gov Entity 2 Gov Entity 5 Gov Entity 3 Gov Entity 4

  31. Integration & Canonical Data Modelالترابط و نموذج البيانات القياسي Gov Entity 1 Gov Entity 2 Gov Entity 3 Gov Entity 4 Gov Entity 5 Adapter Adapter Adapter Adapter Adapter Canonical Message Canonical Message Canonical Message Canonical Message Canonical Message Enterprise Service Bus Business Process Engine Shared Services

  32. E-Service Categories فئات الخدمات • Vertical Services (خدمات عامودية):Self-Contained end to end service provided by a governmental entity • Cross Organization Services (خدمات عابرة للجهات الحكومية):A service which requires the involvement of several government entities in order to be delivered. • Composite Services (خدمات مركبة):A service which flows across multiple government entities. Process across multiple entities. • Shared Services (خدمات مشتركة): shared services are defined as the ‘’enablers’’, providing technology-based functionality that are central to the provision of vertical and cross-organizational services such as: SMS Gateway, Authentication, Payment Gateway, etc.

  33. Access Layer PC Business Kiosk PC Home Mobile Access Other Access Gateway/Portal Layer Internet Portal and Content Management Data Conversion Audit & Management Authentication Messaging Transaction Engine Payment Services Secure Government Network Department A Department X E-Gov Portal & Delivery Channelsبوابة الحكومة الالكترونية و قنوات الإيصال

  34. SOA Service Oriented Architecture معمارية الخدمات الموجَّهة

  35. Service Oriented Architecture – معمارية الخدمات الموجَّهة Service-Oriented Architecture (SOA) is a set of principles and methodologies for designing and developing software in the form of interoperable services. These services are well-defined business functionalities that are built as software components that can be reused for different purposes. معمارية الخدمات الموجَّهة (SOA)هي مجموعة من مبادئ تصميم الأنظمة تستخدم في مجال الحوسبة أثناء مراحل تطوير الأنظمة واندماجها. يقدم النظام الذي يستخدم هذه البنية وظائفه على هيئة حزمة من الخدمات المتعاونة التي يمكن استخدامها من قبل أنظمة مختلفة من مجالات تجارية متعددة.

  36. What is a Service A Service is generally defined as: A functionality provided as a modular piece of software, with a well defined interface contract. Service can be accessed by a service consumer by invoking the service interface. وظيفة مقدمة من خلال وحدات برمجية ذات عقد واجهة ربط واضح المعالم. يتمالتواصل مع الخدمة من قبل المستهلكين من خلال استدعاء واجهة ربط الخدمة.

  37. Service Attributes – سمات الخدمة • A service must have a well defined interface. • A service is “loosely coupled”, in that sense changes made to the implementation of the service require no changes from theconsumer. • A service is modular and independent from otherservices. • A service is a reusable unit. • الخدمة تحتوي على عقد واجهة ربط واضح المعالم • الخدمة تقترن مع مثيلاتها بشكل متباعد، بمعنى أنه أي تغييرات في تطبيق الخدمة لا يتطلب تغييرات من المستهلك بفضل عقد الترابط. • الخدمة هي وحدة مستقلة عن غيرها من الخدمات • الخدمة هي وحدة قابلة لإعادة الاستخدام

  38. Service Interface / Contract واجهة / عقد الخدمة

  39. Service Interface / Contract واجهة / عقد الخدمة A service interface is a contract that establishes the identity of the service and the rules of the service invocation. Listed below are details typically presented in a service interface. • Request Data Message • Response Data Message • Exception Conditions • Metadata to identify the function and purpose of the service واجهة الخدمة هو العقد الذي يحدد هوية وقواعد طلب الخدمة. تحتوي واجهة الخدمة على: • بيانات رسالة الطلب • بيانات رسالة الاستجابة • شروط الاستثناءات • معلومات عن وظائف الخدمة والغرض منها

  40. Advantages of SOA مزايا معمارية الخدمات الموجَّهة • Adapt applications to changing technologies. • Easily integrate applications with other systems. • Leverage existing investments in legacy applications. • Quickly and easily create a business process from existing services. • تكييف التطبيقات مع التكنولوجيات المتغيرة • تسهل التكامل مع الأنظمة الأخرى • يتيح إمكانية التخاطب البيني للتطبيقات القديمة بدون تكاليف إضافية • خلق عمليات أعمال بسرعة و بسهولة من الخدمات المتاحة

  41. SOA Principles مبادئ معمارية الخدمات الموجَّهة • Software that enables the services must be modular. • The software modules must be distributable. • Software developers must write or generate interface metadata that specifies an explicit contract so that another developer can find and use the service (this helps enable loose coupling). • The service interface must be separate from the implementation (code and data) of the service provider module . • Service providers must be shareable — that is, designed and deployed in a manner that allows them to be invoked successively by disparate consumers. • يجب أن تكون البرمجيات مبنية بشكل وحدات • يجب أن تكون البرمجيات قابلة للتوزيع على عدة خوادم • يجب على مطوري البرمجيات كتابة أو توليد بيانات واجهة الخدمة لتحديد عقد واضح بحيث يمكن العثور عليه من قبل مطور آخر واستخدام الخدمة (وهذا يساعد على تمكين اقتران فضفاض). • يجب أن تكون واجهة الخدمة منفصلة عن البرمجية المنفذة لمزود الخدمة. • يجب أن تكون الخدمات تشاركية. أي أن تصمم وتنشر على نحو يسمح للمستهلكين طلب الخدمة على التوالي في آن واحد.

  42. SOA Governance & Maturity Model حوكمة معمارية الخدمات الموجَّهة و نموذج النضج

  43. SOA Governance حوكمة معمارية الخدمات الموجَّهة Specifying the decision rights and accountability framework to encourage desirable behavior in the use of IT.

  44. SOA Maturity Model نموذج النضج

  45. Oracle SOA Suite

  46. Oracle SOA Suite

  47. Oracle SOA Suite Components • JDeveloper • Oracle Service Bus • Oracle Mediator • Oracle Adapters • Metadata Service Repository • Oracle Policy Manager • Oracle Business Rules • Oracle BPEL • Human Workflow • Oracle Business Activity Monitoring – BAM • Oracle Complex Event Processing • Oracle User Messaging Service • Oracle B2B • Oracle Enterprise Manager

  48. JDeveloper • Integrated Development Environment – IDE • Uniform Integrated set of Tools for: • Developers, • Architects, • Business Analysts • Others • Visual Interaction • Declarative Tools • Minimize Coding • Rapid Deployment

  49. Oracle ESB: An ESB Moves Data

  50. Oracle ESB: Facilitates Service Invocation

More Related