Scientific Workflow Interchanging Through Patterns: Reversals and Lessons Learned Bruno Fernandes Bastos Regina Maria Maciel Braga Antônio Tadeu Azevedo.

Slides:



Advertisements
Similar presentations
A Workflow Engine with Multi-Level Parallelism Supports Qifeng Huang and Yan Huang School of Computer Science Cardiff University
Advertisements

Architecture Representation
Key-word Driven Automation Framework Shiva Kumar Soumya Dalvi May 25, 2007.
Presented by: Thabet Kacem Spring Outline Contributions Introduction Proposed Approach Related Work Reconception of ADLs XTEAM Tool Chain Discussion.
Background information Formal verification methods based on theorem proving techniques and model­checking –to prove the absence of errors (in the formal.
Object-Oriented Analysis and Design
Architecture-driven Modeling and Analysis By David Garlan and Bradley Schmerl Presented by Charita Feldman.
1 Ivan Lanese Computer Science Department University of Bologna Roberto Bruni Computer Science Department University of Pisa A mobile calculus with parametric.
The Future of Learning Designs Making them useful and useable for teachers and learners Sue Bennett University of Wollongong,Australia Sue Bennett University.
Geography 465 Overview Geoprocessing in ArcGIS. MODELING Geoprocessing as modeling.
Composing Models of Computation in Kepler/Ptolemy II Summary. A model of computation (MoC) is a formal abstraction of execution in a computer. There is.
Course Instructor: Aisha Azeem
Component-based Authoring of Complex, Petri net-based Digital Library Infrastructure Yung Ah Park, Unmil P. Karadkar, and Richard Furuta Department of.
Department of Computer Science 1 CSS 496 Business Process Re-engineering for BS(CS)
A Semantic Workflow Mechanism to Realise Experimental Goals and Constraints Edoardo Pignotti, Peter Edwards, Alun Preece, Nick Gotts and Gary Polhill School.
CASE Tools And Their Effect On Software Quality Peter Geddis – pxg07u.
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
Špindlerův Mlýn, Czech Republic, SOFSEM Semantically-aided Data-aware Service Workflow Composition Ondrej Habala, Marek Paralič,
DR. AHMAD SHAHRUL NIZAM ISHA
Aurora: A Conceptual Model for Web-content Adaptation to Support the Universal Accessibility of Web-based Services Anita W. Huang, Neel Sundaresan Presented.
WP.5 - DDI-SDMX Integration E.S.S. cross-cutting project on Information Models and Standards Marco Pellegrino, Denis Grofils Eurostat METIS Work Session6-8.
The Semantic Web Service Shuying Wang Outline Semantic Web vision Core technologies XML, RDF, Ontology, Agent… Web services DAML-S.
Integrating Security Design Into The Software Development Process For E-Commerce Systems By: M.T. Chan, L.F. Kwok (City University of Hong Kong)
A Z Approach in Validating ORA-SS Data Models Scott Uk-Jin Lee Jing Sun Gillian Dobbie Yuan Fang Li.
Discussions for oneM2M Semantics Standardization Group Name: WG5 Source: InterDigital Communications Meeting Date: Agenda Item: WI-0005 ASN/MN-CSE.
Introduction to MDA (Model Driven Architecture) CYT.
Project Coordinators: Eduardo Santana de Almeida Silvio Romero de Lemos Meira Federal University of Pernambuco Informatics Center Recife Center for Advanced.
Formal Analysis of Problem Domain Workflows Uldis Donins Riga Technical University Baltic DB & IS 2012, July 8-11, Vilnius, Lithuania This work.
Lecture 9: Chapter 9 Architectural Design
Chapter 4.8: Determine if the Relation is a Function.
10/18/20151 Business Process Management and Semantic Technologies B. Ramamurthy.
E-Science for the SKA WF4Ever: Supporting Reuse and Reproducibility in Experimental Science Lourdes Verdes-Montenegro* AMIGA and Wf4Ever teams Instituto.
11 CORE Architecture Mauro Bruno, Monica Scannapieco, Carlo Vaccari, Giulia Vaste Antonino Virgillito, Diego Zardetto (Istat)
Conceptual Modelling – Behaviour
An Ontological Framework for Web Service Processes By Claus Pahl and Ronan Barrett.
Formal Specification and Analysis of Software Architectures Using the Chemical Abstract Machine Model CS 5381 Juan C. González Authors: Paola Inverardi.
11 CORE Architecture Mauro Bruno, Monica Scannapieco, Carlo Vaccari, Giulia Vaste Antonino Virgillito, Diego Zardetto (Istat)
Chapter 6 – Architectural Design Lecture 1 1Chapter 6 Architectural design.
1 Limitations of BLAST Can only search for a single query (e.g. find all genes similar to TTGGACAGGATCGA) What about more complex queries? “Find all genes.
Of 33 lecture 1: introduction. of 33 the semantic web vision today’s web (1) web content – for human consumption (no structural information) people search.
BPEL Business Process Engineering Language A technology used to build programs in SOA architecture.
Improving Dependability in Service Oriented Architectures using Ontologies and Fault Injection Binka Gwynne Jie Xu School of Computing University of Leeds.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
® IBM Software Group © 2004 IBM Corporation Developing an SOA with RUP and UML 2.0 Giles Davies.
Automating DAML-S Web Services Composition Using SHOP2 Based on an article by Dan Wu, Bijan Parsia, Evren Sirin, James Hendler and Dana Nau in Proceedings.
Software Design: The Next Step A presentation by Sean Matthews.
UCL DEPARTMENT OF SPACE AND CLIMATE PHYSICS MULLARD SPACE SCIENCE LABORATORY Taverna Plugin VAMDC and HELIO (part of the ‘taverna-astronomy’ edition) Kevin.
Chapter 5 System Modeling. What is System modeling? System modeling is the process of developing abstract models of a system, with each model presenting.
Software Reuse Course: # The Johns-Hopkins University Montgomery County Campus Fall 2000 Session 4 Lecture # 3 - September 28, 2004.
Formal Verification. Background Information Formal verification methods based on theorem proving techniques and model­checking –To prove the absence of.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Design and implementation Chapter 7 – Lecture 1. Design and implementation Software design and implementation is the stage in the software engineering.
ACCESSING DATA IN THE NIS USING THE KEPLER WORKFLOW SYSTEM Corinna Gries.
Vertical Integration Across Biological Scales A New Framework for the Systematic Integration of Models in Systems Biology University College London CoMPLEX.
Chapter 7 Lecture 1 Design and Implementation. Design and implementation Software design and implementation is the stage in the software engineering process.
Of 24 lecture 11: ontology – mediation, merging & aligning.
Service Composition Orchestration BPEL Cédric Tedeschi ISI – M2R.
Designing classes How to write classes in a way that they are easily understandable, maintainable and reusable 6.0.
These exercises highlight the services that do not perform biological functions, but are vital for running life science workflows.
1 The XMSF Profile Overlay to the FEDEP Dr. Katherine L. Morse, SAIC Mr. Robert Lutz, JHU APL
Object-Oriented Software Engineering Using UML, Patterns, and Java,
SysML v2 Formalism: Requirements & Benefits
Unified Modeling Language
Web Ontology Language for Service (OWL-S)
Chapter 10: Process Implementation with Executable Models
Graph Coverage for Specifications CS 4501 / 6501 Software Testing
Semantic Markup for Semantic Web Tools:
Business Process Management and Semantic Technologies
Scientific Workflows Lecture 15
Presentation transcript:

Scientific Workflow Interchanging Through Patterns: Reversals and Lessons Learned Bruno Fernandes Bastos Regina Maria Maciel Braga Antônio Tadeu Azevedo Gomes 1

Agenda Introduction – Problem Formulation and Initial Hypothesis Envisioned Solution Preliminary Experiments Reformulated Hypothesis Qualitative Analysis of the Research Material – The myExperiment Repository Related Work Conclusions 2

Introduction Scientific workflows are used for tackling complex problems in different e-science domains – They may be described as a directed graph where the vertices represent the tasks and the edges represent the data relationships between the tasks Several Scientific Workflow Management Systems (SWfMSs) have been developed – Specifying scientific workflows with higher-level abstractions (Workflow Specification Languages - WfSL) than scripts, – Orchestrating the execution of the tasks, and – Managing the data consumed and produced by these workflows. 3

Problem Formulation We formulated our research problem – The state-of-the-art in SWfMSs does not allow a scientist to easily reuse workflow specifications previously modeled in other SWfMSs than those this scientist is used to work with. 4

Initial Hypothesis The use of workflow patterns could help in keeping the semantics of a workflow – The use of workflow patterns combined with software architecture concepts to capture the key semantics expressed in workflow specifications enables the establishment of automated processes that transform these specifications across different SWfMSs. These processes allow for a reduction on the effort scientists would make to reuse workflow specifications developed by other research groups in SWfMSs that are not part of the usual tooling these scientists employ in their daily work 5

Envisioned Solution A novel language for interchanging workflow specifications – Using the Acme architecture description interchange language It was based on the specification of a single architectural style where the components were the tasks and the connectors were the patterns – Definition of an interchangeable workflow: workflow composed of a set of “interchangeable elements” Constants, subworkflows and webservices tasks 6

Envisioned Solution Patterns Structural Sequence: binds a single output port to a single input port; Parallel Split: binds a single output port to two or more input ports, replicating the same data from the output port to all input ports; Simple Merge: binds two or more output ports to a single input port, feeding the input port with data received from each output port in an interleaved way; Behavioral Synchronization: similar in structure to the Simple Merge pattern, but the task with the input port may be only executed when data coming from all the output ports have been received and grouped according to some criteria; Exclusive Choice: similar in structure to the Parallel Split pattern, but only one of the input ports may receive data from the output port, according to some condition. 7

Workflow Pattern Identification Patterns may be implemented in different ways – Depending on the features each SWfMS supports – Eg: Exclusive Choice Pattern 8

Preliminary Experiments Experiment Planning – 4 VisTrails, 46 Kepler and 1452 Taverna specifications For the 1st hypothesis the task type matters – VisTrails has only one Web Service and it is not available – Kepler has 45 types of tasks but none of them is a Web Service – Taverna has more than 100 types and many Web Services 9

Preliminary Experiments Analysis of the workflow transformations – 53% of the Taverna tasks were interchangeable Quantity of Tasks Quantity of Interchangeable Workflows 10

Reformulated Hypothesis The use of workflow patterns and software architecture concepts to capture the key structural semantics expressed in workflow specifications enables the establishment of semi-automated processes that transform these specifications across different WfSLs. These processes allow for a reduction on the effort scientists would make to reuse structurally complex workflow specifications (in the sense of having a large number of tasks and dependency relationships between these tasks) developed by other research groups in SWfMSs that are not part of the usual tooling these scientists employ in their daily work. 11

Further Experiments After interchanging the workflows structures we could interchange almost all workflows (98.28%) – Problems related to the patterns identification 12

Qualitative Analisys of the Research Material The myExperiment repository – Webservice tasks implemented as either local, inaccessible, or authenticated, which made it impossible to execute these workflows, even in their source specifications – Lack of documentation: Most of the analyzed workflows have no or very few metadata information Similar problems reported in the Wf4Ever project – Proposal of a new myExperiment repository 13

Qualitative Analisys of the Research Material The studied systems – Once a task has its type defined and its input and output ports linked to other tasks, it cannot have its type changed, therefore it needs to be removed Once removed the relations are gone! It reduces the utility of our approach – Some SWfMS have limitations VisTrails does not export subworkflows 14

Related Work Taverna 2-Galaxy and Tavaxy – Limited to two SWfMSs and their adaptability to a broader range of SWfMSs would depend on a complete reformulation of their architectures Although Tavaxy brings the patterns approach IWIR – Most similar to ours – Syntactical structures that are quite similar to those defined for the SWfMSs Other works 15

Conclusions This research endeavor started with exploratory studies aiming at identifying whether it would be possible to establish “future-proof” automated processes for transforming workflows between different SWfMSs. It was unclear whether the perceived problem does actually exist, and the experimental data we employed may point out in a different direction. The fact that the myExperiment repository is plenty of “toy” made it harder to execute a proof of concept. 16

Questions 17