un/cefact modeling methodology

UN/CEFACT Modeling Methodology

葉慶隆大同大學資訊工程系所

Email:[email protected]://www.cse.ttu.edu.tw/chingyeh

UMM 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 colla

borations: 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.

Business Aspects

Information TechnologyAspects

Maps

Business Operational View

Functional Service View

Open-edi Reference Model

BPSSBOV

CC

RRFSV

CPPA MS

ebXML standards dichotomy

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 Trans

action, 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 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.

BOM

BRV

BTV

BSV

Business Modeling

Requirements

Analysis

Design

Business AreaProcess AreaBusiness Process (Use Case)

Use Case DescriptionBusiness Collaboration

Business TransactionsBusiness Documents

Service Collaborations

UMM Workflow Deliverables

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

[ITEM PENDING]

Request Purchase Order

[FAILURE]

[SUCCESS]

Purchase OrderRequest

Buyer Seller

[ITEM PENDING]

Process Purchase OrderUpdate

Purchase Order Confirmation

Confirm Purchase Order

Notify Purchase OrderUpdate

[SUCCESS][FAILURE

]

Purchase OrderUpdate Notification

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 term

s of business services that are network components• The BSV also describes the structure of message exchanged among b

usiness 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-n

etwork component, such as a browser.• The BSV can be implemented by the FSV component in the Open-edi r

eference 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

BOM

BRV

BTV

BSV

Business Modeling

Requirements

Analysis

Design

Domain Patterns

Business Collaboration Patterns

Business Transaction Patterns

Business Service Integration PatternsBusiness Document Design Patterns

UMM Workflow Deliverables Patterns

The most developed in UMM

UMM 16


• 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


– Request/Response:• This pattern is used to obtain information based on a query that require

s dynamically creating this information.• E.g., a response might get a quote for a product service as a result of r

equest.– 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


– Notification• This pattern is used for a formal exchange of a notifying business docu

ment 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 p

roduct updates

UMM 19


Time to Ack.Receipt

Time to Ack Acceptance

Time to perform

AuthorizationRequired

Commercialtransaction

2hr 6hr 24hr True

2hr 6hr 24hr TrueQuery/Response

Null Null 4hr False

Null Null 4hr FalseRequest/Response

Null Null 4hr False

Null Null 4hr FalseRequest/confirm

Null Null 24hr False

2hr Null 24hr TrueNotification 24hr Null 24hr False

24hr Null 24hr False

Business transaction properties (1)

The top and bottom rows in each patter are for the Requesting and Responding roles, respectively.

UMM 20


Nonrepudiation of Origin and Content

Nonrepudiation of Receipt

Recurrence

Commercialtransaction

True True 3

TrueQuery/Response

False Null 3

FalseRequest/Response

False Null 3

FalseRequest/confirm

False True 3

FalseNotification True True 3

False

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 en

d user and a Business Service• Five SIPs are specified.

– Service-Service– Agent-Service-Service– Service-Service-Agent– Service-Agent-Service– Agent-Service-Agent

Service-Interaction PatternsVariations

InitiatingService RespondingService

1. request(BusinessActionMessage)()

1.1signal(ReceiptAcknowledgement)()

1.2signal(AcceptanceAcknowledgement)()

No responding document, time to perform = time to acknowledge

InitiatingService RespondingService

1. request(BusinessActionMessage)()


1.2signal(AcceptanceAcknowledgement)()

2. response(BusinessActionMessage)()


Time to perform > time to acknowledge

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

Business Collaboration PatternsExample

Economic Contract

Economic Claim

Economic Commitment

Economic Event

Economic Event

establishes

based on

settles

fulfills

duality

fulfills

Commitment-fulfill pattern

Business Collaboration PatternsExample

Order

Invoice

Order Item

Shipment

Payment

establishes

based on

settles

fulfills

duality

fulfills

Order-payment

Deploying the ebXML Framework

Deployment PhasesPhase 1 Phase 2 Phase 3 Phase 4 Phase 5

Messaging ebMS ebMS ebMS ebMS ebMS

Profile Proprietary ebCPPA ebCPPA ebCPPA ebCPPA

Contract(agreement)

Proprietary Proprietary ebCPPA ebCPPA ebCPPA

Business Collaboration

Proprietary,RosettaNet,other

Proprietary,RosettaNet,other

ebBPSS,RosettaNet,other



Registry None,proprietary,ebRegistry

None,proprietary,ebRegistry



None,ebRegistry

Business documents

EDI, XML, other

EDI, XML, other

EDI, XML, other

EDI, XML, other

EDI, XML, ebCC, other