Flowcharting With the ANSI Standard: A Tutorial
ACM Computing Surveys (CSUR)
Letters to the editor: go to statement considered harmful
Communications of the ACM
A syntactical chart of ALGOL 60
Communications of the ACM
Proposed standard flow chart symbols
Communications of the ACM
The Computer from Pascal to Von Neumann
The Computer from Pascal to Von Neumann
Flowchart techniques for structured programming
ACM SIGPLAN Notices
From theory to practice: the invention of programming, 1947-51
Dependable and Historic Computing
The diagram of flow: its departure from software engineering and its return
Diagrams'12 Proceedings of the 7th international conference on Diagrammatic Representation and Inference
Twelve years of diagrams research
Journal of Visual Languages and Computing
| Hi-index | 0.00 |
Drawings of water are the earliest, least abstract forms of flow diagram. Representations of ideal or generalised sequences for manufacturing or actual paths for materials between machines came next. Subsequently documentation of production and information flow become subjects for graphical representation. A similar level of abstraction was necessary for representations of invisible flows such as electricity. After initial use to define control, flow diagrams became a general purpose tool for planning automated computation at all levels of composition. Proliferation of syntax variants and the need for a common language for documentation were the motivations behind standardisation efforts. Public communication of metalevel systems information superseded private comprehension of detailed algorithmic processes as a primary function. Changes to programming language structures and their associated processes caused the initial demise of flow diagrams in software engineering.