Electronic Commerce Group Institute for Software Technology and Interactive Systems Vienna University of Technology Favoritenstraße 9-11/ Vienna. Austria/Europe Tel.: +43 (1) , Fax: +43 (1) UN/CEFACT‘s Modeling Methodology (UMM) E-Commerce Technologien – WS09 Thomas Motal

Agenda Introduction UN/CEFACT‘s Modeling Methodology (UMM) Business Requirements View (BRV) Business Choreography View (BCV) Business Information View (BIV) Conclusion 2

3 1 Introduction

Web-Browser EDI, ebXML & Web Services B2B vs. B2C H2A B2C:  Server dominates the business process  Consumer reacts on the fly B2B:  Applications must interact with each other  Applications must follow an agreed upon business process A2A

The traditional approach Document-centric Traditional EDI standards have been in use since the 1980’s ANSI X12, UN/EDIFACT, ODETTE, VDA, EANCOM… Transmission over Value Added Networks (VAN), X.400,…, floppy disks UNB+UNOC:3+ATCABV+ATCABV :1133+L ' UNH PAYMUL:D:96A:UN' BGM ' DTM+137: :203' FII+MR :25:137‘ … (extracted from an EDIFACT PAYMUL) Great efforts on standardizing business document

A B C D E A B C D E Standard Format  Syntax  Document structure  Document content Message Implementation Guideline (MIG): Standard MIG User Group MIG Company MIG Partner-specific Overloaded document types require bilateral agreements between business partners Ambiguous Document Standards

Order from Quote Business Scenario 7 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. BuyerSeller

Interoperability Requirements between Enterprises HOW are documents exchanged between enterprises? Common definition in which order documents are exchanged Global process choreography vs. local process choreography Use of technologies for the unambiguous definition of process choreographies UN/CEFACT‘s Modeling Methodology 2.0 (UMM) WHICH documents are exchanged between enterprises? Common definition of the artifacts which are exchanged between enterprises Business document standards UML Profile for Core Components 3.0 (UPCC) 8 Next Week

XML Schema, BPEL, workflow languages … Functional Service View related standards UN/CEFACT’s Modeling Methodology (UMM) & Core Component Technical Specification (CCTS) The Open-edi Reference Model (ISO 14662) Business Operational View related standards Business Transactions Business aspects of business transactions Information technology aspects of business transactions viewed as comply with covered by comply with transformed to Business Operational View Functional Service View

10 2 UMM

Principles of the UMM Solution 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 11

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 from requirements elicitation to process design UMM is defined as a UML profile on top of UML UMM is used in order to define global business choreographies 12

Process Choreography – The HOW 13

Orchestration vs. Choreography 14

What is 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 15 Buyer‘s viewSeller‘s view Buyer Seller Collaboration

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 Realized by a request from one side and an optional response from the other side 16

The UMM 2.0 Architecture Development process of the UMM Business Requirements View (BRV) Business Choreography View (BCV) Business Information View (BIV) 17 UMMBRVBCVBIV

UMM Package Structure 18 UMM Foundation Module BusinessRequirementsView BusinessDomainView BusinessRealizationView BusinessPartnerView BusinessEntityView BusinessChoreographyView BusinessTransactionView BusinessCollaborationView BusinessInformationView

19 3 Business Requirements View

Announce Waste Transport Waste Movement in Europe 20 Export AuthorityImport Authority Notifier Notifiee Announce Transport Arrival

Involved Parties 21 Exporter Export Authority Import Authority Importer Announce Waste Transport Announce Waste Transport Announce Waste Transport Announce Transport Arrival Announce Transport Arrival Announce Transport Arrival

The BRV Package Structure 22 UMM Foundation Module BusinessRequirementsView BusinessDomainView BusinessPartnerView BusinessEntityView BusinessChoreographyView BusinessInformationView

The Business Domain View (BDV) Purpose Getting to know the domain under consideration Discovery of existing business processes Rough identification of desired collaborations Important: No new business processes are created in the BDV! Artifacts Use case diagrams Activity diagrams 23 B Requirements V BDV BPV BEV

Classifying Business Processes Using the concept of Business Areas (bArea) and Process Areas the business modeler can classify the different processes UMM does not mandate a particular structure 24 B Requirements V BDV BPV BEV

BDV – Example [1] 25 B Requirements V BDV BPV BEV

Using Worksheets to Capture Requirements 26 A detailed definition of the different worksheets is provided in the UMM 2.0 specification.

BDV – Example [2] 27 B Requirements V BDV BPV BEV

The Business Entity View (BEV) Purpose Identification of relevant business entities  a business entity is something that has business significance (e.g., order, newspaper,...) Describing the lifecycle of business entities A business entity state that is shared between two business partners is a strong indicator for a required exchange of business information Artifacts State machine diagram describing the lifecycle of a business entity Changes of business entity states may be visualized in the business domain view 28 B Requirements V BDV BPV BEV

BEV – Example 29 B Requirements V BDV BPV BEV

Relationship between BEV and BDV 30 B Requirements V BDV BPV BEV

The Business Partner View (BPV) Purpose Container for business partners and stakeholders that are identified in the business domain view Modeling organization relationships between those actors (optional) Artifacts Use case diagram Business partners and stakeholders 31 B Requirements V BDV BPV BEV

BPV – Example 32 B Requirements V BDV BPV BEV

Relationship between BPV and BDV 33 B Requirements V BDV BPV BEV

34 4 Business Choreography View

The BCV Package Structure 35 UMM Foundation Module BusinessRequirementsView BusinessRealizationView BusinessChoreographyView BusinessTransactionView BusinessCollaborationView BusinessInformationView

The Business Transaction View (BTV) Purpose A business transaction describes the message exchange between exactly two business partners The message exchange synchronizes the shared state of the two partners Message exchange might be one-way or two-way Artifacts Activity diagrams of the business transactions Use cases capturing the requirements 36 B Choreography V BTV BCV BRV

BTV – Example [1] 37 B Choreography V BTV BCV BRV

BTV – Example [2] 38 B Choreography V BTV BCV BRV

Requirements are expressed using use cases A business transaction itself is expressed using activity diagrams BTV – Example [3] 39 B Choreography V BTV BCV BRV

BTV – Example [4] 40 B Choreography V BTV BCV BRV Time constraints Security Flags Retry Counter Time Constraints Security Flags Security Flags Security Flags

BTV – Example [4] 41 B Choreography V BTV BCV BRV timeToPerform: 24 hrs timeToAcknowledgeReceipt: 2 hrs timeToAcknowledgeProcessing: 4 hrs isAuthorizationRequired: false isNonRepudiationRequired: false isNonRepudiationOfReceiptRequired: false isIntelligibleCheckRequired: true retryCount: 3 timeToPerform: 24 hrs timeToAcknowledgeReceipt: 2 hrs timeToAcknowledgeProcessing: 4 hrs isAuthorizationRequired: false isNonRepudiationRequired: false isIntelligibleCheckRequired: true isConfidential: No isTamperProof: No isAuthenticated: No isConfidential: Yes isTamperProof: Yes isAuthenticated: Yes

The Business Collaboration View Purpose A business collaboration describes the order in which business transactions are executed A business collaboration describes the global choreography of an inter-organizational business processes. Artifacts Activity diagrams of the business collaborations Use cases capturing the requirements 42 B Choreography V BTV BCV BRV

BCV – Example [1] 43 B Choreography V BTV BCV BRV

BCV – Example [2] 44 B Choreography V BTV BCV BRV

BCV – Example [3] 45 B Choreography V BTV BCV BRV

BCV – Example [5] 46 B Choreography V BTV BCV BRV

BCV – Example [4] 47 B Choreography V BTV BCV BRV timeToPerform: 24hrs isConcurrent: false timeToPerform: 24hrs isConcurrent: false

The Business Realization View Purpose Assigning business partners to authorized roles participating in a collaboration. Collaboration Realizations allow that different sets of business partners perform the same collaboration Artifacts Use cases, Business partners, Authorized Roles 48 B Choreography V BTV BCV BRV

Business Scenario 49 B Choreography V BTV BCV BRV > Importer Export Authority Import Authority Exporter Business realization Exp-ExpA Business realization ExpA-ImpA Business realization ImpA-Imp

BRV – Example [1] 50 B Choreography V BTV BCV BRV

Derivation of Deployment Artifacts 51

52 5 Business Information View

The Business Information View Purpose The business information artifacts which are exchanged in the different business transaction are described in the business information view UN/CEFACT does not mandate a specific business document modeling methodology However, it is strongly encouraged to use the UML Profile for Core Components ( UPCC ) Artifacts Class diagrams and associations describing the business documents 53

The BIV Package Structure 54 UMM Foundation Module BusinessRequirementsView BusinessRealizationView BusinessChoreographyView BusinessTransactionView BusinessCollaborationView BusinessInformationView

BIV – Example [1] 55 B Information V

BIV – Example [2] 56 B Information V

57 6 Conclusion

Capture IT system requirements of distributed (service oriented) systems independent of the implementation technology Define an agreement upon an inter-organizational business process between two business partners (global choreography) Create the basis for the derivation of deployment artifacts for IT systems (generate abstract BPEL) UMM – What it can do 58

UMM – What it can’t do Provide models for the derivation of orchestrations (UMM does not provide an internal view of a business partner) Generate ready-to-use deployment artifacts (e.g. executable BPEL) UMM is on the BOV layer UMM does not provide service definitions and service bindings 59

UMM Technical Specification UMM 2.0 Foundation Model UMM Development site UMM User Guide Example models Academic papers … VIENNA Tool UMM Resources 60

ECT UMM Exercise Facts Requirements Sparx Systems Enterprise Architect (30 day trial)  VIENNA Tool  Prepare a meaningful presentation [!] 61

62 ? Questions