By Ursula Huber on November 22 2018 08:20:50
In terms of the Information Systems industry, flowcharts have been used for years, well before the introduction of the commercial computer in business. Originally they included process diagrams; later they were used by programmers as a convenient means to document program logic. Such flowcharts typically made use of ANSI standard flowcharting symbols. But as the Structured Programming movement flourished in the late 1970`s, ANSI symbols were considered archaic, and many new types of diagramming techniques emerged, including Bubble Diagrams, Data Structure Diagrams, E/R Diagrams, HIPO, VTOC, etc. (anybody remember Nassi-Schneiderman Charts?). I could argue the pros and cons of the various techniques but that is not the point. What is important is that all of these diagramming techniques acknowledged documentation as an inherent part of the design process.
Helping an organization map out processes can be a challenging task unless you know how to create sample flowcharts. When attempting to get subject matter experts to redefine their business processes, it is imperative to help them identify gaps or redundancies in their current as-is process.
A flowchart could be defined as a pictorial representation of a process in which the steps are symbolized by shapes - in other words a diagram that explains the steps in a procedure. Each shape should link to its neighbour by a connector line, and often these have arrow heads to describe the direction of flow.
I guess what I`m driving at is that despite all of this peripheral activity, and to refute my Business Analyst friend, the principal thrust of the engineer or architect is to produce and maintain a reliable set of drawings. It all comes down to boxes and lines. Interestingly, today`s analysts and programmers think drawings are "old-hat" or passé. I don`t care whether you draw it with pencil and paper or by computer, documentation is an inherent part of the design process. Failure to recognize this is to deny reality.
Creating purchase requisitions is a standard function in every business. Unfortunately, the manual paper purchase order or requisition is one of the most frustrating areas of every business because the constant approval issues and long turnaround times that can occur.
Usually, this exercise takes place during an e-procurement project as part of the analysis phase, but can be done at any time. As long as there is a resource who has the proper skills and knows how to draw a flowchart to help the various departments identify their current procedures and potential problem areas within the purchase order approval process.
free flowchart software
interactive flowchart maker