1 / 43

SAP Research Switzerland, Andrea Fuchsloch, Diploma Student

From Public Processes to Service Definitions A Method for the Model-Driven Derivation of Service Interfaces. SAP Research Switzerland, Andrea Fuchsloch, Diploma Student. Agenda. Motivation Basics of Method-Engineering Meta-Model Procedure Model 4.1. Analysis 4.2. Design

vaughan
Download Presentation

SAP Research Switzerland, Andrea Fuchsloch, Diploma Student

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. From Public Processes to Service DefinitionsA Method for the Model-Driven Derivation of Service Interfaces SAP Research Switzerland, Andrea Fuchsloch, Diploma Student

  2. Agenda • Motivation • Basics of Method-Engineering • Meta-Model • Procedure Model 4.1. Analysis 4.2. Design 4.3. Implementation • Summary

  3. Public Business Process= Interorganizational Collaboration Government Collaboration Collaboration Company A Company B Collaboration

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

  5. Agenda • Motivation • Basics of Method-Engineering • Meta-Model • Procedure Model 4.1. Analysis 4.2. Design 4.3. Implementation • Summary

  6. 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 Elements of a Method

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

  8. Agenda • Motivation • Basics of Method-Engineering • Meta-Model • Procedure Model 4.1. Analysis 4.2. Design 4.3. Implementation • Summary

  9. Meta-Model

  10. Agenda • Motivation • Basics of Method-Engineering • Meta-Model • Procedure Model 4.1. Analysis 4.2. Design 4.3. Implementation • Summary

  11. Procedure Model Analysis Design Implementation

  12. Procedure ModelAnalysis

  13. Procedure ModelDesign

  14. Procedure ModelImplementation

  15. Agenda • Motivation • Basics of Method-Engineering • Meta-Model • Procedure Model 4.1. Analysis 4.2. Design 4.3. Implementation • Summary

  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. Agenda • Motivation • Basics of Method-Engineering • Meta-Model • Procedure Model 4.1. Analysis 4.2. Design 4.3. Implementation • Summary

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

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

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

  26. Design – 6th Step – Business TransactionsSpecification of
Business Transactions ExportDeclaration ReleaseGoodsForExport

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

  28. Design – 7th Step – Service OperationsClassification of relevant Activities Operationsaretypecastas: One-Way Notification Request-response Solicit-response Activitiesaretypecastas: invoke receive (sync) receive (async) reply (sync) reply (async)

  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 Maximun all identified Service Operationsofonerolearetakentogetherin one Service. • As Minimum the Service Operationsofone Business Transaction shouldbetakentogetheras a Service • Data Cohesion • Logical Cohesion • FunctionalCohesion

  31. Design – 8thStep – Service OperationsDefinition of Services • As a Maximun all identified Service Operationsofonerolearetakentogetheras a Service • As Minimum the Service Operationsofone Business Transaction shouldbetakentogetheras a Service • Logical Cohesion • FunctionalCohesion • Data Cohesion

  32. Design – 8th Step – Service OperationsConsolidationofServices

  33. Design – 8th Step – Service Landscape

  34. Agenda • Motivation • Basics of Method-Engineering • Meta-Model • Procedure Model 4.1. Analysis 4.2. Design 4.3. Implementation • Summary

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

  36. Implementation – 9th Step – Data Contract (Un)QualifiedDataTypesandCodeLists • Ich bin ein Screenshot der UDT, QDT und einer Enumeration

  37. Implementation – 9th Step – Data Contract Business Documentas XSD • <?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>

  38. Implementation – 10thStep – Service ContractImplementationofContract(graphically)

  39. Implementation – 10thStep– Service ContractImplementationofService Contract

  40. Implementation – 11th StepImplementationof Service Interface • Ich bin ein wundervoller Screenshot

  41. Implementation – 12th Step Coding& DeploymentofWeb Services

  42. Agenda • Motivation • Basics of Method-Engineering • Meta-Model • Procedure Model 4.1. Analysis 4.2. Design 4.3. Implementation • Summary

  43. Thank you!

More Related