Actually, I was the one who suggested something like, person doing the
scanning which is what I thought the original poster was trying to say.
Scanner settings seems like it refers to hardware.
In Sean's use of names, wouldn't that get confusing in the case of multiple
people with different
In Sean's use of names, wouldn't that get confusing in the case of multiple
people with different roles? Uma (the network admin) and John (the user)
could be ambiguous without their titles. I can see where actors could help
solidify some concepts, but I don't think they would be the best in
So, I've been playng around with the idea of using flowcharts
instead of numbered steps in documentation.
It seems like it would make complicated procedures, with multiple
options, easier to follow. The drawback, of course, is that it's
not a tool people would be familiar with--except in
I don't think it's such a radical idea. Just look at the flip charts
on some copy machines for existing examples. The stumbler
would be if you need to insert a note or safety warning or if
your reader wants to acquire any knowledge beyond what
Pavlov's dog would need to know to get to the last
If the individual steps are complex, I feel that
scrunching them into small flowchart boxes or making
the flowchart boxes large would not help. If the steps are
numerous but the complexity of each step is small, then a
flowchart really shouldn't be used in place of the procedure,
but
