GRAPHICAL REPRESENTATION OF COMPATIBLE WORKFLOW STEPS

FIELD OF THE INVENTION

The present invention generally relates to the field of workflows, and more particularly relates to managing workflow steps through a user interface.

BACKGROUND OF THE INVENTION

Workflow is among the most highly investigated problems in distributed computing and many complete workflow systems exist. However, these workflow systems execute jobs in a homogeneous way. For example, BPEL4WS is a workflow specification for orchestrating Web Service invocations in order to realize a workflow. IBM's LoadLeveler is a high performance computing job scheduler that can orchestrate workflows running on clusters of machines connected by a network. Lotus Workflow is a system for orchestrating workflow where the jobs are performed by user applications on personal workstations and orchestrated via a document management system.

Although useful, these workflow systems are not without their deficiencies, drawbacks, and problems. For example, these workflow systems cannot orchestrate workflow where the job steps involved are high performance computing applications, web services, and user applications. In addition, advanced fields such as cancer research require workflows involving the participation of laboratory equipment.

Workflow systems sometimes provide user interfaces for user interaction with the workflow. However, these user interfaces are often difficult to use when trying to find compatible input and output parameters for workflow steps. For example, in a semantic data application, where a data object in the system might represent any number of different semantic data types, it is not always possible for a user to easily determine which parts of an application can provide and or accept the data objects when they are involved in a drag and drop operation. Current user interfaces utilizing drag and drop features, show a user which parts of the application can accept or provide a data object by changing the mouse icon when the a data object is dragged over different parts of the application. The drawback of this type of system, is that the user must first drag the data object to all possible parts of an application to determine which parts of the application are valid receptors of the drag and drop operation.

Therefore a need exists to overcome the problems with the prior art as discussed above.

SUMMARY OF THE INVENTION

Briefly, in accordance with the present invention, disclosed are a method, user interface, and computer readable medium for graphically representing compatible workflow components to a user. The method includes graphically displaying, in a graphical user interface, a plurality of steps in a workflow. A user's selection is received, wherein the selection is for at least one step in the plurality of steps. The user's selection denotes at least one selected step. At least a portion of the graphical user interface is dynamically populated for displaying a list with at least one workflow component that is compatible to accept an output from the selected step. The list can also display at least one workflow component that can provide an output to the selected step. The workflow component is selectable by the user so that it can be added to the workflow.

In another embodiment, a user interface for graphically representing compatible workflow components to a user is disclosed. The user interface includes at least one window for graphically displaying a plurality of steps in a workflow. At least a first visual indicator denotes a user's selection for at least one step in the plurality of steps. At least a first portion of the window comprises at least a workflow component list. The workflow component list is dynamically populated with at least one workflow component that is compatible to at least one of accepting an output from the selected step. The workflow component list can also be dynamically populated with at least one workflow component that can provide an output to the selected step. The workflow component is selectable by the user so that it can be added to the workflow.

In yet another embodiment, a computer readable medium for graphically representing compatible workflow components to a user is disclosed. The computer readable medium comprises instructions for graphically displaying, in a graphical user interface, a plurality of steps in a workflow. A user's selection is received, wherein the selection is for at least one step in the plurality of steps. The users selection denotes at least one selected step. At least a portion of the graphical user interface is dynamically populated for displaying a list with at least one workflow component that is compatible to accept an output from the selected step. The list can also display at least one workflow component that can provide an output to the selected step. The workflow component is selectable by the user so that it can be added to the workflow.

An advantage of the foregoing embodiment is that a user is able to use a workflow user interface to manage a workflow. When a workflow step is selected all of the compatible steps that can accept its output or provide an input are automatically displayed. Also, the user interface can be dynamically populated with a list of compatible workflow steps (or data values) that provide an input to the selected step, workflow steps that can accept the output from the selected step. A user does not have to drag a particular workflow step over the other steps to find out which steps can accept the output of the particular workflow step. The user interface provides a user with visual feedback or cues that help identify compatible inputs and outputs.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying figures where like reference numerals refer to identical or functionally similar elements throughout the separate views, and which together with the detailed description below are incorporated in and form part of the specification, serve to further illustrate various embodiments and to explain various principles and advantages all in accordance with the present invention.

FIG. 1 is block diagram illustrating an exemplary workflow management system according to an embodiment of the present invention;

FIG. 2 is a block diagram illustrating an exemplary information processing according to an embodiment of the present invention

FIG. 3A to FIG. 3L are exemplary annotated listings of Resource Description Framework triples that correspond to a workflow;

FIG. 4 is a block diagram illustrating an exemplary workflow user interface according to an embodiment of the present invention;

FIG. 5 is a block diagram illustrating the exemplary workflow user interface according to another embodiment of the present invention;

FIG. 6 is a block diagram illustrating the exemplary workflow user interface according to another embodiment of the present invention;

FIG. 7 is a block diagram illustrating another example of the workflow user interface according to another embodiment of the present invention;

FIG. 8 is a block diagram illustrating another example of the workflow user interface according to another embodiment of the present invention;

FIG. 9 is a block diagram illustrating another example of the workflow user interface according to another embodiment of the present invention;

FIG. 10 is an input/output flow diagram illustrating the input/output relationship between steps of a workflow according to an embodiment of the present invention;

FIG. 11 is an operational flow diagram illustrating an exemplary process of a central storage system maintaining a workflow according to an embodiment of the present invention;

FIG. 12 is an operational flow diagram illustrating an exemplary process of a participant of a workflow interacting with the workflow according to an embodiment of the present invention;

FIG. 13 is an operational flow diagram illustrating an exemplary process of a graphically displaying workflow steps and their compatibility for accepting each others output through a user interface according to an embodiment of the present invention;

FIG. 14 is an operational flow diagram illustrating an exemplary process of a determining which workflow steps can accept an output of another workflow step according to an embodiment of the present invention;

FIG. 15 is an operational flow diagram illustrating an exemplary process of a visually indicating which workflow steps can provide a compatible input for the selected workflow step, according to an embodiment of the present invention;

FIG. 16 is an operational flow diagram illustrating an exemplary process of graphically providing available inputs for a workflow step to a user through a workflow user interface 136; and

FIG. 17 is an operational flow diagram illustrating an exemplary process of graphically providing available workflow steps to a user that can accept an output of a selected workflow step as an input.

DETAILED DESCRIPTION

As required, detailed embodiments of the present invention are disclosed herein; however, it is to be understood that the disclosed embodiments are merely exemplary of the invention, which can be embodied in various forms. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present invention in virtually any appropriately detailed structure. Further, the terms and phrases used herein are not intended to be limiting; but rather, to provide an understandable description of the invention.

The terms “a” or “an”, as used herein, are defined as one or more than one. The term plurality, as used herein, is defined as two or more than two. The term another, as used herein, is defined as at least a second or more. The terms including and/or having, as used herein, are defined as comprising (i.e., open language). The term coupled, as used herein, is defined as connected, although not necessarily directly, and not necessarily mechanically. The terms program, software application, and the like as used herein, are defined as a sequence of instructions designed for execution on a computer system. A program, computer program, or software application may include a subroutine, a function, a procedure, an object method, an object implementation, an executable application, an applet, a servlet, a source code, an object code, a shared library/dynamic load library and/or other sequence of instructions designed for execution on a computer system.

The present invention, according to an embodiment, overcomes problems with the prior art by orchestrating a workflow in a non-centralized fashion. In other words, a single program is not continually orchestrating the workflow. Another advantage of the present invention is that a system can orchestrate workflows involving diverse types of processes in a highly distributed environment. For example, job steps involving high processing computer applications, web services, user applications, and laboratory equipment are able to be integrated and execute a workflow.

Another advantage of the present invention is that a user is able to use a workflow user interface to manage a workflow. When a workflow step is selected all of the compatible steps that can accept its output or provide an input are automatically displayed. A user does not have to drag an input connector or an output connector over each step to find out which steps can accept the output. The user interface provides a user with visual feedback or cures that help identify compatible inputs and outputs. Additionally, the user interface can be dynamically updated to display a list of compatible workflow steps that can provide an input to a selected workflow step or accept an output of the selected workflow step. The use interface can also display a list a data values that can be used as an input for a selected workflow step.

Exemplary Workflow Management System

According to an embodiment of the present invention, as shown in FIG. 1, an exemplary workflow management system 100 is illustrated. FIG. 1 shows a system 100 comprising Participant A 102, Participant B 104, Participant C 106, Participant D 108, Participant E 110, a central storage system 112, and a network 114. A participant, in one embodiment, is an information processing system or a plurality of information processing system communicatively coupled together to perform one or more steps of a workflow. A workflow, for example, is one or more interrelated steps that are distinct and where the output of one step can be the input of another step. In another embodiment, a participant is laboratory equipment communicatively coupled to an information processing system. Each participant includes at least one resource such as processing capabilities, algorithms, or the like that are needed to perform the one or more steps of the workflow. For example, in one embodiment, Participant A 102 provides a high performance computing/grid environment comprising a plurality of information processing systems. The plurality of information processing systems, for example, concurrently executes one or more workflow steps that require significant computation. Participant B 104, in one embodiment, is a notebook computer allowing human interaction such as output verification in real time.

Participant C 106, in one embodiment, is a workstation comprising programs made available by the user of the workstation to be used as workflow steps. Participant D 108, for example, is laboratory equipment used for scientific workflows and interacts with the system 100 through an information processing system. Participant E 110, in one embodiment, is a web services invoker that is used to invoke web services on behalf of the users of the Participant E 110 information processing system. Each participant 102, 104, 106, 108, 110 communicates with the central storage system 112 through the network 114. The network 114, according to one embodiment, is a LAN, WAN, World Wide Web, wired, wireless network, or the like.

Each participant 102, 104, 106, 108, 110 includes a workflow analyzer 116, 118, 120, 122, 124, a workflow updater 126, 128, 130, 132, 134, and a workflow user interface 136, 138, 140, 142, 144, which will be discussed in greater detail below. The central storage system 112 includes a workflow database 146, a workflow information transceiver 148, and a workflow updater 150. In one embodiment, the central storage system 112 is a resource description framework (“RDF”) storage system. In another embodiment, the central storage system 112 is an extensible markup language (“XML”) storage system. The workflow database 146, for example, is a file such as a relational database or an object oriented database that backs the central storage system 112. The workflow database 146, in one embodiment, publishes updates associated with workflows in the database 146 using a high performance publish/subscribe system such as a Collections, ACLS, Replication, and Transaction system (“CART”). CART is an implementation of an RDF-based central storage system such as the central storage system 112. In a CART system each triple <subject><predicate><object> may be placed in zero or more collections for the purpose of identification and subscription in publication-subscription services.

An ACL is an access control list. Each triple or collection has an access control list that determines who can read/modify the triple. Client's of CART write their data first to a local memory or file store. The data may then be replicated to the central storage system 112, and new data is pulled down based on subscription. In one embodiment of the present invention, a client-pull rather than a server push is used to retrieve the data. In another embodiment of the present invention, both a client-pull and a server push are used to retrieve the data. Each time a client of CART submits data to the central storage system 112, the updates are processed as a transaction so that any conflicts with other users are resolved or errors are raised.

In one embodiment, the central storage system stores RDF. For example, the central storage system 112 stores OWL-S, which is a set of RDF ontologies created using the Ontology Web Language (“OWL”) that defines how workflows are embodied in RDF. For example, if a particular step of a workflow outputs an image, that step commits the image itself to a data storage system (not shown), and provides the RDF central storage system with a link or pointer to the actual data to be stored with the workflow image. These links or pointers, in one embodiment, are file paths in the case of a distributed file system or HTTP/FTP URL's when the data storage system (not shown) is a Web Server. In another embodiment, a life science identifier (“LSID”) is used. A LSID uniquely identifies and resolves pieces of data that are used or created in a workflow. LSIDs were initially developed for the Life Sciences community but can be easily applied in any data-needy domain. The data storage system (not shown) that assigns LSIDs to data (and in turn provides their resolution) is called a dynamic data repository (“DDR”).

The workflow transceiver 148 transmits and receives workflow information. For example, workflows and workflow updates that are transmitted by the participants 102, 104, 106, 108, 110 are received at the central storage system 112 by the workflow information transceiver 148. In one embodiment, the workflow information transceiver is a general purpose RDF storage service. The workflow information transceiver 148 also transmits notifications to the participants 102, 104, 106, 108, 110 when a workflow is updated. A workflow is updated, for example, when a step of the workflow is completed. The workflow updater 150 updates a workflow in the workflow database 146 based on information received by the workflow information transceiver 148. The workflow database 146 also includes at least one record 152 for each workflow managed by the workflow database 146. The workflow database record 152 will be discussed in greater detail below.

Exemplary Information Processing System

FIG. 2 is a block diagram illustrating a more detailed view of the Participant A 102 information processing system according to an embodiment of the present invention. Although the following discussion is with respect to the Participant A 102 information processing system, the following discussion is also applicable to each of the information processing systems used as a participant or communicatively coupled to a participant of a workflow as shown in FIG. 1. The Participant A 102 information processing system is based upon a suitably configured processing system adapted to implement the exemplary embodiment of the present invention. Any suitably configured processing system is similarly able to be used as the Participant A 102 information processing system by embodiments of the present invention, for example, a personal computer, workstation, or the like. The Participant A 102 information processing system includes a computer 202. The computer 202 has a processor 204 that is connected to a main memory 206, mass storage interface 208, terminal interface 210, and network adapter hardware 212. A system bus 214 interconnects these system components. The mass storage interface 208 is used to connect mass storage devices, such as data storage device 216, to the Participant A 102 information processing system. One specific type of data storage device is a computer readable medium such as a floppy disk drive, which may be used to store data to and read data from a CD 218 or floppy diskette (not shown). Another type of data storage device is a data storage device configured to support NTFS type file system operations.

The main memory 206 comprises the workflow analyzer 116. The workflow analyzer 116 analyzes the workflow in the central storage system 112. For example, a participant subscribes to the central storage system 112. Each step in a workflow that is stored in the central storage system 112 identifies a particular location/participant where the step is to be executed. As a subscriber, the participant recognizes that it is a participant of a workflow and the workflow analyzer 116 analyzes the workflow to determine which steps of the workflow are currently executable at its location. The workflow analyzer 116 also analyzes a workflow after the Participant A 102 information processing system receives a notification from the central storage system 112 that the workflow has been updated.

The main memory 206 also includes the workflow updater 126. The workflow updater 126 transmits workflow update information to the central storage system 112. Workflow update information, in one embodiment, includes output data from a completed step; a notification that a particular step has been completed; and the like. The main memory also comprises a workflow user interface 136. The workflow user interface 136 allows a user at the Participant A 102 information processing system to interact with one or more subscribed to workflows. For example, the workflow user interface 136, in one embodiment, indicates visually, the inputs and outputs of the steps that may be wired together. In another embodiment, the user interface 136 can be dynamically updated to show a list of currently available workflow steps that can accept an output from a workflow step selected in the user interface 136. The user interface 136 can also be dynamically updated to display a list of currently available workflow steps or data values that can provide an input to the selected workflow step.

The Participant A 102 information processing system also includes a job scheduler (not shown) such as IBM's Load Leveler in the main memory 206. The job scheduler (not shown), among other things, allows multiple workflow steps to be performed on the Participant A 102 information processing system. In one embodiment, the main memory 206 also includes a workflow language interpreter (not shown) such as an OWL-S interpreter, a BPEL4WS interpreter, or the like. The workflow language interpreter (not shown) allows the workflow analyzer 136 to determine what workflow steps are next in the workflow. The workflow language interpreter (not shown) also allows the workflow analyzer 136 to determine if the steps of the workflow are bound to the current location and if they can be executed under one or more identities of the Participant A 102.

The identity of a participant, in one embodiment, is the username under which a particular participant interacts with the central storage system 112, for example, CART. The identity of a participant is also used as the login in the embodiment where a DDR data store is performed. A workflow, in one embodiment, identifies the identity under which a step is executable. For example, a first user of the information processing system may make certain resources available for the workflow while a second user may not.

An application 220 such as an application needed for executing a workflow step is also included in the main memory 206. The application 220, for example, is running or waiting to be executed. Although illustrated as concurrently resident in the main memory 206, it is clear that respective components of the main memory 206 are not required to be completely resident in the main memory 206 at all times or even at the same time. In one embodiment, the server1106 utilizes conventional virtual addressing mechanisms to allow programs to behave as if they have access to a large, single storage entity, referred to herein as a computer system memory, instead of access to multiple, smaller storage entities such as the main memory 206 and data storage device 216, Note that the term “computer system memory” is used herein to generically refer to the entire virtual memory of the Participant A 102 information processing system.

Although only one CPU 204 is illustrated for computer 202, computer systems with multiple CPUs can be used equally effectively. Embodiments of the present invention further incorporate interfaces that each includes separate, fully programmed microprocessors that are used to off-load processing from the CPU 204. Terminal interface 210 is used to directly connect one or more terminals 222 to computer 202 to provide a user interface to the server1106. These terminals 222, which are able to be non-intelligent or fully programmable workstations, are used to allow system administrators and users to communicate with the Participant A 102 information processing system. The terminal 222 is also able to consist of user interface and peripheral devices that are connected to computer 202 and controlled by terminal interface hardware included in the terminal I/F 210 that includes video adapters and interfaces for keyboards, pointing devices, and the like.

An operating system (not shown) included in the main memory is a suitable multitasking operating system such as the Linux, UNIX, Windows XP, and Windows Server 2003 operating system. Embodiments of the present invention are able to use any other suitable operating system. Some embodiments of the present invention utilize architectures, such as an object oriented framework mechanism, that allows instructions of the components of operating system (not shown) to be executed on any processor located within the server1106.

The network adapter hardware 212 is used to provide an interface to the network 114. Embodiments of the present invention are able to be adapted to work with any data communications connections including present day analog and/or digital techniques or via a future networking mechanism.

Although the exemplary embodiments of the present invention are described in the context of a fully functional computer system, those skilled in the art will appreciate that embodiments are capable of being distributed as a program product via floppy disk, e.g. floppy disk 218, CD ROM, or other form of recordable media, or via any type of electronic transmission mechanism.

Exemplary Annotated Listing of Resource Description Framework Triples

FIG. 3 illustrates an exemplary annotated listing of Resource Description Framework triples that correspond to a workflow. For example, FIG. 3 shows the RDF triples for a workflow that is about to be executed. As each step is executed, as described will be described below, each participant 102, 104, 108, 108, 110 submits updates. The workflow updater 126 updates the RDF triples accordingly.

Exemplary Workflow User Interface

FIG. 4 to FIG. 9 illustrate an exemplary workflow user interface 136 according to an embodiment of the present invention. FIG. 4 illustrates a workflow user interface 136 for graphically displaying compatible inputs and outputs of steps can be wired together. The workflow user interface 136, among other things, visually represents a workflow. A user can create/delete workflow steps, track the progress of the workflow, manipulate workflow steps, add/change input, and output parameters of a workflow step, and the like through the workflow user interface 136.

The workflow user interface 136 includes a window 402 for displaying various components of the interface 136. For example, the steps 404, 406, 408, 410 of a selected workflow are graphically displayed in the window 402. FIG. 4 shows a workflow comprising Step A 404, Step B 406, Step C 408, and Step N 410. The steps 404, 406, 408, 410 are represented graphically by a box. In another embodiment, the steps 404, 406, 408, 410 are represented graphically by an icon, picture, or the like. In one embodiment, inputs and outputs of a step are also graphically represented in the interface 136. For example, input boxes 412, 414, 416, 418 and output boxes 420, 422, 424, 426 are included in each step 404, 406, 408, 410. Although only one input/output box is shown in FIG. 4, each input/output connector can represent zero or more inputs or outputs, respectively.

The workflow user interface 136 allows a user to select one or more of the graphically represented steps 404, 406, 408, 410. When a user selects a step 404, 406, 408, 410, the appearance of the selected step is visually altered. For example, Step A 404 is selected in FIG. 4 and has a solid outlined box 428 surrounding the box representing Step A 404. In another embodiment, one or more colors are used to represent selected and non-selected steps. In an alternative embodiment, the box representing Step A 404 is resized, shaded, changed to a new graphic, or the like to visually indicate to a user that the step has been selected.

After a user has selected a step, each step in the workflow that can accept the output of the selected step is also visually identified to the user. For example, in FIG. 4, Step C 408 is the only step that can accept the output of Step A 404. Therefore, the box representing Step C 406 has a dashed box 430 surrounding it to visually indicate to the user that Step C 408 can accept the output of Step A 408. In another embodiment, one or more colors are used to represent that a step can accept an output of another step. Different colors represent the type and strength of compatibility between the output of a step and what input can be accepted at another step. For example, a first color can represent a strong compatibility and a second color can represent a weaker compatibility.

The strength of the compatibility, in one embodiment, is a function of analyzing the outputs and inputs of the steps as well as other metadata in the workflow system. For example, connection precedence, metadata between workflow steps such as organization, author, licenses, and the like are analyzed to determine the strength of compatibility. In an alternative embodiment, the box representing Step C 408 is resized, shaded, changed to a new graphic, or the like to visually indicate to a user that the step can accept the output of Step A 408. In another embodiment, the strength of the compatibility is based on a number of connection matches. For example, the percentage of inputs/outputs that are themselves compatible. In another embodiment, the strength of the compatibility is also based on the number of previous times these workflow steps have been wired together. This data, for example, can be queried in the central storage system 112.

In an alternative embodiment, a user drags a pointer (not shown) over the graphic representing a step or an output box 420, 422, 424, 426 of a step 404, 406, 408, 410. The steps that can accept the output of the currently pointed to step are visually altered. For example, the graphic representing a step that can accept the output is resized, shaded, changed to a new graphic, or the like to visually indicate the ability to accept the output. In another embodiment, as the user drags the pointer (not shown) over an output box of a step, the type output generated by the step and/or a description of the output is displayed to the user.

FIG. 5 shows one embodiment of the user interface after the output of Step A 404 has been selected to be the input of Step C 408. The workflow user interface 136 allows a user to select an output of a step and drag a connector over to an input of a step that can accept the output. For example, FIG. 5 shows a connector 502 connecting the output box 420 of Step A 404 to the input box 416 of Step C 408. The connector 502, in one embodiment, includes a color representing the type and strength of compatibility between the output of Step A 402 the acceptable input of Step C 408 as described above with reference to FIG. 4.

FIG. 6 illustrates the workflow user interface 136 according to another embodiment of the present invention. FIG. 6 illustrates the workflow user interface 136 for showing a user available workflow steps within the application and outside the application. FIG. 6 shows the window 402 for displaying various components of the interface 136. For example, the steps 404, 406, 408, 410 of a selected workflow are graphically displayed in the window 402. FIG. 6 shows a workflow comprising a Step A 404, a Step B 406, a Step C 408, and a Step N 410 each step including an input 412, 414, 416, 418 and an output 420, 422, 424, 426.

A user can select any of the available workflow steps in the window (e.g., palette) 604 and add the steps to the workflow workspace 606. The same workflow steps can be added to the workflow workspace 606 more than once. In one embodiment a user selects a workflow step for identifying which of the non-selected workflow steps can provide an input to the selected step. For example, the user selects the graphic representing Step B 406, which is then highlighted by a box 602 as described above with reference to FIG. 4. If any of the remaining steps can provide an input to Step B 406, the graphic representing those steps is visually altered (as described above with reference to FIG. 4) to indicate this.

In one embodiment, the palette 604 includes a list 608 workflow steps that are currently available to add to the workflow workspace 606. For example, workflow step A 404 through workflow step N 410 is included in the list 608. A user can select a widget in the list 608 corresponding to a workflow step, which is then added to the workflow workspace 606. Alternatively, the user can drag the widget over to the workflow workspace 608 causing the workflow step to be added to the workflow workspace 606. FIG. 6 shows the widget 610 corresponding to workflow step B 406 as being highlighted as an example to show that the widget 610 has been selected by a user.

The workflow steps, in one embodiment, are part of another application residing on the information processing system being used by the user or communicatively coupled to the user information processing system through a network. For example, the user interface 136 can show the workflow steps from a life sciences application for accepting images from a microscope residing on the user information processing system. In one embodiment, all currently opened workflow steps in an application are searched for and displayed to the user through the user interface 136.

In one embodiment, the palette 604 is dynamic so that as more workflow steps become available, the palette 604 is dynamically updated to show these new workflow steps. In another embodiment, as shown in FIG. 7, as the workflow steps displayed in the palette 604 become unavailable, the palette 604 is dynamically updated to remove these workflow steps. For example, FIG. 7 shows that workflow step A 404, workflow step C 408, and workflow step N 410 have been removed.

In another embodiment, as shown in FIG. 8, the palette 604 can also display workflow steps that can accept the output of a selected workflow step or that can provide an input to the selected workflow step. For example, FIG. 8 shows workflow step A 404 as being selected, as indicated by the dashed box 702. The palette 604, in the example of FIG. 8, displays a list 808 including workflow step D 704 and workflow step E 706. The workflow steps 704, 706 can either be steps that can accept workflow step A's 404 output as an input or provide an input to workflow step A 404. The palette 604 can be dynamically updated with these workflow steps 704, 706 when a workflow step in the workflow workspace 606 is selected. Alternatively, the palette 604 can be dynamically updated with the appropriate information when an input portion 414 or an output portion 422 is selected by a user.

In one embodiment, the palette 604 is dynamically updated to display these workflow steps in addition to workflow steps in the workflow workspace 606 being visually altered to indicate compatibility with the selected workflow step. In other words, as more workflow steps that are compatible with the selected workflow step become available, the palette 604 is dynamically updated to display these new workflow steps. In an alternative embodiment, if the non-selected workflow steps in the workflow workspace 606 cannot accept the output of the selected workflow step (or cannot provide an input), the palette is dynamically updated to display additional compatible workflow steps. The workflow steps 704, 706 in the palette 604 can be selected and added to the workflow workspace 606 as described above.

FIG. 9 shows another embodiment of the user interface 136. Similar to the embodiments discussed above, a user can select a workflow step in the workflow workspace 606. For example, FIG. 9 shows workflow step B 406 as being selected, as indicated by the dashed box 902. As the user selects the input box 414 of workflow step B 406, the palette 604 is dynamically updated to display a list 908 of data values that can be used as an input for the selected workflow step B 406. For example, FIG. 9 shows a list 908 with data value A 904, data value B 906, and data value C 910. These data values 904, 906, 910 can be selected as an input for the selected workflow step B 406. The palette 604 can display these data values 904, 906, 910 in addition to one or more of the non-selected workflow steps in the workflow workspace 606 being able to provide an input to the selected workflow step. In another embodiment, the palette 604 is dynamically updated with data values when the non-selected workflow steps in the workflow workspace 606 cannot provide an input to the selected workflow step.

It should be noted that the palette 604 can display more than one item type at a time. For example, the palette 604 can display, any combination of item types such as workflow steps that can provide an input to a selected workflow step, data values that be used as input, and workflow steps that can accept the output of a selected workflow step. Also, in one embodiment, the dynamic updating includes querying a global database such as the central storage system 112. This database is queried to determine if any other workflow steps exist that can provide an input to the selected workflow step or accept the output of the selected step as an input. The database, in one embodiment, is an RDF store and the palette can be dynamically populated using a collection of RDQL or SPARQL queries. In one example, one such query determines which potential workflow steps in the database have an input or output that is compatible with the output or input of the selected workflow step.

Exemplary Workflow Input/Output Flow Diagram

FIG. 10 illustrates an exemplary input/output flow diagram according to an embodiment of the present invention. FIG. 10 shows a Step E 1002, a Step F 1004, and a Step N 1006. In this embodiment, Step E 1002 has a single input 1008 and generates a plurality of outputs 1010, 1012, 1014. For example, Step E 1002 can perform multiple actions upon a single input to generate one or more outputs. The input 1008, in this embodiment is a predefined input. For example, the author of workflow Step E 1002 submitted a predefined value for the input 1008 of Step E 1002 when the workflow was submitted to the central storage system 112. In another embodiment, after the workflow is submitted, but before its execution, an input value can be entered for a step. In an alternative embodiment, the input 1008 is an output of another step.

Output 1010, for example, is an intermediary value that is stored for verification or later use. For example, a user may retrieve the output 1010 and verify its value to ensure the workflow is executing properly. The second and third outputs 1012, 1014 of Step E 1002 are used as inputs for Step F 1004. Step F also has a predefined input 1016. Step F 1004 produces two outputs 1018, 1020. One output 1018 is used as an intermediary value and the other output is used as an input for another step. Step N 1006 includes two predefined inputs 1022, 1024 which result in one output 1026. The output 1026 of Step N 1006 in one embodiment is an intermediary value in this embodiment. If Step N 1006 is the final step in the workflow, the output 726 is the final result of the workflow.

Exemplary Process of Sending Participants of a Workflow Information Regarding the Workflow

FIG. 11 is an operational flow diagram illustrating an exemplary process of communicating workflow information to participants of the workflow by the central storage system 112. The operational flow diagram of FIG. 11 begins at step 1102 and flows directly to step 1104. The central storage system 112, at step 1104, receives a workflow from a workflow participant. In another embodiment, the workflow is submitted by a user on an information processing machine which is not a participant of the workflow. The central storage system 112, at step 1106, enters the workflow into the workflow database 146 where a record 152 is created for the entered workflow. The received workflow, for example, includes a list of participants for the workflow and any predefined values for the steps of the workflow

A subscriber to the central storage system 112, at step 1108, is identified as a participant of a workflow and receives information about the workflow. For example, a participant subscribes to the central storage system 112. Each step in a workflow that is stored in the central storage system 112 identifies a particular location/participant where the step is to be executed. A participant is selected by a creator of a workflow step, in one embodiment, based on the ability to perform a step, location, and identity of the participant. After each participant executes a step of the workflow, the workflow information transceiver 148, at step 1110, receives workflow updates from each participant. For example, the update information, in one embodiment, includes completed status identifier, output values generated by completing the step, and the like. In another embodiment, workflow update information is received when a participant manipulates a workflow step. A participant, for example, can change the input parameters for the step.

The workflow updater 150, at step 1112, updates the workflow database 146 based on the received updates from the participants. The central storage system 112, at step 1114, determines if the workflow is completed. For example, when a participant completes a workflow step it queries the central storage system 112 to determine if the completed step was the last step of the workflow. If the participant determines that the workflow is completed, it transmits information to the central storage system 112 identifying the workflow as being completed. In other words, the participant flags the workflow as being completed. The central storage system receives this information from the participant and determines that the workflow is complete.

If the result of this determination is positive, the central storage system 112, at step 1116, notifies each participant that the workflow has been completed. The control then exits at step 1118. If the result of this determination is negative, the central storage system 112, at step 1120, notifies the participants that the workflow has been updated. The central storage system 112 continues to receive workflow updates from the participants until the workflow has been completed. In an embodiment where the central storage system 112 is an RDF central storage system, the workflow retained in the central storage system 112 can be modified after it has been completed. For example, a human user can add additional RDF statements commenting on the success of the workflow. The participants of the work flow are then be notified of these changes

Exemplary Process of Managing a Workflow

FIG. 12 is an operational flow diagram illustrating an exemplary process of at least one workflow step by a participant of the workflow. The operational flow diagram of FIG. 12 begins at step 1202 and flows directly to step 1204. A workflow participant such as Participant A 102, at step 1204, is identified as a participant of a workflow. Each participant 102, 104, 106, 108, 110, at step 1206, performs a pull operation to obtain the workflow from the central storage system 112. The workflow, at step 1208, is then analyzed by each participant 102, 104, 106, 108, 110. Each participant 102, 104, 106, 108, 110, at step 1210, then determines if any of the steps associated with the respective participant can be currently performed.

If the result of this determination is negative, the participant, at step 1212, waits for another notification from the central storage system 112. If the result of this determination is positive the participant, at step 1214, executes the workflow step. For example, in an exemplary life sciences workflow, Participant D 108 is laboratory equipment such as a microscope that is coupled to an information processing system. The workflow step to be performed by Participant D 108 is to submit an image for processing. After a participant 102, 104, 106, 108, 110 executes one or more steps, the participant, at step 1216, transmits workflow update information to the central storage system 112. For example, Participant D transmits update information in using RDF language including a pointer to the image that is to be processed.

The participants 102, 104, 106, 108, 110, at step 1218, receive a notification from the central server 112 informing the participants 102, 104, 106, 108, 110 that the workflow has been updated. The participants 102, 104, 106, 108, 110, at step 1220 determine if the workflow has been completed based on the update information sent by the central storage system 112. If the result of this determination is positive, the control flow exits at step 1222. If the result of this determination is negative the control flows to step 1206 where the participants 102, 104, 106, 108, 110 download the workflow. For example, after the workflow is updated by the central server 112 to reflect the execution of a step by Participant D, the participants are notified and determine if any of the remaining steps of the workflow can be currently executed.

Participant A 102, in one embodiment, is a high performance computing environment and uses an algorithm submitted by, for example, Participant C 106 for processing the image submitted by Participant D 108. The processing of the image by Participant A 102 and the submission of an algorithm by Participant C 106, in one embodiment, are separate steps of the workflow. For example, Participant A 102 determines that it can process the image only if the algorithm has been submitted by Participant C 106. Participant A uses both the image and algorithm as its inputs. Participant E 110, in one embodiment, are web services such as services for life sciences data that can also be used by Participant A 102 for processing the image submitted by Participant D 108. After Participant A 102 processes the image and submits its update information to the central storage system 112, Participant B 104, for example, determines that it can perform the workflow step associated with it. For example, Participant B 104 is a personal computer that allows a human to verify the results of Participant A 102. Once the verification process is completed by Participant B 104, Participant B 104 submits its update information to the central storage system 112, which determines that the workflow is completed.

One advantage of the present invention is that a workflow can be orchestrated in a non-centralized fashion. In other words, a single program is not continually orchestrating the workflow. Another advantage of the present invention is that a system can orchestrate workflows involving diverse types of processes in a highly distributed environment. For example, job steps involving high processing computer applications, web services, user applications, and laboratory equipment are able to be integrated and execute a workflow.

Exemplary Process of Providing Workflow Management Through a Workflow User Interface

FIG. 13 and FIG. 14 are operational flow diagrams illustrating an exemplary process of at providing graphical management of a workflow to a user through a workflow user interface 136. The operational flow diagram of FIG. 13 begins at step 1302 and flows directly to step 1304. The workflow user interface 136, at step 1304, graphically displays steps of a workflow. For example, the steps are displayed as boxes or any other shape, picture, icon, or the like. The user interface 136, at step 1306, receives a user's selection of at least one workflow step. For example, a user can user a mouse pointer to click on a box representing a workflow step thereby selecting it.

The output, at step 1308, of the selected step is analyzed to determine if it can be used as an input of at least one of the non-selected steps. If the result of this determination is negative, the user interface 136, at step 1310, displays a message to the user stating that the output of the selected workflow step cannot be used as an input of the non-selected steps. The control flow then exits at step 1312. If the result of this determination is positive, the non-selected workflow step, at step 1314, is graphically changed to indicate that it can accept the output of the selected step.

For example, in one embodiment, workflow steps are registered with the central storage system 112. This registration process tells the central storage system 112 the data types the workflow step provides and can accept. In one embodiment, when a user selects a workflow step through the user interface 136, a notification is sent to the central storage system 112. The central storage system notifies all the registered workflow steps that a selection of a certain data type has been made, and those workflow steps can visually change their user interface to show the user that they can either accept or not accept the selected data type. For example, the shape, icon, or picture representing the non-selected workflow step is changed, resized, shaded, or painted with a different color. The operational flow then exits at step 1316.

FIG. 14 illustrates a more detailed process of determining the compatibility of using an output of one workflow step as an input of another workflow step. The operational flow diagram of FIG. 14 begins at step 1402 and flows directly to step 1404. The output of a selected workflow step, at step 1404, is analyzed to determine whether it can be used as an input of a non-selected step. If the result of this determination is negative, the user, at step 1406, is notified that the output cannot be used as an input of another workflow step. The control flow then exits at step 1408. If the result of this determination is positive, the output type of the selected step, at step 1410, is compared with the input type of the non-selected workflow step. Also, metadata associated with the output of the selected workflow step, at step 1412, is compared with metadata associated with the input of the non-selected step. In one embodiment, connection precedence and metadata such as organization, author, license, and the like are compared.

A compatibility strength, at step 1414, is determined from the comparisons of steps 1410 and 1412 between the output of the selected step and the input of the non-selected step. If the compatibility is determined to be high, at step 1416, a connection line 502 between the output of the selected workflow step and the input of the non-selected step, at step 1418, is changed to a first color representing high compatibility. If the compatibility is determined to be medium, at step 1420, the connection wire 502, at step 1422, is changed to a second color representing medium compatibility. If the compatibility is determined to not be high or medium, the compatibility is low and the connection line 502, at step 1424, is changed to a color representing a low compatibility. The control flow then exits at step 1426.

Exemplary Process of Providing a Graphic Representation of Available Inputs for a Workflow Step

FIG. 15 illustrates an exemplary process of graphically providing available inputs for a workflow step to a user through a workflow user interface 136. The operational flow diagram of FIG. 15 begins at step 1502 and flows directly to step 1504. The operational flow diagram of FIG. 15 begins at step 1502 and flows directly to step 1504. The workflow user interface 136, at step 1004, graphically displays steps of a workflow. For example, the steps are displayed as boxes or any other shape, picture, icon, or the like. The user interface 136, at step 1506, receives a user's selection of at least one workflow step. For example, a user can user a mouse pointer to click on a box representing a workflow step thereby selecting it.

The non-selected steps, at step 1508, are analyzed to determine whether the non-selected steps can provide an input to the selected step. If the result of this determination is positive, the non-selected step, at step 1510, is graphically changed to indicate that it can provide an input as discussed above with reference to FIG. 13 and FIG. 14. The control flow then exits at step 1512. If the result of this determination is negative, the user interface 136, at step 1514, notifies the user that none of the steps in the workflow can provide the selected step with an input. Alternatively, the description of FIG. 15 is also applicable when identifying which of the non-selected steps can accept the input of the selected step.

Exemplary Process of Dynamically Updating Available Inputs for a Workflow Step

FIG. 16 illustrates another exemplary process of graphically providing available inputs for a workflow step to a user through a workflow user interface 136. The operational flow diagram of FIG. 16 begins at step 1602 and flows directly to step 1604. The workflow user interface 136, at step 1604, graphically displays steps of a workflow. For example, the steps are displayed as boxes or any other shape, picture, icon, or the like. The user interface 136, at step 1606, receives a user's selection of at least one workflow step. For example, a user can user a mouse pointer to click on a box representing a workflow step thereby selecting it.

The non-selected steps, at step 1608, are analyzed to determine whether the non-selected steps can provide an input to the selected step. If the result of this determination is positive, the non-selected step, at step 1610, is graphically changed to indicate that it can provide an input as discussed above with reference to FIG. 13 and FIG. 14. The control flow then exits at step 1612. If the result of this determination is negative, the user interface 136, at step 1614, determines if any other workflow steps exist that can provide an input to the selected workflow step. For example, as discussed above, RDQL or SPARQL queries can be used to query a database comprising potential workflow steps. The queries can be used to identify workflow steps that have an input or output that is compatible with the output or input of the selected workflow step. In another embodiment, a similar process can be used to display compatible data values for the selected workflow step.

If the result of this determination is negative (e.g., no workflow steps exits that can provide an input to the selected workflow step), the user, at step 1616, that an input is not available for the selected workflow step. The control flow then exits at step 1618. If the result of this determination is positive, the palette, at step 1620, is dynamically updated to display a list of workflow steps (or data values) that can provide an input to the selected workflow step. The control flow then exits at step 1622.

Exemplary Process of Dynamically Updating Available Compatible Workflow Steps

FIG. 17 illustrates another exemplary process of graphically providing available workflow steps that can accept an output of a selected workflow step as an input. The operational flow diagram of FIG. 17 begins at step 1702 and flows directly to step 1704. The workflow user interface 136, at step 1704, graphically displays steps of a workflow. For example, the steps are displayed as boxes or any other shape, picture, icon, or the like. The user interface 136, at step 1706, receives a user's selection of at least one workflow step. For example, a user can user a mouse pointer to click on a box representing a workflow step thereby selecting it.

The non-selected steps, at step 1708, are analyzed to determine whether the non-selected steps can accept the output of the selected step as an input. If the result of this determination is positive, the non-selected step, at step 1710, is graphically changed to indicate that it can provide an input as discussed above with reference to FIG. 13 and FIG. 14. The control flow then exits at step 1712. If the result of this determination is negative, the user interface 136, at step 1714, determines if any other workflow steps exist that can accept the output of the selected step as an input. For example, as discussed above, RDQL or SPARQL queries can be used to query a database comprising potential workflow steps. The queries can be used to identify workflow steps that have an input or output that is compatible with the output or input of the selected workflow step. In another embodiment, a similar process can be used to display compatible data values for the selected workflow step.

If the result of this determination is negative (e.g., no workflow steps exits that can accept the output), the user, at step 1716, is notified that a workflow steps are not available that can accept the output. The control flow then exits at step 1718. If the result of this determination is positive, the palette, at step 1720, is dynamically updated to display a list of workflow steps that can accept the output of the selected workflow step. The control flow then exits at step 1622.

Non-Limiting Examples

The foregoing embodiments of the present invention are advantageous because they allow the orchestration a workflow in a non-centralized fashion. In other words, a single program is not continually orchestrating the workflow. Another advantage of the present invention is that a system can orchestrate workflows involving diverse types of processes in a highly distributed environment. For example, job steps involving high processing computer applications, web services, user applications, and laboratory equipment are able to be integrated and execute a workflow. The interaction of such different types of processes can be handled automatically by the workflow management system and special compatibility layers for the different types of processes are not needed.

The present invention can be realized in hardware, software, or a combination of hardware and software. A system according to a preferred embodiment of the present invention can be realized in a centralized fashion in one computer system or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system—or other apparatus adapted for carrying out the methods described herein—is suited A typical combination of hardware and software could be a general purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.

Embodiments of the invention can be implemented as a program product for use with a computer system such as, for example, the computing environment shown in FIG. 1 and described herein. The program(s) of the program product defines functions of the embodiments (including the methods described herein) and can be contained on a variety of computer readable media. Illustrative computer readable medium include, but are not limited to: (i) information permanently stored on non-writable storage medium (e.g., read-only memory devices within a computer such as CD-ROM disk readable by a CD-ROM drive); (ii) alterable information stored on writable storage medium (e.g., floppy disks within a diskette drive or hard-disk drive); or (iii) information conveyed to a computer by a communications medium, such as through a computer or telephone network, including wireless communications. The latter embodiment specifically includes information downloaded from the Internet and other networks. Such computer readable media, when carrying computer-readable instructions that direct the functions of the present invention, represent embodiments of the present invention.

In general, the routines executed to implement the embodiments of the present invention, whether implemented as part of an operating system or a specific application, component, program, module, object or sequence of instructions may be referred to herein as a “program.” The computer program typically is comprised of a multitude of instructions that will be translated by the native computer into a machine-readable format and hence executable instructions. Also, programs are comprised of variables and data structures that either reside locally to the program or are found in memory or on storage devices. In addition, various programs described herein may be identified based upon the application for which they are implemented in a specific embodiment of the invention. However, it should be appreciated that any particular program nomenclature that follows is used merely for convenience, and thus the invention should not be limited to use solely in any specific application identified and/or implied by such nomenclature.

It is also clear that given the typically endless number of manners in which computer programs may be organized into routines, procedures, methods, modules, objects, and the like, as well as the various manners in which program functionality may be allocated among various software layers that are resident within a typical computer (e.g., operating systems, libraries, API's, applications, applets, etc.) It should be appreciated that the invention is not limited to the specific organization and allocation or program functionality described herein.

Each computer system may include, inter alia, one or more computers and at least a computer readable medium allowing a computer to read data, instructions, messages or message packets, and other computer readable information from the computer readable medium. The computer readable medium may include non-volatile memory, such as ROM, Flash memory, Disk drive memory, CD-ROM, and other permanent storage. Additionally, a computer medium may include, for example, volatile storage such as RAM, buffers, cache memory, and network circuits. Furthermore, the computer readable medium may comprise computer readable information in a transitory state medium such as a network link and/or a network interface, including a wired network or a wireless network that allow a computer to read such computer readable information.

Although specific embodiments of the invention have been disclosed, those having ordinary skill in the art will understand that changes can be made to the specific embodiments without departing from the spirit and scope of the invention. The scope of the invention is not to be restricted, therefore, to the specific embodiments, and it is intended that the appended claims cover any and all such applications, modifications, and embodiments within the scope of the present invention.

GRAPHICAL REPRESENTATION OF COMPATIBLE WORKFLOW STEPS

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

US Classifications

International Classifications

Abstract

Description

Claims

CROSS REFERENCE TO RELATED APPLICATION