By Sabrina Amsel on October 09 2018 02:01:16
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.
Many departments have established business rules based on guiding principles and philosophies that may have been created years before. Because there has been no initiative in documenting these procedures, chances are that there are many rules still in place that are causing unnecessary barriers and redundancies that add to the purchase order cycle time.A flowchart is a sequence of graphical symbols and shapes that can be used to help subject matter experts visually walk through their processes and validate those rules for accuracy and relevancy based on current business needs.
I recently overheard a Business Analyst say there was more to systems architecture than drawing boxes and arrows on a piece of paper. This may be true to a degree, but the ultimate deliverable of any engineering/architectural practice is a set of drawings from which to build a product. Architects and engineers do not spend all of their time drawing diagrams; for example, they have to specify requirements and analyze such things as the stress of components to determine the suitability of materials for use in design. But aside from this, the end result of engineering or architecture, their deliverable, is a set of drawings, be it a blueprint, a floor plan, wiring diagram, plumbing, or a set of flowcharts.
This is not easily done, especially in a large room with multiple experts who know only a small portion of the entire process. Each contributor who works within the team can identify their specific areas they deal with on a daily basis, but do not necessarily understand or know the linkages and dependencies that exist outside of their general areas.
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.