Transcript Document 7117008

VIENNA Add-In
Philipp Liegl
Michael Strommer
Research Studio Inter-Organisational Systems
Project Public Private Interoperability
Whoami?
Agenda
• Introduction
• UN/CEFACT's Modeling Methodology
• UN/CEFACT's Core Components
• VIENNA Add-In
• Q&A
B2C – Client-Server Computing
HTTP request
Messaging Layer
HTTP response
Presentation Layer
Business Layer
Databases
ERP Systems
Persistence Layer
Client
Web
Application
Server
Legacy Applications
B2B Application Computing
B2B Application Server
SOAP request over
Messaging Layer
HTTP, SMTP, ...
Document Layer
Common Document Logic
Business Layer
Databases
ERP Systems
Persistence Layer
B2B Application Server
Common Process Logic
…
Messaging Layer
Document Layer
Business Layer
Databases
ERP Systems
Persistence Layer
…
UN/CEFACT‘s Core Components Technical Specification
UN/CEFACT's Modeling Methodology
UN/CEFACT =
United Nations Center for Trade Facilitation and
Electronic Business
6
The United Nations and
e-Business?
• To maintain international
UN Layout Key
peace and security
UN/EDIFACT
• To develop friendly relations
among nations
• To achieve international cooperation
ebXML
UMM/CC
Business Transactions
open-EDI reference model
From Conceptual Models to Deployment Artifacts
Business Operational View
Business aspects
of business transactions
comply
with
covered
by
viewed
as
UN/CEFACT's Modeling
Business
Methodology
Operational
(UMM)
View
Core
related
Components
standards
Technical Specification
(CCTS)
transformed
to
Functional Service View
Information technology
aspects of business
transactions
comply
with
covered
by
UN/EDIFACT
Functional Service
Web Services
View
Windows Workflow
related standards
…
Business Transactions
open-EDI cont'd
Business Operational View
Business aspects
of business transactions
comply
with
covered
by
viewed
as
UN/CEFACT's Modeling
Methodology (UMM)
Core Components
Technical Specification
(CCTS)
transformed
to
Functional Service View
Information technology
aspects of business
transactions
comply
with
covered
by
UN/EDIFACT
Web Services
Windows Workflow
…
Requirements for Interoperability
between Different Enterprises
• How to exchange?
• Define in which order business documents are
exchanged (global process choreography)
• Solved by UN/CEFACT's Modeling Methodology (UMM)
• What to exchange?
• Define which information artifacts are exchanged and
how they are structured
• Solved by UN/CEFACT's Core Components Technical
Specification (CCTS)
How to Define a Global Business Process
Choreography?
UN/CEFACT's Modeling Methodology (UMM) at a
Glance
• 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
• UMM is defined as a UML profile on top of UML 2
• UMM is used in order to define global business choreographies
Now – What’s a Global Choreography?
• If each organization defines its own choreography with business
partners, interoperability is unlikely
Buyer's view on collaboration
Buyer
Seller
Seller's view on collaboration
Buyer
Seller
• UMM describes collaborative business processes from a global and
neutral point of view
Collaboration
Buyer
Seller
Buyer
S
Order Product
Seller
S
Order Product
Carrier
S
Check against Offer
S
Reserve Stock
S
Reserve Production Line
Calculate Delivery Date
S
Reserve Transport
C
C
Reserve Transport
S
S
Confirm Transport
Confirm Transport
Response
To Order
Response To Order
B
B
S
S
Get Status
Get Status
Private internal service
B
Inform on Status
B
Inform on Status
S
Cancel order
S
Cancel order
S
Clear Resources
B
Notify Shipment
S
Deallocate Production Line
Publically visible service
S
Ready to ship
B
Notify Shipment
S
Transfer to
accounting
Sellers's
orchestration
of the order
management
Buyer
Seller
S
S
Order Product
Order Product
B
Response To Order
Carrier
C
C
Reserve Transport
Reserve Transport
S
S
Confirm Transport
Confirm Transport
B
Response To Order
S
Local
choreographies
S
Get Status
Get Status
B
Inform on Status
B
Inform on Status
S
S
Cancel order
Cancel order
B
B
Notify Shipment
Notify Shipment
S
Out: buyer
In: seller
Order Product
Out: seller
B In: buyer
Response To Order
Out: buyer
S In: seller
Get Status
Out: seller
B In: buyer
Inform on Status
Out: buyer
S
In: seller
Cancel order
Out: seller
B In: buyer
Notify Shipment
Global
Choreography
between Buyer and
Seller
Global Choreography using
UN/CEFACT's Modeling Methodology
«bCPartition»
«bCPartition»
:Buyer
:Seller
«initFlow»
«bNestedCollaboration»
«bTransactionAction»
«initFlow»
:Order Product
«reFlow»
«reFlow»
«bTPartition»
«bTPartition»
:Buyer
:Seller
[Order.rejected]
[Order.pending]
«ReqAction»
«ResAction»
:PurchaseOrderEnvelope
«initFlow»
«reFlow»
«initFlow»
:PurchaseOrderEnvelope
«bTransactionAction»
:Get Order Status
:PurchaseOrderPendingEnvelope
:PurchaseOrderPendingEnvelope
Control
Failure
Failure
«reFlow»
[Order.notconfirmed]
:PurchaseOrderRejectionEnvelope
«initFlow»
:PurchaseOrderRejectionEnvelope
«bTransactionAction»
:Cancel Order
[OrderPendingEnvelope
!= null]
«initFlow»
[else]
«bESharedSta...
:Order
«bESharedS...
:Order
[pending]
[rejected]
[Order.confirmed]
«bTransactionAction»
Business Success
Business
Failure
«initFlow»
:Notify Shipment
«initFlow»
:Reserv e Transport Collaboration
What Kind of Business Information
Artifacts are Exchanged?
Multiple Interactions between Different
Market Participants
Company A
Company B
Company C
Company D
Company E
Company F
Company G
Company H
How Serious is the Problem?
20
Core Components at a Glance
• Semantic building blocks
• Reference data models
• Messages
• Based on a common semantic basis
• Core Component Library
• Implementation neutral
• One general model – derivation for specific contexts
• Started as part of the ebXML standard
• Today an independent UN/CEFACT project
Core Components in One Slide
• Identification of objects
Order
ACC
• Identification of properties of objects
Order
ASCCItem
• Two kinds of properties
• Simple properties (text, number, date)
• Complex properties (other objects)
Item
ACC
- Part
BCCnumber
• Object type
=
Aggregate Core Component
• Simple Property
=
Basic Core Component
• Simple Property Data Type
=
Core Data Type
• Complex Property
=
ASociation Core Component
22
Adding Context – Business Information Entities
• Core components in a specific business context
• Qualifiers help to differentiate BIEs
US_Person
ABIE
• Two kinds of properties
ASBIE
private_address
• Simple properties (text, number, date)
• Complex properties (other objects)
•
•
•
•
Object type
Simple Property
Simple Property DT
Complex Property
=
=
=
=
US_Address
ABIE
-- Street
BBIE
Aggregate Business Information Entity
Basic Business Information Entity
Business Data Type
ASociation Business Information Entity
23
«signal»
Dependency
between
Signal1
Core Components and Business Information Entities
«ACC»
Person
«ABIE»
US_Person
basedOn
«BCC»
+ DateofBirth: Date
+ FirstName: Text
«BBIE»
+ DateofBirth: Date
+ FirstName: Text
«ASBIE»
«ASCC»
basedOn
+Private
«ASCC»
«ACC»
Address
«BCC»
+Work + Country: CountryCode
+ PostalCode: Text
+ Street: Text
+ and 20 more attributes
+US_Work
«ASBIE»
basedOn
+US_Private
«ABIE»
US_Address
«BBIE»
+ PostalCode: PostalCodeType
+ Street: Text
basedOn
BIEs are derived from CCs by restriction
«signal»
Signal2
A UML Profile for Core Components
(UPCC)
• Major flaw of Core Components
• missing formalized representation model
• no direct integration into modeling tools possible
• UPCC goals
• Map technology independent core component concepts to UML
• Set of stereotypes, tagged values, and OCL constraints
• Easy integration in UML case tools
• Implementation for Enterprise Architect
•
http://www.umm-dev.org
Visualizing Inter ENterprise Network Architectures
VIENNA Add-In
UMM (UN/CEFACT’s Modeling
Methodology)
UPCC (UML Profile for Core
Components)
o UML Profile definition
o UML Profile definition
o Model validation
o Model validation
o Deployment artifact
generation (XML Schema)
o Automated model structure
generator
o Generation of deployment
artifacts (BPEL) - in progress
o Model-artifact creation
wizards
o Core Component Library
import
http://vienna-add-in.googlecode.com
Tool Support for
Business Document Engineering
My
Library
Modeling with
custom Library
UN/CEFACT
Library
VIENNA AddIn
Transform
Modeling with
standardized
Library
DocModel
A
DocModel
B
DocModel
C
Generate
XML
Schema
B
Import
XML
Schema
C
VIENNA Add-In at a Glance
Thank you for your Attention!
<Lecturer>
<Name>Philipp Liegl</Name>
<Company>Vienna University of Technology</Company>
<Email>[email protected]</Email>
<Url>http://www.umm-dev.org</Url>
</Lecturer>
<Lecturer>
<Name>Michael Strommer</Name>
<Company>Research Studios Austria</Company>
<Email>[email protected]</Email>
</Lecturer>