Top Banner
By: Nezar Gharbia Director of Information Systems Urban Planning and Development Authority
21

SOA

Nov 03, 2014

Download

Technology

Nezar Gharbia

I gave this presentation at IBM SOA Summit in 2009. It talks about my take on SOA and why I adopted as an application strategy at Urban Planning.
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: SOA

By: Nezar GharbiaDirector of Information SystemsUrban Planning and Development AuthorityQatar

Page 2: SOA

Challenge– Currently oversees and directs the preparation of the Master Plan for the

State of Qatar. The Master Plan for Qatar is a comprehensive long term master plan that will guide the physical development of Qatar through the year 2025

– The country has witnessed big construction development in all fields, and re-planning of many areas in Doha. As a result, and because of the intense construction activities, there is delay in processing of development and building permits.

Working Smarter– The government, therefore, considered it necessary to establish a

complex for issuance of building permits in which all departments and authorities related to issuance of building permits shall be represented.

– Simplification of procedures for obtaining various building permits, in coordination with the concerned services authorities, establishments and departments. Preparation of periodic reports on building permits Applications, and to provide these reports to the concerned authorities.

Page 3: SOA

Service-oriented architecture is a client/server software design approach in which an application consists of software services and software service consumers (also known as clients or service requesters). SOA differs from the more general client/server model in its definitive emphasis on loose coupling between software components, and in its use of separately standing interfaces.

Page 4: SOA

A Service-Oriented Architecture is an enterprise-scale IT architecture for linking resources on demand. These resources are represented as business-aligned services which can participate and be composed in a value-net, enterprise, or line of business to fulfill business needs. The primary structuring element for SOA applications is a service as opposed to subsystems, systems, or components.

Page 5: SOA

An IT architectural paradigm for building Business services that are loosely coupled and can be connected on Demand.

Page 6: SOA

It is an IT Architecture, and a paradigm.It is about loosely coupled services.Integrated on Demand.It is all about Business Services.

Not web services. WS is implementation technology.The business helps you define itIt provides tangible value.

Page 7: SOA

Tech (Bottom Up)Business (Top Down)

Page 8: SOA

It is not just another IT architecture. (like 3 tier, client/server, etc).Always focus on the tangible business value.Make a clear distinction between services & components. Why?

Chatty architecture.Very flat architecture.No tangible Business Value.

Page 9: SOA

Data Layer

Components

Services

Process

Application

Shipping Sales Partners

CustomerData

Email Gateway Right Fax Server Call CenterSMS Gateway Pricing

Web Services W.S W.S W.S

Contact Customer

CRM

Process

Mass Marketing

Partner Application

Page 10: SOA

Enterprise GovernanceEnterprise Governance

Enterprise Strategy

Business

Enterprise Architecture

Business

Operating Environment

Business - Peoples - Partners - Rules & Regulation

Projects

Planning Team Work Leadership Development

IT SOA

Information Technology

Information Technology - Infrastructure - Legacy System - Planning & Development

SOA Governance

Road Map

Top Down SOA Entry

People’s Dimension

Process Dimension

Product Dimension

Partner’s Dimension

Page 11: SOA
Page 12: SOA

So Many Partners & Sister MinistriesSo Many Partners & Sister Ministries

Big Drive for Quality

Many redundancies at the process level

Integration, Integration, Integration Mapped to loosely coupled services

Process centric. IT has to be agile. Lots of changes on the business side. The business needs it’s help to provide

tools, methodology on how to change.

Common Services / Processes. Clear separation between processes

& business services, and low level components.

Business NeedsBusiness Needs IT SolutionsIT Solutions

Monitor & Control KPI support Dashboard Support Multi channels escalation

Over 50 processes to automateAnd improveOver 50 processes to automateAnd improve

Process centric Simulation Built in KPI & dashboard

Transform IT to Service Oriented culture Mind set has to change

Tools has to support it Process has to support it

Page 13: SOA

We needed a way to execute our SOA strategy.Process Centric.Simulation.Built in Performance Measurement tools.Built in reporting and dash boarding.

Page 14: SOA

People’s Dimension– Training– New hires– SOA Center of Excellence.

Processes– Defined a new SOA/BPM process based on IBM SOMA– SOA Governance Board

Technology– Web Sphere Platform (BPM)– Rational Tools (SDLC)

Partners– IBM / GBM

Page 15: SOA

Integration– internally– Externally

Focus on Governance– Focus on IT agility– Aligning IT with Business– Process

Focus on ROIContinual Improvement– Process– People - Training– Partners - Encourage capacity building.

Page 16: SOA

1. WebSphere Business Modeler.

1. Rational Software Architect.2. WebSphere Integration Developer.

1. WebSphere Application Server.2. WebSphere Process Server.3. WebSphere ESB.4. WebSphere portal

1. WebSphere Business Monitor.

None

Page 17: SOA

Building Permit – Going Live this months.

Customer Service Center – Going Live in 2 months.

Planning Implementation – before end of the year.

Page 18: SOA

Need to improve the process.Shorten service time from months to days.Process is not defined.Go electronic / e-service.Monitor and control.Need to integrate with 6-9 external agencies.Needed to integrate with a few other internal processes & systems.

Page 19: SOA

Using BPM platform as a shell for legacy systems.Leverage our existing legacy system

Changed legacy to fire events for every transaction back to our monitoring / dashboard Two way interaction between legacy / BPM platform

Page 20: SOA

It is a paradigm shift. Culture change within Business & IT.Support from upper management is a must.It takes time. It is a journey.Can’t rely on vendors & partners alone.Build your own expertise.Start small.Focus on quick wins high impact projects.You will make mistakes, learn from them.

Page 21: SOA