 |
 |
 |
 |
 |
 |
|
|
|
|
|
|
 |
|||||
John decided to make a flow chart to track the things he needed to do to learn how much it would cost to produce the pulp. John knew that just as a good table can collect and organize information, a good flow chart can organize a process, or the order in which things have to happen. And, John knew that a good flow chart would help him see how a decision point — whether or not his new customer had a flexible schedule, for instance — was related to the actions he would take — whether, for instance, he needed to produce the rayon pulp immediately (if the customer's schedule wasn't flexible) or whether he could produce the rayon pulp when the mill was not busy (if the customer's schedule was flexible). John reviewed the basics of flow charting before he got started. He knew that flow charts use three basic symbols:
John knew that a flow chart should start in the upper left corner of the page and move right and down as he moved through steps in the process. He also knew that whenever he came to a decision point — a point in the process where he needed to know the answer to a question — he could use the flow chart to show the different actions he would take if the answer was 'yes' or if the answer was 'no.' Before tackling the difficult question of figuring out the cost of manufacturing the rayon pulp, John decided to practice with a simple flow chart. John thought about the decisions he would make about traveling home from work that evening. He had ridden his bicycle to work that morning, and would ride it home again in the evening... but only if it wasn't raining. If it was raining, he would prefer to take the bus... but only if he had enough change for bus fare. If he didn't, he would have to ride home in the rain. How would that process look?
Now, it was time to create a flow chart for the rayon pulp.
Click to return to the first page of the on-screen preview. |
|
|
|
|
|
|
|