I was trying to create a simple workflow diagram to visualize a process in our business that relies very heavily on how much time has elapsed. For example:
if an order is placed, and the order is made for a partner store, and 5 minutes has elapsed without the ops manager approving it, then highlight the order row as yellow and set the status as "needs approval", if another 3 minutes passes, highlight the order row as red, and set the status as "late"
I found the diagram I created (part of which is depicted below) as extremely verbose and lacking.
I went through the Modelling the Requirment section of the book Software Requirements and found a large set of modeling diagram types including:
Visual requirements models described in this book include:
- Data flow diagrams (DFDs)
- Process flow diagrams such as swimlane diagrams
- State-transition diagrams (STDs) and state tables
- Dialog maps
- Decision tables and decision trees
- Event-response tables
- Feature trees
- Use case diagrams
- Activity diagrams
- Entity-relationship diagrams
Wiegers, Karl; Beatty, Joy. Software Requirements (Developer Best Practices) (Kindle Locations 6268-6276). Pearson Education. Kindle Edition.
But also none of them were really suitable for what I'm looking for.. Any ideas?