The scenario
This Petri net models a typical software development lifecycle, starting from requirements through deployment, including the iterative nature of testing and bug fixing.
What is in this drawing
Read the decisions behind it.
01
Modeling test outcomes as a conflict structure (two transitions consuming from a single code place)
02
Token cycles back from failed test to code for rework after bug fix
Suitable for illustrating any sequential process with branching and iteration, especially software workflows with quality gates.
More like this