page 1 copyright © 2010 data access technologies, inc. model driven solutions may 2009 cory...

Copyright © 2010 Data Access Technologies, Inc.

Model Driven SolutionsMay 2009

Cory Casanave

Architecture of Services

SOA for E-Government Conference 2010



Hungry?

Pretzels in a Marketplace

$4

Pretzel



The Pretzel Franchise Service

Franchise

Ordering

Marketing

Establish Franchise



Pretzel Logic *

•Without context services have no meaning

•Services enable people, organizations and systems to collaborate to provide business value

•You need to trust your service partners

* Not Pretzel Logic by Steely Dan



SOA Mythology

• Your going to find services on the internet and run them dynamically– We vet our service partners carefully, “finding” is not always important

• The point of SOA is reuse of technology– The point is enabling collaboration to achieve business value

– If you can reuse that or pieces of it, GREAT! Reuse requires planning!

• Each service is independent– Services are meaningful in a context that may involve many services

• SOA is about technology, processes are about business– SOA is about people, organizations and systems collaborating – it is a way to

understand business federation, facilitated by technology

– Likewise, BPM has technology and business aspects

• You can just start exposing capabilities as services– An architecture puts the services in context to provide business value



Enterprise SOA

• Collaboration– Working with your business partners, collaborators, policy makers

& supply chain– The parts of your organization working together

• Context– Your business environment – internal and external– The business value achieved– Supporting technology services, components and applications

• Trust– Vetting of collaborators– Agreements



SOA & Architecture for Open Government

• Transparency– Transparency means visibility of information, this information includes the

processes, resources, services, data descriptions and policies of government. This information is captured in various kinds of architecture, the most useful being architectures as models

• Collaboration– Collaboration requires an understanding between independent parties, we

have to understand what each has to offer in a common vocabulary and the rules of engagement, captured in architectures

• Participation– Participation is transparency with collaboration. Moving beyond human to

human networking will require architectural data about how to participate

You can only leverage what you understand!



What if your organization wanted to outsource financial operations?

• What is the context?– Outsourced Financial Services

• What is the collaboration?– Your organization and the financial service provider– At a more detail level

• All the ways your organization and departments interacts with the various parts of financial services

• Where is the trust?– Serious vetting of the providing organization– Contract, MOU– Internal assignment of responsibilities



Financial Management Enterprise Context

Other enterprise level participants

Other enterprise level participants

• The service-oriented business architecture of an enterprise is modeled as a Collaboration of enterprise-level Participants.

• The service-oriented business architecture of an enterprise is modeled as a Collaboration of enterprise-level Participants.

Role binding

Collaboration UseRole



Composite Services

Financial Management is responsible for providing a number of Acquisition

Accounting services.

Financial Management is responsible for providing a number of Acquisition

Accounting services.



Details of Exchange

Indicates ownership

First the submitter submits a bill to the receiver…

First the submitter submits a bill to the receiver…

…then either the bill is successfully delivered or it is returned.

…then either the bill is successfully delivered or it is returned.

Note that, while one Participant requests the service and the other

responds, information may flow both ways during the interaction.

Note that, while one Participant requests the service and the other

responds, information may flow both ways during the interaction.



Information

This means “zero or more”

This means “one or more”This indicates a compositional (as opposed to referential) association.

This is a constraint that defines the sub-classification.

A term in the vocabulary represents a class of things to be described.

A term in the vocabulary represents a class of things to be described.

Attributes specify descriptive information having simple types.

Attributes specify descriptive information having simple types.

Entities may be described as having a unique identity.

Entities may be described as having a unique identity.

A relation between terms is described by an association between classes.

A relation between terms is described by an association between classes.

A class may be specialized into sub-classifications.

A class may be specialized into sub-classifications.

An un-shaded class is not detailed on this diagram.



Software Components Collaborating

Implements the Establish Customer Order activity. Implements the Establish Customer Order activity.

Implements the Generate Recurring Receivable and Establish and Accrue Revenue activities.

Implements the Generate Recurring Receivable and Establish and Accrue Revenue activities.



Models are part of the technology solution

<wsdl:portType name=“Bill_Receiver_Interface"> <wsdl:operation name=“submit_bill"> <wsdl:input message="tns:Bill_Submission__Message_Type“ name=“bill_submission"> </wsdl:input> </wsdl:operation> </wsdl:portType>

<wsdl:portType name=“Bill_Submitter_Interface"> <wsdl:operation name=“notify_bill_delivered"> <wsdl:input message="tns:Bill_Delivered__Message_Type“ name=“bill_delivered"> </wsdl:input> </wsdl:operation> <wsdl:operation name=“notify_bill_returned"> <wsdl:input message="tns:Bill_Returned__Message_Type“ name=“bill_returned"> </wsdl:input> </wsdl:operation> </wsdl:portType>



SoaML as a standard for architecting services

• An OMG Standard for Modeling Service Oriented Architectures

– Adopted from the UML® Profile for Modeling Services (UPMS) RFP

– SoaML supports the “A” in SOA

– Used for modeling SOA at the business, enterprise and technology levels

– Leverages Model Driven Architecture

• A “Profile” of the Unified Modeling Language™

– Can be used with off-the-shelf UML tools as well as customized tooling

• An adopted OMG (Object Management Group) specification

• Tool support & implementations already exist

– Tool support – making it easy to create services models

– MDA Implementations – provisioning web services, business artifacts and

implementations from SoaML models



Model Driven Solutions

Enterprise & Solutions Architecture– Enterprise architecture

– OMG MDA standards: UML, SoaML, BPMN, ADM, etc.

– Systems & Systems of Systems Architecture

– Semantic Web/Ontology application to Architecture

– Enterprise SOA and process architecture

MDA based systems implementation– SOA & BPM driven by business architecture

– Distributed systems, Web Services SOA, Executable Models

– Business Process Management

Open Source tools and infrastructure (ModelDriven.org)– Eclipse based MDA provisioning of solutions for SOA

– Semantic Web

– Open source enterprise knowledge base

April 10, 2023

Where business meets technology



Additional Information:

at

http://www.SoaML.org

: http://www.modeldriven.org

: http://soaplus.cameosuite.com/

Cory Casanave, CEOModel Driven SolutionsCory-c (at) modeldriven.com

page 1 copyright © 2010 data access technologies, inc. model driven solutions may 2009 cory...

Documents

data access technologies

model driven solutions

context services

business value slide

business soa

pretzel slide

data descriptions

architectural data