Austrian Research Centers GmbH - ARCIntelligent Business Process Management Group 1 Modeling...

Austrian Research Centers GmbH - ARC Intelligent Business Process Management Group

1

Modeling e-Government processes with UMM

Dr. Klaus GschwendtnerPhilipp Liegl

Rainer SchusterResearch Studios Austria

Austrian Research Centers - [email protected]

[email protected]

Robert Mosser

Institute for Distributed and Multimedia SystemsUniversity of Vienna

[email protected]


2

Agenda

Business processes in the eGovernment domain United Nations Centre for Trade Facilitation and e-Business

(UN/CEFACT) UN/CEFACT‘s Modeling Methodology (UMM) Core Components Technical Specification The UMM Add-In UMM and WeGo Future work and conclusion


3

Business processes in the eGovernment domain

Business-to-Government (B2G) should work like B2B e.g. Waste Management, Governmental Aids, Financial Services

Government-to-Government (G2G) Electronic Government, Administrative communication between federal & local government International Transactions – e.g. European Waste Management

Business

Government

Citizen

G2G

B2C

C2CB2B

G2CB2G


4

Business Process Modeling

Traditional Business Process Modeling How does the flow of data look like in order to fulfill customer requirements and

who is responsible for these tasks? How does the organizational structure look like?

Recent Business Process Modeling Interorganizational Business Process Modeling Capturing commitments and agreements between collaborating business partner Business processes from a global perspective

"A business process is defined as an organized group of related activitiesthat together create customer value" Hammer and Champy


5

We are going to talk about …

UN/CEFACT‘s Modeling Methodology (UMM)


6

UN and e-Business?

To maintain international peace and security

To develop friendly relations among nations

To achieve international co-operation


7

UN Layout Key


8

ApplicationApplication ApplicationApplication

Goal: Exchange of business related data,independent of software, hardware and communication protocols

Goal: Exchange of business related data,independent of software, hardware and communication protocols

EDIEDI EDIEDI

Electronic Data Interchange (EDI)


9

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

UN/EDIFACT

ebXML

UMM & CC

UN Layout Key


10

Open-edi Reference Model – ISO 14662

Functional Service View

Business aspects of

business transactions

Information technology aspects of


Transformed To

Business Operational View

Functional Service View

Business aspects of


Information technology aspects of


BU

SIN

ES

S T

RA

NS

AC

TIO

NS

BOV RelatedStandards

FSV RelatedStandards

UN/CEFACT`s ModelingMethodology (UMM)

UN/EDIFACTWeb Services

ebXML

viewedas

comply with

covered by

comply with

covered by


11

UN/CEFACT‘s Modeling Methodology (UMM)

Customizing UML for modeling B2B Independent of the IT platform, concentrates on business semantics 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

UMMUMM

BDVBusiness

Domain View

BDVBusiness

Domain View

BRVBusiness

Requirements View

BRVBusiness

Requirements View

BTVBusiness

Transaction View

BTVBusiness

Transaction View


12

Import AuthorityExport Authority

UMM Add-In in Action European crossborder waste management

Notifier Notifiee

Announce Waste TransportAnnounce Transport Arrival

accept/reject


13

Top-level UMM Packages<<BusinessDomainView>>

<<BusinessArea>>

<<BusinessRequirementsView>>

<<BusinessProcessView>>

<<BusinessEntityView>>

<<TransactionRequirementsView>>

<<CollaborationRequirementsView>>

<<CollaborationRealizationView>>

<<BusinessTransactionView>>

<<BusinessInteractionView>>

<<BusinessChoreographyView>>

<<BusinessInformationView>>


14

UMM by example - BRVud 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»

«participates»«participates»

<<

ma

psT

o>>

<<mapsTo>> <<mapsTo>>

<<

ma

psT

o>>


15

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

ImporterExportAuthority

ImportAuthority

Exporter

UMM by example – Business Partner


16

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


17


<<BusinessArea>>












18

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

BTUC

BTUC

BCUC

<<m

apsT

o>>

<<mapsTo>>

<<mapsTo>>


19


<<BusinessArea>>












20

Motivation for standardizing the exchanged data

SOAP message

Importer

announce waste transport

announce transport arrival

check waste statusEnterprise Application

Exporter

Enterprise Application



WSDL

WSDLWSDL

WSDL

WSDL

SOAP message

SOAP message

UDDI registry


21

Motivation for standardizing the exchanged data

SOAP message

Order processing of enterprise X

request for quote

place order

check order statusEnterprise Application

Customer Y




WSDL

WSDL

WSDLWSDL

WSDL

SOAP message

SOAP message

UDDI registry

SOAP Message

SOAP Body

SOAP Header

Message Body


22

Motivation Problem domain

Business documents exchanged in business processes in a service oriented context

UN/CEFACT provides a generic solutions Core Components Technical Specification (CCTS) Almost no tool support possible - CCTS are standardized as spread sheets

UML profile for core components We are actively participating in the standardization Seamless integration into UML modeling tools possible Seamless integration into e.g. process specific models possible (UMM)


23

Harmonizing the exchanged data Known standardization efforts

UN/EDIFACT XML based solutions (e.g. 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 reengineering

Solution Usage of Core Components to model the exchanged information


24

Core Components

Are the central building blocks of the Core Component Technical Specification (CCTS)

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


25

A Core Component Example

«ACC»TransportMeans

«BCC»+ Identification: Identifier [0..*]+ Type: Code [0..*]+ Type: Text [0..*]

«ACC»TransportMode

«BCC»+ Type: Code [0..*]+ Type: Text [0..*]

«ACC»Party

«BCC»+ Access Rights: Code [0..*]+ Classification: Code [0..*]+ Description: Text [0..*]+ Identification: Identifier [0..*]+ Language: Code [0..*]+ Name: Text [0..*]+ Role: Code [0..*]+ Type: Code [0..*]

«ACC»MovementForm

«BCC»+ TransportNumber: Identifier+ IdentificationNumber: Identifier

«ACC»Period

«BCC»+ Complete: Date Time [0..1]+ Description: Text [0..*]+ Duration: Measure [0..*]+ End: Date Time [0..1]+ Identification: Identifier [0..*]+ Inclusive: Indicator [0..1]+ Open: Indicator [0..1]+ Season: Code [0..*]+ Start: Date Time [0..1]

+Movement

«ASCC»

+Carrier

«ASCC»

+Transport

«ASCC»

+Movement

«ASCC»


26

Business Information Entities

«ABIE»Waste_MovementForm

«BBIE»+ TransportNumber: IdentifierNumber+ IdentificationNumber: IdentifierNumber

«ABIE»Period

«BBIE»+ End: DateTime+ Start: DateTime

«ABIE»TransportMeans

«BBIE»+ Identification: Identifier

«ABIE»TransportMode

«BBIE»+ Type: Text+ TypeCode: Code

«ABIE»Party

«BBIE»+ Description: Text+ Identification: PartyIdentifier

+Waste_Carrier

«ASBIE»

+Waste_Movement

«ASBIE»

+Waste_Movement

«ASBIE»

+Waste_Transport

«ASBIE»


27

Interdependency between Core Components and Business Information Entities

«ACC»TransportMeans

«BCC»+ Identification: Identifier [0..*]+ Type: Code [0..*]+ Type: Text [0..*]

«ACC»TransportMode

«BCC»+ Type: Code [0..*]+ Type: Text [0..*]

«ACC»Party

«BCC»+ Access Rights: Code [0..*]+ Classification: Code [0..*]+ Description: Text [0..*]+ Identification: Identifier [0..*]+ Language: Code [0..*]+ Name: Text [0..*]+ Role: Code [0..*]+ Type: Code [0..*]

«ACC»MovementForm

«BCC»+ TransportNumber: Identifier+ IdentificationNumber: Identifier

«ACC»Period

«BCC»+ Complete: Date Time [0..1]+ Description: Text [0..*]+ Duration: Measure [0..*]+ End: Date Time [0..1]+ Identification: Identifier [0..*]+ Inclusive: Indicator [0..1]+ Open: Indicator [0..1]+ Season: Code [0..*]+ Start: Date Time [0..1]

+Movement

«ASCC»

+Carrier

«ASCC»

+Transport

«ASCC»

+Movement

«ASCC»



«ABIE»Period






«ABIE»Party


+Waste_Carrier

«ASBIE»

+Waste_Movement

«ASBIE»

+Waste_Movement

«ASBIE»

+Waste_Transport

«ASBIE»

Core Components (CC) Business Information Entities (BIE)

BIEs are derived from CCs by restriction


28

Derivation of XSD artifacts



«ABIE»Period






«ABIE»Party


+Waste_Carrier

«ASBIE»

+Waste_Movement

«ASBIE»

+Waste_Movement

«ASBIE»

+Waste_Transport

«ASBIE»

Business Information Entities (BIE)

UN/CEFACTNaming and Design Rules

<xsd:complexType name="Waste_MovementForm"> <xsd:sequence> <xsd:element name= "TransportNumber" type="udt1:IdentifierNumber"/> <xsd:element name="IdentificationNumber" type="udt1:IdentifierNumber"/> <xsd:element name="Waste_Transport_Period" type="bie1:PeriodType"/> <xsd:element name="Waste_Movement_TransportMeans" type="bie1:TransportMeansType"/> <xsd:element name="Waste_Carrier_Party" type="bie1:PartyType"/> <xsd:element name="Waste_Movement_TransportMode" type="bie1:TransportModeType"/> </xsd:sequence></xsd:complexType>


29

The UMM Add-In

First prototypical implementation which supports The UMM approach The UML profile for core components 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


30

UMM Add-In Overview

Semi automatic artifact generation

Requirements EngineeringSupport

Model validation

Transformation tochoreography languages

Core Components supportUMM Add-In

UMM specific toolbar


31

<<BusinessPartner>>

uc Actualization

ExportAuthority


«BusinessProcess»Pre-Inform on

Waste Transport

Exporter


«participates»

«participates»

<XML>UMM-specific toolbar

Requirements Engineering – UMM Worksheets


32

Valid?

[yes]

[no]

act Announce Waste Transport

Responder :Notifiee

«BusinessTransactionSw imlane»

Requestor :Notifier


«RequestingInformationEnvelop...:WasteMov ementFormEnv elope

«RespondingBusinessActiv ity»Process Waste Mov ement Form

«RequestingBusinessActiv ity»Notify Waste Transport

«InformationEnvelope»:WasteMov ementResponseEnv elope

[Success][Failure]


Responder :Notifiee


Requestor :Notifier






[Success][Failure]


Responder :Notifiee


Requestor :Notifier






[Success][Failure]

UMM Add-In – BPEL/BPSS Generator

<BPEL><BPSS>

Validating UMM Model


Responder :Notifiee


Requestor :Notifier






[Success][Failure]

Semi-automatic generation of UMM artifacts

Transformation into Choreography Languages

UMM Validation


33

Future Research Issues

Development of UMM 2.0 based on UML 2.0 Development of a UML profile for the Core Component Technical

Specification 3.0 Writing the "UMM @ Work" book

Adaptation of the tool support to the new standards Building a repository for modeling artifacts


34

EU funded project within FP6 Boost eGovernment awareness and knowledge Raise awareness of interoperability and cooperation

Interoperability Framework Demonstration Prototypes WeGo Academies Knowledge Net


35

UMM & We-Go I

High need for clear and structured modeling and description of processes in eGovernment

Interoperability issues when establishing cross-organizational services

Business

Government

Citizen

G2G

C2CB2B

G2CB2G


36

UMM & We-Go II

Cross-organizational processes in WeGo: eAdministration, eJustice, eCustoms

Success depends on appropriate design and specification of processes

Specification to follow general, well-accepted design principles Uniform structure and modeling of inter-organizational processes helps

to increase business process interoperability UMM is a methodology for the unambiguous definition of such

processes UMM knowledge transfer via WeGo Knowledge Net: tutorials,

specifications, business process models for re-use


37

Conclusion & Summary

We showed how

UMM can be used to model interorganizational business processes

the UML Profile for Core Components can be used to model the information exchanged in an inter-organizational business process

the UMM Add-In supports the modeler in modeling UMM and CCTS artifacts

UMM and CCTS can be used in the eGovernment context


38

INITS Award 2006 - 1st place for the best ICT master thesis in Austria


39

Thank you for your attention

<Lecturer><Name>Dr. Klaus Gschwendtner</Name><Name>Philipp Liegl</Name><Name>Rainer Schuster</Name><Company>Research Studios Austria</Company><Department>Intelligent Business Process Management Group</Department><Address>

<Street>Thurngasse 8/20</Street><ZIP>1090</ZIP><City>Vienna</City><Country>Austria</Country>

</Address><Contact>

<Telephone>+43 1 585 0537 12 </Telephone><Email>[email protected]</Email><Email>[email protected]</

Email>

<Http>http://ummaddin.researchstudio.at</Http></Contact><? Presentation status=“questions” ?>

</Lecturer>

<Lecturer><Name>Robert Mosser</Name><Company>University of Vienna</Company><Department>Institute of Distributed and Multimedia Systems</Department><Address>

<Street>Liebiggasse 4/3-4</Street><ZIP>1010</ZIP><City>Vienna</City><Country>Austria</Country>

</Address><Contact>

<Telephone>+43 1 4277 39623 </Telephone><Email>[email protected]</Email>

<Http>http://www.cs.univie.ac.at/robert.mosser</Http></Contact><? Presentation status=“questions” ?>

</Lecturer>

Austrian Research Centers GmbH - ARCIntelligent Business Process Management Group 1 Modeling...

Documents

Transcript of Austrian Research Centers GmbH - ARCIntelligent Business Process Management Group 1 Modeling...