1 / 7

Challenge 1: Composition of Processes...

This text discusses challenges in the composition and integration of processes, data, and components. It explores topics such as data warehouses, web data wrapping, reuse of components, autonomy of megamodules, heavy-weight services, non-technical domain experts, and the need for a purely compositional language.

woodrowperez
Download Presentation

Challenge 1: Composition of Processes...

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. Challenge 1: Composition of Processes... • versus composition and integration of Data • data-warehouses • wrapping data available on web • versus composition of Components • reusing small components via copy/paste or shared libraries locally installed • large distributed components within same “domain” as composition, e.g. within one bank or airline CHAIMS:»processed information provided by megamodules » composing autonomous execution threads CHAIMS

  2. I/O I/O Data Resources Local Components, Remote Data Domain expert Client computer Control & Computation Services c e a b d Wrappers to resolve differences CHAIMS

  3. MEGA modules Sites Data Resources Remote Computational Components Domain expert Client workstation IO module IO module C Computation Services e b a d T c S U T R CHAIMS

  4. Challenge 2: Autonomy Megamodule C at site NewCom provided by BestCalc Megamodules are autonomous: • responsibility for maintenance is with provider • client has no direct control over availability of services and resources provided • client might be able to choose from several providers • heterogeneity concerning implementation languages, interface definitions (onthologies), server platforms and distribution systems ==> many advantages, yet access protocols and composition environments have to take these issues into account Megamodule A at site Stanford provided by InfoLab Megamodule B at site SLAC provided by Admin CHAIMS

  5. Challenge 3: Heavy-weight Services What we need: ==>monitoring progress of a service ==> possibility to choose among equivalent services based on estimated waiting time and fees ==>parallelism among services ==> preliminary overview results, choosing level of accuracy / number of results for complex processes ==> novel optimization techniques Services are not free for a client: • execution time of a service • transfer time for data • fees for services CHAIMS

  6. Challenge 4:Non-technical Domain Experts “Composer”: • is domain expert of domain that uses these services • is not technical expert of middleware system or experienced programmer, • wants to focus on problem at hand (=results of using a megaprogram) • e.g. scientist, assistant of a general Company providing services: • domain experts of domain of service (e.g. weather) • technical experts for wrapping services, setting up servers in a middleware system • marketing experts CHAIMS

  7. Challenge 5: Purely Compositional Language Possible? Which languages did succeed? • Algol, ADA: integrated composition and computation • C, C++: focus on computation Why new language? • complexity: not all facilities of a common language (compare to approach of Java), • inhibiting traditional computational programming (compare C++ and Smalltalk concerning object-oriented programming) • focus on issue of composition, parallelism by asynchrony, and optimization CHAIMS

More Related