1 / 39

Modeling e-Government processes with UMM

Modeling e-Government processes with UMM. Dr. Klaus Gschwendtner Philipp Liegl Rainer Schuster Research Studios Austria Austrian Research Centers - ARC philipp.liegl@researchstudio.at rainer.schuster@researchstudio.at. Robert Mosser Institute for Distributed and Multimedia Systems

haines
Download Presentation

Modeling e-Government processes with UMM

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. Modeling e-Government processes with UMM Dr. Klaus Gschwendtner Philipp Liegl Rainer Schuster Research Studios Austria Austrian Research Centers - ARC philipp.liegl@researchstudio.at rainer.schuster@researchstudio.at Robert Mosser Institute for Distributed and Multimedia Systems University of Vienna robert.mosser@univie.ac.at

  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. G2G Business processes in the eGovernment domain Government B2G G2C B2B Business Citizen C2C B2C • 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

  4. Business Process Modeling "A business process is defined as an organized group of related activities that together create customer value"Hammer and Champy • 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

  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. Electronic Data Interchange (EDI) Goal: Exchange of business related data, independent of software, hardware and communication protocols Application Application EDI EDI

  9. United Nations Centre for Trade Facilitationand e-Business (UN/CEFACT) UN Layout Key UN/EDIFACT ebXML UMM & CC

  10. Open-edi Reference Model – ISO 14662 UN/CEFACT`s Modeling Methodology (UMM) UN/EDIFACT Web Services ebXML Business Operational View comply with BOV Related Standards Business aspects Business aspects of of business transactions business transactions covered by BUSINESSTRANSACTIONS Transformed To viewedas Functional Service View Functional Service View comply with Information technology FSV Related Standards Information technology aspects of aspects of business transactions business transactions 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 UMM BDVBusiness Domain View BRVBusiness Requirements View BTVBusiness Transaction View

  12. UMM Add-In in Action • European crossborder waste management Import Authority Export Authority Notifier Notifiee accept/reject Announce Transport Arrival Announce Waste Transport

  13. Top-level UMM Packages <<BusinessDomainView>> <<BusinessArea>> <<BusinessRequirementsView>> <<BusinessProcessView>> <<BusinessEntityView>> <<TransactionRequirementsView>> <<CollaborationRequirementsView>> <<CollaborationRealizationView>> <<BusinessTransactionView>> <<BusinessInteractionView>> <<BusinessChoreographyView>> <<BusinessInformationView>>

  14. UMM by example - BRV <<mapsTo>> <<mapsTo>> <<mapsTo>> <<mapsTo>>

  15. UMM by example – Business Partner <<BusinessPartner>> <<BusinessPartner>> <<BusinessPartner>> <<BusinessPartner>> Import Authority Export Authority Importer Exporter

  16. UMM by example - BRVSubview: CollaborationRealizationView

  17. Top-level UMM Packages <<BusinessDomainView>> <<BusinessArea>> <<BusinessRequirementsView>> <<BusinessProcessView>> <<BusinessEntityView>> <<TransactionRequirementsView>> <<CollaborationRequirementsView>> <<CollaborationRealizationView>> <<BusinessTransactionView>> <<BusinessInteractionView>> <<BusinessChoreographyView>> <<BusinessInformationView>>

  18. UMM by example - BTV <<mapsTo>> <<mapsTo>> BTUC BTUC <<mapsTo>> BCUC

  19. Top-level UMM Packages <<BusinessDomainView>> <<BusinessArea>> <<BusinessRequirementsView>> <<BusinessProcessView>> <<BusinessEntityView>> <<TransactionRequirementsView>> <<CollaborationRequirementsView>> <<CollaborationRealizationView>> <<BusinessTransactionView>> <<BusinessInteractionView>> <<BusinessChoreographyView>> <<BusinessInformationView>>

  20. Motivation for standardizing the exchanged data Enterprise Application Enterprise Application EnterpriseApplication Enterprise Application Exporter Importer announce waste transport WSDL WSDL SOAP message announce transport arrival WSDL SOAP message check waste status WSDL WSDL SOAP message UDDI registry

  21. Motivation for standardizing the exchanged data Enterprise Application Enterprise Application EnterpriseApplication Enterprise Application Customer Y Order processing of enterprise X request for quote WSDL WSDL SOAP message SOAP Message place order SOAP Header WSDL SOAP message SOAP Body Message Body check order status WSDL WSDL SOAP message UDDI registry

  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

  26. Business Information Entities

  27. Interdependency between Core Components and Business Information Entities Core Components (CC) Business Information Entities (BIE) BIEs are derived from CCs by restriction

  28. Derivation of XSD artifacts UN/CEFACTNaming and Design Rules Business Information Entities (BIE) <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

  31. Requirements Engineering – UMM Worksheets <<BusinessPartner>> <XML> UMM-specific toolbar

  32. Semi-automatic generation of UMM artifacts <BPEL> <BPSS> [yes] [no] Valid? Transformation into Choreography Languages UMM Add-In – BPEL/BPSS Generator Validating UMM Model 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. G2G UMM & We-Go I • High need for clear and structured modeling and description of processes in eGovernment • Interoperability issues when establishing cross-organizational services Government B2G G2C B2B Business Citizen C2C

  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>philipp.liegl@researchstudio.at</Email> <Email>rainer.schuster@researchstudio.at</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>robert.mosser@univie.ac.at</Email> <Http>http://www.cs.univie.ac.at/robert.mosser</Http> </Contact> <? Presentation status=“questions” ?> </Lecturer>

More Related