Building an Operational Enterprise Architecture and Service Oriented

Architecture Best Practices

Presented by: Ajay Budhraja

Copyright 2006 Ajay Budhraja, All rights reserved

Disclaimer: This information represents author’s views only, not any organization’s views

2

Enterprise Architecture

Operational Enterprise ArchitectureThe ability of Enterprise Architecture to impact strategic decision making and support planning, compliance, technology and investments

3

Operational Enterprise Architecture

An Operational Enterprise Architecture is a platform for IT and Business Process Information

Operational Enterprise

Architecture

Operational Enterprise

Architecture

Portfolio Management

Business Processes

Strategy and Planning

Technology

4

Enterprise Architecture for decision support

• Enterprise architecture as a platform for decision support should provide the following levels of support– Strategic– Operational– Technology

5

Operational Enterprise Architecture

• An Operational Enterprise Architecture Program should support the following areas for strategy and planning:– Strategic Planning– Portfolio Analysis– Performance Management– Technology Alignment– Standards Alignment

6

Operational Enterprise Architecture

Enterprise Architecture should also support the following areas at operational level:

• Asset Analysis

• Business flow analysis

• Operational planning

• Transition planning

7

Operational Enterprise Architecture

• An operational Enterprise Architecture needs to document or utilize:– Business architecture and Processes– Information Technology Assets– Query Capabilities– Reporting Capabilities– Mappings to reference models

8

Enterprise Architecture-Technology to Business Evolution

• Investments• Portfolio Management• Standards

• Technology• Compliance• Architecture

9

Realization of an Operational EA

• Realization can be achieved by developing an Enterprise Architecture Repository that stores the following information:– IT Assets– Business Processes– Investments– People

10

Enterprise SOA

Enterprise SOA is a blueprint for an Enterprise wide IT architecture for developing services-

based, interoperable solutions

11

ConsumerConsumer

RegistryRegistry

ServiceService

Discover

Invoke(XML/SOAP)

Register

Service Oriented Architecture

12

Enterprise Services Platform

Enterprise Services Platform

Service Service Service

Service Broker

Security

Services Interface

13

Service Oriented Architecture

Service Oriented Architecture• Leverages highly cohesive, loosely coupled

components• Encapsulates business data• Establishes contracts through interfaces• Provides interfaces to business data

14

Strategy

Service Oriented

Architecture

Planning

Technology

Governance

SOA Key Areas

15

Elements of a service

• A service is a building block with a standard interface that is independent of implementation considerations

• Services are– Self contained– Loosely coupled– Support Reuse– Easily maintainable

16

Service patterns

• Everything is not a Service! • Typical services can be business, workflow, data,

security• Service Categories

– Business Services– Application Services– Infrastructure Services

• Security• Identity management• Persistence

17

SOA Adoption

• Identify existing services and business processes

• Identify existing service interfaces

• Identify information that can be encapsulated as new services

• Build services and support service discovery

18

SOA Adoption

SOA Adoption should focus on:

• SOA Planning, governance, policies, procedures

• Support and deployment of shared services

• Support of interfaces based on standards

• Iterative development

19

Benefits of SOA

• The benefits of SOA are: – Reuse– Cost reduction– Flexibility– Interoperability– Platform independence

20

SOA Best Practices

• Create a roadmap and detailed plans• Incorporate the SOA strategy in transition

planning• Utilize existing standards such as web services• Develop services with the right granularity• Define interfaces and categorize services• Define mechanisms for discovering services

21

Document Current StateDocument Current State

Service Oriented Architecture Process

Develop Future StateDevelop Future State

Develop Strategy and PlanDevelop Strategy and Plan

Document Transition PlanDocument Transition Plan

Roadmap, Technology, Gap Analysis

IT Assets, Business Flows

Project plan, resources, priorities

Plan to move from Current to Future State

22

SOA Service Design Best Practices

• SOA service design considerations are:– Granularity of services– Appropriate coupling– Local or Remote– Incremental development

23

SOA Operational Best Practices

• Identify the existing Business Domain Model - Data, Systems, Functions

• Define the technology standards and use them across the organization – SOAP, XML, WSDL

• Define and identify services and relate to business processes based on data, latency

• Create a Registry in the organization - UDDI

• Security – WS Security, SAML etc

• Process and Governance – Interface management, Points of contact, SOA adoption across the enterprise

24

Abstract

The development of an operational Enterprise Architecture program enables effective decision making and improved efficiency in an organization. Key decisions about technology investments, compliance and technologies can be driven through Enterprise Architecture. An operational Enterprise Architecture platform gives a high level enterprise view of assets and business processes, that can serve as a blueprint for documenting and modernizing operations and systems. Service oriented architecture (SOA) is bridging the gap between business strategists and IT architects and can result in business agility, efficient integration and reuse. SOA promotes the encapsulation and deployment of services that support an operational Enterprise Architecture program. Such distributed services can provide a high degree of flexibility for responding to changes and to support business processes. This presentation will discuss SOA best practices, methodologies and challenges. An effective operational Enterprise Architecture that incorporates SOA best practices can promote significant cost savings and can support strategic decision-making in an organization.

Bio

Ajay Budhraja has over 17 years in Information Technology with experience in areas such as management, project management, enterprise architecture, system architecture, software engineering, training, methodologies, networks, databases etc. He has a Masters in Engineering (Computer Science) and also a Masters in Management. He is a Project Management Professional certified by the PMI and is also CICM certified. Ajay has led large scale projects for big organizations and has extensive IT experience related to telecom, business, manufacturing, airlines, finance, government. He has delivered web based technology solutions and strategies for e-business platforms, portals, mobile e-business and content management. As Adjunct Faculty, he has taught courses for several universities and has presented papers at worldwide conferences.

Thank you. Contact Information: Ajay Budhraja

Email: ajbudregister@yahoo.com

Building an Operational Enterprise Architecture and Service OrientedArchitecture Best Practices