It is common to encounter BPMN diagrams those
days. The modeling notation is victim of
its success and broadly use in the workplace. But what about its core
definition, it’s standards, they are simply washed away by the urge to draw
quickly an interpretation of a business process. Basically a quick win.
If you want your work to end up at the correct
place: the architecture repository, then spend some extra time to review and
improve your diagrams.
Re-open the specifications,
check some basic rules.
For ex.:
·
A subprocess
MUST have a None start event; it’s a spec violation to have a triggered start
in a subprocess
·
Message flow
represents communication between the process and an external entity.
Happy modeling!