Modeling interorganizational business processes

1
Modeling inter-organizational business processes
UN/CEFACT's Modeling Methodology and UN/CEFACT's
Core Components
Rainer Schuster Studio Digital Memory
Engineering
2
Why business process modeling?

• Combining two worlds of SOA
• invitation for a dialogue between e-business
  world and geo-spatial world
• finding commonness
• reference architectures, intersections between
  different domains etc.
• our contribution
• business process standards and business
  information standards from a major international
  standardization initiative

3
Business process classification
G2G
Government
G2C
B2G
Business
Citizen
C2C
B2B
B2C

• Business-to-Business (B2B)
• common business processes e.g. request geo data
  from geo data provider
• often no long term relationships established
• need for a flexible and scalable architecture
• Business-to-Government (B2G)
• should work like B2B
• e.g. Waste Management, Governmental Aids,
  Financial Services

4
We are going to talk about
UN/CEFACTs Modeling Methodology (UMM) Core
Components
5
UN/CEFACT United Nations Center for Trade,
Facilitation and Electronic Business
1970
1980
1990
2000
2010
6
UN/CEFACTs Modeling Methodology (UMM)

• Customizing UML for modeling B2B
• Independent of the IT platform, concentrates on
  business semantics
• Describes a choreography from a global
  perspective
• UML Profile Stereotypes, Tagged Values,
  Constraints on top of the UML Meta Model
• 40 stereotypes defined in the meta model

UMM
BDVBusiness Domain View
BRVBusiness Requirements View
BTVBusiness Transaction View
7
UMM by example - BTV
30. Oktober 2009
ltltmapsTogtgt
BTUC
ltltmapsTogtgt
BCUC
7
8
Advantages through the usage of UMM

• Capture the requirements of an inter-organizationa
  l business process from a global perspective
• Establish a common UML based model describing the
  business process
• Use the model to automatically derive machine
  executable code (BPEL or BPSS) for a service
  oriented architecture (SOA)
• add core component logic (business information)

UMM-Model
Business Partner A
Capture Requirements
Automatically derive
use in
Service Oriented Architecture
BPEL BPSS
ltXMLgt
Business Partner B
Core Components
9
Standardizing the exchanged data
Exporter
Importer
announce waste transport
WSDL
WSDL
SOAP message
announce transport arrival
Enterprise Application
Enterprise Application
WSDL
SOAP message
check waste status
WSDL
WSDL
SOAP message
UDDI registry
10
Standardizing the exchanged data
Exporter
Importer
announce waste transport
WSDL
WSDL
SOAP message
SOAP Message
announce transport arrival
Enterprise Application
Enterprise Application
SOAP Header
WSDL
SOAP message
SOAP Body
Message Body
check waste status
WSDL
WSDL
SOAP message
UDDI registry
11
Core Components

• Problem domain
• Information exchanged in business processes in a
  service oriented context
• UN/CEFACT provides a generic solution
• Core Components Technical Specification (CCTS)
• Almost no tool support possible - CCTS are
  standardized as spread sheets
• UML profile for core components
• Seamless integration into UML modeling tools
  possible
• Seamless integration into e.g. process specific
  models possible (UMM)
• ARC are actively participating in the
  standardization

12
Core Components

• Are the central building blocks of the Core
  Component Technical Specification (CCTS)
• Platform independent
• Used to create shared libraries of interoperable
  business documents
• The ontological base of the CCTS is the United
  Nations Trade Data Element Dictionary (UN/TDED)
• Initially started as part of ebXML standards
  suite
• Now a dedicated project independent of ebXML

13
A Core Component Example
14
Business Information Entities
15
Interdependency between Core Components and
Business Information Entities
Core Components (CC)
Business Information Entities (BIE)
BIEs are derived from CCs by restriction
16
Derivation of XSD artifacts
UN/CEFACTNaming and Design Rules
Business Information Entities (BIE)
ltxsdcomplexType name"Waste_MovementForm"gt
ltxsdsequencegt ltxsdelement name
"TransportNumber" type"udt1IdentifierNumber"/gt
ltxsdelement name"IdentificationNumber"
type"udt1IdentifierNumber"/gt ltxsdelement
name"Waste_Transport_Period" type"bie1PeriodTyp
e"/gt ltxsdelement name"Waste_Movement_Transpo
rtMeans" type"bie1TransportMeansType"/gt
ltxsdelement name"Waste_Carrier_Party"
type"bie1PartyType"/gt ltxsdelement
name"Waste_Movement_TransportMode"
type"bie1TransportModeType"/gt
lt/xsdsequencegt lt/xsdcomplexTypegt
17
Conclusion Summary

• We showed how
• UMM can be used to model inter-organizational
  business processes
• the UML Profile for Core Components can be used
  to model the information exchanged in an
  inter-organizational business process
• the UMM Add-In developed by ARC supports the
  modeler in modeling UMM and CCTS
• we expect that a dialogue between the geo-spatial
  and the e-business modeling initiatives could
  result in improvements and wider international
  acceptance of SOA standards

18
Thank you for your attention

• ltLecturergt
• ltNamegtRainer Schusterlt/Namegt
• ltCompanygtAustrian Research Centers - Research
  Studios Austrialt/Companygt
• ltDepartmentgtIntelligent Business Process
  Management Grouplt/Departmentgt
• ltAddressgt
• ltStreetgtThurngasse 8/20lt/Streetgt
• ltZIPgt1090lt/ZIPgtltCitygtViennalt/Citygt
• ltCountrygtAustrialt/Countrygt
• lt/Addressgt
• ltContactgt
• ltTelephonegt43 1 585 0537 12 lt/Telephonegt
• ltEmailgtphilipp.liegl_at_researchstudio.atlt/Emailgt
• ltEmailgtrainer.schuster_at_researchstudio.atlt/Emailgt
  
• ltHttpgthttp//ummaddin.researchstudio.atlt/Httpgt
• lt/Contactgt
• lt? Presentation statusquestions ?gt
• lt/Lecturergt