Abstract
In the early days of computers, diagramming didn’t figure as an important topic in the design process. Further, the only pictorial method used was that of the flow chart. At that time there was little distinction between programming and design (nor, for that matter, between programmers and designers). The design and development process usually went something as follows:
-
Programmers thought about the problem to be solved.
-
They wrote lines of code to solve it.
-
The code was tested and modified until it was correct (or appeared to be so).
-
This source code was released as the system documentation.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Green, T.R.G. (1982), Pictures of programs and other processes, or how to do things with lines, Behaviour and Information Technology, Vol.1, No.1, pp3–36.
Martin, J. and McClure, C. (1985), Diagramming Techniques for Analysts and Programmers, Prentice-Hall, Inc., Englewood Cliffs, New Jersey 07632, USA, ISBN 0-13-208794-4.
O’Sullivan, V.J. (1986), The use of diagrams in the software development process, Master’s Thesis in Information Technology, Department of Electronic and Electrical Engineering, Loughborough University.
Rothon, N.M. (1979), ‘Design Structure Diagrams: a new standard in flow diagrams’, Computer Bulletin, Series 2, No. 19, pp4–6.
Author information
Authors and Affiliations
Rights and permissions
Copyright information
© 1991 J. E. Cooling
About this chapter
Cite this chapter
Cooling, J.E. (1991). Diagramming — an introduction. In: Software Design for Real-time Systems. Springer, Boston, MA. https://doi.org/10.1007/978-1-4899-2957-0_5
Download citation
DOI: https://doi.org/10.1007/978-1-4899-2957-0_5
Publisher Name: Springer, Boston, MA
Print ISBN: 978-0-442-31174-2
Online ISBN: 978-1-4899-2957-0
eBook Packages: Springer Book Archive