Hello, I would like to ask you about the way of modeling process which cintains a lot of acceptance steps performed by each business process participant (separate business actor). Earch role (4 or 5) in the process can accept or reject (return to the previous role) the document (the process can't be changed - this is formal waterfall process in public administration :))
What is the best suitable way to present it to keep readable diagram ? Should I present all this alternatives and control flows ?
I would be greatful for your opinion.
Thank you.
Adamos,
Kmajoos,
Ok, thank you very much for your answer.
In this case, if I use this generic process description, where is the suitable place to show how this workflow should look ?
Sorry for this late response, been a bit busy. But could you please post your first attempt - make sure that you keep company information private. I'd suggest that you create a diagram thats "generic" for your document review/approval cycle and post it as Jpeg/Png on this site. Check on Google there are a lot of sample diagrams (UML, BPMN and other) that deal with review/approval cycles
warm regards,
K
This is generic model - each participant is separate business actor - there couldn't be marged. Is it sensible to repeat the same action (very similar) performed by diffierent roles ?
brought to you by enabling practitioners & organizations to achieve their goals using: