[PPT] - Technical Framework Technical Framework Technical Framework PowerPoint Presentation

SLIDE 1

Christian Huemer TMG Chair

Technical Framework Supporting eBusiness Standards Technical Framework Technical Framework Supporting Supporting eBusiness eBusiness Standards Standards

SLIDE 2

Requirements for interoperability between enterprises

2

Which documents are exchanged between enterprises?
Common definition of the artifacts which are exchanged between

enterprises

Business document standards
CCTS, UPCC, NDR, UCM
How are documents exchanged between enterprises?
Common definition in which order documents are exchanged
Global process choreography
UMM, REA, (UCM in the future)

SLIDE 3

Meta Model sickness

3

Health warning

If you want to learn modeling, it is not a good idea to start with the meta

model

If you are an experienced modeler the meta model serves as reference
A tool builder must implement the meta model to provide the modeling

environment for the modeler

SLIDE 4

Overview of Core Component related UN/CEFACT specifications

4

Core Component Technical Specification (CCTS) UML Profile for Core Components (UPCC)

based on

Core Component Library (CCL)

conforms to use core component definitions derive

XML-Schema

Naming and Design Rules (NDR)

conforms to define unambiguous derivation rules

Core Data Type Catalogue

SLIDE 5

UN/CEFACT’s Core Components – Definition of reusable building blocks

5

Semantic building blocks for the

definition of business document data

Context free – reuse in multiple

business sectors

Customization of generic core

components to specific business sectors and application domains

SLIDE 6

UN/CEFACT’s Core Components – Reuse of building blocks

6

Core Components Business document

SLIDE 7

Creation and use of building blocks

7 Core Component Library (CCL) UN/CEFACT Company A Company C Company B Company X

SLIDE 8

Reduction of complexity through reusable document building blocks 8 Article ID Description Price Color Weight Article Article ID Description Price Color Weight Catalog_Article Order_Article Invoice_Article Contextualization by omitting non-used elements

SLIDE 9

Core components in one slide

9

Identification of objects
Identification of object properties
Two types of properties
Simple properties (text, number, date)
Complex properties (other objects)
Object type

= Aggregate Core Component

Simple Property

= Basic Core Component

Simple Property Data Type

= Core Data Type

Complex Property

= ASociation Core Component

LineItem Article

item

ACC ACC

ASCC
BCC
BCC
ArticleNumber
BCC
Number
BCC
BCC
Description
Price
Color
Weight
BCC
BCC
Amount

Text Quantity : : : : : : : Text Text Amount Text Quantity CDT CDT CDT CDT CDT CDT CDT

SLIDE 10

From Core Components to Business Information Entities

10

Core Components act as conceptual models that are used to define

business information entities (BIE)

Business Information entities are created
by the application of context
by restricting a generic core component
Business Information Entities and Core Components are

complementary in many respects

A Business Information Entity must always be based on a Core

Component Core Component Business Information Entity

based on

SLIDE 11

Business Information Entities in one slide

11

Core Components in a specific context
Qualifiers help to distinguish BIEs
Two different type of properties
Simple properties (text, number, date)
Complex properties (other objects)
Object type

= Aggregate Business Information Entity

Simple Property

= Basic Business Information Entity

Simple Property DT

= Business Data Type

Complex Property

= ASociation Business Information Entity

LineItem Article

item

ABIE ABIE

ASBIE
BBIE
BBIE
Chemical_ArticleNumber
BBIE
Number
BBIE
BBIE
Description
Price
Amount

Text Quantity : : : : : Text Text Amount BDT BDT BDT BDT BDT

SLIDE 12

Overview of Core Component related UN/CEFACT specifications

12

Core Component Technical Specification (CCTS) UML Profile for Core Components (UPCC)

based on

Core Component Library (CCL)

conforms to use core component definitions derive

XML-Schema

Naming and Design Rules (NDR)

conforms to define unambiguous derivation rules

Core Data Type Catalogue

SLIDE 13

A UML Profile for Core Components (UPCC)

13

UPCC goals
Define UML Profile for CCTS to allow for an unambiguous

representation of Core Components in UML

Support validation of structure and semantics of CCTS compliant

information models

Provide an unambiguous basis for the derivation of XML Schema

artifacts

Make CCTS information modeling available to a broad user

community

Help to improve model interchange between UML tools of different

vendors

SLIDE 14

Overview of Core Component related UN/CEFACT specifications

14

Core Component Technical Specification (CCTS)

UML Profile for Core Components (UPCC) based on

Core Component Library (CCL)

conforms to use core component definitions derive

XML-Schema Naming and Design Rules (NDR)

conforms to define unambiguous derivation rules

Core Data Type Catalogue

SLIDE 15

XML Schema Web Services Windows Workflow … UN/CEFACT's Modeling Methodology (UMM) UML Profile for Core Components (UPCC) Functional Service View related standards Business Operational View related standards The Open-edi Reference Model ISO 14662

Business Transactions

Business aspects

f business transactions

Information technology aspects of business transactions

viewed as comply with covered by covered by comply with transformed to

Business Operational View Functional Service View

SLIDE 16

Transformation concepts

16

Business Information Entity Concept XML Schema Construct

Aggregate Business Information Entity (ABIE) Association Business Information Entity (ASBIE) Basic Business Information Entity (BBIE) Business Data Type (BDT) xsd:simpleType xsd:complexType xsd:element Local Declaration xsd:complexType xsd:element Global Declaration xsd:element Local Declaration

OR

SLIDE 17

Resulting XML files

17

Root XML Schema File BDT XML Schema File BIE XML Schema File includes includes includes Aggregate Business Information Entity (ABIE) Association Business Information Entity (ASBIE) Business Data Type (BDT) Business Document Definitions Basic Business Information Entity (BBIE)

SLIDE 18

« A B I E » B I E L i b r a r y ︵ B u s i n e s s I n f

r

m a t i

n

E n t i t y L i b r a r y ︶ : : W a s t e ︳ C

n

s i g n m e n t I t e m « B B I E » + W a s t e ︳ C h a r g e a b l e W e i g h t : W a s t e ︳ M e a s u r e [ . . * ] + W a s t e ︳ D e c l a r e d V a l u e F

r

C a r r i a g e : W a s t e ︳ A m

u

n t [ . . 1 ] + W a s t e ︳ D e c l a r e d V a l u e F

r

C u s t

m

s : W a s t e ︳ A m

u

n t [ . . 1 ] + W a s t e ︳ D e c l a r e d V a l u e F

r

S t a t i s t i c s : W a s t e ︳ A m

u

n t [ . . 1 ] + W a s t e ︳ D e l i v e r y I n s t r u c t i

n

s : W a s t e ︳ T e x t [ . . * ] + W a s t e ︳ G r

s

s V

l

u m e : W a s t e ︳ M e a s u r e [ . . * ] + W a s t e ︳ G r

s

s W e i g h t : W a s t e ︳ M e a s u r e [ . . * ] + W a s t e ︳ I d e n t i f i c a t i

n

: W a s t e ︳ I d e n t i f i e r [ . . * ] + W a s t e ︳ I n f

r

m a t i

n

: W a s t e ︳ T e x t [ . . * ] + W a s t e ︳ I n s u r a n c e V a l u e : W a s t e ︳ A m

u

n t [ . . 1 ] + W a s t e ︳ I n v

i

c e : W a s t e ︳ A m

u

n t [ . . * ] + W a s t e ︳ N e t W e i g h t : W a s t e ︳ M e a s u r e [ . . * ] S O 1 « A B I E » B I E L i b r a r y ︵ B u s i n e s s I n f

r

m a t i

n

E n t i t y L i b r a r y ︶ : : W a s t e ︳ C

n

s i g n m e n t + W a s t e ︳ I d e n t i f i c a t i

n

: W a s t e ︳ I d e n t i f i e r [ . . * ] « M A » W a s t e M

v

e m e n t F

r

m « A B I E » B I E L i b r a r y ︵ B u s i n e s s I n f

r

m a t i

n

E n t i t y L i b r a r y ︶ : : W a s t e ︳ C

u

n t r y « B B I E » + W a s t e ︳ I d e n t i f i c a t i

n

: W a s t e ︳ I d e n t i f i e r [ . . * ] + W a s t e ︳ N a m e : W a s t e ︳ T e x t [ . . * ] D e f i n e d i n a D O C L i b r a r y D e f i n e d i n B I E L i b r a r y + W a s t e ︳ I n c l u d e d 1 . . * « A S B I E » + A t t a c h e d 1 . . * « A S M A » « A S B I E » + W a s t e ︳ E x p

r

t 1 « A S B I E » + W a s t e ︳ I m p

r

t a t i

n

1 « A S B I E » + W a s t e ︳ T r a n s i t . . *

Example for a business document schema

18

SLIDE 19

UCM: Modeling Dimension

The is the initial, and only, UCM specification being worked on. It is in the Modeling Dimension.

1. A Grammar (BNF) to express context values such as:
“All of Europe but not the UK”
BIEs which are relevant for Step3 in OrderToCash for partner1
Automotive industry in Germany
More – you define your values
2. Mathematical foundation based on a Directed Acyclic Graph (DAG)
3. Will specify

A UML logical metamodel for defining context values

UCM will NOT define context values such as in CCTS 2.X
UCM WILL define how to define context values via Classification

Scheme instances

SLIDE 20

Reduction of complexity through reusable document building blocks

20

SLIDE 21

Order from Quote business scenario – simple, but realistic

21

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. Buyer Seller

SLIDE 22

Principles of the UMM solution

22

Separation of business logic and implementation technology
Model-driven approach
Based on the Unified Modeling Language (UML)
Process centric
UMM is business process centric
Business state centric
Adjust UMM to a business state centric methodology
Business context sensitive
Need concepts for applying models in multiple contexts with respect to the

environment-specific requirements

SLIDE 23

UN/CEFACT's Modeling Methodology (UMM) at a glance

23

Graphical process modeling technique for inter-organizational (B2B)

business processes

Concentrates on business semantics – it is implementation neutral
Provides a procedure similar to a software development process
from requirements elicitation to process design
UMM is defined as a UML profile on top of UML 2.1.1
UMM is used in order to define global business choreographies

SLIDE 24

Global choreography

24

If each organization defines its own choreography with business

partners, interoperability is unlikely

UMM describes collaborative business processes from a global and

neutral point of view

Buyer‘s view Seller‘s view Buyer Seller Collaboration

SLIDE 25

From UMM to Exectuion

25

internal

Company A

public internal

Company B

public

UMM Modell

:Seller «bTPartition» :Buyer «bTPartition» «ReqAction» :PurchaseOrderPendingEnvelope :PurchaseOrderRejectionEnvelope :PurchaseOrderEnvelope «ResAction» :PurchaseOrderPendingEnvelope :PurchaseOrderRejectionEnvelope :PurchaseOrderEnvelope Control Failure «bESharedSta... :Order [pending] «bESharedS... :Order [rejected] Business Success Business Failure [else] [OrderPendingEnvelope != null]

rchestration
rchestration

global local local choreography

SLIDE 26

End of Presentation

26

<Lecturer> <Name>Christian Huemer</Name> <Company>Vienna University of Technology</Company> <Department>Business Informatics Group</Department> <Address> <Street>Favoritenstraße 9-11/188</Street> <ZIP>1040</ZIP><City>Vienna</City> <Country>Austria</Country> </Address> <Contact> <Email>huemer@big.tuwien.ac.at</Email> <Http>http://www.big.tuwien.ac.at</Http> </Contact> <? Presentation status=“questions” ?> </Lecturer>