Hubbry Logo
FlowchartFlowchartMain
Open search
Flowchart
Community hub
Flowchart
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
Flowchart
Flowchart
Flowchart
View on Wikipedia
from Wikipedia

A simple flowchart representing a process for dealing with a non-functioning lamp.

A flowchart is a type of diagram that represents a workflow or process. A flowchart can also be defined as a diagrammatic representation of an algorithm, a step-by-step approach to solving a task.

The flowchart shows the steps as boxes of various kinds, and their order by connecting the boxes with arrows. This diagrammatic representation illustrates a solution model to a given problem. Flowcharts are used in analyzing, designing, documenting or managing a process or program in various fields.[1]

Overview

[edit]
Flow diagram a C-style for loop, representing the following code: 
for(i=0;i<5;i++)
  printf("*");
The loop will cause five asterisks to be printed.

Flowcharts are used to design and document simple processes or programs. Like other types of diagrams, they help visualize the process. Two of the many benefits are that flaws and bottlenecks may become apparent. Flowcharts typically use the following main symbols:

  • A process step, usually called an activity, is denoted by a rectangular box.
  • A decision is usually denoted by a diamond.

A flowchart is described as "cross-functional" when the chart is divided into different vertical or horizontal parts, to describe the control of different organizational units. A symbol appearing in a particular part is within the control of that organizational unit. A cross-functional flowchart allows the author to correctly locate the responsibility for performing an action or making a decision, and to show the responsibility of each organizational unit for different parts of a single process.

Flowcharts represent certain aspects of processes and are usually complemented by other types of diagram. For instance, Kaoru Ishikawa defined the flowchart as one of the seven basic tools of quality control, next to the histogram, Pareto chart, check sheet, control chart, cause-and-effect diagram, and the scatter diagram. Similarly, in UML, a standard concept-modeling notation used in software development, the activity diagram, which is a type of flowchart, is just one of many different diagram types.

Nassi-Shneiderman diagrams and Drakon-charts are an alternative notation for process flow.

Common alternative names include: flow chart, process flowchart, functional flowchart, process map, process chart, functional process chart, business process model, process model, process flow diagram, work flow diagram, business flow diagram. The terms "flowchart" and "flow chart" are used interchangeably.

The underlying graph structure of a flowchart is a flow graph, which abstracts away node types, their contents and other ancillary information.

History

[edit]

The first structured method for documenting process flow, the "flow process chart", was introduced by Frank and Lillian Gilbreth in the presentation "Process Charts: First Steps in Finding the One Best Way to do Work", to members of the American Society of Mechanical Engineers (ASME) in 1921.[2] The Gilbreths' tools quickly found their way into industrial engineering curricula. In the early 1930s, an industrial engineer, Allan H. Mogensen began to train business people in the use of some of the tools of industrial engineering at his Work Simplification Conferences in Lake Placid, New York.

Art Spinanger, a 1944 graduate of Mogensen's class, took the tools back to Procter and Gamble where he developed their Deliberate Methods Change Program. Ben S. Graham, another 1944 graduate, Director of Formcraft Engineering at Standard Register Industrial, applied the flow process chart to information processing with his development of the multi-flow process chart, to present multiple documents and their relationships.[3] In 1947, ASME adopted a symbol set derived from Gilbreth's original work as the "ASME Standard: Operation and Flow Process Charts."[4]

Douglas Hartree in 1949 explained that Herman Goldstine and John von Neumann had developed a flowchart (originally, diagram) to plan computer programs.[5] His contemporary account was endorsed by IBM engineers[6] and by Goldstine's personal recollections.[7] The original programming flowcharts of Goldstine and von Neumann can be found in their unpublished report, "Planning and coding of problems for an electronic computing instrument, Part II, Volume 1" (1947), which is reproduced in von Neumann's collected works.[8]

The flowchart became a popular tool for describing computer algorithms, but its popularity decreased in the 1970s, when interactive computer terminals and third-generation programming languages became common tools for computer programming, since algorithms can be expressed more concisely as source code in such languages. Often pseudo-code is used, which uses the common idioms of such languages without strictly adhering to the details of a particular one. Also, flowcharts are not well-suited for new programming techniques such as recursive programming.

Nevertheless, flowcharts were still used in the early 21st century for describing computer algorithms.[9] Some techniques such as UML activity diagrams and Drakon-charts can be considered to be extensions of the flowchart.

Types

[edit]
IBM flowcharting template

Sterneckert (2003) suggested that flowcharts can be modeled from the perspective of different user groups (such as managers, system analysts and clerks), and that there are four general types:[10]

  • Document flowcharts, showing controls over a document-flow through a system
  • Data flowcharts, showing controls over a data-flow in a system
  • System flowcharts, showing controls at a physical or resource level
  • Program flowchart, showing the controls in a program within a system

Notice that every type of flowchart focuses on some kind of control, rather than on the particular flow itself.[10]

However, there are some different classifications. For example, Andrew Veronis (1978) named three basic types of flowcharts: the system flowchart, the general flowchart, and the detailed flowchart.[11] That same year Marilyn Bohl (1978) stated "in practice, two kinds of flowcharts are used in solution planning: system flowcharts and program flowcharts...".[12] More recently, Mark A. Fryman (2001) identified more differences: "Decision flowcharts, logic flowcharts, systems flowcharts, product flowcharts, and process flowcharts are just a few of the different types of flowcharts that are used in business and government".[13]

In addition, many diagram techniques are similar to flowcharts but carry a different name, such as UML activity diagrams.

Reversible flowcharts[14] represent a paradigm in computing that focuses on the reversibility of computational processes. Unlike traditional computing models, where operations are often irreversible, reversible flowcharts ensure that any atomic computational step can be reversed. Reversible flowcharts are shown to be as expressive as reversible Turing machines, and are a theoretical foundation for structured reversible programming and energy-efficient reversible computing systems.[15]

Building blocks

[edit]

Common symbols

[edit]

The American National Standards Institute (ANSI) set standards for flowcharts and their symbols in the 1960s.[16] The International Organization for Standardization (ISO) adopted the ANSI symbols in 1970.[17] The current standard, ISO 5807, was published in 1985 and last reviewed in 2019.[18] Generally, flowcharts flow from top to bottom and left to right.[19]

ANSI/ISO Shape Name Description
Flowline (arrowhead)[17] Shows the process's order of operation. A line coming from one symbol and pointing at another.[16] Arrowheads are added if the flow is not the standard top-to-bottom, left-to right.[17]
Terminal[16] Indicates the beginning and ending of a program or sub-process. Represented as a stadium,[16] oval or rounded (fillet) rectangle. They usually contain the word "Start" or "End", or another phrase signaling the start or end of a process, such as "submit inquiry" or "receive product".
Process[17] Represents a set of operations that changes value, form, or location of data. Represented as a rectangle.[17]
Decision[17] Shows a conditional operation that determines which one of the two paths the program will take.[16] The operation is commonly a yes/no question or true/false test. Represented as a diamond (rhombus).[17]
Input/output[17] Indicates the process of inputting and outputting data,[17] as in entering data or displaying results. Represented as a rhomboid.[16]
Annotation[16] (comment)[17] Indicating additional information about a step in the program. Represented as an open rectangle with a dashed or solid line connecting it to the corresponding symbol in the flowchart.[17]
Predefined process[16] Shows named process which is defined elsewhere. Represented as a rectangle with double-struck vertical edges.[16]
On-page connector[16] Pairs of labeled connectors replace long or confusing lines on a flowchart page. Represented by a small circle with a letter inside.[16][20]
Off-page connector[16] A labeled connector for use when the target is on another page. Represented as a home plate-shaped pentagon.[16][20]

Other symbols

[edit]

The ANSI/ISO standards include symbols beyond the basic shapes. Some are:[19][20]

Shape Name Description
Flowchart database Data File or Database Data represented by a cylinder symbolizing a disk drive.
Flowchart Document Document Single documents represented as a rectangle with a wavy base.
Flowchart Document multiple Multiple documents represented as a stack of rectangles with wavy bases.
Flowchar Manual input Manual operation Represented by a trapezoid with the longest parallel side at the top, to represent an operation or adjustment to process that can only be made manually.
Flowchart manual input Manual input Represented by quadrilateral, with the top irregularly sloping up from left to right, like the side view of a keyboard.
Flowchart Preparation Preparation or Initialization Represented by an elongated hexagon, originally used for steps like setting a switch or initializing a routine.

Parallel processing

[edit]
  • Parallel Mode is represented by two horizontal lines at the beginning or ending of simultaneous operations[19]

For parallel and concurrent processing the Parallel Mode horizontal lines[21] or a horizontal bar[22] indicate the start or end of a section of processes that can be done independently:

  • At a fork, the process creates one or more additional processes, indicated by a bar with one incoming path and two or more outgoing paths.
  • At a join, two or more processes continue as a single process, indicated by a bar with several incoming paths and one outgoing path. All processes must complete before the single process continues.[22]

Diagramming software

[edit]
A screenshot of the flowchart software Flowgorithm

Any drawing program can be used to create flowchart diagrams, but these will have no underlying data model to share data with databases or other programs such as project management systems or spreadsheet. Many software packages exist that can create flowcharts automatically, either directly from a programming language source code, or from a flowchart description language.

There are several applications and visual programming languages[23] that use flowcharts to represent and execute programs. Generally these are used as teaching tools for beginner students.

See also

[edit]

References

[edit]

Further reading

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Flowchart

View on Grokipedia
from Grokipedia
A flowchart is a graphical representation of the definition, analysis, or method of solution of a problem in which symbols are used to represent operations, , flow, equipment, and other elements, with lines connecting the symbols to illustrate the sequence and relationships. These diagrams visually depict stages of a process, , computer , or system, employing shapes such as ovals for terminals, rectangles for processes, and diamonds for decisions, connected by arrows to show directional flow and decision points. Flowcharts are widely utilized across fields like , , and to document, analyze, plan, and optimize procedures, reducing ambiguity and facilitating communication among stakeholders. The origins of flowcharts trace back to the early 20th century in , where Frank and Lillian Gilbreth introduced the concept of the in 1921 to the (ASME) as a tool for optimizing workflows and eliminating inefficiencies in . This foundational work evolved through further refinements by engineers, leading to ASME's standardization of flowchart symbols in 1947. By the late 1940s, flowcharts gained prominence in computing when and adapted them in 1947 to represent algorithms for early electronic computers, positioning them as essential blueprints for programming and problem-solving in the emerging field of . In the mid-20th century, flowcharts became integral to , serving multiple roles: as design aids for translating complex logic into structured code, communication tools bridging analysts and programmers, and documentation methods for post-implementation review. Standardization efforts advanced with the American Standards Association's 1963 conventions and the (ANSI)'s conventions published in 1965, with formal standard X3.5 approved in 1970, which were later adopted internationally by the (ISO), adopting similar conventions in 1973 and publishing ISO 5807 in 1985. These standards defined core symbols for data (e.g., parallelograms for ), processes (e.g., rectangles for operations), and flow (e.g., arrows for direction), ensuring interoperability in information processing documentation across industries. While flowcharts peaked in popularity during the and for algorithmic representation, their use declined in the late 1970s with the rise of paradigms and interactive terminals, which favored textual over visual diagrams. Modern evolutions include integrations with tools like (UML) activity diagrams from the 1990s and Business Process Model and Notation (BPMN) codified in 2005 by the Business Process Management Initiative, extending flowchart principles to more sophisticated digital process modeling. Today, flowcharts remain a foundational tool in , as endorsed by organizations like the , for mapping processes sequentially to identify bottlenecks and improve efficiency.

Fundamentals

Definition

A flowchart is a that visually represents a , , or by depicting a sequence of operations through interconnected standardized shapes, with arrows indicating the direction of flow. This structured visualization allows for the clear illustration of how individual steps relate to one another in achieving a specific outcome. The primary purposes of flowcharts include visualizing algorithms, workflows, decision-making processes, and system operations to simplify the comprehension of complex procedures and enhance communication among stakeholders. By breaking down intricate sequences into digestible components, they facilitate problem-solving, process improvement, and the identification of inefficiencies or bottlenecks. Key characteristics of flowcharts encompass sequential or branched paths that emphasize logical progression over aesthetic elements, enabling their broad applicability in disciplines such as , , and . Flowcharts differ from related visuals in their focus on step-by-step process flows; in contrast, mind maps organize information hierarchically around a central theme in a radial, non-linear manner, while entity-relationship diagrams model static structures and their interconnections rather than dynamic operations.

Basic Elements

Flowcharts consist of fundamental structural components that ensure clarity and logical progression in representing processes. Central to these are arrows, or flow lines, which serve as connectors indicating the sequence and direction of operations or movement between elements. Straight arrows typically denote sequential flow, while branching arrows from decision points represent alternative paths based on conditions, adhering to conventions that maintain unambiguous progression. Entry and exit points bookend the diagram using terminal symbols, such as ovals, to mark the initiation and conclusion of the process, providing clear boundaries for the . These terminators ensure that every has defined starting and ending points, facilitating comprehension of the overall scope. Connectors, often circular symbols with identifiers like letters or numbers, link discontinuous sections of the , such as across pages, without altering the primary flow. Standard flow direction conventions mimic natural reading patterns, progressing from top to bottom or left to right, with arrowheads clarifying the path and open arrowheads indicating reverse flow when necessary. This orientation enhances readability by aligning with conventional text layout, though bidirectional flows may use double lines with appropriate arrowheads. Basic layout principles emphasize a logical sequence that avoids unintentional loops, ensuring each step leads coherently to the next while minimizing crossovers and maintaining consistent spacing between elements. To prevent clutter, diagrams incorporate adequate white space, hierarchical organization for complex flows, and synchronization lines for parallel processes, all of which promote readability without compromising the diagram's integrity. While shapes like rectangles denote processes, the focus remains on these connective and directional structures to support effective visualization.

History

Origins

The origins of flowcharts trace back to the early within the framework of , where efforts to optimize industrial workflows laid the groundwork for graphical representations of processes. Frederick Winslow Taylor's principles of , outlined in his work, emphasized systematic analysis of work tasks to enhance efficiency, influencing subsequent developments in process documentation during the 1910s. These ideas evolved into more visual tools as industrial engineers sought ways to break down and improve operations beyond mere time studies. A pivotal advancement came in 1921 when industrial engineers and introduced process charts as a method for motion study in manufacturing. In their presentation to the titled "Process Charts: First Steps of Finding the One Best Way to Do Work," the Gilbreths proposed using standardized symbols to depict worker tasks, operations, inspections, transports, and delays, enabling a clear visualization of workflows to identify inefficiencies. This innovation built directly on Taylor's by shifting focus to motion economy, allowing engineers to map and refine physical movements in industrial settings. Central to the Gilbreths' approach was their "Therbligs" system, developed around 1915 and integrated into the 1921 process charts, which divided human motions into 18 fundamental elements such as search, grasp, and transport empty. These elemental breakdowns served as precursors to modern flowchart symbols, providing a granular, symbolic language for analyzing and optimizing repetitive tasks in engineering and assembly line work. By representing processes graphically, Therbligs facilitated the elimination of unnecessary motions, marking an early step toward structured workflow diagramming. Flowcharts gained further traction in quality control during the mid-20th century, notably through Kaoru Ishikawa's integration of process flow diagrams into his in the . Ishikawa, a Japanese professor, promoted these tools—including flowcharts—for problem-solving in , adapting earlier industrial charting techniques to emphasize defect prevention and process . This adoption solidified flowcharts as essential for visualizing and improving operational sequences in contexts.

Evolution

In the mid-20th century, flowcharts were adapted for use in electronic computing, notably by mathematicians and in 1947. While working on programming the computer and planning algorithms for the successor at the Institute for Advanced Study, they introduced flow diagrams as a graphical notation to represent computational processes, enabling systematic planning and coding of problems for electronic instruments. This approach formalized the breakdown of mathematical problems into sequential steps, using symbols for operations, decisions, and data flows, which facilitated communication between mathematicians and machine operators. Standardization efforts followed to ensure consistency in programming . In 1963, the (ANSI) proposed a set of flowchart symbols for information processing, which was formalized as ANSI X3.5 in 1970, defining shapes for processes, decisions, inputs/outputs, and connectors to support structured representation of algorithms. Internationally, the (ISO) published ISO 1028 in 1973, establishing graphical symbols for flowcharts in information processing systems, aligning closely with ANSI standards to promote in . These standards emphasized clarity and universality, becoming essential for documenting control flows in early programming practices. By the and , the use of flowcharts in declined significantly, driven by the advent of high-level programming languages that incorporated structured constructs like loops and conditionals, reducing the reliance on manual diagramming for design. The shift toward , critiqued earlier by Edsger Dijkstra in 1968 for issues like unrestricted statements, further diminished flowcharts' role, as languages such as Pascal and encouraged linear, hierarchical code over detailed graphical planning. This evolution prioritized code readability and maintainability, rendering traditional flowcharts less practical for complex systems. Flowcharts experienced a resurgence in the 2000s, integrated into agile and visual methodologies that emphasized iterative and collaboration in . Digital tools enabled rapid creation and sharing of diagrams for analysis, while evolutions like UML activity diagrams and BPMN built on flowchart principles for visualization. In the , ISO revisions in standards, such as updates to ISO/IEC 12207 (2008 and 2017) for system and software life cycle processes, incorporated diagrammatic representations to support and process documentation, adapting flowcharts to modern engineering needs.

Symbols and Standards

Standard Symbols

Standard symbols in flowcharts are defined by the ISO 5807:1985, which specifies shapes and conventions for documentation in information processing, including , program, and system flowcharts. These symbols provide a consistent notation for representing , decisions, flows, and other elements, ensuring clarity and across diagrams. The standard emphasizes simplicity, with symbols designed for manual or automated creation, and includes rules for their application to avoid ambiguity. Flowcharts typically begin and end with or symbols to define scope, without a dedicated terminal shape. The process symbol, a standard rectangle, represents any computational or operational step that transforms data, such as calculations or assignments, and contains a brief description of the action performed. Decision points are indicated by a shape, which has one and multiple exit paths branching based on conditional logic, such as yes/no outcomes; conditions are written adjacent to the exits, but no other text appears inside the diamond itself. Input and output operations use a circle to signify unspecified exchange with external sources or destinations, like reading from a file or displaying results, with the direction of flow clarified by connecting lines. Specialized symbols (e.g., for storage types) use variations on the circle shape. Connectors, often small circles or dots, facilitate continuity by linking distant parts of a , such as off-page references or modular sections, and are labeled with matching identifiers (e.g., A to A) to avoid cluttered lines. Loop limits use two-part circles with identifiers. The full set of symbols in ISO 5807:1985 encompasses , , and line elements, as summarized below. Usage rules include ensuring symbols connect via symbols in flow diagrams, directing flow with arrowheads only when necessary for clarity, and pairing loop limits with identical identifiers for matching begin/end points. Note that ISO 5807:1985 remains the current standard, last reviewed in 2019, though many modern tools favor earlier ANSI conventions with ovals for terminals and parallelograms for .
CategorySymbol ShapeNameMeaning and Usage
ProcessAny transformation or operation; describe action inside.
Process with double vertical linesPredefined Subroutine or module call; reference name externally.
Process (wider at bottom)Manual OperationHuman-performed task; specify manual aspect.
ProcessPreparationInitialization or setup, like parameter adjustment.
ProcessDecisionConditional ; one entry, multiple labeled exits.
ProcessHorizontal bar with vertical linesParallel ModeSynchronization point for concurrent flows.
ProcessTwo-part with identifierLoop LimitMarks loop start/end; match identifiers.
DataBasic DataUnspecified input/output; indicate flow direction.
Data with horizontal lineStored DataPersistent storage, medium unspecified.
Data with two horizontal linesInternal StorageData in memory or registers.
Data with one curved sideSequential Access StorageLinear access , e.g., tape.
Data with two curved sidesDirect Access StorageRandom access , e.g., disk.
Data with folded cornerHuman-readable output, e.g., printout.
Data (wider at top)Manual InputUser-entered , e.g., via forms.
Data with notched edgeCardPunched or card input.
Data with holesTape-based .
Data with curved topDisplayVisual output, e.g., screen.
LineStraight line (optional )Flow LineConnects symbols; s show direction if needed.
LineDotted line with Control TransferUnconditional jump, e.g., .
LineJagged lineCommunication LinkOff-system transfer.
LineDashed lineAnnotation or AlternativeEncloses notes or indicates optional paths.
ConnectorSmall or dotConnectorLinks diagram sections; label for matching.

Specialized Symbols

In addition to the standard symbols defined by ANSI and ISO, flowcharts incorporate specialized symbols to represent domain-specific operations, particularly in data processing, manual interventions, and complex diagramming needs. These extensions build on foundational notation to address nuances in information handling and flow continuity. For instance, the document symbol, depicted as a rectangle with a top-right corner cut off, represents input/output functions involving printed documents or reports, such as generating a form or record. Similarly, the manual operation symbol, shown as a trapezoid (wider at top), denotes offline processes performed by hand without automated assistance, like sorting papers or entering data manually. Delays are represented using the terminal symbol (oval in ANSI conventions). For data persistence, the database storage symbol—typically a cylinder—illustrates online storage media like disks or tapes where data is archived or retrieved in data flowcharts. Specialized symbols also facilitate data organization in and contexts. The collate symbol, rendered as a , signifies the merging, matching, or extracting of multiple inputs into ordered sets, commonly used in administrative workflows to combine reports. The sort symbol, depicted as a with extended sides, represents arranging items into a specific sequence, such as alphabetizing files or prioritizing tasks. These symbols enhance clarity in flowcharts depicting repetitive or integrative operations. To manage complexity in large diagrams, off-page connectors serve as navigational aids. These are circular shapes labeled with letters or numbers, linking elements across multiple pages; for example, an "A" on one page connects to a matching "A" on another, ensuring seamless continuity without cluttering a single view. Domain-specific extensions further adapt flowchart notation for specialized applications. In , the visual language introduces rules to improve readability and reduce errors in algorithmic representations, such as using curved arrows in loops to avoid right angles and prohibiting line intersections, with branches ordered left-to-right by temporal sequence along a central "skewer" line. These conventions, developed for Soviet space programs like Buran, ensure diagrams mimic natural reading patterns while expressing any algorithm without ambiguity. For , BPMN gateways extend traditional decision diamonds with typed variants: exclusive gateways (marked "X") route to one path based on conditions; parallel gateways ("+") split or join multiple flows simultaneously; inclusive gateways ("O") allow subsets of paths; event-based gateways (circled) defer to the first triggered event; and complex gateways ("*") handle custom rules like n-of-m synchronization. These elements, standardized by the , enable precise modeling of conditional, concurrent, and event-driven business logic beyond basic flowchart capabilities.

Types of Flowcharts

Process Flowcharts

Process flowcharts are diagrams that map the activities involved in a sequential or operational , visually representing the step-by-step progression of tasks to achieve a specific outcome. These diagrams emphasize the flow of activities within a , often arranged horizontally to accommodate cross-functional teams through the use of swimlanes, which delineate responsibilities across departments or roles. This structure facilitates a clear depiction of how inputs transform into outputs in operational contexts, such as production lines or protocols. Key features of process flowcharts include linear sequences of activities connected by arrows to indicate direction and flow, interspersed with decision branches—typically represented by diamond shapes—to account for conditional paths or exceptions in the . These elements enable detailed analysis of process efficiency, making process flowcharts particularly valuable in for assembly line optimization and in for streamlining customer interactions. Unlike more abstract diagrams, they prioritize the tangible sequence of human and procedural actions, helping teams visualize handoffs and dependencies without delving into data structures or logic. A representative example is the process in , where the flowchart begins with receiving a order, followed by verification, item picking and packing, quality checks, and final shipping to delivery. Decision points might include branches for out-of-stock scenarios, looping back to or notifying the of delays, while error-handling loops address issues like damaged goods returned for rework. This visualization highlights the end-to-end journey from order to , using standard symbols like rectangles for action steps to maintain clarity. The primary advantages of process flowcharts lie in their capacity to reveal bottlenecks, such as delays at handoff points between teams, thereby supporting targeted interventions to reduce cycle times and enhance overall . By mapping the current state of a , they promote and continuous improvement in operational environments. However, a notable limitation is their tendency to oversimplify factors, such as interpersonal communications or adaptive , which can lead to incomplete representations that ignore informal processes or cultural influences within teams.

Data and System Flowcharts

Data flow diagrams (DFDs), a specialized type of flowchart, depict the movement and transformation of data across processes, external entities, and data stores within a , highlighting how is input, manipulated, and output. These diagrams use notations such as the Yourdon-DeMarco approach, originally developed for in the late 1970s, where circles represent data-processing functions that receive inputs, perform transformations, and produce outputs, while open-ended rectangles denote data stores and arrows illustrate data flows between components. DFDs focus on logical data dependencies in information systems rather than physical or strict procedural sequences. In , external entities—such as users or other systems—are typically shown as squares or rectangles to indicate sources or destinations of , ensuring the diagram captures the complete lifecycle of from entry to final utilization. For instance, parallelograms may be employed to represent operations in data-centric contexts, bridging user interactions with internal processing. Unlike general flowcharts that emphasize with decisions and sequences, prioritize parallel data paths and transformations without built-in decision elements. System flowcharts, in contrast, offer a high-level view of hardware and software interactions, mapping out system architecture including components like central processing units (CPUs), storage devices, and interfaces to illustrate control and data pathways. Standardized symbols from early computing guidelines, such as those in ANSI X3.5-1970, include rectangles for online storage under CPU control, cylinders for magnetic disks representing persistent , and flowlines to connect these elements, demonstrating how operations sequence across the system. These diagrams are particularly valuable for documenting complex environments where software routines interface with hardware, using predefined process symbols for subroutines and communication links for data transmission between modules. A representative example is a database query system flowchart, where user-submitted queries (via manual input symbol) flow to a CPU for processing, triggering retrieval from a magnetic disk data store, followed by software transformation of the raw data into formatted reports output through a display interface; this visualization reveals bottlenecks in data retrieval or hardware dependencies.
Symbol TypeDescriptionExample Usage in System Flowcharts
Online StorageRectangle representing storage accessible by CPUBuffering query results before processing
Magnetic Disk for persistent data I/OStoring and retrieving database records
Predefined ProcessDouble-sided rectangle for software routinesExecuting query logic or transformation
Manual Input for user-entered Accepting database search parameters
Flowline indicating direction and sequenceConnecting hardware retrieval to software output

Program Flowcharts

Program flowcharts provide a visual representation of the sequential steps in a program's execution, emphasizing the logical flow of control through algorithms in . These diagrams depict , iterative loops, conditional branches, and subroutine calls using standardized symbols such as ovals for start/end points, rectangles for processes, and diamonds for decisions. Originating from early computational planning efforts, program flowcharts evolved to model imperative program structures, enabling developers to outline logic before implementation. In visualizing , program flowcharts map control structures like statements with diamond-shaped decision nodes that branch based on conditions, leading to parallel paths that converge after execution. Loops are represented by arrows returning to decision points until exit criteria are met, while subroutines appear as modular off-page connectors or predefined blocks to promote code reusability. A structured variant, the Nassi-Shneiderman diagram, restricts representations to hierarchical boxes without arrows, enforcing disciplined programming by avoiding unstructured jumps like statements; developed in 1972, it uses nested regions for sequences, selections, and iterations to mirror block-based languages. For instance, a program flowchart for the bubble sort algorithm begins with an initialization of the and outer loop counter, followed by nested inner loops: a checks if elements are out of order, triggering a swap in a rectangular if true, with the loop repeating until no swaps occur, ensuring the is sorted in ascending order. This depiction highlights comparison-based decisions and iterative swaps, aiding in and optimization of the O(n²) . In , particularly for quantum and low-power applications, program flowcharts incorporate backward-compatible paths to ensure computations can be undone without information loss, modeling bijective functions where each step is invertible. These reversible flowcharts extend traditional structures by pairing forward operations with their inverses, such as using guarded swaps in quantum circuits, to maintain in both directions and support applications like quantum .

Creation and Tools

Manual Creation

Manual creation of flowcharts refers to the traditional hand-drawn methods used to visualize processes, predating digital tools and emphasizing tactile, iterative design on physical media. These early charts were sketched freehand to identify inefficiencies, marking a foundational shift toward graphical process representation in engineering. The process typically begins with brainstorming the workflow, where creators outline key steps, decisions, and sequences in a narrative or bullet-point form to capture the essence of the process without initial visual constraints. This is followed by sketching rough outlines on plain or graph paper, using basic shapes like circles for decisions and rectangles for actions to map the high-level flow and identify logical branches. Refining the draft involves tracing precise standard symbols onto the paper for uniformity and clarity, often iterating through multiple versions to resolve ambiguities. Essential tools for manual creation include for maintaining alignment and scale, mechanical pencils or fine-tip pens for precise lines and erasures, and specialized flowchart templates—thin sheets of clear plastic with cutout shapes corresponding to standard symbols, introduced around 1955 by companies like and later standardized by ANSI. These templates, often accompanied by explanatory envelopes, allowed users to trace symbols accurately onto drafting paper, with historical setups employing drafting tables for stability during extended drawing sessions on larger sheets. Best practices emphasize starting with simple, linear sketches to prioritize logical flow before adding complexity, iterating drafts to enhance readability by minimizing crossings and ensuring consistent symbol sizing, and validating the diagram through walkthroughs—manually tracing paths to simulate the process and detect errors like infinite loops. For symbol rendering, adherence to standards such as ANSI X3.5-1970 ensures compatibility, with ovals denoting terminals and parallelograms for data inputs. Manual creation offers advantages like low cost, relying solely on inexpensive supplies such as paper and pencils without needing specialized equipment, and fostering tactile understanding that deepens comprehension of process interdependencies through physical manipulation. However, it is time-intensive, particularly for revisions, as alterations often require redrawing entire sections, limiting scalability for complex or frequently updated diagrams.

Diagramming Software

Diagramming software facilitates the creation of flowcharts by providing digital tools for drawing, connecting shapes, and automating layouts, often incorporating libraries of standard symbols such as ovals for start/end points and rectangles for processes. These tools range from traditional desktop applications to cloud-based platforms, enabling users to visualize processes efficiently without manual drafting. Traditional desktop tools like have been staples for vector-based flowchart creation since their introduction, offering templates for basic flowcharts, process diagrams, and integration with for data-linked visuals. Open-source alternatives include Dia, a free program for structured diagrams including flowcharts, supporting exports to formats like EPS, , and , and customizable shapes for various types. Free alternatives include yEd Graph Editor, which provides automatic layout algorithms tailored for flowcharts, such as hierarchical arrangements with user-defined branch directions, making it suitable for complex graphs without requiring manual positioning. Modern cloud-based options emphasize collaboration and accessibility. , founded in 2010, supports real-time collaborative editing where multiple users can simultaneously modify flowcharts, with features like commenting, sharing, and integration with tools such as . Miro, established in 2011 as RealtimeBoard, enables real-time team flowcharting on infinite canvases, incorporating drag-and-drop shapes and templates for process mapping in distributed environments. Draw.io (now ), when integrated with , allows embedding editable flowcharts directly into pages, supporting real-time collaboration and version history within team wikis. offers a free online platform for creating flowcharts with an easy-to-use interface, a variety of templates, and real-time collaboration features suitable for visualizing processes. Visual Paradigm Online provides a drag-and-drop editor for professional flowcharts, including built-in templates, formatting options, collaboration via cloud repository, and export to formats like PNG, SVG, and PDF. For educational purposes, tools like focus on turning visual flowcharts into executable code, allowing users to design algorithms graphically and export them to over 18 programming languages including C++, , and Python, which aids in teaching programming logic without syntax barriers. Emerging features in diagramming software include AI-assisted auto-generation and integrations. Starting in 2023 and enhanced through 2024, has introduced AI capabilities such as prompt-based diagram generation, where users input text descriptions to automatically create and iterate on flowcharts, alongside summarization of collaborative sessions and features like diagram as code. Additionally, tools like draw.io support integration with for , enabling diagrams stored as XML files to be tracked, branched, and merged alongside code repositories.

Applications

Business and Engineering

In business contexts, flowcharts serve as essential tools within frameworks for process mapping, enabling organizations to visualize workflows and pinpoint inefficiencies such as excess inventory or redundant steps. , a specific application of flowcharts, documents material and information flows across an entire process to identify and eliminate waste, thereby streamlining operations and enhancing value delivery to customers. This approach, rooted in lean principles, supports continuous improvement by highlighting non-value-adding activities and facilitating targeted interventions to boost productivity. A seminal case study is the (TPS), pioneered in the 1950s by and others, which integrated flowcharts into just-in-time manufacturing to synchronize production with demand and minimize waste. By using process flowcharts to map sequences and supplier interactions, TPS achieved dramatic reductions in levels and lead times, setting a benchmark for global manufacturing efficiency that influenced lean practices worldwide. For instance, maps in TPS helped visualize bottlenecks, allowing for real-time adjustments that reduced production cycle times in early implementations. In disciplines, flowcharts are employed during requirements gathering to delineate functionalities and dependencies, ensuring comprehensive coverage of operational needs from inception. They provide a sequential representation of processes, aiding multidisciplinary teams in aligning technical specifications with project goals. Additionally, in safety protocol development, utilizes flowchart-like diagrams to deduce potential failure paths from top-level hazards, quantifying risks through logical branching to inform robust engineering safeguards. The adoption of flowcharts in these fields yields key benefits, including the standardization of procedures that simplifies training and compliance auditing, as well as measurable reductions in cycle times by eliminating unnecessary steps. These tools promote a shared understanding among stakeholders, fostering and enabling scalable improvements without overhauling entire systems.

Computing and Education

In computing, flowcharts serve as a visual intermediary for translating into actual program code and facilitating by mapping control flows and explicitly. This approach enhances and readability, allowing programmers to trace execution paths and identify logical errors before implementation. In the context of paradigms, flowcharts proved instrumental in promoting disciplined control structures—such as sequence, selection, and iteration—over unstructured jumps like the statement, a practice critiqued by in his seminal 1968 letter, which argued that such primitives led to unmanageable code complexity and advocated for hierarchical, structured designs. In education, flowcharts are widely employed to teach programming logic and algorithmic thinking to beginners, providing a graphical representation that demystifies abstract concepts without the syntax barriers of real code. Tools like , a free graphical programming environment, enable students to construct and execute flowcharts that automatically generate code in multiple languages, making it particularly effective for introductory curricula at the K-12 level by emphasizing visual problem-solving over textual coding. This method aligns with pedagogical principles that prioritize flowchart-based instruction to build foundational skills in algorithm design, as outlined in on novice programmers. A representative example in introductory algorithms courses involves using flowcharts to visualize the binary search algorithm, where a sorted is repeatedly halved based on comparisons to a target value at the midpoint, with decision diamonds representing conditions like "target found" or "search left/right half" to illustrate iterative refinement efficiently. Such visualizations help learners grasp the logarithmic and conditional branching inherent in search problems, reinforcing step-by-step execution without overwhelming details. In modern contexts, flowcharts play a key role in fostering among non-programmers by encouraging , , and —core elements of Jeannette Wing's 2006 framework, which positions these skills as essential for problem-solving across disciplines beyond traditional coding. This application extends flowcharts' utility in educational settings to promote broader literacy in algorithmic reasoning, applicable in fields like and .

Advanced Topics

Parallel Processing

In flowcharts, parallel processing is represented through specific notations that depict concurrent execution paths diverging from a common point and later converging. Branching for concurrency typically involves drawing multiple arrows emanating from a single process symbol or, briefly, a standard decision to initiate simultaneous flows, allowing visualization of tasks that can proceed independently. This approach enables the depiction of multitasking scenarios where operations do not depend on strict sequencing. Synchronization symbols are essential for showing where parallel paths merge, ensuring all concurrent activities complete before proceeding. These are often illustrated as double transverse lines or bars perpendicular to the flow direction, known as parallel mode symbols in standard conventions. The parallel mode symbol specifically marks the start or end of two or more simultaneous operations, facilitating the representation of points in multitasking environments. For instance, ANSI extensions, as outlined in early information processing standards, incorporate these for handling concurrent flows. A representative example is a flowchart for a multi-threaded program, such as a CPU scheduler managing multiple tasks. The begins with a symbol for thread initialization, followed by parallel mode bars to fork into separate paths—one for each thread handling distinct computations like input and . Each path includes sequential steps within the thread, culminating in another set of parallel bars as a join point where results synchronize before a final output . This structure highlights how resources like are accessed concurrently, common in systems requiring efficient parallelism. Representing parallel processing in flowcharts presents challenges, particularly in visually handling race conditions, where unpredictable interleaving of concurrent threads can lead to inconsistent outcomes due to unsynchronized access to shared resources. Flowcharts' linear, deterministic nature makes it difficult to convey such timing-dependent nondeterminism without additional annotations or supplementary diagrams. These notations find applications in real-time systems, such as for concurrent task scheduling, where precise ensures timely responses in environments like automotive controls or .

Modern Integrations

In the realm of object-oriented design, flowcharts have evolved into (UML) activity diagrams, which extend traditional flowchart notation to better support complex, concurrent behaviors in software systems. Adopted as a standard by the (OMG) in 1997, UML activity diagrams build on flowchart principles by incorporating elements like swimlanes for partitioning activities across objects, fork and join nodes for parallelism, and object flows to track data movement, making them particularly suited for modeling dynamic system interactions. Within agile methodologies, diagrams similar to flowcharts are used to visualize workflows and support iterative development. For instance, process flow diagrams can illustrate the Scrum sprint cycle, including stages like sprint planning, daily stand-ups, execution, review, and retrospectives, helping teams identify dependencies and bottlenecks. User story mapping employs visual structures, often diagram-like, to organize epics, , and tasks along a timeline, facilitating and alignment with user needs. In AI and , flowcharts are instrumental for delineating pipelines, where they outline sequential stages from data ingestion to model deployment. pipelines are commonly visualized using diagrams to illustrate components like , transformation, and evaluation, ensuring reproducible workflows in production environments. Similarly, decision trees in predictive modeling are visualized using flowchart structures to map branching logic for or regression tasks, with tools like Decision Forests providing built-in visualization capabilities as of the . Cloud-based and collaborative tools have integrated flowcharts into practices, allowing real-time updates and embedding within platforms like Jira for seamless team coordination. In Jira, add-ons such as draw. enable the creation and embedding of flowcharts directly into issues and boards, supporting pipelines by visualizing stages with live editing and . Recent developments as of November 2025 include AI-assisted diagramming features in these tools, where generative AI generates diagrams and smart templates, enhancing efficiency in dynamic, distributed environments.

References

  1. https://cdn.standards.iteh.ai/samples/11955/1b7dd254a2a54fd7a89d616dc0570e18/ISO-5807-1985.pdf
  2. https://www.ibm.com/think/topics/flowchart
  3. https://asq.org/quality-resources/flowchart
  4. https://homes.luddy.indiana.edu/nensmeng/files/Ensmenger2016.pdf
  5. https://nvlpubs.nist.gov/nistpubs/Legacy/FIPS/fipspub24.pdf
  6. https://www.cs.uic.edu/~cornelia/papers/2024.ECAI.pdf
  7. https://digital.ahrq.gov/health-it-tools-and-resources/evaluation-resources/workflow-assessment-health-it-toolkit/all-workflow-tools/flowchart
  8. https://www.sjsu.edu/people/burford.furman/docs/me30/Notes_on_Algorithms.pdf
  9. https://blogs.onlineeducation.touro.edu/visually-organize-thoughts-mind-maps/
  10. https://www.umsl.edu/~sauterv/analysis/f06Papers/Nitakorn/
  11. https://vatraining.remote-learner.net/public/ONC/comp10_unit3b_lecture_handout.pdf
  12. https://nationalhumanitiescenter.org/pds/gilded/progress/text3/taylor.pdf
  13. https://web.mit.edu/allanmc/www/TheGilbreths.pdf
  14. https://archive.org/details/processcharts00gilb
  15. https://www.thegilbreths.com/resources/Gilbreth-Process-Charts-1921.pdf
  16. https://www.thegilbreths.com/tgno/tgno-therbligs.php
  17. https://ilssi.org/7_quality_tools_ishikawa/
  18. https://escholarship.org/content/qt2kt3x0th/qt2kt3x0th.pdf
  19. https://markpriestley.net/pdfs/FlowDiagramsAssertionsFormalMethods.pdf
  20. https://www.historyofinformation.com/detail.php?id=658
  21. https://www.iso.org/standard/5500.html
  22. https://link.springer.com/chapter/10.1007/11783183_17
  23. https://link.springer.com/chapter/10.1007/978-3-642-31223-6_26
  24. https://www.iso.org/standard/11955.html
  25. https://drakon-editor.sourceforge.net/DRAKON.pdf
  26. https://www.omg.org/spec/BPMN/2.0/PDF
  27. https://www.lucidchart.com/pages/what-is-a-swimlane-diagram
  28. https://www.lucidchart.com/pages/what-is-a-flowchart-tutorial
  29. https://www.efulfillmentservice.com/2015/06/order-fulfillment-process-flow-chart/
  30. https://online.visual-paradigm.com/diagrams/templates/flowchart/order-fulfillment-flowchart-
  31. https://clearbusinessoutcome.com/how-to-avoid-bottlenecks-with-process-mapping/
  32. https://www.planettogether.com/aps-trends/limitations-of-process-flowcharts
  33. https://online.visual-paradigm.com/knowledge/software-design/dfd-using-yourdon-and-demarco
  34. https://sites.nd.edu/businessanalysis/?page_id=392
  35. https://www.geeksforgeeks.org/software-engineering/difference-between-flowchart-and-data-flow-diagram-dfd/
  36. https://asana.com/resources/what-is-a-flowchart
  37. https://softwareengineering.stackexchange.com/questions/402241/how-to-represent-in-a-flowchart-data-fetched-from-a-database
  38. https://www.edrawsoft.com/flowchart/program-flowchart-definition.html
  39. https://www.programiz.com/article/flowchart-programming
  40. https://homes.luddy.indiana.edu/nensmeng/files/Ensmenger2016-draft.pdf
  41. https://miro.com/blog/flowchart-for-programming/
  42. https://eagereyes.org/blog/2016/nassi-shneiderman-diagrams
  43. https://www.geeksforgeeks.org/dsa/bubble-sort-algorithm/
  44. https://www.softwareideas.net/a/1598/bubble-sort-flowchart-
  45. https://www.sciencedirect.com/science/article/pii/S030439751500691X
  46. https://dl.acm.org/doi/10.1145/3635800.3636967
  47. https://www.atlassian.com/work-management/project-management/flowchart
  48. https://nulab.com/learn/design-and-ux/keep-it-simple-follow-flowchart-rules-for-better-diagrams/
  49. https://americanhistory.si.edu/collections/object-groups/flowcharting-templates
  50. https://www.smartdraw.com/flowchart/flowchart-tips.htm
  51. https://www.edrawsoft.com/flowchart-limitations.html
  52. https://www.yworks.com/products/yed/applicationfeatures
  53. https://www.microsoft.com/en-us/microsoft-365/visio
  54. http://dia-installer.de/doc/en/intro-chapter.html
  55. https://www.lucidchart.com/pages/enterprise
  56. https://miro.com/blog/features/realtimeboard-is-now-miro/
  57. https://www.drawio.com/doc/drawio-confluence-cloud
  58. https://www.canva.com/online-whiteboard/flowcharts/
  59. https://online.visual-paradigm.com/diagrams/solutions/free-flowchart-maker-online/
  60. http://www.flowgorithm.org/features/index.html
  61. https://www.lucidchart.com/blog/2023-lucidchart-highlights
  62. https://www.lucidchart.com/blog/new-diagramming-features-roundup
  63. https://www.drawio.com/integrations
  64. https://www.purdue.edu/leansixsigmaonline/blog/six-sigma-process-map/
  65. https://asq.org/quality-resources/lean/value-stream-mapping
  66. https://www.purdue.edu/leansixsigmaonline/blog/value-stream-mapping/
  67. https://dspace.mit.edu/bitstream/handle/1721.1/103819/16-842-fall-2009/contents/lecture-notes/MIT16_842F09_lec03.pdf
  68. https://stacks.cdc.gov/view/cdc/9322/cdc_9322_DS1.pdf
  69. https://users.ece.utexas.edu/~valvano/Volume1/IntroToEmbSys/Ch2_SoftwareDesign.html
  70. https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.pdf
  71. http://www.flowgorithm.org/
  72. https://peer.asee.org/flowgorithm-principles-for-teaching-introductory-programming-using-flowcharts
  73. https://watts.cs.sonoma.edu/SFC/SFC-v2-3.pdf
  74. https://www.cs.cmu.edu/~15110-s13/Wing06-ct.pdf
  75. https://slickplan.com/diagram/symbols
  76. https://www.researchgate.net/figure/Flowchart-of-multi-thread-parallel-algorithm_fig1_345967436
  77. https://www.cs.cmu.edu/~nbeckman/papers/race_detection_survey.pdf
  78. https://users.ece.utexas.edu/~valvano/EE345M/view01_Dataflow_Intro.pdf
  79. https://developer.ibm.com/articles/an-introduction-to-uml/
  80. https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-activity-diagram/
  81. https://ones.com/blog/mastering-scrum-process-flow-diagram-visual-guide-agile-success/
  82. https://www.drawio.com/blog/story-mapping
  83. https://www.tensorflow.org/decision_forests/tutorials/dtreeviz_colab
  84. https://marketplace.atlassian.com/apps/1210933/draw-io-diagrams-uml-bpmn-aws-erd-flowcharts
Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.