OMG SOA SIG Activity Debrief

Model-Driven SOA OMG SOA SIG Activity Debrief

June 28th 2007

Dr. Harsh W. Sharma, Co-Chair, OMG SOA SIGJames Odell, Co-Chair, OMG SOA SIG

Pete Rivett, Chair-Emeritus, OMG SOA SIG

2

Agenda

SOA Challenge OMG SOA SIG: Mission &

Participants OMG’s approach to SOA & Value

Proposition Summary of gap analysis effort Summary of Standards in

development SOA Standards Harmonization

activity SIG Next Steps

3

SOA Challenge

Inadequate emphasis on Business & Architectural aspects of SOA Poor (if any) traceability of Services to business processes & functions, compliance..

Many standards organizations are developing standards with possible overlaps and rapid churn

Vendors are repositioning their products as SOA enabled, end-to-end solution and takeovers leaving the Consumer with the burden to identify the best of breed solution

..We know this already…so what is OMG doing?

http://www.innoq.com/soa/ws-standards/poster/

4

SOA SIG Mission & Participants

Mission Support a Model Driven

Architecture (MDA) approach to SOA that links architectural, business and technology views of Services, including Business Process Management (BPM) and Event-Driven Architecture (EDA)

Identify and foster development of OMG modeling standards for SOA that integrate with and complement standards developed by other organizations such as W3C, Open Group and OASIS…

Participants IBM, HP, SAP, BEA, Unisys, EDS, RTI, Model Driven Systems, Adaptive, MEGA, MetLife, VISA,

Bank of America, CitiGroup, Boeing, Raytheon, Rhysome, AptSoft, XAware, SOA COP, SOA Consortium, The Open Group, OASIS, Satyam, US EPA, ebizQ, Georgetown University, NIST, Liberty-Mutual, Penn National, Prima-Solutions, OSOA, Nortel, Indiana University…

Oth

er…

Oth

er…

Rel

atio

nal

Rel

atio

nal

.NE

T.N

ET

J2E

EJ2

EE

EDABPM

EA/Business Models

MDA

SOA

Implementation StacksImplementation Stacks

5

Model Driven Architecture: “The DNA of SOA”

Unified Modeling Language Addresses system modeling

Common Warehouse Metamodel/Information Management Metamodel (IMM) Addresses information modeling &

metadata exchange Traceability of information

(source to targets) Meta Object Facility

Addresses the definition of modeling languages (metamodels)

Integration, interchange and management of models

Core MDA Standards are ISO StandardsCore MDA Standards are ISO Standards

MOF/XMIFacilities for defining, interchanging, transformation

and managingAll models and metamodels

Bu

sin

ess

Mo

del

ing

(mo

tiva

tio

n,

Inte

nt.

.)

Pro

cess

Mo

del

ing

Ap

pli

cati

on

, S

ervi

ce,

Eve

nt

Mo

de

lin

g

Other..In

form

atio

n M

od

elin

g

Sec

uri

ty,

Pe

rfo

rman

ce,

Tes

tin

g,

Co

mp

lian

ce

M

od

elin

g

6

OMG’s Approach & Value Proposition

While other organizations have focused on specific standards for integration or web services protocols (e.g., WS-* standards), OMG complements their efforts by taking a Platform Independent View and applying a Modeling Approach to SOA

Modeling offers the capability to design a complete SOA solution

Intellectual property documented through models can have a longer lifespan, allowing an organization a choice of the best technical platform for SOA implementation

Modeling is OMG’s Core CompetenceModeling is OMG’s Core Competence

7

SOA Related Business Modeling Standards

Business Motivation Model (BMM) Mission, goals and objectives for an organization linked to external factors

Semantics for Business Vocabulary and Rules (SBVR) Combines natural language expression with precise logical underpinning

Business Process Modeling Notation (BPMN) Existing standard from BPMI.org (merged into OMG)

Business Process Definition Metamodel (BPDM) Notation and platform independent process modeling and interchange

Production Rules Representation (PRR)* Platform independent model for executable rules

Business Process Runtime Interface (BPRI)* Platform independent interfaces to running processes

Organization Structure Metamodel (OSM)* Organizations, relationships, positions and roles

*in development

8

SOA Related Technology Modeling Standards UML

Architecture and design of services/internals General purpose modeling language (via UML Profiles)

Reusable Asset Specification (RAS) Packaging of reusable assets for retrieval, usage and deployment

CWM and forthcoming Information Management Metamodel (IMM) Service Payloads (information content) and mapping to enterprise

data sources Ontology Definition Metamodel (ODM)

Modeling Ontology of ‘Services’ and Events’ Facilitate development of Semantic Web Services

Knowledge Discovery Metamodel (KDM) Models of the enterprise systems to which services typically map

Software Process Engineering Metamodel (SPEM) Modeling the SOA development process (Service Life cycle)

9

SOA and Information Modeling: IMM Overview

Meta Object Facility (MOF2)IMM FoundationIMM Foundation

CWM PackagesMultidimensional, Data Mining, OLAP,

ETL Transformations, Warehouse Process, Operations…

(Carry- Forward, with minor changes)

CWM PackagesMultidimensional, Data Mining, OLAP,

ETL Transformations, Warehouse Process, Operations…

(Carry- Forward, with minor changes)

ER Modeling(Logical)

ER Modeling(Logical)

Relational Modeling(Physical)

Relational Modeling(Physical)

XML Modeling

XML Modeling

Information Management Metamodel (IMM)Information Management Metamodel (IMM)

Extended ScopeExtended Scope

ER Modeling

Relational Modeling

XMLModeling

RecordStructureModeling

Object OrientedDatabaseModeling

ExpressDatabaseModeling

UML2 Profiles

Mandatory Components (Metamodels)

Record StructuresModeling

Record StructuresModeling

Object OrientedDatabaseModeling

Object OrientedDatabaseModeling

LDAPModeling

LDAPModeling

RelationalModeling Notation for IE,

Support for Methods…

RelationalModeling Notation for IE,

Support for Methods…

ExpressDatabaseModeling

ExpressDatabaseModeling

Optional Components (Metamodels)

XSDXSD SQL DDLSQL DDL CobolData Division

CobolData Division Other..Other..

LDAPModelingLDAP

Modeling

MO

F Q

VT

: Metam

od

el <>

UM

L P

rofile

MO

F Q

VT

: Metam

od

el <>

UM

L P

rofile

10

OMG Standards apply to all layers of SOA

Interfaces defined by enterprise context

Data Data DataData

ServersMainframes MainframesServers

BPMN

UML

BPDM

SBVR

ODM UML

RAS

J2EE UML Profile

CORBA UML Profile

CWM/IMM

KDM

BusinessProcess

BusinessServices

Task definition

Task implementation

Components

OperationalResources

Interfaces defined by enterprise semantics and requirements

http://www.omg.org/attachments/pdf/OMG-and-the-SOA.pdf

11

Summary of Gap Analysis Effort

Modeling approach to SOA*

Service Traceability to Business Processes*

Service Relationship to Events*

Need to Harmonize development of SOA Standards*

Service Discovery & Assets SOA Life Cycle Metrics and Maturity SOA Governance & Compliance

* Gaps OMG SOA SIG started working on

12

Standards in Development

UML Profile and Metamodel for Software Services (UPMS) RFP MOF metamodel and equivalent UML2 profile Extend, but not conflict with UML semantics Notation icons for services extensionshttp://www.omg.org/cgi-bin/doc?soa/06-09-09

Event Driven Architecture (EDA) and its relationship with SOA, BPM – RFP (to be issued in Dec. 07) Addresses Event vocabulary, relationship between

EDA, BPM and SOA Event Metamodel and UML Profile Event metadata exchange using standard formats like XMI Event Traceability and causality in relation to Services Processing of complex events

13

UPMS Goals (submission in progress)

A common vocabulary and metamodel to unify the diverse service definitions that exist in the industry

Complement existing UML metamodel by defining an extension to UML to ensure complete and consistent service specifications and implementations

Integrate with and complement standards developed by other organizations such as W3C and OASIS

Support a service contract describing the collaboration between participating service consumers and service providers

Enable traceability between contracts specifying services requirements, service specifications that fulfill those requirements and service providers that realize service specifications

The ability to exchange services models between tools using XMI

14

Who is working on UPMS?

IBM Adaptive Cap Gemini EDS HP Model Driven Solutions Telelogic BAE Systems Azora everware-cbdi France Telecom R&D The Thales Group European Software

Institute, Softteam, Rhysome and MIDt

SINTEF University of Augsburg, NKUA – University of Athens German Research Center for

Artificial Intelligence (DFKI) Oslo Software DERI (University of Innsbruck) Fujitsu Mega International

15

Agenda

SOA ChallengeSOA Challenge OMG SOA SIG: Mission & OMG SOA SIG: Mission &

ParticipantsParticipants OMG’s approach to SOA & Value OMG’s approach to SOA & Value

PropositionProposition Summary of gap analysis effortSummary of gap analysis effort Summary of Standards in Summary of Standards in

developmentdevelopment SOA Standards Harmonization

activity Next steps

16

SOA Standards Harmonization Activity: Drivers

Many standards organizations are developing standards with possible overlaps and rapid churn

“Just the mere number of standards and specifications that one has to consider when attempting SOA is mind numbing”..

Which ones are specifications (not yet standards) submitted to standard bodies?

Which ones are specifications ratified by the standard bodies as industry standards?

Which ones (standards or specifications) overlap (some do) and which to choose / use in such cases?

And worst of all, there is not a single place to go to for these standards!

http://blogs.sun.com/roller/page/alur?entry=soa_standards_overload_or_real

“Given the proliferation of SOA standards, there is an opportunity to take a step back and provide some perspective on all the SOA standards that exist…”

http://searchwebservices.techtarget.com/tip/0,289483,sid26_gci1244481,00.html?track=NL-110&ad=581964&asrc=EM_NLN_1076649&uid=783626

17

SOA Standards Harmonization Activity: Mission

Enable various standards organizations to reconcile their SOA efforts and offer clarity to the end-users lost in the maze of SOA standards

Prioritize and foster development of standards applicable to Business and Technology Dimensions of SOA

Enable standards organizations to become trusted advisors to the SOA community

18

How do we Harmonize?

Develop and maintain an authoritative source of SOA and related standards (SOA Standards Knowledgebase) Sponsored by OMG SOA SIG, being developed collaboratively with

other standards organizations Map SOA standards (proposed, in development or adopted) to ‘SOA

Perspectives’ Business Perspective: Motivation (mapping Services to Business

Functions), legal/compliance, Cost, discovery*, maturity*… Architectural Perspective: Reference Models, Design-patterns… IT Perspective

Information Perspective (Service Payload): Data Distribution, Domain Standards…

Developer Perspective: Orchestration, Security, Protocols… Publish a roadmap of who is developing which category of SOA standards

*can apply to more than one Perspective

For each Standard: Name, description, current release/version (as applicable) Life-cycle status (proposed, RFI, RFP, initial submission, adopted…)

Timeline Responsible Organization

Link to the organization and its SOA standards roadmap, noteworthy news (RSS feeds to keep the information current)

19

20

21

Harmonization Activity: other examples

Use of OASIS’ SOA reference model and vocabulary in OMG’s SOA standards development as applicable

Discussions started with Everware-CBDI to harmonize their SOA metamodels with the OMG’s UPMS (additional joint RFP planned)

OMG working with Events Processing Technical Society (EPTS) on the development of modeling standards for EDA/CEP The goal of EPTS is to promote the understanding of the

“event processing” area, its potential impact and serve as a catalyst to the growth and understanding of the area by the general technical and business community

Collaborating with The Events Processing Reference Architecture Working Group on CEP/EDA patterns and extensions to OMG standards relevant to events processing

22

SIG next steps

UPMS adoption- March 2008 EDA RFP- to be issued in Dec. 2007, initial

submission March 2008 SOA Standards Knowledgebase – in

development, beta rollout Sept.-Oct. 2007 Domain specific ‘Business Services’

Insurance Define Property and Casualty Services – RFP

planned Scope discussion planned for Sept. SOA SIG-OMG

Insurance WG meeting

White paper “Business Agility: Is SOA Enough” –by SOA SIG, Sept. 2007

23

FYI

OMG SOA SIG (http://soa.omg.org ) meets every Tuesday at the quarterly OMG technical meetings (for 2007 calendar: http://www.omg.org/news/schedule/upcoming.htm )

Upcoming SOA Information Day Sept. 25, 2007 (part of OMG Technical meeting, Jacksonville,

FL, USA) Joint session with OMG Insurance Working Group

Mailing list: [email protected] (to join, please send email to: [email protected] )

24

Contact Info: [email protected] [email protected]@adaptive.com

Contact Info: [email protected] [email protected]@adaptive.com

Thanks for your Time..