300 likes | 396 Views
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.
E N D
VIENNA Add-In Philipp Liegl Michael Strommer Research Studio Inter-Organisational Systems Project Public Private Interoperability
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 Client Web Application Server Business Layer Databases ERP Systems Legacy Applications Persistence Layer
B2B Application Computing B2B Application Server B2B Application Server SOAP request over HTTP, SMTP, ... Messaging Layer Messaging Layer Document Layer Document Layer Common Document Logic Business Layer Business Layer Common Process Logic … … Databases ERP Systems Databases ERP Systems Persistence Layer Persistence Layer
UN/CEFACT‘s Core Components Technical SpecificationUN/CEFACT's Modeling Methodology UN/CEFACT = United Nations Center for Trade Facilitation and Electronic Business
UN Layout Key UN/EDIFACT ebXML UMM/CC The United Nations and e-Business? To maintain international peace and security To develop friendly relations among nations To achieve international co-operation
open-EDI reference modelFrom Conceptual Models to Deployment Artifacts
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)
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 UMM describes collaborative business processes from a global and neutral point of view Buyer's view on collaboration Seller's view on collaboration Buyer Seller Buyer Seller Collaboration Buyer Seller
Multiple Interactions between Different Market Participants Company A Company B Company C Company D Company E Company F Company G Company H
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 Identification of properties of objects Two kinds 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 Order ACC Order Item ASCC Item ACC - BCC - Part number
Adding Context – Business Information Entities Core components in a specific business context Qualifiers help to differentiate BIEs Two kinds 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 InformationEntity US_Person ABIE ASBIE private_address US_Address ABIE - BBIE - Street
Dependency between Core Components and Business Information Entities basedOn basedOn basedOn basedOn BIEs are derived from CCs by restriction
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 http://vienna-add-in.googlecode.com
My Library UN/CEFACT Library Tool Support for Business Document Engineering Modeling with custom Library XMLSchemaB Generate VIENNA AddIn Import Transform XMLSchemaC Modeling with standardized Library Doc-ModelA Doc-ModelC Doc-ModelB
Thank you for your Attention! • <Lecturer> • <Name>Philipp Liegl</Name> • <Company>Vienna University of Technology</Company> • <Email>liegl@big.tuwien.ac.at</Email> • <Url>http://www.umm-dev.org</Url> • </Lecturer> • <Lecturer> • <Name>Michael Strommer</Name> • <Company>Research Studios Austria</Company> • <Email>mstrommer@researchstudio.at</Email> • </Lecturer>