Dr Berre - Service Modelling and Representation Techniques

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 13 th , 2010

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, ...

The emerging importance of Services

Porter’s Value Chain

Open Services Innovation Book : January 2011

A Services Value Web

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

NEFFICS (2010-2012)
36 Months
Cost:
4.147 M €
2.898 M € requested EU
323 man-months
Started Sept. 1 st , 2010
Partners:
2 case owners
2 technology providers
3 research partners
`

NEFFICS Community of highly innovative networked enterprises Networked innovation community services (Induct) Applications for highly innovative networked enterprises Virtual Factory Network (Vlastuin) Connected Retail Network (Telecom Italia) Enterprise SaaS Cloud business operations and 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) VDM BEI Networked innovation models, leadership and management processes (ICI) CEN/389

SHAPE (2008-2010)

REMICS (2010-2012) SoaML VDM SoaML Recover Legacy Artifacts Source Architecture Migrate Target Architecture for Service Cloud platform Forward MDA through PIM 4 Cloud Service Cloud Implementa tion Model Driven Interoperability Validate , Control and Supervise Knowledge : REMICS KDM Business Process and Rules Components : SoaML Implementation : UML , U 2 TP 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

ENVISION (2010-2012) SoaML VDM

Zachman Framework – for Enterprise Architecture (IBM, 1987)

OMG Model-Driven Architecture (MDA) www.omg.org/mda

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

Zachman with OMG standards USDL (TEXO, W3C) USDL USDL USDL USDL

OMG standards coverage USDL

Modeling the Business
A business is a complex, multidimensional organism
A 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 dimension
The 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
15 Dec 2010 The Business The Business Architecture

Elements of a Business Architecture

CSI – Center for Service Innovation Norwegian national initiative

CSI planned Activities

Business model innovation 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”.

Sample Customer Experience Model

www.service-innovation.org

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 VDM - Value Delivery Metamodel

Business partner relationships Merchant Customer Internet Publisher 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 Value Exchange Provide Content Purchase Goods Clicks Purchase Ad Publish Ad Sell Goods

VDML Dimensions
Activity network: roles of capabilities
Deliverable producers and consumers
Organizational relationships
Contributions to value propositions
Exchange networks
Performance monitoring
12/15/10

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

OMG - Business Motivation Model (BMM)

People naturally network as they work. So why not model the work itself as a network? December 15, 2010 Value Network Analysis models value creation with a powerful human network approach to managing any business activity.

How Networks Create Value © 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 2008 Value Creating Network

Realizing Value for Network Participants December 15, 2010 Impact Analysis How do we grow financial and intangible assets from our inputs?

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 - RO BCA SOW final validator Integrator of test requirements Authorized management SOW approver(s) Technical Designer-finalizer PO coordinator IDS requirements researcher-author - SOW Initiator Communication convener Functional resource estimator RO 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 validator Test estimate reasonableness assessor Test estimate collector-checker-documenter Functional estimate approver Test estimate requester BCA estimate integrator BCA Pricer BCA 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-acceptor authorized management approver IDS financial analyst IDS Technical Analyst IDS Cost Analyst 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 December 15, 2010 Complex Procurement Activity Showing both tangible and intangible value creation!

e 3 value : A formal ontology for designing and evaluating networked value constellations

e3value Ontology

e3value business model illustration … can be integated with SoaML …

Examples of Services Related to a Service ~ Product ~ Business Process as a Unique Asset Service ~ Product ~ Business Process Analyse Design Simulate Sell Buy Rent Lease Finance Execute Monitor Implement

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

An Example of an REA for Capability to Produce Product or Provide a Service
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
Value Chain Level REA Level

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

See also: www.soaml.org

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.

SoaML – History

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.

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.

SoaML – Concepts
Agent
Attachment
Capability
Consumer
Collaboration
CollaborationUse
Expose
MessageType
Milestone
Participant
Port
Property
Provider
Request
ServiceChannel
ServiceContract
ServiceInterface
Service
ServicesArchitecture

SOA in Model Driven Architecture (MDA) Business Concerns Goals Policy Customers Costs Agility Technology Specification JMS, JEE, Web Services WSDL, BPEL, XML Schema Logical System Model Technology Services (t-SOA) Software Components Interfaces, Messages & Data Business Model Enterprise Services (e-SOA) Roles, Collaborations & Interactions Process & Information Refinement & Automation Line-Of-Sight Computation Independent Model Platform Independent Model Platform Specific Model MDA Terms

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).

SoaML Metamodel, Service/Request Port

SoaML Metamodel ServiceArchitecture and ServiceContract

UML Profile - Collaboration

UML Profile – ServiceInterface, Port

Marketplace Services Example Order Conformation Ship Req Shipped Shipped Delivered Status Provider Consumer Provider Consumer Consumer Provider Mechanics Are Us Dealer Acme Industries Manufacturer GetItThere Freight Shipper Physical Delivery

Business process overview

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 » .
Community-level services architecture for the Dealer Network Shipping Request service Ship Status service Place Order service

Participants and 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 » .
type collaboration use role binding role binding

Services architecture (Participant-level) Order Conformation Shipped Ship Req Shipped Delivered Participant-level services architecture for the Manufacturer OrderHandler Invoicing Productions

Choreography: Place order (Service contract behaviour) (Service interface behaviour) 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 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.
type type Request port Service port

Components implement the service interfaces providing the link to systems. Participants and services may be used in multiple architectures.
Logical system components: Dealer Network Architecture

Software components: Manufacturer Architecture Mapped to software components

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, …

Associated BPMN 2.0 Collaboration

Associated BPMN 2.0 Conversation

Associated BPMN 2.0 Conversation (showing mini-Choreography)

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

Service Variability Process Overview (from SHAPE) © SAP 2009 / Page © SAP 2009 / Page Customization & Personalization Variability Modelling & Pre-Configuration Design, Development, Publication Provider Domain Expert Consumer Roles Phases Artefacts Variability Specification Variability Specification Service Variability Model Service Variability Metamodel Service Variant Model resolves 1:n according to according to Service Model Service Metamodel Service Interface extends 1:n extends Service Variant Interface according to described by described by consistent & valid subset

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/

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

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 13 th , 2010

Dr Berre - Service Modelling and Representation Techniques

by ServiceWave 2010

Accessibility

Upload Details

Usage Rights

Statistics