[evfanknitram]

Yes, this is what my co-workers refer to as an if-statement.

[paxys]

All programming is just if statements. That doesn't mean systems can't be complex.

[adrianN]

If you're creative you can get away without conditional branches: http://www.jucs.org/jucs_2_11/conditional_branching_is_not/R...

[a1369209993]

Not true; if the conditional branch goes backward then it's a (possibly do-) while statement. Also subroutine calls.

[dudul]

This is not about how it translates into code. I see a lot of value in this diagram when compared to the half-assed "requirements" most PMs put in their JIRA tickets.

[sethammons]

That is my takeaway: PMs and non-developers - you must think through the entire workflow. When you don't, your engineers will and will either pepper you with questions that you are not prepared for or they will decide for you.

[lliamander]

I find myself creating a lot of these diagrams to share with PMs (along with sequence diagrams, system architecture diagrams, decision tables, etc.).

Systematically articulating all of these different conditions isn't necessarily the strong suit of a PM, but they're generally quite capable of understanding and providing input to such documents.

[saagarjha]

I mean, the chart is still useful to have, and it'd be a couple of methods probably had I written it. But it's not a huge state space, and most of the transitions are fairly reasonable.

[Drdrdrq]

I can imagine it was quite a lot of work to come to such a clean and relatively simple chart.