Post on 11-May-2015
description
ICT
Service Modelling and Representation Techniques - a holistic Enterprise Architecture perspective on using and influencing the emerging standards of VDM, USDL and SoaML
Dr. Arne-Jørgen Berre
SINTEF
Networked Systems and Services
Keynote at SMART’2010, Ghent, December 13th, 2010
ICT
Agenda Service science, Enterprise architecture and Services life cycle
Zachman, RM-ODP and other EA frameworks Business architecture and IT architecture – and standards (OMG, W3C, ...) Service – definitions (SoaML ++), NEFFICS and SHAPE projects
Business architecture and Service Innovation (Open) Services innovation (CSI, NEFFICS, CINEX, Chesbrough) Service Design – Service experiences (AT-ONE) Business Model Innovation (NEFFICS) Value Models and Value Networks (VDM) OOram and Role Modeling, e3Value and REA modeling USDL – Universal Service Description Language (W3C)
System and IT architecture SoaML Service Model – background/history SoaML - SHAPE, ..
Composition, Deployment, Runtime, Service Composition tool (ENVISION) Service variability, CVL, and configuration (SHAPE)
Your Future Impact on Standards VDM, SoaML, USDL, BPMN, CVL, ...
ICT
The emerging importance of Services
ICT
Porter’s Value Chain
ICT
Open Services Innovation
Book:January 2011
ICT
A Services Value Web
ICT
SMART - Service Modelling and Representation Techniques
Enterprise Architecture perspective Service – definitions OOram and Role Modeling RM ODP – services view, SWING/ENVISION/CM
VDM e3Value and REA modeling SoaML Service Model – and background/history
USDL VDM workshops
SoaML OMG standard VDM workshops
ICT
8
NEFFICS (2010-2012)
36 Months Cost:
4.147 M€ 2.898 M€ requested EU
323 man-months Started Sept. 1st, 2010 Partners:
2 case owners 2 technology providers 3 research partners
`
ICT
9
NEFFICS Community ofhighly innovative networked enterprises
Networked innovationcommunity services
(Induct)
Applications for highly innovative networked enterprises
Virtual Factory Network(Vlastuin)
Connected Retail Network(Telecom Italia)
Enterprise SaaS Cloud business operationsand orchestration platform
(Cordys)
Google Apps/Waves, Cloud computing & Web 2.0 platform
Networked Enterprises on Internet of Services (COIN) and Things (ASPIRE)
Networked enterprises MashApp applications and process support
(Cordys)
Networked process and service models
(SINTEF)BPMN 2.0,
SoaML, OSM, CMPM
Networked business value analysis models
(IC Focus)VDMBEI
Networked innovation models, leadership and management processes
(ICI)CEN/389
ICT
SHAPE (2008-2010)
10
UPMSUPMS
ICT
REMICS (2010-2012)
11
Recover
Legacy Artifacts
Source
Architecture MigrateTarget
Architecture for Service
Cloud platform
Forward MDA through
PIM4Cloud
Service Cloud
Implementation
Model Driven Interoperability
Validate, Control and Supervise
Knowledge: REMICS KDMBusiness Process and Rules
Components: SoaMLImplementation: UML, U2TP
Knowledge Discovery,Reverse Engineering
Source code, binaries, documentation, users
knowledge, configuration files, execution logs and traces.
SOA and Cloud Computing Patterns applied,
Legacy Components Replacement and Wrapping,
Design by Service Composition
Service mediation for adaptation
SoaML with REMICS extensions for Service Clouds,
Links to Business Models
Model Transformation, Code Generation, Traceability
RESERVOIR, Joyant, Amazon, Google, Microsoft
Models@Runtime for application management,
Model Checking, Model-based Testing for validation
SoaML
VDM
SoaML
ICT
ENVISION (2010-2012)
SoaML
VDM
ICT 13
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL
(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
Things Important to the Business
Entity = Class of Business Thing
Processes Performed
Function = Class of Business Process
Semantic Model
Ent = Business Entity Rel = Business Relationship
Business Process Model
Proc = Business Process I/O = Business Resources
Business LogisticsSystem
Node = Business Location Link = Business Linkage
Work Flow Model
People = Organization Unit Work = Work Product
Master Schedule
Time = Business Event Cycle = Business Cycle
Business Plan
End = Business Objectiv e Means = Business Strategy
ImportantOrganizations
People = Major Organizations
Business locations
Node = Major Business Locations
Ev ents Significantto the Business
Time = MajorBusiness Event
Business Goalsand Strategy
Ends/Means =Major Business Goals
Logical DataModel
Ent = Data Entity Rel = Data Relationship
Application Architecture
Proc = Application Function I/O = User Views
Distributed SystemArchitecture
Node = IS Function Link = Line Characteristics
Human InterfaceArchitecture
People = Role Work = Deliv erable
ProcessingStructure
Time = System Event Cycle = Processing Cycle
Business RuleModel
End = Structural Assertion Means = Action Assertion
Physical DataModel
Ent = Segment/Table Rel = Pointer/Key
SystemDesign
Proc = Computer Function I/O = Data Elements/Sets
TechnologyArchitecture
Node = Hardware/Softw are Link = Line Specifications
PresentationArchitecture
People = User Work = Screen Format
ControlStructure
Time = Ex ecute Cycle = Component Cycle
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Language Statement I/O = Control Block
Netw orkArchitecture
Node = Addresses Link = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub-Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Netw ork
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
Based on work by John A. Zachman
VA Enterprise Architecture
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
DATAWhat
FUNCTIONHow
NETWORKWhere
PEOPLEWho
TIMEWhen
MOTIVATIONWhy
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
SCOPE(CONTEXTUAL)
Planner
ENTERPRISEMODEL
(CONCEPTUAL)
Owner
SYSTEM MODEL(LOGICAL)
Designer
TECHNOLOGYMODEL
(PHYSICAL)
Builder
DETAILEDREPRESENTATIONS(OUT-OF-CONTEXT)
Sub-Contractor
FUNCTIONINGENTERPRISE
Things Important to the Business
Entity = Class of Business Thing
Processes Performed
Function = Class of Business Process
Semantic Model
Ent = Business Entity Rel = Business Relationship
Business Process Model
Proc = Business Process I/O = Business Resources
Business LogisticsSystem
Node = Business Location Link = Business Linkage
Work Flow Model
People = Organization Unit Work = Work Product
Master Schedule
Time = Business Event Cycle = Business Cycle
Business Plan
End = Business Objectiv e Means = Business Strategy
ImportantOrganizations
People = Major Organizations
Business locations
Node = Major Business Locations
Ev ents Significantto the Business
Time = MajorBusiness Event
Business Goalsand Strategy
Ends/Means =Major Business Goals
Logical DataModel
Ent = Data Entity Rel = Data Relationship
Application Architecture
Proc = Application Function I/O = User Views
Distributed SystemArchitecture
Node = IS Function Link = Line Characteristics
Human InterfaceArchitecture
People = Role Work = Deliv erable
ProcessingStructure
Time = System Event Cycle = Processing Cycle
Business RuleModel
End = Structural Assertion Means = Action Assertion
Physical DataModel
Ent = Segment/Table Rel = Pointer/Key
SystemDesign
Proc = Computer Function I/O = Data Elements/Sets
TechnologyArchitecture
Node = Hardware/Softw are Link = Line Specifications
PresentationArchitecture
People = User Work = Screen Format
ControlStructure
Time = Ex ecute Cycle = Component Cycle
RuleDesign
End = Condition Means = Action
DataDefinition
Ent = Field Rel = Address
Program
Proc = Language Statement I/O = Control Block
Netw orkArchitecture
Node = Addresses Link = Protocols
SecurityArchitecture
People = IdentityWork = Job
Timing Definition
Time = InterruptCycle = Machine Cycle
RuleDesign
End = Sub-Condition Means = Step
Data
Ent = Rel =
Function
Proc =I/O =
Netw ork
Node = Link =
Organization
People = Work =
Schedule
Time = Cycle =
Strategy
End = Means =
Zachman Framework – for Enterprise Architecture (IBM, 1987)
ICT 14
OMG Model-Driven Architecture (MDA)
www.omg.org/mda
ICT
Use of OMG metamodels Business Architecture
UPDM, BMM BPMN 2.0 VDM, OSM (Value Networks, Value Chain, REA, e3Value, …) SoaML USDL (Theseus TEXOS, SAP) (W3C)
IT Architecture SoaML SBVR, ODM
Deployment, Configuration CVL, ServiceVariability, PIM4Cloud/CloudML
Conclusion VDM, SoaML, USDL
15
ICT
Zachman with OMG standards
16
Data(What)
Function(How)
Network(Where)
People(Who)
Time(When)
Motivation(Why)
Scope(Contexts)
Business(Concepts)
System(Logic)
Technology(Physics)
Component(Assemblies)
List of things importantto business
SBVR
List of processes thatthe business performs
VDM
List of locations whichthe business operates
VDM
List of organizationsimportant to the business
OSM
List of events/cyclesimportant to the business
DTFV
List of businessgoals/strategies
BMM
Semantic Model
ODM,IMM (CWM)
Business ProcessModel
BPMN, CMPM
Business LogisticsSystem
BPMN, CMPM
Workflow Model
OSM, BPMN, CMPM
Master Schedule
BPMN, CMPM, DTFV
BusinessPlan
SBVR
Logical Data Model
ODM, IMM (CWM), UML
ApplicationArchitecture
SoaML, UML
DistributedSystem Architecture
SoaML, UML
Human InterfaceArchitecture
BPMN, CMPM
Process Structure
BPMN, CMPM, DTFV
Business RuleModel
SBVR
Physical Data Model
IMM (CWM), UMLSystem Design
SoaML, UML
TechnologyArchitecture
SoaML, UML
PresentationArchitecture
Control Structure
BPMN, CMPM, DTFV
RuleDesign
SBVR
Data Definition
IMM (CWM), UMLProgram
UML
NetworkArchitecture
UML
SecurityArchitecture
TimingDefinition
DTFV
RuleDefinition
SBVR
Operation(Instances)
Data Function Network Organization Schedule Strategy
USDL (TEXO, W3C)
USDL USDLUSDL USDL
ICT
OMG standards coverage
17
Data(What)
Function(How)
Network(Where)
People(Who)
Time(When)
Motivation(Why)
Scope(Contexts)
Business(Concepts)
System(Logic)
Technology(Physics)
Component(Assemblies)
List of thingsimportant
to business
List of processesthat the business
performs
List of locationswhich the business
operates
List of organizationsimportant to the
business
List of events/cyclesimportant to the
business
List of businessgoals/strategies
Semantic ModelBusinessProcessModel
BusinessLogisticsSystem
WorkflowModel
MasterSchedule
BusinessPlan
Logical Data ModelApplicationArchitecture
DistributedSystem
Architecture
HumanInterface
Architecture
ProcessStructure
Business RuleModel
Physical Data Model System DesignTechnologyArchitecture
PresentationArchitecture
ControlStructure
RuleDesign
Data Definition ProgramNetwork
ArchitectureSecurity
ArchitectureTiming
DefinitionRule
Definition
Operation(Instances)
Data Function Network Organization Schedule Strategy
BMM
SBVR
VDM OSMSBVR
DTFV
BPMN
UMLIMM(CWM)
CMPM
SoaML
ODM
USDL
ICT
18
12 Apr 2023 18
Modeling the Business
A business is a complex, multidimensional organismA metaphor for a multi-dimensional representation is the multi-hedron shown
below, representing some of the most important dimensions, like process, application, data and of course the customer
Each dimension has linkages with every other dimensionThe goal of modeling is to optimally represent just enough of these dimensions
and linkages (without devolving into infinite possibilities) so that we model the problems and solutions at hand
The Business The Business Architecture
ICT
Capabilities
Initiatives& Projects
Customers,Suppliers & Competitors
Information & Vocabulary
Products, Services &
Assets
Business Processes
Vision, Strategies &
Tactics
Decisions & Events
OrganizationUnits
Business Architecture
Metrics & Measures
Policies, Rules,
Regulations
Strategic:Direction setting / Executive level decision making
Value Add: Core of who the organization is / how customers view organization
Support:Expenses incurred as result of being in business
Reserves Management
Marketing
Claims Administration Billing
Human Resources
Procurement
Customer Management
Sales
Investments
Accounting
Legal
Information Technology
Customer
Customer Access Points
Value Stream
Organization Structure Delineation Points
Horizontal Business Processes
Source: TSG, Inc.
Balance Scorecard
ABC Insurance
Property & Casualty
Life & Disability
Health
ClaimsReserves Management Investments
Sales
Marketing
EnterpriseDiagram Key
Business Unit
Supporting Capabilities
Value Add Capabilities
Strategic Capabilities
ITCustomer
Management
Administration
Procurement
Human Resources
Legal
Accounting
Billing
Information Technology
Finance
Marketing
Legal Dept.
Purchasing
HR
Completion % of projects impacting customer consolidation capabilities & processes
Percentage of Spend supporting Strategic Initiatives
Rate of New Issues Logged for Strategic Initiatives
Executive View: Root Cause Analysis
Process / Value Stream Aggregation & Decomposition
Executive Dashboards
Value Chains/Value Streams
Organization Models
Capability Map
Business Domain Mappings
19
Elements of a Business Architecture
ICT
CSI – Center for Service InnovationNorwegian national initiative
ICT
CSI planned Activities
ICT
Timmers, 1998 “Business model stands for the architecture for the product, service and information flows, including a description of the various business actors and their roles, the potential benefits for these actors and the sources of revenues……… the business model includes competition and stakeholders”
Stewart and Zao, 2000
“Business model is a statement of how a firm will make money and sustain its profit stream over time”.
Weill and Vitale, 2001
“A description of the roles and relationships among a firm’s consumers, customers, allies and suppliers that identifies major flows of product, information and money and the major benefits to participants”.
Osterwalder et al. 2004
“A blueprint of how a company does business. It is a conceptual tool that contains a set of elements and their relationships and allows expressing a company’s logic of earning money. It is a description of the value a company offers to one or several segments of customers and the architecture of the firm and its network of partners for creating, marketing and delivering this value and relationship capital, in order to generate profitable and sustainable revenue stream”
Chesbrough 2006
“…is a useful framework to link ideas and technologies to economic outcomes”… “It also has value in understanding how companies of all sizes can convert technological potential [e.g. products, feasibility, and performance] into economic value [price and profits]”….. “Every company has a business model, whether that model is articulated or not”.
Skarzynski and Gibson 2008
“…is a conceptual framework for identifying how a company creates, delivers, and extracts value. It typically includes a whole set of integrated components, all of which can be looked on as opportunities for innovation and competitive advantage”.
Business model innovation
ICT
23
Sample Customer Experience Model
ICT
www.service-innovation.org
ICT
Value Delivery Modeling Language(OMG RFP) (2009 – 2011 – 2012)
Ongoing work on a Value Delivery Metamodel RFP to OMG – with initial submission in May 2011
25
VDM - Value Delivery Metamodel
ICT
Merchant
Customer
Internet Publisher
Business partner relationships
Participation
Participation
Participation
Value Prop’n
Value Prop’n
Value Prop’n
Value Prop’n
Value Prop’n
Value Prop’n
Each business entity must realize a net
gain
Diagram for illustration, not a proposed notation
ValueExchange
Provide ContentPurchase
Goods
Clicks
Purchase Ad
Publish AdSell
Goods
ICT
VDML Dimensions
Activity network: roles of capabilities Deliverable producers and consumers Organizational relationships Contributions to value propositions Exchange networks Performance monitoring
04/12/23
27
ICT
Related Techniques
Porter Value Chain Value Chain Group, Value Reference Model (VRM) Verna Allee, value networks e3Value e-Commerce analysis Business model generation (Osterwalder) Value stream mapping Capability mapping Service Oriented Architecture (SOA) analysis
ICT
OMG - Business MotivationModel (BMM)
29
ICT
So why not model the
work itself as a network?
So why not model the
work itself as a network?
People naturally network as they work.
April 12, 202330
Value Network Analysis models value creation with a powerful human network approach to managing any business activity.
ICT
How Networks Create Value
31©
The emergent purpose of the value network is revealed through the pattern of roles and value exchanges that support an economic or
social goal or output.
Sustainability depends on a consistent high level of both transactional and network perceived value.
Allee, Journal of Intellectual Capital, January 2008Value Creating Network
ICT
VNA Fills An Analytical Gap
Formal Organization
Social Networks Business ProcessModeling
Asset Management
April 12, 2023 32© 1997-2009 Value Networks, LLC All rights reserved.
ICT
Value Network Modeling
April 12, 202333© 1997-2010 Value Networks, LLC All rights
reserved.
Roles
Intangible (Informal) Interaction
s
Tangible (Formal) Deliverabl
es
ICT
Realizing Value for Network Participants
April 12, 202334
AgR Developers
License
Commercializers
AgR Investors
Proof ofConcept
MarketParticipants
Orders
Market Pull
Experts
Investors
StrategicDirection
ExpertiseProof ofConcept
Impact Analysis
How do we grow financial and intangible assets from our inputs?
ICT
A Network View of the Work Itself
Confidential Information – Do Not Distribute. Copyright © 2000-2008 ValueNetworks.com. All rights reserved.
CITAP Inputer - RO_IDS
SOW Inputer - ROBCA SOW final validatorIntegrator of test requirements
Authorized management SOW approver(s)
Technical Designer-finalizer PO coordinator
IDS requirements researcher-author - SOW Initiator
Communication convener
Functional resource estimatorRO SOW Final Approver
Resource Owner
FOTV-BCA PO info advisor
ITAR_EAR Analyst-Determiner
RO RFP Creator
BCA RFP Reviewer
PIW Creator
Non-FTO_V estimate collector-checker-coordinator
SOW technical evaluator-reviewer
Non-FTOV estimate collector-checker-coordinator
Functional SME
Authorized management PIW approver
PoP Adjuster
Coordinator
BCA SOW estimate and PoP validatorTest estimate reasonableness assessor
Test estimate collector-checker-documenter
Functional estimate approver
Test estimate requester
BCA estimate integrator
BCA PricerBCA Price approver
Expiration date assigner
BCA Proposal Creator
BCA cost policy reviewer
CITAP Project Manager
BCA work performer
BCA proposal implementer
Chargeline assigner
Job Number Assigner
IDS Proposal evaluator-acceptorauthorized management approver
IDS financial analyst
IDS Technical Analyst
IDS Cost Analyst0
00
0
00
000
0
0
0
0
0
0
00
0
0
0 0
0
0
0
0
0
0
0
0
00
00000
0
00
0
0
00
0
00000
0
00
0
000
0
0000
0
0
0
0
0
0
0
000
0
00
00 0
0
0
00
0
0
00
0
0 000
0
0
00
000
0
0
0
0
0
00
00
0
0
0
00
0
0
00
0
0
00
0
0
00
0
0
0
0
0
00
April 12, 202335
Complex Procurement ActivityShowing both tangible and intangible value creation!
ICT
e3value : A formal ontology for designing and evaluating networked value constellations
ICT
e3value Ontology
ICT
e3value business model illustration
… can be integated with SoaML …
ICT
Examples of Services Related to a Service ~ Product ~ Business Process as a Unique Asset
Service ~ Product ~ Business Process
Analyse
Design
Simulate
SellBuyRent
LeaseFinance Execute
Monitor
Implement
ICT
REA (Resources, Events, Agents)The Nucleus of Every Value-Adding Process
• Small set of archetypes: Resource, Event, Agent, Commitment, Contract, that allows to effectively model any value-adding process
• An ontology for economic systems and a generalized framework for modeling business processes, developed by William E. McCarthy and Guido Geerts, since1982.
UMM Modeling Methodology
ICT
An Example of an REA for Capability to Produce Product or Provide a Service
«resource»Raw Material
«economic event»Material Issue
«economic event»Production
«resource»Product or
Service
«produce»«economic event»
Labor Consumption
«resource»Labor
«economic agent»Company
«economic agent»Company
«provide»
«receive»
«economic event»Oven Use
«conversion»
«resource»Machinery
«provide»
«use»
«provide»
«receive»
«consume»
«consume»
• Use – resource still exists after the economic event
• Consume – resource does not exist after the economic event
• Produce – resource is created by the event or a service is provided by the economic event
«conversion process»Production
Product or ServiceLaborRaw Material
Machinery
Value Chain Level
REA Level
ICT
USDL – The Unified Service Description Language (USDL)See: http://www.internet-of-services.com/
See also: http://www.w3.org/2005/Incubator/usdl/wiki/Main_Page
ICT
ICT
ICT
ICT
ICT
ICT
ICT 49
See also: www.soaml.org
ICT
What is SoaML?
Service oriented architecture Modeling Language (SoaML)
Extensions to UML2 to support service concepts – as a UML Profile and a corresponding metamodel
Focuses on basic service modelling concepts.
A foundation for further extensions and integration with BPMN, BMM and other metamodels.
50
ICT 51
SoaML – History
Issued September 29, 2006
LOI DeadlineNovember 28, 2006
Initial Submission Deadline June 4, 2007
Voting List DeadlineAugust 5, 2007
Revised SubmissionNovember 19, 2007
Revised Submission Deadline May 26, 2008
OMG Technical MeetingJune 23-27, 2008 * Ontario Canada
IBM,... Fujitsu,... SHAPE,...
Adaptive,...
Revised Submission Deadline Aug 25, 2008
OMG Technical MeetingSept 22-26, 2008 * Orlando EEUU
OMG Technical MeetingDec 08-12, 2008 * Santa Clara EEUU
Revised Submission Deadline Nov 10, 2008
S1(3)
S2(2)S3(1)
S4
S5
Sx – Submission version xBx – Beta version x
SoaML FTF Feb., 2009B1
SoaML FTF Nov., 2009 SoaML FTF Rec. Dec., 2009, Los Angeles
SoaML final standardMarch, 2010 (veto, by
Oct. 2010)
B2
BPMN 2.0, Dec. 2009
AMP, Aug. 2009
Issued September 29, 2006
LOI DeadlineNovember 28, 2006
Initial Submission Deadline June 4, 2007
Voting List DeadlineAugust 5, 2007
Revised SubmissionNovember 19, 2007
Revised Submission Deadline May 26, 2008
OMG Technical MeetingJune 23-27, 2008 * Ontario Canada
IBM,... Fujitsu,... SHAPE,...
Adaptive,...
Revised Submission Deadline Aug 25, 2008
OMG Technical MeetingSept 22-26, 2008 * Orlando EEUU
OMG Technical MeetingDec 08-12, 2008 * Santa Clara EEUU
Revised Submission Deadline Nov 10, 2008
S1(3)
S2(2)S3(1)
S4
S5
Sx – Submission version xBx – Beta version x
SoaML FTF Feb., 2009B1
SoaML FTF Nov., 2009 SoaML FTF Rec. Dec., 2009, Los Angeles
SoaML final standardMarch, 2010 (veto, by
Oct. 2010)
B2
BPMN 2.0, Dec. 2009
AMP, Aug. 2009
ICT
SoaML – Goals
Model Driven Architecture (MDA).
Intuitive and complete service modelling in UML.
Bi-directional asynchronous services.
Services architectures where parties provide and use multiple services.
Services defined to contain other services.
Mapped to and part of a business process specification.
Compatibility with UML and BPMN.
Direct mapping to Web services.
Top-down, bottom up or meet-in-the-middle modelling.
Design by contract or dynamic adaptation of services.
Service capability and its contract.
No changes to UML.
52
ICT
SoaML – Capabilities
UML extensions to support service modelling:
identifying services
specifying services
defining service consumers and providers
policies for using and providing services.
defining classification schemes
defining service and service usage requirements and linking them to related OMG metamodels such as the BMM and BPMN.
53
ICT
SoaML – Concepts
Agent
Attachment
Capability
Consumer
Collaboration
CollaborationUse
Expose
MessageType
Milestone
Participant
Port
Property
Provider
Request
ServiceChannel
ServiceContract
ServiceInterface
Service
ServicesArchitecture
54
ICT
SOA in Model Driven Architecture (MDA)
55
Business Concerns
Goals
Policy
Customers
Costs
AgilityTechnology Specification
JMS, JEE, Web ServicesWSDL, BPEL, XML Schema
Technology SpecificationJMS, JEE, Web Services
WSDL, BPEL, XML Schema
Logical System ModelTechnology Services (t-SOA)
Software ComponentsInterfaces, Messages & Data
Logical System ModelTechnology Services (t-SOA)
Software ComponentsInterfaces, Messages & Data
Business ModelEnterprise Services (e-SOA)
Roles, Collaborations & InteractionsProcess & Information
Business ModelEnterprise Services (e-SOA)
Roles, Collaborations & InteractionsProcess & Information
Re
finem
ent &
Au
tom
atio
n
Lin
e-O
f-S
igh
tC
om
pu
tati
on
Ind
ep
en
de
nt
Mo
de
l
Pla
tfo
rmIn
de
pe
nd
en
tM
od
el
Pla
tfo
rmS
pec
ific
Mo
de
l
MDATerms
ICT
56
SoaML – Service and SOA
”A service is value delivered to another through a well-defined interface and available to a community (which may be the general public). A service results in work provided to one by another. “
Service Oriented Architecture (SOA) is a way of describing and understanding organizations, communities and systems to maximize agility, scale and interoperability.
SOA is an architectural paradigm for defining how people, organizations and systems provide and use services to achieve results.
SoaML provides a standard way to architect and model SOA solutions using the Unified Modeling Language (UML).
ICT
SoaML Metamodel, Service/Request Port
ICT
SoaML MetamodelServiceArchitecture and ServiceContract
ICT
UML Profile - Collaboration
ICT
UML Profile – ServiceInterface, Port
ICT
Marketplace Services Example
Order
Conformation
Ship Req
Shipped
Shipped
PhysicalDelivery
Delivered
Status
Pro
vid
er
Consumer
Pro
vid
er
Co
ns
um
er
Consumer
Pro
vid
er
Mechanics Are UsDealer
Acme IndustriesManufacturer
61
GetItThereFreight Shipper
ICT
Business process overview
62
: I
nvo
icin
g :
Pro
du
ctio
ns
: O
rde
rHan
dle
r
: S
hip
per
: M
anuf
actu
rer
: D
eale
r
I nitiate production
:O rderC onfirmation :O rder
Start event
I nventory low?
[yes]
[no]
:ShippingRequest :ShipmentStatus
:ShipmentStatus
End event
:DeliveryC onfirmation
Send invoice
End event
End event
Ship order Order production
C onfirm orderReceive order
Receive order confirmationPlace order
Ship item Send shipping confirmation
Receive shipping confirmation
Forward shipping confirmation
Receive shipping confirmation
Send delivery confirmation
Receive delivery confirmation I nvoice customer
ICT
Dealer Network Architecture<<ServicesArchitecture>>
ship: Shipping Requeststatus: Ship Status
order: Place Order
provider
consumer
provider
consumer
providerconsumer
shipper: Shipper
acme: Manufacturerdealer: Dealer
Services architecture(Community-level)
Services architecture: High level description of how participants work together for a purpose by
providing and using services expressed as service contracts. UML collaboration stereotyped «ServicesArchitecture».
63
ShippingRequest service
ShippingRequest service
Ship Status service
Ship Status service
Place Order servicePlace Order service
Community-level services architecture for the Dealer Network
Community-level services architecture for the Dealer Network
ICT
Dealer Network Architecture
<<ServicesArchitecture>>
ship: Shipping Requeststatus: Ship Status
order: Place Order
provider
consumer
provider
consumer
providerconsumer
shipper: Shipper
acme: Manufacturerdealer: Dealer
Participantsand service
contracts
Service contract: Service specifications that define
the roles each participant plays in the service and the interfaces they implement to play that role.
UML collaboration stereotyped «ServiceContract».
Participant: Represent logical or real people or
organizational units that participate in services architectures and/or business processes.
UML class stereotyped «Participant».
64
Shipper
<<Participant>>
Manufacturer
<<Participant>>
Dealer<<Participant>>
Shipping Request
<<ServiceContract>>
Ship Status
<<ServiceContract>>
Place Order
<<ServiceContract>>
provider:consumer:
provider:consumer:
provider: OrderTakerconsumer: OrderPlacer
type
collaborationuse
rolebinding
rolebinding
ICT
Manufacturer Architecture
<<ServicesArchitecture>>
po: Production Order
ic: I nvoice Customer
ship: Shipping Request
order: Place Order
provider
provider
consumer
consumerconsumer
provider
provider
consumer
shipper: Shipper
dealer: Dealer
p: Productions
i: I nvoicing
oh: OrderHandler
Services architecture(Participant-level)
65
Order
Conformation
Shipped
Ship Req
Shipped
Delivered
OrderHandler
Invoicing
Productions
Participant-level services
architecture for the Manufacturer
Participant-level services
architecture for the Manufacturer
ICT
opt
[]
provider: OrderTakerconsumer: OrderPlacer
quoteRequest
quote
order
orderConfirmation
Choreography: Place order(Service contract behaviour)(Service interface behaviour)
66
prov
ide
r :
Ord
erT
aker
con
sum
er :
Ord
erPl
ace
r
orderquoteRequest
orderC onfirmationquote
Service choreography can be specified using any UML behaviour,
e.g, interaction or activity
Service choreography can be specified using any UML behaviour,
e.g, interaction or activity
Service choreography can be specified using any UML behaviour,
e.g, interaction or activity
Service choreography can be specified using any UML behaviour,
e.g, interaction or activity
ICT
Service and request ports:Place order
Service: Specifies a feature of a participant that is the offer of a service by one participant
to others using well defined terms, conditions and interfaces. UML port stereotyped «Service» on a participant or component.
Request: Specifies a feature of a participant that represents a service the participant needs
and consumes from other participants. UML port stereotyped «Request» on a participant or component.
67
Manufacturer<<Participant>>
Dealer<<Participant>>
<<Service>> s: PlaceOrderI nterface<<Request>> r: ~PlaceOrderI nterface
OrderTakerOrderTaker
OrderPlacer OrderPlacer
<<use>>
<<use>>
OrderPlacer<<interface, Consumer>>
OrderTaker<<interface, Provider>> PlaceOrderInterface
<<ServiceInterface>>~PlaceOrderInterface<<ServiceInterface>>
quote()
orderConfirmation()
quoteRequest()
order()
typetype
Request port
Request port
Service port
Service port
ICT
Shipper<<Participant>>
Manufacturer<<Participant>>
Dealer<<Participant>>
<<Service>> ssi: ShipStatusI nterface
<<Service>> s: PlaceOrderI nterface
<<Request>> r: ~PlaceOrderI nterface
OrderPlacer
OrderTaker
OrderTaker
OrderPlacer
Shipper
<<Service>> sri: ShippingRequestI nterface
<<Request>> sri: ~ShippingRequestI nterface
<<Request>> ssi: ~ShipStatusI nterface
ShippingProviderShippingConsumer
ShippingConsumer
ShippingProvider
Shipper
Components implement the service interfaces providing the link to systems. Participants and services may be used in multiple architectures.
Dealer Network Architecture
<<ServicesArchitecture>>
ship: Shipping Requeststatus: Ship Status
order: Place Order
provider
consumer
provider
consumer
providerconsumer
shipper: Shipper
acme: Manufacturerdealer: Dealer
Logical systemcomponents:
Dealer Network Architecture
68
ICT
Software components:
Manufacturer Architecture
69
Manufacturer Architecture<<ServicesArchitecture>>
po: Production Order
ic: I nvoice Customer
ship: Shipping Request
order: Place Order
provider
provider
consumer
consumerconsumer
provider
provider
consumer
shipper: Shipper
dealer: Dealer
p: Productions
i: I nvoicing
oh: OrderHandler
Shipper<<Participant>>
Manufacturer<<Participant>>
Dealer<<Participant>>
p: Productions
i: I nvoicing
oh: OrderHandler
<<Service>> sri: ShippingRequestI nterface
<<Request>> r: ~PlaceOrderI nterface
<<Service>> poi: ProductionOrderI nterface
<<Service>> ici: I nvoiceCustomerI nterface
<<Request>> ici: ~I nvoiceCustomerI nterface
<<Request>> poi: ~ProductionOrderI nterface
<<Service>> s: PlaceOrderI nterface
<<Request>> sri: ~ShippingRequestI nterface
<<Service>> s: PlaceOrderI nterface
<<Request>> sri: ~ShippingRequestI nterface
Mapped to software components
ICT
BPMN 2.0 and SoaML tools today
BPMN 2.0 Signavio has 2.0 Conversation and Choreography diagrams – a
SaaS solution Most BPMN 1.2 are doing stepwise migration, making existing
parts 2.0 compliant
SoaML (in most UML tools) Magic Draw (Cameo), Enterprise Architect, IBM RSA/RSM,
Modelio, …
ICT
Associated BPMN 2.0 CollaborationO
rder
P
roce
ssor
Cus
tom
er
Sch
edul
er
Order
Invo
icer
PriceData
Shi
pper
Invoice
Price DataUpdate
Invoice
ShippingResponse
Schedule
ShippingRequest Schedule
RequestShedule
Response
Pools/Participants represent
PartnerEntities (at any level) and/or
PartnerRoles
The Message Flow are unordered and
ungrouped.Grouping by Conversation
can be hidden.
ICT
Associated BPMN 2.0 ConversationO
rder
P
roce
ssor
Cus
tom
er
Sch
edul
er
Order
Invo
icer
Shi
pper
Invoice Shipping Schedule
Conversations group Message Flow based on
business level info or Correlation Keys
ICT
Associated BPMN 2.0 Conversation (showing mini-Choreography)
Ord
er
Pro
cess
or
Cus
tom
er
Sch
edul
er
Invo
icer
Shi
pper
Invoicer
Establish Price
Order Processor
Invoicer
Update Price
Order Processor
Invoicer
Create Invoice
Order Processor
PriceData
Price DataUpdate
Invoice
ScheduleShipping
Order
ICT
Mappings
SoaML Term BPMN Mapping
ServicesArchitecture (a UML Collaboration) or a specification Participant
Overview Choreography
Participant Participant representing PartnerEntity (within definitional collaboration
Service Port One end of a communication between participants in a communication diagram: Interface of the above participant
Request Port The other end of the communication, the one sending the first message
ServiceInterface (defining the type of a Service or Request Port)
Interface, but doesn’t support service protocols. Alternatively, a communication in a communication diagram, including the corresponding messages in a collaboration diagram, and the choreography of those messages in a choreography diagram
Interface (realized or used by a ServiceInterface) Interface, but not clear how this relates to a communication
Operation or Reception (of an Interface) Operation of an Interface or Message, but not clear how this relates to an operation of an interface
Parameter (of an Operation) Message inputs and outputs for an Operation
ICT © SAP 2009 / Page 75
© SAP 2009 / Page 75
Service Variability ProcessOverview (from SHAPE)
Customization& Personalization
Variability Modelling &Pre-Configuration
Design, Development, Publication
Provider Domain Expert ConsumerRol
esP
hase
sA
rtef
acts
Variability SpecificationVariability
SpecificationService Variability
Model
Service Variability Metamodel
Service Variant Model
resolves1:n
according to according to
Service Model
Service Metamodel
Service Interface
extends1:n
extends
Service Variant Interface
according to
described by described by
consistent & valid subset
ICT © SAP 2009 / Page 76
Example (from SHAPE)Customization & Personalization
ICT
References SoaML Beta2 - http://www.omg.org/spec/SoaML/1.0/Beta2 BPMN 2.0 Beta2 http://www.omg.org/spec/BPMN/2.0/Beta2
SHAPE Methodology Paper M. Stollberg, B. Elvesæter, V. Shafran, R. Magarshak, “A Customizable
Methodology for the Model-driven Engineering of Service-based System Landscapes”, MDA4ServiceCloud workshop, Paris, France, 15 June 2010.
SHAPE Methodology Online http://www.shape-project.eu/download-area/SHAPE-
Methodology_OnlineLibrary_final/index.htm SoaML wiki
http://www.omgwiki.org/SoaML/doku.php Business Motivation Model (BMM)
http://www.omg.org/spec/BMM/1.1/PDF/ Eclipse Process Framework (EPF)
http://www.eclipse.org/epf/
77
ICT
Conclusion
Understand Services in a holistic perspective Enterprise architectures (enhanced) can a provide a
framework for modeling and representations
Evolving standardisation activities should be influenced by good ideas and research results
VDM (OMG) – Consider contributions in 2011 USDL (W3C) – Consider contributions in 2011 SoaML (OMG) – Consider contributions in 2011
ICT
Service Modelling and Representation Techniques - a holistic Enterprise Architecture perspective on using and influencing the emerging standards of VDM, USDL and SoaML
Dr. Arne-Jørgen Berre
SINTEF
Networked Systems and Services
Keynote at SMART’2010, Ghent, December 13th, 2010