The other day, I introduced to you the steps of how to evaluate Questetra BPM Suite in “How to Evaluate Questetra (Step 1)”
Then, somebody told me
“I understand the way to evaluate, alright. But I want to know how to configure more specifically now. Especially, I need to know the hang of how to draw a Process Diagram from scratch!”.
I would like to help you by showing my “idea for creating process Diagrams”, which I drew from my 8-year experience.
The creation flow is shown below:
2) Analyze the summary
3) Drop it into the Process Diagram
I will explain this with an example of a simple Reporting task between a Subordinate and his/her Superior.
Summarization and Analysis about Business Rules
Now, “1) Summarize the business rule”.
Let’s organize the target business rule into sentences.
The Superior calls for creation and submission of a report. The Subordinate creates a report and submits it to the Superior.
The Superior reviews the content of the report.
The above is the result of a spoken interview.
Summarize it in bullet points.
The following is what should be noted upon summarization.
Separate each sentence, and clarify the output. Arrange them in a time series.
So the summary will be
#1) The Superior instructs creation of a report to the Subordinate. (Output: Instruction of report creation)
#2) The Subordinate creates a report and submits it to the Superior. (Output: a report)
#3) The Superior checks the report. If there was any problem, sends it back to the Subordinate. If not, operation is finished. (Output: result of review)
Don’t you feel like somehow being able of drawing a Process Diagram by reading this summary?
The first sentence will be drawn in a Process Diagram by mapping the words into Swimlanes or Tasks.
Drawing the contents of “#1” in the Process Diagram
* “#1” is special because it is the start of the operation, so it will be connected from a “Start Event”
You might wonder what happened to the part of “to the subordinate”.
You will see it when you put the sentence corresponding to “#2” into the Diagram.
Drawing the contents of “#2” into the Process Diagram
Likewise, draw the sentence of “#2”
The part “…to the Subordinate” is expressed by the direction of the arrow which connects the Tasks “Instruct Creation” and “Create and Submit”.
And for the Subordinate, there are two operations “Creating a report” and “Submitting the report”. However, these could be done at the same time, so they can be combined as one Task.
Drawing the contents of “#3” in Process Diagram
The Diagram will be completed when drawing “#3”, like we did with “#1” and “#2”.
* “#3” is the closing of this operation, so it will be connected to an “End Event” eventually.
Even though this “Report management” operation as a very simple example, don’t you think it is easy to draw a Process Diagram from the sentences of a business rule?
Next, I would like to show you some tips for detailed settings (settings of Process Data items, Splitting, Operator) based on the Process Diagram that we have created today.
I have named the Tasks as “Instruct Creation”, “Create and Submit”, and “Check”.
You may think it is hard to find out “what” needs to be created, submitted or checked.
However, it would be easily understood from context even if it is omitted.
That is, this entire operation (Process Model) would likely be named “Report submission management” or something similar. Since in Questetra BPM Suite the operations are proceeded as a combination of the names of the operations and its Tasks, the “what” can be easily guessed from the context.
|Prev article - 55. Improvement Tips||Implement Customer Master using Options-XML (Part 2)|
|Next article - 55. Improvement Tips||Daily Report by Sales People. For Themselves? Or for Management?|
|Another article - Masato Furukubo||How to Monitor Asynchronous System Connectivity|