University of Vienna, Institute of Distributed and Multimedia Systems Christian Huemer Institute of Distributed and Multimedia Systems Liebiggasse 4/3-4,

University of Vienna, Institute of Distributed and Multimedia Systems

Christian HuemerInstitute of Distributed and Multimedia Systems

Liebiggasse 4/3-4, 1010 WienTel. +43-1-4277-38443 Fax [email protected]://www.cs.univie.ac.at/christian.huemer

Introduction to UN/CEFACT’s Modeling Methodology


The rest of all Business that should be exchanging information electronically

FORTUNE 10000

(1000 in the top 10 Economics)

95%

5%

Using EDI

EDI Capable

2%

98%

Is There a Problem?

Did EDI reach critical mass after 20+ years?


A

B

CD

E

A

B

CD

E StandardFormat

Standard:

MIGPartner-specificStandard

MIGUser Group

MIGCompany

Message Implementation Guide (MIG):

Traditional B2B Approaches


Commercial Off-The-Shelf Software

SMEs need Commercial Off-The-Shelf Software (COTS) that are a combination of ERP systems and B2B software for communication

ERP vendors must implement common B2B scenarios in their products

This requires unambiguous business processes instead of ambiguous business documents

Business processes must be defined in their business context


Business Process

Define a choreography Business State Centric

What kind of apples do you have?

We provide 5 alternatives: .....

What is the price of the 2nd and 4th option?

The 2nd is x$ and the 4th is y$

I take 5 pieces of the second option

Fine.


BusinessRequirements

TechnologyImplementation

Requirements vs. Technology

Interactions

Data


Open-edi: Seperation of business logic and IT

Business aspectsof

business transactions

Information technologyaspects of

business transactions

BOV

FSV

BU

SIN

ES

S C

OLL

AB

OR

AT

ION

BOV relatedStandards

FSV relatedStandards

viewedas

comply with

comply with

covered by

covered by

transformed to

BOV relatedStandards

UMM

FSV relatedStandards

ebXMLWebServices


UN/CEFACT´s Modelling Methodology (UMM)

UML-based description technique for describing B2B scenarios

Concentrates on business semantics UMM Meta Model (UML Profile) Provides a procedure similar to the first steps of a software

development process

BDVBusinessDomain

View

BRVBusiness

RequirementView

BTVBusiness

TransactionView

BSVBusiness Service

View

BOVBusiness Operational View


UMM is based on UML

Use Case

Actor 1

Actor 2

Requirement Gathering

Use CaseDiagram

Activity 1

Activity 2

ChoreographyActivityGraph

InformationStructures

ClassDiagram

RegistrationRequest

DocumentID : IdentifierTypeDocumentCreationDateTime : DateTimeTypeResponseByDateTime : DateTimeType

<<BusinessInformation>>

CustomerInformation<<BusinessEntity>>

Address

...

<<BusinessObject>>

Party

+ LegalName : TextType+ ShortName[0..1] : TextType+ OfficialRegistrationID : IdentifierType+ OfficialRegistrationAuthorityCode : CodeType

<<BusinessObject>>

+Customer

+Billing 0..1+Shipping

0..1

Account

BankID : IdentifierTypeID : IdentifierTypeTypeCode : CodeTypeHolder : TextTypeBalanceValue : NumericTypeEndDateTime : DateTimeType

<<BusinessObject>>

1..n1..n

+CreditCard


UMM Terminology

Business Process Group of related activities that together create customer value Traditionally intra-organizational, but also inter-organizational

Business Collaboration Performed by two business partners (=binary collaboration) or

more business partners (=multi-party collaboration) Complex, composed of many activities (=business transactions)

between the partners

Business Transaction Always a binary collaboration Unit of work allowing roll back to a defined business state Realized by a request from one side and an optional response

from the other side


Relevant UMM Artefacts

Business Collaboration Protocol Use Case

Use Case

Business Collaboration Protocol

Activity Graph

Business Transaction Activity

Activity

Business Transaction Use Case

Use Case

Business Transaction

Activity Graph

Business Action (Initiating/Reacting)

Activity

1

1

n

n

1

1

1

1

1

2

desribes choreography for

is composed of

Is refined by

desribes choreography for

is composed of


Business Requirements Specification (BRS)

1. Objective2. Scope3. Business requirements

1. “Business requirements” views1. Business process elaboration2. Information flow definition3. Information model definition

2. Business rules3. Definition of terms

Categories

Business Process

Product Classification

Industry Classification

Geopolitical

Official Constraint

Business Process Role

Supporting Role

System Capabilities

Use cases,worksheets

Activity, sequence,

collaboration diagrams

Class diagrams

Rules relative to information

model


Business Domain View (BDV)

Identify the business processes in the domain of the business problem that are important to stakeholders intra-enterprise processes business collaborations, i.e. inter-enterprise processes

Business process are discovered, not constructed Business processes are classified according to a

classification schema Porter`s Value Chain SCOR (Supply Chain Operations Reference Model) UN/CEFACT Catalog of Common Business Processes

(under development)


Acquire product

Retailer Sell product Wholesaler

Order Management

Business Collaboration Use Case

…

Organize Transport

Find product

Sell product

Ship product

Provide Catalogue

…

Acquire product

Transporter


Business Requirements View (BRV)

Identifies possible business collaborations

for possible business collaborations

Depends on the business processes of the BDV

Describes how the business domain expert sees and describes the process to be modelled

Captures use case scenarios, inputs & outputs constraints system boundaries

Uses worksheets to describe the use case for a business collaboration


BC Worksheet


Business Collaboration Decomposition

PresentReservedProducts

Customer Seller

<<BusinessTransactionUseCase>>

SearchProduct


RegisterCustomer


ReserveProduct


OrderProduct


OrderManagement

<<BusinessCollaborationProtocolUseCase>>

<<include>>

<<include>>

<<include>>

<<include>>

<<include>>


Business Transaction View (BTV)

Presents the view of the business process analyst

Models the business collaboration Defines a choreography for the business collaboration The business collaboration protocol is an activity graph Each activity in a business collaboration protocol is an

interorgranizatonal activity = business transaction activities

Details each business transaction activity Defines the semantics of an business information exchange between

partner roles A business transaction is an activity graph The business transaction follows one out of six patterns

Models the business information exchanged The business information exchanged is modelled in a class diagram. It should contain all necessary information to transfer the effected

business entity (or entities) from one state to the other; It should not contain any information not needed for business state

changes

<<BusinessTransactionActivity>>

request for quote


register customer<<BusinessTransactionActivity>>

order product

[NOT Product.Ordered]

[NOT Product.Quoted]

[Product.Quoted]

[Product.Ordered]

PurchaseOrderManagement.BusinessFailure

[NOT CustomerInformation.Confirmed] [CustomerInformation.Confirmed]

[CustomerInformation.Confirmed]

[CustomerInformation.Rejected]

PurchaseOrderManagement.BusinessSuccess

timeToPerform: 24 hrsisConcurrent: true

timeToPerform: 48 hrsisConcurrent: true

timeToPerform: 12 hrsisConcurrent: false

PurchaseOrderManagement.BusinessFailure

<<BusinessCollaborationProtocol>> Purchase Order Management



Request for Quote


Register Customer<<BusinessTransactionActivity>>

Order Products

[ControlFail]

[NOT CustomerInformation.Confirmed] [CustomerInformation.Confirmed]

[CustomerInformation.Confirmed]

[ControlFail]


[Con

tro

l Fai

l]

[Suc

cess

]

<<RespondingBusinessActivity>>

<<RequestResponse>>

: Buyer : Seller

:RegistrationRequestEnvelope

:RegistrationResponseEnveloperequest registration

perform registration

[Con

tro

l Fai

l]

[Suc

cess

]

<<RespondingBusinessActivity>>[Con

tro

l Fai

l]

[Suc

cess

]

<<RespondingBusinessActivity>><<RespondingBusinessActivity>>

<<RequestResponse>><<RequestResponse>>

: Buyer : Seller




: Buyer : Seller













changes


[Con

tro

l Fai

l]

[Suc

cess

]



<<RequestResponse>>

: Buyer : Seller

:QuoteRequestEnvelope

:QuoteEnvelopeobtain quote

calculate quote


Which Type of Business Transaction?

Is there a response required?

Select Query/

Response

Is this a formal non-reputable notification?

Select Request/ Confirm

Select Commercial Transaction

Is pre-editor context validation required before processing?Select

Information Distribution

Select Notification

Does the responder already

have the information?

Yes

Yes

Yes

Yes

No

No

No

No

Is there a residualobligation between roles

to fulfill terms of thecontract?

Select Request/Response

No

Yes

Is there a response required?

Select Query/

Response

Is this a formal non-reputable notification?

Select Request/ Confirm

Select Commercial Transaction

Is pre-editor context validation required before processing?Select

Information Distribution

Select Notification

Does the responder already

have the information?

Yes

Yes

Yes

Yes

No

No

No

No

Is there a residualobligation between roles

to fulfill terms of thecontract?

Select Request/Response

No

Yes


Requesting Activity Property Values

Tim

e toA

ckno

wled

ge

Receip

t

Tim

e toA

ckno

wled

ge

Accep

tance

Tim

e to P

erform

Au

tho

rization

Req

uired

No

n-rep

ud

iation

of O

rigin

and

Co

nten

t

No

n-rep

ud

iation

of R

eceipt

Recu

rrence

CommercialTransaction 2hrs 6hr 24hr true true true 3

Request /Confirm null Null 24hrs false false true 3

Request /Response null Null 4hrs false false null 3

Query /Response null Null 4hrs false false null 3

Notification 24hrs Null 24hrs false true true 3

InformationDistribution null null 24hrs false false false 3


[Con

tro

l Fai

l]

[Suc

cess

]


<<RequestResponseActivity>>

Initiating Role : Buyer Reacting Role: Seller

:QuoteRequestEnvelope

:QuoteEnvelopeobtain quote

calculate quote

isConfidential: NoisTamperProof: NoisAuthenticated: No

isConfidential: YesisTamperProof: YesisAuthenticated: Yes

isAuthorizationRequired: falseisNonRepudiationRequired: falsetimeToPerform: 4 hrstimeToAcknowledgeReceipt: nulltimeToAcknowledgeAcceptance: nullisIntelligibleCheckRequired: trueisNonRepudiationOfReceiptRequired: falseretryCount: 3

timeToPerform: 4 hrstimeToAcknowledgeReceipt: 2 hrstimeToAcknowledgeAcceptance: nullisIntelligibleCheckRequired: trueisAuthorizationRequired: falseisNonRepudiationRequired: false

Business Transaction: Request for Quote










changes


Business State Centric

Business Collaborations are about managing a shared view on Business States.

Aligning Business States between business partners requires exchange of Business Information.

Business Information is limited to the information required to change the state of one or more Business Entities affected by the exchange.

Business Documents also have the potential to change the state of a business entity. However, business documents do not concentrate on what is needed to change the state, and thus, include a lot of unnecessary data.

Each element included in a business document exchange is a source for incompatibility.

Limit the Business Information exchange to an absolut minimum, i.e. the information required to change the State of a Business Entity.


QuoteIDQuoteDate

Quote QuoteRequest

QuoteRequestID

Line

LineNumber

LineQuote

UnitPrice

Book

ISBNTitleAuthors

<<references>>

0..n

1

1

1n

1

Business Document: Quote


Business Document: Quote based on ABIEs


<Thanks/>

<Lecturer><Name>Christian Huemer</Name><Company>University of Vienna</Company><Dept>Institute of Distributed and Multimedia Systems</Dept><Address>

<Street>Liebiggasse 4/3-4</Street><ZIP>1010</ZIP><City>Vienna</City><Country>Austria</Country>

</Address><Contact>

<Telephone>+43-1-4277-38434</Telephone><Email>[email protected]</Email><Http>www.cs.univie.ac.at/christian.huemer</Http>

</Contact><? Presentation status=“questions” ?>

</Lecturer>

University of Vienna, Institute of Distributed and Multimedia Systems Christian Huemer Institute of Distributed and Multimedia Systems Liebiggasse 4/3-4,

Documents

university of vienna

multimedia systems liebiggasse

business context slide

multimedia systems openedi

seperation of business

unambiguous business

b2b software

combination of erp systems