1 / 18

Arguments for Open Structure Execution Services

Arguments for Open Structure Execution Services Jessica Rubart 1 , Weigang Wang 1 , Jörg M. Haake 2 1 Fraunhofer Institute for Integrated Publication and Information Systems (IPSI), Darmstadt, Germany 2 FernUniversität Hagen, Hagen, Germany. Contents. EXTERNAL Object-oriented Software

Download Presentation

Arguments for Open Structure Execution Services

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. Arguments for • Open Structure Execution Services • Jessica Rubart1, Weigang Wang1, Jörg M. Haake2 • 1Fraunhofer Institute for Integrated Publication and Information Systems (IPSI), Darmstadt, Germany • 2FernUniversität Hagen, Hagen, Germany

  2. Contents • EXTERNAL • Object-oriented Software • Integration of Execution Services in the Concept of Open Service Provision • OHS Services and Web Services • Discussion

  3. EXTERNAL • EXTended Enterprise Resources, Network Architectures and Learning • EU project with five partners • Shared workspaces for supporting EEs • Hypermedia-based knowledge model integrated with process support • Methodology, infrastructure, and tools • Three real world use cases

  4. Extended Enterprise EXTERNAL Infrastructure Integration

  5. EE Infrastructure and Tools • Services • EXTERNAL shared repository • Collaboration services • Modeling services • Simulation service • Operational services (Execution)

  6. Infrastructure – Abstract View • Open Protocol for Work Process Support based on a hypermedia data model and represented with XML

  7. Integration of Services

  8. Integration of Services

  9. Integration of Services

  10. Integration of Services

  11. EXTERNAL - Summary • Repository services incorporate foundation services and a kind of structure service • Workware, SimVision and XCHIPS provide execution services on a workflow structure • Number of execution services provided by them is growing • Abstraction for execution services useful

  12. Object-oriented Software • Structure plays an important role • UML standard notation for modeling • Execution functionality, such as code generation or generating documentation • The same structure can be executed in several ways • Abstraction for execution services useful

  13. Integration in „Open Service Provision“ [Wiil et al.]

  14. Integration in „Open Service Provision“ [Wiil et al.] • Separate layer is open to any number of execution services • Neither structure services nor applications have to implement them • Where to put the execution services layer when considering a separate cooperation services layer (proposed by Tata et al.)? On top.

  15. OHS Services and Web Services • Make business functions readily sharable (through WSDL, SOAP, Java, XML, messaging APIs)

  16. OHS Services and Web Services • Compose them into composite services or link them into a flexible process flow (using e.g. XLANG or WSFL) • Deliver it in the right format (e.g. XML, Java, WML) • Make them discoverable and available to others anywhere (using UDDI standard)

  17. Discussion • Reference Architecture: Separate Execution Layer? • Where to put? • Integration of user interfaces • Distribution of execution services • Web Services: • Develop? • Learn from? • Utilize?

  18. Thanks Thanks for your attention!

More Related