On-the-Fly Computing a new Paradigm for Software Development and Operation

Transcription

1 On-the-Fly Computing a new Paradigm for Software Development and Operation Gregor Engels University of Paderborn 1 July 10, 2013 SATToSE 2013, Bern (CH)

2 That s my life Gregor Engels engels@upb.de University of Paderborn Information Systems Group s-lab Software Quality Lab C-LAB Cooperative Computing & Communication Laboratory Capgemini, CSD Research, Munich 2 July 10, 2013 SATToSE 2013, Bern (CH)

3 The Vision of On-The-Fly Computing 10s Analysis & Decomposition 10s 10s Specific & Individual Wish Configuration On-The-Fly Matching 7s Analysis & Functionality Check Market 10s Search for Matching Services 7s 3 July 10, 2013 SATToSE 2013, Bern (CH) Custom-made Product

4 Software Market of the Future Service Requestor Service Provider provided interface Service 1 Service 2 required interface? How to find? efficient / effective search appropriate matching 4 July 10, 2013 SATToSE 2013, Bern (CH) How to be found? high fitting accuracy high reputation

5 Collaborative Research Center (CRC) funded by DFG (Deutsche Forschungsgemeinschaft) ( ) 50 scientists (computer science, economics) 5 July 10, 2013 SATToSE 2013, Bern (CH)

6 SFB 901: Structural Overview Project Area A Algorithmic and Economic Foundations A1: Local Strategies in Dynamic Networks A2: Overlays over Physical Networks A3: Market of Services Project Area B Modeling, Composition & Quality Analysis of Services B1: Parametric Service Specifications B2: Configuration & Rating B3: Composition Analysis in Uncertain Contexts B4: Proof-Carrying Services Project Area C Reliable Runtime Environments & Application Scenarios C1: Robustness & Security C2: On-The-Fly Compute Centers C3: Modeling of Optimization Problems 6 July 10, 2013 SATToSE 2013, Bern (CH)

7 Project Area B: Structural Overview Project Area A Algorithmic and Economic Foundations Project Area C Reliable Runtime Environments & Application Scenarios Project Area B Modeling, Composition & Quality Analysis of Services B1: Parametric Service Specifications B2: Configuration & Rating B3: Composition Analysis in Uncertain Contexts B4: Proof-Carrying Services 7 July 10, 2013 SATToSE 2013, Bern (CH)

8 Project Area B: Modeling, Composition & Quality Analysis of Services B1 Languages B2 Configuration?A 10s B1 Matching TripPlanner GoogleMaps PaderTouristik Client Rating PaderSprinter B3 Analysis 8 July 10, 2013 SATToSE 2013, Bern (CH) OTF Market A B B1 Languages B4 10s Certification

9 Subproject B1: Parametric Service Specifications Goal Enable the specification of service requests of a client and provided services in OTF Markets and the matching between them 9 July 10, 2013 SATToSE 2013, Bern (CH)

10 ?A Subproject B1: Parametric Service Specifications Example 10s Client WSDL UML Statechart BPEL? OTF Market 10 July 10, 2013 SATToSE 2013, Bern (CH) WSDL MoveMeAround App Petri Net RDSEFF

11 Subproject B1: Parametric Service Specifications Example WSDL UML Statechart BPEL?A? Client OTF Market 11 July 10, 2013 SATToSE 2013, Bern (CH) WSDL Petri Net RDSEFF TripPlanner? IDL Statechart Rating BPEL??? WSDL Statechart RDSEFF GoogleMaps WSDL Story PaderTouristik Diagram BPEL WSDL PaderSprinter Statechart Sequence D.

12 Hotel Reservation at HRS How it works HRS: Hotel Reservation Service Zille Huma et al. Towards an Automatic Service Discovery for UML-based Rich Service Descriptions MODELS'12 12

13 Rich Service Descriptions & Automatic Matching Service Requestor Service Provider {pre} op1( ) {post} Rich Service Request Structural Aspects: op1(p1:a) op2(p1:b):a op3(p1:c) Behavioral Aspects: loop call op1( ); call op2( ); call op3( ); {pre} opa( ) {post} Rich Service Offer Service Offer Structural Aspects: opa(p1:x) opb(p1:y):x opc(p1:z) Behavioral Aspects: (opa( ) opb( ) opc( ) )* 13 Zille Huma et al. Towards an Automatic Service Discovery for UML-based Rich Service Descriptions MODELS'12

14 HRS Service Request Hotel X Service Offer (a) - checkavailability( ) - viewdetails( ) - makereservation( ) - makepayment( ) (a) -getavailableroom( ) -makeabooking( ) -validatecredentials( ) -payforbooking( ) (b) (c) Matching Parameters Ontological Heterogeneity (b) Operation Matching (1:1, 1:n, n:1, n:m) Protocol Matching Service Composition (c) typed over OTA-based Local Ontology HarmoNET-based Local Ontology typed over 14 Zille Huma et al. Towards an Automatic Service Discovery for UML-based Rich Service Descriptions MODELS'12

15 1 Requestor operation Provider Protocol 2 Result=validateCredentials( ) 3 Result = Result + payforbooking( ) 15 Zille Huma et al. Towards an Automatic Service Discovery for UML-based Rich Service Descriptions MODELS'12

16 1 Requestor operation Provider Protocol 2 Result=validateCredentials( ) 3 Result = Result + payforbooking( ) 4 Result = validatecredentials( ) + payforbooking( ) 16 Zille Huma et al. Towards an Automatic Service Discovery for UML-based Rich Service Descriptions MODELS'12

17 HRS & Hotel X Operation Mappings 17 Zille Huma et al. Towards an Automatic Service Discovery for UML-based Rich Service Descriptions MODELS'12

18 Subproject B1: Parametric Service Specifications Example WSDL UML Statechart BPEL?A? Client ICSOB 2013, Potsdam OTF Market WSDL Petri Net RDSEFF TripPlanner? IDL Statechart Rating BPEL??? WSDL Statechart RDSEFF GoogleMaps WSDL Story PaderTouristik Diagram BPEL WSDL PaderSprinter Statechart Sequence D.

19 Subproject B1: Parametric Service Specifications Approach parametric core language Behavior Protocols Performance Contracts matching mapping-by-example 19 July 10, 2013 SATToSE 2013, Bern (CH) PetriNets UML Statecharts Visual Contracts concrete languages

20 Vision: OTF Computing in 2023 A1 A2 A3 OTF Service Provider for Optimization Project Area A Algorithmic & Model Economic Foundations Data Management User Generation Model Solver Project Area B Modeling, Composition & Visualization Quality Analysis Decision Support System B1 B2 B3 B4 OTF Service Provider for Optimization 20 July 10, 2013 SATToSE 2013, Bern (CH) Project Area C Reliable Execution Environments & Application Scenarios ROKA GS Plant Simulation C1 C2 C3 OTF Compute Center

21 Software Market of the Future Service Requestor Service Provider provided interface Service 1 Service 2 required interface? How to find? efficient / effective search appropriate matching 21 July 10, 2013 SATToSE 2013, Bern (CH) How to be found? high fitting accuracy high reputation

22 Software Market of the Future Business Architecture Business Services provided interface Service Provider Service 2 Enterprise Architecture Business / IT alignment IT Architecture 22 July 10, 2013 SATToSE 2013, Bern (CH) IT services How to be found? high fitting accuracy high reputation

23 A Method for Designing IT-Services Business Architecture Business Services Enterprise Architecture Business / IT alignment IT Architecture 23 July 10, 2013 SATToSE 2013, Bern (CH) IT services

24 Integrated Architecture Framework (IAF) Integrated Architecture Framework (IAF), Capgemini 24 July 10, 2013 SATToSE 2013, Bern (CH)

25 Integrated Architecture Framework (IAF) Enterprise Architecture Business Architecture Alignment IT Architecture 25 July 10, 2013 SATToSE 2013, Bern (CH) Integrated Architecture Framework (IAF), Capgemini

26 A Method for Designing IT-Services Architectural Aspects Business Aspects Business Information Information system IT Aspects Technical Infrastructure Principles Questions Analysis Design Why? What? How? With what? What are the business services? How is the business logically structured? What are the relevant operational business units? Integrated Architecture Framework (IAF), Capgemini 26 July 10, 2013 SATToSE 2013, Bern (CH) What are strategic goals, principles, context? What is the relevant information? How is the information logically structured? How is the information managed? What are the relevant IT services? How are the services logically structured into components? How are the components physically realized? What are the relevant technical services? How are the technical services logically structured into TIcomponents? How are the TI-components physically realized? Architecture Solution

27 Example Application Domain: Travel Agency Christopher Columbus Travel (CCT) fictitious travel agency sells package travels and (individual) custom travels 27 July 10, 2013 SATToSE 2013, Bern (CH)

28 Identification of Level 1 business services Def. Level 1 business services Internally and externally offered core services of an enterprise to fulfill its business objectives. Evaluate last travel season and plan new one 28 July 10, 2013 SATToSE 2013, Bern (CH) Buy hotel beds and flight seats Design travel packages and fix a price Book travels Help customers before, during, after travel

29 Refined Business Services Notation: UML-like Use Case Diagram 29 July 10, 2013 SATToSE 2013, Bern (CH)

30 A Method for Designing IT-Services Architectural Aspects Business Aspects Business Information Information system IT Aspects Technical Infrastructure Principles Questions Analysis Design Why? What? How? With what? What are the business services? How is the business logically structured? What are the relevant operational business units? Integrated Architecture Framework (IAF), Capgemini 30 July 10, 2013 SATToSE 2013, Bern (CH) What are strategic goals, principles, context? What is the relevant information? How is the information logically structured? How is the information managed? What are the relevant IT services? How are the services logically structured into components? How are the components physically realized? What are the relevant technical services? How are the technical services logically structured into TIcomponents? How are the TI-components physically realized? Architecture Solution

31 Def. Designing Domains Domain business-oriented clustering of components of an application domain maybe hierachically structured components are associated to leaf domains 31 July 10, 2013 SATToSE 2013, Bern (CH) Notation: UML-like Package and Component Diagrams

32 Core business services are candidate domains Planning Purchasing Production Sales Support 32 July 10, 2013 SATToSE 2013, Bern (CH)

33 Domains of Christopher Columbus Travel derived from business objects 33 July 10, 2013 SATToSE 2013, Bern (CH) derived from supporting business services

34 Categories of IT services Def. IT service is a business service (or part of it) which is realized by a software application Def. Categories of IT services data: managing business objects function: providing algorithmic business logic process: providing flow-oriented business logic interaction: allowing users to interact with applications Examples: Categories of IT services data: Maintain customer function: Select resource process: Book custom travel interaction: Compose custom travel 34 July 10, 2013 SATToSE 2013, Bern (CH)

35 Domains with associated categorized IT services CCT TRA INT xxxx CCE xxxx xxxx Sell custom travel Compose custrom travel xxxx xxxx xxxx PLA PUR PCT Recommed resource BOK SRV Select resource Check plausibility Compose custom offer Book custom travel PPT RSM Check Availability Book resource CUM Maintain customer ORM Maintain travel order ACC YYY Legend domain 35 July 10, 2013 SATToSE 2013, Bern (CH) xxx application service REP xxxx xxxx xxxx PER.. of category interaction.. of category function.. of category process.. of category data

36 Designing components Def. Component realizes IT services has explicit interfaces for provided and requested operations 36 July 10, 2013 SATToSE 2013, Bern (CH)

37 Determine candidate components and refine Candidate component All IT services of the same domain and category become a candidate component Design Rules for refining candidate components a component belongs to exactly one domain. all operations of a component shall be of the same category. business logic that changes at a different pace shall be separated. components of category data have responsibility of business objects. components shall not have cyclic dependencies. components of different categories shall have layered dependencies according to interaction process function data. components shall have low coupling and high cohesion. 37 July 10, 2013 SATToSE 2013, Bern (CH)

38 Final components of Christopher Columbus Travel 38 July 10, 2013 SATToSE 2013, Bern (CH)

39 Designing interfaces Design rules for interfaces and operations business-oriented: every operation shall provide business logic only and must not reveal implementation details. coarse-grained: operations shall comprise as much business logic as possible. idempotent: multiple invocations of an operation with the same parameters shall have the same effect as a single invocation. compensating: for each operation there shall be a compensating operation which undoes its business implications. context free: operations shall have minimal knowledge on the context in which they are invoked (session context, transaction context, batch / online). 39 July 10, 2013 SATToSE 2013, Bern (CH)

40 Software Market of the Future Service Requestor Service Provider provided interface Service 1 Service 2 required interface? How to find? efficient / effective search appropriate matching 40 July 10, 2013 SATToSE 2013, Bern (CH) How to be found? high fitting accuracy high reputation

41 The Vision of On-The-Fly Computing 10s Analysis & Decomposition 10s 10s Specific & Individual Wish Configuration On-The-Fly Matching 7s Analysis & Functionality Check Market 10s Search for Matching Services 7s Custom-made Product 41 July 10, 2013 SATToSE 2013, Bern (CH)

42 Thank you for your attention! Prof. Dr. Gregor Engels University of Paderborn Zukunftsmeile Paderborn Germany Phone: / engels@upb.de Web: 42 July 10, 2013 SATToSE 2013, Bern (CH)