Service Oriented Architecture

1

What is Architecture

Formal DefinitionFormal Definition• IEEE 1471-2000IEEE 1471 2000

– Software architecture is the fundamental organizationof a system, embodied in its components, their y , p ,relationships to each other and the environment, and the principles governing its design and evolution

IEEE 1471IEEE 1471--20002000

Why Architecture?

• Architecture serves as the blueprint for the system but l th j talso the project:– Team structure– Documentation organizationDocumentation organization– Work breakdown structure– Scheduling, planning, budgetingg, p g, g g– Unit testing, integration

• Architecture establishes the communication and coordination mechanisms among components

Directions of System Architecture

1960 - 1980 1990 - 2000 2010 - 2050

•Organization Focus•Mainframe Centric•Internal Use•Unique Data

•Process Focus•Client Server•Partial Connectivity•EDI File Transfer

•Distributed Functions•Data Centric•Universal Interoperability•Real-time Connectivity

4

Unique Data EDI File Transfer Real time Connectivity

What is a Service Oriented Architecture (SOA)?

• A method of design, deployment, and management of b th li ti d th ft i f t tboth applications and the software infrastructure where: – All software is organized into business services thatAll software is organized into business services that

are network accessible and executable. – Service interfaces are based on public standards for

i biliinteroperability.

5

Key Characteristics of SOA

• Quality of service, security and performance are ifi dspecified.

• Software infrastructure is responsible for managing. • Services are cataloged and discoverable• Services are cataloged and discoverable. • Data are cataloged and discoverable. • Protocols use only industry standards. y y

6

SOA –Based Cloud Infrastructure Steps

• Analysis and Strategy• Planning• Implementation

V l d i• Value -driven

7

What is a “Service”?

• A Service is a reusable component.• A Service changes business data from one state to

another.• A Service is the only way how data is accessed• A Service is the only way how data is accessed.

8

Information Technology is Not SOA

Business Mission

Information Management

Information Systems

Systems DesignSOA

Systems Design

Computing & CommunicationsInformation Technology

9

SOA Must Reflect Conflicting Interests

Personal

Local

Personal

Organizations

Missions

Enterprise

10

11

12

13

Organization of Infrastructure Services

InfrastructureInfrastructureServices

(Enterprise Information)

DataServices

SecurityServices

ComputingServices

CommunicationServices

ApplicationServices

14

Organization of Data Services

D tDataServices

Discovery Management Collaboration Interoperability SemanticDiscoveryServices

ManagementServices

CollaborationServices

InteroperabilityServices

SemanticServices

15

Data Interoperability Policies

• Data are an enterprise resource.• Single-point entry of unique dataSingle point entry of unique data.• Enterprise certification of all data definitions.• Data stewardship defines data custodians. • Zero defects at point of entry.• De-conflict data at source, not at higher levels.• Data aggregations from sources data not from• Data aggregations from sources data, not from

reports.

16

Organization of Security Services

S itSecurityServices

Transfer Protection Certification Systems AuthenticationTransferServices

ProtectionServices

CertificationServices

SystemsAssurance

AuthenticationServices

17

Organization of Computing Services

C tiComputingServices

Computing Resource Control & Configuration FinancialComputingFacilities

ResourcePlanning

Control &Quality

ConfigurationServices

FinancialManagement

18

Computing Services

• Provide Adaptable Hosting EnvironmentsGlobal facilities for hosting to the “edge”– Global facilities for hosting to the edge .

– Virtual environments for data centers. • Distributed Computing InfrastructureDistributed Computing Infrastructure

– Data storage, and shared spaces for information sharing.

• Shared Computing Infrastructure Resources– Access shared resources regardless of access

devicedevice.

19

Organization of Communication Services

C i iCommunicationServices

Interoperability Spectrum Connectivity Continuity of ResourceInteroperability Services

SpectrumManagement

ConnectivityArrangements

Continuity ofServices

Resource Management

20

Network Services Implementation

• From point-to-point communications (push i ti ) t t k t i ( llcommunications) to network-centric processes (pull

communications).• Data posted to shared space for retrieval.Data posted to shared space for retrieval.• Network controls assure data synchronization and

access security.

21

Communication Services

• Provide Information Transport– Transport information, data and services

anywhere.Ensures transport between end user devices and– Ensures transport between end-user devices and servers.

– Expand the infrastructure for on-demand capacity.

22

Organization of Application Services

A li iApplication Services

Component Code Binding Maintenance ExperimentalComponent Repository

Code BindingServices

MaintenanceManagement Portals Experimental

Services

23

Application Services and Tools

• Provide Common End User Interface Tools– Application generators, test suites, error

identification, application components and standard utilities.standard utilities.

• Common end-user Interface Tools.– E-mail, collaboration tools, information

dashboards, Intranet portals, etc.

24

A Few Key SOA Protocols

• Universal Description, Discovery, and Integration, UDDI. Defines the publication and discovery of web service implementations.

• The Web Services Description Language, WSDL, is an XML-based language that defines Web Services.

• SOAP is the Service Oriented Architecture Protocol. It is a key SOA in which a network node (the client) sends a request to another node (the server).

• The Lightweight Directory Access Protocol, or LDAP is protocol for querying and modifying directory services.

• Extract, Transform, and Load, ETL, is a process of moving data , , , , p gfrom a legacy system and loading it into a SOA application.

25

Why SOA Saves Code

• Provides a standard way of interacting with shared ftsoftware.

• Enables software to become building blocks for reuse.• Shifts focus to application assembly rather than design• Shifts focus to application assembly rather than design.• Creates new applications out of existing components.• Integrates with applications in other enterprises.g pp p

26

Preservation of Assets is the Purpose of SOAp

What the Customer Trains to Apply;

Open Systems,Equipment

Data &Systems Integration;

Trains to Apply;Applications

Usage

Equipment,Software,

Communications

CommunicationsInfrastructureArchitecture

Short-termA t

ObsolescentC dit A t

Long - termA tAsset

(An Enterprise Function)>70% of Cost

Commodity Asset(Outsource According to

Architecture)<20% of Cost

Asset(An Enterprise Function)

<10% of Cost

27