By Sabrina Amsel on December 05 2018 02:42:36
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.
Well, flowcharts can be used to analyze, design, document or manage a process in a wide variety of fields. Examples could include a Recruitment or Accounting process, the logical procedure within a piece of software, or a process in an organization such as Health & Safety, Equal Opportunities, Conciliation & Arbitration or Social Services. There are several derivatives of the basic flowchart including the Workflow Diagram,
In addition to diagramming techniques, engineers and architects have found it useful to develop models and prototypes to evaluate the overall physical aspects of their design. These are useful but let us not forget they are all ultimately based on a design of some kind (boxes and lines). From the models and prototypes, designs can be adjusted as required.
Each flowchart should ideally begin with a Terminator shape, from which the next step should be linked. Each shape should be indicative of a specific stage in the process and there are conventions for each of these, the most common being the rectangular "Process" shape. Many others exist, however, including shapes representing Data, Documents and Decisions. Decision shapes are diamonds, each of the four corners (or nodes) being either a link from the preceding shape or action to be taken in the next stage depending on the decision.
Although drawings typically consist of geometric shapes, it is not uncommon to include tables or indices to represent decisions or to provide a cross-reference. Nonetheless, boxes and lines represent the principal means to visualize and communicate a design regardless of the structure to be built, and have been used since time immemorial.
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.