Most recent edit on 2008-12-03 19:33:33 by DougBarry
Additions:
Deletions:
Edited on 2008-12-03 17:20:05 by DougBarry
Additions:
The
Decomposition Matrix∞ on this site generates diagrams that meet this criteria. You do, however, need to provide the naming in verb-noun format yourself after the diagram is generated.
Deletions:
The
Decomposition Matrix∞ on this site generates diagrams that meet this criteria. You do, however, need to provide the naming in verb-noun format yourself after the diagram is generated.
Edited on 2008-12-03 17:19:31 by DougBarry
Additions:
Well-Formed Business Process Diagrams
The following characterize a well-formed business process diagram:
- There is a start and an end event. [1]
- Each split is matched with a join. [1]
- Each task should be atomic in that it cannot be decomposed further.
The
Decomposition Matrix∞ on this site generates diagrams that meet this criteria. You do, however, need to provide the naming in verb-noun format yourself after the diagram is generated.
Deletions:
Well Formed Business Process Diagrams
- Match each split with a join. [1]
- Have a well-defined start and end event. [1]
- Process models should provide aid in process understanding. Aim for a minimum of four, and a maximum of fifteen tasks in a process. Aim for a maximum of three or four levels in a hierarchy. [1]
Edited on 2008-12-03 17:06:19 by DougBarry
Additions:
Well Formed Business Process Diagrams
- Match each split with a join. [1]
- Have a well-defined start and end event. [1]
- Look out for orphan tasks. [1]
- A given input message/event is received by only one process/task.
- A given output message/event is produced by only one process/task.
- Processing of an input message/event is started in the process/task that receives the input.
- An output message/event is generated at the earliest point possible and not passed to a later process/task.
- Each process/task must have at least one input or one output message/event.
- All input and output messages/events are at an atomic level. No composite messages/events are used.
- Use parallel processes/tasks whenever possible.
- Process/task names should be in verb-noun format. An example is “pay invoice.” [2]
- Assemble processes based on frequency and affinity. High affinity is define as having 1:1 links. This technique clusters steps with 1:1 links and separates those clusters at the point of 1:M or M:1 links. [2]
- Process models should provide aid in process understanding. Aim for a minimum of four, and a maximum of fifteen tasks in a process. Aim for a maximum of three or four levels in a hierarchy. [1]
[1]
Business Process Driven SOA using BPMN and BPEL∞, Matjaz B. Juric and Kapil Pant
[2]
Workflow Modeling∞, Alec Sharp and Patrick
McDermott
Deletions:
Placeholder
Oldest known version of this page was edited on 2008-12-03 16:47:31 by DougBarry []
Page view:
Placeholder