slide 1 business modelling: omg - edoc bringing together business goals, standards, processes and...

Business Modelling: OMG - EDOC

Bringing together business goals, standards, processes and technologies for the e-enabled enterprise

EnterpriseDistributedObjectComputing

Integrating Enterprises, People & Systems - WorldwideIntegrating Enterprises, People & Systems - Worldwide

Using InternetTechnologies

Enabling e

Integrating Enterprises, People & Systems - WorldwideIntegrating Enterprises, People & Systems - Worldwide

Business RequirementsVirtual Enterprises

Enterprise Integration (EAI)

Supply-chain automation (B2B)

Customer Integration (B2B)

Web deployment (B2C)

Internet Marketplace (B2C)

Collaboration and Integration

The dynamic reality

The information system must facilitate;Rapid realization of business goalsIntegration of independent processes and systemsMultiple and Changing

business requirementsbusiness processestechnologiesstandards enterprise boundariespartners

The e-enabled enterprise

Has a competitive advantage in its capability to embrace collaboration and

change

Components

Workflow

Repositories

Metadata

OpenOpenCollaborativeCollaborative

EnterpriseEnterprise

Embracing collaboration and change

Model DrivenArchitecture

Shared Data

EAI

We need to extract the meat from the buzzwords

And figure out how these concepts fit together

To e-enable the enterprise

Web Services

Middleware

Messaging& Events

Business & Technology Coupling

“Open B2B”Ad-hoc business

“Community B2B” - Business Partners & Independent Divisions

Integration within a managed domain

Integration or production of an application

InternetComputing

Model

ebXMLSoap Events &

Messaging

JMSMQ-Series

SynchronousTransactional

RPC

CorbaEJB

SharedData

SQLIMS-DB

CollaborativeComponents

EDOCModel

(UML)

TraditionalEDI

The role of open systems in the enterprise

Supporting open distributed computing while meeting local requirements

The Enterprise“The Enterprise”

The “open domain”Independent domains collaborating

via open standards

No assumption of “the same thing” on both sides!

Appropriate inside and outside the enterprise (EI & B2B)

Requires business (process collaboration and information) and technical (middleware) standards

The open domain needs a point of ownership in the enterprise

Enterprise boundaries are not static!

The Internet Computing Model

Collaboration of independent entitiesDocument exchange over internet technologies

Large grain interactions

No required infrastructure *Long lived business processesBusiness transactions

BusinessParty

BusinessParty

Portals

Requirements for the “ICM”Contract of Collaboration

Shared business semantics

Meta-Model (EDOC-ECA) and representation (I.E. XMI, ebXML-BPSS)

Shared Repository for Contracts (MOF, UDDI, ebXML)

Connectivity (middleware) which meets requirements of the contract

Implementation of each contract role providing connectivity (application server)

BusinessPartner

BusinessPartner

Repository

Contracts(Metadata)

Contract of collaboration can be mapped to the format of various technologies. (ebXML, Soap, .NET)

Instance Data

Two levels of interoperability

Instance data and interoperability

Metadata (contract) interoperability

BusinessPartner

BusinessPartner Bridge

Each can be transformed

PurchasingModel

.NETebXMLBPSS

ebXML Biztalk

Normal Form

Over Soap Over Soap

Drilling down – inside a roleThe open domain should make no

assumptions about the “inside” of a role.

Inside one role you frequently find more collaborating “parts” of the enterprise - the same model may be used

Until you get to system inside a managed domain

Shared resources (DBMS)

Common Management

Frequently a legacy system

Inner RoleLegacy

InnerRole

Inner RoleDomain

Cust

Collaborative Business Semantics

Defined: The processes, information and contracts of interaction between collaborators within a community

Collaborative business semantics are a valuable long-term asset

Captures information and process

Requires ownership and support in the open domain

Do not put this valuable asset in a (transient - one size fits all) technology specific formUse technology independent models (MDA)

Map to the technology of the day (E.G. DTD)

Required support for the open domain

Connectivity standards and infrastructureProviding the enterprise “bus” (Intranet)

http, Soap, ebXML

Common processes and lexiconWhat goes on the bus - the real business value!

Facilitating communities of practice

Meta-model standards (UML, ebXML-BPSS, EDOC...)How to represent shared processes and information

Repositories Finding services, models and components for design time and runtime integration

Standards for Global Internet Computing

UML4EDOCUML4EDOCUML4EDOCUML4EDOCSOAP

WSDL

XML

XML-Schema.NET BPML

XML Standards

XML Schema & DTDDescription and packaging of data

SoapBasic messaging and packaging

Extensions for Soap-RPC with WSDL

May be extended to support collaborative messaging

Vision

EDOC (a UML Profile)Provide an architecture for open collaborative computing

Simplify the development of component based distributed systems by means of a modelling framework, based on UML 1.4

Provide a platform independent, recursive collaboration based modelling approach supporting multiple technologies.

Embrace Model Driven Architectures (MDA) – Provide design and infrastructure models and mapping

ebXMLCreating a single global electronic market

Includes process specification, transport and repositories

ebXML & EDOC

Transport

Distribution

Repository

Runtime

EnterpriseIntegration

Components

InformationModel

MDA

Collaboration

Process Model

ebXML EDOC

Standards for collaboration

EDOC-ECA ebXML-BPSS

Business Collaborations Yes – Community Process Yes – Multi Party Collaboration

Contract of Interaction Yes – Protocol with Choreography & Object Interface

Yes – Binary Collaboration with Choreography and Business Transactions

Content Model Yes – Document Model Uses external forms, such as XML Schema

Recursive Composition Yes – Recursive Composition into Enterprise

No – Only “B2B”

Detail sufficient to drive communications

No – Requires technology mapping Yes – As ebXML transport. BPSS includes timing and security parameters.

Computing Models Supported Internet document exchange, entities, business processes, objects and events

Internet document exchange

Parts of EDOC

Enterprise Collaboration Architecture (PIM)Component Collaboration Architecture

Business Process Specification

Entities

Business Events

Patterns

Technology Mapping (PSM – in progress)Flow Composition Model (Messaging)

EJB & Corba Components

ebXML

.NET

Others…

MAPPING – Precise models are are source code

XMLCorbaEJB

.NETEvents

HTTP Web ServerApplications

Enterprise ArchitectureEnterprise Architecture

SQL DBMS,Client/Server

& Legacy Applications

ClientApplications

EAI Applications &B2B E-Commerce

WebBrowser

Supply Chain

EnterpriseComponents

Parts of ebXML

Business Process Specification (Like EDOC-CCA)XML Representation of business process

Core Components Business Data Types & documents based on context

Collaboration Protocol ProfileWhat business partners implement what business processes using what technologiesOne-One agreement for doing business

Transport Routing & Packaging Messaging Built on Soap

Registry & RepositoryFinding business partners, document and process specifications

ebXML Architecture

BPSpecification

Business Process

Core Data Blocks

Business Messages

CPA

Context For Built With

Implement one Partner Role Implement other

Partner Roles

Register

Designtime Designtime

CPP CPP

Transport

Package

Business Service

Interface

Internal Business App

Internal Business App

Business Service

Interface

Runtime

Summary of points thus farWe must enable the emerging Internet Computing Model

Loosely coupled roles exchanging documents based on a contract of collaboration

Web need interoperability at two levelsMessaging for the data

Metadata for the contract of collaboration, stored in repositories

This model of collaborating roles is recursive, extending into the enterprise, into managed domains and into applications

Inside the enterprise we want to include resources entities, business events and business processes

Supporting the open domain has some required parts and can be augmented with a “treasure chest” of tools and infrastructure

Between EDOC & ebXML we are covering B2B and intra enterprise

EDOC Component Collaboration Architecture The model of collaborative

work

The Marketplace Example

Mechanics Are UsBuyer

Acme IndustriesSeller

GetItThere FreightShipper

Order

Conformation

Ship Req

Shipped

Shipped

PhysicalDelivery

Delivered

Status

ProcessComplete

The Seller’s Detail

Order

Conformation

Shipped

Ship Req

Shipped

Delivered

Order Processing

Shipping

Receivables

Event

Parts of a CCA Specification

Structure of process components and protocolsProcess components, ports, protocols and documents

Class Diagram or CCA Notation

Composition of process componentsHow components are used to specify components

Collaboration diagram or CCA Notation

Choreography Ordering of flows and protocols in and between process components

Activity Diagram

The Community Process

Identify a “community process”, the roles and interactions

Buyer Seller

BuySell CommunityProcess

Buy Sell

Shipper

ShipDelivery

ShipDelivery

Protocol

Protocol OrderBT

OrderDenied

OrderConfirmationOrder

responderRoleSeller

initiatorRoleBuyer

Protocols

<<initiates>> Order

<<responds>> OrderDenied <<responds>> OrderConfirmation

Failure Success

Composition

ECA Entity Profile

The model of things

Data Inside a “shared domain”

Adding Entities

Entities are added to manage entity data

Entity Roles are managers that provides a view of the same identity in another context

The Entities have ports for managing and accessing the entities

Non-entities which are owned by (aggregate into) an entity are managed by the entity

+Street : String+City : String+State : String+Zip : String

«EntityData»Addtress

+Cust

1

+Adr

1..*

+Name : String+Balance : Decimal = 0+AccountNo : long

«EntityData»Account

+AccountNo : String

«Key»AccountKey

-.

1

-.

1

+Name : String-CompanyId : String

«EntityData»Company

+CompanyId : String

«Key»CompanyKey

-.

1

-.

1

.Manages

<<Entity>>CompanyManager

Manage

<<EntityRole>>AccountManager

Manage

-Manages1

-.1

ECA Business Events

The model of when…

Loosely coupled integration within the enterprise and with “aligned” business

partners

Business Process

Business Entity

BusinessRules

Business Events

Business Actions

Business Process

Business Entity

BusinessRules

Business Events

Business Actions

Event Based Business Processes

Event Notification

App

Business Process

Business Entity

BusinessRules

Business Events

Business Actions

App

Business Process

Business Entity

BusinessRules

Business Events

Business Actions

App

Business Process

Business Entity

BusinessRules

Business Events

Business Actions

App

Business Process

Business Entity

BusinessRules

Business Events

Business Actions

Point to point Event Notification

Event Notifications

App

Business Process

Business Entity

BusinessRules

Business Events

Business Actions

App

Business Process

Business Entity

BusinessRules

Business Events

Business Actions

App

Business Process

Business Entity

BusinessRules

Business Events

Business Actions

App

Business Process

Business Entity

BusinessRules

Business Events

Business Actions

Pub/Sub

Pub/Sub Event Notification

Event Example

Vision

Building and adapting systems for collaboration, reuse and change

Business Component Marketplace

The business component marketplace is projected to be a 10b market in 5 years

Consider the value of XML components that wrap popular legacy

New application functionality built from components

Components for integration and transformation

XML and web services makes an excellent basis for such components

Technology components, such as for repositories and DBMS

Marketplace my be inside the enterprise or commercial

OMG Model Driven Architecture (MDA)

High level – platform independent models

Technology Models

MappingCustom

Standard

Standard Models produce technology specific standards artifacts

Automated MDA

ProfileProfile(E.G. EDOC)(E.G. EDOC)

Framework &Framework &InfrastructureInfrastructure

(E.G. XML)(E.G. XML)

InfrastructureInfrastructureMappingMapping

(E.G. XML)(E.G. XML)

Mapping is tunedMapping is tunedto the infrastructureto the infrastructure

ToolsToolsProduce &Produce &IntegrateIntegrate

EnterpriseEnterpriseComponentsComponents

UMLUMLDesignDesign

Technology Independence

BusinessLogic

ComponentebXml

BusinessLogic

ComponentBizTalk

BusinessLogic

ComponentRosetaNet

BusinessLogic

ComponentEjb

Adapters

EJB

BusinessLogic

Component

ebXml

BizTalk

Rosetanet

Adapters

CICS

EJB

MQ

Corba

Iterative Development

Build Build Build Build BuildRelease

Build Deploy

BusinessModelDesign

InfrastructureDevelopment

Automation

High level tooling & infrastructure

MUST BE SIMPLE!We must be able to create better applications faster

We must separate the technology and business concerns, enable the user

Tooling + InfrastructureExecutable models are source code

Tooling must be technology aware

Infrastructure must support tooling, not manual techniques

Model based component architectures

High level tooling & infrastructure

MUST BE SIMPLE!We must be able to create better applications faster

We must separate the technology and business concerns, enable the user

Tooling + InfrastructureExecutable models are source code

aTooling must be technology aware

Infrastructure must support tooling

Model based component architectures

Executable Models

Net effect

Using these open standards and automated techniques we can;Achieve the strategic advantage of an open and flexible enterpise

Produce and/or integrate these systems FASTER and CHEAPER than could be done with legacy techniques

Provide a lasting asset that will outlive the technology of the day

Typical Requirement

B2BBuyer

WebService Seller

BuyerWeb Page

HTML Seller

B2BBuyer

Multi-tier implementation

BuyerWeb Page

HTMLBuyerProxy

WebService Seller

Could havemultiple

implementationsusing differenttechnologies

Could havemultiple

implementationsusing differenttechnologies

LegacySeller

Applications

Event Cloud

B2BBuyer

Multi-tier implementation

BuyerWeb Page

HTMLBuyerProxy

WebService Seller

EventEvent

Implementing sellerusing events

Model Driven Architecture

Automating Design To execution

MDA Overview

Use high level UML models made precise with profiles

With technology specific mappings

To produce substantial parts of the executable system

Models and mappingSpecification

Implementation

Solution Provisioning

BXS

mapPlatform-specificartifacts (IDL/DTD)

PlatformIndependent

Model

Versionedrepository

BusinessModel

•UML/CORBA•UML/EJB•XML

•OAG•SOAP•ebXml•RosettaNet

•Legacy

ManagementOver Time

Model to Deployed Artifacts

Map source

Automated platform-specific process

object

module

application

runtime

compile

package

assemble

deploy

Supplier-Specific artifacts

overrides

Process control parameters

•Configure map•Select Tools•Locate Resources

•Platform-specific•Process steps•artifacts

Generated Artifacts

Implementation Artifacts (EJB Examples)

Java Source

Class Objects

Stubs, Skeletons,Helpers, Holders,

Interfaces

Jars,Wars,Ears

BeanInfo,Editors..

Business ObjectImplementation

Logic

Homes,Managers,

Primary Keys

SQL

Descriptors

Documentation

M0/M1 XMI/DTD

Serialization,Persistence

Management

Artifact generation involves multiple tools•EJB Container provider;Deployment tools;Packagers; •java development tools(IDE);persistence provider;…Typical 10-20 per PIM Classifier0-20% manual override

PIM

Reverse Engineering

modelnavigation

process

disposition

algorithms

Production ruleengine

Native artifacts

•Native meta-model is platform-specific

•XML DTD/Schema; java introspection; SQL tables; legacy model; etc.

•Map navigates the native meta-model, populates PIM

•Limited semantic recovery

•Information and middleware models work best

MDA and ComponentsSpecification

Implementation

Solution Provisioning

BXS

PlatformIndependent

Model

BusinessModel

DirectExecution

Components

Summary of MDA benefits

Isolates domain specifications from platform detailsReduces complexityPreserves domain model semanticsIncreases stability and lifetimeGenerates to platform/legacy of choice

Decreased development timefast iterative developmentseparation between the engineering and business requirements

Increased quality. Builds on industry directions

DomainDomainSpecificationsSpecifications

MDAMDA

UsersUsers

Goal

Understand human mind.Difficulty

Minds are unobservable

Minds differ human from other animals. It is not comfortable to make research on it.

BenefitsHelp us understand ourselves more

Help to write software requirement specifications.

What is mind?

Cognitive Science hopes to explain mind in terms of low-level neural events.Measure electrical and chemical changes in the brain as it performs various

tasks

Explain mind in terms of such things as synaptic dynamics and brain modularity

Authors attack this approach as ridiculous as predicting the weather based on the known behavior of gas molecules.

My different thoughts

What is mind? - 2

Social-psychological science tries to explain mind in terms of social interactions.Minds come from evaluating, comparing, and imitating one another, from

experience and emulating the success behaviors of others.My different thought.

How to explain inventions, such as integral, relativity theory.

Wolfram secludes himself for 10 years to write the book

Assertions

Minds are socialHuman intelligence results from social interaction

Culture and cognition are inseparable consequences of human sociality. Culture emerges as individuals become more similar through mutual social learning.

What is the relation between society and culture?

Particle swarms are a useful computational intelligence(soft computing) methodology.

Social learning Theory: Bandura

Arisen out of reinforcement theories of behaviorism

Human is different from other animals. Human can learn skills and behaviors by observations

Remnant of reinforcement theory: people are more likely to imitate models whose behavior is rewarded

Why do so many criminals do the same crimes shortly after they are released from prisons?

Social learning theory: more

Two advantages:Information

Punishments are more impressive than rewards

Motivation

SourcesOwn experience

Other’s experiences (vicarious experience)

Formation of culture

Spread of influence

When the influence reaches enough people, a culture is born

What is culture?Kroeber, A.L., & Kluckhohn, C. (1952). Culture: A critical review of concepts

and definitions 161 variation of culture definition was listed." Culture consists of patterns, explicit and implicit, of and for behavior acquired

and transmitted by symbols, constituting the distinctive achievements of human groups, including their embodiments in artifacts; the essential core of culture consists of traditional (i.e. historically derived and selected) ideas and especially their attached values; culture systems may, on the one hand, be considered as products of action, and on the other as conditioning elements of further action."

Culture’s influence on individuals

Individuals’ reasoning depends on their cultureExplanations on the different history of science in China and The West.

Different reasoning styles:

Reasoning styles in China and the west

China West

Principle of Change:Reality is a dynamical, constantly-changing process. The concepts that reflect reality must be

subjective, active, flexible.

Law of IdentityEverything is what it is. Thus it is a necessary fact that A equals A, no matter what A is

Principle of ContradictionReality is full of contradictions and never clear-cut or precise. Opposites coexist in harmony with one another, opposed but connected

Law of NoncontradictionNo statement can be both true and false.

Principle of RelationshipTo know something completely, it is necessary to know its relations, what it affects and what affects it.

Law of the Excluded MiddleEvery statement is either true or false. There is no middle term.

Human behavior 1: Group Polarization

Risky shift Phenomenon Old belief: Groups make more conservative choices that individuals.Experiment result: Group decisions are more extreme than individual decisions. The individuals really changed their views after group discussions.

Caution Shift phenomenon was found later.Group Polarization:

Groups tend to exaggerate the opinions of the individuals.

Question: Do we need to change the jury system?

Explanation of Group Polarization

Persuasive argumentIndividuals change their views because they are exposed to a greater

number of arguments in favor of one position

Normative argumentIn order to get other members’ recognition or approval, individuals tend to

shift their view towards the extreme.

Particle swarm theoretical argumentSocial learning and influence tends to make individuals to try more extreme

positions to get optimized results.

Human behavior 2: Self-Esteem

People tend to seek behaviors and situations that help them value themselves positively and to avoid those that make them feel bad about who they are.

High self-esteem helps the individual deal with stress and other negative emotions and improves their confidence and persistence to achieve their goals

Low self-esteem makes the individual depressed and less confident and easy to give up their efforts.

Explanation of self-esteem

Self-esteem is a measure of how well the individuals are accepted by their social group.

Self-esteem can facilitate the maintenance of social groups

People do not have the need to maintain self-esteem itself; instead, they have the need to be included in the social group

Human behavior 3: Self-attribution and social illusion

Common belief: people have direct, immediate knowledge of our thoughts and feelings

People make attributions about themselves on the basis of the same kind of information they used to interpret the action of others (Daryl Bem)

Schachter and Singer’s “misattribution” paradigm.What would happen if the subjects know the effect of those drugs?

Nisbett and Wilson’s self-report experimentPeople are sometimes unable to report their own mental process because they are

not aware of how they think.

Computer intelligence

Particle swarm computing.Imitating human society.

Every particle can be considered as a person and particles interact with each other.

According to the social learning theory each particle is constantly watching the particles around it to see how they are doing and adjust its behavior accordingly. (people can learn by observation)

Each particle also has a memory of its behavior history. (people can learn from their own experiences)

Soft computing: Research Areas

Evolutionary algorithms and genetic programming

Neural science and neural network systems

Fuzzy set theory and fuzzy systems

Chaos theory and chaotic systems

Soft computing: attributesHard computing requires programs to be written; soft computing can evolve its

own programs

Hard computing uses two-valued logic; soft computing can use multivalued or fuzzy logic

Hard computing is deterministic; soft computing incorporates stochasticity

Hard computing requires exact input data; soft computing can deal with ambiguous and noisy data

Hard computing is strictly sequential; soft computing allows parallel computations

Hard computing produces precise answers; soft computing can yield approximate answers

slide 1 business modelling: omg - edoc bringing together business goals, standards, processes and...

Documents

integration slide

e slide

business modelling

object computing slide

business process collaboration

net instance data slide

enterprise ei b2b

open standards