1. introduction service-oriented architecture · pdf filebusiness architecture means ... bok...

1 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciences, WS 09/10. 14.10.2009

Service-Oriented Architecture

1. Introduction

Winter Semester 2009/10

Prof. Dr. Bernhard Humm

Darmstadt University of Applied Sciences

Department of Computer Science

Organisation

SOA: myths and reality

Cities and application landscapes

An example project

Literature

� Organisation

Agenda


Organization of the course

� Lectures:

– Weekly Wednesday 14:15 in D19/07 (Alternative, to be discussed, Mo., 10:15 or 12:00)

– Download of slides from my homepage www.fbi.h-da.de/~b.humm

� Labs:

– Fortnightly on Monday, 14:15 – 17:30 in D19/07 (x and y groups)

– You will use your own notebooks via WLAN

– Download of assignments from my home page

– Assignments may be performed in pairs (teams of 2 students)

– It is necessary to finish assignments at home

– Installation manual for technical infrastructure can be downloaded from my home page

– Tutoring during lab sessions by Bernhard Humm

� Examination

– Oral examination at the end of the semester


Overview of the entire course

1. Introduction

2. Business architecture

3. Designing domains

4. Designing components

5. Designing interfaces and operations

6. Excursus: business information systems

7. Loose coupling

8. Web Services

9. Service orchestration - BPEL

10. Integration Platforms

11.Evolution of application landscapes

Organisation



An example project

Literature

� SOA: myths and reality

Agenda


Source: IBM white paper: “Smart SOA: Best practices for agile innovation and optimization”

What tools vendors say…


Source: Software AG white paper“Business InfrastructureSoftware“

8 Prof. Dr. Bernhard Humm, Darmstadt University of Applied Sciences, WS 09/10. 14.10.2009Source: SAP „Enterprise Service-Oriented Architecture made Easy“


HP

Source: HP white paper „Service Oriented Architecture“


Myths and reality

� SOA is a technology (standards and products)

� "If you’re using Web services (such as SOAP over HTTP),

you’ve achieved SOA”

� SOA is paradigm for structuringthe business of an enterprise

which then drives the IT application landscape

� SOA is easy� "You can buy SOA out of the

box"

� Structuring applicationlandscapes towards a true SOA takes a long time, needs high

expertise and is expensive

� Technology drives business� “Business automatically

responds to market forces, onceSOA technology is implemented“

� Business must drivetechnology

� Technology can only supportbusiness

� Architecture meanstechnical infrastructure

� “Enterprise Service bus is thecore of an SOA“

� The structure of applications isthe primary focus of SOA

� Technical infrastructure issecondary

Myth Example Reality

Organisation



An example project

Literature

� Cities and application landscapes

Agenda


Megacity


Software-Megacity?Software-Megacity = (large) application landscape

= individual application


Application landscape of a bank City map of Rome / Italy

The metaphor holds since …

�Like city planning, the design and management of an application landscape via service-oriented

architecture is a discipline on ist own

– Planning and building houses is different from developing cities

�Application landscapes are (nearly) never built greenfield

– Like cities, application landscapes evolve continuously

– It is the task of the enterprise architect to manage this evolution

�Like in city planning, the enterprise architect uses different models („plans“)


Topics Planning tools

City planning tools

Land utilization planSuburbs, Industrial areas, …

Zoning MapTypes of houses, …

Infrastructure mapStreets, railroads, electricity, gas, …

str

ate

gic

opera

tive


Land utilization plans and domain models

Land utilization plan (City of Berlin)

Von Städten und Unternehmen

Domain model(tour operator)


Zoning maps and component architectures

Zoning map(Pariser Platz)


Kerngeschäft

Component architecture(tour operator)


Infrastructure maps and integration architectures

Infrastructure map


Portal Server

<<IP>>P

Reiseportal-

Präsentation

(REPO-P)

<<AL>>

Reiseportal-

Katalogdatenmanagement

(REPO-K, auf Basis CMS)

<<AL>>P

ESB

Portlet

<<IP>>P

UTM

Adapter

L (ESB)<<IP>>

asynchrones Messaging

Exactly once

Vakanzprüfungs- und

Buchungssystem (VBS)

<<AL>>L (UTM)

Kundenmanagement

(KUMA)

L (ESB)<<AL>>

Virtuelles Lager

(VILA)

L (ESB)<<AL>>

Individualreise-

konfigurator (IRKO)

L (ESB)<<AL>>

synchroner RPC

best effort

BPEL-Engine

<<IP>>

Individualbuchungs-

prozess (IBPR)

<<AL>>

L (ESB)

ESB

Portlet

<<IP>>P

O

T T

T

O

Integration architecture

Organisation



An example project

Literature

� An example project

Agenda


The (fictious) company: Christopher Columbus Travel Pty Ltd.

� Products:

– Package holidays, i.e. transport + accommodation

– Short-distance (Germany), medium-distance (e.g., Mallorca), long-distance (e.g., south east Asia)

� Customers:

– Private customers

– From low-budget to premium

– In various European countries

– Diverse brands, focused on customer segments

� Company:

– Multi-national tour operator

– Several thousand travel agencies

– Large IT department


Strategic business decision in order to differentiate from competitors and to develop new markets

In addition to the classicpackage holiday,

new custom holidays shallbe offered


The strategic decision has multiple implications

In addition to the

classic package

holiday,

new custom

holidays shall be

offered

�New business partners

�Marketing for new product

�Adapted sales channels (Internet)

�Modified operations

�…

Strategic decision

Business implications

�New back-end applications

�New Internet portals

�Integration of new applications in

legacy applications

�…

IT implications


The existing enterprise IT architecture is complex and has grown over 20 years


The strategic decision has implications on many parts of the enterprise IT architecture


Step 1: Identify core business services (business architecture)

Planning ServiceSalesProduction

�Evaluate last travel season�Plan passengerquota

�Design offers�Calculate prices�Produce catalogs

�Sell travels�Manage stock (accomodations & transports)

�Producecustomerdocuments�Invoice�Informaccomodation & transport partners�Serve customerduring travel�Pay partners

Purchasing

�Buy resources(accomodation & transports)


� The domain model forms the background layer of the enterprise IT architecture diagram.

� Structuring the enterprise IT architecture according to the planned domain model allows you to

identify necessary changes.

Step 2: Design domains


Step 3: Design components

ANM

VKI

PGP VKP

RAM

<<AL>>

Auftrags-

management

AUMA

<<AL>>

Pauschal-

Preisberechnung

PPRB

<<AL>>

Individualbu-

chungssteuerung

IBST

<<AL>>

Pauschalbu-

chungssteuerung

PBST

Zu migr.

CTT

Kerngeschäft

PUR

CUM

BOK

RSM

PPT

PCT SRV

ACC REP

TRA INT CCE

PLA

ORM

<<AL>>

Order

Mgmt.

<<AL>>

Cust.

Mgmt.<<AL>>

Hotel

Stock

<<AL>>

Prizing

<<AL>>

Booking

Custom

<<AL>>

xxxx

xxxx

xxxx

Travel

Portal

<<AL>>

Travel

Config.

<<AL>>

Accoun-

ting

<<AL>>

Booking

Package

<<AL>>

Repor-

ting

<<AL>>

Flight

Stock

<<AL>>

Supplier

Mgmt

<<AL>>

Flight

Purch.

<<AL>>

Hotel

Purch.

<<AL>>

Payment

...

<<AL>>

Virtual

Stock

<<AL>>

Planning

<<AL>>

xxxx

xxxx

xxxx

Call

Center

<<AL>>

xxxx

xxxx

xxxx

Travel

Agency

PER <<AL>>

Perso-

nell

<<AL>>

Package

Config.


Step 4: Implement

� Buy and implement commercial off the shelf (COTS) packages

� Design & implement custom components

� Provide interfaces for

existing components

� Integrate

� Test

� Put into

Operation

Organisation



An example project

Literature� Literature

Agenda


Literature

� Gregor Engels, Andreas Hess, Bernhard Humm, Oliver Juwig, Marc Lohmann, Jan-Peter Richter, Markus Voß, Johannes Willkomm: Quasar Enterprise –Anwendungslandschaften serviceorientiert gestalten. dpunkt-Verlag 2008.

� Bernhard Humm: Was ist eigentlich ein Service? GI-Workshop Software Architektur 2008. Softwaretechnik-Trends Band 28, Heft 4, S. 8-11. Gesellschaft für Informatik, Nov. 2008.

� Gregor Engels, Andreas Hess, Bernhard Humm, Oliver Juwig, Marc Lohmann, Jan-Peter Richter, Markus Voß, Johannes Willkomm: A Method forEngineering a true Service-Oriented Architecture. To appear: Proceedings of the 10th International Conference on Enterprise Information Systems. Barcelona, Spain, 2008.

� Andreas Hess, Bernhard Humm, Markus Voß, Gregor Engels: StructuringSoftware Cities - A Multidimensional Approach. Proceedings of the 11th IEEE International EDOC Enterprise Computing Conference, Annapolis, Maryland, USA, pp. 122-129. IEEE Press, 2007.

� A. Hess, B. Humm, M. Voß: Regeln für serviceorientierte Architekturen hoher Qualität. Informatik Spektrum 6/06. Springer Verlag 2006.

Exkursion

Capgemini sd&m

1. introduction service-oriented architecture · pdf filebusiness architecture means ... bok...

Documents