UN/CEFACT‘s Modeling Methodology (UMM 1.0) towards UMM 2.0

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UN/CEFACT‘s Modeling Methodology (UMM 1.0)

towards UMM 2.0

DissertantInnen Seminar – Mo, 21.05.2007

Christian HuemerMarco Zapletal

Philipp LieglRainer Schuster

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Outline

Introduction to UMM UMM 1.0 by Example A Business Service Interface for Business

Transactions Limitations of UMM 1.0 Modeling Business Documents Call Behavior and Alternative Responses UMM Choreographies and Business Entity States Re-packaging the UMM Multiparty Collaborations and Local Choreographies Summary

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

We are going to talk about …

UN/CEFACT‘s Modeling Methodology (UMM)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UN and e-Business?

To maintain international peace and security

To develop friendly relations among nations

To achieve international co-operation;

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UN Layout Key

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Application Application

Goal: Exchange of business related data,Goal: Exchange of business related data,independent of independent of SoftwareSoftware, , HardwareHardware and and Communication ProtocolsCommunication Protocols

EDIEDI EDIEDI

Electronic Data Interchange (EDI)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

United Nations Centre for Trade Facilitationand e-Business (UN/CEFACT]

UN/EDIFACT

UMM & CC

UN Layout Key

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Open-edi Reference Model – ISO 14662

Business Operational View

Functional Service View

Comply with

Covered by

Comply with

Covered by

Business aspects of

business transactions

Information technology aspects of

Viewedas

Transformed To

Business Operational View

Functional Service View

Covered by

Business aspects of

Information technology aspects of

BOV RelatedStandards

FSV RelatedStandards

UN/CEFACT`s ModelingMethodology (UMM)

UN/EDIFACTWeb Services

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UN/CEFACT´s Modeling Methodology

Customizing UML for modeling inter-organizational processes

Concentrates on business semantics Independent of the IT platform Describes a choreography from a global perspective UML Profile: Stereotypes, Tagged Values, Constraints on

top of the UML Meta Model

BDVBusinessDomain

BRVBusiness

RequirementView

BTVBusiness

TransactionView

BSVBusiness Service

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Outline

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UN/CEFACT‘s Modeling Methodology (UMM)

Customizing UML for modeling B2B Concentrates on business semantics Independent of the IT platform Describes a choreography from a global perspective UML Profile: Stereotypes, Tagged Values, Constraints

on top of the UML Meta Model– ~ 40 stereotypes defined in the meta model

BDVBusiness

Domain View

BRVBusiness

Requirements View

BTVBusiness

Transaction View

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Import AuthorityExport Authority

UMM by example European crossborder waste management

Notifier Notifiee

Announce Waste TransportAnnounce Transport Arrival

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Top-level UMM Packages<<BusinessDomainView>>

<<BusinessArea>>

<<BusinessRequirementsView>>

<<BusinessProcessView>>

<<BusinessEntityView>>

<<TransactionRequirementsView>>

<<CollaborationRequirementsView>>

<<CollaborationRealizationView>>

<<BusinessTransactionView>>

<<BusinessInteractionView>>

<<BusinessChoreographyView>>

<<BusinessInformationView>>

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UMM by example - BRV ud Announce Waste Transport

Notifier

«BusinessTransactionUseCase»Announce Waste

Transport

Notifiee

«participates»«participates»

ud Announce Transport Arrival

Notifier Notifiee

«BusinessTransactionUseCase»Announce

Transport Arrival «participates»«participates»

ud Manage Waste Transport

Notifier Notifiee

«BusinessCollaborationUseCase»Manage Waste

Transport

«BusinessTransactionUseCase»Announce

Transport Arrival

«BusinessTransactionUseCase»Announce Waste

Transport

«include»«include»

<<mapsTo>> <<mapsTo>>

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

<<BusinessPartner>> <<BusinessPartner>> <<BusinessPartner>> <<BusinessPartner>>

ImporterExportAuthority

ImportAuthorityExporter

UMM by example – Business Partner

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ud Manage Waste Transport, Ex - ExA

«BusinessCollaborationRealization»Manage Waste

Transport

Notifer Notifee

Exporter

(from Waste Management)

ExportAuthority

(from Manage Waste Transport)

«BusinessCollaborationUseCase»Manage Waste

Transport

Notifiee

Notifier

«participates» «participates»

«mapsTo»«mapsTo»

«mapsTo»

«participates»

«mapsTo»

«participates»

«realize»

UMM by example - BRVSubview: CollaborationRealizationView

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Top-level UMM Packages<<BusinessDomainView>>

<<BusinessArea>>

<<BusinessRequirementsView>>

<<BusinessProcessView>>

<<BusinessEntityView>>

<<TransactionRequirementsView>>

<<CollaborationRequirementsView>>

<<CollaborationRealizationView>>

<<BusinessTransactionView>>

<<BusinessInteractionView>>

<<BusinessChoreographyView>>

<<BusinessInformationView>>

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ad Announce Waste Transport

Responder :Notifiee

«BusinessTransactionSwimlane»

Requestor :Notifier

«RequestingInformationEnvelope»:WasteMovementFormEnvelope

«RespondingBusinessActivity»Process Waste Movement Form

«RequestingBusinessActivity»Notify Waste Transport

«InformationEnvelope»:WasteMovementResponseEnvelope

[Success][Failure]

ad Announce Transport Arrival

Requestor :Notifier

Responder :Notifiee

«RequestingInformationEnvelope»:TransportArrivalFormEnvelope

«RespondingBusinessActivity»Process Transport Arrival Form

«RequestingBusinessActivity»Notify Transport Arrival

[Success]

[Failure]

ad Manage Waste Transport

«BusinessTransactionActivity»Announce Transport Arrival

«BusinessTransactionActivity»Announce Waste Transport

UMM by example - BTV

<<mapsTo>>

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The UMM Add-In

First prototypical implementation which supports the UMM approach

Developed by the University of Vienna in cooperation with the Research Studios Austria

Available for free from the project’s website– http://ummaddin.researchstudio.at

Extension of the Enterprise Architect Developed in C#

Current version: 0.8.2

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UMM Add-In Overview

Semi automatic artifact generation

Requirements EngineeringSupport

Model validation

Transformation tochoreography languages

Core Components supportUMM Add-In

UMM specific toolbar

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

<<BusinessPartner>>

uc Actualization

ExportAuthority

«BusinessProcess»Pre-Inform on

Waste Transport

Exporter

«participates»

<XML>UMM-specific toolbar

Requirements Engineering – UMM Worksheets

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Valid?

act Announce Waste Transport

Responder :Notifiee«BusinessTransactionSwimlane»

Requestor :Notifier«BusinessTransactionSwimlane»

«RequestingInformationEnvelop...:WasteMovementFormEnvelope

«RespondingBusinessActiv ity»Process Waste Movement Form

«RequestingBusinessActiv ity»Notify Waste Transport

[Success][Failure]

Responder :Notifiee

Requestor :Notifier

«RequestingInformationEnvelop...:WasteMov ementFormEnv elope

«RespondingBusinessActiv ity»Process Waste Mov ement Form

«InformationEnvelope»:WasteMov ementResponseEnv elope

[Success][Failure]

Responder :Notifiee

«BusinessTransactionSw imlane»

Requestor :Notifier

«BusinessTransactionSw imlane»

«RequestingInformationEnvelop...:WasteMovementFormEnvelope

«RespondingBusinessActiv ity»Process Waste Movement Form

[Success][Fai lure]

UMM Add-In – BPEL/BPSS Generator

Validating UMM Model

Responder :Notifiee

Requestor :Notifier

«RequestingInformationEnvelop...:WasteMov ementFormEnv elope

«RespondingBusinessActiv ity»Process Waste Mov ement Form

[Success][Failure]

Semi-automatic generation of UMM artifacts

Transformation into Choreography Languages

UMM Validation

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Outline

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

trol F

<<RespondingBusinessActivity>>

Business Transaction

<<RequestingBusinessActivity>>

: Buyer : Seller

:PurchaseOrderEnvelope

:OrderResponseEnvelopeplace order

process order

isConfidential: noisTamperProof: yesisAuthenticated: yes

timeToRespond: 24 hrstimeToAcknowledgeReceipt: 1 hrstimeToAcknowledgeProcessing: 4 hrsisAuthoriztionRequired: yesisNonRepudiationRequired: yesisNonRepudiationOfReceiptRequired: yesisIntelligibleCheckRequired: yesretryCount: 3

timeToAcknowledgeReceipt: 2 hrstimeToAcknowledgeProcessing: 8 hrsisAuthoriztionRequired: yesisNonRepudiationRequired: yesisNonRepudiationOfReceiptRequired: yesisIntelligibleCheckRequired: yes

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Old Business Service View

:BuyerService :SellerService

PurchaseOrderEnvelope

AcknowledgmentOfReceipt

AcknowledgmentOfProcessing

OrderResponseEnvelope

sd 02-AnnounceWasteTransport - Success - Drop of Document by Message Broker

:MessageBroker:CompetentAuthori tyOfDispatch :MessageQueue :CompetentAuthori tyOfDestination:MessageQueue

[Document Expired]

If the document expires (according to the expiration timementioned in the ini tia l https Response after the document was submitted by the Competentent Authori ty of Dispatch), but the document waspicked up by the CA of Destination before, the MessageBroker drops the Movement Document from the Message Queue. In this case no fax is sent, since the document was already picked up.

According to the Vienna Meeting, Business Signals do not expire. This m eans business signals must always be droped by the CAs.

????????????Alternative:Business signals that were picked up by a CAare deleted by the broker after a fixed time period.????????????

MovementDocument

https Response

MovementDocument

AckOfReceipt

pickup AckOfReceipt

AckOfReceipt

drop AckOfReceipt

pickup MovementDocument

MovementDocument

Drop MovementForm

AckOfProcessing

https Response

AckOfProcessing

AckOfReceipt[4AckProc]

pickup AckOfReceipt[4AckProc]

AckOfReceipt[4AckProc]

drop AckOfReceipt[4AckProc]

pickup AckOfProcessing

AckOfProcessing

drop AckOfProcessing

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

State Machines

Describes the Business Service Interface of a participating partner

Unambiguous definition on how to react on– Incoming messages

– Messeages expected, but not received

Resulting State Machines:– The state machine of the initiator

– The state machine of the responder

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Outline

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Limitation 1

Vague guidelines on modeling business documents

cd Waste Mov ement Form

«InformationEnvelope»WasteMov ementFormEnvelope

«InformationEntity»StandardBusinessDocumentHeader

«ABIE»WasteMov ementForm

«ABIE»Waste

«ABIE»...

+Waste 1..*

+body+header

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Limitation 2

Work-around to support call behavior in UML 1.4

ad Manage Waste Transport

«BusinessTransactionActivity»Announce Transport Arrival

Responder :Notifiee

Requestor :Notifier

«RequestingInformationEnvelope»:WasteMovementFormEnv elope

«InformationEnvelope»

:WasteMov ementResponseEnvelope

[Success][Failure]

ad Announce Transport Arriv al

Requestor :Notifier

Responder :Notifiee

«RequestingInformationEnvelope»

:TransportArriv alFormEnv elope«RespondingBusinessActivity»

Process Transport Arriv al Form

«RequestingBusinessActivity»Notify Transport Arriv al

[Fai lure]

[Success]

<<mapsTo>>

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Limitation 3

Inability to model alternative responsesad Announce Waste Transport

Responder :Notifiee

Requestor :Notifier

«RequestingInformationEnvelope»:WasteMov ementFormEnv elope

«RespondingBusinessActivity»Process Waste Mov ement Form

[Success][Failure]

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Limitation 4

Flow may be well interpreted by humans Fails to give an unambiguous machine-

processable definitionact Manage Waste Transport

Success

«BusinessTransactionActivity»

:AnnounceWasteTransport

:AnnounceTransportArrivalFailure

[Transportwas notaccepted]

[Transportwas accepted]

Responder :Notifiee

Requestor :Notifier

:WasteMov ementResponseEnv elope

[Success][Failure]

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Limitation 5

Split of strongly related artifacts into different packages

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Limitation 6

No multi-party choreographies No nested business transactions

sd PurchaseOrderManagement

Buyer RespondentSellerQuoteRequestEnvelope

CreditCheckRequestEnvelope

CreditCheckResponseEnvelopeQuoteEnvelope

PurchaseOrderEnvelope

OrderResponseEnvelope

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Outline

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Motivation for standardizing the exchanged data

SOAP message

Order processing of enterprise X

request for quote

place order

check order statusEnterprise Application

Customer Y

Enterprise Application

WSDLWSDL

SOAP message

UDDI registry

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Motivation for standardizing the exchanged data

SOAP message

Order processing of enterprise X

request for quote

place order

check order statusEnterprise Application

Customer Y

WSDLWSDL

SOAP message

UDDI registry

SOAP Message

SOAP Body

SOAP Header

Message Body

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Motivation

Problem domain– Business documents exchanged in a business process in

a service oriented context

UN/CEFACT provides a generic solution– Core Components Technical Specification (CCTS)– Almost no tool support possible – CCTS are standardizes

as spread sheets

UML Profile for Core Components– Seamless integration into UML modeling tools possible– Seamless integration into e.g. process modeling specific

models possible

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Harmonizing the exchanged data

Known standardization efforts– UN/EDIFACT– XML based solutions (RosettaNet)

Known issues of these efforts– Multitude of different and competing standards– Inclusion of every possible element that may be required –

strong overhead– Changes in the transfer syntax would require a complete

reegineering

Solution– Platform independent resuable building blocks for

creating shared libraries of business documents developed by UN/CEFACT

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Core Components

Are the central building blocks of the Core Component Technical Specification

Platform independent Used to create shared libraries of

interoperable business documents The ontological base of the CCTS is the United

Nations Trade Data Element Dictionary (UN/TDED)

Initially started as part of ebXML standards suite Now a dedicated project independent of ebXML

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Core Component (CC) example

No business context Independent of industry

or domain

ACC Aggregate Core Component

BCC Basic Core ComponentASCC Association Core

Component

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Business Information Entity (BIE) example

Core Components in a specific business context (e.g. travel industry)

BIEs have a specific business semantic

Qualifiers (US_) help to define and differentiate a BIE from ist associated CC and other BIEsABIE Aggregate Busines Information

EntityBBIE Basic Business Information

EntityASBIE Association Business

Information Entity

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

By introducing the business context core components become business information

entities

Core Components (CC) Business Information Entities (BIE)

BIEs are derived from CCs by restriction

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Dependency between Core Components and Business Information Entites

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Data Types

Qualified Data Types (QDT) are derived from Core Data Types (CDT) by restriction

Business Information Entities use QDT and CDT

Core Components use only CDT

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The core component meta model

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

A UML Profile for Core Components

Flaws of the Core Components Technical Specification– Standardization process of Core Components is based on

spread sheets– No direct integration into modeling tools possible

UML Profile for Core Components– Independent project based on the CCTS– Set of stereotypes, tagged values and OCL constraints– Can be integrated into a modeling tool of choice– Proof of concept based on UML modeling tool Enterprise

Architect– UML class diagrams are used for the modeling of Core

Components

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UML profile for Core Components - Stereotypes

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Assembling a business document using the different libraries of the UML profile for Core

Components

Business Library

DOCLibrary

BIELibrary

CCLibrary

QDTLibrary

CDTLibrary

ENUMLibrary

PRIMLibrary

Business document

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Derivation of XSD artifacts

<xsd:complexType name="US_PersonType"><xsd:sequence>

<xsd:element name= "DateofBirth" type="udt1:DateType"><xsd:element name="FirstName" type="udt1:TextType"/><xsd:element name="US_Work"

type="bie1:US_AddressType"/><xsd:element name="US_Private"

type="bie1:US_AddressType"/><xsd:sequence>

</xsd:complexType>

<xsd:complexType name="US_AddressType"> […]</xsd:complexType>

Core Component Model

XSD Schema generator

Naming and Design Rules

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Conclusion and Outlook

The UML profile for core components provides a method to model exchanged information– independent of the platform– independent of the transfer syntax– in shared libraries– on a common ontological base– derive different platform specific artifacts

Future work– Develop a new UML profile for CCTS 3.0 (UPCC)– Adaptation of the XSD schema generator– Build a repository to store and retrieve existing ABIE

and data type libraries

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Outline

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

UML 2 provides the concept of call behavior actions

eliminates the maps to‘s ad Manage Waste Transport

«BusinessTransactionActivity»Announce Transport Arriv al

Responder :Notifiee

Requestor :Notifier

«RequestingInformationEnvelope»:WasteMovementFormEnv elope

:WasteMov ementResponseEnvelope

[Success][Failure]

ad Announce Transport Arriv al

Requestor :Notifier

Responder :Notifiee

:TransportArriv alFormEnv elope«RespondingBusinessActivity»

Process Transport Arriv al Form

«RequestingBusinessActivity»Notify Transport Arriv al

[Fai lure]

[Success]

<<mapsTo>>

Eliminating Limitation 2 by Call Behavior

Activity

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Eliminating Limitation 3 – Allowing multiple responses

Differing business intentions should be expressed using different response document types

Responder :Notifiee

Requestor :Notifier

[Success][Failure]

Multiple responses denoted via the object pin syntax

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

XOR relation between the possible response document types

In case multiple documents are sent – parameter sets are used to implement an XOR realtionship– there is always a 1:1 relationship between a document

flow and its enclosing parameter set

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Limitation 4 – Only human-comprehensible interdependencies

The content of a response document needs to be examined to decide on the positive or negative outcome of a business transaction. – Using different response business document types alleviates

this problem The actual business document type decides on the

end state of a business transaction. – However, there exists no formal relationship between a

business document type and the semantically corresponding final state

The business collaboration protocol is guarded by the outcome of business transactions. – However, there is no explicit reference between the

transition guards and the business transaction final states.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Limitation 4 – Only human-comprehensible interdependencies

act Manage Waste Transport

Success

:AnnounceTransportArrivalFailure

[Transportwas notaccepted]

[Transportwas accepted]

Responder :Notifiee

Requestor :Notifier

:WasteMov ementFormEnv elope«RespondingBusinessActivity»

Process Waste Mov ement Form

[Success][Failure]

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

context NotifyWasteTransportinv NegativeResponse: self.input−>one (x|x.isTypeOf WasteMovementRejectionEnvelope) and x <> null)context NotifyWasteTransportinv PositiveResponse: self.input−>one (x|x.isTypeOf (WasteMovementAcceptanceEnvelope) and x <> null)

BusinessSuccess

BusinessFailure

«RespondingBusinessActivity»

Process Waste Movement Form:WasteMovementFormEnvelope

:WasteMovementRejectionEnvelope

:WasteMovementAcceptanceEnvelope

«RequestingBusinessActivity»

Notify Waste Transport

:WasteMovementFormEnvelope

Eliminating Limitation 4 – Step 1 Binding final states to business document

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Eliminating Limitation 4 – Step 2 Introducing Business Entity States in BT

The execution of a business transaction changes the state of a business entity

act Announce Waste Transport - with States

BusinessFailure

BusinessSuccess

Process Waste Movement Form

:WasteMovementAcceptanceEnvelope:WasteMovementRejectionEnvelope

«BusinessEntity»:WasteTransport

[accepted]

[rejected]

stm WasteTransport

«BusinessEntity...announced

«BusinessEntity...arrived

«BusinessEntity...rejected

«BusinessEntity...accepted

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Eliminating Limitation 4 – Step 3 Business Entity States as Guard Conditions in BCP

The flow of a business collaboration protocol is unambiguously governed by business entity states

act Manage Waste Transport - with States

:AnnounceTransportArrival

Success

Failure

[WasteTransport.oclInState(rejected)]

[WasteTransport.oclInState(accepted)]

act Announce Waste Transport - with States

BusinessFailure

BusinessSuccess

Process Waste Movement Form

:WasteMovementAcceptanceEnvelope:WasteMovementRejectionEnvelope

[accepted]

[rejected]

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Conclusion

Showed the benefits of the transition from UML 1.4.2 to UML 2– eliminating meta model workarounds

Added the possibility to explicitly model different business intentions using multiple response document types

Formally bound business document types to business transaction final states and those in turn to guard conditions in a business collaboration protocol– required for a MDA-like approach

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Outline

<<BusinessDomainView>>

<<BusinessPartner>><<BusinessRequirementsView>>

<<BusinessProcessView>>BusinessProcessActivityGraph

<<TransactionRequirementsView>><<BusinessTransactionUseCase>><<AuthorizedRole>> (2 x)

<<CollaborationRequirementsView>><<BusinessCollaborationUseCase>><<AuthorizedRole>> (2+ x)

<<BusinessTransactionView>><<BusinessInteractionView>>

<<BusinessInteraction>><<BusinessTransaction>>

<<BusinessCollaborationView>><<BusinessCollaboration>>

<<BusinessCollaborationProtocol>><<BusinessInformationView>>

<<BusinessArea>><<ProcessArea>>

<<BusinessProcess>>

<<BusinessEntityView>><<BusinessEntity>>

<<BusinessEntityLifeCycle>>

<<CollaborationRealizationView>><<BusinessCollaborationRealization>><<AuthorizedRole>> (2+ x)

<<BusinessInformation>>

<<BusinessPartnerView>>

<<BusinessChoreographyView>><<BusinessTransactionView>>

Other Folders From UML Profile for CC

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Waste Management: UMM 2

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Outline

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Multi-party Collaboration

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Multiple Bi-lateral Collaborations

uc OrderFromQuote

«BusinessTransactionUseCase»RequestForQuote

«BusinessTransactionUseCase»PlaceOrder

«BusinessCollaborationUseCase»OrderFromQuote

«include»«include»

uc CheckCreditworthiness

«BusinessTransactionUseCase»CheckCredit

«BusinessCollaborationUseCase»CheckCreditworthiness

«include»

<<BusinessCollaborationUseCase>>OrderFromFirmQuote

<<include>> <<include>>

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

<<LocalChroeography>> of a Wholesaler (1)

uc PurchaseManagement

«BusinessCollaborationRealization»OrderFromQuote

Retailer :Buyer Wholesaler

Buyer Seller

<<RespondingBusinessActivity>>calculate quote

<<RespondingBusinessActivity>>act on purchase order

[Quote.provided]

[Order.accepted][Order.rejected][Quote.refused]SuccessFailure

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

uc CheckCreditworthiness

«BusinessCollaborationRealization»CheckCreditworthiness

CheckRequestor Respondent

Wholesaler Bank

<<RequestingBusinessActivity>>request credit check

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

<<RespondingBusinessActivity>>calculate quote

<<RespondingBusinessActivity>>act on purchase order

[Quote.provided]

[Order.accepted][Order.rejected][Quote.refused]SuccessFailure

r <<RequestingBusinessActivity>>request credit check

<<CallNestedTransaction>>:request credit check

act OrderFromFirmQuoteSeller

«RespondingBusinessActiv ity»calculate quote

:QuoteRequestEnvelope

:QuoteEnvelope

«ReceiveBusinessInformation»receive quote envelope

«Priv ateAction»

file quote request

«CallNestedTransaction»

:request credit check

«PrivateAction»act on credit check

result

«Priv ateAction»refuse quote

«Priv ateAction»prov ide quote

«RespondingBusinessActiv ity»act on purchase order

:PurchaseOrderEnvelope

:OrderResponseEnvelope

«ReceiveBusinessInformation»receive purchase order

«Priv ateAction»

file purchase order

«Priv ateAction»

compare purchase order and quote

«PrivateAction»rej ect order

«Priv ateAction»accept order

Start Success

Failure

«SendBusinessInformation»send quote response «SendBusinessInformation»

send order response

[CreditCheck.reported]

[Quote.provided]

[not ok][ok]

[Order.accepted]

[Quote.refused]

[Order.rejected]

[CreditCheck.refused]

act OrderFromFirmQuoteSeller

«RequestingBusinessActiv ity»request credit check

:CreditCheckRequestEnvelope

:CreditCheckResponseEnvelope

«Priv ateAction»prepare credit

«SendBusinessInformation»send credit check request

«Priv ateAction»

file credit check response

«ReceiveBusinessInformation»receive credit check response

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Outline

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Summary

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Techniques & Methodologies Grouphttp://www.untmg.org

http://www.umm-dev.org

UN/CEFACT‘s Modeling Methodology (UMM 1.0) towards UMM 2.0

Documents

Transcript of UN/CEFACT‘s Modeling Methodology (UMM 1.0) towards UMM 2.0

1Business Models – REA in UMM REA in UMM UN/CEFACT Modelling Methodology A Methodology for eCollaborations.

widyatama - UMM

DISERTASI - UMM

Version 1.0 August 2012 - NatureServehelp.natureserve.org/biotics/Content/Methodology/Spatial_Model.pdf · 1. Streamline spatial methodology workflow 2. Provide flexibility in implementation

UN/CEFACT’s Modeling Methodology (UMM): UMM Meta Model ...€¦ · Technical Specification 2006-10-06 . Table of Contents 1 About this Document.....2 1.1 Status of this Document

3HUNHUDVDQ - UMM

1.0 Verilog Synthesis Methodology - Cornell Universitypeople.ece.cornell.edu/land/courses/ece5760/Verilog/...October 18, 2001 1 1.0 Verilog Synthesis Methodology Finbarr O’Regan

FARMAKOTERAPI UMM

SUDAN: North Kordofan State - Administrative Map · Arti Tamar Aulad Noai Umm Tandub Umm Hadhir Umm Sughra Umm Berbit Umm Tulayh Umm Qurayn Gabr Ad Dar Abd Ad Daim Umm Khayran Didan

SARANA DAN PRASARANA UNIVERSITAS MUHAMMADIYAH …pgsd.umm.ac.id/files/file/FASILITAS UMM(1).pdf · UNIVERSITAS MUHAMMADIYAH MALANG Hotel UMM Inn . Masjid Ar Fachruddin UMM . UMM DOME.

ITPI Methodology Version 1.0 Final

JORDANIE & JORDANIE & JERUSALEMJERUSALEMJERUSALEM3500.atscaf.fr/IMG/pdf/jordanie_jerusalem_atscaf.pdf · amman amman –––– umm qais umm qais umm qais –––– jerash jerash

Naskah - UMM

American Carbon Registry® Methodology for REDD— Planned ... · Methodology for REDD— Avoiding Planned Deforestation Version 1.0 August 2010 ACR Methodology for REDD – Avoiding

HAMPTON ROADS MODEL METHODOLOGY REPORT (Ver. 1.0) · VDOT Project ID:30681-01-02 Hampton Roads Model Methodology Report Ver. 1.0 Version 1.0 2

PANDUAN - UMM

TCS Siebel Implementation Methodology Module 4 - Ver 1.0

Introduction to SQLBI Methodology Draft 1.0

Methodology for assessing the safety of Hydrogen Systems ... · This document provides a description of the methodology and models contained in the HyRAM version 1.0. HyRAM 1.0 includes

TESIS - UMM