1 / 30

Christian Huemer

Christian Huemer. Institute of Distributed and Multimedia Systems Liebiggasse 4/3-4, 1010 Wien Tel. +43-1-4277-38443 Fax +43-1-4277-38449 christian.huemer@univie.ac.at http://www.cs.univie.ac.at/christian.huemer. Introduction to UN/CEFACT’s Modeling Methodology. Is There a Problem?.

piper
Download Presentation

Christian Huemer

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Christian Huemer Institute of Distributed and Multimedia Systems Liebiggasse 4/3-4, 1010 Wien Tel. +43-1-4277-38443 Fax +43-1-4277-38449 christian.huemer@univie.ac.at http://www.cs.univie.ac.at/christian.huemer Introduction to UN/CEFACT’s Modeling Methodology

  2. Is There a Problem? Did EDI reach critical mass after 20+ years? Using EDI 95% 98% EDI Capable 2% 5% FORTUNE 10000 (1000 in the top 10 Economics) The rest of all Business that should be exchanging information electronically

  3. Traditional B2B Approaches Standard: A A E E B B Standard Format C C D D Message Implementation Guide (MIG): MIG User Group MIG Company MIG Partner-specific Standard

  4. Commercial Off-The-Shelf Software • SMEs need Commercial Off-The-Shelf Software (COTS) that are a combination of ERP systems and B2B software for communication • ERP vendors must implement common B2B scenarios in their products • This requires unambiguous business processes instead of ambiguous business documents • Business processes must be defined in their business context

  5. Business Process What kind of apples do you have? • Define a choreography • Business State Centric 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.

  6. Requirements vs. Technology Business Requirements Interactions Data Technology Implementation

  7. Open-edi: Seperation of business logic and IT BOV related Standards UMM ebXML WebServices FSV related Standards BOV comply with Business aspects of business transactions BOV related Standards covered by BUSINESS COLLABORATION viewed as transformed to FSV comply with Information technology aspects of business transactions FSV related Standards covered by

  8. UN/CEFACT´s Modelling Methodology (UMM) • UML-based description technique for describing B2B scenarios • Concentrates on business semantics • UMM Meta Model (UML Profile) • Provides a procedure similar to the first steps of a software development process

  9. UMM is based on UML Actor 1 Use Case Actor 2 Requirement Gathering Use Case Diagram Activity 1 Activity Graph Choreography Activity 2 Class Diagram Information Structures

  10. 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 • Unit of work allowing roll back to a defined business state • Realized by a request from one side and an optional response from the other side

  11. Relevant UMM Artefacts Business Transaction Use Case Business Collaboration Protocol Use Case Use Case Use Case 1 1 desribes choreography for desribes choreography for 1 1 Business Collaboration Protocol Business Transaction Activity Graph Activity Graph 1 n 1 is composed of is composed of 2 n Business Action (Initiating/Reacting) 1 Business Transaction Activity Activity Activity Is refined by

  12. Business Requirements Specification (BRS) • Objective • Scope • Business requirements • “Business requirements” views • Business process elaboration • Information flow definition • Information model definition • Business rules • Definition of terms Use cases, worksheets Activity, sequence, collaboration diagrams Rules relative to information model Class diagrams

  13. Business Domain View (BDV) • Identify the business processes in the domain of the business problem that are important to stakeholders • intra-enterprise processes • business collaborations, i.e. inter-enterprise processes • Business process are discovered, not constructed • Business processes are classified according to a classification schema • Porter`s Value Chain • SCOR (Supply Chain Operations Reference Model) • UN/CEFACT Catalog of Common Business Processes (under development)

  14. Business Collaboration Use Case … … Wholesaler Transporter Provide Catalogue Find product Sell product Retailer Sell product Ship product Acquire product Acquire product Organize Transport Order Management

  15. Business Requirements View (BRV) • Identifies possible business collaborations for possible business collaborations • Depends on the business processes of the BDV • Describes how the business domain expert sees and describes the process to be modelled • Captures • use case scenarios, • inputs & outputs • constraints • system boundaries • Uses worksheets to describe the use case for a business collaboration

  16. BC Worksheet

  17. Business Collaboration Decomposition

  18. Business Transaction View (BTV) • Presents the view of the business process analyst • Models the business collaboration • Defines a choreography for the business collaboration • The business collaboration protocol is an activity graph • Each activity in a business collaboration protocol is aninterorgranizatonal activity = business transaction activities • Details each business transaction activity • Defines the semantics of an business information exchange between partner roles • A business transaction is an activity graph • The business transaction follows one out of six patterns • Models the business information exchanged • The business information exchanged is modelled in a class diagram. • It should contain all necessary information to transfer the effected business entity (or entities) from one state to the other; • It should not contain any information not needed for business state changes

  19. <<BusinessCollaborationProtocol>> Purchase Order Management <<BusinessTransactionActivity>> <<BusinessTransactionActivity>> <<BusinessTransactionActivity>> register customer order product timeToPerform: 24 hrsisConcurrent: true [NOT Product.Quoted] request for quote PurchaseOrderManagement.BusinessFailure [Product.Quoted] [CustomerInformation.Confirmed] [NOT CustomerInformation.Confirmed] [CustomerInformation.Confirmed] [Product.Ordered] [CustomerInformation.Rejected] timeToPerform: 12 hrsisConcurrent: false timeToPerform: 48 hrsisConcurrent: true [NOT Product.Ordered] PurchaseOrderManagement.BusinessSuccess PurchaseOrderManagement.BusinessFailure

  20. Business Transaction [ControlFail] Request for Quote <<BusinessTransactionActivity>> <<BusinessTransactionActivity>> <<BusinessTransactionActivity>> [CustomerInformation.Confirmed] [NOT CustomerInformation.Confirmed] [CustomerInformation.Confirmed] Register Customer Order Products [ControlFail]

  21. Business Transaction View (BTV) • Presents the view of the business process analyst • Models the business collaboration • Defines a choreography for the business collaboration • The business collaboration protocol is an activity graph • Each activity in a business collaboration protocol is aninterorgranizatonal activity = business transaction activities • Details each business transaction activity • Defines the semantics of an business information exchange between partner roles • A business transaction is an activity graph • The business transaction follows one out of six patterns • Models the business information exchanged • The business information exchanged is modelled in a class diagram. • It should contain all necessary information to transfer the effected business entity (or entities) from one state to the other; • It should not contain any information not needed for business state changes

  22. Business Transaction : Buyer : Seller <<RespondingBusinessActivity>> <<RequestResponse>> :QuoteEnvelope obtain quote [Control Fail] [Success] :QuoteRequestEnvelope calculate quote

  23. Which Type of Business Transaction?

  24. Requesting Activity Property Values Time to Time to Receipt Content Required of Receipt Recurrence Acceptance of Origin and Acknowledge Acknowledge Authorization Time to Perform Non-repudiation Non-repudiation Commercial 2hrs 6hr 24hr true true true 3 Transaction Request / null Null 24hrs false false true 3 Confirm Request / null Null 4hrs false false null 3 Response Query / null Null 4hrs false false null 3 Response Notification 24hrs Null 24hrs false true true 3 Information null null 24hrs false false false 3 Distribution

  25. Business Transaction: Request for Quote <<RespondingBusinessActivity>> <<RequestResponseActivity>> [Control Fail] [Success] isAuthorizationRequired: false isNonRepudiationRequired: false timeToPerform: 4 hrs timeToAcknowledgeReceipt: null timeToAcknowledgeAcceptance: null isIntelligibleCheckRequired: true isNonRepudiationOfReceiptRequired: false retryCount: 3 Initiating Role : Buyer Reacting Role: Seller isConfidential: Yes isTamperProof: Yes isAuthenticated: Yes :QuoteEnvelope obtain quote :QuoteRequestEnvelope calculate quote timeToPerform: 4 hrs timeToAcknowledgeReceipt: 2 hrs timeToAcknowledgeAcceptance: null isIntelligibleCheckRequired: true isAuthorizationRequired: false isNonRepudiationRequired: false isConfidential: No isTamperProof: No isAuthenticated: No

  26. Business Transaction View (BTV) • Presents the view of the business process analyst • Models the business collaboration • Defines a choreography for the business collaboration • The business collaboration protocol is an activity graph • Each activity in a business collaboration protocol is aninterorgranizatonal activity = business transaction activities • Details each business transaction activity • Defines the semantics of an business information exchange between partner roles • A business transaction is an activity graph • The business transaction follows one out of six patterns • Models the business information exchanged • The business information exchanged is modelled in a class diagram. • It should contain all necessary information to transfer the effected business entity (or entities) from one state to the other; • It should not contain any information not needed for business state changes

  27. Business State Centric • Business Collaborations are about managing a shared view on Business States. • Aligning Business States between business partners requires exchange of Business Information. • Business Information is limited to the information required to change the state of one or more Business Entities affected by the exchange. • Business Documents also have the potential to change the state of a business entity. However, business documents do not concentrate on what is needed to change the state, and thus, include a lot of unnecessary data. • Each element included in a business document exchange is a source for incompatibility. • Limit the Business Information exchange to an absolut minimum, i.e. the information required to change the State of a Business Entity.

  28. Business Document: Quote Quote QuoteID QuoteDate Line LineNumber QuoteRequest QuoteRequestID LineQuote UnitPrice Book ISBN Title Authors <<references>> 1 0..n 1 n 1 1

  29. Business Document: Quote based on ABIEs

  30. <Thanks/> <Lecturer> <Name>Christian Huemer</Name> <Company>University of Vienna</Company> <Dept>Institute of Distributed and Multimedia Systems</Dept> <Address> <Street>Liebiggasse 4/3-4</Street> <ZIP>1010</ZIP><City>Vienna</City> <Country>Austria</Country> </Address> <Contact> <Telephone>+43-1-4277-38434</Telephone> <Email>christian.huemer@univie.ac.at</Email> <Http>www.cs.univie.ac.at/christian.huemer</Http> </Contact> <? Presentation status=“questions” ?> </Lecturer>

More Related