A Java command line tool which converts a Taverna workflow to an Archimate model instance. It creates a process model including the three Archimate layers Business, Application and Technology. Therefore, in a first step each Taverna processor gets presented as a Business Process element on the Archimate Business Layer. In addition, worklow input/output ports and intermediate values of process steps are modelled as Business Objects. For the various Taverna processor types (e.g., Beanshell Script, Tool Innvocation, External Services) we have defined transformation patterns to generate the Application and Technology layer elements. To extend the Archimate model with additional information on processed file formats (for a specfic workflow run), the converter accesses the Taverna provenance database to extract those files. In a further step DROID (Digital Record Object Identification) is used to identify the corresponding file formats defined in the PRONOM registry. This tool can also update an existing ontology with those gathered file format informations.
The left figure presents a simple Taverna 2.4 workflow, which uses a global weather web service to request the current weather information for a specific city. The automated converted Archimate model of this workflow is shown in the right figure.
Copyright (c) 2013/2014 Verein zur Foerderung der IT-Sicherheit in Oesterreich (SBA). The work has been developed in the TIMBUS Project and the above-mentioned are Members of the TIMBUS Consortium. TIMBUS is supported by the European Union under the 7th Framework Programme for research and technological development and demonstration activities (FP7/2007-2013) under grant agreement no. 269940. Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at: http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTIBITLY, or FITNESS FOR A PARTICULAR PURPOSE. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law or agreed to in writing, shall any Contributor be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work. See the License for the specific language governing permissions and limitation under the License.
The Taverna2Archi v1.0 command line tool is available for download.
This project is hosted at opensourceprojects. You can clone the project using following command:
git clone https://@opensourceprojects.eu/git/p/timbus/context-population/extractors/taverna-extractor timbus-context-population-extractors-taverna-extractor
In case you want to compile and build the program on your own, you can clone the from the link above and follow the instructions in the README file.
IMPORTANT: Before running the converter, you have to adapt the Taverna.properties file!
The extractor offers following commands:
A => -i,--inputFile
...specifies the taverna t2flow (input) file. \path\to\taverna\input.t2flow -o,--outputFile ...specifies the archimate (output) file. \path\to\archimate\output.archimate -d,--dependencyDir ...workflow dependencies directory. [OPTIONAL] B1 => -d,--droid ...\path\where\to\save\droidOutputFile B2 => -cr,--report ...\path\where\droidOutputFile\is\located B3 => -ont,--ontology-file ...ontology to extend. \path\to\ontology -r,--reportFile ...generated DROID CSV report. -v, verbose ...enable verbose mode
In this section, we present a sample call for each command:
[A] Convert a Taverna Workflow to an Archimate Model: java -jar TavernaExtractor.jar -i \path\to\TavernvaWorkflowInputFile.t2flow -o \path\to\ArchimateOutputFile.archimate [B] Extract including file formats from Workflow and identify them with DROID. In the following the 3 necessray steps are presented: ATTENTION: Due to its DROID dependencies, make sure you are executing the TavernaExtractor.jar in the respective directory!! [B1] Running DROID identififaction on collected Taverna Workflow Run data: INPUT: path to file which gets created. OUTPUT: file containing DROID identification information in a none readable form. java -jar TavernaExtractor.jar -d path\to\myDroidFile.droid Sample Output: ===== [ID] | [Workflow Name (Timestamp)] ===== | 2 entries found.  MusicClassificationExperiment (2013-09-25 13:11:42.488)  MusicClassificationExperiment (2013-09-23 10:44:43.839) Your choice: //Enter an ID to process [B2] Generate a CSV report out of a DROID profile: (CSV report is stored in the same directory as the *.droid input file) INPUT: file from step [B1]. OUTPUT: file in CSV format containing DROID information in a readable form. java -jar TavernaExtractor.jar -cr path\to\myDroidFile.droid [B3] Extend existing ontology with information about the used file formats in the workflow run: INPUT1: existing OWL file, which should be extended. INPUT2: file from step [B2]. OUTPUT: updates OWL file from INPUT1. java -jar TavernaExtractor.jar -ont \path\to\myOntology.owl -r \path\to\myDroidCSVreportFile.droid.csv