A Dynamic Workflow Management Model Based on Web Services

2010 ◽  
Vol 439-440 ◽  
pp. 599-604
Author(s):  
Hong Zhen Xu ◽  
Bin Tang ◽  
Ying Gui ◽  
Huai Ping Wang

Workflow technology has emerged as one of those technologies designed to support modeling, designing and executing business processes. One of the major limitations of current workflow management systems is the lack of flexibility to support dynamic management of workflows. In this paper, we propose a dynamic workflow management model based on web services. We integrate web services and ontology technologies to support dynamic specifying, monitoring, analyzing, designing, configuring and executing workflows. We explain the need and functionality of the main modules and interfaces of the model, and introduce its application in a case study. An important feature of this model is to support for planning and adaptive workflow management.

2012 ◽  
Vol 601 ◽  
pp. 401-405
Author(s):  
Wen Bo Zhou ◽  
Shu Zhen Yao

The degree of flexibility of workflow management systems heavily influences the way business processes are executed. Constraint-based models are considered to be more flexible than traditional models because of their semantics: everything that does not violate constraints is allowed. More and more people use declarative languages to define workflow, such as linear temporal logic. But how to guarantee the correctness of the model based on the linear temporal logic is still a problem. This article proposes a way to verify the model based on Büchi automaton and gives the corresponding algorithms. Thus the verification of declarative workflow based on the linear temporal logic is solved.


Author(s):  
Ling Liu ◽  
Calton Pu ◽  
Duncan Dubugras Ruiz

This chapter presents a framework for dynamic restructuring of long-running business processes. The framework is composed of the ActivityFlow specification language, a set of workflow restructuring operators, and a dynamic workflow management engine. The ActivityFlow specification language enables the flexible specification, composition, and coordination of workflow activities. There are three unique features of our framework design. First, it supports a collection of specification mechanisms, allowing workflow designers to use a uniform workflow specification interface to describe different types of workflows involved in their organizational processes. A main objective of this characteristic is to help increase the flexibility of workflow processes in accommodating changes. The ActivityFlow language also provides a set of activity modeling facilities, enabling workflow designers to describe the flow of work declaratively and incrementally, and allowing to reason about correctness and security of


Author(s):  
Yuhong Yan ◽  
Philippe Dague ◽  
Yannick Pencolé ◽  
Marie-Odile Cordier

Web services based on a service-oriented architecture framework provide a suitable technical foundation for business process management and integration. A business process can be composed of a set of Web services that belong to different companies and interact with each other by sending messages. Web service orchestration languages are defined by standard organizations to describe business processes composed of Web services. A business process can fail for many reasons, such as faulty Web services or mismatching messages. It is important to find out which Web services are responsible for a failed business process because we could penalize these Web services and exclude them from the business process in the future. In this paper, we propose a model-based approach to diagnose the faults in a Web service-composed business process. We convert a Web service orchestration language, more specifically BPEL4WS, into synchronized automata, so that we have a formal description of the topology and variable dependency of the business process. After an exception is thrown, the diagnoser can calculate the business process execution trajectory based on the formal model and the observed evolution of the business process. The faulty Web services are deduced from the variable dependency on the execution trajectory. We demonstrate our diagnosis technique with an example.


Author(s):  
Vincent Yen

In large organizations, typical systems portfolios consist of a mix of legacy systems, proprietary applications, databases, off-the-shelf packages, and client-server systems. Software systems integration is always an important issue and yet a very complex and difficult area in practice. Consider the software integration between two organizations on a supply chain; the level of complexity and difficulty multiply quickly. How to make heterogeneous systems work with each other within an enterprise or across the Internet is of paramount interest to businesses and industry. Web services technologies are being developed as the foundation of a new generation of business-to-business (B2B) and enterprise application integration (EAI) architectures, and important parts of components as grid (www.grid.org), wireless, and automatic computing (Kreger, 2003). Early technologies in achieving software application integration use standards such as the common object request broker architecture (CORBA) of the Object Management Group (www.omg.org), the distributed component object model (DCOM) of Microsoft, and Java/RMI, the remote method invocation mechanism. CORBA and DCOM are tightly coupled technologies, while Web services are not. Thus, CORBA and DCOM are more difficult to learn and implement than Web services. It is not surprising that the success of these standards is marginal (Chung, Lin, & Mathieu, 2003). The development and deployment of Web services requires no specific underlying technology platform. This is one of the attractive features of Web services. Other favorable views on the benefits of Web services include: a simple, lowcost EAI supporting the cross-platform sharing of functions and data; and an enabler of reducing integration complexity and time (Miller, 2003). To reach these benefits, however, Web services should meet many technology requirements and capabilities. Some of the requirements include (Zimmermann, Tomlinson & Peuser, 2003): • Automation Through Application Clients: It is required that arbitrary software applications running in different organizations have to directly communicate with each other. • Connectivity for Heterogeneous Worlds: Should be able to connect many different computing platforms. • Information and Process Sharing: Should be able to export and share both data and business processes between companies or business units. • Reuse and Flexibility: Existing application components can be easily integrated regardless of implementation details. • Dynamic Discovery of Services, Interfaces, and Implementations: It should be possible to let application clients dynamically, i.e., at runtime, look for and download service address, service binding, and service interface information. • Business Process Orchestration Without Programming: Allows orchestration of business activities into business processes, and executes such aggregated process automatically. The first five requirements are technology oriented. A solution to these requirements is XML-based Web services, or simply Web services. It employs Web standards of HTTP, URLs, and XML as the lingua franca for information and data encoding for platform independence; therefore it is far more flexible and adaptable than earlier approaches. The last requirement relates to the concept of business workflow and workflow management systems. In supply chain management for example, there is a purchase order process at the buyer’s side and a product fulfillment process at the supplier’s side. Each process represents a business workflow or a Web service if it is automated. These two Web services can be combined into one Web service that represents a new business process. The ability to compose new Web services from existing Web services is a powerful feature of Web services; however, it requires standards to support the composition process. This article will provide a simplified exposition of the underlying basic technologies, key standards, the role of business workflows and processes, and critical issues.


2012 ◽  
Vol 2 (4) ◽  
pp. 20-34
Author(s):  
Bob Chermin ◽  
Ingmar Frey ◽  
Hajo Reijers ◽  
Harm Smeets

Even though workflow management systems are currently not being applied on a wide scale in healthcare settings, their benefits with respect to operational efficiency and reducing patient risk seem enticing. The authors show how an approach that is rooted in simulation can be useful to predict the benefits of using a workflow management system. The approach is discussed and its application is demonstrated in the setting of the pre-operative process as being executed in the Bronovo hospital. The approach is considered useful for other healthcare organizations in search for a better foundation for the application of workflow technology.


2015 ◽  
Vol 3 (1) ◽  
pp. 4-20
Author(s):  
John Ndeta ◽  
Stamatia A. Katriou ◽  
Kerstin V. Siakas

Abstract In today’s highly competitive and rapidly changing environment, e-businesses constantly have to modify their business processes, i.e. the flow of documents and tasks in a business also known as workflow. More flexible Workflow Management Systems are required to support these constantly changing processes. In this research a platform independent architecture for the design of e-workflow systems is illustrated. The architecture includes an information pool, namely a Workflow Pattern Repository, which contains patterns, which are repeatable solutions to reoccurring problems, in order to make the system more apt to change and assist the workflow designer/user in defining workflows faster and more accurately. The patterns in the repository are in the form of UML activity diagram templates. A straightforward input format for storing patterns in the repository is provided along with an example of its practical application.


2014 ◽  
Vol 56 (6) ◽  
Author(s):  
Thomas Bauereiß ◽  
Dieter Hutter

AbstractWorkflow management plays an important role in analyzing and automating business processes. Security requirements in workflow management systems are typically mapped to (role-based) access control configurations. This paper focuses on information flow control, taking into account implicit information leaks. The presented approach operates on a specification level in which no executable program is available yet. We illustrate the modeling of a workflow management system as a composition of state-event systems, each representing one of the activities of the workflow. This facilitates distributed deployment and eases verification by splitting up the verification of the overall system into verification of the individual components. Confidentiality requirements are modeled in terms of information flow predicates using the MAKS framework and verified following existing decomposition methodologies, which are adapted for open systems with ongoing user interaction. We discuss the interaction with other security requirements, notably separation of duty.


Sign in / Sign up

Export Citation Format

Share Document