ITAIDE Information Technology for Adoption and Intelligent Design for E-Government

1. ITAIDE Information Technology for Adoption and Intelligent Design for E-Government SAP Research Switzerland, Project Manager

2. ITAIDE’s Work Packagesand Living Labs

3. Major export partners of the EU Community in 2007

4. Demand for e-tools in transport and trade • 175.000.000customsdeclarationsperyear • 480.000customsdeclarations per day • 333customsdeclarationsperminute • 5,5customsdeclarationspersecond

5. From Public Processes to Service DefinitionsA Method for the Model Driven Derivation of Service Interfaces SAP Research Switzerland, Andrea Fuchsloch, Diploma Student Institute ofTelematics IT-Management andWeb Engineering

6. Agenda • Motivation • Basics of Method Engineering • Meta Model • Procedure Model in theory and practice • SummaryandAchievements

7. Public Business Process= InterorganizationalCollaboration Government Collaboration Collaboration Company A Company B Collaboration

8. Purpose of the Thesis BPEL, WS-Security, XML Schema, WSDL, UDDI, SOAP, Rest, XML, HTTP/S G ? ? A B Finding a way for model driven derivation of services, starting from public business processes 8

9. ProcedureModel 1 Analysis of potentialities Meta Model Design and Choice of alternatives 2 Design ResultOutcome Planning and Implementation of Prototype 3 Techniques 4 Continuation Roles customer trainee mechanic secretary Arrange Appointment X Investigate Vehicle X X Order Parts x X Repair Vehicle x X Method EngineeringElements accordingtoGutzwiller Elements of a Method Quelle: Gutzwiller, T. A., Das CC RIM-Referenzmodell für den Entwurf von betrieblichen, transaktionsorientierten Informationssystemen Physica Verlag, Heidelberg 1994

10. Method EngineeringElements andRelationships is part of Meta-Model Design Result / Outcome represents problem-oriented view produces / consumes guides creation of predecessor / successor is part of Role (Design) Activity Technique participates in consists of supports Procedure Model Tool

11. Agenda • Motivation • Basics of Method Engineering • Meta Model • Procedure Model in theory and practice • SummaryandAchievements

13. Agenda • Motivation • Basics of Method Engineering • MetaModel • Procedure Model in theory and practice • SummaryandAchievements

14. Procedure Model Analysis Design Implementation

15. Procedure ModelAnalysis

16. Analysis – 1st Step – Process View Modeling of Use Cases

17. Analysis – 2nd Step – Process View Modeling of Activities

18. Analysis – 3rd Step – Message View Modeling of Communication

19. Analysis – 4th Step – Data View Identification of Business Objects 4.1 Set up documents repository 4.2 Analysedocuments componenets • Name and business rule • Cardinality and type • Structure or content 4.3 Assemble document components

20. Analysis – 4th Step – Data View Analyse Documents Componenets

21. Analysis – 4th Step – Data View Assemble Document Components

22. Design – 5th Step – Data View Specification of Business Objects

23. Design – 5th Step – Data View Consolidation of Business Objects

24. Procedure ModelDesign

25. Design – 6th Step – Business TransactionsIdentification ofBusiness Transactions

26. Design – 7th Step – Service OperationsIdentification of relevant Activities

27. Design – 7th Step – Service OperationsClassification of relevant Activities Activity invoke receive (sync) receive (sync) receive reply invoke receive receive(sync) receive(async) reply(sync) reply(async) reply (sync) reply (sync)

28. Design – 7th Step – Service OperationsClassification of relevant Activities InvokedOperations ProvidedOperations submitExportDeclaration(Request-Response) invoke receive (sync) receive (sync) InvokedOperations ProvidedOperations submitExportDeclaration (Request-Response) receive reply (sync) reply (sync)

29. Design – 7th Step – Service OperationsSpecification of In- and Output Parameter • Office of departure should provide a service operation: • submitExportDeclaration • Input parameter: Declaration • Output parameter : ControlResult

30. Design – 8thStep – Service OperationsDefinition of Services • As a maximumall identifiedserviceoperationsofonerolearetakentogetherin oneservice • As a minimumthe serviceoperationsofonebusinesstransactionshouldbetakentogetheras a service • Logical cohesion • Functionalcohesion • Data cohesion

31. Design – 8th Step – Service OperationsConsolidationofServices Before After

32. Design – 8th Step – Service Landscape Businesses BorderCrossingCustoms Customs Office ofDeparture Consignor Office of Exit Office of Transit Consignee Office of Destination

33. Procedure ModelImplementation

34. Implementation – 9th Step – Data ContractConceptof Data Contract Business DocumentModule 0..n 1 Business ObjectModule 1 1 1 Qualified Data Type Module Unqualified Data Type Module 1 1 1 Code List Module 0..n 0..n 0..n

35. Implementation – 9th Step – Data ContractCodeListsExample

36. Implementation – 9th Step – Data ContractUnqualified Data Type Example

37. Implementation – 9th Step – Data ContractBusiness DocumentModule Example

38. Implementation – 9th Step – Data Contract Business DocumentasXSD • <?xmlversion="1.0"?> • <!-- ===================================================================== --> • <!-- ===== CustomsDocument Module ===== --> • <!-- ===================================================================== --> • <!-- • Schema agency: ITAIDE (Andrea Fuchsloch) • Schema version: 1.0 • Schema date: 30. March 2009 • --> • <xs:schemaxmlns:xs="http://www.w3.org/2001/XMLSchema"xmlns:bom="http://www.my.business.object.module"xmlns:cdm="http://www.my.customs.document.module"targetNamespace="http://www.my.customs.document.module"> • <!-- ================================================================== --> • <!-- ===== Import of Business Objects Module ===== --> • <!-- ================================================================== --> • <xs:import namespace="http://www.my.business.object.module"schemaLocation="../BusinessObjectModule.xsd"/> • <!-- ================================================================== --> • <!-- ===== Type Definition: ExportDeclarationType ===== --> • <!-- ================================================================== --> • <xs:elementname="ExportDeclaration" type="cdm:ExportDeclarationType"/> • <xs:complexTypename="ExportDeclarationType"> • <xs:sequence> • <xs:elementname="ExportDeclaration" type="bom:DeclarationType"/> • </xs:sequence> • </xs:complexType> • </xs:schema>

39. Implementation – 10th Step – Service ContractImplementationofContract (graphically)

40. Implementation – 10th Step– Service ContractImplementationofService Contract

41. Implementation – 11th StepImplementationof Service Interface

42. Implementation – 12th Step Coding& Deploymentof Web Services

43. Implementation – 12th Step Coding& Deploymentof Web Services

44. Implementation – 12th Step Coding& DeploymentofWeb Services

45. Agenda • Motivation • Basics of Method Engineering • MetaModel • Procedure Model in theory and practice • SummaryandAchievements

46. Summary • Demo-Video

47. SummaryandAchievements completelyfulfilled insufficientlyfulfilled partiallyfulfilled

48. Thank you!