UN/CEFACT‘s Modeling Methodology (UMM)

1. UN/CEFACT‘s Modeling Methodology (UMM) E-Commerce Technologien – WS09 Thomas Motal

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

3. 1 Introduction

4. B2C B2B B2B vs. B2C H2A Web-Browser A2A EDI, ebXML & Web Services 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

5. 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+060529:1133+L0605291133001' UNH+16052911330001+PAYMUL:D:96A:UN' BGM+452+111112006052911333500001+9' DTM+137:20060529113335:203' FII+MR+471114711+14000:25:137‘ … (extracted from an EDIFACT PAYMUL) • Great efforts on standardizing business document

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

7. Order from Quote Business Scenario 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 Buyer Seller Fine.

8. 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) Next Week

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

10. 2 UMM

11. 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

12. 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 2.1.1 • UMM is used in order to define global business choreographies

13. Process Choreography – The HOW

14. Orchestration vs. Choreography

15. 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 globaland neutralpoint of view Buyer‘s view Seller‘s view Collaboration Seller Buyer

16. 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) ormore 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

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

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

19. 3 Business Requirements View

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

21. Involved Parties Announce Waste Transport Announce Waste Transport Announce Waste Transport Exporter ExportAuthority ImportAuthority Importer Announce Transport Arrival Announce Transport Arrival Announce Transport Arrival

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

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

24. Classifying Business Processes B Requirements V • 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 BDV BPV BEV

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

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

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

28. The Business Entity View (BEV) B Requirements V • 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 BDV BPV BEV

29. BEV – Example B Requirements V BDV BPV BEV

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

31. The Business Partner View (BPV) B RequirementsV • 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 BDV BPV BEV

32. BPV – Example B Requirements V BDV BPV BEV

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

34. 4 Business Choreography View

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

36. The Business Transaction View (BTV) B Choreography V • 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 BTV BCV BRV

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

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

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

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

41. BTV – Example [4] isConfidential: No isTamperProof: No isAuthenticated: No B Choreography V BTV isConfidential: Yes isTamperProof: Yes isAuthenticated: Yes 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

42. The Business Collaboration View B Choreography V • 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 BTV BCV BRV

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

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

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

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

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

48. The Business Realization View B Choreography V • 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 BTV BCV BRV

49. <<BusinessPartner>> <<BusinessPartner>> <<BusinessPartner>> <<BusinessPartner>> Business Scenario B Choreography V BTV BCV Export Authority Import Authority BRV Exporter Importer Business realizationImpA-Imp Business realizationExp-ExpA Business realizationExpA-ImpA

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