UN/CEFACT Modeling Methodology

1. UN/CEFACT Modeling Methodology 葉慶隆 大同大學 資訊工程系所 Email:chingyeh@cse.ttu.edu.tw http://www.cse.ttu.edu.tw/chingyeh

2. Source • UN/CEFACT Modeling Methodology, pp. 378-388, ebXML: Concepts and Application, by Brian Gibb and Damodaran, Wiley 2003 UMM

3. Background • A methodology, UMM, is useful when • when the ebXML framework is applied to implement new business collaborations, or • when existing systems are migrated to the ebXML framework. • It supports modeling of existing business practices as business collaborations and drives the implementation. UMM=UN/CEFACT Modeling Methodology UMM

4. Background • Additional benefits of the methodology include • Modeling documents the underlying required business collaboration steps among the partners. • Modeling helps to identify best practices and establish benchmarks. • Formal descriptions resulting from modeling also help identify possible improvements that may streamline transaction costs or other overhead. • New requirements due to legislation, technology, or reorganization are easier to implement if a model already exists. • Modeling also helps identify the e-business standards and solutions that may be applicable. UMM

5. Background • Use of a formal modeling methodology, such as UMM, makes the process of modeling efficient because of established procedures and terms. • The goal of UMM is to provide a methodology to model business collaborations in a technology-neutral and implementation-independent way. UMM

6. Open-edi Reference Model • The Open-edi reference model permits two views of business collaborations: a BOV and a FSV. • The primary scope of UMM is BOV. • The only aspects of FSV within the scope of UMM is the design of messages that would be exchanged among services that implement the BOV. Open-edi Reference Model ebXML standards dichotomy Business Operational View BOV Business Aspects BPSS CC Maps FSV MS RR CPPA Information Technology Aspects Functional Service View UMM

7. UMM • The UMM extends the syntax and semantics of the UML metamodel (the model that defines UML itself) by using an extension mechanism in UML: stereotyping. • For example, <<Business Transaction>>. • UMM augments UML by defining the stereotype Business Transaction, so a business modeler can specify that a class have a stereotype of Business Transaction. • The use of stereotype adds a rich layer of useful semantics to UML and makes it easier to understand a UML diagram. UMM

8. UMM UMM Workflow Deliverables • UMM recognizes that all software development projects go through four phases: • Inception, • Elaboration, • Construction, and • Transition. • In each of these phases, a different sequence of activities (workflows) take place. Business Area Process Area Business Process (Use Case) Business Modeling BOM BRV Use Case Description Business Collaboration Requirements Business Transactions Business Documents BTV Analysis BSV Design Service Collaborations UMM

9. Business Operations Map • Business Modeling workflow creates a business operations map (BOM). • The BOM identifies • Business Areas, e.g., Order Management, • Process Areas, e.g., Buy, within each Business Area, and • Business Processes, use cases, e.g., Perform Credit Check. • The BOM provides an organized view of the entire business problem by providing a systematic decomposition of business entities. • In the Requirement workflow the business processes (use cases) are further elaborated. UMM

10. Business Requirements View • The Requirements workflow creates a business requirement view (BRV) that consists primarily of • business uses case descriptions corresponding to each business process, e.g., the sequence of steps involved in Buy. • The use cases can be choreographed as activity diagrams. UMM

11. Business Requirements View UMM

12. Business Transaction View • The Analysis workflow produces a business transaction view (BTV) that includes • Further refined business collaborations, which are decomposed into business transactions with attributes. UMM

13. Business Service View • The Design workflow produces a Business Service View (BSV) that captures the syntax and semantics of a Service Collaboration. • Service Collaboration • An execution of the business activities within a business transaction in terms of business services that are network components • The BSV also describes the structure of message exchanged among business services. • CPP and CPA captures the profile and agreement of technical aspects of these services, respectively. • BSV introduces the notion of a Service Agent that captures a non-network component, such as a browser. • The BSV can be implemented by the FSV component in the Open-edi reference model. UMM

14. Patterns • Patterns • used to describe a problem that occurs in an environment and the core of a solution to this problem, so that • the same solution can be used to solve this problem that occurs repeatedly in that environment or other environment. • In software design, design patterns are popular because they provide • a common vocabulary among software designers and • good techniques for solving common problems. UMM

15. Patterns UMM Workflow Deliverables Patterns Business Modeling BOM Domain Patterns BRV Requirements Business Collaboration Patterns BTV Analysis Business Transaction Patterns The most developed in UMM BSV Business Service Integration Patterns Business Document Design Patterns Design UMM

16. Business Transaction Patterns • UMM specifies six Business Transaction Patterns • Commercial transaction: • This pattern is used when there is an explicit or an implicit residual obligation between two business partners. • A transaction based on this pattern should meet authorization, authentication, and nonrepudiation requirements. • E.g., issuing a purchase order • Query/Response • This pattern is used to obtain information using a query on static information kept at the Responding partner. • No residual obligation • E.g., a Query of a catalog for perfumes costing less than $200.00. continued UMM

17. Business Transaction Patterns • Request/Response: • This pattern is used to obtain information based on a query that requires dynamically creating this information. • E.g., a response might get a quote for a product service as a result of request. • Request/Confirm • This pattern is used to obtain the status of an in-progress business collaboration. • Nonrepudiation requirements are acknowledgement or receipt are optional. • E.g., obtaining the status of an order continued UMM

18. Business Transaction Patterns • Notification • This pattern is used for a formal exchange of a notifying business document and the return of an ReceiptAcknowledgement business signal. • Requiring nonrepudiation • E.g., shipping notification sent to the Buyer by a Seller after the order is placed and paid for • Information distribution • Similar to the Notification patter, with the exception that the transaction is done informally. • No nonrepudiation requirement • E.g., informing current customers the availability of newer products or product updates UMM

19. Business Transaction Patterns Business transaction properties (1) The top and bottom rows in each patter are for the Requesting and Responding roles, respectively. UMM

20. Business Transaction Patterns Business transaction properties (2) UMM

21. Service-Interaction Patterns • Patterns for initiating message exchanges and responding to message exchanges among network components that implement Business Service and non-network components that implement Service Agents • A Service Agent acts on behalf of a Business Service. • For example, a browser is a Service Agent that sits between the end user and a Business Service • Five SIPs are specified. • Service-Service • Agent-Service-Service • Service-Service-Agent • Service-Agent-Service • Agent-Service-Agent UMM

22. Service-Interaction PatternsVariations No responding document, time to perform = time to acknowledge Time to perform > time to acknowledge

23. Service-Interaction Patterns • The Design workflow also discovers Information Structure Design Patterns. • EDI Transaction Sets and XML-based business document, such as OASIS BODs, fulfill the needs of the Documents. • However, UMM allows the creation of new document structures that address the needs of the Service Interaction Patterns and Business Transactions. UMM

24. Business Collaboration PatternsExample Commitment-fulfill pattern

25. Business Collaboration PatternsExample Order-payment

26. Deploying the ebXML Framework