Modeling projects should exercise rigor in the creation of workflow diagrams because those diagrams are the expressive artifacts within the project. If a picture is worth a 1000 words, then complex workflow diagrams are the equivalent of, perhaps not exactly 1000 words, but at least several hundred. The workflow diagrams, in a very small space, convey tasks, sequencing, decisions, participation, and information. The diagrams are the first thing that everyone wants to see and it is the diagrams that provide the construct for their understanding of the text. Workflow diagrams are the most powerful and expressive aspect of process models. Process models are a balance of workflow diagrams and descriptions of workflows. John Long, in Process Modeling Style, 2014 1.1 Not Focusing on the Diagrams These interfaces should be shown as well. In addition, within a process, the workflow within an activity typically interfaces with the workflow in another activity that belongs to the same process.
These interfaces should be indicated with a special symbol. Most processes interface with other processes because the output of a process is typically used by some other process. Interfaces with other activities or processes: Rarely are processes self-contained.
For instance, a comment box may provide clarity for the conditions in which a workflow is started or to describe more detail about a decision box. Ĭomment boxes: These are informative devices that can be used anywhere in a workflow diagram to provide clarity about what is happening in a workflow.
For these situations, use synchronization bars or nodes to show the beginning of parallel tasks and the end of parallel tasks. Synchronization bars or nodes: Some tasks must be carried out in parallel and may not proceed until all parallel tasks have been completed. Yes/no decisions are the most basic, but more complex decision nodes that show multiple decision results are also necessary. ĭecision nodes: Typically shown as diamond boxes, decision nodes are used to show the different paths that result from a decision.In addition, workflows may optionally contain the following: (The arrows indicate the direction of the flow.) For instance, in Change Management, when modeling the submission of a change request, you would want to show a connection between “Submit Change Request” and “Accept Change Request.” The Accept Change Request task, when being performed, may use additional information to carry out the task, like a Change Request Database or User Information, but the flow of work is clearly caused by sending the change request, not the user information from whatever repository it may reside in. These connections represent the directional flow of work between activities or tasks, not the flow of information, although information is typically passed with the flow of work. A workflow should not have just a single activity or task because such a workflow does not require decomposition and has no real value. Without a stop node, it may be difficult to determine if the workflow was simply left unfinished. One or more stop nodes that indicate how the workflow is terminated. Without a start node, it may be difficult to determine what caused the workflow to begin. One or more start nodes that indicate how the workflow is initiated. A workflow diagram should contain the following:
0 kommentar(er)
