Leveraging MDA for meet-in-the-middle SOA

Copyright © 2007 Model Driven Solutions, Inc.

The Architecture of ServicesWorkshop on eGovernment and the Web

Cory Casanave

cory-c (at) ModelDriven.com

Full Paper

http://modeldriven.com/whitepapers.shtml

Formerly Data Access Technologies

http://www.w3.org/

Page 2Copyright © 2007 Model Driven Solutions18/06/07

Our perspective on Service OrientedArchitecture (SOA)

• SOA is:– An enterprise and business architecture approach – a way tounderstand and integrate the enterprise in the context of itscommunity and as a network of business services. “A SOA” at thebusiness level is part of the enterprise architecture showing howthis network of services delivers business value

– A system of systems solution architecture – a way tounderstand and integrate enterprise systems internally andexternally as a network of technology services. “A SOA” at thesystems of systems level is the solutions architecture showing howthis network of systems works together to delivers business value.

– A system integration approach – a way to expose existingcapabilities to integrate applications and create new compositesolutions.


SOA Hype and Reality

• This is easy – no planning required– Hype: “Just start exposing capabilities as services – use these tomake new services and “mash up” applications”

– Reality: Service anarchy is a road to disaster – architect forlongevity and loose coupling

• Network of Services– Hype: Services are simple and stand-alone– Reality: Services can be complex and interdependent

• Suitability, process and trust– Hype: Dynamically find and use services from across the internet– Reality: Mission critical use of services requires trusted and reliableservices from known parties


Spaghetti Enterprise Example

Uses one

Of the

Services

Offers a

New service

Offers a

Service

Builds an

Application

Using other

services

http://images.google.com/imgres?imgurl=http://www.bcfas.org/theater/images/LARGE%2520THEATER%2520SEATING%2520CHART.jpg&imgrefurl=http://www.bcfas.org/theater/LT_seating_chart.html&h=800&w=1125&sz=197&hl=en&start=4&tbnid=7Z4CmnyFnAUMhM:&tbnh=107&tbnw=150&prev=/images%3Fq%3Dtheater%2Bseating%26gbv%3D2%26svnum%3D10%26hl%3Den%26sa%3DG


Services Use Services



Anti-Agile Service Dependencies

Changed or

Discontinued

Core problem – services “bottom up” – not architected or standard



SOA Simplification

•Services are limited to a singleinteraction between provider andconsumer

•There is just a “request message”and a result

ProviderConsumer Service


Reality – Multiple services work together

AssetManagement

AssetAccounting

GeneralLedger

ReceivablesAccounting

Asset Data

Asset Transfer

Asset Disposal GL Updates

AssetRecord

Asset DisposalRevenue

Asset Service Collaboration

The Asset service collaboration shows the service interactions supporting the management ofasset records and the posting of general ledger as a result of asset transactions.


Bn-FSE

Bde - FSE Bde- Artillery

FABn - FSE

Co-FIST MLRS Battery

MLRSForward Observer

Services can be complex and long lived interactions

Fire Ready

End Of Mission

Call For Fire

Fire Shot

Fire Splash

Mission Fire Rpt

Rounds Complete

Call for fire is a “protocol”of action and informationexchange between parties


Trust and Validation

Clear, Trusted and Validated Service Effects

Under All Conditions

Service Contract

http://images.google.com/imgres?imgurl=http://64.41.64.113/home/rockets/launch.jpg&imgrefurl=http://64.41.64.113/home/tips.html&h=480&w=640&sz=62&hl=en&start=11&um=1&tbnid=g6bYaHoavm6cuM:&tbnh=103&tbnw=137&prev=/images%3Fq%3Dlaunch%2Bbutton%26svnum%3D10%26um%3D1%26hl%3Den%26sa%3DG


Message – Don’t forget the “A” in SOA!

• A Service Oriented Architecture Should:– Treat the enterprise as “service oriented” at the business level -people and organizations provide and use services

– Define technology services to augment and enable businessservices

– Define “service contracts” so all parties know what to expect– Abstract “enterprise services” from solution specific capabilities– Provide for reuse and longevity– Define how services collaborate to provide business value– Separate service contracts from implementing technologies– Provide an integrated view of processes, collaborations, informationand services – without coupling these together


Business Concerns

Goals

Mission

Policy

Customers

Collaborators

Costs

AgilityTechnology SpecificationWeb Services

WSDL, BPEL, XML Schema

Logical Systems of Systems ModelTechnology Services (t-SOA),

ComponentsInterfaces, Messages & Data

Business Focus Using Model Driven ServicesArchitecture

SOA Business ModelBusiness Services (b-SOA)

Roles, Collaborations & InteractionsProcess & Information

Refinem

ent&Autom

ation

Line-Of-Sight

Computation

Independent

Model

Platform

Independent

Model

Platform

Specific

Model

MDATerms


Core of services architecture• Services contract

– What is the service provided?– Under what terms and guarantees?– What are the interactions – information and assets exchanged?– What is the data?– How is the services choreographed?

• Service Collaboration– Why do parties work together – what is the business goal?– What roles do they play in this collaboration?– What services does each party provide and use?

• Process– Externally, what process or processes does the collaboration serve?– Internally, what activities take place to enact a service?– What resources are consumed or produced?

• Information– What is the core information (ontology) of the domain– What information is exchanged to enact services– What information is retained and shared


Model DrivenModel DrivenArchitectureArchitectureStandardsStandards

Automate from Architecture model totechnology

Framework &Framework &InfrastructureInfrastructure(E.G. -J2EE-WS)(E.G. -J2EE-WS)

PSMPSM

InfrastructureInfrastructureMappingMapping

(E.G. J2EE-WS)(E.G. J2EE-WS)

Mapping is tunedMapping is tunedto the infrastructureto the infrastructure

ToolsToolsProduce &Produce &IntegrateIntegrate

EnterpriseEnterpriseServiceService

ComponentsComponents

EnterpriseEnterpriseArchitectureArchitectureModel (CIM)Model (CIM)

Minimize and structuremanual implementation

C

TechnicalArchitecture


Model Driven Solutions

• Business Enablement– Business Transformation– Enterprise Agility– Enterprise Integration– Service Implementation

• Architecture– Enterprise Architecture– Business Architecture– Service Oriented Architecture– Model Driven Architecture– Business Process Architecture

• Open Source– www,ModelDriven.org – Open community for MDA, SOA and theSemantic web

• Opportunity to solution – architected, fast, strategic

www.ModelDriven.com


Backup Example


Bn-FSE


FABn - FSE



Example Call for Fire - MLRS

Fire Ready

End Of Mission

Call For Fire

Fire Shot

Fire Splash

Mission Fire Rpt

Rounds Complete

Call for fire is a “protocol”of action and informationexchange between parties


Bn-FSE


FABn - FSE



Call for Fire - MLRS


Model Of CFF Thread


Model Information Flows

Fire Ready

End Of Mission

Call For Fire

Fire Shot

Fire Splash

Mission Fire Rpt

Rounds Complete

* Not technology details!


Choreography – Understanding When


Generated Web Services Definition

<wsdl:portType name="CustomerOrderEstablishment.CustomerOrderEstablishment"><wsdl:operation name="CustomerOrderEstablishment"><wsdl:input message="tns:CustomerOrderEstablishmentPanopticInheritanceCluster“

name="CustomerOrderEstablishment"></wsdl:input>

</wsdl:operation></wsdl:portType>

<wsdl:portType name="CustomerOrderEstablishment.CustomerOrderEstablishmentCallback"><wsdl:operation name="CustomerOrderEstablished"><wsdl:input message="tns:CustomerOrderEstablishedPanopticInheritanceCluster“

name="CustomerOrderEstablished"></wsdl:input>

</wsdl:operation><wsdl:operation name="CustomerOrderEstablishmentRejected"><wsdl:input message="tns:CustomerOrderEstablishmentRejectedInheritance“

name="CustomerOrderEstablishmentRejected"></wsdl:input>

</wsdl:operation></wsdl:portType>

The primary port type has operations correspondingto the request flows in the protocol.

The callback port type has operations correspondingto the response flows in the protocol.


Example Transaction Message XML Document<CustomerOrderEstablishment>

<customerOrderEstablishment><newOrder>

<customerOrder><customerOrderID> … </customerOrderID><customerOrderAmount> … </customerOrderAmount><orderingCustomer>

<customer><customerID> … </customerID>

</customer><party>

<name> … </name></party>

</orderingCustomer><controllingSalesInstrument>

<salesInstrumentID> … </salesInstrumentID></controllingSalesInstrument>…<lineItems>

…</lineItems>

</customerOrder></newOrder>

</customerOrderEstablishment><businessDomainTransaction>

<transactionID> … </transactionID></businessDomainTransaction>

</CustomerOrderEstablishment>

Leveraging MDA for meet-in-the-middle SOA

Technology

services use services

network of business

informationand services

model driven solutions

abstract enterprise

howthis network of services

network of technology

reality multiple services