Search

Plan and build a workflow management system to integrate allows you to design workflow processes and build request forms, no coding skills required. Easy to implement and learn in Internet of Thing (IoT). Integrify will save you time and effort by eliminating lengthy process development. There are many related standardized solutions in (IoT), but are no features to cross-over manufacture industry, virtualized organization flow control, front-end development tools and are not easy to customize. So use flexibility and easy to maintain, and cost down are the main consideration for workflow management in company. The proposed method of this research is based upon J2EE technology to design workflow management engine, using Wf-MXL message format standard of Workflow Management Coalition (WfMC) and describe information exchange format in multi-organizations workflow to complete product design. The experimentation used workflow engine in IoT, network product manufacture from product development to product design. The result of this research innovation factor of the paper, apply workflow engine to product design flow for network products in Industrial Science Park. Use the customized business process management system function to adjust business’ ability to speed up product development time and meet user requirements, and to reduce the product development cost.

There are two major concerns in the development of current workflow system. The first is security considerations and the second is context awareness. Modern workflow systems cross the boundaries of organisations, each may have its own security requirements, policies and constraints. Even within one organisation, activities in a workflow system may be executed, in one of its instances, within a platform, but in another instance it may be executed or performed on a different platform with completely different environment. Indeed it may not even be automated. This lends modern workflow systems to be security and context-critical. This is in addition to the fact that some of its activities must satisfy variety of hard timing constraints. Current specification and design languages for workflow systems are inadequate in dealing with context-aware secure workflows. This paper presents a sound wide-spectrum language, CS − F l o w , for the specification and design of context-aware, secure workflow systems. As workflow systems have strong temporal aspects (e.g. activity sequencing, deadline, scheduling constraints, etc.), the proposed CS − F l o w is equipped with a rich set of temporal constructs together with temporal proof rules which can be used to be integrated with temporal expert systems, hence enhancing the capabilities of current workflow software. In addition, CS − F l o w is supported by a proof system which underpins the workflow engine that provides decision service using its state to make some decision and update the workflow state. CS − F l o w therefore provides a sound linkage between expert systems and workflow engines.

Through the analysis of workflow management system based on Web, the work, following WFMC workflow model, proposed a universal workflow management system with the combination of specific application requirements of enterprises. Workflow management system based on Web was described from system function, software structure, system structure, workflow engine and security. The actual case of the design of aeronautical structure showed that workflow system performance can be greatly improved by using Web technology.

With increasingly widespread adoption of workflow technology as a standard solution to business process management, a large number of workflow models have been put in use in companies in the era of electronic commerce. These workflow models form a valuable resource for workflow domain knowledge, which should be reused to support workflow model design. However, current workflow modeling approaches do not facilitate workflow model reuse as a fundamental requirement, leading to a research gap in effective workflow model reuse. In this paper, we propose a novel approach called Data-centric Workflow Model Reuse framework (DWMR) to provide a solution to workflow model reuse. DWMR compliments existing control-flow-focused workflow modeling approaches by explicitly storing workflow data information, such as data dependency, data task relationships, and data similarity scores. DWMR also provides data-driven workflow model search and composition algorithms to satisfy user query requirements by automatically combining multiple workflow models. We demonstrate the feasibility of the DWMR approach by applying it to data from a well-known industry workflow model repository. We propose a formal data-driven approach (DWMR) to facilitate efficient workflow model reuse.DWMR compliments existing control-flow-focused workflow modeling approaches by explicitly storing workflow data information.DWMR provides data-driven workflow model search and composition algorithms to automatically satisfy user query requirements.The result generated by our approach has a high accuracy in terms of precision and recall, comparing with human experts.

Scientific workflows orchestrate the execution of complex experiments frequently using distributed computing platforms. Meta-workflows represent an emerging type of such workflows which aim to reuse existing workflows from potentially different workflow systems to achieve more complex and experimentation minimizing workflow design and testing efforts. Workflow interoperability plays a profound role in achieving this objective. This paper is focused at fostering interoperability across meta-workflows that combine workflows of different workflow systems from diverse scientific domains. This is achieved by formalizing definitions of meta-workflow and its different types to standardize their data structures used to describe workflows to be published and shared via public repositories. The paper also includes thorough formalization of two workflow interoperability approaches based on this formal description: the coarse-grained and fine-grained workflow interoperability approach. The paper presents a case study from Astrophysics which successfully demonstrates the use of the concepts of meta-workflows and workflow interoperability within a scientific simulation platform.

This paper presents HyperFlow: a model of computation, programming approach and enactment engine for scientific workflows. Workflow programming in HyperFlow combines a simple declarative description of the workflow structure with low-level implementation of workflow activities in a mainstream scripting language. The aim of this approach is to increase the programming productivity of workflow developers who are skilled programmers and desire a programming experience similar to the one offered by a mature programming ecosystem. Combining a declarative description with low-level programming enables elimination of shim nodes from the workflow graph, considerably simplifying workflow implementations. The workflow description is based on a formal model of computation (Process Networks) and is characterized by a simple and concise syntax, utilizing just three key abstractions—processes, signals and functions. Yet it is sufficient for expressing complex workflow patterns in a simple way. The adopted model of computation implemented in the HyperFlow workflow engine enables fully distributed and decentralized workflow enactment. The paper describes HyperFlow from the perspective of its workflow programming capabilities, the adopted model of computation, as well as the enactment engine, in particular its distributed workflow enactment capability. The provenance model and logging features are also presented. Several workflow examples derived from other workflow systems and reimplemented in HyperFlow are extensively discussed.

This paper presents a component-based product line for workflow management systems. The process followed to design the product line was based on the Catalysis method. Extensions were made to represent variability across the process. The domain of workflow management systems has been shown to be appropriate to the application of the product line approach as there are a standard architecture and models established by a regulatory board, the Workflow Management Coalition. In addition, there is a demand for similar workflow management systems but with some different features. The product line architecture was evaluated with Rapide simulation tools. The evaluation was based on selected scenarios, thus, avoiding implementation issues. The strategy that has been used to populate the architecture and experiment with the product line is shown. In particular, the design of the workflow execution manager component is described.

Command process of Joint operations throughout the lifecycle of joint operations. For the dynamic development of the command process execution order and semi-automatic/ automated command process management, we introduce workflow technology and methods. In order to meet the dynamic variations of the process definition in the workflow system, this paper analyzes the dynamic characteristics of the workflow technology, which is based on the concept of joint operation, and proposes the mapping of the hierarchical decomposition model for the joint operation to the application requirements. According to the above study, the workflow process definition meta-model that was put forward by the Workflow Management Coalition (WfMC) has been improved in the paper. While the workflow process definition language (XPDL) is a kind of text description language that is based on the meta-model, thus the XPDL demands to be extended accordingly. These improvements and extension make the rectification of both the definition state and the running state process model more flexible. Through these improvements and extensions, the modification of the process model becomes more flexible. The workflow management system based on the improved meta-model is both flexible and fully embodies the dynamic characteristics of the workflow, which is more suitable for the workflow system and apply on a more complex command process.

Business process management has often focused on business processes with a production or administrative focus, resulting in a task-centric approach for modeling and execution of workflow based on the processes. However, the area of collaborative business processes exists, which includes important processes like research and development which have not been adequately addressed by the techniques offered for production workflows. For this, goal-oriented processes have been proven useful to allow for a more flexible approach in modeling and executing workflow. In addition, distributed workflow management allows for a more flexible approach regarding organizational structures. However, the actual recording of action taken in a process is still relevant for workflow analysis and re-engineering. As a result, this paper presents a distributed approach for generating, gathering, distributing, and storing events resulting from the execution of goal-oriented workflows in a distributed workflow environment while allowing the real-time association of occuring actions with business goals in the process using drill-down analysis. Copyright © 2015 John Wiley & Sons, Ltd.

As the rapid development of modern society, it's hard for traditional workflow technologies to meet the variant requirements inside an enterprise. The research focus of workflow technology has been moved to flexibly adjustable workflow models that can easily and fast adapt to business change. In terms of this point, a flexible workflow model is put forward based on the UML technology. Several UML diagrams, such as class diagram, activity diagram and sequence diagram, are introduced to illustrate both model elements and detailed working mechanism of the workflow model. In addition, the strategy of flexible adaption is proposed to deal with changes. Based on this model, a general-purpose system of project application and review is designed and implemented, which is able to adapt flexibly to the business flow changes of project applying after putting into use.

In order to achieve the interconnection between different workflow management systems, it was proposed that all the distributed workflow systems would be encapsulated as web services to perform the entire business process collaboratively by the way of processes’ composition in this paper. By analyzing the comparison between the composition of processes and ordinary Web service, we studied interactive control, the parameters required to be passed through the distributed workflow systems, the workflow system service’s interfaces and its packaging. Furthermore we put forward a general method of the workflow systems interactive interfaces’ extension and the way of the workflow service’s encapsulating and invoking. By this approach, it can easily combine the processes or process fragments which deployed on different workflow systems without other agents and components. It also provides support for the interconnection of the workflow systems in distributed environment, and ultimately achieves a coordinated operation between different workflow engines.

To manage the rapid growth and complexity of software, model-based development workflow is being increasingly adapted in industry. This paper provides a brief overview of some of the important verification and validation steps in this workflow and illustrates them using Simulink Design Verifier tool of MathWorks .

Software has become a rapidly evolving artifact and Workflow Management Systems (WfMSs) are not an exception. WfMSs’ changes may impact key performance indicators or resource consumption levels may change among different versions. Thus, users considering a WfMS upgrade need to evaluate the extent of such changes for frequently issued workload. Deriving such information requires running performance experiments with appropriate workloads. In this paper, we propose a novel method for deriving a structurally representative workload from a given business process collection, which we later use to evaluate the performance and resource consumption over four versions of two open-source WfMSs, for different numbers of simulated users. In our case study scenario the results reveal relevant variations in the WfMSs’ performance and resource consumption, indicating a decrease in performance for newer versions.

You’ve had an introduction to how Shopify themes are put together, and ended the last chapter looking at the contents of the default Debut theme via the Shopify Admin’s online theme editor. If you were a bit of a masochist, you could do all your theme development through this editor. If you tried that, though, you’d most likely come across these difficulties.

Today’s scientific application requires tremendous amount of computation-driven as well as data-driven supported resources. The scientific applications are represented as workflows. The workflow management systems are designed and developed to depict the workflows of complex nature. The workflow management systems are able to reliably and efficiently coordinate among various resources in a distributed environment. This chapter describes various workflow management software like Kepler, Taverna, Triana, Pegasus, and Askalon. The architecture and functionalities of these workflow management systems are explained in the following sections.

Workflow platform as a service (WaaS) allows users to define, integrate and run workflow based applications and it is becoming popular with the rapid development of cloud computing. However, for a workflow-enabled application, a single workflow model is not possible to meet various requirements from different users. Therefore, many workflow platforms provide tools that can be used to change the workflow model by users. An approach to mine users' workflow change operations is proposed, through which change rules can be discovered and be reused to configure the workflow model automatically in the future. The method to retrieve the change operations is firstly introduced and a change rule-mining algorithm is given. Then the process of applying change rules to configure the workflow model is described. Finally, a prototype system and a case study are presented.

The workflow management, in which the main line is the product, is used widely. The emergence of product structure makes workflow management more complex. This thesis focuses on the realization method of workflow engine based on product structure. Firstly, this paper describes the formal definition of the workflow based on product structure, and then gives the algorithm of instantiating workflow, the startup algorithms and the advance algorithms involved in the workflow execution in detail, finally, this paper shows the realization of the engine based on these algorithms. These algorithms described in this paper allow users to make decisions on designing and establishing the composition of the product structure flexible, to define the approval process of the task node flexible, and to advance the process according to the results of the instantiation automatically.

Service-oriented computing offers efficient solutions for executing complex applications in an acceptable amount of time. These solutions provide important computing and storage resources, but they are too difficult for individual users to handle. In fact, Service-oriented architectures are usually sophisticated in terms of design, specifications, and deployment. On the other hand, workflow management systems provide frameworks that help users to manage cooperative and interdependent processes in a convivial manner. In this paper, we propose a workflow-based approach to fully take advantage of new service-oriented architectures that take the users' skills and the internal complexity of their applications into account. To get to this point, we defined a novel framework named JASMIN, which is responsible for managing service-oriented workflows on distributed systems. JASMIN has two main components: unified modeling language (UML) to specify workflow models and business process execution language (BPEL) to generate and compose Web services. In order to cover both workflow and service concepts, we describe in this paper a refinement of UML activity diagrams and present a set of rules for mapping UML activity diagrams into BPEL specifications. Keywords—Service Composition, Service-Oriented Computing, Service-Oriented Workflow, UML2BPEL, Workflow

The workflow model is used widely in modern society office, production and manufacturing fields in computer environment. It plays a more and more important role in the office circumstance, industrial and manufacturing domain with the development of computer automation in modern business. Workflow management system is a tool. It is also a platform to develop and implement the workflow. But heterogeneities under distributed network environments hamper the coordination among the tasks in a workflow management system. We propose a new workflow management system based on CORBA and mobile-Agent to solve these problems. And we make the detailed analysis of this system. Firstly, this paper introduces the research background and research status. The second part is the related concepts of workflow management system, CORBA and agent technology under a distributed environment. The third part is the new workflow management system. The last part is the conclusion.

The paper, in which Government Affair Workflow Model as an illustrated application is discussed, clarifies nature and concept of Ontology. Based on the characteristics of the workflow model and application of Government Affair Workflow , this paper puts forward Government Affair Workflow Model and creates a Workflow Meta-Model, Document Meta-Model and Determent Meta-Model and offers framework of OWL+RDF+XML. It is proved in the experiments that Ontology can be applied effectively in Government Affairs Workflow.

E-scientists want to run their scientific experiments on Distributed Computing Infrastructures (DCI) to be able to access large pools of resources and services. To run experiments on these infrastructures requires specific expertise that e-scientists may not have. Workflows can hide resources and services as a virtualization layer providing a user interface that e-scientists can use. There are many workflow systems used by research communities but they are not interoperable. To learn a workflow system and create workflows in this workflow system may require significant efforts from e-scientists. Considering these efforts it is not reasonable to expect that research communities will learn new workflow systems if they want to run workflows developed in other workflow systems. The solution is to create workflow interoperability solutions to allow workflow sharing. The FP7 Sharing Interoperable Workflow for Large-Scale Scientific Simulation on Available DCIs (SHIWA) project developed two interoperability solutions to support workflow sharing: Coarse-Grained Interoperability (CGI) and Fine-Grained Interoperability (FGI). The project created the SHIWA Simulation Platform (SSP) to implement the Coarse-Grained Interoperability approach as a production-level service for research communities. The paper describes the CGI approach and how it enables sharing and combining existing workflows into complex applications and run them on Distributed Computing Infrastructures. The paper also outlines the architecture, components and usage scenarios of the simulation platform.

Efficient business workflow management in large-scale areas is in great demand. However, current business workflow management systems are short of distributed workflow execution support. In our paper, we design and implement a distributed framework called PeerODE for Apache ODE (Orchestration Director Engine) [1], an open-sourced business workflow engine. PeerODE presents a scalable approach to P2P business process execution. The scheduling experiment on PeerODE shows that the framework handles the distributed business process execution effectively.

At present, the enterprise has many business processes. It need transfer many forms involving personnel, procurement and other aspects. The workflow management system uses computer network to realize the automation of the business process. This paper analyses the workflow management system, describes the operational principle of the workflow engine and presents a cooperative platform design based on workflow. It can effectively track the whole process and realize standardized management. Otherwise, it can enhance the enterprise business operation efficiency.

Workflow is a widely used term to describe the sequence of steps to accomplish a task. The use of workflow technology in medicine and medical imaging in particular is limited. In this article, we describe the application of a workflow engine to improve workflow in a radiology department. We implemented a DICOM-enabled workflow engine system in our department. We designed it in a way to allow for scalability, reliability, and flexibility. We implemented several workflows, including one that replaced an existing manual workflow and measured the number of examinations prepared in time without and with the workflow system. The system significantly increased the number of examinations prepared in time for clinical review compared to human effort. It also met the design goals defined at its outset. Workflow engines appear to have value as ways to efficiently assure that complex workflows are completed in a timely fashion.

Workflow is a kind of automatic execution of business process partly or fully, according to a series of rules, documents, information or tasks which can be transferred and executed in different executor such in Data center. Modeling process workflow management model on ontology is divided into following steps based on: Determine professional field and category of Ontology; Important terms and concepts; Definition of class and class hierarchy; Define class attributes and surface properties, Because user demand always changes according to the development of economic, In workflow management system, user demand migration prediction system can give some help. There are two subsystems: Data Mining subsystem and migration of recommendation subsystem.

With the technology of the workflow, we can separate the process logic from the application logic, which can make it easy and quick to operate in each flow. There are two main tasks to build the workflow model: one is the workflow process model and the other is the establishing process of the description language. This paper will first discuss the types of the workflow, then it proposes OA system model. Finally, it analyzes the workflow model.

the workflow process model is actually the computational description of the business process, which includes all the required information in the process, such as the conditions of the beginning and ending in the process every task item in the business process the information transferring rules between every task and the required application tools or programs and so on. This paper first introduces the standard workflow reference model, then it proposes the meta-model of the workflow, and finally it analyzes the operating process of the workflow cases.

In this article, we design a HR work service hall based on the workflow engine. The service hall is focusing on how to design the search and perform the service workflow to provide users with convenience. The business forms and workflows are completed with the workflow engine. The design can greatly reduce the development effort and the program does not need to be transformed when the business process changing occurs. We just need to modify the corresponding forms and processes without program upgrade, which can be easily adapt to changes in business processes.

Workflow management systems are the powerful tools as well as the best supports for industries which involve series of complex workflows. Specifically, two of the main objectives of workflows management system are (1) ensuring the correctness and integration of workflow advancement, and (2) carrying workflow forward to the maximum extent automatically. To ensure the correctness and integration of workflow management system, in this paper, a workflow management method based on the workflow node property is proposed, and a workflow management system model is given. In addition, in the given model, an automatic advance mode is proposed to make the workflow is able to be carried on automatically.

Workflow is the further improvement of MIS system, emphasizing to link each MIS module whose logic is separate in a specific manner so that they can cooperate with one another and achieve their effects in the form of process. In order to attain the universality of workflow application, on one hand, in this article the author designs connectors among workflow, workflow nodes and workflow parameters to simplify the structure of workflow. On the other hand, the author applies delegate and event technique to solve the problem of communication in time between workflow and workflow nodes so that workflow can flow sequentially among the nodes. In the end, a set of reusable, scalable and easily-usable generic OA components is encapsulated.

For the purpose to realize information collection, collation, transfer, tracking and execution required by Hunan Urban Construction College to carry out the function of scientific research and management, and through the re-definition of the workflow process definition, we combine the modeling technology of Petri net and the workflow technology to design the amendment of the workflow process and the storage mechanism. Also we design the data structure of the workflow engine, hoping to make breakthrough on both thoughts and measures for the realization of the research management & information system.

Scientific workflow systems support various workflow representations, operational modes, and configurations. Regardless of the system used, end users have common needs: to track the status of their workflows in real time, be notified of execution anomalies and failures automatically, perform troubleshooting, and automate the analysis of the workflow results. In this paper, we describe how the Stampede monitoring infrastructure was integrated with the Pegasus Workflow Management System and the Triana Workflow Systems, in order to add generic real time monitoring and troubleshooting capabilities across both systems. Stampede is an infrastructure that provides interoperable monitoring using a three-layer model: (1) a common data model to describe workflow and job executions; (2) high-performance tools to load workflow logs conforming to the data model into a data store; and (3) a common query interface. This paper describes the integration of Stampede monitoring architecture with Pegasus and Triana and shows the new analysis capabilities that Stampede provides to these workflow systems. The successful integration of Stampede with these workflow engines demonstrates the generic nature of the Stampede monitoring infrastructure and its potential to provide a common platform for monitoring across scientific workflow engines.

Most of the existing scientific workflow systems rely on proprietary concepts and workflow languages. We are convinced that the conventional workflow technology that is established in business scenarios for years is also beneficial for scientists and scientific applications. We are therefore working on a scientific workflow system based on business workflow concepts and technologies. The system offers advanced flexibility features to scientists in order to support them in creating workflows in an explorative manner and to increase robustness of scientific applications. We named the approach Model-as-you-go because it enables users to model and execute workflows in an iterative process that eventually results in a complete scientific workflow. In this paper, we present main ingredients of Model-as-you-go, show how existing workflow concepts have to be extended in order to cover the requirements of scientists, discuss the application of the concepts to BPEL, and introduce the current prototype of the system.

International audience; In this paper, we leverage the previous work on the SHIWA bundling format and expand on this specification in order to facilitate workflow execution within a multi-workflow environment. We introduce a scalable and robust execution pool environment that supports workflows consisting of sub-workflows built upon a multitude of different workflow engines and environments, and also provide a common workflow representation for seamless connectivity through serialization to workflow bundles. We also present a meta-workflow scenario based upon this system. Workflow bundles employ the lightweight Open Archives Initiative Object Reuse and Exchange (ORE) Web-based standard, to provide a common format for representing and sharing workflows and the associated metadata required for their execution. This generalized bundling approach is already available within five workflow engines and has proven a useful environment for inter-workflow experimentation. The execution pool facilitates federated access to multiple distributed computing infrastructures supported by the underlying workflow engines subscribed to the pool. Workflow bundles are exposed using the eXtensible Messaging and Presence Protocol (XMPP), which provides the necessary communication backbone to enable multiple workflow engine agents to asynchronously publish and subscribe to bundles in meta-workflow pipelines. We present experiments showing the scalability and robustness of the pool execution approach with results showing that overheads remain controlled for up to 150 workflow agents, and that agent failures have very limited impact. We then demonstrate the applicability of our architecture by describing how a Java-based music analysis workflow can be distributed within such a multi-workflow environment consisting of the Triana and MOTEUR workflow engines.

Today's enterprise business processes become increasingly complex given that they are often executed by geographically dispersed partners or different organizations. Designing and modeling such a cross-organizational workflow is a complicated, time-consuming process and requires that a designer has extensive experience. Workflow logs captured by different cross-organizational systems provide a very valuable source of information on how business processes are executed in reality and thus can be used to derive workflow models through process mining. In this paper, we investigate the application of process mining for workflow integration based on the concept of RM_WF_Net, a type of Petri net extended with resource and message factors. Four coordination patterns are defined for workflow integration. A process mining approach is presented to discover the coordination patterns between different organizations and the workflow models in different organizations from the running logs containing the information about resource allocation. A process integration approach is then presented to obtain the model for a cross-organizational workflow based on the model mined for each organization and the coordination patterns between different organizations.

Drawing Management System (DMS) has begun to be used more and more widely in modern enterprise and public institution. It has become one of the necessary tools to improve image file management efficiency. A subsystem model based on three layer of structure is put forward in this paper which meets Workflow Management Coalition (WfMC) standard. The model consists of workflow interaction, process management system, message mechanism, workflow engine. Each module finishes their own job to realize the auto run of DMS’s files.

Workflow management technology is an important computer technology in enterprise business process management. At present, there was a few of Workflow Engine which supported BPEL4WS specification. Base on the current research case of workflow, the aim of our study bring a Workflow platform support BPEL4WS Specification.According to the analysis of the web service’s new features and issues, we look into the dynamic workflow based on web services from the angles of service-oriented. We introduce the basic concepts, elements , activity, fault handler and compensate mechanism of BPEL4WS.This paper presents a design schem of framework of a web service-based dynamic workflow engine.

Workflow management systems are software systems that model and execute the logic of business processes. There are many approaches for modelling process workflows and many systems or ‘engines’ for executing such models. One goal of workflow design is robustness , which, in general, means resistance to software or hardware errors, and the ability to recover the execution of the workflow process from such errors, in a graceful manner. In this paper, we propose an architecture and implementation for robust workflow management systems, using the Erlang language. We first show how common workflow design patterns such as sequence , split and join can be implemented in Erlang, and then how robustness supporting mechanisms such as workflow monitors can be added. We illustrate the approach by showing how a business workflow described in Business Process Model and Notation BPMN can be implemented according to the above approach, and demonstrate its failure handling capabilities.

Recently, workflow fragments gains increasing momentum for reuse and re-purpose in Cyber-Physical Systems. To the end, this article proposes to detect and recommend workflow fragments gratifying e-Scientist requirement. Specifically, most common workflow fragments in the form of layer hierarchy are extracted from scientific workflows, which are collected in the myExperiment repository. Annotations for those workflow fragments are developed to support the discovery of workflow fragments. Consequently, an approach for workflow fragments rank and recommendation is presented considering the semantics and structure of workflow fragments.

As biomedical data has become increasingly easy to generate in large quantities, the methods used to analyze it have proliferated rapidly. Reproducible and reusable methods are required to learn from large volumes of data reliably. To address this issue, numerous groups have developed workflow specifications or execution engines, which provide a framework with which to perform a sequence of analyses. One such specification is the Common Workflow Language, an emerging standard which provides a robust and flexible framework for describing data analysis tools and workflows. In addition, reproducibility can be furthered by executors or workflow engines which interpret the specification and enable additional features, such as error logging, file organization, optim1izations tocomputation and job scheduling, and allow for easy computing on large volumes of data. To this end, we have developed the Rabix Executora, an open-source workflow engine for the purposes of improving reproducibility through reusability and interoperability of workflow descriptions.

BPMN usage has been extended beyond the workflow systems and service-oriented architecture. Development methodologies have been proposed using BPMN to describe use cases, to specify the activities flow that forms each scenario of general purpose systems and business process execution with web services. This article proposes a metric to estimate software size, called BPMN Activity Points based on activities counting from three different perspectives, in which these scores are increasingly detailed and refined.

Emerging Internet of Things (IoT) system consists of heterogeneous physical devices that are interconnected via the Internet Protocol (IP) networks. In order to integrate the front-end physical things in the IoT management systems, Business Process Management Systems (BPMS) have gained attention as a viable option. However, enabling the participation of the resource constrained IoT devices in the business process execution raises the question, when considering the agility and energy conservation, whether the device should embed a standard workflow engine or it is better to execute a program representing the workflow. This paper aims to provide a guideline to developers by investigating the two business process workflow execution approaches for resource constrained IoT devices via the comparison of performance and resource usage. The experiments show the comprehensive comparison between the two approaches together with the discussion of the lessons learned.