This is my entry for the Weeping Horse award for the most boring blog post of the year. Another item stuffed in the back of the drawer of things I didn’t know what to do with.
We were told to buy one of these when I started my Computing Masters course in 1980. Except for the square and rectangular boxes, I never used it.
What is it? I don’t really know, other than to say it is a template for drawing symbols used in computer flowcharting. I hardly gave it a second glance until now. It relates to an approach to programming that was becoming outdated before the course began. I think it was used for designing COBOL programs that took ages to run with no human input once started. I have no idea how to use the symbols. What is an auxiliary operation, a terminal interrupt, or a transmittal tape? And there were even more symbols on the packet it came in, on both sides.
 |
| The packet it came in, and an example of how the symbols are used |
The course taught us a different technique called Jackson Structured Programming (JSP) which was more suited to programs that interact with the user, as in most of today’s software. JSP defines programs as combinations of sequences, selections, and repetitions. It uses a notation consisting only of rectangles, plain for sequences, marked O for selections and * for repetitions. If you adhere to its rules for putting them together, you avoid the unintelligible, spaghetti-like tangle of code that defeats most novice programmers. I found it invaluable.
Later, I used something called Structured Systems Analysis and Design Method (SSADM). This employed a further set of techniques with names such as Data Flow Diagrams, Logical Data Structures, and Entity Life Histories. It organised data into the most flexible and efficient form, which was helpful in systems that handle complex information, such as customer orders, stock control, or bus timetables. This figure shows some of the notations. I could probably just about remember enough to explain them further, but it would be gobbledygook.
 |
| Jackson Structured Programming example from my Masters Dissertation SSADM Logical Data Structure and Data Flow Diagram |
I know it is off the end of the autistic spectrum, but I enjoyed this kind of stuff and took great pride in it (and in what I was paid to do it). If the design is right, software works as intended without bugs that need fixing all the time. At the computer company I worked at, our large and complicated service management system did what it was supposed to do. It was used throughout Europe and elsewhere. The design was right. I would say that, today, companies like Amazon and Ebay largely have it right. So why don’t government systems such as for the DSS Carers Allowance? Why didn’t the Post Office? There used to be a saying based on the quality-time-cost triangle which was that you can have it good, you can have it quick, and you can have it cheap, but you can’t have it all three.
To come back to the template, it was not used. Like with books, do not buy anything a university or college recommends until it is needed. It might not be.
What to do with it? It takes up little space. It is back in the drawer with all the other useless rubbish.