What you're trying to chart is a switch statement. It can be done with multiple decision nodes. Here is an example...
http://www.gailer-net.de/tutorials/java/Notes/chap43/ch43_8.html And there is more info here on charting different decision statements... http://www2.tech.purdue.edu/eet/courses/referencematerial/atmel/Control_Statements/control_statements.htm Depending on the audience for this chart, you could certainly simplify to using an action box with 5 decision paths out. The multiple decision node approach might be confusing to people not familiar with diagramming logical flows. However, if you're creating specifications for engineers, a detailed flowchart showing each decision node would probably be the right way to go. I find it's best to target the communication method to fit the needs of the intended audience, rather than be to concerned with keeping true to a particular format. It's a balancing act. Personally, I don't like seeing a decision (diamond) node with anything other than a yes/no output - that comes from my EE digital logic background - to me it's a yes/no (on/off) switch. But I know I'm probably in the minority on that opinion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=44552 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
