1 / 42

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

kiet
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. Procedure Model 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 and Relationships 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 Analyse Documents Componenets • Name and Business Rule • Cardinality and Type • Structure or Content • 4.3 Assemble Document Components

  20. Analysis – 4th Step – Data View Identification of Business Objects

  21. Analysis – 4th Step – Data View Identification of Business Objects

  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 of Business 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 Operations are typecast as: One-Way Notification Request-response Solicit-response Activities are typecast as: invoke receive (sync) receive (async) reply (sync) reply (async)

  29. Design – 8th Step – Service OperationsDefinition of Services • As a Maximun all identified Service Operations of one role are taken together as a Service • As Minimum the Service Operations of one Business Transaction should be taken together as a Service • Logical Cohesion • Functional Cohesion • Data Cohesion

  30. Design – 8th Step – Service OperationsDefinition of Services • As a Maximun all identified Service Operations of one role are taken together as a Service • As Minimum the Service Operations of one Business Transaction should be taken together as a Service • Logical Cohesion • Functional Cohesion • Data Cohesion

  31. Design – 8th Step – Service OperationsConsolidation of Services

  32. Design – 8th Step – Service Landscape

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

  34. Implementation – 9th Step – Data ContractConcept of Data Contract Business Document Module 0..n 1 Business Object Module 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 Contract (Un)QualifiedDataTypes and CodeLists • Ich bin ein Screenshot der UDT, QDT und einer Enumeration

  36. Implementation – 9th Step – Data Contract Business Document as 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>

  37. Implementation – 10th StepImplementation of Service Contract

  38. Implementation – 10th StepImplementation of Service Contract

  39. Implementation – 11th Step Implementation of Service Interface • Ich bin ein wundervoller Screenshot

  40. Implementation – 12th Step Coding & Deployment of Web Services

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

  42. Thank you!

More Related