Software requirements: analysis and specification
Software requirements: analysis and specification
Flowcharting With the ANSI Standard: A Tutorial
ACM Computing Surveys (CSUR)
ACM Computing Surveys (CSUR)
Flow diagrams, turing machines and languages with only two formation rules
Communications of the ACM
Flowchart techniques for structured programming
ACM SIGPLAN Notices
Principles of Program Design
Structured programming
Flow diagrams: rise and fall of the first software engineering notation
Diagrams'06 Proceedings of the 4th international conference on Diagrammatic Representation and Inference
Twelve years of diagrams research
Journal of Visual Languages and Computing
| Hi-index | 0.00 |
The first diagrammatic notation used in software engineering represented the concept of flow. This paper considers the factors that affected the apparent departure of the flowchart from software engineering practice during the 1970s and 1980s and its subsequent return in the 1990s. A new emphasis on hierarchy (as level of abstraction) and on data structure meant that the general concept of flow was completely superseded, only to re-emerge later as a new duality of control flow and data flow. This reappearance took a variety of forms with varying semantics until its stabilisation in the latest version of the Unified Modeling Language. Flow is there re-instated as a fundamental concept in software engineering although its importance, and that of the activity diagram used to represent it, diminished as a consequence of its becoming just one among a wider set of paradigms for software systems development, each associated with its own diagrams.